WO2022237291A1 - Message transmission method and apparatus, related device, and storage medium - Google Patents

Abstract

The present application discloses a message transmission method and apparatus, a network node, and a storage medium. The method comprises: a first network node determining a slice identifier of a first message; generating a second message on the basis of the slice identifier and the first message, a source address field in a message header of the second message carrying the slice identifier; and sending the second message.

Description

Message transmission method, device, related equipment and storage medium

Cross References to Related Applications

This application is based on a Chinese patent application with application number 202110513378.1 and a filing date of May 11, 2021, and claims the priority of this Chinese patent application. The entire content of this Chinese patent application is hereby incorporated by reference into this application.

technical field

The present application relates to the Internet Protocol (IP) network field, and in particular to a message transmission method, device, related equipment and storage medium.

Background technique

Network slicing is one of the key technologies of the fifth generation mobile communication technology (5G). Network slicing refers to the implementation of diversion management similar to traffic management for network data. Its essence is to divide the existing physical network into multiple virtual networks of different types at the logical level. According to the service requirements of different users, such as The time delay, bandwidth, reliability and other indicators are used to classify, so as to deal with complex and changeable application scenarios. Through network slicing, mobile network operators can divide users into different types, each user has different service requests, and manage the slice types and services each user is eligible to use according to the service level agreement (SLA).

The 5G bearer network is a part of the 5G end-to-end service path, and bearer network slicing refers to: virtualizing network topology resources (such as links, nodes, ports, and network element internal resources) Separate multiple logical virtual transport subnets. The virtual transmission subnet has an independent management plane, control plane, and forwarding plane, and independently supports various services, so as to realize the isolation between different services.

From the perspective of IP forwarding, data transmission mainly includes two aspects: the control plane and the forwarding plane. Therefore, bearer network slicing technology is mainly distributed on the control plane and the forwarding plane.

For the bearer network slicing technology, slice IDs need to be introduced on the forwarding plane. How to introduce slice IDs is an urgent problem to be solved.

Contents of the invention

To solve related technical problems, embodiments of the present application provide a message transmission method, device, related equipment, and storage medium.

The technical scheme of the embodiment of the application is realized in this way:

An embodiment of the present application provides a message transmission method applied to a first network node, including:

Determine the slice identifier of the first packet;

Generate a second message based on the slice identifier and the first message; the source address field in the header of the second message carries the slice identifier;

sending the second message.

In the above solution, the packet header of the second packet further carries first information, and the first information indicates that the source address field of the second packet header carries the slice identifier.

In the above solution, the traffic class (Traffic Class) field or the flow label (Flow Label) field in the packet header of the second packet carries the first information.

In the above solution, the function field in the segment identifier (SID) of the source address field in the packet header of the second packet carries the slice identifier.

In the above solution, the determination of the slice identifier of the first message includes:

determining the service characteristics of the first packet;

Searching for a slice identifier corresponding to the service feature of the first packet in the first table; the first table is at least provided with a correspondence between a service feature and a slice identifier.

In the above scheme, the method also includes:

Receiving second information sent by a software-defined network (SDN) controller or a network management system; the second information at least includes service characteristics and corresponding slice identifiers;

Using the second information, the first table is formed.

In the above solution, the sending of the second message includes:

determining the outgoing interface of the second packet;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the second table; the second table is at least provided with a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

sending the second packet by using the found physical resource.

In the above solution, the determination of the outgoing interface of the second message includes:

Determine the outbound interface of the second packet by searching the routing and forwarding table.

In the above scheme, the method also includes:

receiving third information sent by the SDN or the network management system; the third information at least includes the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

The second table is formed using the third information.

The embodiment of the present application also provides a message transmission method applied to the second network node, including:

receiving a second message; the source address field in the message header of the second message carries a slice identifier;

The second packet is forwarded by using the slice identifier.

In the above solution, the packet header of the second packet further carries first information, and the first information indicates that the source address field of the second packet header carries the slice identifier.

In the above solution, the Traffic Class field or the Flow Label field in the packet header of the second packet carries the first information.

In the above solution, the function field in the SID of the source address field in the packet header of the second packet carries the slice identifier.

In the above solution, the forwarding of the second message by using the slice identifier includes:

Determine the outbound interface of the second packet by searching the routing and forwarding table;

Searching the physical resource corresponding to the outgoing interface and the slice identifier in the third table; the third table is provided with at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

Forwarding the second packet by using the found physical resource.

In the above scheme, the method also includes:

Receive the fourth information sent by the SDN or the network management system; the fourth information includes at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

The third table is formed using the fourth information.

The embodiment of the present application also provides a message transmission device, including:

The first determining unit is configured to determine the slice identifier of the first packet;

A generating unit configured to generate a second message based on the slice identifier and the first message; the source address field in the header of the second message carries the slice identifier;

A transmission unit configured to send the second message.

The embodiment of the present application also provides a message transmission device, including:

The receiving unit is configured to receive the second message; the source address field in the message header of the second message carries a slice identifier;

The forwarding unit is configured to use the slice identifier to forward the second packet.

The embodiment of the present application also provides a first network node, including:

The first processor is configured to determine the slice identifier of the first message; and generate a second message based on the slice identifier and the first message; the source address field in the message header of the second message carries the the above slice identification;

The first communication interface is configured to send the second message.

The embodiment of the present application also provides a second network node, including: a second communication interface and a second processor; wherein,

The second communication interface is configured to receive a second message; the source address field in the message header of the second message carries a slice identifier;

The second processor is configured to use the slice identifier to forward the second message through the second communication interface.

The embodiment of the present application also provides a first network node, including: a first processor and a first memory configured to store a computer program that can run on the processor,

Wherein, the first processor is configured to, when running the computer program, execute the steps of any method on the first network node side above.

The embodiment of the present application also provides a second network node, including: a second processor and a second memory configured to store a computer program that can run on the processor,

Wherein, the second processor is configured to, when running the computer program, execute the steps of any method on the side of the second network node above.

The embodiment of the present application also provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of any method on the side of the first network node are implemented, or any method on the side of the second network node is implemented. the steps of a method.

In the message transmission method, device, related equipment, and storage medium provided in the embodiments of the present application, the first network node determines the slice identifier of the first message; generates a second message based on the slice identifier and the first message; The source address field in the message header of the second message carries the slice identifier; the second message is sent; the second network node receives the second message; the source address in the message header of the second message The field carries a slice identifier; the second packet is forwarded by using the slice identifier. In the solution provided by the embodiment of the present application, the source address field in the message header carries a slice identifier, which has no security risks, strong implementability, high processing efficiency, and strong compatibility with related technologies.

Description of drawings

FIG. 1 is a schematic flow diagram of a method for message transmission according to an embodiment of the present application;

FIG. 2 is a schematic diagram of the process of planning slices according to an embodiment of the present application;

Fig. 3 is a schematic diagram of an IPv6 packet format according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an SRv6 message format according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a SID format according to an embodiment of the present application;

FIG. 6 is a schematic flowchart of another method for message transmission according to an embodiment of the present application;

FIG. 7 is a schematic flow chart of message forwarding in an application embodiment of the present application;

FIG. 8 is a schematic structural diagram of a message transmission device according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of another message transmission device according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a first network node according to an embodiment of the present application;

FIG. 11 is a schematic diagram of a second network node structure according to an embodiment of the present application.

Detailed ways

The present application will be further described in detail below in conjunction with the embodiments.

Bearer network slicing technology is also mainly distributed in two aspects: the control plane and the forwarding plane. in,

The technology of the control plane mainly includes the flexible algorithm (FlexAlgo) technology. FlexAlgo technology is extended through the interior gateway protocol (IGP) segment routing (SR, Segment Routing), that is, assigning different segment identifiers (SIDs) to the same device, and different SIDs represent different FlexAlgo planes, and in each FlexAlgo plane , the cost type (MetricType), calculation type (CalcType) and link color (LinkColor) are combined for SPF calculation, and for each FlexAlgo plane, SPF calculation is performed separately, thus forming an independent routing forwarding entry.

Currently, FlexAlgo technology can only implement coarse-grained slicing at the physical link level, and because FlexAlgo technology needs to expand the control plane protocol, the system overhead is too large to support large-scale slicing, that is, it cannot support many slicing scenarios.

The technology of the forwarding plane is: introduce the slice ID to the forwarding plane, carry the slice ID in the message, and the forwarding device associates the slice ID with the physical resource, and combines it with the corresponding physical isolation technology to realize end-to-end high-quality SLA is the requirement to realize end-to-end service guarantee with quality assurance. The technical solution of the forwarding plane can achieve fine-grained slicing at the sub-interface level. At the same time, since it does not need to expand the control plane protocol, it will not bring too much overhead to the system and can support large-scale slicing.

To carry the slice ID in the message, the carrying position of the slice ID needs to be considered, and the slice ID can be carried in the hop-by-hop option header (English can be expressed as Hop-by-Hop) field in the IPv6 message header. However, for the Hop-by-Hop field, the forwarding device is required to process it hop by hop, and there is a risk of DOS attack, which is difficult in practical application at present.

The slice ID can be carried in the Flow Label field in the IPv6 packet header. However, since the Flow Label field is mainly used for traffic load sharing, it currently has 20 bits. In practical applications, when the impact of traffic load sharing is small, some bits can be divided to carry slice IDs. The larger the number of slices, the greater the number of slices. The impact on traffic load sharing is also greater, and the balance between the two needs to be considered.

The slice ID can be carried in the destination address field in the IPv6 packet header. However, for SRv6 technology, the destination address is obtained from the segment table (SegmentList) during the forwarding process, and there is a possibility of change, so the slice ID cannot be planned. Moreover, in the G-SRv6 technology, destination address compression also makes slice ID planning unfeasible.

Based on this, in various embodiments of the present application, the source address field in the packet header carries a slice identifier, such as a slice ID, which has no security risk, is highly implementable, and is compatible with related technologies.

It should be noted that: in the embodiment of this application, the first network node and the third network node are network edge nodes, which may be called PE nodes, PE routers, PE devices, etc., such as operator edge nodes in the backbone network; corresponding Specifically, the second network node is a network forwarding node, which may be called a P node, a P router, a P device, etc., such as an operator node in a backbone network.

The embodiment of the present application provides a message transmission method, which is applied to the first network node, as shown in FIG. 1, the method includes:

Step 101: Determine the slice identifier of the first packet;

Step 102: Generate a second message based on the slice identifier and the first message; the source address field in the header of the second message carries the slice identifier;

Step 103: Send the second message.

Wherein, the second packet is an IPv6 packet, and the second packet is obtained by encapsulating the first packet.

In an embodiment, the specific implementation of step 101 may include:

determining the service characteristics of the first packet;

Searching for a slice identifier corresponding to the service feature of the first packet in the first table; the first table is at least provided with a correspondence between a service feature and a slice identifier.

Wherein, the first network node may obtain the service characteristic of the first packet from configuration information of the device.

In practical applications, slice identifiers can be allocated globally through unified planning and configuration, for example, by the SDN controller or network management system, according to the characteristics of user services (such as virtual local area network (VLAN), virtual private network (VPN), or differentiated service code point ( DSCP), etc.) to plan slice identifiers globally, that is, to assign slice identifiers to corresponding user services. At this time, the SDN controller or network management system needs to send the formed slice planning information to the first network node, so that the first network node Based on this, the network node can obtain the slice identifier of the first packet.

Based on this, in an embodiment, the method may also include:

Receiving second information sent by the SDN controller or the network management system; the second information at least includes service characteristics and corresponding slice identifiers;

Using the second information, the first table is formed.

Exemplarily, as shown in Figure 2, it is assumed that there are three VPN services from three customer edge routers (CE) (respectively CE1, CE2 and CE3), and the corresponding VPN IDs are respectively VPN1, VPN2 and VPN3, and the SDN control The router or network management system plans the corresponding bandwidth (BW) requirements according to different VPN services (also can be understood as different VPN users) (the corresponding BW requirements can be planned according to the user's requirements), and assigns different slice identifiers according to the BW requirements , that is, assign required BWs and slice identifiers to different VPN users, and deliver the information to the PE1 device to form a slice planning table, as shown in Table 1.

VPN ID slice ID resource information VPN1 1 BW: 10G VPN2 2 BW: 20G VPN3 3 BW: 30G

Table 1

Here, the SDN controller or network management system (also referred to as a network management system) can be understood as a manager of network devices, and its functions can include configuration delivery, information monitoring, and route planning. In SDN, the SDN controller can plan and configure in a unified manner, and assign slice identifiers globally; in non-SDN, the network management system can plan and configure in a unified manner, and assign slice identifiers globally.

The source address field in the packet header of the second packet carries the slice identifier, that is, the slice identifier of the first packet is set in the source address field in the packet header of the second packet.

Figure 3 shows the format of an IPv6 message. As shown in Figure 3, the source address field of the IPv6 message header carries a slice identifier, such as a slice ID. In this way, if the forwarding device does not support the slice function, the source address field remains the current It has meaning, and the message can be forwarded according to the relevant IPv6 forwarding mechanism, and there is no compatibility problem. If the forwarding device supports the slicing function, the source address field can be parsed for the slicing identifier, so as to forward packets based on the slicing identifier.

For SRv6 and G-SRv6 technologies. During the SRv6 message forwarding process, as shown in Figure 4, the first network node (that is, the ingress device) carries a slice identifier in the source address of the outer IPv6 message header encapsulated in the SRv6 message, for example, in the source address field In this way, if the forwarding device does not support the slice function, then the source address field retains the existing meaning, and the message can be forwarded according to the relevant SRv6 forwarding mechanism, and there is no compatibility problem. If the forwarding device supports the slicing function, the source address field can be parsed for the slicing identifier, so as to forward packets based on the slicing identifier.

Wherein, in an embodiment, the function (Function) field in the SID of the source address field in the packet header of the second packet may carry the slice identifier. Exemplarily, as shown in FIG. 5 , the lower 16 bits reserved in the Function field may carry the slice identifier.

In practical application, as long as the IP and SRv6SID are properly planned, there is enough address space in the source address field to carry the slice identifier. Taking 16 bits as an example, it can support a maximum of 65,535 slices, which can meet the future carrying needs of thousands of industries and meet the demands of large-scale slices.

Moreover, the slice ID is carried in the source address, and the forwarding device only needs to parse a specific field in the source address in the message header, which has high processing efficiency and little impact on performance, and will not introduce new difficulties to the forwarding device (forwarding chip).

In practical applications, when the source address field carries a slice identifier, an identifier bit can be set in the packet, and the forwarding device can use the identifier bit to determine whether to analyze the slice identifier for the source address field. In this way, processing efficiency can be improved.

Based on this, in an embodiment, the packet header of the second packet further carries first information, and the first information indicates that the source address field of the second packet header carries the slice identifier.

Wherein, the first information may be encapsulated in the Traffic Class field or the Flow Label field of the packet header. That is to say, the Traffic Class field or the Flow Label field in the message header of the second message carries the first information, that is, the Traffic Class field or the Flow Label in the message header of the second message field sets the first information.

Exemplarily, the first information may be 1 bit. When it is set to 1, it means that the source address field needs to be parsed for the slice identifier. When it is set to 0, it means that the source address field does not need to be parsed for the slice identifier. .

When the SDN controller or network management system assigns slice identifiers to different user services, it associates the slice identifiers with actual physical resources (also known as link resources) for forwarding devices, and the forwarding devices identify the slice identifiers in the source address And match the corresponding physical resources for packet forwarding, and finally realize the end-to-end network slicing function of the bearer network.

Similarly, for the first network node, it is necessary to match the corresponding physical resource according to the slice identifier, so as to send the second packet.

Based on this, in an embodiment, the specific implementation of step 103 may include:

determining the outgoing interface of the second packet;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the second table; the second table is at least provided with a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

sending the second packet by using the found physical resource.

Wherein, in an embodiment, the determining the outgoing interface of the second message includes:

Determine the outbound interface of the second packet by searching the routing and forwarding table.

Here, when the second message is an IPv6 message, the outgoing interface of the second message is determined by searching the IPv6 routing table; when the second message is an SRv6 message, by searching the SRv6 routing table (It may also be referred to as a segment routing (SR) forwarding table), and determine the outgoing interface of the second packet.

The second table may be called a slice forwarding table. When the SDN controller or the network management system allocates slice identifiers for different user services, and associates the slice identifiers with actual physical resources, the SDN controller or the network management system needs to send the contents of the slice forwarding entries to the first network node and the second network node, so that the first network node and the second network node send and forward packets based on the slice forwarding table.

Based on this, in an embodiment, the method may also include:

receiving third information sent by the SDN or the network management system; the third information at least includes the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

The second table is formed using the third information.

Here, in actual application, the SDN controller or network management system can plan physical resources according to the bandwidth information of the service, so that the forwarding device combines link resource isolation technologies (such as Flexible Ethernet (FlexE), QoS, VLAN, etc.) to realize physical resource binding. Certainly.

Exemplarily, for the three slices in the above example, the slice IDs are 1, 2, and 3 respectively. For example, the physical interface GE1/0/0 is divided into BWs, and for each packet forwarding device, a corresponding G.MTN sub The interface sends corresponding information such as the slice ID and resource interface to the corresponding message forwarding devices, that is, the first network node and the second network node to form a slice forwarding table, as shown in Table 2.

out interface slice ID resource information resource interface GE1/0/0 1 BW: 10G GE1/0/0.MTN1 GE1/0/0 2 BW: 20G GE1/0/0.MTN2 GE1/0/0 3 BW: 30G GE1/0/0.MTN3

Table 2

Correspondingly, the embodiment of the present application also provides a message transmission method, which is applied to the second network node. As shown in FIG. 6, the method includes:

Step 601: Receive a second message; the source address field in the message header of the second message carries a slice identifier;

Step 602: Using the slice identifier, forward the second packet.

Wherein, in actual application, the second network node receives the second message sent from the last-hop network node; the last-hop network node may be the first network node, or the second message Other network forwarding nodes on the corresponding path.

In step 601, the second network node parses the source address field in the header of the second message to obtain the slice identifier.

In an embodiment, the packet header of the second packet further carries first information, and the first information indicates that the source address field of the second packet header carries the slice identifier; correspondingly, the The second network node determines, according to the first information, that the source address field of the second packet header needs to be analyzed for the slice identifier.

In an embodiment, the Traffic Class field or the Flow Label field in the header of the second message carries the first information, that is, the second network node passes the Traffic Class field or the Flow Label The field is parsed to obtain the first information.

In an embodiment, when the Function field in the SID of the source address field in the packet header of the second packet carries the slice identifier, the second network node parses the Function field in the SID , to get the slice ID.

In an embodiment, the forwarding of the second message by using the slice identifier includes:

Determine the outbound interface of the second packet by searching the routing and forwarding table;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the third table; the third table is provided with at least a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

Forwarding the second packet by using the found physical resource.

In one embodiment, the method may also include:

Receive the fourth information sent by the SDN or the network management system; the fourth information includes at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

The third table is formed using the fourth information.

Correspondingly, for the third network node, after receiving the second packet, it decapsulates the second packet similarly to the related technology. Wherein, the third network node receives the second message sent by the previous hop network node.

In the message transmission method provided by the embodiment of the present application, the first network node determines the slice identifier of the first message; generates a second message based on the slice identifier and the first message; the message of the second message The source address field in the header carries the slice identifier; the second packet is sent; the second network node receives the second packet; the source address field in the packet header of the second packet carries the slice identifier; using the The slice identifier is used to forward the second packet. In the solution provided by the embodiment of the present application, the source address field in the message header carries a slice identifier, which has no security risks, strong implementability, high processing efficiency, and strong compatibility with related technologies.

The present application will be further described in detail below in conjunction with application examples.

In this application example, there are three VPN services, and the VPN IDs are VPN1, VPN2, and VPN3 respectively. The SDN controller or network management system plans the corresponding BW requirements according to different VPN services, and allocates different slice IDs according to the BW requirements, and plans corresponding hardware resources according to the BW requirements for forwarding devices, such as G.MTN sub-interfaces, and assigns The interface information is associated with the slice ID, including:

First, the SDN controller or network management system allocates the required BW and slice ID for different VPN services, and sends the information to the PE device to form a slice planning table, as shown in Table 1.

Secondly, the SDN controller or network management system plans physical resources for each slice according to the BW information, so that the forwarding device combines the link resource isolation technology to realize the binding of slices and physical resources. For example, the bandwidth of the physical interface GE1/0/0 is divided, and a corresponding G.MTN sub-interface is generated for each forwarding device to implement packet forwarding. For each forwarding device, the corresponding information such as the SDN controller or the network management system slice ID and resource interface is sent to the forwarding devices (PE1, P1, and P2) to form a slice forwarding table, as shown in Table 2.

In this application embodiment, an SRv6 policy (policy) is used for packet forwarding, and the process of packet forwarding is described below in conjunction with FIG. 7 .

PE1 receives a message (a message of one of the three VPN services, including the IP header (head) and payload (payload)), first, PE1 inherits the SRv6Policy encapsulation method, encapsulates the message, and the encapsulated message contains IP head, payload, SRH, IPv6 destination address (DA) and IPv6 source address (SA); then look up table 1 according to the VPN information of the message, obtain the slice ID, and encapsulate the obtained slice ID into the source address of the SRv6 message header The lower 16 bits of the SID field; then, according to the SRv6 forwarding mechanism, look up the SR forwarding entry to confirm the physical outgoing interface; finally, according to the physical outgoing interface and slice ID lookup table 2, obtain the resource interface, and forward the packet according to the resource interface. Wherein, as shown in Table 3, the slice ID is set at the last bit of the SID.

out interface slice ID SRv6SID GE1/0/0 1 End A1:1:1:1::1:1 GE1/0/0 2 End A1:1:1:1::1:2 GE1/0/0 3 End A1:1:1:1::1:3

table 3

After P1 receives the packet, first, according to the SRv6 forwarding mechanism, it searches for the SR forwarding entry and confirms the physical outbound interface; then it analyzes the slice ID carried in the source address of the SRv6 packet header, and searches for the P1 maintained by itself according to the physical outbound interface and the slice ID. Slice the forwarding table, obtain the resource interface, and forward packets according to the resource interface.

After receiving the packet, P2 performs the same forwarding operation as that of P1.

After receiving the packet, PE2 decapsulates the packet according to the SRv6 forwarding mechanism.

It can be seen from the above description that the solution provided by the embodiment of the present application carries the slice ID in the source address field of the IPv6 packet header, has no security risk, is highly implementable, and supports IPv6, SRv6, and G-SRv6 network forwarding. And it is naturally compatible with devices that do not support slicing. The number of supported physical slices depends on the number of slice ID bits reserved in the source address field. Taking 16 bits as an example, it can support 65536 physical slices. If the address planning allows, more bits can be reserved to increase the number of slices.

In addition, the SDN controller or network management system uniformly plans user slice IDs and corresponding resource information, thereby associating slice IDs with physical link resources, which can not only realize resource isolation between physical ports, but also achieve resource isolation within the same physical port .

The forwarding device confirms the outgoing interface of the packet forwarding according to the packet forwarding table (that is, the routing forwarding table, such as IPv6 forwarding table or SRv6 forwarding table), and then uses the slice ID carried in the source address field of the packet header to determine the actual physical resources under the outgoing interface , the resource interface, and finally forward the message according to the resource interface, thus realizing finer-grained slicing under the same physical interface. In the solution of the embodiment of the present application, the slice information table lookup and forwarding process is added on the forwarding plane, which does not involve other operations and has little impact on system performance.

In the solution of the embodiment of the present application, the slice identifier is introduced into the forwarding plane, which can be combined with the FlexAlgo scheme of the control plane to form two-level slices of the control plane and the forwarding plane. Fine-grained slices.

In order to implement the method in the embodiment of the present application, the embodiment of the present application also provides a message transmission device, which is set on the first network node, as shown in FIG. 8 , the device includes:

The first determining unit 801 is configured to determine a slice identifier of the first packet;

The generating unit 802 is configured to generate a second packet based on the slice identifier and the first packet; the source address field in the packet header of the second packet carries the slice identifier;

The transmission unit 803 is configured to send the second packet.

Wherein, in an embodiment, the first determination unit 801 is configured to:

determining the service characteristics of the first packet;

Searching for a slice identifier corresponding to the service feature of the first packet in the first table; the first table is at least provided with a correspondence between a service feature and a slice identifier.

In an embodiment, the first determining unit 801 is further configured to:

receiving second information sent by the SDN controller or the network management system; the second information at least includes service characteristics and corresponding slice identifiers;

Using the second information, the first table is formed.

In an embodiment, the transmission unit 803 is configured as:

determining the outgoing interface of the second packet;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the second table; the second table is at least provided with a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

sending the second packet by using the found physical resource.

Wherein, in an embodiment, the determining the outgoing interface of the second message includes:

The transmission unit 803 determines the outbound interface of the second packet by searching the routing and forwarding table.

In an embodiment, the transmission unit 803 is further configured to:

receiving third information sent by the SDN or the network management system; the third information at least includes the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

The second table is formed using the third information.

In practical application, the first determining unit 801 and the transmitting unit 803 may be realized by a processor in the message transmission device combined with a communication interface; the generating unit 802 may be realized by a processor in the message transmission device.

In order to implement the method on the side of the second network node in the embodiment of the present application, the embodiment of the present application also provides a message transmission device, which is set on the second network node, as shown in Figure 9, the device includes:

The receiving unit 901 is configured to receive a second message; the source address field in the message header of the second message carries a slice identifier;

The forwarding unit 902 is configured to use the slice identifier to forward the second packet.

Wherein, in an embodiment, the forwarding unit 902 is configured as:

Determine the outbound interface of the second packet by searching the routing and forwarding table;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the third table; the third table is provided with at least a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

Forwarding the second packet by using the found physical resource.

Here, in an embodiment, the receiving unit 901 is further configured to:

Receive the fourth information sent by the SDN or the network management system; the fourth information includes at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

The forwarding unit 902 is further configured to use the fourth information to form the third table.

In practical applications, the receiving unit 901 and the forwarding unit 902 may be implemented by a processor in the packet transmission device combined with a communication interface.

It should be noted that: when the message transmission device provided in the above-mentioned embodiment transmits a message, it only uses the division of the above-mentioned program modules as an example for illustration. In practical applications, the above-mentioned processing can be allocated to different program modules as required Completion means that the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the message transmission device and the message transmission method embodiment provided by the above embodiment belong to the same idea, and the specific implementation process thereof is detailed in the method embodiment, and will not be repeated here.

Based on the hardware implementation of the above program modules, and in order to implement the method on the first network node side of the embodiment of the present application, the embodiment of the present application also provides a first network node. As shown in FIG. 10 , the first network node 1000 includes :

The first communication interface 1001 is capable of exchanging information with other network nodes;

The first processor 1002 is connected to the first communication interface 1001 to implement information interaction with other network nodes, and is configured to execute the methods provided by one or more technical solutions on the first network node side when running a computer program;

A first memory 1003 on which the computer program is stored.

Specifically, the first processor 1002 is configured to determine a slice identifier of the first packet; and generate a second packet based on the slice identifier and the first packet; the packet header of the second packet The middle source address field carries the slice identifier;

The first communication interface 1001 is configured to send the second message.

In an embodiment, the first processor 1002 is configured to:

determining the service characteristics of the first packet;

Searching for a slice identifier corresponding to the service feature of the first packet in the first table; the first table is at least provided with a correspondence between a service feature and a slice identifier.

In an embodiment, the first communication interface 1001 is further configured to receive second information sent by an SDN controller or a network management system; the second information includes at least service characteristics and corresponding slice identifiers;

The first processor 1002 is further configured to use the second information to form the first table.

In an embodiment, the first processor 1002 is configured to:

determining the outgoing interface of the second packet;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the second table; the second table is at least provided with a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

sending the second packet by using the found physical resource.

Wherein, in an embodiment, the determining the outgoing interface of the second message includes:

The first processor 1002 determines the outgoing interface of the second packet through the routing and forwarding table.

In an embodiment, the first communication interface 1001 is further configured to receive third information sent by SDN or a network management system; the third information includes at least the corresponding relationship between an outgoing interface, a slice identifier, and a physical resource;

The first processor 1002 is further configured to use the third information to form the second table.

It should be noted that: the specific processing process of the first processor 1002 can be understood with reference to the above method.

Of course, in practical applications, various components in the first network node 1000 are coupled together through the bus system 1004 . It can be appreciated that the bus system 1004 is configured to enable connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus and a status signal bus. However, the various buses are labeled as bus system 1004 in FIG. 10 for clarity of illustration.

The first memory 1003 in the embodiment of the present application is configured to store various types of data to support the operation of the first network node 1000 . Examples of such data include: any computer program for operating on the first network node 1000 .

The methods disclosed in the foregoing embodiments of the present application may be applied to the first processor 1002 or implemented by the first processor 1002 . The first processor 1002 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the first processor 1002 or an instruction in the form of software. The aforementioned first processor 1002 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The first processor 1002 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in the first memory 1003, and the first processor 1002 reads the information in the first memory 1003, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the first network node 1000 may be implemented by one or more Application Specific Integrated Circuits (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), complex programmable logic device (CPLD, Complex Programmable Logic Device), field programmable gate array (FPGA, Field-Programmable Gate Array), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), microprocessor (Microprocessor), or Other electronic components are implemented and configured to perform the aforementioned method.

Based on the hardware implementation of the above program modules, and in order to implement the method on the second network node side of the embodiment of the present application, the embodiment of the present application also provides a second network node, as shown in FIG. 11 , the second network node 1100 includes :

The second communication interface 1101 is capable of exchanging information with other network nodes;

The second processor 1102 is connected to the second communication interface 1101 to implement information interaction with other network nodes, and is configured to execute the methods provided by one or more technical solutions on the second network node side when running a computer program;

The second memory 1103, and the computer program is stored on the second memory 1103.

Specifically, the second communication interface 1101 is configured to receive a second message; the source address field in the message header of the second message carries a slice identifier;

The second processor 1102 is configured to use the slice identifier to forward the second packet through the second communication interface.

Wherein, in an embodiment, the second processor 1102 is configured to:

Determine the outbound interface of the second packet by searching the routing and forwarding table;

Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the third table; the third table is provided with at least a corresponding relationship between the outgoing interface, the slice identifier and the physical resource;

and forwarding the second packet through the second communication interface 1101 by using the found physical resource.

Here, the second communication interface 1101 is further configured to receive fourth information sent by the SDN or the network management system; the fourth information includes at least the corresponding relationship between the outgoing interface, the slice identifier, and the physical resource;

The second processor 1102 is further configured to use the fourth information to form the third table.

It should be noted that: the specific processing procedures of the second processor 1102 and the second communication interface 1101 can be understood with reference to the above method.

Of course, in practical application, various components in the second network node 1100 are coupled together through the bus system 1104 . It can be appreciated that the bus system 1104 is configured to enable connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus and a status signal bus. However, the various buses are labeled as bus system 1104 in FIG. 11 for clarity of illustration.

The second memory 1103 in the embodiment of the present application is configured to store various types of data to support the operation of the second network node 1100 . Examples of such data include: any computer program for operating on the second network node 1100 .

The method disclosed in the above embodiments of the present application may be applied to the second processor 1102, or implemented by the second processor 1102. The second processor 1102 may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method may be implemented by an integrated logic circuit of hardware in the second processor 1102 or instructions in the form of software. The aforementioned second processor 1102 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The second processor 1102 may implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and the storage medium is located in the second storage 1103, and the second processor 1102 reads information in the second storage 1103, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the second network node 1100 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, Microprocessors, or other electronic components, configured to perform the aforementioned methods .

It can be understood that the memory (the first memory 1003 and the second memory 1103 ) in this embodiment of the present application may be a volatile memory or a nonvolatile memory, and may also include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (ROM, Read Only Memory), programmable read-only memory (PROM, Programmable Read-Only Memory), erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory) Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD, or CD-ROM (Compact Disc Read-Only Memory); magnetic surface storage can be disk storage or tape storage. The volatile memory may be random access memory (RAM, Random Access Memory), which is used as an external cache. By way of illustration and not limitation, many forms of RAM are available such as Static Random Access Memory (SRAM, Static Random Access Memory), Synchronous Static Random Access Memory (SSRAM, Synchronous Static Random Access Memory), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), enhanced Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Memory ). The memories described in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

In an exemplary embodiment, the embodiment of the present application also provides a storage medium, that is, a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1003 storing a computer program, and the above computer program can be accessed by the first network The first processor 1002 of the node 1000 executes to complete the steps described above in the first network node side method. Another example includes the second memory 1103 storing a computer program, and the above computer program can be executed by the second processor 1102 of the second network node 1100 to complete the steps described in the foregoing second network node side method. The computer-readable storage medium can be memories such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

It should be noted that: "first", "second", etc. are used to distinguish similar objects, and not necessarily used to describe a specific order or sequence.

In addition, the technical solutions described in the embodiments of the present application may be combined arbitrarily if there is no conflict.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the protection scope of the present application.

Claims (22)

A message transmission method, applied to a first network node, comprising: Determine the slice identifier of the first packet; Generate a second message based on the slice identifier and the first message; the source address field in the header of the second message carries the slice identifier; sending the second message. The method according to claim 1, wherein the packet header of the second packet further carries first information, and the first information indicates that the source address field of the second packet header carries the slice identifier . The method according to claim 2, wherein the traffic level field or the flow label field in the packet header of the second packet carries the first information. The method according to claim 1, wherein the function field in the segment identifier SID of the source address field in the packet header of the second packet carries the slice identifier. The method according to claim 1, wherein said determining the slice identifier of the first packet comprises: determining the service characteristics of the first packet; Searching for a slice identifier corresponding to the service feature of the first packet in the first table; the first table is at least provided with a correspondence between a service feature and a slice identifier. The method according to claim 5, wherein the method further comprises: Receiving second information sent by a software-defined network SDN controller or a network management system; the second information at least includes service characteristics and corresponding slice identifiers; Using the second information, the first table is formed. The method according to any one of claims 1 to 6, wherein the sending the second message includes: determining the outgoing interface of the second packet; Searching the physical resource corresponding to the outgoing interface of the second message and the slice identifier in the second table; the second table is at least provided with a corresponding relationship between the outgoing interface, the slice identifier and the physical resource; sending the second packet by using the found physical resource. The method according to claim 7, wherein said determining the outgoing interface of said second message comprises: Determine the outbound interface of the second packet by searching the routing and forwarding table. The method according to claim 7, wherein the method further comprises: receiving the third information sent by the SDN or the network management system; the second information includes at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource; The second table is formed using the third information. A message transmission method, applied to a second network node, comprising: receiving a second message; the source address field in the message header of the second message carries a slice identifier; The second packet is forwarded by using the slice identifier. The method according to claim 10, wherein the packet header of the second packet further carries first information, and the first information indicates that the source address field of the second packet header carries the slice identifier . The method according to claim 11, wherein the traffic level field or the flow label field in the packet header of the second packet carries the first information. The method according to claim 10, wherein the function field in the SID of the source address field in the packet header of the second packet carries the slice identifier. The method according to any one of claims 10 to 13, wherein the forwarding of the second message by using the slice identifier includes: Determine the outbound interface of the second packet by searching the routing and forwarding table; Searching the physical resource corresponding to the outgoing interface and the slice identifier in the third table; the third table is provided with at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource; Forwarding the second packet by using the found physical resource. The method according to claim 14, wherein said method further comprises: Receive the fourth information sent by the SDN or the network management system; the fourth information includes at least the corresponding relationship between the outgoing interface, the slice identifier and the physical resource; The third table is formed using the fourth information. A message transmission device, comprising: The first determining unit is configured to determine the slice identifier of the first packet; A generating unit configured to generate a second message based on the slice identifier and the first message; the source address field in the header of the second message carries the slice identifier; A transmission unit configured to send the second message. A message transmission device, comprising: The receiving unit is configured to receive the second message; the source address field in the message header of the second message carries a slice identifier; The forwarding unit is configured to use the slice identifier to forward the second packet. A first network node comprising: The first processor is configured to determine the slice identifier of the first message; and generate a second message based on the slice identifier and the first message; the source address field in the message header of the second message carries the the above slice identification; The first communication interface is configured to send the second message. A second network node, comprising: a second communication interface and a second processor; wherein, The second communication interface is configured to receive a second message; the source address field in the message header of the second message carries a slice identifier; The second processor is configured to use the slice identifier to forward the second message through the second communication interface. A first network node comprising: a first processor and a first memory configured to store a computer program executable on the processor, Wherein, the first processor is configured to execute the steps of the method according to any one of claims 1 to 9 when running the computer program. A second network node comprising: a second processor and a second memory configured to store a computer program executable on the processor, Wherein, the second processor is configured to execute the steps of the method according to any one of claims 10 to 15 when running the computer program. A storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are realized, or the steps of the method according to any one of claims 10 to 15 are realized step.

Images