CN113411258B

CN113411258B - Message processing method and device

Info

Publication number: CN113411258B
Application number: CN202110629485.0A
Authority: CN
Inventors: 林长望; 陈梦骁; 李�昊
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2021-06-07
Filing date: 2021-06-07
Publication date: 2024-03-12
Anticipated expiration: 2041-06-07
Also published as: CN113411258A

Abstract

The application provides a message processing method and a message processing device, wherein the method is applied to first network equipment which is in an IPv6 networking, and the method comprises the following steps: receiving a first data message; acquiring a first forwarding table item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs according to the first data message; and forwarding the first data message through the first forwarding table item and the service resource matched with the network slice identifier.

Description

Message processing method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a message.

Background

Currently, increasingly diversified network services place various performance demands on the network. For example, high definition video services require a network to provide high bandwidth, assisted driving services require a network to provide low latency, and so on. The network slicing technology constructs a plurality of virtual network slices based on a set of shared network hardware facilities, and provides different services for users through different network slices so as to meet the demands of the users.

Often different network slices share the same network hardware facilities. For example, data packets belonging to different network slices are forwarded through the same router, but each network slice may require different network performance. For example, network slice 1 provides services for audio and video data streams, a higher link bandwidth needs to be configured, and network slice 2 provides services for mail data streams, and a common link bandwidth needs to be configured. Therefore, when the router forwards the data messages of different data flows, the router needs to identify the network slice to which the data messages belong, and then processes the data messages by adopting the action corresponding to the network slice.

Before processing the actual data message, each router in the network needs to issue routing information in the network through a routing protocol. And each router forms a forwarding table according to the received routing information, and guides the forwarding of the data message through the forwarding table. Therefore, the existing published routing information needs to be expanded to support the router to be capable of forwarding data messages of different network slices.

Disclosure of Invention

In view of this, the present application provides a method and apparatus for processing a packet, so as to enable a router to support forwarding of data packets of different network slices.

In a first aspect, the present application provides a method for processing a message, where the method is applied to a first network device, and the first network device is in an IPv6 network, and the method includes:

receiving a first data message;

acquiring a first forwarding table item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs according to the first data message;

and forwarding the first data message through the first forwarding table item and the service resource matched with the network slice identifier.

In a second aspect, the present application provides a method for processing a message, where the method is applied to a first network device, the first network device is in SRv network, and the first network device is a source node, and the method includes:

receiving a first data message sent by a first user terminal, wherein the first data message comprises message characteristics;

according to the message characteristics, determining a network slice to which the first data message belongs, and acquiring a network slice identifier of the network slice;

generating a second data message, wherein the second data message comprises a first destination address, the first destination address is a first SID, the first SID comprises a first prefix part and a first non-prefix part, and the first non-prefix part comprises the network slice identifier;

Acquiring a first forwarding table item for forwarding the second data message according to the first prefix part;

and forwarding the second data message through the first forwarding table item and the service resource matched with the network slice identifier.

In a third aspect, the present application provides a method for processing a message, where the method is applied to a first network device, the first network device is in SRv group network, and the first network device is an end node, and the method includes:

receiving a first data message sent by second network equipment, wherein the first data message comprises a first destination address, and the first destination address is a first SID of the first network equipment;

acquiring a network slice identifier and generating a second SID according to the first SID;

acquiring a first forwarding table item matched with the second SID according to the second SID;

In a fourth aspect, the present application provides a method for processing a message, where the method is applied to a first network device, the first network device is in SRv network, and the first network device is a transit node, and the method includes:

Receiving a first data message sent by second network equipment, wherein the first data message comprises a first destination address, and the first destination address is a first SID of third network equipment;

acquiring a first forwarding list item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs according to the first SID;

In a fifth aspect, the present application provides a packet processing apparatus, where the apparatus is applied to a first network device, and the first network device is in an IPv6 network, and the apparatus includes:

the receiving unit is used for receiving the first data message;

the acquisition unit is used for acquiring a first forwarding table item used for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs according to the first data message;

and the processing unit is used for forwarding the first data message through the first forwarding table item and the service resource matched with the network slice identifier.

In a sixth aspect, the present application provides a packet processing apparatus, where the apparatus is applied to a first network device, the first network device is in SRv network, and the first network device is a source node, and the apparatus includes:

the receiving unit is used for receiving a first data message sent by a first user terminal, wherein the first data message comprises message characteristics;

the acquisition unit is used for determining a network slice to which the first data message belongs according to the message characteristics and acquiring a network slice identifier of the network slice;

a generating unit, configured to generate a second data packet, where the second data packet includes a first destination address, where the first destination address is a first SID, and the first SID includes a first prefix portion and a first non-prefix portion, and the first non-prefix portion includes the network slice identifier;

the obtaining unit is further configured to obtain, according to the first prefix portion, a first forwarding table entry for forwarding the second data packet;

and the processing unit is used for forwarding the second data message through the first forwarding table item and the service resource matched with the network slice identifier.

In a seventh aspect, the present application provides a packet processing apparatus, where the apparatus is applied to a first network device, the first network device is in SRv network, and the first network device is an end node, and the apparatus includes:

a receiving unit, configured to receive a first data packet sent by a second network device, where the first data packet includes a first destination address, and the first destination address is a first SID of the first network device;

the acquisition unit is used for acquiring the network slice identifier and generating a second SID according to the first SID;

the obtaining unit is further configured to obtain, according to the second SID, a first forwarding table entry that is matched with the second SID;

In an eighth aspect, the present application provides a packet processing apparatus, where the apparatus is applied to a first network device, the first network device is in SRv network, and the first network device is a transit node, and the apparatus includes:

a receiving unit, configured to receive a first data packet sent by a second network device, where the first data packet includes a first destination address, and the first destination address is a first SID of a third network device;

The acquisition unit is used for acquiring a first forwarding table item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs according to the first SID;

In a ninth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the first aspect of the present application.

In a tenth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused to perform the method provided in the second aspect of the present application.

In an eleventh aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the third aspect of the present application.

In a twelfth aspect, the present application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the fourth aspect of the present application.

Therefore, by applying the message processing method and the device provided by the application, the first network equipment receives the first data message; according to the first data message, the first network equipment acquires a first forwarding table item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs; and forwarding the first data message by the first network equipment through the first forwarding table item and the service resource matched with the network slice identifier.

Therefore, by carrying the network slice identifier in the data message, each router in the forwarding path can acquire the matched service resource according to the network slice identifier, and process the data message through the service resource. The router can support forwarding of the data messages of different network slices, and the data messages of different network slices do not provide different services.

Drawings

Fig. 1 is a flowchart of a message processing method provided in an embodiment of the present application;

fig. 2 is a schematic structural diagram of an OSPFv3 network slice identifier location sub-TLV provided in an embodiment of the present application;

fig. 3 IS a schematic diagram of an IS-IS network slice identifier location sub-TLV structure provided in an embodiment of the present application;

FIG. 4 is a flowchart of another message processing method according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of another method for processing a message according to an embodiment of the present disclosure;

FIG. 6 is a flowchart of another method for processing a message according to an embodiment of the present disclosure;

fig. 7 is a networking schematic diagram of implementing a message processing method in an IPv6 networking according to an embodiment of the present application;

fig. 8 is a networking schematic diagram of implementing a message processing method in SRv networking according to an embodiment of the present application;

fig. 9 is a block diagram of a message processing apparatus according to an embodiment of the present application;

FIG. 10 is a block diagram of another message processing apparatus according to an embodiment of the present application;

FIG. 11 is a block diagram of another message processing apparatus according to an embodiment of the present application;

FIG. 12 is a diagram of another message processing apparatus according to an embodiment of the present disclosure;

fig. 13 is a hardware structure of a network device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The following describes the message processing method provided in the embodiment of the present application in detail. Referring to fig. 1, fig. 1 is a flowchart of a message processing method provided in an embodiment of the present application. The method is applied to the first network device, and the message processing method provided by the embodiment of the application can comprise the following steps.

Step 110, a first data message is received.

Specifically, the first network device is within an IPv6 networking. The first network device may in particular be a source node or a transit node or an end node.

When the first network device is specifically a source node, the first network device receives a first data message sent by a user terminal.

When the first network device is specifically a transit node or an end node, the first network device receives a first data message sent by the second network device. The second network device is a last hop device of the first network device.

Step 120, according to the first data packet, a first forwarding table item for forwarding the first data packet and a network slice identifier of a network slice to which the first data packet belongs are obtained.

Specifically, according to the description of step 110, after receiving the first data packet, the first network device obtains the first forwarding table entry and the network slice identifier according to the first data packet. The first forwarding table entry is a table entry for forwarding the first data packet, and the network slice identifier is an identifier of a network slice to which the first data packet belongs.

Further, in a first implementation, the first data packet includes a first destination address, the first destination address including a first prefix portion and a first non-prefix portion, the first non-prefix portion including a network slice identity.

In this embodiment of the present application, regardless of the node role of the first network device, after the first network device receives the first data packet, the first destination address is obtained from the first data packet, and the first prefix portion is obtained from the first destination address.

From the local forwarding table, the first network device searches for a first forwarding table entry matching the first prefix portion according to the first prefix portion. The first forwarding table entry includes a network slice identification tag and network slice identification location information.

The first network device obtains a network slice identifier from a first non-prefix portion included in the first destination address based on the network slice identifier tag and the network slice identifier location information.

It will be appreciated that in the first implementation described above, the network slice identity is carried by the user terminal in the first data message. After the network device receives the first data packet, the network slice identifier may be obtained from the first non-prefix portion by searching for the forwarding table entry. The user terminal carries the network slice identifier in the first data message not within the scope of the present application.

When the first network device is an end node, the first network device determines that the next hop is a user terminal after acquiring the first forwarding entry. According to the network slice identification mark, the first network device determines that the network slice identification included in the first destination address needs to be removed and reverts to the address of the user terminal. And the first network equipment updates the bit occupied by the network slice identifier in the first non-prefix part to 0 to obtain the address of the user terminal.

In a second implementation, the first data message includes a message feature, which may be specifically five-tuple information; or the first data message comprises flow information carried by HBH header and intra-DO-header option in IPv6 extension header.

In this embodiment of the present application, the first network device is a source node, and after receiving the first data packet, the first network device obtains a first destination address from the first data packet, and obtains a first prefix portion from the first destination address.

According to the message characteristics, the first network device identifies the message type of the first data message. According to the message type, the first network device determines the network slice to which the first data message belongs and acquires the network slice identifier of the network slice from the local configuration.

And according to the network slice identifier position information, the first network equipment configures the network slice identifier in the first non-prefix part to obtain a second non-prefix part. The first network device generates a second destination address that includes a second prefix portion and a second non-prefix portion, the second prefix portion being identical to the first prefix portion. The second destination address is used for acquiring the network slice identifier from the second non-prefix portion after the next hop device of the first network device receives the data message including the second destination address.

The process of acquiring the network slice identifier by the next hop device of the first network device is the same as the process of acquiring the network slice identifier in the foregoing first implementation manner, and will not be repeated here.

In a third implementation, the first data packet includes a packet feature, which may be quintuple information in particular; or the first data message comprises flow information carried by HBH header and intra-DO-header option in IPv6 extension header.

The first data message also includes a first destination address including a first prefix portion and a first non-prefix portion.

In this embodiment of the present application, the first network device is a source node, and when the first network device receives the first data packet, the first network device obtains the packet characteristics from the first data packet. According to the message characteristics, the first network device identifies the message type of the first data message. According to the message type, the first network device determines the network slice to which the first data message belongs and acquires the network slice identifier of the network slice from the local configuration.

After the network slice identifier of the network slice is obtained from the local configuration, the first network device obtains the network slice identifier position information from the local configuration. And according to the network slice identifier position information, the first network equipment configures the network slice identifier in the first non-prefix part to obtain a second non-prefix part. The first network device generates a second destination address that includes a second prefix portion and a second non-prefix portion, the second prefix portion being identical to the first prefix portion.

After the first network device generates the second destination address, the first network device searches the local forwarding table for a second forwarding table entry matching the second prefix portion according to the second prefix portion (i.e., the first prefix portion). The first network device may forward a data message to the next hop device according to the second forwarding table entry, where the data message includes the second destination address. The second forwarding table entry also includes a network slice identification tag and network slice identification location information. The second destination address is used for acquiring the network slice identifier from the second non-prefix portion after the next hop device of the first network device receives the data message including the second destination address.

The process of acquiring the network slice identifier by the next hop device of the first network device is the same as the process of acquiring the network slice identifier in the foregoing first implementation manner, and will not be repeated here. It will be appreciated that in the second and third implementations described above, the source node carries the network slice identifier in the data packet, and the data packet sent by the user terminal no longer includes the network slice identifier. After the next hop device of the source node receives the data message, the network slice identifier can be obtained from the second non-prefix part by searching the forwarding table entry.

And 130, forwarding the first data message through the first forwarding table item and the service resource matched with the network slice identifier.

Specifically, according to the description of step 120, regardless of the node role of the first network device, after the first network device obtains the first forwarding table entry and the network slice identifier, according to the service resource matched by the network slice identifier and the next hop address and the outgoing interface information included in the first forwarding table entry, the first network device forwards the first data packet to the network device or the user terminal indicated by the next hop address through the outgoing interface indicated by the outgoing interface information according to the service resource.

Therefore, by applying the message processing method provided by the application, the first network device receives the first data message; according to the first data message, the first network equipment acquires a first forwarding table item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs; and forwarding the first data message by the first network equipment through the first forwarding table item and the service resource matched with the network slice identifier.

Therefore, by carrying the network slice identifier in the data message, each router in the forwarding path can acquire the matched service resource according to the network slice identifier, and process the data message through the service resource. The router can support forwarding of the data messages of different network slices and provide different services for the data messages of different network slices.

Optionally, in the embodiment of the present application, before the first network device receives the first data packet, a process of each network device in the IPv6 network publishing the route advertisement packet to each other is further included.

Specifically, the first network device generates a first route announcement message, where the first route announcement message includes a user terminal address and network slice identifier location information.

The first network device sends a first route advertisement message to a third network device. And the third network equipment acquires the user terminal address and the network slice identification position information from the first route notification message after receiving the first route notification message. And generating a third forwarding table item by third network equipment according to the user terminal address and the network slice identification position information. The third forwarding table entry includes a prefix portion of the user terminal address, a next hop address, outgoing interface information, a network slice identification tag, and network slice identification location information.

The fourth network device generates a second route announcement message, and the second route announcement message comprises a user terminal address and network slice identification position information.

The fourth network device sends a second route advertisement message to the first network device. And after the first network equipment receives the second route notification message, acquiring the user terminal address and the network slice identification position information from the second route notification message. And generating a fourth forwarding table item by the first network equipment according to the address of the user terminal and the network slice identification position information. The fourth forwarding table entry includes a prefix portion of the user terminal address, a next hop address, outgoing interface information, a network slice identification tag, and network slice identification location information.

Further, in embodiments of the present application, network devices may communicate routing information within an IPv6 network via IGP protocols. The following description will take an IGP protocol, specifically an OSPFv3 protocol, an IS-IS protocol, as an example.

In one implementation, the IGP protocol is specifically the OSPFv3 protocol. The OSPFv3 protocol is run within the first network device. The first network device may publish a route including the network slice identity using an Inter-extension-Area-Prefix link state advertisement (E-Inter-Area-Prefix-LSA), an Intra-extension-Area-Prefix link state advertisement (E-Intra-Area-Prefix-LSA), or an extension-autonomous-outside-domain link state advertisement (E-AS-External-LSA).

The E-Inter-Area-Prefix-LSA comprises an Inter-Area-Prefix TLV; the E-Intra-Area-Prefix-LSA comprises Intra-Area-Prefix TLV; the E-AS-External-LSA includes an External-Prefix TLV. The Intra-Area-Prefix TLV, intra-Area-Prefix TLV and External-Prefix TLV all comprise a Prefix Length field, an Address Prefix field and a Sub-TLVs field.

In the embodiment of the application, the first Network device stores a Prefix Length in a Prefix Length field, stores a Prefix portion of an IPv6 Address in an Address Prefix field, and sets an OSPFv3 Network Slice identifier location Sub-TLV (OSPFv 3 Network-Slice-ID-location Sub-TLV) in a Sub-TLVs field.

As shown in fig. 2, fig. 2 is a schematic diagram of an OSPFv3 network slice identifier location sub-TLV structure provided in an embodiment of the present application. In fig. 2, the OSPFv3 Network-Slice-ID-Position Sub-TLV includes a Sub-TLV Type (Sub-TLV Type) field, a Sub-TLV Length (Sub-TLV Length) field, a Flags (Flags) field, a Reserved (Reserved) field, a Start Position (Start Position) field, and an ID Length (ID Length) field.

The Start Position field stores the initial Position of the network slice identifier in the IPv6 address (specifically, a non-prefix part), and the highest bit of the IPv6 address is 0, and the initial Position is calculated in an incremental way from high to low; the unit is a bit; the ID Length field stores the Length of the network slice identifier in bits. If standardization is needed, the Sub-TLV type is distributed by an Internet digital distribution mechanism (English: internet Assigned Numbers Authority, abbreviated as IANA); if normalization is not required, the Sub-TLV Type field may choose an unoccupied value, e.g., 33000, according to the OSPF 3 protocol; the Sub-TLV Length field is the Length of all subsequent fields in the Sub-TLV (excluding the Sub-TLV Type field and the Sub-TLV Length field); the flag field is temporarily undefined and has a value of 0; the Reserved field may be used for future extensions.

In another implementation, the IGP protocol IS embodied as an IS-IS protocol. The IS-IS protocol IS run within the first network device. The first network device may issue a route including the network slice identity using an IPv6 Reachability TLV (IPv 6 Reachability TLV) or a Multi-topology reachable IPv6 prefix TLV (Multi-Topology Reachable IPv6 Prefixes TLV).

The IPv6 REACHAVITY TLV, multi-Topology Reachable IPv6 Prefix TLV includes a Prefix Len field, a Prefix field, and a Sub-TLVs field.

In the embodiment of the application, the first Network device stores a Prefix length in a Prefix Len field, stores a Prefix portion of an IPv6 address in the Prefix field, and sets an IS-IS Network Slice identifier location Sub-TLV (IS-IS Network-Slice-ID-Position Sub-TLV) in a Sub-TLVs field.

As shown in fig. 3, fig. 3 IS a schematic diagram of an IS-IS network slice identifier location sub-TLV structure provided in an embodiment of the present application. In fig. 3, the IS-IS Network-Slice-ID-Position Sub-TLV includes a Sub-TLV Type (Sub-TLV Type) field, a Sub-TLV Length (Sub-TLV Length) field, a Flags (Flags) field, a Reserved (Reserved) field, a Start Position (Start Position) field, and an ID Length (ID Length) field.

The Start Position field stores the initial Position of the network slice identifier in the IPv6 address (specifically, a non-prefix part), and the highest bit of the IPv6 address is 0, and the initial Position is calculated in an incremental way from high to low; the ID Length field stores the Length of the network slice identifier in bits. If normalization is required, sub-TLV types are allocated by IANA; if normalization IS not required, the Sub-TLV Type field may choose an unoccupied value, e.g., 200, according to the IS-IS protocol; the Sub-TLV Length field is the Length of all subsequent fields in the Sub-TLV (excluding the Sub-TLV Type field and the Sub-TLV Length field); the flag field is temporarily undefined and has a value of 0; the Reserved field may be used for future extensions.

Optionally, in the embodiment of the present application, before the first network device receives the first data packet, the method further includes a process that the first network device receives a configuration instruction input by a controller or a user, and performs network slice identifier configuration locally according to the configuration instruction.

Specifically, in one implementation, the controller generates a first configuration instruction that includes a network slice identifier and a service resource that the network slice identifier matches. The controller issues a first configuration instruction to the first network device.

And after the first network equipment receives the first configuration instruction, acquiring the network slice identifier and the service resource matched with the network slice identifier from the first configuration instruction.

The first network device stores the network slice identity and the service resources that match the network slice identity.

The controller generates a second configuration instruction that includes a configuration rule for the network slice identification. The controller issues a second configuration instruction to the first network device.

And after the first network equipment receives the second configuration instruction, acquiring the configuration rule of the network slice identifier from the second configuration instruction.

The first network device stores configuration rules for network slice identification.

In another implementation, a first network device receives a first configuration instruction input by a user, the first configuration instruction including a network slice identity and a service resource matching the network slice identity.

The first network device receives a second configuration instruction input by a user, wherein the second configuration instruction comprises a configuration rule of a network slice identifier.

In the embodiment of the application, the configuration of the network slice in the network device defines differentiated forwarding behaviors for the data messages belonging to different network slices. The network device stores each network slice identifier, the service resources that match the network slice identifier, and the configuration rules for the network slice identifiers. When forwarding the data message, the network device identifies the network slice to which the data message belongs, and decides forwarding behavior according to the stored service resource matched with the network slice identifier.

In one example, routers A, B, C form an IPv6 network, and the physical link bandwidths between a and B, B and C are all 100G. The controller slices the network into 2 network slices, network slice 1 allocates 70G bandwidth and network slice 2 allocates 30G bandwidth. For B, when forwarding the data message from A to C or from C to A, the link bandwidth occupied by forwarding the data message belonging to the network slice 1 is not more than 70G, and the link bandwidth occupied by forwarding the data message of the network slice 2 is not more than 30G.

B can specify the service resource of the network slice, the network slice identification and the service resource matched with the network slice identification in a mode of being issued by the controller or being input by a user. For example, AB links, BC links in network slice 1 occupy 70G bandwidth; and the AB link and the BC link in the network slice 2 occupy 30G bandwidth. B configures ase:Sub>A network slice identifier, ase:Sub>A service resource matching the network slice identifier at interface B-A.

For example, network slice identifier 1—link bandwidth 70G; network slice identifier 2—link bandwidth 30G. B, configuring a network slice identifier and service resources matched with the network slice identifier at interfaces B-C. For example, network slice identifier 1—link bandwidth 70G; network slice identifier 2—link bandwidth 30G.

In an embodiment of the present application, the configuration rule of the network slice identifier includes network slice identifier location information. Wherein the network slice identity location information comprises the location of the non-prefix portion of the network slice identity included at the destination address and the length of the network slice identity.

The IPv6 address comprises a prefix part and a non-prefix part, the high order of the IPv6 address is still used for storing the prefix part, and the prefix part represents the positions of the user terminal and the network equipment in the network, so that the guiding routing and the data message forwarding are realized; the lower bits of the IPv6 address are used to store the non-prefix portion, and part of the bits in the non-prefix portion are used to store the network slice identity.

For example, the upper bits (96 bits) of the IPv6 address store the prefix portion, and the lower bits (32 bits) of the IPv6 address store the network slice identifier; the upper bits (64 bits) of the IPv6 address store the prefix portion, the lower bits of the IPv6 address consist of three portions, the first portion (16 bits) for other purposes, the second portion (32 bits) store the network slice identity, and the third portion (16 bits) for other purposes.

In the non-prefix portion of the IPv6 address, the location and length of the network slice identifier may depend on the actual application. To facilitate a uniform understanding of the network slice identity by all routers within the network, the length of the network slice identity remains the same between different routers. However, the location of the network slice identity within the non-prefix portion of the IPv6 address may be the same or different.

The following describes the message processing method provided in the embodiment of the present application in detail. Referring to fig. 4, fig. 4 is a flowchart of another message processing method according to an embodiment of the present application. The method is applied to the first network device, and the message processing method provided by the embodiment of the application can comprise the following steps.

Step 410, a first data message sent by a first user terminal is received, where the first data message includes a message feature.

Specifically, the first network device is within a segment routing (English: segment Routing over IPv6, SRv) networking based on an IPv6 network. The first network device may be embodied as a source node.

The first network equipment receives a first data message sent by the user terminal. The first data message includes a message feature, which may be specifically five-tuple information; or the first data message comprises flow information carried by HBH header and intra-DO-header option in IPv6 extension header.

Step 420, determining a network slice to which the first data packet belongs according to the packet characteristics, and obtaining a network slice identifier of the network slice.

Specifically, according to the description of step 410, after receiving the first data packet, the first network device obtains the packet characteristics from the first data packet.

According to the message characteristics, the first network device determines the network slice to which the first data message belongs and the network slice identification of the network slice.

Further, after the first network device receives the first data message, the message feature is obtained from the first data message. According to the message characteristics, the first network device identifies the message type of the first data message. According to the message type, the first network device determines the network slice to which the first data message belongs and acquires the network slice identifier of the network slice from the local configuration.

Step 430, generating a second data packet, where the second data packet includes a first destination address, where the first destination address is a first SID, and the first SID includes a first prefix portion and a first non-prefix portion, and the first non-prefix portion includes the network slice identifier.

Specifically, according to the description of step 420, the first network device obtains the network slice identifier and generates the second data packet. The second data message includes a first destination address, where the first destination address is a first segment identifier (english: segment Identifier, abbreviated: SID), the first SID includes a first prefix portion and a first non-prefix portion, and the first non-prefix portion includes a network slice identifier.

Further, the first data message further includes a second destination address; the second data message also includes a segment list including at least one SID. Each SID includes a network slice identity, each SID is for indicating a SID of each end node in a forwarding path for the first network device to the second network device, and at least one SID includes the first SID.

The second network device is an end node, and the second user terminal indicated by the second destination address is accessed to the end node.

In the embodiment of the present application, the first network device generates the second data packet, which specifically includes:

the first network device obtains a second SID for each end node in the forwarding path, each second SID including a second prefix portion and a second non-prefix portion. And obtaining the configuration rule of the network slice identifier from the local configuration by the first network equipment.

The first network device configures a network slice identifier in each of the second non-prefix portions according to the configuration rules of the network slice identifier. The first network device generates a third SID for each end node, each third SID comprising a third prefix portion and a third non-prefix portion. The third prefix portion is identical to the second prefix portion, and the third non-prefix portion includes a network slice identification.

The first network device generates a segment list based on the location of each end node in the forwarding path, the segment list including the third SID. And acquiring the first SID from the third SID by the first network equipment, wherein the first SID is the SID of the next hop end node of the first network equipment. The first network device configures the first SID at a first destination address and configures the first destination address at an IPv6 extension header. The first network device generates a segment list and configures the segment list in the SRH header. And the first network equipment encapsulates the IPv6 extension header and the SRH header on the outer layer of the first data message to obtain a second data message.

In this step, the first network device needs to encapsulate the IPv6 extension header and the SRH header at the outer layer of the first data packet as the source node. The first network device generates a first destination address according to the foregoing manner, and configures the first destination address in the IPv6 extension header. The first network device generates a segment list (including the SIDs of all end nodes in the forwarding path) according to the foregoing manner, and configures the segment list in a segment routing (english: segment Routing Header, abbreviated: SRH) header. And the first network equipment encapsulates the IPv6 extension header and the SRH header on the outer layer of the first data message to obtain a second data message.

The IPv6 extension header, other fields of the SRH header, and ordering of SIDs in the segment list are all configured according to the existing SRv protocol, and are not repeated here.

Step 440, obtaining a first forwarding table item for forwarding the second data packet according to the first prefix portion.

Specifically, after the first network device generates the second data packet according to the description of step 430, the first network device obtains, according to the first prefix portion, a first forwarding table item for forwarding the second data packet. The first forwarding table entry includes a prefix portion of the SID of the end node, a next hop address, outgoing interface information.

It will be appreciated that the first forwarding table entry also includes network slice identification tags and network slice identification location information.

And 450, forwarding the second data message through the first forwarding table item and the service resource matched with the network slice identifier.

Specifically, according to the description of step 440, after the first network device obtains the first forwarding table, according to the service resource matched by the network slice identifier and the next hop address and the outgoing interface information included in the first forwarding table, the first network device forwards the first data packet to the network device indicated by the next hop address through the outgoing interface indicated by the outgoing interface information according to the service resource.

Therefore, by applying the message processing method provided by the application, the first network device receives the first data message sent by the first user terminal, and the first data message comprises the message characteristics; according to the characteristics of the message, the first network equipment determines a network slice to which the first data message belongs and acquires a network slice identifier of the network slice; the first network device generates a second data message, wherein the second data message comprises a first destination address, the first destination address is a first SID, the first SID comprises a first prefix part and a first non-prefix part, and the first non-prefix part comprises a network slice identifier; according to the first prefix part, the first network equipment acquires a first forwarding table item for forwarding the second data message; and forwarding the second data message by the first network equipment through the first forwarding table item and the service resource matched with the network slice identifier.

Optionally, in the embodiment of the present application, before the first network device receives the first data packet, a process of receiving a route advertisement packet issued by each network device in the SRv network group is further included.

Specifically, the third network device generates a first route advertisement message (also referred to as a location (Locator) route), where the first route advertisement message includes the SID of the end node and the network slice identifier location information.

The third network device sends a first route advertisement message to the first network device. And after the first network equipment receives the first route notification message, acquiring SID of the end node and network slice identification position information from the first route notification message. And generating a second forwarding table item by the first network equipment according to the SID of the end node and the network slice identification position information. The second forwarding table entry includes a prefix portion of the SID of the end node, a next hop address, outgoing interface information, a network slice identification tag, and network slice identification location information.

Further, in embodiments of the present application, network devices may communicate the routing information within the SRv network via IGP protocols. The following description will take an IGP protocol, specifically an OSPFv3 protocol, an IS-IS protocol, as an example.

In one implementation, the IGP protocol is specifically the OSPFv3 protocol. The OSPFv3 protocol is run within the first network device. The first network device may utilize SRv to locate a link state advertisement (SRv 6 Locator LSA), an Inter-extension Area Prefix link state advertisement (E-Inter-Area-Prefix-LSA), an Intra-extension Area Prefix link state advertisement (E-Intra-Area-Prefix-LSA), or an extension autonomous outside domain link state advertisement (E-AS-External-LSA) to publish a route including the network slice identity.

SRv6 Locator LSA includes SRv6 Locator TLV. SRv6 the Locator TLV includes a Locator Length field, a Locator field, and a Sub-TLVs field.

In the embodiment of the application, the first Network device stores the prefix Length in the Locator Length field, stores the prefix portion of the SID in the Locator field, and sets an OSPFv3 Network Slice identifier location Sub-TLV (OSPFv 3 Network-Slice-ID-location Sub-TLV) in the Sub-TLVs field.

In fig. 2, the OSPFv3 Network-Slice-ID-Position Sub-TLV includes a Sub-TLV Type (Sub-TLV Type) field, a Sub-TLV Length (Sub-TLV Length) field, a Flags (Flags) field, a Reserved (Reserved) field, a Start Position (Start Position) field, and an ID Length (ID Length) field.

The Start Position field stores the initial Position of the network slice identifier in the SID (specifically, a non-prefix part), and the highest bit of the SID is 0, so that the initial Position is calculated in an incremental way from high to low; the unit is a bit; the ID Length field stores the Length of the network slice identifier in bits. If normalization is required, sub-TLV types are allocated by IANA; if normalization is not required, the Sub-TLV Type field may choose an unoccupied value, e.g., 33000, according to the OSPF 3 protocol; the Sub-TLV Length field is the Length of all subsequent fields in the Sub-TLV (excluding the Sub-TLV Type field and the Sub-TLV Length field); the flag field is temporarily undefined and has a value of 0; the Reserved field may be used for future extensions.

The routing procedure of the E-Inter-Area-Prefix-LSA, E-Intra-Area-Prefix-LSA, E-AS-External-LSA publication including the network slice identifier is the same AS the routing procedure of the foregoing embodiment publication including the network slice identifier in the IPv6 networking, and will not be repeated again.

In another implementation, the IGP protocol IS embodied as an IS-IS protocol. The IS-IS protocol IS run within the first network device. The first network device may issue a route including the network slice identity using a SRv6 location TLV (SRv 6 Locator TLV), an IPv6 Reachability TLV (IPv 6 Reachability TLV), or a Multi-topology reachable IPv6 prefix TLV (Multi-Topology Reachable IPv6 Prefixes TLV).

SRv6 the Locator TLV includes a Loc-Size field, a Locator field, and a Sub-TLVs field.

In the embodiment of the application, the first Network device stores the prefix length in the Loc-Size field, stores the prefix portion of the SID in the Locator field, and sets an IS-IS Network Slice identifier location Sub-TLV (IS-IS Network-Slice-ID-Position Sub-TLV) in the Sub-TLVs field.

In fig. 3, the IS-IS Network-Slice-ID-Position Sub-TLV includes a Sub-TLV Type (Sub-TLV Type) field, a Sub-TLV Length (Sub-TLV Length) field, a Flags (Flags) field, a Reserved (Reserved) field, a Start Position (Start Position) field, and an ID Length (ID Length) field.

The Start Position field stores the initial Position of the network slice identifier in the SID (specifically, a non-prefix part), and the highest bit of the SID is 0, so that the initial Position is calculated in an incremental way from high to low; the ID Length field stores the Length of the network slice identifier in bits. If normalization is required, sub-TLV types are allocated by IANA; if normalization IS not required, the Sub-TLV Type field may choose an unoccupied value, e.g., 200, according to the IS-IS protocol; the Sub-TLV Length field is the Length of all subsequent fields in the Sub-TLV (excluding the Sub-TLV Type field and the Sub-TLV Length field); the flag field is temporarily undefined and has a value of 0; the Reserved field may be used for future extensions.

The routing procedure for issuing the IPv6 Reachability TLV or the Multi-Topology Reachable IPv6 Prefixes TLV including the network slice identifier is the same as the routing procedure for issuing the network slice identifier in the IPv6 networking in the foregoing embodiment, and will not be repeated again.

It should be noted that, in this embodiment, the process of locally configuring the network slice identifier by the first network device according to the configuration instruction is similar to the process of locally configuring the network slice identifier by the first network device according to the configuration instruction described in the foregoing embodiment, and will not be repeated here.

The configuration rules of the network slice identifier are briefly described below.

In an embodiment of the present application, the configuration rule of the network slice identifier includes network slice identifier location information. Wherein the network slice identification location information includes a location of the network slice identification at the non-prefix portion included by the SID and a length of the network slice identification.

Wherein the SID includes a location (Locator) field, a Function (Function) field, and an images field (optional). The Locator field is a prefix part and is used for guiding routing and forwarding; the Function field and the structures field are non-prefix parts, the Function field is used for indicating the forwarding behavior corresponding to the SID, and the structures field represents parameters used in the forwarding behavior.

In the embodiment of the application, the network slice identifier may be stored at a selected location after the Locator field.

In one example, the SID is 128 bits, the first 64 bits are the prefix portion, and the remaining 64 bits are the non-prefix portion. In the non-prefix portion, the first 32 bits are used to store the network slice identity, and the remaining 32 bits are the Function field and the graphics field.

In another example, the SID is 128 bits, the first 64 bits are prefix portions, and the remaining 64 bits are non-prefix portions. In the non-prefix portion, the first 16 bits are the Function field, the middle 32 bits are used to store the network slice identity, and the remaining 16 bits are the graphics field.

In another example, the SID is 128 bits, the first 64 bits are prefix portions, and the remaining 64 bits are non-prefix portions. In the non-prefix portion, the first 32 bits are the Function field and the structures field, with the remaining 32 bits being used to store the network slice identification.

In the non-prefix portion of the SID, the location and length of the network slice identifier may depend on the actual application. To facilitate a uniform understanding of the network slice identity by all routers within the network, the length of the network slice identity remains the same between different routers. However, the location of the network slice identity within the non-prefix portion of the SID may be the same or different.

The following describes the message processing method provided in the embodiment of the present application in detail. Referring to fig. 5, fig. 5 is a flowchart of another message processing method according to an embodiment of the present application. The method is applied to the first network device, and the message processing method provided by the embodiment of the application can comprise the following steps.

Step 510, receiving a first data packet sent by a second network device, where the first data packet includes a first destination address, the first destination address is a first SID, and the first SID includes a network slice identifier.

Specifically, the first network device is within SRv6 network. The first network device may be embodied as an end node.

The first network device receives a first data message sent by the second network device. The second network device is a last hop device of the first network device. The first data message includes a first destination address, which is a first SID. The first SID includes a first prefix portion and a first non-prefix portion, the first non-prefix portion including a network slice identification.

It is understood that the first data message includes an IPv6 extension header and an SRH header, the SRH header including a segment list. The two heads are encapsulated at the outer layer of the original data sent by the user terminal by the source node, and the source node forwards the encapsulated data message to the end node in the forwarding path through the transit node.

The transit node does not update the IPv6 extension header and the SRH header, and only searches a local forwarding table (corresponding to the Locator route) according to the prefix portion of the destination address, and forwards the local forwarding table to the end node in the forwarding path.

The end nodes in the forwarding path update the IPv6 extension header and the SRH header according to the existing SRv6 protocol. If the node is not the last end node in the segment list, the local forwarding table (corresponding to the Locator route) is searched according to the prefix part of the destination address, and the node is forwarded to other end nodes in the forwarding path. If the self is the last end node in the segment list, recovering the SID of the self according to the destination address, and searching the local forwarding table (corresponding to SID route) according to the SID of the self again. And carrying out corresponding processing on the data message according to the local forwarding table.

Step 520, according to the first SID, obtaining the network slice identifier and generating a second SID, where the second SID is the SID of the first network device.

Specifically, after the first SID is obtained by the first network device, the network slice identifier is obtained from the first SID, as described in step 510. The first network device generates a second SID based on the first SID, the second SID being the SID of the first network device.

In this embodiment of the present application, according to the first SID, the first network device obtains the network slice identifier and generates the second SID, which specifically includes:

according to the first prefix part, the first network device obtains a second forwarding table entry for forwarding the first data message, where the second forwarding table entry is specifically a forwarding table entry corresponding to the Locator route. The second forwarding entry includes a network slice identification tag and network slice identification location information.

The first network device obtains a network slice identification from the first non-prefix portion based on the network slice identification tag and the network slice identification location information. As can be seen from the foregoing embodiments, the network slice identification location information includes the location of the network slice identification at the non-prefix portion included by the SID and the length of the network slice identification.

The first network device updates a bit occupied by the network slice identifier in the first non-prefix portion to 0, and obtains a second non-prefix portion. The first network device combines the second prefix portion and the second non-prefix portion into a second SID. Wherein the second prefix portion is identical to the first prefix portion.

It can be understood that the forwarding table entry corresponding to the Locator route includes a next-hop address, where the next-hop address is a local address of the first network device, and then the first network device needs to generate the second SID according to the first SID.

And 530, acquiring a first forwarding table item matched with the second SID according to the second SID.

Specifically, after the first network device generates the second SID according to the description of step 520, the first network device obtains the first forwarding entry matching the second SID according to the second SID. The first forwarding table entry is specifically a forwarding table entry corresponding to SID routing of the first network device. The first forwarding entry includes an End instruction with a first-to-last segment decapsulation (english: ultimate Segment Decapsulation, abbreviated: USD).

Step 540, forwarding the first data packet through the first forwarding table item and the service resource matched with the network slice identifier.

Specifically, according to the description of step 530, after the first network device obtains the first forwarding table, the first network device forwards the first data packet to the user terminal according to the service resource that is matched with the network slice identifier and the End instruction with the USD that is included in the first forwarding table.

Therefore, by applying the message processing method provided by the application, the first network device receives the first data message sent by the second network device, the first data message comprises a first destination address, the first destination address is a first SID, and the first SID comprises a network slice identifier; according to the first SID, the first network device acquires the network slice identifier and generates a second SID, wherein the second SID is the SID of the first network device; according to the second SID, the first network equipment acquires a first forwarding table item matched with the second SID; and forwarding the first data message by the first network equipment through the first forwarding table item and the service resource matched with the network slice identifier.

Optionally, in this embodiment of the present application, before the first network device receives the first data packet, a process of locally generating a forwarding table entry corresponding to the Locator route and generating a forwarding table entry corresponding to the SID route of the first network device is further included.

Specifically, the first network device configures its own SID, i.e., the second SID. According to the second SID, the first network device generates a first forwarding table entry including the second SID, the address of the first network device, and the message processing action. The message processing action is an End instruction with USD.

The first network device obtains a prefix portion from the second SID. And generating a second forwarding table item according to the prefix part, wherein the second forwarding table item comprises the prefix part, the address of the first network equipment, the network slice identification mark and the network slice identification position information.

Optionally, in the embodiment of the present application, before the first network device receives the first data packet, a process of issuing a route advertisement packet in the SRv network is further included.

It should be noted that, in this embodiment, the process of issuing the route advertisement message by the first network device is similar to the process of issuing the route advertisement message by the first network device described in the foregoing embodiment, and will not be repeated here.

It should be noted that, in this embodiment, the process of locally configuring the network slice identifier by the first network device according to the configuration instruction is the same as the process of locally configuring the network slice identifier by the first network device according to the configuration instruction described in the foregoing embodiment, and will not be repeated here.

The following describes the message processing method provided in the embodiment of the present application in detail. Referring to fig. 6, fig. 6 is a flowchart of another message processing method according to an embodiment of the present application. The method is applied to the first network device, and the message processing method provided by the embodiment of the application can comprise the following steps.

Step 610, receiving a first data packet sent by a second network device, where the first data packet includes a first destination address, and the first destination address is a first SID of a third network device.

Specifically, the first network device is within SRv6 network. The first network device may be embodied as a transit node.

The first network device receives a first data message sent by the second network device. The first data message includes a first destination address, the first destination address being a first SID of the third network device. The second network device is a last hop device of the first network device. The third network device is an end node in the forwarding path.

Step 620, according to the first SID, obtaining a first forwarding table item for forwarding the first data packet and a network slice identifier of a network slice to which the first data packet belongs.

Specifically, according to the description of step 610, after the first network device acquires the first SID, the first forwarding table entry and the network slice identifier are acquired according to the first SID. The first forwarding table entry is a table entry for forwarding the first data packet, and the network slice identifier is an identifier of a network slice to which the first data packet belongs.

Further, the first SID includes a first prefix portion and a first non-prefix portion, the first non-prefix portion including a network slice identification.

In the embodiment of the application, after the first network device acquires the first SID, the first prefix portion is acquired from the first SID.

The first network device obtains a network slice identification from the first non-prefix portion based on the network slice identification tag and the network slice identification location information.

And 630, forwarding the first data message through the first forwarding table item and the service resource matched with the network slice identifier.

Specifically, according to the description of step 620, after the first network device obtains the first forwarding table entry and the network slice identifier, according to the service resource matched by the network slice identifier and the next hop address and the outbound interface information included in the first forwarding table entry, the first network device forwards the first data packet to the network device indicated by the next hop address through the outbound interface indicated by the outbound interface information according to the service resource.

Therefore, by applying the message processing method provided by the application, the first network device receives the first data message sent by the second network device, wherein the first data message comprises a first destination address, and the first destination address is the first SID of the third network device; according to the first SID, a first forwarding table item for forwarding the first data message and a network slice identifier of a network slice to which the first data message belongs are obtained; and forwarding the first data message by the first network equipment through the first forwarding table item and the service resource matched with the network slice identifier.

It should be noted that, in this embodiment, the process of receiving the route announcement message by the first network device is the same as the process of receiving the route announcement message by the first network device described in the foregoing embodiment, and will not be repeated here.

The following describes the message processing method provided in the embodiment of the present application in detail. Referring to fig. 7, fig. 7 is a schematic diagram of a networking diagram for implementing a message processing method in an IPv6 networking according to an embodiment of the present application.

In fig. 7, a router A, B, C forms an IPv6 network to provide forwarding services with network slicing functions for data packets that reach U2 by U1.

Within IPv6 networking, two network slices, network slice 1 and network slice 2, are partitioned. Network slice 1 occupies 70G bandwidth in the forwarding path of a-B-C; network slice 2 occupies 30G of bandwidth in the forwarding path of a-B-C.

Two data streams, namely data stream 1 and data stream 2, are transmitted between U1 and U2. The data stream 1 is an audio/video stream, the forwarding direction is U1- > U2, and forwarding is realized through the network slice 1; the data stream 2 is a voice e-mail stream, the forwarding direction is U1- > U2, and forwarding is realized through the network slice 2.

The IPv6 address of U1 is 100:1/64, wherein the 64 th-95 th bit stores the network slice identification; the IPv6 address of U2 is 200:1/64, wherein bits 64-95 store the network slice identification.

A. B, C are configured with a network slice identifier, and service resources matching the network slice identifier.

And A is as follows:

configuration within interface A-B: network slice identifier 1, the service resource matching network slice identifier 1 is link bandwidth 70G; network slice identifier 2, the service resource that matches network slice identifier 2 is link bandwidth 30G.

And B, in the process:

The interface B-C is internally configured, the network slice identifier 1, and the service resource matched with the network slice identifier 1 is link bandwidth 70G; network slice identifier 2, the service resource that matches network slice identifier 2 is link bandwidth 30G.

C, in:

the interface C-U2 is internally configured, the network slice identifier 1, and the service resource matched with the network slice identifier 1 is link bandwidth 70G; network slice identifier 2, the service resource that matches network slice identifier 2 is link bandwidth 30G.

To enable forwarding of data messages for different network slices, two transmit queues may be generated within a for interfaces a-B. Namely, queue 1 and queue 2. The transmission bandwidth of the queue 1 is 70G; the transmission bandwidth of queue 2 is 30G. When the interfaces A-B send data messages belonging to the network slice 1, the data messages are pressed into the queue 1 and sent through the queue 1; when the interfaces a-B send data messages belonging to the network slice 2, the data messages are pushed into the queue 2 and sent through the queue 2.

Similarly, two transmit queues may be generated for interfaces B-C in B, and the specific process is the same as generating two transmit queues in a, and will not be repeated here.

In the embodiment of the application, the link bandwidth is taken as a service resource for illustration. The service resources are not limited thereto in practical applications.

C, issuing a route notification message; A. and B, receiving the route notification message and generating a corresponding forwarding table item. The following description will take the example that the route advertisement message is issued by C through E-Intra-Area-Prefix-LSA.

C issues host routes of the network where the U2 is located in the IPv6 networking through E-Intra-Area-Prefix-LSA. The E-Inter-Area-Prefix-LSA comprises an Inter-Area-Prefix TLV, C stores 64 in a Prefix Length field included in the Inter-Area-Prefix TLV, stores a Prefix corresponding to 200:64 in the Address Prefix field, and sets an OSPF 3 Network-Slice-ID-Position Sub-TLV in a Sub-TLVs field.

Wherein, C stores 64 in the Start Position field included in the OSPF 3 Network-Slice-ID-Position sub-TLV and 32 in the ID Length field.

And B, after receiving the route notification message issued by the C, calculating a forwarding path, generating a routing table, and adding a forwarding table item corresponding to the routing table. The specific forwarding table items are:

200:64- > IP address with next hop C+out interface B-C+network slice identification mark+network slice identification position information (start position 64, length 32)

And B continuously forwarding the route notification message to A, after receiving the route notification message, calculating a forwarding path, generating a routing table, and adding a forwarding table item corresponding to the routing table. The specific forwarding table items are:

200:64- > IP address with next hop B+output interface A-B+network slice identification tag+network slice identification location information (start location 64, length 32)

A. B, C forward data flow procedure:

u1 sends a plurality of data messages to U2. U1 fills in the destination address of the audio and video data message as 200:1:0:1, and uses the forwarding service provided by the network slice 1; u1 fills out the destination address of the email data message as 200:2:0:1, using the forwarding service provided by network slice 2.

A receives a plurality of data messages sent by U1, searches a local forwarding table entry by adopting a longest matching principle according to a destination address of 200:1:0:1 or 200:2:0:1, and the searching result is as follows:

For an audio/video data message with the destination address of 200:1:0:1, forwarding the audio/video data message to B through an interface A-B, and simultaneously using a 70G bandwidth queue 1 corresponding to a network slice identifier 1; and forwarding the email data message with the destination address of 200:2:0:1 to B through an interface A-B, and simultaneously using a 30G bandwidth queue 2 corresponding to the network slice identifier 2.

B, receiving a plurality of data messages forwarded by the A, and inquiring a local forwarding table item by adopting a longest matching principle according to the destination address of 200:1:0:1 or 200:2:0:1, wherein the inquiring result is as follows:

For an audio/video data message with the destination address of 200:1:0:1, forwarding the audio/video data message to C through an interface B-C, and simultaneously using a 70G bandwidth queue 1 corresponding to the network slice identifier 1; and forwarding the email data message with the destination address of 200:2:0:1 to C through an interface B-C, and simultaneously using a 30G bandwidth queue 2 corresponding to the network slice identifier 2.

C, receiving a plurality of data messages forwarded by the B, and inquiring a local forwarding table item by adopting a longest matching principle according to the destination address of 200:1:0:1 or 200:2:0:1, wherein the inquiring result is as follows:

200:64- > IP address with next hop U2+output interface C-U2+network slice identification mark+network slice identification position information (starting position 64, length 32)

For an audio/video data message with the destination address of 200:1:0:1, forwarding the audio/video data message to U2 through an interface C-U2, and simultaneously using a 70G bandwidth queue 1 corresponding to a network slice identifier 1; and forwarding the email data message with the destination address of 200:2:0:1 to U2 through an interface C-U2, and simultaneously using a 30G bandwidth queue 2 corresponding to the network slice identifier 2.

And U2 receives the plurality of data messages forwarded by C. U2 checks that the destination address of the multiple data messages is 200:1:0:1 or 200:2:0:1, and accords with the prefix part (200:1/64, wherein the 64 th bit to the 95 th bit are network slice identifiers) of the IP addresses of the multiple data messages.

After the U2 acquires the network slice identifiers from the plurality of data messages, the bit corresponding to the network slice identifiers is updated to 0, and an IP address is obtained. And the U2 compares the IP address with the IP address of the U2, and if the IP address is the same, the U2 processes the audio and video data message and the electronic mail data message from the U1.

The following describes the message processing method provided in the embodiment of the present application in detail. Referring to fig. 8, fig. 8 is a networking schematic diagram of implementing a message processing method in SRv networking according to an embodiment of the present application.

In fig. 8, the router A, B, C forms SRv a network to provide forwarding service with network slicing function for the data packets from U1 to U2.

Within the SRv network, two network slices, network slice 1 and network slice 2, are partitioned. Network slice 1 occupies 70G bandwidth in the forwarding path of a-B-C; network slice 2 occupies 30G of bandwidth in the forwarding path of a-B-C.

SIDs are configured in C.

The local SID configured in C is 303:1. Wherein bits 0-63 are the Locator field, bits 64-95 store the network slice identification, bits 96-127 are the Function field, and execute the End instruction with USD (Ultimate Segment Decapsulation, penultimate decapsulation) additional behavior.

Router C adds a forwarding table entry corresponding to the Locator:

303:64- > local address + network slice identification tag + network slice identification location information (start location 64, length 32)

Router C adds a forwarding entry corresponding to the local SID:

303:1/128- > local Address+end instruction with USD

And A is as follows:

And B, in the process:

C, in:

C, issuing a route notification message; A. and B, receiving the route notification message and generating a corresponding forwarding table item. The following description will take the example that the C issues the route advertisement message through SRv Locator LSA.

And C issues a Locator route corresponding to 303:1 in SRv6 networking through SRv Locator LSA. SRv6Locator LSA includes SRv6Locator TLV, C stores 64 in a Locator Length field included in SRv6Locator TLV, 303 in the Locator field, and OSPF 3Network-Slice-ID-Position Sub-TLV is set in the Sub-TLVs field.

Wherein, C stores 64 in the Start Position field included in the OSPF 3Network-Slice-ID-Position sub-TLV and 32 in the ID Length field.

303:64- > IP address with next hop C+out interface B-C+network slice identification mark+network slice identification position information (start position 64, length 32)

303:64- > IP address with next hop B+output interface A-B+network slice identification mark+network slice identification position information (start position 64, length 32)

A. B, C forward data flow procedure:

The first data message sent by the U1 to the U2 is when entering SRv to the network. And A, identifying the message type of the first data message according to the message characteristics (such as quintuple information, source address, destination address, protocol type, source port number and destination port number) of the first data message, namely the first data message is an audio/video data message or an electronic mail data message. And according to the message type, A determines the network slice to which the first data message belongs and acquires the network slice identification of the network slice.

A encapsulates the IPv6 extension header and the SRH header in the outer layer of the first data message, wherein a segment list field of the SRH header stores the SID of C (in the embodiment of the application, C is an end node and B is a transit node), 64-95 bits in the SID of C store network slice identification, and the rest of fields are filled in according to SRv protocol standard.

For example, when the first data message is an audio/video data message, the SID of C stored in the segment list is 303:1:0:1, and when the first data message is an electronic mail data message, the SID of C stored in the segment list is 303:2:0:1.

The IPv6 extension header includes a destination address filled in according to the SIDs stored in the segment list, namely 303:1:0:1 or 303:2:0:1.

A queries the forwarding table item according to the destination address 303:1:0:1 or 303:2:0:1 by adopting the longest matching principle, and the query result is as follows:

For an audio/video data message with the destination address of 303:1:0:1, forwarding the audio/video data message to B through an interface A-B, and simultaneously using a 70G bandwidth queue 1 corresponding to a network slice identifier 1; and forwarding the email data message with the destination address of 303:2:0:1 to B through an interface A-B, and simultaneously using a 30G bandwidth queue 2 corresponding to the network slice identifier 2.

And B, receiving the packaged first data message forwarded by the A, and querying a local forwarding table item by adopting a longest matching principle according to the destination address 303:1:0:1 or 303:2:0:1, wherein the query result is as follows:

For an audio/video data message with the destination address of 303:1:0:1, forwarding the audio/video data message to C through an interface B-C, and simultaneously using a 70G bandwidth queue 1 corresponding to the network slice identifier 1; and forwarding the email data message with the destination address of 303:2:0:1 to C through an interface B-C, and simultaneously using a 30G bandwidth queue 2 corresponding to the network slice identifier 2.

C, receiving the packaged first data message forwarded by the B, and inquiring a local forwarding table item by adopting a longest matching principle according to the destination address 303:1:0:1 or 303:2:0:1, wherein the inquiring result is as follows:

And C, setting all corresponding positions of the network slice identifiers in the destination address to 0, namely 303:1, inquiring a forwarding table item by adopting a longest matching principle, wherein the inquiring result is as follows:

303:1/128- > local Address+end instruction with USD

And C, performing decapsulation operation on the encapsulated first data message, and stripping the IPv6 extension header and the SRH header of the outer layer to obtain the first data message. And C, forwarding the first data message to U2 according to the End instruction with the USD.

Based on the same inventive concept, the embodiment of the application also provides a message processing device corresponding to the message processing method. Referring to fig. 9, fig. 9 is a block diagram of a message processing apparatus according to an embodiment of the present application. The apparatus is applied to a first network device, the first network device being within an IPv6 network, the apparatus comprising:

a receiving unit 910, configured to receive a first data packet;

an obtaining unit 920, configured to obtain, according to the first data packet, a first forwarding table for forwarding the first data packet and a network slice identifier of a network slice to which the first data packet belongs;

And a processing unit 930, configured to forward the first data packet through the first forwarding table entry and a service resource matched with the network slice identifier.

Optionally, when the first network device is a source node, the receiving unit 910 is further configured to receive the first data packet sent by the user terminal;

when the first network device is a transit node or an end node, the receiving unit 910 is further configured to receive the first data packet sent by a second network device, where the second network device is a last hop device of the first network device.

Optionally, the first data packet includes a first destination address, and the first destination address includes a first prefix portion;

the acquiring unit 920 specifically includes: a searching subunit (not shown in the figure) configured to search, from the local forwarding table, for a first forwarding table entry matching the first prefix portion, where the first forwarding table entry includes a network slice identifier tag and network slice identifier location information;

an obtaining subunit (not shown in the figure) is configured to obtain, according to the network slice identifier flag and network slice identifier location information, the network slice identifier from a first non-prefix portion included in the first destination address.

Optionally, the first data packet includes a packet feature;

when the first network device is a source node, the obtaining unit 920 further includes: an identifying subunit (not shown in the figure) configured to identify a message type of the first data message according to the message characteristics;

a determining subunit (not shown in the figure) configured to determine, according to the packet type, a network slice to which the first data packet belongs, and obtain a network slice identifier of the network slice from a local configuration;

a processing subunit (not shown in the figure) configured to configure the network slice identifier in a first non-prefix portion included in the first destination address according to the network slice identifier location information, so as to obtain a second non-prefix portion;

a generating subunit (not shown in the figure) is configured to generate a second destination address, where the second destination address includes a second prefix portion and the second non-prefix portion, where the second prefix portion is the same as the first prefix portion, and the second destination address is used for obtaining the network slice identifier from the second non-prefix portion after a next hop device of the first network device receives a data packet including the second destination address.

Optionally, the first data packet includes feature information;

when the first network device is a source node, the obtaining unit 920 specifically includes: an identifying subunit (not shown in the figure) configured to identify a message type of the first data message according to the message characteristics;

a determining subunit (not shown in the figure) is configured to determine, according to the packet type, a network slice to which the first data packet belongs, and obtain a network slice identifier of the network slice from a local configuration.

the acquisition unit 920 further includes: an obtaining subunit (not shown in the figure) configured to obtain network slice identifier location information from the local configuration;

a generating subunit (not shown in the figure) configured to generate a second destination address, where the second destination address includes a second prefix portion and the second non-prefix portion, where the second prefix portion is the same as the first prefix portion, and the second destination address is used for obtaining the network slice identifier from the second non-prefix portion after a next hop device of the first network device receives a data packet including the second destination address;

The obtaining unit 920 is specifically configured to search, from the local forwarding table, a second forwarding table entry that matches the second prefix portion according to the second prefix portion, where the second forwarding table entry includes a network slice identifier tag and network slice identifier location information.

Optionally, when the first network device is an end node, the obtaining subunit (not shown in the figure) is further configured to update, according to the network slice identifier flag, a bit occupied by the network slice identifier in the first non-prefix portion to be 0, to obtain an address of the user terminal.

Optionally, the apparatus further comprises: a sending unit (not shown in the figure) configured to send a first routing advertisement packet to a third network device, where the first routing advertisement packet includes a user terminal address and network slice identifier location information, so that the third network device generates a third forwarding table item, where the third forwarding table item includes a prefix part of the user terminal address, a next hop address, outgoing interface information, a network slice identifier tag, and network slice identifier location information.

Optionally, the receiving unit 910 is further configured to receive a second route advertisement packet sent by the fourth network device, where the second route advertisement packet includes a user terminal address and network slice identifier location information;

The apparatus further comprises: a generating unit (not shown in the figure) is configured to generate a fourth forwarding table entry, where the fourth forwarding table entry includes a prefix portion of the address of the user terminal, a next hop address, outgoing interface information, a network slice identifier tag, and network slice identifier location information.

Optionally, the receiving unit 910 is further configured to receive a first configuration instruction issued by the controller, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the apparatus further comprises: a storage unit (not shown in the figure) for storing the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 910 is further configured to receive a second configuration instruction sent by the controller, where the second configuration instruction includes a configuration rule of the network slice identifier;

the storage unit (not shown in the figure) is further configured to store a configuration rule of the network slice identifier;

or,

the receiving unit 910 is further configured to receive a first configuration instruction input by a user, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 910 is further configured to receive a second configuration instruction input by the user, where the second configuration instruction includes a configuration rule of the network slice identifier;

the configuration rule of the network slice identifier comprises the network slice identifier position information, and the network slice identifier position information comprises the position of a non-prefix part included in a destination address of the network slice identifier and the length of the network slice identifier.

Based on the same inventive concept, the embodiment of the application also provides a message processing device corresponding to the message processing method. Referring to fig. 10, fig. 10 is a block diagram of a message processing apparatus according to an embodiment of the present application. The apparatus is applied to a first network device, the first network device is in SRv networking, the first network device is a source node, and the apparatus includes:

a receiving unit 1010, configured to receive a first data packet sent by a first user terminal, where the first data packet includes a packet feature;

An obtaining unit 1020, configured to determine, according to the message characteristics, a network slice to which the first data message belongs, and obtain a network slice identifier of the network slice;

a generating unit 1030, configured to generate a second data packet, where the second data packet includes a first destination address, where the first destination address is a first SID, and the first SID includes a first prefix portion and a first non-prefix portion, and the first non-prefix portion includes the network slice identifier;

the obtaining unit 1020 is further configured to obtain, according to the first prefix portion, a first forwarding table entry for forwarding the second data packet;

and the processing unit 1040 is configured to forward the second data packet through the first forwarding table entry and a service resource that matches the network slice identifier.

Optionally, the first data packet further includes a second destination address;

the second data message further includes a segment list including at least one SID, each SID including the network slice identity, each SID being for indicating a SID of each end node in a forwarding path for the first network device to the second network device, the at least one SID including the first SID;

Wherein the second network device is an end node, and the second user terminal indicated by the second destination address accesses the end node.

Optionally, the generating unit 1030 is specifically configured to obtain a second SID of each end node in the forwarding path, where each second SID includes a second prefix portion and a second non-prefix portion;

acquiring a configuration rule of the network slice identifier from local configuration;

configuring the network slice identifier in each second non-prefix portion according to the configuration rule of the network slice identifier;

generating a third SID for each end node, each third SID comprising a third prefix portion and a third non-prefix portion, said third prefix portion being identical to said second prefix portion, said third non-prefix portion comprising said network slice identity;

generating the segment list according to the position of each end node in the forwarding path, wherein the segment list comprises the third SID;

acquiring the first SID from the third SID, wherein the first SID is the SID of a next hop end node of the first network equipment;

configuring the first SID at the first destination address and configuring the first destination address at an IPv6 extension header;

Generating the segment list and configuring the segment list in an SRH head;

and encapsulating the IPv6 extension header and the SRH header on the outer layer of the first data message to obtain a second data message.

Optionally, the receiving unit 1010 is further configured to receive a first routing advertisement packet sent by a third network device, where the first routing advertisement packet includes an SID of an end node and network slice identifier location information;

the generating unit 1030 is further configured to generate a second forwarding table entry, where the second forwarding table entry includes a prefix portion of the SID of the end node, a next hop address, egress interface information, a network slice identifier tag, and network slice identifier location information.

Optionally, the receiving unit 1010 is further configured to receive a first configuration instruction issued by the controller, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 1010 is further configured to receive a second configuration instruction sent by the controller, where the second configuration instruction includes a configuration rule of the network slice identifier;

or,

the receiving unit 1010 is further configured to receive a first configuration instruction input by a user, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 1010 is further configured to receive a second configuration instruction input by the user, where the second configuration instruction includes a configuration rule of the network slice identifier;

the configuration rule of the network slice identifier comprises the network slice identifier position information, and the network slice identifier position information comprises the position of the network slice identifier in a non-prefix part included by the SID and the length of the network slice identifier.

Based on the same inventive concept, the embodiment of the application also provides a message processing device corresponding to the message processing method. Referring to fig. 11, fig. 11 is a block diagram of a message processing apparatus according to an embodiment of the present application. The apparatus is applied to a first network device, the first network device being within a SRv network, the first network device being an end node, the apparatus comprising:

A receiving unit 1110, configured to receive a first data packet sent by a second network device, where the first data packet includes a first destination address, and the first destination address is a first SID of the first network device;

an obtaining unit 1120, configured to obtain a network slice identifier and generate a second SID according to the first SID;

the obtaining unit 1120 is further configured to obtain, according to the second SID, a first forwarding table entry that matches the second SID;

and a processing unit 1130, configured to forward the first data packet through the first forwarding table entry and a service resource that matches the network slice identifier.

Optionally, the first SID includes a first prefix portion and a first non-prefix portion;

the obtaining unit 1120 is specifically configured to obtain, according to the first prefix portion, a second forwarding table entry for forwarding the first data packet, where the second forwarding table entry includes a network slice identifier tag and network slice identifier location information;

acquiring the network slice identifier from the first non-prefix portion according to the network slice identifier tag and network slice identifier position information;

updating the bit occupied by the network slice identifier in the first non-prefix part to 0 to obtain the second non-prefix part;

A second prefix portion and a second non-prefix portion are combined into the second SID, the second prefix portion being identical to the first prefix portion.

Optionally, the apparatus further comprises: a generating unit (not shown in the figure) configured to generate, according to the second SID, the first forwarding table entry, where the first forwarding table entry includes the second SID, an address of the first network device, and a packet processing action;

and generating the second forwarding table item according to the first prefix part, wherein the second forwarding table item comprises the first prefix part, the address of the first network equipment, the network slice identification mark and network slice identification position information.

Optionally, the apparatus further comprises: a sending unit (not shown in the figure) configured to send a first routing advertisement packet to a third network device, where the first routing advertisement packet includes a SID of the first network device and network slice identifier location information, so that the third network device generates a third forwarding table entry, where the third forwarding table entry includes the first prefix portion, a next hop address, output interface information, a network slice identifier tag, and network slice identifier location information.

Optionally, the receiving unit 1110 is further configured to receive a first configuration instruction issued by the controller, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 1110 is further configured to receive a second configuration instruction sent by the controller, where the second configuration instruction includes a configuration rule of the network slice identifier;

or,

the receiving unit 1110 is further configured to receive a first configuration instruction input by a user, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 1110 is further configured to receive a second configuration instruction input by the user, where the second configuration instruction includes a configuration rule of the network slice identifier;

wherein the configuration rule of the network slice identifier comprises the network slice identifier position information, and the network slice identifier position information comprises the position of the network slice identifier in a non-prefix part included by the SID and the length of the network slice identifier

Based on the same inventive concept, the embodiment of the application also provides a message processing device corresponding to the message processing method. Referring to fig. 12, fig. 12 is a block diagram of a message processing apparatus according to an embodiment of the present application. The apparatus is applied to a first network device, the first network device is in SRv network, the first network device is a transit node, and the apparatus includes:

a receiving unit 1210, configured to receive a first data packet sent by a second network device, where the first data packet includes a first destination address, and the first destination address is a first SID of a third network device;

an obtaining unit 1220, configured to obtain, according to the first SID, a first forwarding table for forwarding the first data packet and a network slice identifier of a network slice to which the first data packet belongs;

And a processing unit 1230, configured to forward the first data packet through the first forwarding table entry and a service resource matched with the network slice identifier.

the obtaining unit 1220 is specifically configured to search, from a local forwarding table, for a first forwarding table entry that matches the first prefix portion according to the first prefix portion, where the first forwarding table entry includes a network slice identifier tag and network slice identifier location information;

and acquiring the network slice identifier from the first non-prefix part according to the network slice identifier mark and the network slice identifier position information.

Optionally, the receiving unit 1210 is further configured to receive a first routing advertisement packet sent by the third network device, where the first routing advertisement packet includes SID of the third network device and network slice identifier location information;

the apparatus further comprises: a generating unit (not shown in the figure) is configured to generate a second forwarding table entry, where the second forwarding table entry includes a prefix portion of the SID of the third network device, a next hop address, egress interface information, a network slice identifier tag, and network slice identifier location information.

Optionally, the receiving unit 1210 is further configured to receive a first configuration instruction sent by the controller, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 1210 is further configured to receive a second configuration instruction sent by the controller, where the second configuration instruction includes a configuration rule of the network slice identifier;

or,

the receiving unit 1210 is further configured to receive a first configuration instruction input by a user, where the first configuration instruction includes the network slice identifier and a service resource matched with the network slice identifier;

the receiving unit 1210 is further configured to receive a second configuration instruction input by the user, where the second configuration instruction includes a configuration rule of the network slice identifier;

Based on the same inventive concept, the embodiments of the present application also provide a network device, as shown in fig. 13, including a processor 1310, a transceiver 1320, and a machine-readable storage medium 1330, where the machine-readable storage medium 1330 stores machine executable instructions capable of being executed by the processor 1310, the processor 1310 is caused to perform the packet processing method provided in the embodiments of the present application. The message processing apparatus shown in fig. 9, 10, 11, and 12 may be implemented by using a hardware structure of a network device as shown in fig. 13.

The computer readable storage medium 1330 may include a random access Memory (in the english: random Access Memory, abbreviated as RAM) or a nonvolatile Memory (in the english: non-volatile Memory, abbreviated as NVM), such as at least one magnetic disk Memory. Optionally, the computer readable storage medium 1330 may also be at least one storage device located remotely from the processor 1310.

The processor 1310 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (English: digital Signal Processor; DSP; for short), an application specific integrated circuit (English: application Specific Integrated Circuit; ASIC; for short), a Field programmable gate array (English: field-Programmable Gate Array; FPGA; for short), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

In this embodiment, processor 1310, by reading machine-executable instructions stored in machine-readable storage medium 1330, is caused by the machine-executable instructions to implement processor 1310 itself and invoke transceiver 1320 to perform the message processing method described in the previous embodiments of the present application.

Additionally, embodiments of the present application provide a machine-readable storage medium 1330, the machine-readable storage medium 1330 storing machine-executable instructions that, when invoked and executed by the processor 1310, cause the processor 1310 itself and the invoking transceiver 1320 to perform the message processing methods described in the embodiments of the present application described above.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

For the message processing apparatus and the machine-readable storage medium embodiments, since the method content related thereto is substantially similar to the method embodiments described above, the description is relatively simple, and the relevant points are referred to in the description of the method embodiments.

The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.

Claims

1. A method for processing a message, the method being applied to a first network device, the first network device being within an IPv6 network, the method comprising:

receiving a first data message;

forwarding the first data message through the first forwarding table item and a service resource matched with the network slice identifier;

before the first data message is received, the method further includes:

receiving a second route notification message sent by fourth network equipment, wherein the second route notification message comprises a user terminal address and network slice identification position information;

generating a fourth forwarding table item, wherein the fourth forwarding table item comprises a prefix part of the user terminal address, a next hop address, outgoing interface information, a network slice identification mark and network slice identification position information;

the second route notification message comprises a starting position field and an ID length field; storing a start position of a network slice identifier in a destination address included in the first data message in the start position field; the ID length field stores the length of the network slice identifier;

The first data message includes a first destination address, the first destination address including a first prefix portion;

the step of obtaining, according to the first data packet, a first forwarding table for forwarding the first data packet and a network slice identifier of a network slice to which the first data packet belongs, specifically includes:

according to the first prefix part, searching a first forwarding table item matched with the first prefix part from a local forwarding table, wherein the first forwarding table item comprises a network slice identification mark and network slice identification position information;

acquiring the network slice identifier from a first non-prefix part included in the first destination address according to the network slice identifier mark and the network slice identifier position information;

when the first network device is an end node, after the obtaining the network slice identifier from the first non-prefix portion included in the first destination address, the method further includes:

and according to the network slice identification mark, updating the bit occupied by the network slice identification in the first non-prefix part to be 0 to obtain the address of the user terminal.

2. The method of claim 1, wherein when the first network device is a source node, the receiving the first data packet specifically includes:

Receiving the first data message sent by a user terminal;

when the first network device is a transit node or an end node, the receiving the first data packet specifically includes:

and receiving the first data message sent by second network equipment, wherein the second network equipment is last-hop equipment of the first network equipment.

3. The method of claim 1, wherein the first data message comprises a message characteristic;

after the searching the first forwarding table entry that is partially matched with the first prefix when the first network device is the source node, the method further includes:

identifying the message type of the first data message according to the message characteristics;

according to the message type, determining a network slice to which the first data message belongs, and acquiring a network slice identifier of the network slice from a local configuration;

according to the network slice identifier position information, configuring the network slice identifier on a first non-prefix part included in the first destination address to obtain a second non-prefix part;

generating a second destination address, where the second destination address includes a second prefix portion and the second non-prefix portion, where the second prefix portion is the same as the first prefix portion, and the second destination address is used in the next hop device of the first network device to acquire the network slice identifier from the second non-prefix portion after receiving a data packet including the second destination address.

4. The method of claim 1, wherein the first data message includes characteristic information;

when the first network device is a source node, the acquiring, according to the first data packet, a network slice identifier of a network slice to which the first data packet belongs specifically includes:

and determining the network slice to which the first data message belongs according to the message type, and acquiring the network slice identification of the network slice from the local configuration.

5. The method of claim 4, wherein the first data message comprises a first destination address, the first destination address comprising a first prefix portion;

after the network slice identification of the network slice is obtained from the local configuration, the method further includes:

acquiring network slice identification position information from the local configuration;

generating a second destination address, where the second destination address includes a second prefix portion and the second non-prefix portion, where the second prefix portion is the same as the first prefix portion, and the second destination address is used for acquiring the network slice identifier from the second non-prefix portion after a next hop device of the first network device receives a data packet including the second destination address;

The step of obtaining a first forwarding table item for forwarding the first data packet according to the first data packet specifically includes:

and according to the second prefix part, searching a second forwarding table item matched with the second prefix part from a local forwarding table, wherein the second forwarding table item comprises a network slice identification mark and network slice identification position information.

6. The method of claim 1, wherein prior to receiving the first data message, the method further comprises:

and sending a first routing notification message to third network equipment, wherein the first routing notification message comprises a user terminal address and network slice identification position information, so that the third network equipment generates a third forwarding table item, and the third forwarding table item comprises a prefix part of the user terminal address, a next hop address, outgoing interface information, a network slice identification mark and the network slice identification position information.

7. The method of claim 1, wherein prior to receiving the first data message, the method further comprises:

receiving a first configuration instruction issued by a controller, wherein the first configuration instruction comprises the network slice identifier and a service resource matched with the network slice identifier;

Storing the network slice identifier and the service resource matched with the network slice identifier;

receiving a second configuration instruction issued by the controller, wherein the second configuration instruction comprises a configuration rule of the network slice identifier;

storing the configuration rule of the network slice identifier;

or,

receiving a first configuration instruction input by a user, wherein the first configuration instruction comprises the network slice identifier and a service resource matched with the network slice identifier;

receiving a second configuration instruction input by the user, wherein the second configuration instruction comprises a configuration rule of the network slice identifier;

storing the configuration rule of the network slice identifier;

8. The method for processing the message is characterized in that the method is applied to first network equipment, the first network equipment is positioned in SRv network, the first network equipment is a source node, and the method comprises the following steps:

forwarding the second data message through the first forwarding table item and the service resource matched with the network slice identifier;

before the first data message is received, the method further includes:

receiving a first route notification message sent by third network equipment, wherein the first route notification message comprises SID of an end node and network slice identification position information;

generating a second forwarding table entry, wherein the second forwarding table entry comprises a prefix part of the SID of the end node, a next hop address, outgoing interface information, a network slice identification mark and network slice identification position information;

Wherein, the first route notification message includes a start position field and an ID length field; storing a start position of a network slice identifier in a destination address included in the first data message in the start position field; and the ID length field stores the length of the network slice identifier.

9. The method of claim 8, wherein the first data message further comprises a second destination address;

10. The method according to claim 9, wherein the generating the second data message specifically includes:

acquiring a second SID of each end node in the forwarding path, wherein each second SID comprises a second prefix part and a second non-prefix part;

generating the segment list and configuring the segment list in an SRH head;

11. The method of claim 8, wherein prior to receiving the first data message, the method further comprises:

storing the configuration rule of the network slice identifier;

or,

storing the configuration rule of the network slice identifier;

12. A method for processing a message, the method being applied to a first network device, the first network device being within a SRv group network, the first network device being an end node, the method comprising:

receiving a first data message sent by second network equipment, wherein the first data message comprises a first destination address, the first destination address is a first SID, and the first SID comprises a network slice identifier;

acquiring the network slice identifier according to the first SID and generating a second SID, wherein the second SID is the SID of the first network equipment;

before the first data message sent by the second network device is received, the method further includes:

transmitting a first routing notification message to a third network device, wherein the first routing notification message comprises the SID of the first network device and network slice identification position information, so that the third network device generates a third forwarding table item, and the third forwarding table item comprises the first prefix part, a next hop address, outgoing interface information, a network slice identification mark and the network slice identification position information;

Wherein, the first route notification message includes a start position field and an ID length field; storing a start position of a network slice identifier in a destination address included in the first data message in the start position field; the ID length field stores the length of the network slice identifier;

the first SID includes a first prefix portion and a first non-prefix portion;

the step of obtaining the network slice identifier and generating a second SID according to the first SID specifically includes:

acquiring a second forwarding table item for forwarding the first data message according to the first prefix part, wherein the second forwarding table item comprises a network slice identification mark and network slice identification position information;

updating the bit occupied by the network slice identifier in the first non-prefix part to 0 to obtain a second non-prefix part;

13. The method of claim 12, wherein prior to receiving the first data message sent by the second network device, the method further comprises:

generating the first forwarding table item according to the second SID, wherein the first forwarding table item comprises the second SID, the address of the first network equipment and a message processing action;

14. The method of claim 12, wherein prior to receiving the first data message sent by the second network device, the method further comprises:

Storing the configuration rule of the network slice identifier;

or,

storing the configuration rule of the network slice identifier;

15. A method for processing a message, the method being applied to a first network device, the first network device being in a SRv group network, the first network device being a transit node, the method comprising:

receiving a first route notification message sent by the third network device, wherein the first route notification message comprises the SID of the third network device and network slice identification position information;

generating a second forwarding table entry, wherein the second forwarding table entry comprises a prefix part of the SID of the third network equipment, a next hop address, outgoing interface information, a network slice identification mark and network slice identification position information;

16. The method of claim 15, wherein the first SID comprises a first prefix portion and a first non-prefix portion;

the step of obtaining, according to the first SID, a first forwarding table item for forwarding the first data packet and a network slice identifier of a network slice to which the first data packet belongs specifically includes:

17. The method of claim 15, wherein prior to receiving the first data message sent by the second network device, the method further comprises:

storing the configuration rule of the network slice identifier;

or,

storing the configuration rule of the network slice identifier;

18. A message processing apparatus, the apparatus being applied to a first network device, the first network device being within an IPv6 network, the apparatus comprising:

the receiving unit is used for receiving the first data message;

the processing unit is used for forwarding the first data message through the first forwarding table item and the service resource matched with the network slice identifier;

the receiving unit is further configured to receive a second route notification packet sent by the fourth network device, where the second route notification packet includes a user terminal address and network slice identifier location information;

the apparatus further comprises: generating a fourth forwarding table item, wherein the fourth forwarding table item comprises a prefix part of the user terminal address, a next hop address, outgoing interface information, a network slice identification mark and network slice identification position information;

the acquisition unit specifically includes: a searching subunit, configured to search, from a local forwarding table according to the first prefix portion, a first forwarding table entry that is matched with the first prefix portion, where the first forwarding table entry includes a network slice identifier tag and network slice identifier location information;

an obtaining subunit, configured to obtain, according to the network slice identifier tag and network slice identifier location information, the network slice identifier from a first non-prefix portion included in the first destination address;

when the first network device is an end node, the obtaining subunit is further configured to update, according to the network slice identifier tag, a bit occupied by the network slice identifier in the first non-prefix portion to be 0, to obtain an address of the user terminal.

19. A message processing apparatus, wherein the apparatus is applied to a first network device, the first network device is in SRv network, the first network device is a source node, and the apparatus includes:

the processing unit is used for forwarding the second data message through the first forwarding table item and the service resource matched with the network slice identifier;

the receiving unit is further configured to receive a first route notification packet sent by a third network device, where the first route notification packet includes an SID of an end node and network slice identifier location information;

the generating unit is further configured to generate a second forwarding table entry, where the second forwarding table entry includes a prefix portion of the SID of the end node, a next hop address, outgoing interface information, a network slice identifier tag, and network slice identifier location information;

20. A message processing apparatus, wherein the apparatus is applied to a first network device, the first network device is in SRv group network, the first network device is an end node, and the apparatus comprises:

The apparatus further comprises:

a sending unit, configured to send a first routing advertisement packet to a third network device, where the first routing advertisement packet includes an SID of the first network device and network slice identifier location information, so that the third network device generates a third forwarding table item, where the third forwarding table item includes the first prefix portion, a next hop address, egress interface information, a network slice identifier tag, and network slice identifier location information;

the first SID includes a first prefix portion and a first non-prefix portion;

the obtaining unit is specifically configured to obtain, according to the first prefix portion, a second forwarding table entry for forwarding the first data packet, where the second forwarding table entry includes a network slice identifier tag and network slice identifier location information;

21. A message processing apparatus, wherein the apparatus is applied to a first network device, the first network device is in SRv network, the first network device is a transit node, and the apparatus includes:

the receiving unit is further configured to receive a first route notification packet sent by the third network device, where the first route notification packet includes SID of the third network device and network slice identifier location information;

The apparatus further comprises: a generating unit, configured to generate a second forwarding table entry, where the second forwarding table entry includes a prefix portion of a SID of the third network device, a next hop address, outgoing interface information, a network slice identifier tag, and network slice identifier location information;