Method and apparatus for managing a transmission tunnel

Abstract

The embodiment of the application provides a kind of transmission tunnel management method and device, wherein the method is applied to network controller, comprising: receiving the session management function entity SMF sent user plane path establishment request;Determine the user plane path of one session between two UPFs, path label identification and the message forwarding rule of path based on the tunnel information between two UPFs carried in the user plane path establishment request;Send the message forwarding rule configuration request carrying the message forwarding rule of the path to all forwarding devices R on the user plane path.This application provides the transmission tunnel management method, by directly encapsulating GTP message into label message in bearer network, realize the fast transmission of GTP message in bearer network, simplify the complexity of forwarding device processing, reduce the data transmission delay.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method and apparatus for managing transmission tunnels. Background Technology

[0002] In 5G networks, the user plane uses the GTP-U protocol, meaning that the data stream transmitted on the user plane is a GTP data stream. If the GTP data stream needs to be transmitted through a data network, there is no corresponding solution in the existing technology.

[0003] If the existing labeling protocol is used, for the forwarding of 5G GTP packets in the transport network, the incoming label forwarding device first needs to extract the IP packet from the GTP packet after receiving it, generate a label based on the IP packet header, and then encapsulate it into a tagged packet for transmission. Then, the outgoing label forwarding device in the transport network needs to strip the label, extract the IP packet, and then encapsulate the IP packet into a GTP packet based on the IP packet header before transmitting it to the 5G user plane forwarding device. This requires multiple processing steps for the received packets by both the incoming and outgoing label forwarding devices, increasing the complexity of the forwarding equipment and increasing data transmission latency. Summary of the Invention

[0004] To address the problems existing in the prior art, this application provides a method and apparatus for managing transmission tunnels.

[0005] In a first aspect, embodiments of this application provide a method for managing a transmission tunnel, applied to a network controller, comprising:

[0006] Receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs;

[0007] Based on the tunnel information between the two UPFs carried in the user plane path establishment request, determine the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs.

[0008] Send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path;

[0009] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0010] Optionally, the determined packet forwarding rule for the path is the first packet forwarding rule for the path, which specifically includes:

[0011] If the forwarding device R is an ingress forwarding device R, the first packet forwarding rule of the path includes: determining to encapsulate the GTP packet into a tagged packet according to the path tag identifier based on the matching item in the packet forwarding rule of the ingress forwarding device R, and determining the next hop interface;

[0012] If the forwarding device R is an egress forwarding device R, the first packet forwarding rule of the path includes: removing the path label identifier to extract the GTP packet and determining the next hop interface based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header in the label packet.

[0013] If the forwarding device R is an intermediate forwarding device R, the first packet forwarding rule of the path includes: matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, replacing the content of the header of the label packet with the path label identifier corresponding to the next hop in the user plane path, and determining the next hop interface, or matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, and determining the next hop interface.

[0014] Optionally, the user plane path establishment request may also include QoS information, which is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs;

[0015] Alternatively, the user plane path establishment request may also include a QoS flow identifier and QoS information, wherein the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0016] Optionally, before determining the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request, the method further includes:

[0017] The target QoS label is determined based on the QoS indication carried in the user plane path establishment request and the mapping relationship between the QoS indication and the QoS label stored locally, or based on the QoS label carried in the user plane path establishment request.

[0018] Optionally, the step of determining the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request includes:

[0019] Based on the tunnel information between the two UPFs carried in the user plane path establishment request and the target QoS label, a user plane path, path label identifier, and second packet forwarding rule for a session between the two UPFs are determined.

[0020] Optionally, the second message forwarding rule for the path includes:

[0021] If the forwarding device R is an ingress forwarding device R, the second packet forwarding rule of the path includes: matching the content of the header in the GTP packet with the matching item in the packet forwarding rule of the ingress forwarding device R, determining to encapsulate the GTP packet into a tagged packet according to the path label identifier and the QoS label, and determining the next hop interface and performing QoS control according to the QoS label;

[0022] If the forwarding device R is an egress forwarding device R, the second packet forwarding rule of the path includes: removing the path label identifier to extract the GTP packet based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet; determining the next hop interface; and performing QoS control according to the QoS label in the header of the label packet.

[0023] If the forwarding device R is an intermediate forwarding device R, the second packet forwarding rule of the path includes: matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, replacing the content of the header of the label packet with the path label identifier corresponding to the next hop in the user plane path, determining the next hop interface and performing QoS control according to the QoS label in the header of the label packet, or matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, determining the next hop interface and performing QoS control according to the QoS label in the header of the label packet.

[0024] Optionally, the QoS indicator may include: 5QI, Tos, Traffic Class, or Service ClassIndicator.

[0025] Optionally, the method further includes:

[0026] Receive a user plane path modification request sent by the Session Management Function Entity (SMF), wherein the user plane path modification request includes tunnel information and QoS information between the two UPFs;

[0027] Based on the user plane path modification request, determine the target QoS label corresponding to the QoS information;

[0028] Based on the target QoS label, update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R;

[0029] Send the updated second message forwarding rule for the path to the ingress forwarding device R on the user plane path;

[0030] The updated second packet forwarding rule of the path is used to perform QoS control on the target packet according to the target QoS label, wherein the target packet is a GTP packet or a GTP packet encapsulated with a label.

[0031] Optionally, if the user plane path modification request includes tunnel information and QoS information between the two UPFs, the QoS information is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs.

[0032] Alternatively, if the user plane path modification request includes tunnel information between the two UPFs, a QoS flow identifier, and QoS information, then the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0033] Optionally, determining the target QoS tag corresponding to the QoS information based on the user plane path modification request includes:

[0034] The target QoS label is determined based on the QoS indication in the user plane path modification request, the mapping relationship between the locally configured QoS indication and QoS label, or based on the QoS label carried in the user plane path modification request.

[0035] Optionally, the method further includes:

[0036] Receive a user plane path deletion request sent by the Session Management Function Entity (SMF), wherein the user plane path deletion request includes tunnel information between the two UPFs;

[0037] Based on the tunnel information between the two UPFs carried in the user plane path deletion request, the user plane path to be deleted is determined, and an instruction is sent to all forwarding devices R on the user plane path to delete the packet forwarding rules of the corresponding path.

[0038] Secondly, embodiments of this application also provide a method for managing a transmission tunnel, applied to a Session Management Function (SMF) entity, comprising:

[0039] Send a user plane path establishment request to the network controller, the user plane path establishment request including tunnel information between the two UPFs;

[0040] The tunnel information between the two UPFs is used to determine the packet forwarding rules for the path between the two UPFs. The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels for GTP packets and forwarding them to the next-hop interface under the condition of satisfying the matching items.

[0041] Optionally, the user plane path establishment request may also include QoS information, which is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs;

[0042] Alternatively, the user plane path establishment request may also include a QoS flow identifier and QoS information, wherein the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0043] Optionally, the QoS label is determined based on the mapping relationship between locally configured QoS indications and QoS labels.

[0044] Optionally, the method further includes:

[0045] Send a user plane path modification request to the network controller. The user plane path modification request includes tunnel information and QoS information between the two UPFs, or tunnel information and QoS label between the two UPFs. It is used to update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R according to the target QoS label, so that the ingress forwarding device R performs QoS control on the target packet according to the updated QoS label in the second forwarding rule of the path.

[0046] The target QoS label is a QoS label determined based on the QoS information and the pre-configured mapping relationship between QoS indication and QoS label, or a QoS label carried in the user plane path modification request. The QoS information is a QoS indication corresponding to the tunnel information between the two UPFs.

[0047] Optionally, the method further includes:

[0048] Send a user plane path modification request to the network controller. The user plane path modification request includes tunnel information between the two UPFs, QoS flow identifier and QoS information, or tunnel information between the two UPFs, QoS flow identifier and QoS label. It is used to update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R according to the target QoS label, so that the ingress forwarding device R performs QoS control on the target packet according to the updated QoS label in the second forwarding rule of the path.

[0049] The target QoS label is a QoS label determined based on the QoS information and the pre-configured mapping relationship between QoS indication and QoS label, or a QoS label carried in the user plane path modification request. The QoS information is a QoS indication corresponding to the QoS flow identifier.

[0050] Optionally, the method further includes:

[0051] Send a user plane path deletion request to the network controller. The user plane path deletion request includes tunnel information between the two UPFs and is used to delete the packet forwarding rules of the user plane path and all forwarding devices R on the user plane path.

[0052] The deleted user plane path is determined by the network controller based on the tunnel information between the two UPFs carried in the user plane path deletion request, and there is a one-to-one correspondence between the user plane path and the packet forwarding rules of the path on the user plane path.

[0053] Thirdly, embodiments of this application also provide a method for managing transmission tunnels, applied to a forwarding device, comprising:

[0054] Receive the packet forwarding rules for the path generated by the network controller, and complete the configuration of the packet forwarding rules for the path locally;

[0055] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0056] Optionally, when the packet forwarding rule of the path is the first packet forwarding rule of the path:

[0057] If the forwarding device R is an ingress forwarding device R, the GTP message is encapsulated into a tagged message according to the path tag identifier based on the matching item in the message forwarding rule of the ingress forwarding device R, and the next hop interface is determined.

[0058] If the forwarding device R is an egress forwarding device R, the path label identifier is removed to extract the GTP packet and determine the next hop interface based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet.

[0059] If the forwarding device R is an intermediate forwarding device R, the content of the header of the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path, based on the matching item in the packet forwarding rule of the intermediate forwarding device R according to the content of the header of the label packet. The next hop interface is then determined, or the next hop interface is determined based on the matching item in the packet forwarding rule of the intermediate forwarding device R according to the content of the header of the label packet.

[0060] Optionally, when the packet forwarding rule for the path is the second packet forwarding rule for the path:

[0061] If the forwarding device R is an ingress forwarding device R, based on the matching items in the packet forwarding rules of the ingress forwarding device R, it is determined that the GTP packet will be encapsulated into a tagged packet according to the path label identifier and QoS label, and the next hop interface is determined and QoS control is performed according to the QoS label.

[0062] If the forwarding device R is an egress forwarding device R, the path label identifier is removed to extract the GTP packet based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet, and the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet.

[0063] If the forwarding device R is an intermediate forwarding device R, the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R, the content of the header of the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path, and the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet, or the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet, the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R.

[0064] Optionally, the method further includes:

[0065] Receive an update packet forwarding rule request sent by the network controller, which includes packet forwarding rules for paths with new QoS labels, and update the QoS labels in the packet forwarding rules for the paths locally;

[0066] Based on the new QoS label carried by the packet forwarding rules of the path, QoS control is performed on the GTP packet or the GTP packet after encapsulation label.

[0067] Optionally, the method further includes:

[0068] Receive a deletion command from the network controller, which includes the user plane path to be deleted;

[0069] Based on the deletion instruction and the correspondence between the user plane path and the packet forwarding rules of the path, delete the corresponding packet forwarding rules of the path stored locally.

[0070] Fourthly, embodiments of this application also provide a network controller electronic device, including a memory, a transceiver, and a processor, wherein:

[0071] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs in the memory and implementing the steps of the transmission tunnel management method described in the first aspect above.

[0072] Fifthly, embodiments of this application also provide a Session Management Function (SMF) electronic device, including a memory, a transceiver, and a processor, wherein:

[0073] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs in the memory and implementing the steps of the transmission tunnel management method described in the second aspect above.

[0074] Sixthly, embodiments of this application also provide a forwarding electronic device, including a memory, a transceiver, and a processor, wherein:

[0075] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs in the memory and implementing the steps of the transmission tunnel management method described in the third aspect above.

[0076] In a seventh aspect, embodiments of this application also provide a network controller device, the device comprising:

[0077] The first receiving module is used to receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs.

[0078] The first determining module is used to determine the user plane path, path label identifier, and packet forwarding rules of a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request.

[0079] The first sending module is used to send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path;

[0080] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0081] Eighthly, embodiments of this application also provide a Session Management Function (SMF) device, the device comprising:

[0082] The second sending module is used to send a user plane path establishment request to the network controller, wherein the user plane path establishment request includes tunnel information between the two UPFs.

[0083] The tunnel information between the two UPFs is used to determine the packet forwarding rules for the path between the two UPFs. The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels for GTP packets and forwarding them to the next-hop interface under the condition of satisfying the matching items.

[0084] Ninthly, embodiments of this application also provide a forwarding device apparatus, the apparatus comprising:

[0085] The third receiving module is used to receive the packet forwarding rules for the path generated by the network controller and to configure the packet forwarding rules for the path locally.

[0086] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0087] In a tenth aspect, embodiments of this application also provide a processor-readable storage medium storing a computer program configured to cause the processor to perform the steps of the transmission tunnel management method described in the first aspect, or the steps of the transmission tunnel management method described in the second aspect, or the steps of the transmission tunnel management method described in the third aspect.

[0088] The transmission tunnel management method and apparatus provided in this application enable the rapid transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, thereby simplifying the processing complexity of forwarding devices and reducing data transmission latency. Attached Figure Description

[0089] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0090] Figure 1 This is a user plane protocol stack structure diagram of a PDU session in a 5G network provided in this application;

[0091] Figure 2 This is a schematic diagram of the MPLS message format in the existing technology;

[0092] Figure 3 This is a diagram of the bearer network architecture provided in the embodiments of this application;

[0093] Figure 4 This is a protocol stack structure diagram of MPLS-based GTP packet forwarding provided in an embodiment of this application;

[0094] Figure 5 This is one of the flowcharts illustrating the transmission tunnel management method provided in this application embodiment;

[0095] Figure 6 This is a second schematic flowchart of the transmission tunnel management method provided in the embodiments of this application;

[0096] Figure 7 This is the third flowchart illustrating the transmission tunnel management method provided in this application embodiment;

[0097] Figure 8 This is one of the flowcharts for establishing a user plane path provided in the embodiments of this application;

[0098] Figure 9 This is one of the flowcharts for user plane path modification provided in the embodiments of this application;

[0099] Figure 10 This is one of the flowcharts for deleting user plane paths provided in the embodiments of this application;

[0100] Figure 11 This is the second flowchart of user plane path establishment provided in the embodiments of this application;

[0101] Figure 12 This is the second flowchart of user plane path modification provided in the embodiments of this application;

[0102] Figure 13 This is the second flowchart of user plane path deletion provided in the embodiments of this application;

[0103] Figure 14 A schematic diagram of the structure of the network controller electronic device provided in the embodiments of this application;

[0104] Figure 15 A schematic diagram of the structure of the Session Management Function (SMF) electronic device provided in this application embodiment;

[0105] Figure 16 A schematic diagram of the structure of the forwarding electronic device provided in the embodiments of this application;

[0106] Figure 17 This is a schematic diagram of the network controller device provided in the embodiments of this application;

[0107] Figure 18 This is a schematic diagram of the structure of the Session Management Function (SMF) device provided in the embodiments of this application;

[0108] Figure 19 This is a schematic diagram of the forwarding device provided in the embodiments of this application. Detailed Implementation

[0109] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0110] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0111] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0112] This application provides a method and apparatus for managing transmission tunnels, addressing the problem in the prior art where the ingress label forwarding device of the bearer network needs to strip the label to extract the IP packet, and then the egress label forwarding device of the bearer network encapsulates the IP packet header into a GTP packet for transmission to the 5G user plane forwarding device. This requires both the ingress and egress forwarding devices to process the received packets multiple times, increasing the complexity of the forwarding equipment and adding to data transmission latency.

[0113] The technical solution based on this application does not require stripping and extracting IP packets, or encapsulating them into GTP packets based on the IP packet header. Instead, it directly encapsulates tags on the basis of GTP packets, replaces or deletes tags, and forwards the packets according to the packet forwarding rules of the path. This simplifies the processing complexity of the forwarding device and reduces data transmission latency.

[0114] The method and apparatus are based on the same concept of the application. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and the repeated parts will not be described again.

[0115] To better describe the various embodiments of this application, the following will be introduced first:

[0116] (I) User Plane Protocol Stack of PDU Session in 5G Network

[0117] Figure 1 This refers to the user plane protocol stack of a PDU session. 3GPP TS 23.501 describes the user plane protocol stack for a PDU session in 5G networks. In 5G systems, UPF typically uses GTP tunnels for implementation. GTP (GPRS tunneling protocol, tunnel endpoint identifier) ​​tunnels are bidirectional and are identified by the source IP address, destination IP address, UDP port number, and destination GTP TEID. The GTP TEID is assigned by the network elements at both ends of the tunnel. A session consists of multiple GTP tunnel segments, and each GTP tunnel segment corresponds to only one session. During data forwarding, the forwarding network element is determined based on the GTP data packet header in the data packet. If it matches, the GTP data packet header in that data packet is replaced with the GTP data packet header of the next tunnel segment, and then forwarded.

[0118] (II) Basic Principles of MPLS Technology

[0119] MPLS technology uses standard packet processing methods (usually IP) to forward Layer 3 packets and label switching to exchange Layer 2 packets on open networks. It leverages labels to guide high-speed, efficient data transmission, introducing connection-mode characteristics into a connectionless network. An MPLS network mainly consists of three parts: Label Edge Routers (LERs), Label Switching Routers (LSRs), and Label Distribution Protocol (LDP). The LER is responsible for inspecting incoming packets, attaching appropriate labels, and forwarding them to the LSR. The LSR is the core device of the MPLS network, responsible for stripping old labels and adding new ones, using fast hardware switching technology to achieve simple and fast table lookup and packet forwarding. Label switching by switches requires LDP support. LDP utilizes existing routing protocols (such as OSPF and BGP) to provide a method for exchanging label information between LSRs (or LERs).

[0120] Basic processing steps:

[0121] (1) LER and LSR use standard IP routing protocols such as OSPF and BGP to identify routes and generate routing tables. Adjacent LSRs and LERs assign label information to the routing tables through LDP and distribute them, storing them in their respective Label Information Bases (LIBs) and establishing dedicated Label Switching Paths (LSPs) for specified classes of packets.

[0122] (2) Analyze the network layer frame header information of the packet at the ingress LER, select a route, add an FEC association label indicating the packet's affiliation to the packet, and then forward it to the next node LSR on the corresponding LSP.

[0123] (3) At the data link layer, packets are forwarded sequentially between LSRs on the LSP based solely on label values, eliminating the need to analyze network layer frame header information for route selection. At each LSR, the LIB needs to be retrieved to find the new label associated with the egress point and replace the old label.

[0124] (4) At the exit LER, there are two situations: ① If the next node of the boundary node is a non-MPLS node, the label is removed and the packet is routed and forwarded according to the traditional network routing protocol; ② If the next node of the boundary node is the boundary node of another MPLS domain, the label stack technology is used so that the packet continues to enter the next MPLS domain in the label switching mode.

[0125] MPLS message format is as follows: Figure 2 As shown, the total length of the label is 32 bits, and the meaning of each field is as follows:

[0126] Tag: 20 bits long, used to identify FEC, one tag corresponds to one FEC; EXP (Experimental): 3 bits long, its purpose is not explicitly defined, it is a reserved bit, usually used to identify QoS level, can support 8 different values, used to identify 8 DiffServ categories;

[0127] BS (Bottom of Stack): The bottom label bit of the stack, with a length of 1 bit. MPLS supports multiple nesting of labels. When the BS value is 1, it means that the label is the bottom label of the stack.

[0128] TTL (Time to Live): The time-to-live field is 8 bits long and is used to prevent MPLS network packet storms caused by loops.

[0129] The bearer network architecture diagram provided in the embodiments of the present invention is as follows: Figure 3 As shown, the bearer network mainly consists of a network controller and forwarding devices R, where the forwarding devices R are routers / switches. When a GTP packet enters the bearer network through the ingress forwarding device R, a label is encapsulated in the GTP packet. When it is sent to the UPF through the egress forwarding device R, the label is removed from the label packet, and the GTP packet is obtained to continue the next step of transmission.

[0130] Figure 4 This is a protocol stack structure diagram of MPLS-based GTP packet forwarding provided in an embodiment of this application;

[0131] The network controller of the bearer network generates label-based routing rules for packet forwarding and performs QoS control and QoS labeling based on the tunnel information and / or QoS-related information sent by the SMF, ultimately realizing the fast forwarding of GTP packets in the bearer network.

[0132] The following embodiments of the present invention are all based on Figure 3 The network architecture diagram is illustrated based on the session granularity between the two UPFs.

[0133] Figure 5 This is one of the flowcharts illustrating the transmission tunnel management method provided in this application embodiment, such as... Figure 5 As shown in the figure, this application provides a method for managing transmission tunnels, applied to a network controller, the method comprising:

[0134] Step 501: Receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs.

[0135] Step 502: Based on the tunnel information between the two UPFs carried in the user plane path establishment request, determine the user plane path, path label identifier, and packet forwarding rules of a session between the two UPFs.

[0136] Step 503: Send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path;

[0137] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0138] Specifically, the network controller receives a user plane path establishment request sent by the Session Management Function (SMF) entity. The user plane path establishment request includes tunnel information between the two UPFs. The tunnel information between the two UPFs refers to the tunnel information corresponding to a session between the two UPFs: the address and tunnel endpoint identifier of the first UPF, and the address and tunnel endpoint identifier of the second UPF.

[0139] Based on the tunnel information between the two UPFs, the network controller determines the user plane path, path label, and packet forwarding rules for a session between the two UPFs.

[0140] The user plane path of a session between the two UPFs is the forwarding path formed by the forwarding devices R through which the target packet passes in the bearer network. Based on the determined user plane path, a corresponding path label is set to represent the path information and to encapsulate the GTP packet into a labeled packet. The packet forwarding rules of the path are the packet forwarding rules of each router / switch on the path. Specifically, when a GTP packet enters the bearer network through the ingress forwarding device R, a label is encapsulated on the GTP packet to obtain a labeled packet. At the egress forwarding device R, the label is removed from the labeled packet, and the GTP packet is forwarded to the next interface. The specific forwarding rules follow the packet forwarding rules of the path. The target packet is compared with the matching items in the packet forwarding rules of the path. If they match, the target packet is encapsulated with a label according to the packet forwarding rules of the path, the label is replaced or removed, and it is forwarded to the next hop interface.

[0141] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0142] Optionally, the determined packet forwarding rule for the path is the first packet forwarding rule for the path, which specifically includes:

[0143] If the forwarding device R is an ingress forwarding device R, the first packet forwarding rule of the path includes: determining to encapsulate the GTP packet into a tagged packet according to the path tag identifier based on the matching item in the packet forwarding rule of the ingress forwarding device R, and determining the next hop interface;

[0144] If the forwarding device R is an egress forwarding device R, the first packet forwarding rule of the path includes: removing the path label identifier to extract the GTP packet and determining the next hop interface based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header in the label packet.

[0145] If the forwarding device R is an intermediate forwarding device R, the first packet forwarding rule of the path includes: matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, replacing the content of the header of the label packet with the path label identifier corresponding to the next hop in the user plane path, and determining the next hop interface, or matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, and determining the next hop interface.

[0146] Specifically, when the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, the network controller determines the user plane path between the two UPFs based on the tunnel information between the two UPFs in the user plane path establishment request, the path label identifier PLID_i, and the first packet forwarding rule of the path.

[0147] This allows for the direct encapsulation, replacement, and deletion of tags in GTP messages based on path tag identifiers, and the determination of the next-hop interface.

[0148] The first message forwarding rule for the path specifically includes:

[0149] Packet forwarding rules for ingress forwarding device R:

[0150]

[0151] Compare the GTP message sent by the UPF with the matching items in the table above. If a match is found, encapsulate the GTP message with PLID_i to become a tagged message and determine the next-hop interface.

[0152] There are two scenarios for the packet forwarding rules of intermediate forwarding device R. The first scenario is:

[0153] Matching items Message processing Next steps PLID_i Replace tags Next-hop interface

[0154] In the first case, the matching item is the path label identifier between every two intermediate forwarding devices R; when transmitting between different intermediate forwarding devices R in the user plane path, the label needs to be replaced with the path label identifier corresponding to the next hop in the user plane path, and the corresponding next hop interface is found by matching the label packet header content with the matching item.

[0155] The second scenario:

[0156] Matching items Next steps PLID_i Next-hop interface

[0157] In the second case, the matching item is the path label identifier of the user plane path as a whole generated by the network controller. All forwarding devices on the user plane path have this path label identifier. The header of the label packet received by the intermediate forwarding device R is compared with the matching item. If they match, the next hop interface of the label packet is determined.

[0158] In this case, the matching item for the outgoing forwarding device R and the matching item for the intermediate forwarding device R are the same, which is the path label identifier PLID_i encapsulated in the GTP message by the incoming forwarding device R.

[0159] The message forwarding rules for the outbound forwarding device R are as follows:

[0160] Matching items Message processing Next steps PLID_i Delete PLID_i to extract GTP messages Next-hop interface

[0161] Forward the tag message to the egress forwarding device R, delete the path tag identifier PLID_i in the tag message header and extract the GTP message.

[0162] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0163] Optionally, the user plane path establishment request may further include QoS information, which is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs; or, the user plane path establishment request may further include a QoS flow identifier and QoS information, which is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0164] Specifically, when QoS control of packets is required, the user plane path establishment request sent by the SMF includes tunnel information and QoS information between the two UPFs. The QoS information can be a QoS indication corresponding to the tunnel information between the two UPFs or a QoS tag. Alternatively, the user plane establishment request sent by the SMF includes tunnel information between the two UPFs, a QoS flow identifier, and QoS information, where the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0165] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0166] Optionally, before determining the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request, the method further includes:

[0167] The target QoS label is determined based on the QoS indication carried in the user plane path establishment request and the mapping relationship between the QoS indication and the QoS label stored locally, or based on the QoS label carried in the user plane path establishment request.

[0168] Specifically, when the user plane path establishment request sent by the SMF includes tunnel information and QoS information between the two UPFs, but does not include the QoS flow identifier, the network controller, based on the QoS information in the user plane path establishment request, i.e. the QoS indication corresponding to the tunnel information between the two UPFs, looks up the mapping relationship between the locally configured QoS indication and QoS label, determines the QoS label, and uses it as the target QoS label.

[0169] Alternatively, if the user plane path establishment request sent by the SMF includes tunnel information and a QoS tag between the two UPFs, the QoS tag in the request is directly used as the target QoS tag. The QoS tag carried in the request is directly determined by the SMF based on service requirements (corresponding QoS indications) and the mapping relationship between locally stored QoS indications and QoS tags.

[0170] When the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, QoS flow identifiers and QoS information, that is, when the user plane path establishment request includes QoS flow identifiers, it means that there are one or more QoS flow identifiers in the tunnel corresponding to a session established between the two UPFs. Based on the QoS indication corresponding to the QoS flow identifier, the mapping relationship between the locally configured QoS indication and QoS label is looked up, and the QoS label is determined as the target QoS label.

[0171] Alternatively, if the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, QoS flow identifiers, and QoS tags, the QoS tag in the request can be directly used as the target QoS tag. Here, the QoS tag carried in the request is directly determined by the SMF based on service requirements (corresponding QoS indications) and the mapping relationship between locally stored QoS indications and QoS tags.

[0172] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0173] Optionally, the step of determining the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request includes:

[0174] Based on the tunnel information between the two UPFs carried in the user plane path establishment request and the target QoS label, a user plane path, path label identifier, and second packet forwarding rule for a session between the two UPFs are determined.

[0175] Specifically, the target QoS label can be determined indirectly through the QoS information carried in the user plane establishment request or directly through the QoS label carried in the user plane establishment request. Both methods are used by the network controller to determine the user plane path of a session between the two UPFs based on the tunnel information between the two UPFs and the target QoS label included in the received user plane path establishment request. The path label identifier is PLID_i and the second packet forwarding rule of the path is also included.

[0176] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0177] Optionally, the second message forwarding rule for the path includes:

[0178] If the forwarding device R is an ingress forwarding device R, the second packet forwarding rule of the path includes: matching the content of the header in the GTP packet with the matching item in the packet forwarding rule of the ingress forwarding device R, determining to encapsulate the GTP packet into a tagged packet according to the path label identifier and the QoS label, and determining the next hop interface and performing QoS control according to the QoS label;

[0179] If the forwarding device R is an egress forwarding device R, the second packet forwarding rule of the path includes: removing the path label identifier to extract the GTP packet based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet; determining the next hop interface; and performing QoS control according to the QoS label in the header of the label packet.

[0180] If the forwarding device R is an intermediate forwarding device R, the second packet forwarding rule of the path includes: matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, replacing the content of the header of the label packet with the path label identifier corresponding to the next hop in the user plane path, determining the next hop interface and performing QoS control according to the QoS label in the header of the label packet, or matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, determining the next hop interface and performing QoS control according to the QoS label in the header of the label packet.

[0181] Specifically, the second packet forwarding rule for the path mainly targets the case where the user plane path establishment request includes tunnel information and QoS information between the two UPFs, or includes tunnel information, QoS flow identifier and QoS information between the two UPFs. When the network controller receives the user plane path establishment request, it generates the corresponding user plane path between the two UPFs, the path label identifier PLID_i and the second packet forwarding rule for the path.

[0182] This system implements operations such as encapsulating, replacing, and deleting tags on GTP packets based on path label identifiers and QoS tags, determining the next-hop interface, and performing QoS control according to QoS tags. The ingress forwarding device R refers to the first forwarding device R on which the GTP packet is forwarded to the bearer network after passing through the UPF. Conversely, the egress forwarding device R is the last forwarding device R on which the tagged packet is forwarded to the UPF after leaving the bearer network. Intermediate forwarding devices are any forwarding devices on the user plane path other than the ingress and egress forwarding devices.

[0183] When the user plane path establishment request includes tunnel information and QoS information between the two UPFs, the specific second packet forwarding rules for the corresponding path include:

[0184] The packet forwarding rules for the ingress forwarding device R are as follows:

[0185]

[0186] The GTP message sent by the UPF is compared with the matching items in the table above. If a match is found, the GTP message is encapsulated with PLID_i and a QoS label to become a tagged message. The next-hop interface is determined, and QoS control is performed on the tagged message according to the QoS label. The QoS label encapsulation is mainly performed on the ingress forwarding device R.

[0187] There are two scenarios for the packet forwarding rules of intermediate forwarding device R. The first scenario is:

[0188]

[0189] In the first case, the matching item is the path label identifier between every two intermediate forwarding devices R. When transmitting between different intermediate forwarding devices R in the user plane path, the label needs to be replaced with the path label identifier corresponding to the next hop in the user plane path. The matching item is matched with the label packet header content to find the corresponding next hop interface, and QoS control is performed according to the QoS label in the label packet header.

[0190] The second scenario:

[0191]

[0192] In the second case, the matching item is the path label identifier of the user plane path as a whole generated by the network controller. All forwarding devices on the user plane path have this path label identifier. The header of the label packet received by the intermediate forwarding device R is compared with the matching item. If they match, the next-hop interface of the label packet is determined, and QoS control is performed according to the QoS label in the header of the label packet.

[0193] In this case, the matching item for the outgoing forwarding device R and the matching item for the intermediate forwarding device R are the same, which is the path label identifier PLID_i encapsulated in the GTP message by the incoming forwarding device R.

[0194] The message forwarding rules for the outbound forwarding device R are as follows:

[0195]

[0196] The tagged message is forwarded to the egress forwarding device R. The path label identifier PLID_i in the tagged message header is deleted to extract the GTP message. Then, the GTP message is subjected to QoS control according to the QoS label in the tagged message header.

[0197] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0198] Specifically, when the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, QoS flow identifiers and QoS information, the network controller, based on the QoS information in the user plane path establishment request, i.e. the QoS indication corresponding to the QoS flow identifier, looks up the mapping relationship between the locally configured QoS indication and QoS label, determines the QoS label, and uses it as the target QoS label.

[0199] Based on the tunnel information between the two UPFs included in the user plane path establishment request and the final QoS label determined above, a user plane path for a session between the two UPFs is determined, the path label identifier PLID_i and the second packet forwarding rule of the path are determined.

[0200] When a user plane path establishment request includes tunnel information between the two UPFs, QoS flow identifiers, and QoS information, the second packet forwarding rules for the path determined by the network controller specifically include:

[0201] Packet forwarding rules for ingress forwarding device R:

[0202]

[0203] The GTP message sent by the UPF is compared with the matching items in the table above. If a match is found, the GTP message is encapsulated with PLID_i and a QoS label to become a tagged message. The next-hop interface is determined, and QoS control is performed on the tagged message according to the QoS label. The QoS label encapsulation is mainly performed on the ingress forwarding device R. Here, QFI_j represents a flow in a tunnel between the two UPFs, the QoS label is determined according to the QoS indication corresponding to the QoS flow identifier, and the QoS information is the QoS indication corresponding to the QoS flow identifier.

[0204] There are two scenarios for the packet forwarding rules of intermediate forwarding device R. The first scenario is:

[0205]

[0206] In the first case, the matching item is the path label identifier between every two intermediate forwarding devices R. When transmitting between different intermediate forwarding devices R in the user plane path, the label needs to be replaced with the path label identifier corresponding to the next hop in the user plane path. The matching item is matched with the label packet header content to find the corresponding next hop interface, and QoS control is performed according to the QoS label in the label packet header.

[0207] The second scenario:

[0208]

[0209] In the second case, the matching item is the path label identifier of the user plane path as a whole generated by the network controller. All forwarding devices on the user plane path process the tagged packets based on this path label identifier. The header of the tagged packet received by the intermediate forwarding device R is compared with the matching item. If they match, the next-hop interface of the tagged packet is determined, and QoS control is performed according to the QoS label in the header of the tagged packet.

[0210] In this case, the matching item for the outgoing forwarding device R and the matching item for the intermediate forwarding device R are the same, which is the path label identifier PLID_i encapsulated in the GTP message by the incoming forwarding device R.

[0211] The message forwarding rules for the outbound forwarding device R are as follows:

[0212]

[0213] The tagged message is forwarded to the egress forwarding device R. The path label identifier PLID_i in the tagged message header is deleted to extract the GTP message. Then, the GTP message is subjected to QoS control according to the QoS label in the tagged message header.

[0214] The main differences between the second packet forwarding rule determined by the network controller for the user plane path establishment request, which includes tunnel information between the two UPFs, QoS flow identifiers, and QoS information, and the second packet forwarding rule determined by the network controller for the user plane path request, which includes tunnel information between the two UPFs and QoS information, are as follows:

[0215] When a QoS flow identifier is present, the matching items of the packet forwarding rules of the ingress forwarding device R include not only the destination UPF address and tunnel endpoint identifier, but also the QoS flow identifier. The corresponding QoS tag is determined based on the QoS indication corresponding to the QoS flow identifier.

[0216] Without a QoS flow identifier, the matching items for the packet forwarding rules of the ingress forwarding device R are the address of the destination UPF and the tunnel endpoint identifier, and the corresponding QoS label is determined according to the QoS indication corresponding to the tunnel information between the two UPFs.

[0217] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0218] Optionally, the QoS indicator may include: 5QI, Tos, Traffic Class, or Service ClassIndicator.

[0219] Specifically, different business requirements have corresponding QoS information. Of course, there are also cases where different business requirements correspond to the same QoS information. This depends on the network configuration of the operator. The QoS information is a QoS indication corresponding to the tunnel information or QoS flow identifier between the two UPFs. It can also be understood that different business requirements have corresponding QoS indications. The corresponding parameters include: 5QI, Tos, Traffic Class or Service Class Indicator.

[0220] The definition of 5QI is in 3GPP specification 23.501. 5QI is a scalar used to point to a 5G QoS feature. These parameters are used to control the QoS of QoS flow forwarding processing.

[0221] ToS, Service Type.

[0222] Traffic Class, the communication classification field, is used to identify the corresponding communication flow category, or priority level.

[0223] Service Class Indicator.

[0224] Based on the above parameters, determine the QoS indication corresponding to the business requirements, and determine the QoS label according to the mapping relationship between the pre-configured QoS indication and the QoS label.

[0225] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, thereby reducing data transmission latency.

[0226] Optionally, the user plane path modification request sent by the Session Management Function Entity (SMF) is received, wherein the user plane path modification request includes tunnel information and QoS information between the two UPFs.

[0227] Based on the user plane path modification request, determine the QoS tag corresponding to the QoS information;

[0228] Based on the QoS label, update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R;

[0229] Send the updated second message forwarding rule for the path to the ingress forwarding device R on the user plane path;

[0230] The updated second packet forwarding rule of the path is used to perform QoS control on the target packet according to the target QoS label, wherein the target packet is a GTP packet or a GTP packet encapsulated with a label.

[0231] In practical applications, after establishing the user plane path, it may be necessary to modify the QoS information in the user plane path, which is achieved through a user plane path modification request.

[0232] The network controller receives a user plane path modification request sent by the SMF, which includes tunnel information and QoS information between the two UPFs. Based on the tunnel information between the two UPFs, the controller determines the tunnel information corresponding to a specific session between the two UPFs, and based on the QoS information included in the user plane path modification request, determines the corresponding QoS label. The determined QoS label is then used to update the existing second packet forwarding rules for the path.

[0233] Since the QoS label is a process of encapsulating GTP packets with QoS labels performed on the ingress forwarding device R according to the matching rules, the modification here mainly updates the forwarding rules for the ingress forwarding device R in the second packet forwarding rules of the path, and updates the QoS label in the forwarding rules of the ingress forwarding device to the newly determined QoS label.

[0234] The updated path's second packet forwarding rule is sent to the ingress forwarding device R on the user plane path. After receiving the updated path's second packet forwarding rule and completing the configuration, the ingress forwarding device will perform the relevant operations according to the updated path's second packet forwarding rule when forwarding subsequent GTP packets to the corresponding ingress forwarding device R.

[0235] The transmission tunnel management method provided in this application modification method changes the QoS information of the user plane path in a session between two UPFs, changes the QoS label in the packet forwarding rules of the path, and encapsulates the GTP packet with a new QoS label on the ingress forwarding device R, thereby updating the parameters for QoS control of the target packet and performing QoS control on the target packet according to the updated QoS label.

[0236] Optionally, if the user plane path modification request includes tunnel information and QoS information between the two UPFs, the QoS information is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs.

[0237] Alternatively, if the user plane path modification request includes tunnel information between the two UPFs, a QoS flow identifier, and QoS information, then the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0238] Specifically, when the user plane path modification request includes tunnel information and QoS information between the two UPFs, the QoS information can be a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs.

[0239] When a user plane path modification request includes tunnel information between the two UPFs, QoS flow identifiers, and QoS information, the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier. The QoS flow identifier indicates that multiple QoS flows may exist in a tunnel within a session between the two UPFs. Each flow corresponds to a QoS flow identifier, and these identifiers may correspond to different QoS indications, enabling different QoS control for different flows.

[0240] When a QoS flow identifier and QoS information exist, the granularity of the corresponding QoS tag is specific to the QoS flow identifier; when no QoS flow identifier exists, the granularity of the corresponding QoS tag is specific to the tunnel information between the two UPFs. Optionally, determining the target QoS tag corresponding to the QoS information based on the user plane path modification request includes:

[0241] The target QoS label is determined based on the QoS indication in the user plane path modification request, the mapping relationship between the locally configured QoS indication and QoS label, or based on the QoS label carried in the user plane path modification request.

[0242] Specifically, when the user plane path modification request includes tunnel information and QoS information between the two UPFs, and the QoS information is a QoS indication corresponding to the tunnel information between the two UPFs, the network controller determines the target QoS label based on the above QoS indication and the mapping relationship between the locally configured QoS indication and QoS label.

[0243] When the QoS information is a QoS label, the tunnel information and QoS label between the two UPFs are directly carried in the user plane modification request sent by the SMF. The QoS label here is determined by the SMF based on user requirements and the mapping relationship between locally configured QoS indicators and QoS labels; and is then directly sent to the network controller.

[0244] In the case where the user plane path modification request includes tunnel information between the two UPFs, QoS flow identifier, and QoS information, the QoS information is the QoS indication or QoS tag corresponding to the QoS flow identifier.

[0245] When the QoS information is a QoS indication corresponding to the QoS flow identifier, the network controller determines the target QoS tag corresponding to the QoS information based on the aforementioned QoS indication and the mapping relationship between the locally configured QoS indication and QoS tag.

[0246] When the QoS information is a QoS label, the user plane modification request sent by the SMF directly carries the tunnel information between the two UPFs, the QoS flow identifier, and the QoS label. Here, the QoS label is determined by the SMF based on user requirements and the mapping relationship between locally configured QoS indicators and QoS labels; and then directly sent to the network controller.

[0247] The transmission tunnel management method provided in this application modifies the QoS information of the user plane path in the tunnel information corresponding to a session between two UPFs, changing the QoS label in the packet forwarding rules of the path. The QoS label can be determined at the QoS flow identifier granularity or at the QoS indication corresponding to the tunnel between the two UPFs granularity. The new QoS label is then encapsulated in the GTP packet on the ingress forwarding device R to update the parameters for QoS control of the target packet, and QoS control of the target packet is performed according to the updated QoS label.

[0248] Optionally, a user plane path deletion request sent by the Session Management Function Entity (SMF) is received, wherein the user plane path deletion request includes tunnel information between the two UPFs.

[0249] Based on the tunnel information between the two UPFs carried in the user plane path deletion request, the user plane path to be deleted is determined, and an instruction is sent to all forwarding devices R on the user plane path to delete the packet forwarding rules of the corresponding path.

[0250] Specifically, depending on business needs, user plane path information can also be deleted. Specifically, the network controller receives a user plane path deletion request sent by the SMF, which includes tunnel information between the two UPFs.

[0251] Based on the tunnel information between the two UPFs carried in the user plane path deletion request, the network controller determines a tunnel corresponding to a session between the two UPFs. The tunnel determines a specific user plane path, i.e. the user plane path to be deleted, and sends an instruction to the forwarding device on the user plane path so that the forwarding device deletes the packet forwarding rules of the corresponding path and sends a response message to the SMF.

[0252] The transmission tunnel management method provided in this application deletes the tunnel corresponding to a session between two UPFs by sending a user plane path deletion request, i.e., the user plane path information corresponding to the session, and sends it to the forwarding device on the user plane path so as to delete the packet forwarding rules of the corresponding path.

[0253] Figure 6 This is a second schematic flowchart of the transmission tunnel management method provided in the embodiments of this application; as shown Figure 6 As shown, this application embodiment provides a method for managing a transmission tunnel, applied to a Session Management Function (SMF) entity, including:

[0254] Step 601: Send a user plane path establishment request to the network controller. The user plane path establishment request includes tunnel information between the two UPFs.

[0255] The tunnel information between the two UPFs is used to determine the packet forwarding rules for the path between the two UPFs. The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels for GTP packets and forwarding them to the next-hop interface under the condition of satisfying the matching items.

[0256] Specifically, the Session Management Function (SMF) entity sends a User Plane Path Establishment Request to the Network Controller, which includes tunnel information between the two UPFs.

[0257] Upon receiving the request, the network controller generates user plane path information, path label identifier, and packet forwarding rules for the path, and forwards them to the relevant forwarding devices.

[0258] When the SMF receives a response message from the network controller, it can determine that the forwarding device has completed the configuration of the packet forwarding rules for the path. According to the packet forwarding rules of the path, if the target packet meets the matching conditions, it can encapsulate the target packet with a label, replace the label or delete the label, and forward it to the next-hop interface. The target packet is a GTP packet or a GTP packet with an encapsulated label.

[0259] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0260] Optionally, the user plane path establishment request may also include QoS information, which is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs.

[0261] Alternatively, the user plane path establishment request may also include a QoS flow identifier and QoS information, wherein the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0262] Specifically, when QoS control of messages is required, the user plane path establishment request sent by SMF may also include QoS information, or may also include QoS flow identifier and QoS information.

[0263] That is, the user plane path establishment request sent by the SMF includes tunnel information and QoS information between the two UPFs, or includes tunnel information, QoS flow identifier and QoS information between the two UPFs.

[0264] When the user plane path establishment request sent by the SMF includes tunnel information and QoS information between the two UPFs, the QoS information is a QoS indication corresponding to the tunnel information between the two UPFs. Here, the QoS information is at the granularity of the tunnel between the two UPFs.

[0265] Alternatively, if the user plane path establishment request sent by the SMF includes tunnel information and a QoS label between the two UPFs, the QoS label is determined by the SMF based on service requirements (QoS indication) and the mapping relationship between locally configured QoS indication and QoS label.

[0266] Alternatively, if the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, QoS flow identifiers, and QoS information, then the QoS information is a QoS indication corresponding to the QoS flow identifier. The QoS flow identifier represents that there may be multiple flows in the tunnel between the two UPFs, and each flow is characterized by a corresponding identifier. That is, the granularity of the QoS information is specific to the QoS flow identifier.

[0267] Alternatively, if the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, QoS flow identifiers, and QoS tags, the QoS tags are determined by the SMF based on service requirements (QoS indications corresponding to QoS flow identifiers) and the mapping relationship between locally configured QoS indications and QoS tags.

[0268] The transmission tunnel management method provided in this application encapsulates GTP packets into tagged packets directly in the bearer network. The QoS tag can be determined at the QoS indication corresponding to the QoS flow identifier, or at the QoS indication corresponding to the tunnel between the two UPFs. This allows for more precise QoS control of target packets based on the QoS tag.

[0269] Optionally, a user plane path modification request is sent to the network controller. The user plane path modification request includes tunnel information and QoS information between the two UPFs, or tunnel information and QoS label between the two UPFs. This is used to update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R according to the target QoS label, so that the ingress forwarding device R performs QoS control on the target packet according to the updated QoS label in the second forwarding rule of the path.

[0270] The target QoS label is a QoS label determined based on the QoS information and the pre-configured mapping relationship between QoS indication and QoS label, or a QoS label carried in the user plane path modification request. The QoS information is a QoS indication corresponding to the tunnel information between the two UPFs.

[0271] Specifically, when it is necessary to modify the QoS information of the user plane path according to business needs, a user plane path modification request is sent, carrying the tunnel information and QoS information between the two UPFs, or carrying the tunnel information and QoS tag between the two UPFs.

[0272] When a user plane path modification request carries tunnel information and QoS information between the two UPFs, the network controller determines the target QoS label based on the QoS indication corresponding to the tunnel information between the two UPFs represented by the QoS information, as well as the mapping relationship between the locally configured QoS indication information and QoS labels.

[0273] Based on the tunnel information between the two UPFs and the target QoS label, the network controller generates a user plane path, path label identifier, and packet forwarding rules between the two UPFs. The forwarding device, according to the packet forwarding rules, determines whether the target packet meets the matching criteria, encapsulates a label on the target packet, replaces or deletes the label, and forwards it to the next-hop interface. It also performs QoS control on the target packet according to the QoS label, where the target packet is a GTP packet or a GTP packet encapsulated with a label.

[0274] When a user plane path modification request carries tunnel information and QoS labels between the two UPFs, the SMF determines the target QoS label based on the QoS label corresponding to the user's service requirements and the relationship between the locally configured QoS indication and QoS label mapping. This target QoS label is then sent to the network controller in the user plane path establishment request. This is used to generate the user plane path between the two UPFs, the path label identifier, and the packet forwarding rules for the path. Subsequent processing and QoS information are the same as in the case of the QoS indication corresponding to the tunnel information between the two UPFs, and will not be described further here.

[0275] The transmission tunnel management method provided in this application modification method changes the QoS information of the user plane path in a session between two UPFs, changes the QoS label in the packet forwarding rules of the path, and encapsulates the GTP packet with a new QoS label on the ingress forwarding device R, thereby updating the parameters for QoS control of the target packet and performing QoS control on the target packet according to the updated QoS label.

[0276] Optionally, the method further includes:

[0277] Send a user plane path modification request to the network controller. The user plane path modification request includes tunnel information, QoS flow identifier and QoS information between the two UPFs, or tunnel information, QoS flow identifier and QoS label. It is used to update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R according to the target QoS label, so that the ingress forwarding device R performs QoS control on the target packet according to the updated QoS label in the second forwarding rule of the path.

[0278] The target QoS label is a QoS label determined based on the QoS information and the pre-configured mapping relationship between QoS indication and QoS label, or a QoS label carried in the user plane path modification request. The QoS information is a QoS indication corresponding to the QoS flow identifier.

[0279] Specifically, the SMF sends a user plane path modification request to the network controller to modify the QoS information on the corresponding path, i.e., modify the QoS label. The QoS information is the QoS indication corresponding to the QoS flow identifier. When the user plane path modification request sent by the SMF includes tunnel information, the QoS flow identifier, and the QoS information, the network controller determines the target QoS label based on the QoS indication corresponding to the QoS flow identifier and the locally configured mapping relationship between QoS indications and QoS labels. Then, it updates the packet forwarding rules for the path corresponding to the ingress forwarding device R according to the target QoS label, specifically updating the QoS label in the second packet forwarding rule of the path. This ensures that the target packet undergoes QoS control according to the updated QoS label in the second forwarding rule of the path.

[0280] Similarly, when the user plane path modification request sent by SMF includes tunnel information, QoS flow identifier, and QoS tag, the QoS tag carried in the request is determined based on the QoS indication corresponding to the QoS flow identifier and the mapping relationship between the locally configured QoS indication and QoS tag. The subsequent methods are the same as the methods for determining tunnel information, QoS flow identifier, and QoS information in the user plane path modification request, and will not be described in detail here.

[0281] Optionally, the method further includes:

[0282] Send a user plane path deletion request to the network controller. The user plane path deletion request includes tunnel information between the two UPFs and is used to delete the user plane path and the packet forwarding rules of the path of all forwarding devices on the user plane path.

[0283] The deleted user plane path is determined by the network controller based on the tunnel information between the two UPFs carried in the user plane path deletion request, and there is a one-to-one correspondence between the user plane path and the packet forwarding rules of the path on the user plane path.

[0284] Specifically, based on user service requirements, if a corresponding user plane path needs to be deleted, the SMF sends a user plane path deletion request to the network controller. The user plane path deletion request includes tunnel information between the two UPFs. The network controller receives the user plane path deletion request, determines the user plane path information based on the tunnel information between the UPFs carried in the request, and uses it to delete the user plane path. The network controller then sends a sending instruction to all forwarding devices R on the user plane path to delete the packet forwarding rules of the corresponding user plane path.

[0285] The transmission tunnel management method provided in this application deletes a session between two UPFs by sending a user plane path deletion request, i.e., the user plane path information corresponding to the session, and sends it to the forwarding device on the user plane path so as to delete the packet forwarding rules of the corresponding path.

[0286] Figure 7 This is the third flowchart illustrating the transmission tunnel management method provided in this application embodiment; as shown Figure 7 As shown in the embodiment of this application, a method for managing a transmission tunnel is provided and applied to a forwarding device, including:

[0287] Step 701: Receive the packet forwarding rules for the path generated by the network controller, and complete the configuration of the packet forwarding rules for the path locally;

[0288] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0289] Specifically, the forwarding devices in the bearer network can be routers or switches. They receive the packet forwarding rules for the path sent by the network controller and complete the relevant configuration locally according to the packet forwarding rules for the path shown.

[0290] Upon receiving a GTP message or a GTP message encapsulated with a tag, the message forwarding rules of the path are followed. The header content of the target message is compared with the matching items in the message forwarding rules of the path. If a match is found, the GTP message is directly encapsulated with a tag, the tag is replaced or deleted, and the message is forwarded to the next hop interface according to the corresponding rules.

[0291] The transmission tunnel management method provided by this invention enables the rapid transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages, thereby simplifying the processing complexity of forwarding devices and reducing data transmission latency.

[0292] Optionally, when the packet forwarding rule of the path is the first packet forwarding rule of the path:

[0293] If the forwarding device is an ingress forwarding device R, the GTP message is encapsulated into a tagged message according to the path tag identifier based on the matching item in the message forwarding rule of the ingress forwarding device R, and the next hop interface is determined.

[0294] If the forwarding device is an egress forwarding device R, the path label identifier is removed to extract the GTP packet and determine the next hop interface based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet.

[0295] If the forwarding device is an intermediate forwarding device R, the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R, the content of the header of the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path, and the next hop interface is determined, or the next hop interface is determined by matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R.

[0296] Specifically, when the user plane path establishment request sent by the SMF includes tunnel information between the two UPFs, the network controller determines the user plane path between the two UPFs based on the tunnel information between the two UPFs in the user plane path establishment request, identifies the path label PLID_i, the first packet forwarding rule of the path, and sends it to each forwarding device on the user plane path. Each forwarding device completes the relevant configuration locally.

[0297] Implement operations such as encapsulating tags, replacing tags, and deleting tags on target packets based on path tag identifiers, and determine the next-hop interface.

[0298] When the user plane path establishment request includes tunnel information between the two UPFs, the first packet forwarding rule of the path used by the forwarding device is the same as the first packet forwarding rule of the path determined by the network controller based on the above request, and the specific related parameters are also the same, so they will not be repeated here.

[0299] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0300] Optionally, when the packet forwarding rule for the path is the second packet forwarding rule for the path:

[0301] If the forwarding device is an ingress forwarding device R, the GTP message is encapsulated into a tagged message according to the path label identifier and QoS label based on the matching items in the message forwarding rules of the ingress forwarding device R, and the next hop interface is determined and QoS control is performed according to the QoS label.

[0302] If the forwarding device is an egress forwarding device R, the path label identifier is removed to extract the GTP packet based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet, and the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet.

[0303] If the forwarding device is an intermediate forwarding device R, the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R, the content of the header of the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path, the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet, or the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R, the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet.

[0304] Specifically, the second packet forwarding rule for the path mainly targets the case where the user plane path establishment request includes tunnel information and QoS information between the two UPFs. When the network controller receives the user plane path establishment request, it generates the corresponding user plane path between the two UPFs, the path label identifier PLID_i, and the second packet forwarding rule for the path.

[0305] This system implements operations such as encapsulating, replacing, and deleting tags on target packets based on path label identifiers and QoS tags, determining the next-hop interface, and performing QoS control according to QoS tags. The ingress forwarding device R refers to the first forwarding device R on which GTP packets are forwarded from the UPF to the bearer network. Conversely, the egress forwarding device R is the last forwarding device R on which tagged packets are forwarded from the UPF to the bearer network. Intermediate forwarding devices are all forwarding devices on the user plane path other than the ingress and egress forwarding devices.

[0306] When the user plane path establishment request includes tunnel information and QoS information between the two UPFs, or when the user plane path establishment request includes tunnel information, QoS flow identifier and QoS information between the two UPFs, the second packet forwarding rule used by the forwarding device is the same as the second packet forwarding rule determined by the network controller based on the above request, and the specific related parameters are also the same, which will not be repeated here.

[0307] The transmission tunnel management method provided in this application enables fast transmission of GTP messages in the bearer network by directly encapsulating GTP messages into tagged messages in the bearer network, which simplifies the processing complexity of forwarding devices and reduces data transmission latency.

[0308] Optionally, receive an update packet forwarding rule request sent by the network controller, which includes packet forwarding rules for paths with new QoS labels, and update the QoS labels in the packet forwarding rules for the paths locally;

[0309] Based on the new QoS label carried by the packet forwarding rules of the path, QoS control of the target packet is performed.

[0310] Specifically, each forwarding device receives an update message forwarding rule request sent by the network controller, which includes forwarding rules for messages along the path with the new QoS label. Each forwarding device then updates the QoS label in the forwarding rules for the corresponding path of the message based on the new QoS label.

[0311] When the target packet is transmitted between various forwarding devices, QoS control of the target packet is performed according to the new QoS label.

[0312] The transmission tunnel management method provided in this application update the corresponding QoS label through a user plane modification request. Each forwarding device obtains the updated QoS label and completes the update process locally. This enables the target packet to be forwarded according to the packet forwarding rules of the latest path and to perform QoS control on the target packet according to the updated QoS label.

[0313] Optionally, receive a deletion command sent by the network controller, which includes the user plane path to be deleted;

[0314] Based on the deletion instruction and the correspondence between the user plane path and the packet forwarding rules of the path, delete the corresponding packet forwarding rules of the path stored locally.

[0315] Specifically, when each forwarding device receives a deletion command from the network controller, it determines the packet forwarding rules for the corresponding path based on the user plane path information carried, ensuring the synchronization of information between the network controller and each routing and forwarding device, and deleting the interrelated information.

[0316] The transmission tunnel management method provided in this application sends a deletion command through the controller, including the deletion of the user plane path, to ensure the synchronization of information between the network controller and each routing device, thereby improving the resource utilization of each device and the effectiveness of information storage.

[0317] The technical solution of the present invention will be specifically described below, taking the case where the mapping relationship between QoS indication and bearer network layer QoS label (QoS level in bearer network) is configured locally at the network controller in advance.

[0318] QoS indication QoS tag n N1 m N2 ...... ......

[0319] In the table above, n, m, N1, and N2 represent any positive values, indicating the correspondence between QoS indicators and QoS tags. Different QoS indicators may correspond to the same QoS tag or different QoS tags. The QoS indicators mentioned above are not limited to 5QI, ToS, Traffic Class, Service Class Indicator, etc.

[0320] The signaling interaction between SMF and network controller is based on the mapping relationship between QoS indication and bearer layer QoS label configured in the network controller.

[0321] Figure 8 This is one of the flowcharts for establishing a user plane path provided in the embodiments of this application; such as Figure 8 As shown, the specific steps include:

[0322] Step 801: The SMF sends a User Plane Path Establishment Request to the Network Controller, carrying the following information: tunnel information or tunnel information, QoS Flow Identifier (QFI) and QoS information or tunnel information and QoS information. The tunnel information includes: the address and tunnel endpoint identifier of the first UPF, and the address and tunnel endpoint identifier of the second UPF. The QoS information is: a QoS indicator corresponding to the tunnel or QoS flow, wherein the QoS indicator is 5QI, ToS, Traffic Class, or Service ClassIndicator.

[0323]

[0324]

[0325] Step 802: If the request message carries QoS information, the network controller determines the bearer network QoS label corresponding to the QoS indication based on the locally configured QoS indication and QoS label mapping relationship. Based on the tunnel information at both ends and the corresponding QoS labels, the network controller determines whether to select the bearer network user plane path between the two UPFs, determine the path label identifier PLID_i, and generate the packet forwarding rules for each router / switch on the path, or determines that the user plane path establishment has failed.

[0326] Tunnel-related information QoS indication QoS tag (S-UPF1 IP, S-UPF1 TEID) or n N1 (S-UPF2 IP, S-UPF2 TEID) or n N1 (S-UPF1 IP, S-UPF1 TEID, QFI_j) m N2 (S-UPF2 IP, S-UPF2 TEID, QFI_j) m N2

[0327] If the request message does not contain a QoS label, the network controller determines, based on the tunnel information at both ends, the bearer network user plane path between the two UPFs, the path label identifier PLID_i, and the packet forwarding rules for each router / switch on the path, or determines that the user plane path establishment has failed.

[0328] Packet forwarding rules for ingress forwarding device R:

[0329]

[0330] That is, the message forwarding rules of the outgoing forwarding device R:

[0331]

[0332] The packet forwarding rules of intermediate forwarding device R include two cases:

[0333] Scenario 1:

[0334]

[0335] Scenario 2:

[0336]

[0337] When the packet forwarding rule of intermediate forwarding device R is Case 2, the matching items of the corresponding egress forwarding device R and intermediate forwarding device R are the same as the path label identifier encapsulated by the ingress forwarding device R.

[0338] Step 803: The network controller sends a packet forwarding rule configuration request, carrying the generated packet forwarding rule or the generated packet forwarding rule and QoS label.

[0339] Step 804: After configuring the packet forwarding rules, send a response to the network controller.

[0340] Step 805: After receiving the response indicating that the packet forwarding rules have been configured, the network controller sends a user plane path establishment response to the SMF.

[0341] Figure 9 This is one of the flowcharts for user plane path modification provided in the embodiments of this application; such as Figure 9 As shown, the signaling interaction between the SMF and the network controller—user plane path modification—involves the following steps:

[0342] Step 901: When the QoS of a session needs to be modified, the SMF sends a user plane path modification request to the controller, carrying the following information: tunnel information, QoS flow identifier and QoS information, or tunnel information and QoS information.

[0343] Tunnel-related information QoS indication (S-UPF1 IP, S-UPF1 TEID) m (S-UPF2 IP, S-UPF2 TEID) m (S-UPF1 IP, S-UPF1 TEID, QFI_j) n (S-UPF2 IP, S-UPF2 TEID, QFI_j) n

[0344] Step 902: The network controller determines the bearer network QoS label corresponding to the QoS indicator based on the locally configured QoS indicator-QoS label mapping relationship.

[0345] Tunnel-related information QoS indication QoS tag (S-UPF1 IP, S-UPF1 TEID) m N2 (S-UPF2 IP, S-UPF2 TEID) m N2 (S-UPF1 IP, S-UPF1 TEID, QFI_j) n N1 (S-UPF2 IP, S-UPF2 TEID, QFI_j) n N1

[0346] Secondly, the network controller determines the QoS tag value in the packet forwarding rules of the ingress forwarding device based on the tunnel information at both ends and the corresponding QoS tags.

[0347] Packet forwarding rules for ingress forwarding devices:

[0348]

[0349] Step 903: The network controller sends an update packet forwarding rule request to the forwarding device, carrying the updated packet forwarding rules and QoS tags.

[0350] Step 904: After updating the packet forwarding rules, the forwarding device sends a response to the network controller.

[0351] Step 905: After receiving the response from the forwarding device, the network controller sends a user plane path modification response to the SMF.

[0352] Figure 10 This is one of the flowcharts for deleting user plane paths provided in the embodiments of this application; such as Figure 10 As shown, the signaling interaction between the SMF and the network controller—user plane path deletion—involves the following steps:

[0353] Step 1001: When a user plane path needs to be deleted, the SMF sends a user plane path deletion request to the network controller, carrying tunnel information, namely S-UPF1 IP, S-UPF1TEID, S-UPF2 IP, and S-UPF2 TEID in the diagram.

[0354] Steps 1002-1004: The network controller determines to delete the user plane path based on the tunnel information carried in the above request information, sends an instruction to the forwarding device to delete the corresponding user plane packet forwarding rule, and then sends a response to the SMF.

[0355] The technical solution of the present invention will be specifically explained below by taking the case where the mapping relationship between QoS indication and bearer network layer QoS label (QoS level in bearer network) is configured locally at the SMF in advance.

[0356] QoS indication QoS tag n N1 m N2 ...... ......

[0357] In the table above, n, m, N1, and N2 represent any positive values, indicating the correspondence between QoS indicators and QoS tags. Different QoS indicators may correspond to the same QoS tag or different QoS tags. The QoS indicators mentioned above are not limited to 5QI, ToS, Traffic Class, Service Class Indicator, etc.

[0358] Based on the mapping relationship between QoS indications and bearer layer QoS labels configured at the SMF, signaling interaction between the SMF and the network controller is achieved.

[0359] Figure 11 This is the second flowchart of user plane path establishment provided in the embodiments of this application; as follows: Figure 11 As shown, the signaling interaction between the SMF and the network controller—user plane path establishment—involves the following steps:

[0360] Step 1101: If QoS control of the packets is required, the SMF determines the bearer layer QoS label based on the mapping relationship between the locally configured QoS indication and the bearer layer QoS label (QoS level in the bearer network). Then, it sends a user plane path establishment request to the network controller, carrying the following information: tunnel information, QoS flow identifier, and bearer layer QoS label; or tunnel information and bearer layer QoS label.

[0361] Tunnel-related information QoS tag (S-UPF1 IP, S-UPF1 TEID) N1 (S-UPF2 IP, S-UPF2 TEID) N1 (S-UPF1 IP, S-UPF1 TEID, QFI_j) N2 (S-UPF2 IP, S-UPF2 TEID, QFI_j) N2

[0362] If QoS control of the packets is not required, the SMF sends a user plane path establishment request to the network controller, which carries the following information: tunnel information.

[0363] Step 1102: If the request message carries a QoS label, the network controller determines, based on the tunnel information and QoS label between the two UPFs, the bearer network user plane path to be selected between the two UPFs, the path label identifier PLID_i, and the packet forwarding rules for each router / switch on the path, or determines that the user plane path establishment has failed.

[0364] If the request message does not contain a QoS label, the network controller determines, based on the tunnel information at both ends, the bearer network user plane path between the two UPFs, the path label identifier PLID_i, and the packet forwarding rules for each router / switch on the path, or determines that the user plane path establishment has failed.

[0365] Packet forwarding rules for ingress forwarding device R:

[0366]

[0367] Message forwarding rules for egress forwarding device R:

[0368]

[0369] The packet forwarding rules of intermediate forwarding device R correspond to two cases:

[0370] Scenario 1:

[0371]

[0372] Scenario 2:

[0373]

[0374] Step 1103: The network controller sends a packet forwarding rule configuration request, carrying the generated packet forwarding rule or the generated packet forwarding rule and QoS.

[0375] Step 1104: After configuring the packet forwarding rules, send a response to the network controller.

[0376] Step 1105: After receiving the response indicating that the packet forwarding rules have been configured, the network controller sends a user plane path establishment response to the SMF.

[0377] Figure 12 This is the second flowchart of user plane path modification provided in the embodiments of this application; as follows: Figure 12 As shown, the signaling interaction between the SMF and the network controller—user plane path modification—involves the following steps:

[0378] Step 1201: When the QoS of a session needs to be modified, the SMF sends a user plane path modification request, carrying information such as tunnel information, QoS flow identifier and QoS tag or tunnel information and QoS tag.

[0379] Tunnel-related information QoS tag (S-UPF1 IP, S-UPF1 TEID) N2 (S-UPF2 IP, S-UPF2 TEID) N2 (S-UPF1 IP, S-UPF1 TEID, QFI_j) N1 (S-UPF2 IP, S-UPF2 TEID, QFI_j) N1

[0380] Step 1202: The network controller determines the QoS tag value in the update packet forwarding rule based on the tunnel information at both ends and the corresponding QoS tags.

[0381] Packet forwarding rules for ingress forwarding devices:

[0382]

[0383] Step 1203: The network controller sends an update message forwarding rule request to the forwarding device, carrying the updated QoS label.

[0384] Step 1204: After updating the packet forwarding rules, the forwarding device sends a response to the network controller.

[0385] Step 1205: After receiving the response from the forwarding device, the network controller sends a user plane path modification response to the SMF.

[0386] Figure 13 This is the second flowchart of user plane path deletion provided in the embodiments of this application; as follows: Figure 13 As shown, the signaling interaction between the SMF and the network controller—user plane path deletion—involves the following steps:

[0387] Step 1301: When a user plane path needs to be deleted, the SMF sends a user plane path deletion request to the network controller, carrying tunnel information, namely S-UPF1 IP, S-UPF1TEID, S-UPF2 IP, and S-UPF2 TEID in the diagram.

[0388] Steps 1302-1304: The network controller determines to delete the user plane path based on the tunnel information carried in the above request information, sends an instruction to the forwarding device to delete the corresponding user plane packet forwarding rule, and then sends a response to the SMF.

[0389] Figure 14 This is a schematic diagram of the structure of the network controller electronic device provided in the embodiments of this application, such as... Figure 14 As shown, the network controller electronic device includes a memory 1420, a transceiver 1410, and a processor 1400; wherein the processor 1400 and the memory 1420 can also be physically arranged separately.

[0390] The memory 1420 is used to store computer programs; the transceiver 1410 is used to send and receive data under the control of the processor 1400.

[0391] Specifically, transceiver 1410 is used to receive and send data under the control of processor 1400.

[0392] Among them, Figure 14 In this application, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1400 and memory represented by memory 1420 together. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 1410 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0393] The processor 1400 is responsible for managing the bus architecture and general processing, while the memory 1420 can store the data used by the processor 1400 when performing operations.

[0394] The processor 1400 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0395] The processor 1400 executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling the computer program stored in the memory 1420. For example:

[0396] Receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs;

[0397] Based on the tunnel information between the two UPFs carried in the user plane path establishment request, determine the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs.

[0398] Send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path;

[0399] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0400] Optionally, the determined packet forwarding rule for the path is the first packet forwarding rule for the path, which specifically includes:

[0401] If the forwarding device R is an ingress forwarding device R, the first packet forwarding rule of the path includes: determining to encapsulate the GTP packet into a tagged packet according to the path tag identifier based on the matching item in the packet forwarding rule of the ingress forwarding device R, and determining the next hop interface;

[0402] If the forwarding device R is an egress forwarding device R, the first packet forwarding rule of the path includes: removing the path label identifier to extract the GTP packet and determining the next hop interface based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header in the label packet.

[0403] If the forwarding device R is an intermediate forwarding device R, the first packet forwarding rule of the path includes: matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, replacing the content of the header of the label packet with the path label identifier corresponding to the next hop in the user plane path, and determining the next hop interface, or matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, and determining the next hop interface.

[0404] Optionally, the user plane path establishment request may also include QoS information, which may be a QoS indication or a QoS tag.

[0405] Alternatively, the user plane path establishment request may also include a QoS flow identifier and QoS information, wherein the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0406] Optionally, the step of determining the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request includes:

[0407] The target QoS label is determined based on the QoS indication carried in the user plane path establishment request and the mapping relationship between the QoS indication and the QoS label stored locally, or based on the QoS label carried in the user plane path establishment request.

[0408] Optionally, the step of determining the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request includes:

[0409] Based on the tunnel information between the two UPFs carried in the user plane path establishment request and the target QoS label, a user plane path, path label identifier, and second packet forwarding rule for a session between the two UPFs are determined.

[0410] Optionally, the second message forwarding rule for the path includes:

[0411] If the forwarding device R is an ingress forwarding device R, the second packet forwarding rule of the path includes: matching the content of the header in the GTP packet with the matching item in the packet forwarding rule of the ingress forwarding device R, determining to encapsulate the GTP packet into a tagged packet according to the path label identifier and the QoS label, and determining the next hop interface and performing QoS control according to the QoS label;

[0412] If the forwarding device R is an egress forwarding device R, the second packet forwarding rule of the path includes: removing the path label identifier to extract the GTP packet based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet; determining the next hop interface; and performing QoS control according to the QoS label in the header of the label packet.

[0413] If the forwarding device R is an intermediate forwarding device R, the second packet forwarding rule of the path includes: matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, replacing the content of the header of the label packet with the path label identifier corresponding to the next hop in the user plane path, determining the next hop interface and performing QoS control according to the QoS label in the header of the label packet, or matching the content of the header of the label packet with the matching item in the packet forwarding rule of the intermediate forwarding device R, determining the next hop interface and performing QoS control according to the QoS label in the header of the label packet.

[0414] Optionally, the QoS indicator may include: 5QI, Tos, Traffic Class, or Service ClassIndicator.

[0415] Optionally, the steps further include:

[0416] Receive a user plane path modification request sent by the Session Management Function Entity (SMF), wherein the user plane path modification request includes tunnel information and QoS information between the two UPFs;

[0417] Based on the user plane path modification request, determine the target QoS label corresponding to the QoS information;

[0418] Based on the target QoS label, update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R;

[0419] Send the updated second message forwarding rule for the path to the ingress forwarding device R on the user plane path;

[0420] The updated second packet forwarding rule of the path is used to perform QoS control on the target packet according to the target QoS label, wherein the target packet is a GTP packet or a GTP packet encapsulated with a label.

[0421] Optionally, if the user plane path modification request includes tunnel information and QoS information between the two UPFs, the QoS information is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs.

[0422] Alternatively, if the user plane path modification request includes tunnel information between the two UPFs, a QoS flow identifier, and QoS information, then the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0423] Optionally, determining the target QoS tag corresponding to the QoS information based on the user plane path modification request includes:

[0424] The target QoS label is determined based on the QoS indication in the user plane path modification request, the mapping relationship between the locally configured QoS indication and QoS label, or based on the QoS label carried in the user plane path modification request.

[0425] Optionally, the steps further include:

[0426] Receive a user plane path deletion request sent by the Session Management Function Entity (SMF), wherein the user plane path deletion request includes tunnel information between the two UPFs;

[0427] Based on the tunnel information between the two UPFs carried in the user plane path deletion request, the user plane path to be deleted is determined, and an instruction is sent to all forwarding devices R on the user plane path to delete the packet forwarding rules of the corresponding path.

[0428] Figure 15 This is a schematic diagram of the structure of the Session Management Function (SMF) electronic device provided in the embodiments of this application, as shown below. Figure 15 As shown, the SMF electronic device includes a memory 1520, a transceiver 1510, and a processor 1500; wherein the processor 1500 and the memory 1520 can also be physically arranged separately.

[0429] The memory 1520 is used to store computer programs; the transceiver 1510 is used to send and receive data under the control of the processor 1500.

[0430] Specifically, transceiver 1510 is used to receive and send data under the control of processor 1500.

[0431] Among them, Figure 15In this application, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1500 and memory represented by memory 1520 together. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 1510 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0432] The processor 1500 is responsible for managing the bus architecture and general processing, while the memory 1520 can store the data used by the processor 1500 when performing operations.

[0433] The processor 1500 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.

[0434] The processor 1500 executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling the computer program stored in the memory 1520. For example:

[0435] Send a user plane path establishment request to the network controller, the user plane path establishment request including tunnel information between the two UPFs;

[0436] The tunnel information between the two UPFs is used to determine the packet forwarding rules for the path between the two UPFs. The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels for GTP packets and forwarding them to the next-hop interface under the condition of satisfying the matching items.

[0437] Optionally, the user plane path establishment request may also include QoS information, which is a QoS indication or QoS tag corresponding to the tunnel information between the two UPFs;

[0438] Alternatively, the user plane path establishment request may also include a QoS flow identifier and QoS information, wherein the QoS information is a QoS indication or QoS tag corresponding to the QoS flow identifier.

[0439] Optionally, the QoS label is determined based on the mapping relationship between locally configured QoS indications and QoS labels.

[0440] Optionally, the steps further include:

[0441] Send a user plane path modification request to the network controller. The user plane path modification request includes tunnel information and QoS information between the two UPFs, or tunnel information and QoS label between the two UPFs. It is used to update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R according to the target QoS label, so that the ingress forwarding device R performs QoS control on the target packet according to the updated QoS label in the first forwarding rule of the path.

[0442] The target QoS label is a QoS label determined based on the QoS information and the pre-configured mapping relationship between QoS indication and QoS label, or a QoS label carried in the user plane path modification request. The QoS information is a QoS indication corresponding to the tunnel information between the two UPFs.

[0443] Optionally, the steps further include:

[0444] Send a user plane path establishment request to the network controller. The user plane path establishment request includes tunnel information between the two UPFs, QoS flow identifier and QoS information, or tunnel information between the two UPFs, QoS flow identifier and QoS label. This is used to update the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R according to the target QoS label, so that the ingress forwarding device R performs QoS control on the target packet according to the updated QoS label in the second forwarding rule of the path.

[0445] The target QoS label is a QoS label determined based on the QoS information and the mapping relationship between the pre-configured QoS indication and the QoS label, or a QoS label carried in the user plane path modification request. The QoS information is a QoS indication corresponding to the QoS flow identifier.

[0446] Optionally, the steps further include:

[0447] Send a user plane path deletion request to the network controller. The user plane path deletion request includes tunnel information between the two UPFs and is used to delete the packet forwarding rules of the user plane path and all forwarding devices R on the user plane path.

[0448] The deleted user plane path is determined by the network controller based on the tunnel information between the two UPFs carried in the user plane path deletion request, and there is a one-to-one correspondence between the user plane path and the packet forwarding rules of the path on the user plane path.

[0449] Figure 16 The structural schematic diagram of the forwarding electronic device provided in the embodiments of this application is as follows: Figure 16As shown, the forwarding electronic device includes a memory 1620, a transceiver 1610, and a processor 1600; wherein the processor 1600 and the memory 1620 can also be physically arranged separately.

[0450] The memory 1620 is used to store computer programs; the transceiver 1610 is used to send and receive data under the control of the processor 1600.

[0451] Specifically, transceiver 1610 is used to receive and send data under the control of processor 1600.

[0452] Among them, Figure 16 In this application, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 1600 and memory represented by memory 1620 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 1610 can be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0453] The processor 1600 is responsible for managing the bus architecture and general processing, while the memory 1620 can store the data used by the processor 1600 during operation.

[0454] The processor 1600 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.

[0455] The processor 1600 executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling the computer program stored in the memory 1620, for example:

[0456] Receive the packet forwarding rules for the path generated by the network controller, and complete the configuration of the packet forwarding rules for the path locally;

[0457] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0458] Optionally, when the packet forwarding rule of the path is the first packet forwarding rule of the path:

[0459] If the forwarding device is an ingress forwarding device R, the GTP message is encapsulated into a tagged message according to the path tag identifier based on the matching item in the message forwarding rule of the ingress forwarding device R, and the next hop interface is determined.

[0460] If the forwarding device is an egress forwarding device R, the path label identifier is removed to extract the GTP packet and determine the next hop interface based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet.

[0461] If the forwarding device is an intermediate forwarding device R, the header content of the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path, based on the matching items in the header content of the label packet and the packet forwarding rules of the intermediate forwarding device R. The next hop interface is then determined, or the next hop interface is determined based on the matching items in the header content of the label packet and the packet forwarding rules of the intermediate forwarding device R. Optionally, when the packet forwarding rule of the path is the second packet forwarding rule of the path:

[0462] If the forwarding device is an ingress forwarding device R, the GTP message is encapsulated into a tagged message according to the path label identifier and QoS label based on the matching items in the message forwarding rules of the ingress forwarding device R, and the next hop interface is determined and QoS control is performed according to the QoS label.

[0463] If the forwarding device is an egress forwarding device R, the path label identifier is removed to extract the GTP packet based on the matching item in the packet forwarding rule of the egress forwarding device R according to the content of the header of the label packet, and the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet.

[0464] If the forwarding device is an intermediate forwarding device R, the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R, the content of the header of the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path, the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet, or the content of the header of the label packet is matched with the matching item in the packet forwarding rule of the intermediate forwarding device R, the next hop interface is determined and QoS control is performed according to the QoS label in the header of the label packet.

[0465] Optionally, the steps further include:

[0466] Receive an update packet forwarding rule request sent by the network controller, which includes packet forwarding rules for paths with new QoS labels, and update the QoS labels in the packet forwarding rules for the paths locally;

[0467] Based on the new QoS label carried by the packet forwarding rules of the path, QoS control is performed on the GTP packet or the GTP packet after encapsulation label.

[0468] Optionally, the steps further include:

[0469] Receive a deletion command from the network controller, which includes the user plane path to be deleted;

[0470] Based on the deletion instruction and the correspondence between the user plane path and the packet forwarding rules of the path, delete the corresponding packet forwarding rules of the path stored locally.

[0471] It should be noted that the network controller electronic device, SMF electronic device and forwarding electronic device provided in the embodiments of this application can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0472] Figure 17 This is a schematic diagram of the network controller device provided in the embodiments of this application, as shown below. Figure 17 As shown, the device includes:

[0473] The first receiving module 1701 is used to receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs.

[0474] The first determining module 1702 is used to determine the user plane path, path label identifier, and packet forwarding rules of a session between the two UPFs based on the tunnel information between the two UPFs carried in the user plane path establishment request.

[0475] The first sending module 1703 is used to send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path;

[0476] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0477] Figure 18 This is a schematic diagram of the network-side device of the Session Management Function (SMF) device provided in the embodiments of this application, as shown below. Figure 18 As shown, the device includes:

[0478] The second sending module 1801 is used to send a user plane path establishment request to the network controller, wherein the user plane path establishment request includes tunnel information between the two UPFs.

[0479] The tunnel information between the two UPFs is used to determine the packet forwarding rules for the path between the two UPFs. The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels for GTP packets and forwarding them to the next-hop interface under the condition of satisfying the matching items.

[0480] Figure 19 This is a schematic diagram of the structure of the forwarding device provided in the embodiments of this application, such as... Figure 19 As shown, the forwarding device includes:

[0481] The third receiving module 1901 is used to receive the packet forwarding rules of the path generated by the network controller and to complete the configuration of the packet forwarding rules of the path locally.

[0482] The packet forwarding rules for the path are used to limit the rules for directly encapsulating labels, replacing labels, or deleting labels in GTP packets and forwarding them to the next-hop interface under the condition that the matching conditions are met.

[0483] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0484] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0485] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0486] On the other hand, the present invention also provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, which, when executed by a computer, enable the computer to perform the steps of the transmission tunnel management methods provided by the above methods, applied to a network controller, for example including:

[0487] Receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs;

[0488] Based on the tunnel information between the two UPFs carried in the user plane path establishment request, determine the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs.

[0489] Send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path, so that the forwarding devices R forward the target packet according to the packet forwarding rules of the path.

[0490] The target message is a GTP message or a GTP message encapsulated with a label. The path label identifier is used to encapsulate the GTP message into a labeled message. The message forwarding rules of the path are used to limit the rules for encapsulating the GTP message with a label, replacing the label or deleting the label, and forwarding it to the next hop interface under the condition of satisfying the matching item.

[0491] On the other hand, the present invention also provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, which, when executed by a computer, enable the computer to perform the steps of the transmission tunnel management method provided by the above methods, applied to a Session Management Function (SMF) entity, for example including:

[0492] Send a user plane path establishment request to the network controller, the user plane path establishment request including tunnel information between the two UPFs;

[0493] The network controller receives a response message indicating that it has determined a user plane path for a session between two UPFs, a path label identifier, and a packet forwarding rule for the path, and that all forwarding devices R on the user plane path have completed the configuration of the packet forwarding rule for the path, so that the forwarding devices R forward the target packet according to the packet forwarding rule for the path.

[0494] The target message is a GTP message or a GTP message encapsulated with a label. The path label identifier is used to encapsulate the GTP message into a labeled message. The message forwarding rules of the path are used to limit the rules for encapsulating the GTP message with a label, replacing the label or deleting the label, and forwarding it to the next hop interface under the condition of satisfying the matching item.

[0495] On the other hand, the present invention also provides a computer program product, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, which, when executed by a computer, enable the computer to perform the steps of the transmission tunnel management method provided by the above methods, applied to a forwarding device, for example including:

[0496] Receive the packet forwarding rules for the path generated by the network controller, and complete the configuration of the packet forwarding rules for the path locally;

[0497] Based on the packet forwarding rules of the aforementioned path, the target packet is forwarded.

[0498] The target message is a GTP message or a GTP message encapsulated with a label. The message forwarding rules of the path are used to limit the rules for encapsulating a label, replacing a label, or deleting a label on the GTP message and forwarding it to the next-hop interface under the condition that the matching conditions are met.

[0499] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the transmission tunnel management method provided in the above embodiments, such as including:

[0500] Receive a user plane path establishment request sent by the Session Management Function Entity (SMF), wherein the user plane path establishment request contains tunnel information between the two UPFs;

[0501] Based on the tunnel information between the two UPFs carried in the user plane path establishment request, determine the user plane path, path label identifier, and packet forwarding rules for a session between the two UPFs.

[0502] Send a packet forwarding rule configuration request carrying the packet forwarding rules of the path to all forwarding devices R on the user plane path, so that the forwarding devices R forward the target packet according to the packet forwarding rules of the path.

[0503] The target message is a GTP message or a GTP message encapsulated with a label. The path label identifier is used to encapsulate the GTP message into a labeled message. The message forwarding rules of the path are used to limit the rules for encapsulating the GTP message with a label, replacing the label or deleting the label, and forwarding it to the next hop interface under the condition of satisfying the matching item.

[0504] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the transmission tunnel management method provided in the above embodiments, such as including:

[0505] Send a user plane path establishment request to the network controller, the user plane path establishment request including tunnel information between the two UPFs;

[0506] The network controller receives a response message indicating that it has determined a user plane path for a session between two UPFs, a path label identifier, and a packet forwarding rule for the path, and that all forwarding devices R on the user plane path have completed the configuration of the packet forwarding rule for the path, so that the forwarding devices R forward the target packet according to the packet forwarding rule for the path.

[0507] The target message is a GTP message or a GTP message encapsulated with a label. The path label identifier is used to encapsulate the GTP message into a labeled message. The message forwarding rules of the path are used to limit the rules for encapsulating the GTP message with a label, replacing the label or deleting the label, and forwarding it to the next hop interface under the condition of satisfying the matching item.

[0508] On the other hand, embodiments of this application also provide a processor-readable storage medium storing a computer program for causing the processor to execute the transmission tunnel management method provided in the above embodiments, such as including:

[0509] Receive the packet forwarding rules for the path generated by the network controller, and complete the configuration of the packet forwarding rules for the path locally;

[0510] Based on the packet forwarding rules of the aforementioned path, the target packet is forwarded.

[0511] The target message is a GTP message or a GTP message encapsulated with a label. The message forwarding rules of the path are used to limit the rules for encapsulating a label, replacing a label, or deleting a label on the GTP message and forwarding it to the next-hop interface under the condition that the matching conditions are met.

[0512] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).

[0513] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0514] The network-side equipment involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in the access network that communicates with wireless terminal devices through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0515] The terminal involved in the embodiments of this application can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The name of the terminal may differ in different systems; for example, in a 5G system, the terminal can be called a user terminal or user equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a radio access network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the radio access network. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0516] Network devices and terminals can each use one or more antennas for Multiple-Input Multiple-Output (MIMO) transmission. MIMO transmission can be Single-User MIMO (SU-MIMO) or Multiple-User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0517] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0518] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0519] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0520] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0521] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method of managing a transmission tunnel, characterized by, Applied to a network controller, comprising: Receiving a user plane path establishment request sent by a session management function entity SMF, wherein the user plane path establishment request contains tunnel information between two UPFs; Based on the tunnel information between the two UPFs carried in the user plane path establishment request, determining the user plane path of one session between the two UPFs, the path label identifier, and the message forwarding rule of the path; Sending a message forwarding rule configuration request carrying the message forwarding rule of the path to all forwarding devices R on the user plane path; Wherein, the message forwarding rule of the path is used to limit the rule that under the condition of meeting the matching item, the label is directly encapsulated on the GTP message by the entry forwarding device R, the label is replaced by the intermediate forwarding device R or the label is deleted by the exit forwarding device R, and then forwarded to the next hop interface.

2. The management method of a transmission tunnel according to claim 1, characterized in that, The determined message forwarding rule of the path is the first message forwarding rule of the path, and the first message forwarding rule of the path specifically includes: If the forwarding device R is an entry forwarding device R, the first message forwarding rule of the path includes: determining that the GTP message is encapsulated into a label message according to the content of the header in the GTP message and the matching item in the message forwarding rule of the entry forwarding device R, and determining the next hop interface; If the forwarding device R is an exit forwarding device R, the first message forwarding rule of the path includes: removing the path label identifier from the label message to extract the GTP message according to the content of the header in the label message and the matching item in the message forwarding rule of the exit forwarding device R, and determining the next hop interface; If the forwarding device R is an intermediate forwarding device R, the first message forwarding rule of the path includes: replacing the header content in the label message with the path label identifier corresponding to the next hop in the user plane path according to the content of the header in the label message and the matching item in the message forwarding rule of the intermediate forwarding device R, and determining the next hop interface or determining the next hop interface according to the content of the header in the label message and the matching item in the message forwarding rule of the intermediate forwarding device R.

3. The management method of a transmission tunnel according to claim 1, characterized in that, The user plane path establishment request further includes QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the tunnel information between the two UPFs; Or, the user plane path establishment request further includes a QoS flow identifier and QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the QoS flow identifier.

4. The management method of a transmission tunnel according to claim 3, characterized in that, Before the determination of the user plane path of one session between the two UPFs, the path label identifier, and the message forwarding rule of the path based on the tunnel information between the two UPFs carried in the user plane path establishment request, further includes: Based on the QoS indication carried in the user plane path establishment request and the mapping relationship between the QoS indication and the QoS label stored locally, or based on the QoS label carried in the user plane path establishment request, determining the target QoS label.

5. The management method of a transmission tunnel according to claim 4, characterized in that, The tunnel information between the two UPFs carried in the user plane path establishment request is used to determine a user plane path, a path label, and a packet forwarding rule of a session between the two UPFs. The tunnel information between the two UPFs carried in the user plane path establishment request and the target QoS label are used to determine a user plane path, a path label, and a second packet forwarding rule of a session between the two UPFs.

6. The management method of a transmission tunnel according to claim 5, characterized in that, The second packet forwarding rule of the path includes: If the forwarding device R is an ingress forwarding device R, the second packet forwarding rule of the path includes: determining that a GTP packet is encapsulated into a label packet according to the matching between the content of the header in the GTP packet and the matching item in the packet forwarding rule of the ingress forwarding device R, and determining a next hop interface and performing QoS control according to the QoS label; If the forwarding device R is an egress forwarding device R, the second packet forwarding rule of the path includes: removing the path label and extracting a GTP packet according to the matching between the content of the header in the label packet and the matching item in the packet forwarding rule of the egress forwarding device R, and determining a next hop interface and performing QoS control according to the QoS label in the header of the label packet; If the forwarding device R is an intermediate forwarding device R, the second packet forwarding rule of the path includes: replacing the content of the header in the label packet with the path label corresponding to the next hop in the user plane path according to the matching between the content of the header in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R, and determining a next hop interface and performing QoS control according to the QoS label in the header of the label packet, or determining a next hop interface and performing QoS control according to the QoS label in the header of the label packet according to the matching between the content of the header in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R.

7. The management method of a transmission tunnel according to claim 3 or 4, characterized in that, The QoS indication includes: 5QI, Tos, Traffic Class, or Service Class Indicator.

8. The management method of a transmission tunnel according to claim 1, characterized in that, The method further includes: receiving a user plane path modification request sent by the session management function entity SMF, the user plane path modification request including tunnel information and QoS information between the two UPFs; determining a target QoS label corresponding to the QoS information according to the user plane path modification request; updating the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R based on the target QoS label; sending the updated second packet forwarding rule of the path to the ingress forwarding device R on the user plane path; The updated second packet forwarding rule of the path is used to perform QoS control on a target packet according to the target QoS label, and the target packet is a GTP packet or a GTP packet encapsulated with a label.

9. The management method of a transmission tunnel according to claim 8, characterized in that, In a case where the user plane path modification request includes the tunnel information between the two UPFs and the QoS information, the QoS information is a QoS indication or a QoS label corresponding to the tunnel information between the two UPFs. Or, in a case where the user plane path modification request includes the tunnel information between the two UPFs, a QoS flow identifier, and the QoS information, the QoS information is a QoS indication or a QoS label corresponding to the QoS flow identifier.

10. The management method of a transmission tunnel according to claim 9, characterized in that, The determining, according to the user plane path modification request, of the target QoS label corresponding to the QoS information includes: determining the target QoS label based on a QoS indication in the user plane path modification request and a mapping relationship between a locally configured QoS indication and a QoS label, or based on a QoS label carried in the user plane path modification request.

11. The management method of a transmission tunnel according to claim 1, characterized in that, The method further includes: receiving a user plane path deletion request sent by the session management function entity SMF, the user plane path deletion request including tunnel information between two UPFs; determining a deleted user plane path according to the tunnel information between the two UPFs carried in the user plane path deletion request, and sending an instruction to all forwarding devices R on the user plane path for deleting a corresponding path message forwarding rule.

12. A method of managing a transmission tunnel, characterized by, Applied to a session management function entity SMF, including: sending a user plane path establishment request to a network controller, the user plane path establishment request including tunnel information between two UPFs; The tunnel information between the two UPFs is used to determine a path message forwarding rule of a path between the two UPFs, and the path message forwarding rule is used to limit a rule that, under a condition of meeting a matching item, a GTP message is directly encapsulated with a label by an entry forwarding device R, an intermediate forwarding device R replaces the label or an exit forwarding device R deletes the label, and is forwarded to a next hop interface.

13. The management method of a transmission tunnel according to claim 12, characterized in that, The user plane path establishment request further includes QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the tunnel information between the two UPFs. Or, the user plane path establishment request further includes a QoS flow identifier and QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the QoS flow identifier.

14. The management method of a transmission tunnel according to claim 13, characterized in that, The QoS label is determined based on a mapping relationship between a locally configured QoS indication and a QoS label.

15. The management method of a transmission tunnel according to claim 12, characterized in that, The method further includes: sending a user plane path modification request to a network controller, the user plane path modification request including tunnel information between two UPFs and QoS information, or tunnel information between the two UPFs and a QoS label, for updating a QoS label in a second path message forwarding rule corresponding to an entry forwarding device R according to a target QoS label, so that the entry forwarding device R performs QoS control on a target message according to the updated QoS label in the second forwarding rule of the path; The target QoS label is a QoS label determined based on the QoS information and a preconfigured mapping relationship between a QoS indication and a QoS label, or is a QoS label carried in the user plane path modification request, and the QoS information is a Qos indication corresponding to tunnel information between two UPFs.

16. The management method of a transmission tunnel according to claim 12, characterized in that, The method further includes: sending, to a network controller, a user plane path modification request, the user plane path modification request including tunnel information between two UPFs, QoS flow identification and QoS information, or tunnel information between two UPFs, QoS flow identification and a QoS label, for updating a QoS label in a second packet forwarding rule of a path corresponding to an entry forwarding device R according to a target QoS label, so that the entry forwarding device R performs QoS control on a target packet according to the updated QoS label in the second forwarding rule of the path. The target QoS label is a QoS label determined based on the QoS information and a preconfigured mapping relationship between a QoS indication and a QoS label, or is a QoS label carried in the user plane path modification request, and the QoS information is a Qos indication corresponding to the QoS flow identification.

17. The management method of a transmission tunnel according to claim 12, characterized in that, The method further includes: sending, to a network controller, a user plane path deletion request, the user plane path deletion request including tunnel information between two UPFs, for deleting a user plane path and packet forwarding rules of paths of all forwarding devices R on the user plane path; The deleted user plane path is determined by the network controller based on the tunnel information between two UPFs carried in the user plane path deletion request, and the user plane path and the packet forwarding rules of the paths on the user plane path have a one-to-one correspondence.

18. A method of managing a transmission tunnel, characterized by, Applied to a forwarding device R, the method includes: receiving a packet forwarding rule of a path generated by a network controller, and locally completing configuration of the packet forwarding rule of the path; The packet forwarding rule of the path is used to define a rule that, under the condition of meeting a matching item, an entry forwarding device R directly encapsulates a label on a GTP packet, an intermediate forwarding device R replaces the label, or an exit forwarding device R deletes the label, and then forwards to a next hop interface.

19. The management method of a transmission tunnel according to claim 18, characterized in that, When the packet forwarding rule of the path is a first packet forwarding rule of the path: If the forwarding device R is an entry forwarding device R, it is determined that a GTP packet is encapsulated into a label packet according to a path label identification and a next hop interface is determined according to the content of the header in the GTP packet and the matching item in the packet forwarding rule of the entry forwarding device R; If the forwarding device R is an exit forwarding device R, it is determined that the GTP packet is extracted from the path label identification according to the content of the header in the label packet and the matching item in the packet forwarding rule of the exit forwarding device R, and a next hop interface is determined. If the forwarding device R is an intermediate forwarding device R, the header content in the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path according to the matching between the header content in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R, and the next hop interface is determined or the next hop interface is determined according to the matching between the header content in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R.

20. The method of claim 18, wherein, When the packet forwarding rule of the path is a second packet forwarding rule of the path: If the forwarding device R is an ingress forwarding device R, the GTP packet is encapsulated into a label packet according to the path label identifier and the QoS label according to the matching between the header content in the GTP packet and the matching item in the packet forwarding rule of the ingress forwarding device R, and the next hop interface and the QoS control according to the QoS label in the header of the label packet are determined; If the forwarding device R is an egress forwarding device R, the path label identifier is removed from the label packet to obtain the GTP packet according to the matching between the header content in the label packet and the matching item in the packet forwarding rule of the egress forwarding device R, and the next hop interface and the QoS control according to the QoS label in the header of the label packet are determined; If the forwarding device R is an intermediate forwarding device R, the header content in the label packet is replaced with the path label identifier corresponding to the next hop in the user plane path according to the matching between the header content in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R, and the next hop interface and the QoS control according to the QoS label in the header of the label packet are determined, or the next hop interface and the QoS control according to the QoS label in the header of the label packet are determined according to the matching between the header content in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R.

21. The management method of a transmission tunnel according to claim 18, characterized in that, The method further comprises: receiving an update packet forwarding rule request sent by a network controller, wherein the update packet forwarding rule request comprises a packet forwarding rule of a path with a new QoS label, and updating the QoS label in the packet forwarding rule of the path locally; performing QoS control on the GTP packet or the GTP packet encapsulated with a label based on the new QoS label carried by the packet forwarding rule of the path.

22. The management method of a transmission tunnel according to claim 18, characterized in that, The method further comprises: receiving a deletion instruction sent by a network controller, wherein the deletion instruction comprises a user plane path to be deleted; deleting the corresponding packet forwarding rule of the path stored locally based on the deletion instruction and the correspondence between the user plane path and the packet forwarding rule of the path. 23.A network controller electronic device, comprising a memory, a transceiver, and a processor; The memory is configured to store a computer program, the transceiver is configured to transceive data under the control of the processor, and the processor is configured to execute the computer program in the memory and implement the following steps: receiving a user plane path establishment request sent by a session management function entity SMF, wherein the user plane path establishment request comprises tunnel information between two UPFs; determine a user plane path, a path label, and a packet forwarding rule of a session between the two UPFs based on tunnel information between the two UPFs carried in the user plane path establishment request; send a packet forwarding rule configuration request carrying the packet forwarding rule of the path to all forwarding devices R on the user plane path; wherein, the packet forwarding rule of the path is used to limit the rule that under the condition of meeting the matching item, the ingress forwarding device R directly encapsulates a label for the GTP packet, the intermediate forwarding device replaces the label, or the egress forwarding device removes the label, and forwards to the next hop interface.

24. The network controller electronic device of claim 23, wherein, the determined packet forwarding rule of the path is a first packet forwarding rule of the path, and the first packet forwarding rule of the path specifically includes: if the forwarding device R is an ingress forwarding device R, the first packet forwarding rule of the path includes: determining that the GTP packet is encapsulated into a labeled packet according to the path label based on the content of the header in the GTP packet and the matching item in the packet forwarding rule of the ingress forwarding device R, and determining a next hop interface; if the forwarding device R is an egress forwarding device R, the first packet forwarding rule of the path includes: removing the path label from the labeled packet to extract the GTP packet based on the content of the header in the labeled packet and the matching item in the packet forwarding rule of the egress forwarding device R, and determining a next hop interface; if the forwarding device R is an intermediate forwarding device R, the first packet forwarding rule of the path includes: replacing the header content of the labeled packet with the path label corresponding to the next hop in the user plane path based on the content of the header in the labeled packet and the matching item in the packet forwarding rule of the intermediate forwarding device R, and determining a next hop interface or determining a next hop interface based on the content of the header in the labeled packet and the matching item in the packet forwarding rule of the intermediate forwarding device R.

25. The network controller electronic device of claim 23, wherein, the user plane path establishment request further includes QoS information corresponding to the tunnel information between the two UPFs, and the QoS information is a QoS indication or a QoS label; alternatively, the user plane path establishment request further includes a QoS flow identifier and QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the QoS flow identifier.

26. The network controller electronic device of claim 25, wherein, before the step of determining a user plane path, a path label, and a packet forwarding rule of a session between the two UPFs based on tunnel information between the two UPFs carried in the user plane path establishment request, the method further includes: determine a target QoS label based on the QoS indication carried in the user plane path establishment request and a mapping relationship between the QoS indication and a QoS label stored locally, or based on the QoS label carried in the user plane path establishment request.

27. The network controller electronic device of claim 26, wherein, the step of determining a user plane path, a path label, and a packet forwarding rule of a session between the two UPFs based on tunnel information between the two UPFs carried in the user plane path establishment request includes: determine a user plane path, a path label, and a second packet forwarding rule of a path between two UPFs based on tunnel information between the two UPFs and the target QoS label carried in the user plane path establishment request.

28. The network controller electronic device of claim 27, wherein, The second packet forwarding rule of the path includes: If the forwarding device R is an ingress forwarding device R, the second packet forwarding rule of the path includes: determining to encapsulate a GTP packet into a label packet according to the path label and the QoS label, and determining a next hop interface and performing QoS control according to the QoS label, according to the content of the header in the GTP packet and the matching item in the packet forwarding rule of the ingress forwarding device R. If the forwarding device R is an egress forwarding device R, the second packet forwarding rule of the path includes: removing the path label and extracting the GTP packet from the label packet, and determining a next hop interface and performing QoS control according to the QoS label in the header of the label packet, according to the content of the header in the label packet and the matching item in the packet forwarding rule of the egress forwarding device R. If the forwarding device R is an intermediate forwarding device R, the second packet forwarding rule of the path includes: replacing the content of the header in the label packet with the path label corresponding to the next hop in the user plane path, and determining a next hop interface and performing QoS control according to the QoS label in the header of the label packet, according to the content of the header in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R, or determining a next hop interface and performing QoS control according to the QoS label in the header of the label packet, according to the content of the header in the label packet and the matching item in the packet forwarding rule of the intermediate forwarding device R.

29. The network controller electronic device of claim 23, wherein, The steps further include: receiving a user plane path modification request sent by the session management function entity SMF, the user plane path modification request including tunnel information between two UPFs and QoS information; determining a target QoS label corresponding to the QoS information according to the user plane path modification request; updating the QoS label in the second packet forwarding rule of the path corresponding to the ingress forwarding device R based on the target QoS label; sending the updated second packet forwarding rule of the path to the ingress forwarding device R on the user plane path; wherein the updated second packet forwarding rule of the path is used to perform QoS control on a target packet according to the target QoS label, and the target packet is a GTP packet or a GTP packet encapsulated with a label.

30. The network controller electronic device of claim 29, wherein, In the case where the user plane path modification request includes tunnel information between two UPFs and QoS information, the QoS information is a QoS indication or a QoS label corresponding to the tunnel information between the two UPFs; Or, in the case where the user plane path modification request includes tunnel information between two UPFs, a QoS flow identifier, and QoS information, the QoS information is a QoS indication or a QoS label corresponding to the QoS flow identifier.

31. The network controller electronic device of claim 23, wherein, The steps further include: Receiving a user plane path deletion request sent by the session management function entity SMF, wherein the user plane path deletion request comprises tunnel information between two UPFs; According to the tunnel information between the two UPFs carried in the user plane path deletion request, determining the deleted user plane path, and sending an instruction to all forwarding devices R on the user plane path for deleting the corresponding path message forwarding rule.

32. A session management function entity SMF electronic device comprising a memory, a transceiver, and a processor; The memory is used to store computer programs; The transceiver is used to transceive data under the control of the processor; the processor is used to execute the computer programs in the memory and implement the following steps: Sending a user plane path establishment request to a network controller, wherein the user plane path establishment request comprises tunnel information between two UPFs; Wherein, the tunnel information between the two UPFs is used to determine the message forwarding rule of the path between the two UPFs, and the message forwarding rule of the path is used to limit the rule of directly encapsulating a label for a GTP message by an entry forwarding device R, replacing a label by an intermediate forwarding device R or deleting a label by an exit forwarding device R under the condition of meeting a matching item, and forwarding to a next hop interface.

33. The Session Management Function entity (SMF) electronic device of claim 32, wherein, The user plane path establishment request further comprises QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the tunnel information between the two UPFs; or, the user plane path establishment request further comprises a QoS flow identifier and QoS information, and the QoS information is a QoS indication or a QoS label corresponding to the QoS flow identifier.

34. The Session Management Function entity (SMF) electronic device of claim 32, wherein, The steps further comprise: Sending a user plane path modification request to a network controller, wherein the user plane path modification request comprises tunnel information between two UPFs and QoS information, or tunnel information between two UPFs and a QoS label, for updating a QoS label in a second message forwarding rule of a path corresponding to an entry forwarding device R according to a target QoS label, so that the entry forwarding device R performs QoS control on a target message according to the updated QoS label in the second forwarding rule of the path; Wherein, the target QoS label is a QoS label determined based on the QoS information and a preconfigured mapping relationship between a QoS indication and a QoS label, or is a QoS label carried in the user plane path modification request, and the QoS information is a Qos indication corresponding to the tunnel information between the two UPFs.

35. The session management function entity (SMF) electronic device of claim 32, wherein, The steps further comprise: Sending a user plane path modification request to a network controller, wherein the user plane path modification request comprises tunnel information between two UPFs, a QoS flow identifier and QoS information, or tunnel information between two UPFs, a QoS flow identifier and a QoS label, for updating a QoS label in a second message forwarding rule of a path corresponding to an entry forwarding device R according to a target QoS label, so that the entry forwarding device R performs QoS control on a target message according to the updated QoS label in the second forwarding rule of the path; The target QoS label is a QoS label determined based on the QoS information and a preconfigured mapping relationship between a QoS indication and a QoS label, or is a QoS label carried in the user plane path modification request, and the QoS information is a QoS indication corresponding to the QoS flow identifier.

36. The session management function entity (SMF) electronic device of claim 32, wherein, The steps further include: sending, to a network controller, a user plane path deletion request, the user plane path deletion request including tunnel information between two UPFs, for deleting a user plane path and a path of all forwarding devices R on the user plane path; The deleted user plane path is determined by the network controller based on the tunnel information between the two UPFs carried in the user plane path deletion request, and the user plane path and the path of the user plane path have a one-to-one correspondence relationship.

37. A forwarding electronic device, comprising a memory, a transceiver, and a processor; The memory is used for storing a computer program; the transceiver is used for transceiving data under the control of the processor; and the processor is used for executing the computer program in the memory and implementing the following steps: receiving a path message forwarding rule generated by a network controller, and locally completing configuration of the path message forwarding rule; wherein The path message forwarding rule is used for defining a rule that, under the condition of meeting a matching item, an entry forwarding device R directly encapsulates a label for a GTP message, an intermediate forwarding device R replaces the label, or an exit forwarding device R deletes the label, and forwards to a next hop interface.

38. The forwarding electronic device of claim 37, wherein, The steps further include: receiving an update message forwarding rule request sent by a network controller, the update message forwarding rule request including a path message forwarding rule of a new QoS label, and locally completing updating of the QoS label in the path message forwarding rule; Based on the new QoS label carried in the path message forwarding rule, performing QoS control on the GTP message or the GTP message after encapsulation of the label.

39. The forwarding electronic device of claim 37, wherein, The steps further include: receiving a deletion instruction sent by a network controller, the deletion instruction including a user plane path to be deleted; Based on the deletion instruction and the correspondence relationship between the user plane path and the path message forwarding rule, deleting the corresponding path message forwarding rule stored locally.

40. A network controller apparatus, comprising: The device includes: A first receiving module is configured to receive a user plane path establishment request sent by a session management function entity (SMF), the user plane path establishment request including tunnel information between two UPFs. A first determining module is configured to determine, based on the tunnel information between the two UPFs carried in the user plane path establishment request, a user plane path of one session between the two UPFs, a path label identifier, and a path message forwarding rule. A first sending module is configured to send a message forwarding rule configuration request carrying the path message forwarding rule to all forwarding devices R on the user plane path. The path message forwarding rule is used for defining a rule that, under the condition of meeting a matching item, an entry forwarding device R directly encapsulates a label for a GTP message, an intermediate forwarding device R replaces the label, or an exit forwarding device R deletes the label, and forwards to a next hop interface.

41. A session management function entity (SMF) apparatus, the SMF apparatus comprising: The apparatus comprises: The second sending module is used for sending a user plane path establishment request to a network controller, wherein the user plane path establishment request comprises tunnel information between two UPFs; The tunnel information between the two UPFs is used for determining a packet forwarding rule of a path between the two UPFs, and the packet forwarding rule of the path is used for defining a rule that, under the condition of meeting a matching item, an entry forwarding device R directly encapsulates a label for a GTP packet, an intermediate forwarding device R replaces the label or an exit forwarding device R deletes the label, and then forwards to a next hop interface.

42. An apparatus for forwarding comprising: The apparatus comprises: The third receiving module is used for receiving a packet forwarding rule of a path generated by a network controller, and locally completing configuration of the packet forwarding rule of the path; The packet forwarding rule of the path is used for defining a rule that, under the condition of meeting a matching item, an entry forwarding device R directly encapsulates a label for a GTP packet, an intermediate forwarding device R replaces the label or an exit forwarding device R deletes the label, and then forwards to a next hop interface.

43. A processor-readable storage medium, comprising: The processor readable storage medium stores a computer program, and the computer program is used for making the processor execute the transmission tunnel management method in any one of claims 1 to 11, or the transmission tunnel management method in any one of claims 12 to 17, or the transmission tunnel management method in any one of claims 18 to 22.

Images