WO2021018242A1 - Data forwarding method, apparatus and system - Google Patents

Abstract

A data forwarding method, apparatus and system. The method comprises: after receiving a first data packet, a first user plane function network element firstly determining, according to a routing rule matching the first data packet, a first path type of a sending path used for forwarding the first data packet to other user plane function network elements, and the first path type comprises one or more of a loop interface type and a branch interface type; and the first user plane function network element then determining the sending path according to the first path type. When forwarding a data packet, a first user plane function network element can only forward the data packet by means of a transmission path of a specific path type, that is, when a certain transmission path is different from that of the specific path type, the first user plane function network element cannot forward the data packet from the transmission path, such that the problem of loop forwarding caused by the fact that a data packet is forwarded by means of all the transmission paths of a first user plane function network element can be avoided.

Description

Data forwarding method, device and system

Cross references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910696555.7, and the application name is "a data forwarding method, device, and system" on July 30, 2019. The entire content is incorporated herein by reference. Applying.

Technical field

This application relates to the field of communication technology, and in particular to a data forwarding method, device and system.

Background technique

Fifth-generation mobile communication system, a local area network ^{(5 th Generation local area network,} 5G LAN) service is a service provided by the system 5G, the terminal capable of belonging to the same group to provide Internet Protocol LAN (internet protocol, IP) or Ethernet type ( ethernet) type of private communication. For example, devices in a factory form a LAN group, and devices belonging to this LAN group can send Ethernet packets or IP packets to each other.

There is a situation where the networking architecture of multiple user plane function (UPF) network elements constituting the 5GLAN may be a ring architecture or a branch architecture. In this way, when broadcast data is sent in a ring architecture or branch architecture 5GLAN, there may be a loop forwarding problem.

Summary of the invention

The embodiments of the present application provide a data forwarding method, device, and system to solve the loop forwarding problem in a 5G LAN with a ring architecture or a branch architecture.

In a first aspect, a data forwarding method is provided. In this method, after receiving a first data packet, a first user plane function network element first determines to forward the first data packet according to a routing rule matching the first data packet. The first path type of the transmission path of a data packet to other user plane function network elements, the first path type includes one or more of loop interface type and branch interface type, and then, the first user plane function network element Then the sending path is determined according to the first path type.

In the above technical solution, when the first user plane function network element forwards a data packet, it will only forward the data packet through a transmission path of a specific path type, that is, when a certain transmission path is different from a specific path type, then The first user plane function network element does not forward the data packet from the transmission path, so that the loop forwarding problem caused by forwarding the data packet through all transmission paths of the first user plane function network element can be avoided.

In a possible design, after the first user plane function network element determines from at least one transmission path of the first user plane function network element that the transmission path whose path type is the first path type is the transmission path, Then, the first data packet is forwarded to other user plane function network elements through the transmission path.

In a possible design, when the first user plane function network element determines that at least one transmission path of the first user plane function network element does not include a transmission path of the same type as the first path, the first user plane function The network element determines not to forward the first data packet.

In the above technical solution, if the first user plane function network element can determine a transmission path of the same type as the first path from at least one transmission path of the first user plane function network element, the data packet is forwarded through the transmission path, Otherwise, the data packet is not forwarded, thereby avoiding the loop forwarding problem caused by forwarding the data packet through all transmission paths of the first user plane function network element.

In a possible design, the routing rule includes a packet detection rule PDR for detecting the first data packet or a forwarding behavior rule FAR for forwarding the first data packet.

In the above solution, the first data packet may be a data packet whose destination address is a broadcast address. Since the data packet whose destination address is the broadcast address has a higher probability of loop forwarding during the forwarding process, this forwarding method can be used in the forwarding scenario of the data packet whose destination address is the broadcast address.

In a possible design, the first user plane function network element may first determine the second path type of the receiving path for the first user plane function network element to receive the first data packet according to the PDR in the routing rule, and then, according to The second path type and the preset transmission rule determine the first path type.

In the above technical solution, the preset transmission rule can be stored in the first user plane function network element, so that a method for determining the first path type can be provided through the PDR and the preset transmission rule.

In a possible design, if the PDR includes the path type parameter of the receiving path, the first user plane function network element determines the second path type according to the value of the path type parameter of the receiving path; or,

If the PDR includes the tunnel information parameter of the receiving path, the first user plane function network element is based on the value of the tunnel information parameter of the receiving path and the path type of at least one transmission path of the first user plane function network element, Determine the second path type.

In the above technical solution, the second path type can be determined in different ways according to different parameters carried in the PDR, which can increase the flexibility of the solution.

In a possible design, the preset transmission rule includes:

If the path type of the receiving path is the loop interface type, the path type of the sending path is the branch interface type, and if the path type of the receiving path is the branch interface type, then the path type of the sending path is the The branch interface type and the loop interface type.

The foregoing preset transmission rule is only an example, and those skilled in the art can also set other transmission rules, which are not limited here.

In a possible design, the first user plane function network element may determine the first path type according to the value of the path type parameter of the transmission path included in the FAR in the routing rule.

In the above technical solution, the first user plane function network element can directly determine the first path type according to the parameters in the FAR, and the implementation method is simple.

In a possible design, the first user plane function network element may receive a first indication for indicating the path type of at least one transmission path of the first user plane function network element from the session management function network element.

In the above technical solution, the path type of the at least one transmission path of the first user plane function network element is indicated by the session management function network element, which can ensure the accuracy of the path type of the at least one transmission path.

In a possible design, the routing rule may be received by the first user plane function network element from the session management function network element.

In a second aspect, a data forwarding method is provided. In the method, a session management function network element first generates a data forwarding method based on the path type of the transmission path of the first user plane function network element and a preset transmission rule. A set of routing rules corresponding to the functional network element, the path type of the transmission path includes one or more of the loop interface type and the branch interface type, and the preset transmission rule includes if the path type of the receiving path is the loop interface type , The path type of the sending path is the branch interface type, and if the path type of the receiving path is the branch interface type, the path type of the sending path is the branch interface type and the loop interface type. Then, the session management function network element sends the set of routing rules to the first user plane function network element.

In the above technical solution, when the session management function network element generates the routing rule with the first user plane function network element, it has considered the path type of each transmission path of the first user function network element, for example, when the first user function network element If the path type of a certain transmission path in the user plane function network element is the loop interface type, the routing rule corresponding to the transmission path will instruct the data packet received from the transmission path to be forwarded through the branch interface type transmission path, and There is no need to forward through the transmission path of the loop interface type. In this way, the problem of loop forwarding caused by forwarding data packets through all transmission paths of the first user plane function network element can be avoided.

In a possible design, a set of routing rules includes a packet detection rule PDR for detecting the first data packet and a forwarding behavior rule FAR for forwarding the first data packet.

In a possible design, a set of routing rules corresponding to the first user plane function network element generated by the session management function network element may include but not limited to the following two methods:

The first way:

The set of routing rules includes a first PDR for detecting a first data packet received from a first N19 path, and the transmission path of the first user plane function network element includes the first N19 path; and,

A first FAR associated with the first PDR, where the first FAR includes tunnel information of a second N19 path, and the transmission path of the first user plane function network element includes the second N19 path.

Specifically, if the path type of the first N19 path is a loop interface type, then the second N19 path is an N19 path whose path type is a branch interface type in the transmission path of the first user plane function network element. The path type of the first N19 path is a branch interface type, and the second N19 path is a N19 path other than the first N19 path in the transmission path of the first user plane function network element.

The second way:

The set of routing rules includes a first PDR for detecting the first data packet received from a first N19 path, and the transmission path included in the first user plane function network element includes the first N19 path ;as well as,

A first FAR associated with the first PDR, the first FAR is used to forward the first data packet to the internal interface of the first user plane function network element, and the first FAR includes the path type parameter of the outgoing interface , Wherein the path type parameter of the outgoing interface includes the loop interface type or the branch interface type; and,

A second PDR, the second PDR is used to detect the first data packet received from the internal interface, and the second PDR includes the path type parameter of the incoming interface; and,

A second FAR associated with the second PDR, the second FAR includes the tunnel information of the second N19 path, the transmission path of the first user plane function network element includes the second N19 path, and the second N19 path is a path type It is one or more of the transmission path of the loop interface type and the branch interface type.

Specifically, if the path type of the first N19 path is a loop interface type, the value of the path type parameter of the outgoing interface is a loop interface type, and if the path type of the first N19 path is a branch interface type, Then the value of the path type parameter of the outgoing interface branch interface type; and,

If the path type parameter of the incoming interface is a loop interface type, the second N19 path is the N19 path of the transmission path of the first user plane function network element whose path type is the branch interface type. The path type parameter is the branch interface type, and the second N19 path is the N19 path other than the first N19 path in the transmission path of the first user plane function network element.

In the above technical solution, the session management function network element can determine a set of routing rules corresponding to the first user plane function network element in multiple ways, which can increase the flexibility of the solution.

In a possible design, the session management function network element may determine the path type of the transmission path of the first user plane function network element according to the network topology interface of the user plane of the 5G local area network LAN group, and the first user plane The functional network element belongs to the 5GLAN group.

In the above technical solution, a solution is provided in which a session management function network element determines the path type of the transmission path.

In a third aspect, a communication device is provided. The communication device includes a processor for implementing the method executed by the first user plane function network element in the first aspect. The communication device may also include a memory for storing program instructions and data. The memory is coupled to the processor, and the processor can call and execute the program instructions stored in the memory to implement any method executed by the first user plane function network element in the first aspect. The communication device may also include a transceiver, and the transceiver is used for the communication device to communicate with other devices. Exemplarily, the other device is a network element with a session management function.

In a fourth aspect, an embodiment of the present application provides a communication device, including: a transceiving unit, configured to receive a first data packet; and a processing unit, configured to determine the first transmission path according to a routing rule matching the first data packet A path type, the first path type includes one or more of a loop interface type and a branch interface type, and the transmission path is used to forward the first data packet to other user plane function network elements; and, according to The first path type determines the transmission path.

In addition, the communication device provided in the fourth aspect can be used to execute the method corresponding to the first user plane function network element in the first aspect. For the implementation manners not described in detail in the communication device provided in the fourth aspect, refer to the foregoing embodiments. I won't repeat it here.

In a fifth aspect, a communication device is provided. The communication device includes a processor for implementing the method executed by the network element with the session management function in the second aspect. The communication device may also include a memory for storing program instructions and data. The memory is coupled with the processor, and the processor can call and execute program instructions stored in the memory to implement any method executed by the session management function network element in the second aspect. The communication device may also include a transceiver, and the transceiver is used for the communication device to communicate with other devices. Exemplarily, the other device is a first user plane function network element.

In a sixth aspect, an embodiment of the present application provides a communication device, including: a processing unit, configured to generate a connection with the first user plane according to the path type of the transmission path of the first user plane function network element and a preset transmission rule A set of routing rules corresponding to functional network elements, the path type of the transmission path includes one or more of a loop interface type and a branch interface type, and the preset transmission rule includes if the path type of the receiving path is The loop interface type, the path type of the transmission path is the branch interface type, and, if the path type of the receiving path is the branch interface type, the path type of the transmission path is the branch interface The type and the type of the loop interface; the transceiver unit is configured to send the set of routing rules to the first user plane function network element.

In addition, the communication device provided in the sixth aspect can be used to execute the method corresponding to the session management function network element in the second aspect. For the implementation modes not described in detail in the communication device provided in the sixth aspect, please refer to the foregoing embodiments. Repeat it again.

In a seventh aspect, an embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the first user plane function network element in the first aspect or the session in the second aspect The method of management function network element execution.

In an eighth aspect, the embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the first user plane function network element in the first aspect or the session management function in the second aspect The method performed by the network element.

In a ninth aspect, an embodiment of the present application provides a chip system. The chip system includes a processor and may also include a memory for implementing the first user plane function network element in the first aspect or the session management function network element in the second aspect. Meta implementation method. The chip system can be composed of chips, or can include chips and other discrete devices.

In a tenth aspect, an embodiment of the present application provides a communication system. The system includes the communication device described in the third aspect and the fifth aspect, or includes the communication device described in the fourth aspect and the sixth aspect.

For the beneficial effects of the aforementioned third to tenth aspects and their implementation manners, reference may be made to the description of the method and implementation manners of the first aspect or the beneficial effects of the method and implementation manners of the first aspect.

Description of the drawings

Figure 1 is a network architecture diagram of an example of a communication system to which this application applies;

Figure 2 is a schematic diagram of a specific network architecture applicable to this application;

3A is a schematic diagram of an example of an application scenario of an embodiment of the application;

3B is a schematic diagram of another example of an application scenario of an embodiment of the application;

FIG. 4A is a flowchart of an example of the forwarding process within the UPF network element;

4B is a flowchart of another example of the internal forwarding process of the UPF network element;

FIG. 5 is a flowchart of an example of a data forwarding method provided in an embodiment of this application;

FIG. 6 is a flowchart of another example of a data forwarding method provided in an embodiment of this application;

FIG. 7 is a schematic structural diagram of a communication device provided in an embodiment of this application;

FIG. 8 is a schematic structural diagram of another communication device provided in an embodiment of this application;

FIG. 9 is a schematic structural diagram of another communication device provided in an embodiment of this application;

FIG. 10 is a schematic structural diagram of another communication device provided in an embodiment of this application;

FIG. 11 is a schematic block diagram of a communication system provided by an embodiment of this application.

Detailed ways

In order to make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings of the specification and specific implementations.

Please refer to FIG. 1, which is a network architecture diagram of an example of a communication system applicable to this application. The network elements in the network architecture include a terminal, an access network (AN), a core network (Core), and a data network (DN). The access network may be a radio access network (radio access network, RAN). In this network architecture, terminal, AN and Core are the main parts of this network architecture. For the network elements in AN and Core, they can be logically divided into user plane and control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of business data. For example, in the network architecture shown in Figure 1, the NG2 reference point is between the RAN control plane and the Core control plane, the NG3 reference point is between the RAN user plane and the Core user plane, and the NG6 reference point is between the Core user plane and the DN. between.

In the network architecture described in Figure 1, the terminal is also called terminal equipment (terminal equipment), user equipment (UE), mobile station (MS), mobile terminal (mobile terminal, MT), etc. , A terminal is a device with wireless transceiving function, which is the portal for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display business windows to users, and receive user input operations. In the 5G communication system, the terminal will use the new air interface technology to establish a signal connection and data connection with the AN to transmit control signals and service data to the network.

Terminals can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on the water (such as ships, etc.); they can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). For example, the terminal may include a mobile phone (or "cellular" phone), a computer with a mobile terminal, portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile devices, smart wearable devices, and so on. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistants, etc.) PDA), and other equipment.

Alternatively, the terminal may also include restricted devices, such as devices with low power consumption, or devices with limited storage capabilities, or devices with limited computing capabilities. Examples include barcodes, radio frequency identification (RFID), sensors, global positioning system (GPS), laser scanners and other information sensing equipment.

As an example and not a limitation, in the embodiments of this application, smart wearable devices are the general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes Wait. A smart wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Smart wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, smart wearable devices include full-featured, large-sized, complete or partial functions that can be realized without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as various smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.

Alternatively, the terminal can also be a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in driverless, and a remote Wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and smart homes Wireless terminals in

In the network architecture shown in Figure 1, AN is similar to the (radio) access network ((radio) access network, (R) AN) equipment in a traditional communication network, for example, it includes a base station (for example, an access point), and is deployed In a location close to the terminal, the network access function is provided for authorized users in a specific area, and transmission tunnels of different quality can be determined according to the user's level and service requirements to transmit user data. AN can manage and reasonably use its own resources, provide access services for terminals on demand, and be responsible for forwarding control signals and business data between the terminal and the Core.

In the network architecture shown in Figure 1, the Core is responsible for maintaining mobile network subscription data, managing the network elements of the mobile network, and providing the terminal with functions such as session management, mobility management, policy management, and security authentication. For example, when the terminal is attached, the terminal is provided with network access authentication; when the terminal has a service request, the terminal is allocated network resources; when the terminal is moving, the terminal is updated with network resources; when the terminal is idle, the terminal is provided with fast recovery Mechanism: When the terminal is detached, it releases network resources for the terminal; when the terminal has service data, it provides the terminal with data routing functions, such as forwarding uplink data to DN, or receiving downlink data from DN and forwarding to AN.

In the network architecture shown in Figure 1, DN is a data network that provides business services to users. In the actual communication process, the client is usually located at the terminal, and the server is usually located at the DN. The DN can be a private network, such as a local area network, or an external network that is not under the control of operators, such as the Internet, or a private network jointly deployed by operators, such as providing IP multimedia core network subsystem, IMS) service network.

Please refer to FIG. 2, which is a schematic diagram of a specific network architecture applicable to this application. The network architecture is a 5G network architecture. The network elements in the 5G architecture include a terminal, a radio access network (RAN), and a data network (DN). In FIG. 2, the terminal is a user equipment (UE) as an example. In addition, the network architecture also includes core network elements, which include UPF network elements and control plane function network elements. Specifically, control plane function network elements include, but are not limited to, access and mobility management function (AMF) network elements, SMF network elements, authentication server function (authentication server function, AUSF) network elements, and application functions (application function, AF) network element, unified data management (unified data management, UDM) network element, policy control function (PCF) network element, network exposure function (NEF) network element, NF repository function (NF repository function, NRF) network element and network slice selection function (network slice selection function, NSSF) network element.

It should be noted that in the traditional core network architecture, the control plane functional network elements adopt a point-to-point communication method, that is, the interface communication between the control plane functional network elements adopts a set of specific messages, and the control plane functional network at both ends of the interface Yuan can only communicate using this specific set of messages. In the 5G core network architecture, the control plane adopts a service-oriented architecture, that is, the interaction between control plane functional network elements adopts the method of service invocation, and the control plane functional network element will open services to other control plane functional network elements for other control Face function network element call.

The function of each network element in the network architecture shown in FIG. 2 is described in detail below. Since the functions of UE, (R)AN, and DN have been introduced in the related description of the network architecture shown in FIG. 1, the following focuses on the functions of each core network element.

The UPF network element is a functional network element of the user plane, which is mainly responsible for connecting to external networks. It includes a long term evolution (LTE) serving gateway (SGW) and a packet data network gateway (packet data network gateway, PDN-GW) related functions. Specifically, the UPF can perform user data packet forwarding according to the routing rules of the SMF, for example, uplink data is sent to a DN or other UPF; downlink data is forwarded to another UPF or RAN.

The AMF network element is responsible for the access management and mobility management of the UE, for example, the status maintenance of the UE, the reachability management of the UE, and the non-mobility management non-access-stratum (MM NAS) message The forwarding of session management (SM) N2 messages. In practical applications, the AMF network element can implement the mobility management function in the MME in the LTE network framework, as well as the access management function.

The SMF network element is responsible for session management, allocating resources for UE sessions, and releasing resources; the resources include session quality of service (QoS), session paths, routing rules, etc.

The AUSF network element is used to perform security authentication of the UE.

The AF network element may be a third-party application control platform, or a device deployed by an operator, and the AF network element may provide services for multiple application servers.

The UDM network element can store the subscription information of the UE.

The PCF network element is used for user policy management, similar to the policy and charging rules function (PCRF) network element in LTE, and is mainly responsible for the generation of policy authorization, service quality and charging rules, and The corresponding rules are generated through the SMF network element to generate routing rules and sent to the UPF network element to complete the installation of the corresponding policies and rules.

The NEF network element is used to open network functions to third parties in the form of a northbound application programming interface (API).

The NRF network element is used to provide storage and selection functions of network function entity information for other network elements.

The NSSF network element is used to select a network slice for the UE.

In the network architecture shown in FIG. 2, the SMF network element is also used to manage the local area network communication of the UE in the group.

Among them, in the network architecture shown in FIG. 2, the network elements related to this application mainly include: UPF and SMF.

The following describes the application scenarios of this application. This application is mainly used in scenarios where 5G systems provide 5GLAN services.

Please refer to FIG. 3A, which is a schematic diagram of an example of the user plane architecture of the 5GLAN service involved in this application. Among them, UPF1 to UPF4 belong to a 5GLAN. UE1 to UE4 are respectively connected to a UPF network element in the 5GLAN through a RAN. In FIG. 3A, UE1 is connected to UPF1, UE2 is connected to UPF2, UE3 is connected to UPF3, and UE4 is connected to UPF4, thereby accessing the corresponding user plane (UP) of the 5GLAN through the UPF network element. The user plane of 5GLAN can communicate with the existing LAN in the DN through the N6 interface. Alternatively, the user plane of the 5GLAN can also associate the protocol data unit (protocol data unit session, PDU) session (session) of different UEs through the N19 connection between each UPF (for example, UPF1 to UPF4) in the 5GLAN, so as to realize the UE's Private communication between. In Figure 3A, UPF1 is connected to UPF2 and UPF4, respectively, and UPF3 is connected to UPF2 and UPF4, respectively, so that UPF1 to UPF4 form a ring architecture.

Please refer to FIG. 3B, which is a schematic diagram of another example of the user plane architecture of the 5GLAN service involved in this application. The difference from FIG. 3A is that in FIG. 3B, UPF1 to UPF3 constitute a ring architecture, UPF4 is only connected to UPF2, and UPF4 can be understood as a branch of UPF2, and thus UPF1 to UPF4 constitute a branch architecture.

The numbers of UPF, RAN, and UE in FIG. 3A and FIG. 3B are just examples. In practical applications, the user plane architecture of the 5GLAN service provided by this application can provide services for more terminals and can include more UPFs. In addition, in the user plane architecture of the 5GLAN service as shown in FIG. 3A and FIG. 3B, although UPF, UE, and DN are shown, the user plane architecture of the 5GLAN service may not be limited to include the above content. For example, it may also include SMF network elements, PCF network elements, devices for carrying virtualized network functions, wireless relay devices, and so on. These are obvious to those of ordinary skill in the art, and will not be detailed here.

It should be noted that the technical term "5GLAN" in this application can be used interchangeably with "5G LAN-type service", "5G LAN-virtual network (VN)" or "5G VN".

To facilitate those skilled in the art to understand the solutions of the embodiments of the present application, the technical terms involved in the present application are described below.

1) N4 sessions, including UE-level N4 sessions and group-level N4 sessions.

The N4 session is created by the SMF network element on the UPF network element.

As an example, the SMF network element may instruct the UPF network element to create an N4 session corresponding to the PDU session when creating a protocol data unit (PDU) session (session) of the UE, which may also be referred to as a UE-level N4 session. Session (in this application, the UE-level N4 session and the N4 session corresponding to the PDU session can be used interchangeably). For example, in FIG. 3B, UE1 is connected to UPF1 through RAN1, and SMF can instruct UPF1 to create an N4 session corresponding to the PDU session of UE1 when creating a PDU session of UE1. The routing rules in the UE-level N4 session can be used to detect and forward data related to this UE. When the SMF receives the request to delete the PDU session of the UE, it triggers the UPF network element to delete the N4 session corresponding to the PDU session.

For the convenience of description, the N4 session corresponding to the PDU session is distinguished by the “identity of the UE” in the following. For example, the N4 session corresponding to the PDU session of UE1 may be referred to as the N4 session of UE1, and so on.

In order to support the communication between different UPF network elements and the communication between UPF network elements and DN in the 5GLAN service, the SMF network element also needs to be a corresponding 5G VN group (or 5GLAN) for each UPF network element that provides 5GLAN services. Create a group-level N4 session. The routing rules in the group-level N4 session are used to detect the data belonging to any UE in the 5G VN group (which can be understood as the data belonging to the 5G VN group) and forward the data belonging to the 5G VN Group data, where forwarding data belonging to the 5G VN group may include forwarding across UPF network elements (different UPF network elements in a 5G LAN group), or forwarding through an N6 tunnel or locally. In this application, the N4 session corresponding to the group and the N4 session corresponding to the tunnel can be understood as N4 sessions at the group level. For example, in FIG. 3A, UE1 to UE4 belong to a 5GLAN, and the SMF network element creates a group-level N4 session for this 5GLAN in each UPF network element. When the SMF network element creates the first PDU session to the 5GLAN, it creates a group-level N4 session corresponding to the 5GLAN, and when it releases the last PDU session to the 5GLAN, deletes the group level corresponding to the 5GLAN N4 session.

A UPF network element may include one or more N4 sessions corresponding to PDU sessions. For example, if multiple UEs are connected to the same UPF network element, the UPF network element needs to create an N4 session corresponding to each UE's PDU session. And, one UPF network element may include one or more group-level N4 sessions. This application does not limit the number of N4 sessions.

2) Routing rules, used to detect and forward data packets in the context of N4 sessions, including uplink packet detection rule (UL PDR) and uplink forwarding behavior associated with UL PDR Rules (UL forward action rule, UL FAR), downlink packet detection rules (downlink PDR, DL PDR), and DL FAR associated with DL PDR. Among them, PDR (UL PDR and DL PDR) is used to detect the data transmitted from the outside to the UPF network element or the data forwarded from the internal interface of the UPF network element, and FAR (UL FAR and DL FAR) is used to indicate that the UPF network element is detecting The received data is forwarded, copied, buffered, discarded, notified, etc. When the SMF network element instructs UPF to create an N4 session, it will set corresponding routing rules for the N4 session. The incoming data from the outside can be understood as the data received by the UPF network element through the GTP-U tunnel or the N6 interface.

For the N4 session corresponding to the PDU session:

UL PDR specifically includes source interface parameters and tunnel information parameters.

The UL FAR associated with the UL PDR includes target interface parameters, which are used to transmit data packets matching the UL PDR to the target interface. SMF sets the value of the target interface parameter to the value corresponding to the internal interface of the UPF (for example, "5GLAN internal"). It can be understood that the UL FAR in the N4 session corresponding to the PDU session is used to locally forward the data packet matching the UL PDR in the N4 session to the internal interface of the UPF.

The DL PDR specifically includes source interface parameters and filter parameters.

The DL FAR associated with the DL PDR includes target interface parameters and/or external tunnel parameters, and is used to transmit data packets matching the DL PDR to the target interface. The SMF network element sets the value of the target interface parameter to "access side" or "core side", and the value of the external tunnel parameter sets the tunnel information of the PDU session (for example, the tunnel of the PDU session on the AN or UPF network element Head GTP-U TEID). It can be understood that the DL FAR in the N4 session corresponding to the PDU session is used to transmit data packets matching the DL PDR in the N4 session to the designated PDU session tunnel.

For group-level N4 sessions:

UL PDR specifically includes source interface parameters and filter parameters.

The UL FAR associated with the UL PDR includes target interface parameters and/or external tunnel parameters, and is used to forward data packets matching the UL PDR to the target interface. The SMF sets the value of the target interface parameter to "core side", and the value of the external tunnel parameter to the information of the N19 tunnel (for example, the tunnel header GTP-U TEID of the opposite UPF connected to the UPF). It can be understood that the UL FAR in the N4 session with the group level is used to forward data packets matching the UL PDR in the N4 session at the group level to the N19 tunnel connecting the UPF and other UPFs.

The DL PDR specifically includes source interface parameters and/or tunnel information parameters.

The DL FAR associated with the DL PDR includes target interface parameters, which are used to transmit data packets matching the DL PDR to the target interface. The value of the target interface parameter of the SMF is set to the value corresponding to the internal interface of the UPF (for example, "5GLAN internal"). It can be understood that the DL FAR in the N4 session at the group level is used to locally forward data packets matching the DL PDR in the N4 session at the group level to the internal interface of the UPF.

3) The matching process between the data packet and the PDR.

After the UPF network element receives a data packet, it will detect the data packet and determine that the data packet matches the PDR (or, it can be said that the data packet is successfully matched to the PDR, or it can be said that the PDR is successfully matched to the data packet). Specifically include the following four matching processes:

(1) According to the PDU session tunnel information of the incoming data packet, the interface information of the incoming data packet detects the data packet, if the PDU session tunnel information of the incoming data packet, the interface information of the incoming data packet, and the corresponding PDU session The corresponding parameters in the UL PDR of the N4 session are matched one by one, and the UL PDR of the N4 session corresponding to the PDU session is successfully matched to the incoming data packet.

(2) Detect the data packet according to the interface information of the incoming data packet, the header information of the data packet, if the interface information of the incoming data packet, the header information of the data packet, and the corresponding in the DL PDR of the N4 session corresponding to the PDU session If the parameters are matched one by one, the DL PDR of the N4 session corresponding to the PDU session is successfully matched to the incoming data packet.

(3) Detect the data packet based on the interface information of the incoming data packet and the header information of the data packet. If the interface information of the incoming data packet, the header information of the data packet and the corresponding parameters in the UL PDR of the group-level N4 session match one by one, the UL PDR of the group-level N4 session is successfully matched to the incoming data packet .

(4) Detect the data packet according to the interface information of the incoming data packet and/or the N19 tunnel information of the incoming data packet. If the interface information of the incoming data packet and/or the tunnel information of the incoming data packet match the corresponding parameters in the DL PDR of the group-level N4 session, the DL PDR of the group-level N4 session is successful Match to the incoming packet.

In a specific implementation process, the UPF network element executes one or more of the above four matching processes to match the data packet to the PDR.

4) The process of forwarding data packets based on PDR and FAR in the N4 session.

Please refer to Figures 4A to 4B, which are schematic diagrams of forwarding data packets based on PDR and FAR. Figures 4A and 4B include UPF1 and UPF2. Among them, UE1 to UE2 are respectively connected to UPF1, UE3 is connected to UPF2, and UE1 to UE3 are a 5G VN group (group1). UPF1 includes the N4 session of UE1, the N4 session of UE2, and the N4 session of group1.

The first forwarding process, please refer to Figure 4A, which is the internal forwarding process of the UPF network element:

(1) UE1 sends data packet 1 through the PDU session of UE1.

(2) UPF1 receives the data packet 1, executes the matching process between the data packet and the PDR, and detects that the data packet 1 matches the UL PDR of the N4 session of UE1.

(3) UPF1 obtains the UL FAR associated with the UL PDR of the N4 session of UE1, determines that the target interface of the FAR is the internal interface of UPF1, and sends the data packet to the internal interface of UPF1.

(4) UPF1 receives the data packet transmitted through the internal interface, performs the matching process between the data packet and the PDR, and detects that the data packet matches the DL and PDR of the N4 session of UE2.

(5) UPF1 obtains the DL FAR associated with the DL PDR of the N4 session of UE2, determines the tunnel information of the PDU session of UE2, and sends the data packet to the PDU session of UE2 so that UE2 can pass the PDU of UE2 The session receives the packet.

The second forwarding process, please refer to Figure 4B, which is the forwarding process across UPF network elements:

(1) UE1 sends data packet 2 through the PDU session of UE1.

(2) UPF1 receives the data packet 2, performs the matching process between the data packet and the PDR, and detects that the data packet 2 matches the UL PDR of the N4 session of the UE1.

(3) UPF1 obtains the UL FAR associated with the UL PDR of the N4 session of UE1, determines that the target interface of the FAR is the internal interface of UPF1, and sends the data packet 2 to the internal interface of UPF1.

(4) UPF1 receives data packet 2 transmitted through the internal interface, executes the matching process between data packet 2 and PDR, and detects that the data packet 2 matches the UL PDR of the N4 session of group1.

(5) UPF1 obtains the UL FAR associated with the UL PDR of the N4 session of group1, determines the N19 tunnel between UPF1 and UPF2, and sends the data packet 2 to UPF2 through the N19 tunnel.

(6) UPF2 receives the data packet 2 sent through the N19 tunnel, executes the matching process between the data packet 2 and the PDR, and detects that the data packet 2 matches the DL and PDR of the N4 session of group1.

(7) UPF2 obtains the DL FAR associated with the DL PDR of the N4 session of group1, determines that the target interface of the FAR is the internal interface of UPF2, and sends the data packet 2 to the internal interface of UPF2.

(8) UPF2 receives the data packet 2 transmitted through the internal interface, performs the matching process between the data packet 2 and the PDR, and detects that the data packet 2 matches the DL and PDR of the N4 session of the UE3.

(9) UPF2 obtains the DL FAR associated with the DL PDR of the N4 session of UE3, determines the tunnel information of the PDU session of UE3, and sends the packet 2 to the PDU session of UE3 so that UE3 can pass the UE3’s PDU session. The PDU session receives the data packet 2.

5) The internal interface of the UPF is a virtual port or a specific port in the UPF network element, which is used for the UPF network element to locally forward the received data packet. Among them, local forwarding to the internal interface of the UPF network element means that the UPF network element re-receives the data packet on the internal interface so that the data packet is detected by the UPF network element again, so that the classification matches the corresponding routing rule and forwards it to the correct path. Before rechecking, the UPF network element can decapsulate the external tunnel header for the data packet. Optionally, the data packet may be re-encapsulated with new external tunnel header information. The new tunnel information may be included in the FAR of the routing rule, or generated by the UPF network element according to the forwarding indication information in the FAR.

6) In the description of this application, "multiple" means two or more than two. In view of this, "multiple" can also be understood as "at least two" in the embodiments of this application. "At least one" can be understood as one or more, for example, one, two or more. For example, including at least one refers to including one, two or more, and does not limit which ones are included. For example, including at least one of A, B, and C, then the included can be A, B, C, A and B, A and C, B and C, or A and B and C. "And/or" describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. In addition, the character "/", unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship. The terms "system" and "network" in the embodiments of this application can be used interchangeably.

Unless otherwise stated, the ordinal numbers such as “first” and “second” mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or importance of multiple objects.

In addition, the user plane architecture of the 5GLAN service described in the embodiments of this application is to illustrate the technical solutions of the embodiments of this application more clearly, and does not constitute a limitation to the technical solutions provided in the embodiments of this application. Those of ordinary skill in the art will know that, With the evolution of the network architecture, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

The technical features involved in the embodiments of this application are described below.

Sending data by broadcasting is a data sending method used in communication systems. In a 5G LAN, data can be sent in a broadcast manner on the user plane of the 5G LAN according to service requirements, or it can be understood as the transmission of broadcast data on the user plane of the 5G LAN.

The application scenario shown in FIG. 3B is used to describe the transmission process of broadcast data on the user plane of the 5GLAN.

Assume that UPF1 first receives the broadcast data, and then sends the broadcast data to the next hop UPF, namely UPF2 and UPF3 through the N19 interface. In order to make all UPFs in the 5GLAN receive the broadcast data, the next hop UPF will continue to forward the broadcast data after receiving the broadcast data, so that UPF2 will send the broadcast data to the next hop UPF connected to it. That is, UPF3 and UPF3 also send the broadcast data to the next hop UPF connected to it, namely UPF2 and UPF4. In this way, UPF2 and UPF3 will receive the broadcast data again, and then continue to forward it to the next hop UPF, thereby forwarding the broadcast data to UPF1, causing loop forwarding problems.

In view of this, an embodiment of the present application provides a data forwarding method to solve the loop forwarding problem in a 5G LAN with a ring architecture or a branch architecture.

In the following, a data forwarding method provided in this application will be introduced in two embodiments (ie, Embodiment 1 and Embodiment 2). Among them, the main difference between the first embodiment and the second embodiment is that the execution subject of determining the interface for forwarding broadcast data is different. In the first embodiment, the UPF network element determines the interface used to forward the broadcast data; and in the second embodiment, the SMF network element determines the interface used to forward the broadcast data.

It should be noted that, in this embodiment of the application, the session management function network element is an SMF network element, and the first user plane function network element is a UPF network element. The first user plane function network element may be one of the multiple UPF network elements shown in FIG. 3A or FIG. 3B. In addition, the UPF network element and the SMF network element can be used as independent physical function entities or logical function entities in practical applications, and there is no restriction here.

Example one

Please refer to FIG. 5, which is a flowchart of a data forwarding method provided by an embodiment of this application. The description of the flowchart is as follows:

S501. The SMF network element determines the path type of the N19 interface between UPF network elements.

In the embodiment of this application, the path types of the N19 interface between UPF network elements include but are not limited to the following two types.

The first type is the loop interface type.

As an example, in Figure 3A, UPF1 ~ UPF4 form a ring, then the N19 interface between any two UPF network elements in UPF1 ~ UPF4 (for example, the N19 interface between UPF1 and UPF2, and between UPF2 and UPF3 The path type of the N19 interface, etc.) is the loop interface type.

As another example, in FIG. 3B, UPF1 to UPF3 form a ring, and the path type of the N19 interface between any two UPF network elements in UPF1 to UPF3 is a loop interface type.

It can be understood that, among the multiple UPF network elements forming a ring, the path type of the N19 interface between any two adjacent UPF network elements is a loop interface type.

The second type is the branch interface type.

As an example, in Figure 3B, UPF4 is only connected to UPF2, and UPF4 does not form a ring with other UPF network elements. Therefore, UPF4 can be understood as a branch of the ring formed by UPF1 to UPF3, and thus UPF4 is connected to it The path type of the N19 interface between the UPF network elements (ie UPF2) is the branch interface type.

It can be understood that the path type of the N19 interface between the branch UPF network element and the UPF network element connected to it is the branch interface type.

In a possible implementation manner, the SMF network element may determine the path type of the N19 interface between the UPF network elements in the 5GLAN according to the network topology structure of the 5GLAN managed by the SMF network element.

Specifically, the SMF network element obtains all UPFs that serve the terminal devices in the 5GLAN, that is, the anchor UPF of the PDU session of all member UEs, and then, according to whether there is an N19 tunnel between these UPFs or whether there is a deployment The physical connection determines the network topology of the 5GLAN user plane. Of course, the SMF network element can also obtain the network topology of the 5GLAN in other ways, which is not limited here.

Then, the SMF network element determines the path type of the N19 interface between the UPF network elements in the 5GLAN according to the acquired network topology. As an example, the SMF network element may first determine the multiple UPF network elements forming a ring in the 5GLAN, and then the path type of the N19 interface between adjacent UPF network elements forming the ring is a loop interface type. Then, it is determined that the remaining UPF network elements that do not form a ring are branch UPF network elements, and the path type of the N19 interface between the branch UPF network element and the UPF network element connected to it is the branch interface type. The network topology obtained by SMF network elements is shown in Figure 3B. Since UPF1～UPF3 form a ring, the N19 interface between UPF1 and UPF2, the N19 interface between UPF1 and UPF3, and the N19 interface between UPF2 and UPF3 The path types are all loop interface types; because UPF4 does not form a ring and UPF4 is connected to UPF3, the path type of the N19 interface between UPF3 and UPF4 is a branch interface type.

For the convenience of description, in the following, the N19 interface between UPF1 and UPF2 is marked as N19 A interface, the N19 interface between UPF2 and UPF3 is marked as N19 B interface, and the N19 interface between UPF1 and UPF3 is marked as N19 C Interface, mark the N19 interface between UPF3 and UPF4 as N19 D interface.

It should be noted that in the embodiment of this application, the path type of the N19 interface is divided into two types, and the loop interface type and the branch interface type are respectively taken as examples for description, but it should not be understood that they are a reference to the embodiment of this application. The limitation of the method, that is, in other embodiments, the path type of the N19 interface can be more than two, and the name of the path type of the N19 interface can also be other names, which is not limited here.

S502. The SMF network element sends an instruction to each UPF network element of the 5GLAN, and each UPF network element of the 5GLAN receives the instruction.

In the embodiment of the present application, the indication is used to indicate the path type of the N19 interface between UPF network elements, and the indication includes the identifier of the N19 interface and the path type of the N19 interface. After the SMF network element determines the path type of the N19 interface between each UPF network element in the 5GLAN, it sends the indication to each UPF network element in the 5GLAN. For the convenience of description, taking the SMF network element sending the first instruction to the first UPF network element as an example, it can be understood that the first UPF network element is one of the UPF network elements included in the 5GLAN managed by the SMF network element, for example, the first UPF network element A UPF network element is any one of UPF1 to UPF4 shown in FIG. 3B. In the embodiment of the present application, the first UPF network element is UPF1 as an example.

Next, the first instruction will be described. In the embodiment of the present application, the first indication may include but is not limited to the following three situations:

The first situation:

The first indication is used to indicate the path type of the N19 interface associated with a UPF network element in the 5GLAN. In this case, the SMF network element may generate an indication corresponding to each UPF network element according to the number of UPF network elements included in the 5GLAN, and then send the generated multiple indications to the corresponding UPF network element. For example, in FIG. 3B, including 4 UPF network elements, the SMF network element can generate 4 indications, which are the first indication, the second indication, the third indication, and the fourth indication, respectively. Among them, the first indication is used to indicate the path type of the N19 interface associated with UPF1, that is, the path type including the N19 A interface and the N19 C interface; the second indication is used to indicate the path type of the N19 interface associated with UPF2, that is Including the path types of the N19 A interface and the N19 B interface; the third indicator is used to indicate the path type of the N19 interface associated with UPF3, that is, the path type including the N19 B interface, the N19 C interface, and the N19 D interface; the fourth indicator is used To indicate the path type of the N19 interface associated with UPF4, that is, the path type including the N19 D interface. Then, the SMF network element sends the first instruction to the fourth instruction to the corresponding UPF network element, for example, the first instruction is sent to UPF1, the second instruction is sent to UPF2, and so on. Since there is only a path type of the N19 interface associated with one UPF in an indication, redundant information in different indications can be reduced, and resources occupied by each indication can be reduced.

In this case, the indications corresponding to each UPF network element (for example, the first indication to the fourth indication) can also be understood as the same indication, and the indication is used to indicate the status of the N19 interface associated with the UPF network element. Path type, but because the SMF network element sends the instruction to different UPF network elements, the instruction is divided into the first instruction to the fourth instruction according to different objects of the instruction sent. In FIG. 5, the SMF network element sends the first instruction to the fourth instruction as an example for description.

The second case:

In order to further simplify the resources occupied by each indication, the first indication may only be used to indicate the interface whose path type is the loop interface type, so that the interface not indicated by the first indication is the branch interface type. In this case, the first indication may only include the identifier of the interface of the loop interface type. For example, the first indication is used to indicate an interface belonging to the loop interface type among the N19 interfaces associated with UPF1, that is, the first indication includes the identifiers of the N19 A interface and the N19 C interface. In the same way, the second indication is used to indicate the interface of the loop interface type among the N19 interfaces associated with UPF2, that is, the second indication includes the identifiers of the N19 A interface and the N19 B interface; the third indication is used to indicate the association with UPF3 The N19 interface belongs to the loop interface type of the interface. Since the N19 D interface is a branch interface type among the N19 interfaces associated with UPF3, the third indication only includes the identifications of the N19 B interface and the N19 C interface.

Of course, the first indication may also be used only to indicate the interface whose path type is the branch interface type. The specific indication method is similar to the interface whose first indication is only used to indicate the loop interface type, and will not be repeated here.

In this case, the identification of the N19 interface may be a number or tunnel information parameters of the N19 interface, etc., which is not limited here.

The third situation:

The first indication is used to indicate the path type of one or more N19 interfaces. For example, the first indication is used to indicate the path type of an N19 interface, and the first indication includes the tunnel information of the N19 interface indicated by it and the path type of the N19 interface. After the UPF network element receives the first indication, it can determine whether the N19 interface indicated by the SMF network element is the N19 interface associated with the UPF network element according to the tunnel information of the N19 interface carried in the first indication. In this case, it can be understood that the N19 interface indicated in the first instruction does not necessarily have an association relationship with the recipient of the first instruction. For example, the first instruction may indicate the path type of the N19A interface and the N19D interface. The path type of the interface. The SMF network element can send the first instruction to UPF1. After receiving the first instruction, UPF1 determines that the tunnel information of one of the N19 interfaces is the same as the tunnel information of the N19A interface, and then determines the N19A interface according to the first instruction The tunnel information of another N19 interface is different from other N19 interfaces in UPF1, so the information related to the N19 interface in the first instruction is ignored.

In the embodiment of the present application, the manner in which the SMF network element sends the first indication may include but is not limited to the following two.

In the first sending mode, the first instruction is carried in the N4 session creation request (or N4 message) and sent.

During the creation of the N4 session, the SMF network element sends the first indication to the first UPF network element. As an example, after receiving the PDU session creation request sent by the terminal, the SMF network element sends a first indication to the UPF network element anchored to the PDU session. For example, the SMF network element determines that the session of the terminal is on the first UPF network. If the element is anchored, the SMF network element sends an N4 session creation request to the first UPF network element, and carries the first indication in the N4 session creation request.

In the embodiment of the present application, the N4 session creation request includes the group-level N4 session creation request of the 5G LAN. Specifically, the SMF network element may send to the first UPF network element the creation request for creating a group-level N4 session, through one or more information elements (IE), to the first UPF network element Indicates the path type of the N19 interface. For example, an extension IE may be added to the creation request, and the extension value of the extension IE may be used to indicate the path type of the N19 interface associated with the first UPF network element.

In the second sending mode, the first indication is carried in the N4 session modification request (or N4 message) and sent.

The SMF network element may also send the first indication to the first UPF network element during the modification process of the N4 session. For example, after the SMF network element determines that the N4 session needs to be modified (for example, it receives the N4 session modification request sent by the PCF network element or the network topology of the 5GLAN user plane is changed), it sends the second to the corresponding UPF network element. One instruction. The manner in which the first indication is carried in the N4 session modification request is similar to that in the first sending manner, and will not be repeated here.

After receiving the first indication, the first UPF network element may determine the path type of the N19 interface associated with the UPF network element according to the first indication.

S503. The SMF network element generates a routing rule corresponding to each UPF network element of the 5GLAN.

In the embodiment of the present application, the routing rule is used to instruct the detected broadcast data to be forwarded to the N19 interface, or it can be understood as the destination address being a broadcast address (for example, a broadcast MAC address or a broadcast IP address (FFFFFF)). N19 interface. For convenience of description, the following takes the SMF network element to generate a routing rule corresponding to the first UPF network element as an example.

It should be noted that the routing rule corresponding to the first UPF network element can be understood as the routing rule of the UE-level and group-level N4 sessions related to the 5GLAN in the first UPF network element, or can be understood as the routing rule belongs to matching To the N4 session where the PDR of the broadcast data is located.

In the embodiment of the present application, the broadcast data may be transmitted from the PDU session of the terminal device or sent by the core network side, so that the routing rules are divided into the following two types according to different sources of the broadcast data.

The first type of routing rule, the routing rule corresponding to the first UPF network element includes detecting broadcast data incoming from the PDU session of the terminal device, and forwarding it to the PDR and FAR of all N19 interfaces on the first UPF network element. In this case, the SMF network element needs to generate the following UL PDR and UL FAR respectively for the N4 session of each terminal device and the N4 session of the group level.

N4 session for each terminal device:

UL PDR: The source interface parameter is set to "access side" or "core side", the tunnel information parameter is set to the tunnel header information of the UE's PDU session on the side of the first UPF network element, and the rule ID of the associated FAR (Rule ID) );

UL FAR: The target interface parameter is set to the value corresponding to the internal interface of the first UPF network element (for example, "5GLAN internal"), and the path type parameter of the outgoing interface is set to non-loop interface type (or can be understood as branch Interface Type).

For example, after the SMF network element receives the PDU session creation request sent by UE1 and UE2, it determines that the UPF network element anchored to UE1 and UE2 is UPF1 shown in Figure 3B, and the SMF network element can generate PDUs with UE1 for UE1. The first UL PDR and the first UL FAR corresponding to the session, and the second UL PDR and the second UL FAR corresponding to the PDU session of the UE2 are generated for the UE2. Among them, the first UL PDR and the second UL PDR both include source interface parameters, tunnel information parameters, and Rule ID. In the first UL PDR, the source interface parameters are set to "access side" or "core side", and the tunnel The information parameter is set to the tunnel header information of UE1's PDU session in UPF1; in the second UL PDR, the source interface parameter is set to "access side" or "core side", and the tunnel information parameter is set to UE2's PDU session in UPF1 The tunnel header information.

Both the first UL FAR and the second UL FAR include the target interface parameter and the path type parameter of the outgoing interface, and each parameter has the same value in the first UL FAR and the second UL FAR, and the target interface parameters can be equal Set to "5GLAN internal", the path type parameters of the outgoing interface are all set to non-loop interface type. In this case, it is also possible to set only one UL FAR, and all UEs anchored to UPF1 use this UL FAR.

For group-level N4 sessions, there are two forms:

The first form:

UL PDR: The source interface parameter is set to the value corresponding to the internal interface of the first UPF network element, the destination address in the Ethernet filter parameter is set to the broadcast address, the path type parameter of the incoming interface is set to the non-loop interface type, and Rule ID of the associated FAR;

UL FAR: The target interface parameter is set to "core side".

For example, after the SMF network element receives the PDU session creation request sent by UE1 and UE2, and determines that UE1 and UE2 belong to 5GLAN group 1, the SMF network element generates UL PDR and UL FAR corresponding to 5GLAN group 1. Among them, the parameters in UL PDR and UL FAR are as described in the first form, and will not be repeated here. It should be noted that if the SMF network element determines that UE1 and UE2 belong to different 5GLAN groups, for example, UE1 belongs to 5GLAN group 1, and UE2 belongs to 5GLAN group 2, then the SMF network element generates corresponding 5GLAN group 1 and 5GLAN group 2 respectively. UL PDR and UL FAR.

The second form:

Different from the first form, in UL FAR, you can also set the path type parameter of the outgoing interface, for example, set the path type parameter of the outgoing interface to all (ALL) or set the loop interface type and Branch interface type.

The second type of routing rule, the routing rule corresponding to the first UPF network element, includes detecting the incoming broadcast data from an N19 interface and forwarding it to the PDR and FAR of the corresponding N19 interface on the first UPF network element. In this case, the SMF network element needs to generate the following DL PDR and DL FAR in the N4 session at the group level:

The first form:

DL PDR: The source interface parameter is set to "core side", the destination address in the Ethernet filter parameter is set to the broadcast address, and the value of the tunnel information parameter is set to the information of the N19 interface (for example, the one connected to the opposite UPF network element). The tunnel header GTP-U TEID of the first UPF network element, and the Rule ID of the associated FAR;

DL FAR: The target interface parameter is set to "core side";

For example, when the first UPF network element is UPF1 as shown in Figure 3B, the SMF network element determines that UPF1 includes two N19 interfaces, namely N19 A interface and N19 C interface, then the SMF network element can generate two DL PDRs for UPF1 And the DL FAR corresponding to each DL PDR, where the first DL PDR is used to detect the broadcast data received through the N19 A interface, and the second DL PDR is used to detect the broadcast data received through the N19 C interface. The value of the tunnel information parameter in one DL PDR is the information of the N19 interface A, that is, the GTP-U TEID of the UPF1 network element; the value of the tunnel information parameter in the second DL PDR is the information of the N19 C interface, that is GTP-U TEID of UPF1 network element. In this case, the values of the target interface parameters in the DL FAR associated with the first DL PDR and the DL FAR associated with the second DL PDR are both set to "core side".

It should be noted that in this form, since the DL PDR does not include the type of the incoming interface, the UPF network element can determine and save it locally according to the tunnel information parameters in the DL PDR and the UPF network element according to the first instruction. The path type of the N19 interface determines the type of the incoming interface. For example, UPF1 determines that the tunnel information in the first DL PDR is the tunnel information of the N19A interface, and the path type of the N19A interface is the loop interface type to determine the incoming interface The type of is the loop interface type, and the same method is used to determine the type of the incoming interface corresponding to the second DL PDR as the loop interface type. Then, UPF network element according to the transmission rules (if the data is received from the interface of the loop interface type, it is only forwarded to the interface of the branch interface type, if the data is received from the interface of the branch interface type, it is forwarded to the interface and ring of other branch interface types. Interface forwarding), determine the type of outgoing interface. For example, it is determined that the outgoing interface of the DL FAR corresponding to the first PDR is a non-loop interface type, and the outgoing interface of the DL FAR corresponding to the second PDR is a non-loop interface type.

The second form:

Different from the first form, in DL PDR, in addition to the content of the first form, it also includes the path type parameter of the incoming interface. The path type parameter of the incoming interface can be a loop interface type or Non-loop interface type.

For example, UPF1 includes two N19 interfaces, namely N19 A interface and N19 C interface. The SMF network element can generate two DL PDRs and a DL FAR corresponding to each DL PDR for UPF1, where each DL PDR is divided by In addition to the content of DL PDR in the first form, it also includes the type of incoming interface. Since both N19A and N19C interfaces are loop interface types, the type of incoming interface in each DL PDR is set to loop Interface Type. In this form, the UPF network element can determine the type of outgoing interface according to the aforementioned transmission rules. For example, it is determined that the outgoing interface of the DL FAR corresponding to the first PDR is a non-loop interface type, and the outgoing interface of the DL FAR corresponding to the second PDR is a non-loop interface type.

As an example, a field (such as a bit) can be added to the source interface parameter of the PDR to indicate the path type of the incoming interface, where "0" indicates the loop interface type, and "1" indicates the non-loop Road interface type.

In this form, the UPF network element directly obtains the type of the incoming interface from the DL PDR.

The third form:

The difference from the first form is that in DL FAR, in addition to the content of the first form, it also includes the path type parameter of the outgoing interface. The path type parameter of the outgoing interface can be ALL or non-loop. Interface Type.

For example, when the first UPF network element is UPF1 shown in Figure 3B, the SMF network element can also set the non-ring value in the outgoing interface parameter of the FAR of the first PDR. Since the N19 A interface is a loop interface type, Then, according to the foregoing transmission rule, the non-loop interface type is set in the outgoing interface parameter of the DL FAR corresponding to the first PDR. In the same way, the SMF network element sets the non-loop interface type in the outgoing interface parameter of the DL FAR corresponding to the second PDR.

As an example, a field (such as a bit) can be added to the target interface parameter of FAR to indicate the path type of the outgoing interface, where "0" means ALL, and "1" means non-loop interface type .

The fourth form:

DL PDR: The source interface parameter is set to "core side", the destination address in the filter parameter is set to the broadcast address, and the value of the tunnel information parameter is set to the information of the N19 interface (for example, the first one connected to the opposite UPF network element) The tunnel header GTP-U TEID of a UPF network element, and the Rule ID of the associated FAR;

DL FAR: The target interface parameter is set to the value corresponding to the internal interface of UPF (for example, "5GLAN internal"), and also includes the path type parameter of the outgoing interface. For example, the path type parameter of the outgoing interface can be a loop interface Type or non-loop interface type. Specifically, the value of the path type parameter of the outgoing interface may be determined by the SMF network element according to the N19 interface that receives the broadcast data. For example, if broadcast data comes in from the N19A interface, and the path type of the N19A interface is the loop interface type, the path type parameter of the outgoing interface is set to the loop interface type.

In this form, the SMF network element also needs to generate the following UL PDR and UL FAR in the group-level N4 session:

UL PDR: The source interface parameter is set to the value corresponding to the internal interface of the first UPF network element, the destination address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR; optional, also includes the incoming The path type parameter of the internal interface of the broadcast data. For example, if the broadcast data is transmitted from the internal interface of the loop interface type, the path type parameter is set to the loop interface type;

UL FAR: The target interface parameter is set to "core side", optionally, it also includes the path type parameter of the outgoing interface, and the path type parameter of the outgoing interface is set to the non-loop interface type. The SMF network element can be set according to the aforementioned transmission rules. The UL PDR and UL FAR in the group-level N4 session are similar to the routing rules in the group-level N4 session in the first type of routing rule described above, and will not be repeated here.

It should be noted that the SMF can use the same manner as described above to generate routing rules corresponding to other UPFs in the 5GLAN, which will not be repeated here.

S504. The SMF network element sends configuration information corresponding to each UPF network element of the 5GLAN, and each UPF network element receives configuration information corresponding to the UPF network element.

In the embodiment of the present application, the configuration information includes the identifier of the N4 session and the routing rule corresponding to the UPF network element. After the SMF network element generates the routing rule corresponding to each UPF network element, the routing rule corresponding to each UPF network element is sent to the corresponding UPF network element. After receiving the routing rule, the UPF network element configures the routing rule in the corresponding N4 session. In an example, the configuration message may be an N4 message.

For ease of description, in FIG. 5, the first configuration information to the fourth configuration information are used to mark the configuration information sent by the SMF network element to different UPF network elements, for example, the configuration sent from the SMF network element to the first UPF network element The information is marked as the first configuration information, and the first configuration information includes the identifier of the N4 session and the routing rule corresponding to the first UPF network element; the configuration information sent by the SMF network element to the second UPF network element is marked as the second configuration Information, the second configuration information includes the identifier of the N4 session and the routing rule corresponding to the second UPF network element, and so on.

It should be noted that if the FAR indicated in the configuration information already exists in the N4 session, the UPF network element can directly associate the PDR indicated in the configuration information with the existing FAR, and the PDR indicated in the configuration information The FAR ID parameter is set to the rule ID (rule ID) of the existing FAR.

S505: The first UE sends the first data packet through the PDU session of the first UE, and the first UPF network element receives the first data packet sent through the PDU session.

In the embodiment of the present application, the destination address of the first data packet is a broadcast address, and the UPF network element receives the first data packet through a PDU session tunnel. The first UE may be a UE anchored to the UPF1 network element, such as UE1.

S506: The first UPF network element determines that the first data packet matches the UL PDR of the N4 session of the first UE, and forwards it to the internal interface of the UPF.

After receiving the first data packet, the first UPF network element executes the matching process between the first data packet and the PDR, detects that the first data packet matches the UL PDR of the N4 session of the first UE, and forwards it to the corresponding UL FAR The internal interface of the first UPF network element.

S507. The first UPF network element receives the first data packet through the internal interface, performs a matching process between the data packet and the PDR, and detects the UL of the N4 session of the first data packet and the group level of the 5GLAN where the first UPF network element is located. PDR match.

S508. The first UPF network element determines a first interface for forwarding the first data packet according to the UL FAR matched with the UL PDR.

When the first UPF network element determines that the first data packet matches the UL PDR of the N4 session at the group level of the first UPF network element, it can determine to forward the first data packet according to the UL FAR associated with the UL PDR The first interface. In the embodiment of this application, for group-level N4 sessions, the SMF network element can configure different forms of routing rules in the first UPF network element, so as to configure different forms of routing in the first UPF network element according to the SMF network element According to the rule, the manner in which the first UPF network element determines the target interface for forwarding the first data packet according to the UL FAR may include but is not limited to the following manners.

The first way is the first form of the routing rule for the group-level N4 session in step S503:

The first UPF network element determines the first interface according to the path type parameter and the transmission rule of the incoming interface in the UL PDR in the group-level N4 session that matches the first data packet.

As an example, in the UL FAR corresponding to the N4 session at the group level, the target interface parameter is "core side", so the first UPF network element determines that the target interface is the N19 interface. In the 5GLAN shown in Figure 3B, if the first data packet whose destination address is the broadcast address is forwarded through all N19 interfaces, there will be a loop forwarding problem. Therefore, in the embodiment of the present application, when the first UPF network When the meta determines to forward the first data packet whose destination address is the broadcast address through the N19 interface, it also needs to filter the N19 interface to determine the first interface that is actually used to forward the first data packet.

Then, the first UPF network element determines the N19 interface that is actually used to forward the first data packet according to the path type parameter of the incoming interface in the UL PDR of the group-level N4 session and the foregoing transmission rule. For example, if the path type of the incoming interface in the UL PDR is a non-loop interface type, the path type of the N19 interface that forwards the first data packet is all types of N19 interfaces, so that the first UPF network element determines that it is actually used The first interface for forwarding the first data packet is all the N19 interfaces associated with the first UPF network element. Since the N19 interfaces associated with the first UPF network element are the N19A interface and the N19C interface, the first UPF network element determines the first One interface is N19A interface and N19C interface.

The second method is the second form of the routing rule for the group-level N4 session in step S503:

The first UPF network element determines the first interface according to the path type parameter of the outgoing interface in the UL FAR corresponding to the group-level N4 session.

As an example, the first UPF network element determines that the path type parameter of the outgoing interface in the UL FAR is set to all (ALL) or set to the loop interface type and branch interface type, and the N19 interface associated with the first UPF network element Are the N19A interface and the N19C interface, so the first UPF network element determines that the first interface actually used to forward the first data packet is the N19A interface and the N19C interface.

S509. The first UPF network element generates a second data packet.

In the embodiment of the present application, the second data packet is obtained by copying the first data packet. When the first UPF network element is forwarding data to the target interface, it executes the data packet copying process to copy the first data packet to obtain the second data packet.

In the embodiment of the present application, the first UPF network element may include, but is not limited to, the following two ways to copy the first data packet.

The first copy method:

When the SMF network element sets the corresponding routing rules for the group-level N4 session, it can set the copy label for copying the data packet in the UL FAR associated with the UL PDR, so that the first UPF network element detects that the data packet matches After reaching the UL PDR of the N4 session at the group level, the first data packet can be copied according to the copy tag in the UL FAR associated with the UL PDR to trigger the execution of the data packet copy process.

The second copy method:

When each UPF network element forwards broadcast data to the target interface, it triggers the copy function of the UPF network element, executes the data packet copy process, and copies the first data packet.

In addition, it should be noted that the number of copies of the first data packet by the first UPF network element is the same as the number of the first interface. Specifically, after the first UPF network element determines the first interface for forwarding the first data packet, it may copy the first data packet according to the number of the first interfaces. For example, when the first UPF network element is UPF1 as shown in FIG. 3B, and the number of first interfaces is two, then UPF1 can duplicate the first data packet in two copies.

S510. The first UPF network element sends a second data packet to the second UPF network element and sends a second data packet to the third UPF network element, and the second UPF network element and the third UPF network element receive the second data packet.

In the embodiment of the present application, the second UPF network element and the third UPF network element are respectively UPF network elements connected to different first interfaces. For example, if the first interface is the N19 A interface and the N19 C interface, the second UPF network element and the third UPF network element are UPF2 and UPF3, respectively. As an example, the second UPF network element is UPF3, and the third UPF network element For UPF2.

S511. The second UPF network element performs a matching process between the data packet and the PDR, and detects that the second data packet matches the DL PDR of the N4 session at the group level.

In the embodiment of the present application, according to the different routing rules configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface, the subsequent execution steps of the method in the embodiment of the present application are different. If the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface is the first to third forms of the second routing rule in step S503, then the The method executes steps S514 to S518. If the routing rule configured in the second UPF network element for detecting broadcast data incoming from the N19 interface is the fourth form of the second routing rule in step S503, then this application is implemented The method in the example executes step S512 to step S518. That is to say, step S512 to step S513 are optional steps. Therefore, these two steps are represented by dotted lines in FIG. 5.

S512. The second UPF network element sends the second data packet to the internal interface of the second UPF network element.

In the DL FAR corresponding to the DL PDR that matches the second data packet, if the target interface parameter is a value corresponding to the internal interface of the UPF, the second UPF network element sends the second data packet to the internal interface of the second UPF network element, At the same time, a non-ring indication can also be transmitted, and the non-ring indication is used to indicate that the interface through which the second data packet is received is a non-loop interface.

S513. The second UPF network element receives the second data packet through an internal interface, performs a matching process between the data packet and the PDR, and detects that the second data packet matches the UL PDR of the group-level N4 session.

It should be noted that the UL PDR is the UL PDR in the fourth form in step S503.

S514: The second UPF network element determines a second interface for forwarding the second data packet.

When the second UPF network element determines that the second data packet matches the PDR of the group-level N4 session of the second UPF network element, it can determine to forward the second data packet according to the transmission rule or the indication in the associated FAR. The second interface of the packet.

If the second data packet is received through the internal interface, that is to say, in step S512, the routing rule configured in the second UPF network element to detect the incoming broadcast data from the N19 interface is the fourth form in step S503 . In this case, the manner in which the second UPF network element determines the second interface may include but is not limited to the following two. Specifically, when the UL PDR of the N4 session at the group level that matches the second data packet includes the path type parameter of the N19 interface of the incoming broadcast data, the second UPF network element is based on the transmission rule and the incoming broadcast data. The path type parameter of the N19 interface determines the second interface; when the UL FAR corresponding to the UL PDR of the group-level N4 session that matches the second data packet includes the path type parameter of the outgoing interface, the second UPF network element transmits The path type parameter of the outbound interface determines the second interface. The specific implementation process is similar to that in step S508, and will not be repeated here.

If the second data packet is received from the N19 interface, that is, in step S512, the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface is the second type of routing in step S503 The first form ~ the third form of rules. In this case, the manner in which the second UPF network element determines the second interface may include but is not limited to the following two.

The first determination method corresponds to the first form in the second routing rule in step S503:

The second UPF network element first determines the interface type of the incoming interface according to the value of the tunnel information parameter in the DL PDR and the second instruction sent in step S502.

Specifically, the second UPF network element obtains the value of the tunnel information parameter in the DL PDR that matches the second data packet. For example, if the value of the tunnel information parameter is the second UPF network element GTP-U TEID, then the first The second UPF network element determines that the second data packet is received through the N19 interface between the first UPF network element and the second UPF network element. Then, according to the second instruction sent by the SMF network element, it is determined that the path type of the N19 interface between the first UPF network element and the second UPF network element is the branch interface type or the loop interface type.

For example, if UPF3 determines that the tunnel information parameter in the DL PDR that matches the second data packet is the GTP-U TEID of UPF3, then UPF3 determines that the incoming interface of the second data packet is the N19 interface between UPF3 and UPF1, that is, N19 C interface. Then, according to the path type of the N19 interface associated with UPF3 indicated in the second indication, for example, the second indication is "N19 The path type of the B interface is a loop interface type, and the path type of the N19 C interface is a loop interface. Type, and N19 The path type of the D interface is the branch interface type", and the path type of the incoming interface of the second data packet is determined to be the loop interface type.

Then, the second UPF network element determines the type of the outgoing interface according to the path type of the incoming interface and the transmission rule. This process is similar to that in step S508, and will not be repeated here. Therefore, the second UPF network element determines that the N19 interface matching the outgoing interface type is the second interface from the multiple N19 interfaces associated with it. For example, if UPF3 determines that the N19 interface of the incoming second data packet is of the loop interface type, it can be known according to the forwarding rule that the type of the outgoing interface is determined to be the branch interface type. The N19 interface associated with UPF3 includes the N19 B interface, the N19 C interface, and the N19 D interface. The N19 interface whose interface type is the branch interface type is the N19 D interface, so UPF3 determines that the N19 D interface is used to forward the second interface. The second interface of the packet.

The second determination method corresponds to the second form in the second routing rule in step S503:

The second UPF network element determines the interface type of the incoming interface according to the value of the path type parameter of the incoming interface in the DL PDR that matches the second data packet. If the path type of the incoming interface in the DL PDR is a circular value, then the type of the incoming interface is determined to be a loop interface type. If the path type of the incoming interface in the DL PDR is a non-circular value, It is determined that the type of the incoming interface is the branch interface type.

For example, a field in the source interface parameter of DL PDR is used to indicate the path type of the interface, where "0" represents a circular value, and "1" represents a non-circular value. When UPF3 detects the DL PDR that matches the second data packet, it determines whether the value of this field in the source interface parameter of the DL PDR is "0". If it is 0, UPF3 determines that the type of the incoming interface is Branch interface type, otherwise, determine the type of incoming interface as loop interface type.

Then, the second UPF network element determines the type of the outgoing interface according to the path type of the incoming interface and the transmission rule. The specific process is similar to that in the first determination method, and will not be repeated here.

The third determination method corresponds to the third form in the second routing rule in step S503:

The second UPF network element determines the second interface according to the value of the path type parameter of the outgoing interface in the DL FAR corresponding to the DL PDR matching the second data packet. If the value of the path type parameter of the outgoing interface in the DL FAR is all, the type of the outgoing interface is determined to be loop interface type or branch interface type, if the value of the path type parameter of the outgoing interface in the DL FAR If it is a non-circular value, it is determined that the type of the outgoing interface is the branch interface type. Then, the second UPF network element determines from the multiple N19 interfaces associated with it that the N19 interface matching the type of the outgoing interface is the second interface.

For example, a field in the target interface parameter of DL FAR is used to indicate the path type of the interface, where "0" means all, and "1" means a non-ring value. When UPF3 detects the DL PDR that matches the second data packet, it determines whether the value of this field in the DL FAR corresponding to the DL PDR is "0", if it is 0, UPF3 determines the type of outgoing interface It is the loop interface type or the branch interface type. Otherwise, the type of the outgoing interface is determined to be the branch interface type. For example, UPF3 determines that the type of the outgoing interface is the branch interface type, and among the N19 interfaces associated with UPF3, only the N19 D interface is the branch interface type, so UPF3 determines that the N19 D interface is the second one used to forward the second data packet. interface.

S515. The third UPF network element determines not to forward the second data packet.

After the third UPF network element receives the second data packet, it also needs to perform steps S512 to S515, which will not be repeated here. In the embodiment of this application, because UPF2 determines that the type of the N19 interface used to forward the second data packet is the branch interface type, and there is no N19 interface of the branch interface type among the N19 interfaces associated with UPF2, UPF2 determines that it is not used Forward the second data packet.

S516: The second UPF network element generates a third data packet.

S517. The second UPF network element sends a third data packet, and the fourth UPF network element receives the third data packet.

In the embodiment of the present application, the second UPF network element is a UPF network element connected to a second interface. For example, if the second interface is an N19 D interface, the fourth UPF network element is UPF4.

S518. The fourth UPF network element determines not to forward the third data packet.

After the fourth UPF network element receives the third data packet, it executes a similar processing procedure as the foregoing second UPF network element (ie, steps S512 to S514, step S516, and step S517), which will not be repeated here.

As an example, UPF4 determines that the type of the third interface used to forward the third data packet is a ring interface type, or an interface of another branch interface type different from the incoming interface. Because UPF4 has no other branch interface type interface, and no ring interface type interface, UPF4 determines not to forward the third data packet.

In the above technical solution, after the UPF network element receives the broadcast data, it can be determined to be used for forwarding according to the path type of the N19 interface set by the SMF network element (for example, loop interface type or branch interface type) and corresponding routing rules. The type of the interface for the broadcast data, and then according to the determined type of interface for forwarding the broadcast data, to determine which interface to forward the broadcast data through, so that loops caused by forwarding broadcast data through all interfaces can be avoided Forwarding problems.

In the embodiment shown in FIG. 5, the process of forwarding broadcast data incoming from the PDU session of the terminal device is described. In actual use, broadcast data can also be passed in from the N19 interface. When broadcast data comes in from the N19 interface associated with the first UPF network element, the execution process of the first UPF network element is similar to the execution process of the second UPF network element in the embodiment shown in FIG. 5, and will not be repeated here. Repeat.

Example two

Please refer to FIG. 6, which is a flowchart of another example of the data forwarding method provided in this embodiment of the application. The description of the flowchart is as follows:

S601. The SMF network element determines the path type of the N19 interface between the UPF network elements.

Step S601 is similar to step S501 and will not be repeated here.

S602. The SMF network element generates a routing rule corresponding to each UPF network element of the 5GLAN.

In the embodiment of the present application, the routing rule is used to instruct the detected broadcast data to be forwarded to the N19 interface, or it can be understood as the destination address being a broadcast address (for example, a broadcast MAC address or a broadcast IP address (FFFFFF)). N19 interface. For the convenience of description, the following takes the SMF network element to generate a routing rule corresponding to the first UPF network element as an example. The first UPF network element can be understood as any UPF network element in the 5GALN.

In the embodiment of the present application, the broadcast data may be transmitted from the PDU session of the terminal device or sent by the core network side, so that the routing rules are divided into the following two types according to different sources of the broadcast data.

The first type of routing rule, the routing rule corresponding to the first UPF network element includes detecting broadcast data incoming from the PDU session of the terminal device, and forwarding it to the PDR and FAR of all N19 interfaces on the first UPF network element. In this case, the SMF network element needs to generate the following UL PDR and UL FAR respectively for the N4 session of each terminal device and the N4 session of the group level.

The routing rule for the N4 session of each terminal device is similar to that in step S503, and will not be repeated here.

For group-level N4 sessions, the generated UL PDR includes: the source interface parameter is set to the value corresponding to the internal interface of the first UPF network element, the target address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR . The UL PDR is used to detect broadcast data received through the internal interface of the first UPF network element.

Then, the SMF network element according to the transmission rules (if the broadcast data is received through the N19 interface of the loop interface type, the broadcast data is only forwarded through the interface of the branch interface type, and if the broadcast data is received from the N19 interface of the branch interface type, then The broadcast data is forwarded to the N19 interface of the other branch interface type and the N19 interface of the loop interface type), and the outgoing interface of the broadcast data received from the internal interface is determined. Since the internal interface is not a loop interface type, the SMF network element determines that it needs to forward the broadcast data received from the internal interface to all N19 interfaces associated with the first UPF network element. Therefore, the SMF network element determines that it corresponds to the UL PDR In the UL FAR, the target interface parameter is set to the tunnel information of all N19 interfaces associated with the first UPF network element.

As an example, the first UPF network element is UPF1 shown in FIG. 3B, and the UL PDR generated by the SMF network element corresponding to UPF1 includes: the source interface parameter is set to the value corresponding to the internal interface of UPF1, and the target address in the filter parameter Set as the broadcast address and the Rule ID of the associated FAR; the generated UL FAR includes: the target interface parameter is set to "core side", the tunnel information parameter is set to the tunnel information of the N19A interface and the tunnel information of the N19C interface.

The second type of routing rule, the routing rule corresponding to the first UPF network element, includes detecting the incoming broadcast data from an N19 interface and forwarding it to the PDR and FAR of the corresponding N19 interface on the first UPF network element. In this case, the SMF network element generates routing rules corresponding to the first UPF network element, including but not limited to the following two forms:

The first form:

After the SMF network element determines the path type of each N19 interface, the SMF network element will determine the routing rule corresponding to the first UPF network element according to the path type and transmission rule of each N19 interface associated with the first UPF network element. For example, if there are N N19 interfaces associated with the first UPF network element, the SMF network element will generate N routing rules for the first UPF network element, and the N routing rules correspond one-to-one with the N N19 interfaces. To detect the incoming broadcast data from each N19 interface.

As an example, the first UPF network element is UPF1 shown in FIG. 3B, and the N19 interface associated with UPF1 is the N19A interface and the N19C interface. The SMF network element can generate two DL PDRs and a DL FAR corresponding to each DL PDR in a group-level N4 session. Among them, the first DL PDR is used to detect broadcast data received through the N19 A interface, and the second DL PDR is used to detect broadcast data received through the N19 C interface.

Regarding the routing rules corresponding to the N19A interface, since the N19A interface is a loop interface type, the SMF network element determines that the broadcast data incoming from the N19A interface should be forwarded to the branch interface type interface, thereby generating a routing rule corresponding to the N19A interface for:

The first DL PDR includes: the source interface parameter is set to the tunnel information of the N19A interface, the destination address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR;

The first DL FAR includes: the target interface parameter is set to "core side", and the tunnel information parameter is set to the tunnel information of the interface whose path type is the branch interface type.

It should be noted that, since there is no branch interface type interface in the N19 interface associated with the UPF1 network element, the SMF network element can set routing rules corresponding to the N19A interface, so that the broadcast data incoming from the N19 interface does not need to be forwarded.

Regarding the routing rules corresponding to the N19C interface, the way the SMF network element generates the routing rules corresponding to the N19C interface is similar to that of the N19A interface, and will not be repeated here.

As another example, the first UPF network element is UPF3 shown in FIG. 3B, and the N19 interfaces associated with UPF3 are N19 B interface, N19 C interface, and N19 D interface. The SMF network element can generate three DL PDRs and a DL FAR corresponding to each DL PDR in the N4 session at the group level of UPF3. The first DL PDR is used to detect the broadcast data received through the N19 B interface. The two DL PDRs are used to detect broadcast data received through the N19 C interface, and the third DL PDR is used to detect broadcast data received through the N19 D interface.

For the routing rules corresponding to the N19B interface, since the N19B interface is a loop interface type, the SMF network element determines that the broadcast data incoming from the N19B interface should be forwarded to the branch interface type interface. The branch interface type of the N19 interface associated with the UPF3 network element is the N19D interface. Therefore, the SMF network element determines that the incoming broadcast data from the N19B interface is forwarded to the N19D interface, thereby generating the routing rules corresponding to the N19B interface:

The first DL PDR includes: the source interface parameter is set to the value corresponding to the N19B interface, the tunnel parameter information parameter is set to the tunnel information of the N19B interface, the destination address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR;

The first DL FAR includes: the target interface parameter is set to "core side", and the tunnel information parameter is set to the tunnel information of the N19D interface.

The routing rules corresponding to the N19C interface are similar to the routing rules corresponding to the N19B interface, and will not be repeated here.

Regarding the routing rules corresponding to the N19D interface, since the N19D interface is a branch interface type, the SMF network element determines the broadcast data received from the N19D interface and forwards it to the N19 interface of other branch interface types and the N19 interface of the loop interface type. , The SMF network element determines that the incoming broadcast data from the N19D interface is forwarded to the N19B interface and the N19C interface, thereby generating the routing rules corresponding to the N19D interface:

The third DL PDR includes: the source interface parameter is set to the value corresponding to the N19D interface, the tunnel parameter information parameter is set to the tunnel information of the N19D interface, the destination address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR;

The third DL FAR includes: the target interface parameter is set to "core side", and the tunnel information parameter is set to the tunnel information of the N19B interface and the tunnel information of the N19C interface.

The second form:

DL PDR: The source interface parameter is set to "core side", the destination address in the filter parameter is set to the broadcast address, and the value of the tunnel information parameter is set to the information of the N19 interface (for example, the first one connected to the opposite UPF network element) The tunnel header GTP-U TEID of a UPF network element, and the Rule ID of the associated FAR;

DL FAR: The target interface parameter is set to the value corresponding to the internal interface of the first UPF network element (for example, "5GLAN internal"), and also includes the path type parameter of the outgoing interface. For example, the path type parameter of the outgoing interface may be a loop interface type or a non-loop interface type. Specifically, the value of the path type parameter of the outgoing interface may be determined by the SMF network element according to the N19 interface that receives the broadcast data. For example, if broadcast data comes in from the N19A interface, and the path type of the N19A interface is the loop interface type, the path type parameter of the outgoing interface is set to the loop interface type.

In this form, the SMF network element also needs to generate the UL PDR and UL FAR associated with the first UPF network element in the N4 session at the group level.

The SMF network element determines that the broadcast data incoming from the ring interface does not need to be forwarded, and the data incoming from the branch interface needs to be transmitted to all other N19 interfaces, thereby generating and corresponding routing rules as:

UL PDR: The source interface parameter is set to the value corresponding to the internal interface of the first UPF network element, the destination address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR, the path of the interface through which the broadcast data is transmitted The type parameter is set to the branch interface type;

UL FAR: The target interface parameter is set to "core side", and the tunnel information parameter is set to tunnel information of all N19 interfaces in the first UPF network element. or,

UL PDR: The source interface parameter is set to the value corresponding to the internal interface of the first UPF network element, the destination address in the filter parameter is set to the broadcast address, and the rule ID of the associated FAR, the path of the interface through which the broadcast data is transmitted The type parameter is set to the ring interface type;

UL FAR: The target interface parameter is set to "core side", and the tunnel information parameter is set to the tunnel information of the interface of the branch interface type. It should be noted that if the SMF network element determines that there is no branch interface type interface in the first UPF network element, the corresponding UL PDR and UL FAR are not set.

As an example, the first UPF network element is UPF3 shown in FIG. 3B, and the N19 interfaces associated with UPF3 are N19 B interface, N19 C interface, and N19 D interface. The SMF network element can generate two UL PDRs and a UL FAR corresponding to each UL PDR in the group-level N4 session of UPF3. The first UL PDR is used to detect the broadcast data received through the branch interface type interface , The second UL PDR is used to detect the broadcast data received through the loop interface type interface.

The first UL PDR includes: the source interface parameter is set to the value corresponding to the internal interface of UPF3, the destination address in the filter parameter is set to the broadcast address, the rule ID of the associated FAR, and the path type parameter of the interface that transmits the broadcast data Set to branch interface type;

The first UL FAR includes: the target interface parameter is set to "core side", and the tunnel information parameter is set to N19 B interface, N19 C interface, and N19D interface tunnel information.

The second DL PDR includes: the source interface parameter is set to the value corresponding to the internal interface of UPF3, the destination address in the filter parameter is set to the broadcast address, the rule ID of the associated FAR, and the path type parameter of the interface that transmits the broadcast data Set to loop interface type;

The second DL FAR includes: the target interface parameter is set to "core side", and the tunnel information parameter is set to the tunnel information of the N19D interface.

It should be noted that the SMF can use the same manner as described above to generate routing rules corresponding to other UPFs in the 5GLAN, which will not be repeated here.

S603. The SMF network element sends configuration information corresponding to each UPF network element of the 5GLAN, and each UPF network element receives configuration information corresponding to the UPF network element.

S604: The first UE sends the first data packet through the PDU session of the first UE, and the first UPF network element receives the first data packet sent through the PDU session.

In the embodiment of the present application, the destination address of the first data packet is a broadcast address, and the UPF network element receives the first data packet through a PDU session tunnel. The first UE may be a UE anchored to the UPF1 network element, such as UE1.

S605. The first UPF network element determines that the first data packet matches the UL PDR of the N4 session of the first UE, and forwards it to the internal interface of the UPF.

Steps S603 to S605 are similar to steps S504 to S506, and will not be repeated here.

S606. The first UPF network element receives the first data packet through an internal interface, performs a matching process between the data packet and the PDR, and detects the UL of the N4 session of the first data packet and the group level of the 5GLAN where the first UPF network element is located. PDR match.

As an example, the first UPF network element is UPF1, and UPF1 determines that the first data packet matches the UL PDR in the first type of routing rule in step S602.

S607: The first UPF network element generates a second data packet.

As an example, the first UPF network element is UPF1, and UPF1 determines that the target interfaces indicated in the UL FAR corresponding to the UL PDR in the first routing rule in step S602 are the N19A interface and the N19C interface, and UPF1 copies the first data Packet, generate two second data packets, and then send the two second data packets to the N19A interface and the N19C interface respectively.

Wherein, the manner of UPF1 copying the first data packet is similar to step S509, and will not be repeated here.

S608. The first UPF network element sends a second data packet to the second UPF network element and sends a second data packet to the third UPF network element, and the second UPF network element and the third UPF network element receive the second data packet.

As an example, after UPF1 generates the second data packet, it forwards the second data packet according to the UL FAR corresponding to the UL PDR matching the first data packet. The target interfaces indicated in the UL FAR are the N19A interface and the N19C interface, and UPF1 sends the second data packet to UPF2 through the N19A interface, and sends the second data packet to UPF3 through the N19C interface.

S609. The second UPF network element performs a matching process between the data packet and the PDR, and detects a PDR matching the second data packet.

In the embodiment of the present application, according to the different routing rules configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface, the subsequent execution steps of the method in the embodiment of the present application are different. If the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface is the second form of the second routing rule in step S602, the method in the embodiment of the present application executes steps S610- Step S615: If the routing rule configured in the second UPF network element for detecting broadcast data incoming from the N19 interface is the first form of the second routing rule in step S602, then the method in this embodiment of the application is executed Steps S612 to S615. In other words, step S610 to step S612 are optional steps. Therefore, these two steps are represented by dotted lines in FIG. 6.

For ease of description, in the following, the second UPF network element is UPF3 as an example.

S610. The second UPF network element sends the second data packet to the internal interface of the second UPF network element.

The second UPF network element determines that the PDR matched by the second data packet is the second form of the second routing rule in step S602, and then according to the DL FAR corresponding to the DL PDR that matches the second data packet, the second data packet Send the internal interface of the second UPF network element and send the ring interface value at the same time. The ring interface value is used to indicate that the path type of the interface through which the second data packet is received is a ring interface type.

S611. The second UPF network element receives the second data packet through an internal interface, performs a matching process between the data packet and the PDR, and detects that the second data packet matches the UL PDR of the group-level N4 session.

As an example, the second UPF network element determines that the PDR matching the second data packet is, in the second form of the second routing rule in step S602, the UL PDR in the routing rule corresponding to the N19C interface.

S612. The second UPF network element generates a third data packet.

As an example, UPF3 determines that the target interface indicated in the UL FAR corresponding to the UL PDR that matches the second data packet is the N19D interface, and UPF3 copies the second data packet to generate a third data packet.

S613. The third UPF network element determines not to forward the second data packet.

The third UPF network element receives the second data packet through the internal interface, performs a matching process between the data packet and the PDR, and cannot detect the PDR matching the second data packet, and thus determines not to forward the second data packet.

S614. The second UPF network element sends the third data packet to the fourth UPF network element according to the UL FAR corresponding to the UL PDR matching the second data packet, and the fourth UPF network element receives the third data packet.

As an example, UPF3 determines that the target interface indicated in the UL FAR corresponding to the UL PDR matching the second data packet is the N19D interface, and then UPF3 sends the third data packet to UPF4 through the N19D interface.

S615. The fourth UPF network element determines not to forward the third data packet.

The fourth UPF network element receives the third data packet through the N19D interface, performs the matching process between the data packet and the PDR, and after matching the DL PDR corresponding to the N19D, it is forwarded to the internal interface. After that, the third data packet cannot be detected. The UL PDR that the packet matches, thereby determining not to forward the third data packet.

In the above technical solution, SMF network elements configure corresponding routing rules for each UPF network element according to the preset transmission rules and the path type of each N19 interface (for example, loop interface type or branch interface type). After the UPF network element receives the broadcast data, it can forward the broadcast data according to the routing rules configured in the UPF network element. In this way, loop forwarding problems caused by forwarding broadcast data through all interfaces can be avoided.

In the above-mentioned embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspective of interaction between terminal devices, user plane function network elements, and session management function network elements. In order to implement the functions in the method provided in the above embodiments of the present application, the user plane function network element and the session management function network element may include a hardware structure and/or software module, and a hardware structure, a software module, or a hardware structure plus a software module Form to achieve the above functions. Whether one of the above-mentioned functions is executed in a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.

FIG. 7 shows a schematic structural diagram of a communication device 700. The communication device 700 may be any one of the first user plane function network element to the fourth user plane function network element, and can implement the first user plane function network element in the method provided in the embodiment of the present application. The function of any one of the fourth user plane function network elements; the communication device 700 may also be capable of supporting any one of the first user plane function network element to the fourth user plane function network element A device that implements the corresponding function in the method provided in the embodiment of the application. The communication device 700 may be a hardware structure, a software module, or a hardware structure plus a software module. The communication device 700 may be implemented by a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

The communication device 700 may include a processing unit 701 and a transceiving unit 702.

The processing unit 701 may be used to perform steps S506 to S509 in the embodiment shown in FIG. 5, or to perform steps S511 to S514 and step S516 in the embodiment shown in FIG. 5, or to perform Step S515 in the illustrated embodiment is used to perform step S518 in the embodiment shown in FIG. 5, or used to perform step S605 to step S607 in the embodiment shown in FIG. 6, or used to perform Steps S609 to S612 in the embodiment shown in FIG. 6 are used to perform step S613 in the embodiment shown in FIG. 6, or used to perform step S615 in the embodiment shown in FIG. 6, and/or used To support other processes of the technology described in this article.

The transceiver unit 702 is used for the communication device 700 to communicate with other modules, and it may be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device that can implement communication.

The transceiver unit 702 can be used to perform step S502, step S504, step S505, and step S510 in the embodiment shown in FIG. 5, or used to perform step S517 in the embodiment shown in FIG. 5, or used to perform step S517 in the embodiment shown in FIG. Steps S603 to S604 and step S608 in the illustrated embodiment are used to perform step S614 in the embodiment shown in FIG. 6 and/or other processes used to support the technology described herein.

Among them, all relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding function module, and will not be repeated here.

FIG. 8 shows a schematic structural diagram of a communication device 800. Wherein, the communication device 800 may be a session management function network element, which can realize the function of the session management function network element in the method provided in the embodiment of the present application; In the method, the session management function is a device that functions as a network element. The communication device 800 may be a hardware structure, a software module, or a hardware structure plus a software module. The communication device 800 may be implemented by a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

The communication device 800 may include a processing unit 801 and a transceiving unit 802.

The processing unit 801 may be used to perform step S501 and step S503 in the embodiment shown in FIG. 5, or used to perform step S601 to step S602 in the embodiment shown in FIG. 6, and/or used to support the steps described herein Other processes of the technology.

The transceiver unit 802 is used for the communication device 800 to communicate with other modules, and it may be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device that can implement communication.

The transceiver unit 802 may be used to perform step S502 and step S504 in the embodiment shown in FIG. 5, or used to perform step S603 in the embodiment shown in FIG. 6, and/or used to support the technology described herein. Other processes.

Among them, all relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding function module, and will not be repeated here.

Figure 9 shows a communication device 900 provided by an embodiment of the application, where the communication device 900 may be any one of the first user plane function network element to the fourth user plane function network element, which can implement The function of any one of the user plane function network element from the first user plane function network element to the fourth user plane function network element in the method provided in the embodiment of the present application; the communication device 900 may also be capable of supporting the first user plane function network element ~A device for any one of the fourth user plane function network elements to implement the corresponding function in the method provided in the embodiment of the present application. Wherein, the communication device 900 may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

In terms of hardware implementation, the foregoing transceiver unit 702 may be a transceiver, and the transceiver is integrated in the communication device 900 to form a communication interface 910.

The communication device 900 includes at least one processor 920, configured to implement or support the communication device 900 to implement the function of the first user plane function network element in the method provided in the embodiment of the present application. Exemplarily, the processor 920 may determine to determine the path type of the transmission path for forwarding the data packet according to the PDR matching the data packet. For details, refer to the detailed description in the method example, which will not be repeated here.

The communication device 900 may also include at least one memory 930 for storing program instructions and/or data. The memory 930 and the processor 920 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 920 may operate in cooperation with the memory 930. The processor 920 may execute program instructions stored in the memory 930. At least one of the at least one memory may be included in the processor.

The communication device 900 may further include a communication interface 910 for communicating with other devices through a transmission medium, so that the device used in the device 900 can communicate with other devices. Exemplarily, the other device may be a terminal. The processor 920 may use the communication interface 910 to send and receive data. The communication interface 910 may specifically be a transceiver.

The specific connection medium between the above-mentioned communication interface 910, the processor 920, and the memory 930 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 930, the processor 920, and the communication interface 910 are connected by a bus 940 in FIG. 9. The bus is represented by a thick line in FIG. 9, and the connection modes between other components are merely illustrative. , Is not limited. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.

In the embodiment of the present application, the processor 920 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

In the embodiment of the present application, the memory 930 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory). For example, random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.

As shown in FIG. 10 is a communication device 1000 provided by an embodiment of this application, where the communication device 1000 may be a network element with a session management function, which can realize the function of a network element with a session management function in the method provided in the embodiment of this application; the communication device 1000 It may also be a device capable of supporting the terminal to realize the function of the session management function network element in the method provided in the embodiment of the present application. Wherein, the communication device 1000 may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

In terms of hardware implementation, the foregoing transceiver unit 802 may be a transceiver, and the transceiver is integrated in the communication device 1000 to form a communication interface 1010.

The communication device 1000 includes at least one processor 1020, configured to implement or support the communication device 1000 to implement the function of the session management function network element in the method provided in the embodiment of the present application. Exemplarily, the processor 1020 may generate a routing rule corresponding to each UPF network element. For details, refer to the detailed description in the method example, which will not be repeated here.

The communication device 1000 may further include at least one memory 1030 for storing program instructions and/or data. The memory 1030 and the processor 1020 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 1020 may cooperate with the memory 1030 to operate. The processor 1020 may execute program instructions stored in the memory 1030. At least one of the at least one memory may be included in the processor.

The communication device 1000 may further include a communication interface 1010 for communicating with other devices through a transmission medium, so that the device used in the device 1000 can communicate with other devices. Exemplarily, the other device may be a terminal. The processor 1020 may use the communication interface 1010 to send and receive data. The communication interface 1010 may specifically be a transceiver.

The embodiment of the present application does not limit the specific connection medium between the communication interface 1010, the processor 1020, and the memory 1030. In the embodiment of the present application, in FIG. 10, the memory 1030, the processor 1020, and the communication interface 1010 are connected by a bus 1040. The bus is represented by a thick line in FIG. 10, and the connection modes between other components are merely illustrative. , Is not limited. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 10, but it does not mean that there is only one bus or one type of bus.

In the embodiment of the present application, the processor 1020 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

In the embodiment of the present application, the memory 1030 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory), For example, random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.

For a schematic structural diagram of a communication system provided by an embodiment of the present application, refer to FIG. 11. Specifically, the communication system 1100 includes a first user plane function network element and a session management function network element, and optionally, a second user plane function The network element and/or the third user plane function network element may also include more user plane function network elements. In FIG. 11, the second user plane function network element and the third user plane function network element are taken as examples.

The first user plane function network element, the second user plane function network element, and the session management function network element are respectively used to implement the functions of the related network elements in FIG. 5 or FIG. 6. For details, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

The embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the first user plane function network element to the fourth user plane function network element in FIG. 5 or FIG. 6 And session management function network element execution method.

The embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the first user plane function network element to the fourth user plane function network element and session in FIG. 5 or FIG. The method of management function network element execution.

The embodiment of the present application provides a chip system, which includes a processor and may also include a memory for implementing the first user plane function network element to the fourth user plane function network element and the session management function network element in the foregoing method Function. The chip system can be composed of chips, or can include chips and other discrete devices.

The methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present invention are generated in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, network equipment, user equipment, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL for short) or wireless (such as infrared, wireless, microwave, etc.). A computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc., integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, hard disk, Magnetic tape), optical media (for example, digital video disc (DVD for short)), or semiconductor media (for example, SSD).

Obviously, those skilled in the art can make various changes and modifications to the application without departing from the scope of the application. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application also intends to include these modifications and variations.

Claims (35)

1. A data forwarding method, characterized in that it comprises:

   The first user plane function network element receives the first data packet;

   The first user plane function network element determines the first path type of the transmission path according to the routing rule matching the first data packet, and the first path type includes one of a loop interface type, a branch interface type, or Multiple, the sending path is used to forward the first data packet to other user plane function network elements;

   The first user plane function network element determines the transmission path according to the first path type.
2. The method according to claim 1, wherein the first user plane function network element determining the transmission path according to the first path type comprises:

   Determining, by the first user plane function network element, a transmission path whose path type is the first path type from at least one transmission path of the first user plane function network element as the transmission path;

   The method also includes:

   The first user plane function network element forwards the first data packet to the other user plane function network element through the transmission path.
3. The method according to claim 1, wherein the first user plane function network element determining the transmission path according to the first path type comprises:

   Determining, by the first user plane function network element, that at least one transmission path of the first user plane function network element does not include a transmission path of the same type as the first path;

   The method also includes:

   The first user plane function network element determines not to forward the first data packet.
4. The method according to any one of claims 1-3, characterized in that,

   The routing rule includes a packet detection rule PDR for detecting the first data packet or a forwarding behavior rule FAR for forwarding the first data packet.
5. The method according to claim 4, wherein the first user plane function network element determines the first path type according to a routing rule matching the first data packet, comprising:

   Determining, by the first user plane function network element, a second path type of the receiving path according to the PDR, and the first user plane function network element receiving the first data packet through the receiving path;

   The first user plane function network element determines the first path type according to the second path type and a preset transmission rule.
6. The method according to claim 5, wherein the first user plane function network element determining the second path type of the receiving path according to the PDR comprises:

   The PDR includes the path type parameter of the receiving path, and the first user plane function network element determines the second path type according to the value of the path type parameter of the receiving path; or,

   The PDR includes the tunnel information parameter of the receiving path, and the first user plane function network element is based on the value of the tunnel information parameter of the receiving path and the path of at least one transmission path of the first user plane function network element Type to determine the second path type.
7. The method according to claim 5 or 6, wherein the preset transmission rule comprises:

   If the path type of the receiving path is the loop interface type, the path type of the sending path is the branch interface type, and if the path type of the receiving path is the branch interface type, then the sending path The path type of the path is the branch interface type and the loop interface type.
8. The method according to claim 4, wherein the first user plane function network element determines the first path type according to a routing rule matching the first data packet, comprising:

   The first user plane function network element determines the first path type according to the value of the path type parameter of the transmission path included in the FAR.
9. The method according to any one of claims 5-8, wherein the method further comprises:

   The first user plane function network element receives a first indication from the session management function network element, where the first indication is used to indicate a path type of at least one transmission path of the first user plane function network element.
10. The method according to any one of claims 1-9, wherein the method further comprises:

    The first user plane function network element receives the routing rule from the session management function network element.
11. A data forwarding method, characterized in that it comprises:

    The session management function network element generates a set of routing rules corresponding to the first user plane function network element according to the path type of the transmission path of the first user plane function network element and the preset transmission rules, and the path of the transmission path The type includes one or more of a loop interface type and a branch interface type, and the preset transmission rule includes that if the path type of the receiving path is the loop interface type, the path type of the sending path is The branch interface type, and if the path type of the receiving path is a branch interface type, the path type of the sending path is the branch interface type and the loop interface type;

    The session management function network element sends the set of routing rules to the first user plane function network element.
12. The method according to claim 11, wherein:

    The set of routing rules includes a packet detection rule PDR for detecting the first data packet and a forwarding behavior rule FAR for forwarding the first data packet.
13. The method according to claim 11 or 12, wherein a set of routing rules corresponding to the first user plane function network element generated by the session management function network element comprises:

    A first PDR, where the first PDR is used to detect the first data packet received from a first N19 path, and the transmission path of the first user plane function network element includes the first N19 path; and,

    A first FAR associated with the first PDR, where the first FAR includes tunnel information of a second N19 path, and the transmission path of the first user plane function network element includes the second N19 path.
14. The method according to claim 13, wherein:

    If the path type of the first N19 path is a loop interface type, the second N19 path is an N19 path whose path type is a branch interface type in the transmission path of the first user plane function network element. The path type of the first N19 path is a branch interface type, and the second N19 path is a N19 path other than the first N19 path in the transmission path of the first user plane function network element.
15. The method according to claim 11 or 12, wherein the session management function network element generating a set of routing rules corresponding to the first user plane function network element comprises:

    A first PDR, where the first PDR is used to detect the first data packet received from a first N19 path, and the transmission path included in the first user plane function network element includes the first N19 path; and,

    A first FAR associated with the first PDR, the first FAR is used to forward the first data packet to the internal interface of the first user plane function network element, and the first FAR includes outgoing The path type parameter of the interface, where the path type parameter of the outgoing interface includes the loop interface type or the branch interface type; and,

    A second PDR, the second PDR is used to detect the first data packet received from the internal interface, and the second PDR includes the path type parameter of the incoming interface; and,

    A second FAR associated with the second PDR, where the second FAR includes tunnel information of a second N19 path, the transmission path of the first user plane function network element includes the second N19 path, and the second FAR The N19 path is one or more of the transmission paths whose path types are the loop interface type and the branch interface type.
16. The method according to claim 15, wherein:

    If the path type of the first N19 path is a loop interface type, the value of the path type parameter of the outgoing interface is a loop interface type, and if the path type of the first N19 path is a branch interface type, then The value branch interface type of the path type parameter of the outgoing interface; and,

    If the path type parameter of the incoming interface is a loop interface type, the second N19 path is an N19 path whose path type is a branch interface type in the transmission path of the first user plane function network element. The path type parameter of the incoming interface is a branch interface type, and the second N19 path is a N19 path other than the first N19 path in the transmission path of the first user plane function network element.
17. The method according to any one of claims 11-16, wherein the method further comprises:

    The session management function network element determines the path type of the transmission path of the first user plane function network element according to the network topology interface of the user plane of the 5G local area network LAN group, and the first user plane function network element belongs to the 5GLAN group.
18. A communication device, characterized in that it comprises a transceiver unit and a processing unit, wherein:

    The transceiving unit is configured to receive a first data packet;

    The processing unit is configured to determine a first path type of a transmission path according to a routing rule matching the first data packet, and the first path type includes one or more of a loop interface type and a branch interface type The sending path is used to forward the first data packet to other user plane function network elements; and the sending path is determined according to the first path type.
19. The device according to claim 18, wherein the processing unit is specifically configured to:

    Determining, from at least one transmission path of the communication device, a transmission path whose path type is the first path type as the transmission path;

    The transceiver unit is also used for:

    Forward the first data packet to the other user plane function network element through the transmission path.
20. The device according to claim 18, wherein the processing unit is specifically configured to:

    Determining that at least one transmission path of the communication device does not include a transmission path of the same type as the first path;

    The processing unit is also used for:

    Determine not to forward the first data packet.
21. The device according to any one of claims 18-20, wherein:

    The routing rule includes a packet detection rule PDR for detecting the first data packet or a forwarding behavior rule FAR for forwarding the first data packet.
22. The device according to claim 21, wherein the processing unit is specifically configured to:

    Determining the second path type of the receiving path according to the PDR, and the communication device receives the first data packet through the receiving path;

    Determine the first path type according to the second path type and a preset transmission rule.
23. The device according to claim 22, wherein the processing unit is specifically configured to:

    The PDR includes the path type parameter of the receiving path, and the processing unit determines the second path type according to the value of the path type parameter of the receiving path; or,

    The PDR includes the tunnel information parameter of the receiving path, and the processing unit determines the second path type according to the value of the tunnel information parameter of the receiving path and the path type of at least one transmission path of the communication device.
24. The device according to claim 22 or 23, wherein the preset transmission rule comprises:

    If the path type of the receiving path is the loop interface type, the path type of the sending path is the branch interface type, and if the path type of the receiving path is the branch interface type, then the sending path The path type of the path is the branch interface type and the loop interface type.
25. The device according to claim 21, wherein the processing unit is specifically configured to:

    The first path type is determined according to the value of the path type parameter of the transmission path included in the FAR.
26. The device according to any one of claims 22-25, wherein the transceiver unit is further configured to:

    A first indication is received from the session management function network element, where the first indication is used to indicate a path type of at least one transmission path of the communication device.
27. The device according to any one of claims 18-26, wherein the transceiver unit is further configured to:

    Receiving the routing rule from the session management function network element.
28. A communication device, characterized in that it comprises a transceiver unit and a processing unit, wherein:

    The processing unit is configured to generate a set of routing rules corresponding to the first user plane function network element according to the path type of the transmission path of the first user plane function network element and a preset transmission rule, and the transmission path The path type includes one or more of a loop interface type and a branch interface type, and the preset transmission rule includes that if the path type of the receiving path is the loop interface type, the path of the sending path The type is the branch interface type, and if the path type of the receiving path is the branch interface type, the path type of the transmission path is the branch interface type and the loop interface type;

    The transceiver unit is configured to send the set of routing rules to the first user plane function network element.
29. The device of claim 28, wherein:

    The set of routing rules includes a packet detection rule PDR for detecting the first data packet and a forwarding behavior rule FAR for forwarding the first data packet.
30. The device according to claim 28 or 29, wherein the processing unit is specifically configured to:

    A first PDR, where the first PDR is used to detect the first data packet received from a first N19 path, and the transmission path of the first user plane function network element includes the first N19 path; and,

    A first FAR associated with the first PDR, where the first FAR includes tunnel information of a second N19 path, and the transmission path of the first user plane function network element includes the second N19 path.
31. The device of claim 30, wherein:

    If the path type of the first N19 path is a loop interface type, the second N19 path is an N19 path whose path type is a branch interface type in the transmission path of the first user plane function network element. The path type of the first N19 path is a branch interface type, and the second N19 path is a N19 path other than the first N19 path in the transmission path of the first user plane function network element.
32. The device according to claim 28 or 29, wherein the processing unit is specifically configured to:

    A first PDR, where the first PDR is used to detect the first data packet received from a first N19 path, and the transmission path included in the first user plane function network element includes the first N19 path; and,

    A first FAR associated with the first PDR, the first FAR is used to forward the first data packet to the internal interface of the first user plane function network element, and the first FAR includes outgoing The path type parameter of the interface, where the path type parameter of the outgoing interface includes the loop interface type or the branch interface type; and,

    A second PDR, the second PDR is used to detect the first data packet received from the internal interface, and the second PDR includes the path type parameter of the incoming interface; and,

    A second FAR associated with the second PDR, where the second FAR includes tunnel information of a second N19 path, the transmission path of the first user plane function network element includes the second N19 path, and the second FAR includes the second N19 path. The N19 path is one or more of the transmission paths whose path types are the loop interface type and the branch interface type.
33. The device according to claim 32, wherein:

    If the path type of the first N19 path is a loop interface type, the value of the path type parameter of the outgoing interface is a loop interface type, and if the path type of the first N19 path is a branch interface type, then The value branch interface type of the path type parameter of the outgoing interface; and,

    If the path type parameter of the incoming interface is a loop interface type, the second N19 path is an N19 path whose path type is a branch interface type in the transmission path of the first user plane function network element. The path type parameter of the incoming interface is a branch interface type, and the second N19 path is a N19 path other than the first N19 path in the transmission path of the first user plane function network element.
34. The device according to any one of claims 28-33, wherein the processing unit is further configured to:

    According to the network topology interface of the user plane of the 5G local area network LAN group, the path type of the transmission path of the first user plane function network element is determined, and the first user plane function network element belongs to the 5GLAN group.
35. A data forwarding system, characterized by comprising a session management network element and a first user plane function network element;

    The session management network element is configured to generate a set of routing rules corresponding to the first user plane function network element according to the path type of the transmission path of the first user plane function network element and a preset transmission rule. The path type of the transmission path includes one or more of a loop interface type and a branch interface type, and the preset transmission rule includes that if the path type of the receiving path is the loop interface type, the sending path The path type of is the branch interface type, and, if the path type of the receiving path is the branch interface type, the path type of the sending path is the branch interface type and the loop interface type; and Sending the set of routing rules to the first user plane function network element, wherein the set of routing rules includes routing rules matching the first data packet;

    The first user plane function network element is configured to receive a first data packet; and determine a first path type of a transmission path of the first data packet according to a routing rule matching the first data packet, and The first path type includes one or more of the loop interface type and the branch interface type, and the transmission path of the first data packet is used to forward the first data packet to other user plane function network elements; And determining the sending path of the first data packet according to the first path type.

Images