Business processing method and device, computer equipment and computer readable storage medium

Abstract

The invention relates to the technical field of communication, in particular to a business processing method and device, computer equipment and a computer readable storage medium. The method comprises the following steps: acquiring an original service data packet and a protocol type corresponding to the original service data packet; generating a protocol label corresponding to the original service data packet according to the protocol type and the label value distributed for the original service data packet; adding a protocol label in an MPLS label stack of the original service data packet to obtain a packaged service data packet; and sending the packaged service data packet to a target intermediate node in the MPLS network, so that the target intermediate node extracts the protocol label and the original service data packet from the packaged service data packet, and performs service processing on the original service data packet according to the protocol label.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a service processing method, apparatus, computer equipment, and computer-readable storage medium. Background Art

[0002] Multi-Protocol Label Switching (MPLS) is a new technology that uses labels to guide high-speed and efficient data transmission on an open communication network. An MPLS domain is a network area consisting of a series of network devices running MPLS. In an MPLS domain, there are two types of routers: Label Edge Router (LER) is located at the edge of the MPLS domain and connects to other networks. Label Switching Router (LSR) is a network device that switches MPLS labels and forwards packets. The LSR located inside the MPLS domain is called the Core LSR.

[0003] In the MPLS domain, data forwarding is based on labels. When a data packet enters the MPLS domain, the LER assigns it an MPLS label and pushes the label into the data packet. Subsequently, when the data packet is forwarded in the MPLS domain, the LSR forwards it according to the label forwarding table without having to check the IP header of the data packet. This method greatly improves the efficiency of data forwarding.

[0004] However, the current MPLS message encapsulation is simple and lacks a protocol identification field. The protocol identification field is usually used to identify the type of load, such as IPv4 or IPv6. Due to the lack of a protocol identification field, the forwarding device cannot directly perform intelligent scheduling based on the protocol type when performing load balancing. Therefore, improvement is urgently needed. Summary of the invention

[0005] Based on this, it is necessary to provide a business processing method, device, computer equipment and computer-readable storage medium that can realize protocol identification in response to the above technical problems.

[0006] In a first aspect, the present application provides a service processing method, which is applied to an ingress node in a multi-protocol label switching (MPLS) network, and the method includes:

[0007] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0008] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0009] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0010] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0011] In one embodiment, generating a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet includes:

[0012] Obtain the number of MPLS labels in the MPLS label stack of the original service data packet;

[0013] Generate a tag depth value based on the number of tags;

[0014] A protocol label corresponding to the original service data packet is generated according to the protocol type, the label depth value, and the label value allocated to the original service data packet.

[0015] In one embodiment, generating a protocol label corresponding to the original service data packet according to the protocol type, the label depth value and the label value allocated to the original service data packet includes:

[0016] Determine the identification value of the characteristic identification according to the acquisition of the protocol characteristic information corresponding to the protocol type;

[0017] A protocol label corresponding to the original service data packet is generated according to the protocol type, the label depth value and the identification value, as well as the label value allocated to the original service data packet.

[0018] In one of the embodiments, determining the identification value of the characteristic identification according to the acquisition of the protocol characteristic information corresponding to the protocol type includes:

[0019] When the protocol characteristic information corresponding to the protocol type is obtained, the identification value of the characteristic identification is configured as a first preset value; wherein the first preset value is used to indicate that the encapsulated service data packet contains the protocol characteristic information;

[0020] In the case that the protocol characteristic information corresponding to the protocol type is not obtained, the identification value of the characteristic identification is configured as a second preset value; wherein the second preset value is used to indicate that the encapsulated service data packet does not contain the protocol characteristic information.

[0021] In one of the embodiments, when the identification value is a first preset value, adding a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet includes:

[0022] An extended feature field containing protocol feature information is generated, and a protocol label and an extended feature field are added to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0023] In one of the embodiments, when the identification value is a second preset value, adding a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet includes:

[0024] A protocol label is added to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0025] In one embodiment, adding a protocol label and an extended feature field to an MPLS label stack of an original service data packet to obtain an encapsulated service data packet includes:

[0026] In the MPLS label stack of the original service data packet, the extended feature field is added between the protocol label and the original service data packet to obtain an encapsulated service data packet.

[0027] In one embodiment, generating an extended feature field containing protocol feature information includes:

[0028] At least one extended feature field containing the protocol feature information is generated according to the total number of characters required by the protocol feature information and the preset number of characters corresponding to the extended feature field.

[0029] In one of the embodiments, the protocol feature information includes at least a protocol version feature, a security algorithm, and a content summary hash factor corresponding to the protocol type.

[0030] In a second aspect, the present application provides a service processing method, which is applied to a target intermediate node in an MPLS network, and the method includes:

[0031] Obtaining encapsulated service data packets forwarded by the ingress node;

[0032] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0033] Perform service processing on the original service data packet according to the protocol label.

[0034] In one embodiment, performing service processing on the original service data packet according to the protocol label includes:

[0035] If the protocol type in the protocol label is consistent with the protocol type of the target intermediate node, the original service data packet is parsed to obtain the MPLS label and the original service message;

[0036] According to the node task of the target intermediate node, a label processing operation is performed on the MPLS label, and the label processing operation is used to instruct to perform service processing on the original service message.

[0037] In one embodiment, the label handling operation includes label swapping, label pushing, or label ejecting.

[0038] In a third aspect, the present application further provides a service processing device configured at an ingress node in a multi-protocol label switching MPLS network, the device comprising:

[0039] An acquisition module, used to acquire an original service data packet and a protocol type corresponding to the original service data packet;

[0040] A label generation module, used to generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0041] An encapsulation module is used to add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0042] The service processing module is used to send the encapsulated service data packet to the target intermediate node in the MPLS network, so that the target intermediate node extracts the protocol label and the original service data packet from the encapsulated service data packet and performs service processing on the original service data packet according to the protocol label.

[0043] In a fourth aspect, the present application further provides a service processing device, which is configured in a target intermediate node in a multi-protocol label switching MPLS network, and the device includes:

[0044] The encapsulation acquisition module acquires the encapsulated service data packets forwarded by the ingress node;

[0045] A parsing module is used to parse the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0046] The processing module is used to perform service processing on the original service data packet according to the protocol label.

[0047] In a fifth aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0048] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0049] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0050] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0051] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0052] In a sixth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0053] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0054] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0055] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0056] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0057] In a seventh aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0058] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0059] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0060] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0061] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0062] In an eighth aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0063] Obtaining encapsulated service data packets forwarded by the ingress node;

[0064] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0065] Perform service processing on the original service data packet according to the protocol label.

[0066] In a ninth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the following steps are implemented:

[0067] Obtaining encapsulated service data packets forwarded by the ingress node;

[0068] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0069] Perform service processing on the original service data packet according to the protocol label.

[0070] In a tenth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0071] Obtaining encapsulated service data packets forwarded by the ingress node;

[0072] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0073] Perform service processing on the original service data packet according to the protocol label.

[0074] The above-mentioned service processing method, device, computer equipment and computer-readable storage medium, the present application adds a protocol label in the MPLS label stack of the original service data packet, and the forwarding device (such as the target intermediate node) can directly identify and distinguish service data packets of different protocol types (such as IPv4, IPv6, etc.). This enables the forwarding device to perform more intelligent and precise scheduling according to the protocol type when performing load sharing, optimize the utilization of network resources, and improve network performance. The introduction of protocol labels enables the target intermediate node to more quickly identify and process different types of service data packets. This rapid processing mechanism based on protocol type helps to reduce data packet processing delays and improve overall service processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0076] FIG1 is an application environment diagram of a business processing method in one embodiment;

[0077] Figure 2 A flowchart of a business processing method in an embodiment;

[0078] FIG3 is a schematic diagram of a protocol tag in one embodiment;

[0079] FIG4 is a schematic diagram of encapsulating a data packet in one embodiment;

[0080] FIG5 is a schematic diagram of a flow chart of steps for generating a protocol label corresponding to an original service data packet in one embodiment;

[0081] FIG6 is a schematic diagram of a protocol label including a label depth value in another embodiment;

[0082] FIG7 is a schematic diagram of a protocol tag including a tag depth value and a feature identifier in another embodiment;

[0083] FIG8 is a schematic diagram of an extended feature field in one embodiment;

[0084] FIG9 is a schematic diagram of a flow chart of a service processing method in another embodiment;

[0085] FIG10 is a flow chart showing steps of performing service processing on an original service data packet according to a protocol tag in one embodiment;

[0086] FIG11 is a schematic diagram of label switching in one embodiment;

[0087] FIG12 is a schematic diagram of label pressing in one embodiment;

[0088] FIG13 is a schematic diagram of a label pop-up in one embodiment;

[0089] FIG14 is a block diagram of a service processing device in one embodiment;

[0090] FIG15 is a diagram showing the internal structure of an entry node in one embodiment;

[0091] FIG16 is a block diagram of a service processing device in one embodiment;

[0092] FIG. 17 is a diagram showing the internal structure of a target intermediate node in one embodiment. DETAILED DESCRIPTION

[0093] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0094] In traditional technologies, MPLS labels mainly include the following:

[0095] 1. Label Value: The label value is a 16-bit or 20-bit field that uniquely identifies the forwarding equivalence class (FEC) to which a data packet belongs. The router determines the next hop path of the data packet through the label value. The label value is the key index for MPLS label forwarding, ensuring that the data packet can be correctly identified and forwarded within the MPLS domain.

[0096] 2. Experimental bit (EXP / TC bit): The experimental bit is a 3-bit field used to define the quality of service (QoS) and priority of data packets. It is now commonly used as CoS (Class of Service), which has a similar function to Ethernet802.1p and is used to give priority to sending high-priority data packets when the network is congested. The experimental bit provides network administrators with a means to control network traffic and ensure quality of service, so that key applications can be given priority.

[0097] 3. Stacking bit (S bit): The stacking bit is a 1-bit field that indicates whether a data packet has been labeled multiple times in the MPLS network. If the stacking bit is 1, it means that the data packet has been labeled multiple times in the network. The stacking bit supports the multi-layer label nesting function of MPLS, allowing network administrators to build more complex and flexible network topologies.

[0098] 4. Time to Live (TTL) field: The TTL field is an 8-bit field that indicates the maximum lifetime of a data packet in the network. Each router will reduce the TTL value by 1 when forwarding a data packet. When the TTL value is 0, the router will discard the data packet to prevent the data packet from circulating infinitely in the network. The TTL field is an important mechanism to prevent network loops and ensure that the data packet has a limited lifetime in the network.

[0099] V. Other Notes

[0100] Label length: The total length of an MPLS label is 32 bits, or 4 bytes. This fixed length is not particularly burdensome for messages and is easy to process.

[0101] Label nesting: MPLS supports multi-layer label nesting, i.e. label stack. The label close to the Layer 2 header is called the top label or outer label, and the label close to the IP header is called the bottom label or inner label. In theory, MPLS labels can be nested infinitely.

[0102] Label operation: In the MPLS domain, label operation types include label push, label swap, and label pop. These operations enable data packets to be flexibly forwarded and processed in the MPLS domain.

[0103] However, the MPLS message encapsulation in traditional technology is simple and lacks the protocol identification field, which makes it impossible for the forwarding device to directly perform intelligent scheduling based on the protocol type when performing load balancing. Traditional IP networks can perform load balancing based on the protocol field in the IP header, but MPLS messages hide this information, so the device needs to deeply analyze the payload data content in the MPLS label to identify the protocol characteristics.

[0104] Based on this, this embodiment provides a service processing method and an application environment of the service processing method, the application environment includes an ingress node 102, an intermediate node 104 and an egress node 106, wherein:

[0105] The ingress node is the edge device of the MPLS domain, responsible for receiving data packets from non-MPLS networks and introducing them into the MPLS domain. The main function of the ingress node is to analyze the IP packet header and determine the transmission level and label switching path (LSP) of the data packet. It will assign an MPLS label to the data packet according to the forwarding equivalence class (FEC) of the data packet, encapsulate the MPLS label with the data packet to form an MPLS label stack, and then forward it to the next node in the MPLS domain. The ingress node is usually located at the edge of the MPLS network and connected to the non-MPLS network.

[0106] The intermediate node is the core forwarding device within the MPLS domain, responsible for forwarding the data packet to the next node based on its label. The intermediate node no longer performs Layer 3 processing on the data packet (such as IP route lookup), but quickly looks up the next hop and outgoing label based on the Label Forwarding Information Table (LFIB). It then replaces the incoming label of the data packet with the outgoing label and forwards it to the next node within the MPLS domain. The intermediate node is located inside the MPLS domain, connecting the ingress node and the egress node. An LSP may have multiple intermediate nodes, which together constitute the forwarding path of the data packet.

[0107] An egress node refers to the edge device of an MPLS domain, which is responsible for forwarding labeled packets within an MPLS domain to a non-MPLS network or another MPLS domain. An egress node is the end point of an MPLS path (LSP) and the last node where a packet leaves the MPLS domain. When an MPLS packet arrives at an egress node, the egress node identifies the label of the packet and determines the next hop of the packet based on the label forwarding information table (LFIB) or the corresponding routing table. During this process, the egress node usually performs a "label pop" operation, which removes the MPLS label of the packet and restores its original IP header. After removing the MPLS label, the egress node performs traditional IP routing forwarding based on the information in the IP header (such as the destination IP address) to send the packet to its final destination or the next network segment.

[0108] In an exemplary embodiment, as shown in FIG1 , a service processing method is provided, which is described by taking the method applied to the ingress node in FIG1 as an example, and includes:

[0109] S201, obtaining an original service data packet and a protocol type corresponding to the original service data packet.

[0110] It is understandable that when the original service data packet enters the MPLS domain, it will be processed by the ingress node. The ingress node will assign an MPLS label to it according to the protocol type and other relevant information of the data packet, and encapsulate the label with the data packet (payload). Then, this data packet with the MPLS label will be quickly forwarded through label switching in the MPLS domain until it reaches the egress node. At the egress node, the MPLS label will be removed, and the original service data packet will be restored and forwarded to the destination network.

[0111] In the MPLS network, the protocol type corresponding to the original service data packet refers to the network layer protocol used by the data packet. These protocol types determine the transmission method and format of the data packet in the network. Common network layer protocols include IPv4, IPv6, etc.

[0112] Optionally, in order to indicate the protocol type corresponding to the original service data packet, a protocol field is usually included in the header of the data packet. This field is used to indicate the protocol type used by the payload in the original service data packet of the data packet.

[0113] S202: Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value allocated to the original service data packet.

[0114] Among them, in the MPLS (Multi-Protocol Label Switching) network, the label value assigned to the original service data packet is a short identifier used to uniquely identify the forwarding equivalence class (FEC) to which the data packet belongs. This label value plays a key role in the network forwarding process, enabling the data packet to be forwarded to the destination quickly and efficiently within the MPLS domain. Optionally, the label value is usually a fixed-length field, and its length and value range may vary depending on different MPLS implementations and protocol versions.

[0115] It can be understood that the protocol label in this embodiment is different from the conventional MPLS label. The protocol label usually refers to the field in the data packet header used to identify the protocol type, while the MPLS label is an additional label added to the data packet in the MPLS network to achieve fast forwarding.

[0116] Specifically, a new label header is generated, which contains not only the label value assigned to the data packet, but also the information of the protocol type. As shown in Figure 3, field P is the protocol type, and the protocol type P occupies 7 bits; field Label is the label value assigned to the data packet, and the label value occupies 20 bits.

[0117] S203, adding a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0118] It is understandable that the MPLS label stack of the original service data packet is a series of MPLS labels located in the header of the data packet, and each label contains a label value, an experimental field (Exp), a stack bottom flag (S), and a lifetime (TTL) field. These labels are used to guide the forwarding of data packets in the network.

[0119] In an MPLS network, a standard MPLS label does not directly contain protocol type information. When a protocol label needs to be added, an extended label format or method is usually required. The protocol label in this embodiment is a special label or metadata that carries information about the protocol type of the data packet.

[0120] Specifically, there are two ways to add a protocol label to the MPLS label stack: Method 1: The process of adding a protocol label to the MPLS label stack involves inserting a new label (i.e., protocol label) on the basis of the existing label stack. Method 2: Define a new label format that is specifically used to carry protocol type information and use it as part of the MPLS label stack.

[0121] It is understandable that by adding a protocol label in the MPLS label stack, the original service data packet is encapsulated into a new data packet. This encapsulated data packet not only contains the original service data, but also contains the MPLS label stack used to guide forwarding and the protocol label carrying protocol type information.

[0122] Exemplarily, as shown in FIG4 , the original service data packet is encapsulated in a new label header to form a data packet with a protocol label; the original service data packet may include an existing MPLS label and the original service message (payload). It is understandable that the payload is the user data portion actually carried in the data packet. This portion of data can be of various types, such as text, images, video, or audio. During the transmission process, the original service message is encapsulated in the data packet and the necessary header information (such as MPLS labels and other protocol headers) is attached for transmission.

[0123] S204, sending the encapsulated service data packet to a target intermediate node in the MPLS network, so that the target intermediate node extracts the protocol label and the original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0124] The target intermediate node is any intermediate node in the MPLS network.

[0125] First, the ingress node determines the route of the next hop according to the MPLS label in the MPLS label stack to send the encapsulated service data packet to the MPLS network.

[0126] Then, when the encapsulated service data packet arrives at the target intermediate node, the node parses the MPLS label stack layer by layer until the protocol label and the original service data packet are found. According to the extracted protocol label, the target intermediate node can perform service processing on the original service data packet.

[0127] The specific content of the service processing depends on the information carried by the protocol label and the service logic in the network. For example, if the protocol label indicates that this is a data packet that needs to be encrypted, then the target intermediate node may encrypt it.

[0128] After completing the service processing, the target intermediate node needs to decide whether to forward the data packet to the next node based on the remaining MPLS labels in the MPLS label stack. If forwarding is required, the target intermediate node may update the MPLS label stack, such as removing the processed label or adding a new label. Finally, the target intermediate node sends the encapsulated service data packet (which may have been updated) to the next node in the MPLS network.

[0129] In the above-mentioned service processing method, the present application adds a protocol label to the MPLS label stack of the original service data packet, and the forwarding device (such as the target intermediate node) can directly identify and distinguish service data packets of different protocol types (such as IPv4, IPv6, etc.). This enables the forwarding device to perform more intelligent and precise scheduling according to the protocol type when performing load sharing, optimize the utilization of network resources, and improve network performance. The introduction of protocol labels enables the target intermediate node to more quickly identify and process different types of service data packets. This fast processing mechanism based on protocol type helps to reduce data packet processing delays and improve overall service processing efficiency.

[0130] In an exemplary embodiment, as shown in FIG5 , generating a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet includes:

[0131] S501: Obtain the number of MPLS labels in the MPLS label stack of the original service data packet.

[0132] Optionally, parse the data packet header of the original service data packet layer by layer until the starting position of the MPLS label stack is found. Once the MPLS label stack is found, the network device needs to traverse the entire label stack. During the traversal process, it reads each MPLS label one by one and determines the end of the label stack based on the label stack bottom flag (S). In the process of traversing the MPLS label stack, the network device counts the read MPLS labels. This is usually achieved through a counter, which increments each time a new MPLS label is read. After the traversal is completed, the network device can obtain the total number of MPLS labels in the MPLS label stack. This number can be read through the previously set counter.

[0133] S502: Generate a tag depth value according to the number of tags.

[0134] It is understood that the label depth value refers to the number of labels actually used in the MPLS label stack for a specific data packet. This value changes as the forwarding path of the data packet in the network changes.

[0135] S503: Generate a protocol label corresponding to the original service data packet according to the protocol type, the label depth value, and the label value allocated to the original service data packet.

[0136] As shown in Figure 6, the label depth value is represented by L, and the number of bits occupied by the label depth value is 4; the value of the depth field indicates the number of labels from the top of the label stack to the payload information, thereby helping the network device to correctly offset to the payload part when processing the data packet.

[0137] In this embodiment, the MPLS network can efficiently transmit and process service data packets containing multiple labels, and manage and control the depth of the label stack through the depth field L.

[0138] In an exemplary embodiment, a protocol label corresponding to the original business data packet is generated according to the protocol type, label depth value and the label value assigned to the original business data packet, including: determining the identification value of the feature identifier according to the acquisition of protocol feature information corresponding to the protocol type; generating the protocol label corresponding to the original business data packet according to the protocol type, label depth value and identification value, and the label value assigned to the original business data packet.

[0139] The protocol feature information includes at least the protocol version feature, security algorithm and content summary hash factor corresponding to the protocol type.

[0140] It can be understood that 1) Protocol version features refer to new functions, improvements or compatibility changes introduced in the development of the protocol. Different protocol versions may have different characteristics, such as packet format, field definition, processing flow, etc. For example, IPv4 and IPv6 are two different versions of IP protocols, which have significant differences in address length, header structure, extended options, etc. 2) Security algorithm is a series of algorithms and protocols used to protect the security of network communications, such as encryption algorithm, authentication algorithm, integrity verification algorithm, etc. Different protocol types may use different security algorithms to achieve data confidentiality, integrity and authentication. For example, IPSec protocol uses encryption and authentication algorithms to protect the security of IP communications. 3) Content summary Hash factor is an algorithm or parameter used to generate data summary, which can map data of any length to a fixed-length summary value for data integrity verification and fast search. In MPLS networks, content summary Hash factor can be used to quickly find and match specific data packets or data flows to improve forwarding efficiency. For example, in MPLS traffic engineering (TE), hash factors can be used to map data packets to specific forwarding paths. As shown in FIG. 7 , the protocol tag also includes a feature identifier E, and the identifier value of the feature identifier E occupies 1 bit.

[0141] In an exemplary embodiment, according to the acquisition of the protocol feature information corresponding to the protocol type, the identification value of the feature identifier is determined; according to the protocol type, the label depth value and the identification value, and the label value assigned to the original service data packet, the protocol label corresponding to the original service data packet is generated, including the following two methods:

[0142] Method 1): In one implementable method, the identification value of the feature identifier is determined based on the acquisition of the protocol feature information corresponding to the protocol type, including: when the protocol feature information corresponding to the protocol type is acquired, the identification value of the feature identifier is configured as a first preset value.

[0143] Among them, the first preset value is used to characterize that the encapsulated service data packet contains protocol feature information. In this embodiment, the first preset value can be 1. In this embodiment, when the flag bit (E bit) is set to 1, it indicates that the last 32 bits of the MPLS label are used as an extended feature field. This extended feature field can contain various additional information, such as traffic engineering parameters, quality of service (QoS) indicators, virtual private network (VPN) identifiers, etc. This extension provides greater flexibility and functionality, enabling MPLS to support more complex network services and applications.

[0144] Correspondingly, when the identification value is the first preset value, a protocol label is added to the MPLS label stack of the original business data packet to obtain an encapsulated business data packet, including: generating an extended feature field containing protocol feature information, and adding a protocol label and an extended feature field to the MPLS label stack of the original business data packet to obtain an encapsulated business data packet.

[0145] Specifically, generating an extended feature field containing protocol feature information includes: generating at least one extended feature field containing protocol feature information according to a total number of characters required by the protocol feature information and a preset number of characters corresponding to the extended feature field.

[0146] The number of extended feature fields can be obtained by dividing the total number of characters required by the protocol feature information by the preset number of characters corresponding to the extended feature field. If multiple extended feature fields are obtained, each extended feature field stores a part of the protocol feature information.

[0147] Taking one of the extended feature fields as an example, as shown in Figure 8, the extended feature field includes an E' field and a U field; the U field is used to store the protocol feature information corresponding to the extended feature field; the E' field is used to indicate whether the 32 bits after the extended feature field are still the extended feature field; if the E' field is 1, it means that another extended feature field is after the extended feature field, and if the E' field is 0, it means that the MPLS label is after the extended feature field.

[0148] Method 2): In another possible implementation method, the identification value of the feature identifier is determined based on the acquisition of the protocol feature information corresponding to the protocol type, including: if the protocol feature information corresponding to the protocol type is not acquired, the identification value of the feature identifier is configured as a second preset value.

[0149] Among them, the second preset value is used to characterize that the encapsulated service data packet does not contain protocol feature information. As in the above example, the second preset value in this embodiment can be set to 0. When the flag bit (E bit) is set to 0, it indicates that the MPLS label is a standard or "ordinary" MPLS label and the extended feature field is not used. In this case, the corresponding bits of the MPLS label (usually 32 bits, but in some implementations it may be 20 bits or other lengths) are used as the label value, which is used to guide the forwarding path of the data packet in the network.

[0150] Correspondingly, when the identification value is the second preset value, a protocol label is added to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet, including: adding a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0151] Optionally, when the identification value is the second preset value, it indicates that there is no protocol characteristic information at this time, and only a protocol label is added to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0152] In this embodiment, by dynamically constructing and adding protocol labels and their extended feature fields, the flexibility, scalability and data packet processing capability of the MPLS network are improved, while resource utilization is optimized and the readability and maintainability of the network are improved, which helps to meet the ever-changing business needs.

[0153] In an exemplary embodiment, as shown in FIG9 , a service processing method is applied to a target intermediate node in an MPLS network, and the method includes:

[0154] S901, obtaining an encapsulated service data packet forwarded by an ingress node.

[0155] The ingress node receives and forwards a service data packet encapsulated with a protocol label. The data packet may have been processed at a previous node and attached with an MPLS (Multi-Protocol Label Switching) label or other types of protocol labels.

[0156] S902, parse the encapsulated service data packet to obtain a protocol label and an original service data packet.

[0157] The protocol label is generated according to the protocol type of the service data packet and the label value allocated to the service data packet.

[0158] Optionally, first, the target intermediate node first identifies that the received message is an MPLS message, which is usually done by checking the protocol field of the message layer 2 header (such as the Ethernet header). The MPLS message usually carries one or more MPLS labels after the layer 2 header.

[0159] Then, the target intermediate node starts parsing the MPLS label stack. The label stack is composed of one or more MPLS labels, each of which contains a label value, an experimental field (Exp), a stack bottom flag (S), and an extension flag (E).

[0160] During the parsing of the label stack, the target intermediate node identifies the protocol label. The protocol label is a special label used to indicate that the message carries certain specific feature information or needs to be processed in a specific way.

[0161] The target intermediate node then checks the E field in the protocol label. The E field is a flag that indicates whether an extension field or other special information follows the label. If the E field indicates that there are characteristic extension fields following the protocol label (i.e., E=1), the target intermediate node skips these extension fields and does not process them. This is because the extension fields may contain information that is not relevant to the forwarding decision or need to be processed by other devices or subsequent processing steps. After skipping the characteristic field, the target intermediate node continues to parse the label stack and reads out the next MPLS label, which is used to guide the forwarding path of the message. The target intermediate node forwards the message according to the normal process based on the value of the MPLS label and other relevant information (such as routing tables, forwarding policies, etc.). During the forwarding process, the protocol label remains unchanged, that is, it will not be removed or changed.

[0162] S903: Perform service processing on the original service data packet according to the protocol label.

[0163] Specifically, as shown in FIG10 , the original service data packet is processed according to the protocol label, including:

[0164] S1001: If the protocol type in the protocol label is consistent with the protocol type of the target intermediate node, the original service data packet is parsed to obtain an MPLS label and an original service message.

[0165] It is understandable that protocol type matching is the key to ensure that data packets are correctly processed and forwarded. This protocol type is compared with the protocol type of the target intermediate node. If the protocol type does not match, the data packet may be discarded or sent to the wrong path. The original business message is the above payload.

[0166] S1002: Perform a label processing operation on the MPLS label according to the node task of the target intermediate node. The label processing operation is used to instruct to perform service processing on the original service message.

[0167] Optionally, the label handling operation includes label swapping, label pushing, or label ejecting.

[0168] Specifically, the corresponding label processing operations are performed on the MPLS label according to the specific tasks of the target intermediate node (such as forwarding, switching, termination, etc.). These operations may include label swapping (replacing the old label with a new label), pushing a new label (adding a new label to the top of the label stack), or label popping (removing a label from the top of the label stack.

[0169] It is understood that label switching means that when a data packet needs to pass through a different path or needs to be further processed by a different node, a label switching operation may be performed. This allows network devices to dynamically change the forwarding path of the data packet based on the current routing decision or forwarding strategy. As shown in Figure 11, the MPLS label L1 is replaced with the MPLS label L2.

[0170] Pushing a label means that when a data packet needs to enter a new MPLS domain or needs to be further encapsulated to meet specific network requirements, a label push operation may be performed. This allows network devices to add new labels to the label stack of the data packet to guide the forwarding and processing of the data packet in the subsequent network. As shown in Figure 12, MPLS label L2 and MPLS label L3 are pushed on top of MPLS label L1, causing MPLS label L1 to pop out.

[0171] Label popping refers to the process where a packet may be popped when it reaches its destination or no longer needs an MPLS label for forwarding. This allows network devices to remove labels from the packet's label stack, thereby restoring the original service message for further processing or delivery to the end user. As shown in Figure 13, MPLS label L2 and MPLS label L3 are popped, leaving only MPLS label L4.

[0172] Optionally, when the target intermediate node performs the above label switching, label pushing or label popping, the protocol label always remains unchanged and is located at the top of the MPLS stack.

[0173] Furthermore, when the next node of the target intermediate node is an egress node, the target intermediate node strips off all the protocol labels, extended protocol fields and MPLS labels, retains only the original service message, and forwards the original service message to the egress node.

[0174] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0175] Based on the same inventive concept, the embodiment of the present application also provides a business processing device for implementing the business processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more business processing device embodiments provided below can refer to the limitations on the business processing method above, and will not be repeated here.

[0176] In an exemplary embodiment, as shown in FIG14 , a service processing device 1 is provided, comprising: an original acquisition module 11, a label generation module 12, an encapsulation module 13 and a forwarding module 14, wherein:

[0177] The original acquisition module 11 is used to obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0178] The label generation module 12 is used to generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0179] The encapsulation module 13 is used to add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0180] The forwarding module 14 is used to send the encapsulated service data packet to the target intermediate node in the MPLS network, so that the target intermediate node extracts the protocol label and the original service data packet from the encapsulated service data packet and performs service processing on the original service data packet according to the protocol label.

[0181] In one of the embodiments, the label generation module 12 is further used to: obtain the number of MPLS labels in the MPLS label stack of the original service data packet;

[0182] Generate a tag depth value based on the number of tags;

[0183] A protocol label corresponding to the original service data packet is generated according to the protocol type, the label depth value, and the label value allocated to the original service data packet.

[0184] In one embodiment, the label generation module 12 is further configured to:

[0185] Determine the identification value of the characteristic identification according to the acquisition of the protocol characteristic information corresponding to the protocol type;

[0186] A protocol label corresponding to the original service data packet is generated according to the protocol type, the label depth value and the identification value, as well as the label value allocated to the original service data packet.

[0187] In one embodiment, the label generation module 12 is further used to: when the protocol characteristic information corresponding to the protocol type is obtained, configure the identification value of the characteristic identification to a first preset value; wherein the first preset value is used to indicate that the encapsulated service data packet contains the protocol characteristic information;

[0188] In the case that the protocol characteristic information corresponding to the protocol type is not obtained, the identification value of the characteristic identification is configured as a second preset value; wherein the second preset value is used to indicate that the encapsulated service data packet does not contain the protocol characteristic information.

[0189] In one of the embodiments, when the identification value is a first preset value, the label generation module 12 is also used to: generate an extended feature field containing protocol feature information, and add a protocol label and an extended feature field to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0190] In one of the embodiments, when the identification value is the second preset value, the label generation module 12 is further configured to: add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0191] In one embodiment, the label generation module 12 is further used to: add an extended feature field between the protocol label and the original service data packet in the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

[0192] In one embodiment, the label generation module 12 is further used to generate at least one extended feature field containing the protocol feature information according to the total number of characters required by the protocol feature information and the preset number of characters corresponding to the extended feature field.

[0193] In one of the embodiments, the protocol feature information includes at least a protocol version feature, a security algorithm, and a content summary hash factor corresponding to the protocol type.

[0194] Each module in the above-mentioned business processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0195] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG15. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data of a business processing method. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a business processing method is implemented.

[0196] Those skilled in the art will understand that the structure shown in FIG. 15 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0197] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0198] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0199] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0200] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0201] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0202] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0203] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0204] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0205] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0206] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0207] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0208] Obtain the original service data packet and the protocol type corresponding to the original service data packet;

[0209] Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet;

[0210] Add a protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet;

[0211] The encapsulated service data packet is sent to a target intermediate node in the MPLS network, so that the target intermediate node extracts a protocol label and an original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

[0212] In an exemplary embodiment, as shown in FIG16 , a service processing device 2 is provided, comprising: an encapsulation acquisition module 21, a parsing module 22 and a processing module 23, wherein:

[0213] The encapsulation acquisition module 21 acquires the encapsulated service data packet forwarded by the ingress node;

[0214] The parsing module 22 is used to parse the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0215] The processing module 23 is used to perform service processing on the original service data packet according to the protocol label.

[0216] Each module in the above-mentioned business processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0217] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG17. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data of a business processing method. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a business processing method is implemented.

[0218] Those skilled in the art will understand that the structure shown in FIG. 17 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0219] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0220] Obtaining encapsulated service data packets forwarded by the ingress node;

[0221] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0222] Perform service processing on the original service data packet according to the protocol label.

[0223] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0224] Obtaining encapsulated service data packets forwarded by the ingress node;

[0225] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0226] Perform service processing on the original service data packet according to the protocol label.

[0227] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0228] Obtaining encapsulated service data packets forwarded by the ingress node;

[0229] Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value assigned to the service data packet;

[0230] Perform service processing on the original service data packet according to the protocol label.

[0231] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0232] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0233] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A business processing method, characterized in that: Applied to an ingress node in a multi-protocol label switching (MPLS) network, the method comprises: Obtaining an original service data packet and a protocol type corresponding to the original service data packet; Generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet; Adding the protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet; The encapsulated service data packet is sent to a target intermediate node in an MPLS network, so that the target intermediate node extracts the protocol label and the original service data packet from the encapsulated service data packet, and performs service processing on the original service data packet according to the protocol label.

2. The method according to claim 1, characterized in that The generating, according to the protocol type and the label value allocated to the original service data packet, a protocol label corresponding to the original service data packet, comprises: Obtaining the number of MPLS labels in the MPLS label stack of the original service data packet; Generate a tag depth value according to the number of tags; A protocol label corresponding to the original service data packet is generated according to the protocol type, the label depth value and the label value allocated to the original service data packet.

3. The method according to claim 2, characterized in that The generating, according to the protocol type, the label depth value and the label value allocated to the original service data packet, a protocol label corresponding to the original service data packet comprises: Determining an identification value of a characteristic identifier according to an acquisition of the protocol characteristic information corresponding to the protocol type; A protocol label corresponding to the original service data packet is generated according to the protocol type, the label depth value and the identification value, as well as the label value allocated to the original service data packet.

4. The method according to claim 3, characterized in that The determining the identification value of the characteristic identification according to the acquisition of the protocol characteristic information corresponding to the protocol type includes: In the case of acquiring the protocol characteristic information corresponding to the protocol type, configuring the identification value of the characteristic identification to be a first preset value; wherein the first preset value is used to indicate that the encapsulated service data packet contains the protocol characteristic information; In the case where the protocol characteristic information corresponding to the protocol type is not obtained, the identification value of the characteristic identifier is configured as a second preset value; wherein the second preset value is used to indicate that the encapsulated service data packet does not contain the protocol characteristic information.

5. The method according to claim 4, characterized in that When the identification value is the first preset value, adding the protocol label in the MPLS label stack of the original service data packet to obtain the encapsulated service data packet includes: An extended feature field including the protocol feature information is generated, and the protocol label and the extended feature field are added to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

6. The method according to claim 4, characterized in that When the identification value is the second preset value, adding the protocol label in the MPLS label stack of the original service data packet to obtain the encapsulated service data packet includes: The protocol label is added to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet.

7. The method according to claim 5, characterized in that The adding the protocol label and the extended feature field into the MPLS label stack of the original service data packet to obtain the encapsulated service data packet includes: In the MPLS label stack of the original service data packet, the extended feature field is added between the protocol label and the original service data packet to obtain an encapsulated service data packet.

8. The method according to claim 5, characterized in that The generating of the extended feature field containing the protocol feature information comprises: At least one extended feature field containing the protocol feature information is generated according to the total number of characters required by the protocol feature information and the preset number of characters corresponding to the extended feature field.

9. The method according to claim 3, characterized in that: The protocol feature information includes at least the protocol version feature, security algorithm and content summary Hash factor corresponding to the protocol type.

10. A business processing method, characterized in that: Applied to a target intermediate node in an MPLS network, the method comprises: Obtaining encapsulated service data packets forwarded by the ingress node; Parsing the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value allocated to the service data packet; Perform service processing on the original service data packet according to the protocol label.

11. The method according to claim 10, characterized in that The performing service processing on the original service data packet according to the protocol label includes: If the protocol type in the protocol label is consistent with the protocol type of the target intermediate node, the original service data packet is parsed to obtain an MPLS label and an original service message; According to the node task of the target intermediate node, a label processing operation is performed on the MPLS label, where the label processing operation is used to instruct to perform service processing on the original service message.

12. The method according to claim 11, characterized in that The label handling operation includes label swapping, label pushing or label ejecting.

13. A service processing device, characterized in that: An ingress node configured in a multi-protocol label switching (MPLS) network, the device comprising: An original acquisition module, used to acquire an original service data packet and a protocol type corresponding to the original service data packet; A label generation module, used to generate a protocol label corresponding to the original service data packet according to the protocol type and the label value assigned to the original service data packet; An encapsulation module, used for adding the protocol label to the MPLS label stack of the original service data packet to obtain an encapsulated service data packet; The forwarding module is used to send the encapsulated service data packet to the target intermediate node in the MPLS network, so that the target intermediate node extracts the protocol label and the original service data packet from the encapsulated service data packet and performs service processing on the original service data packet according to the protocol label.

14. A service processing device, characterized in that: A target intermediate node configured in a multi-protocol label switching (MPLS) network, the device comprising: The encapsulation acquisition module acquires the encapsulated service data packets forwarded by the ingress node; A parsing module, used to parse the encapsulated service data packet to obtain a protocol label and an original service data packet; the protocol label is generated according to the protocol type of the service data packet and the label value allocated to the service data packet; A processing module is used to perform service processing on the original service data packet according to the protocol label.

15. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 12 are implemented.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

17. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

Images