CN112312510B

CN112312510B - Data forwarding method, device and system

Info

Publication number: CN112312510B
Application number: CN201910696555.7A
Authority: CN
Inventors: 袁立平; 朱强华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-07-30
Filing date: 2019-07-30
Publication date: 2022-09-23
Anticipated expiration: 2039-07-30
Also published as: WO2021018242A1; CN112312510A

Abstract

In the method, after receiving a first data packet, a first user plane function network element determines a first path type of a sending path for forwarding the first data packet to other user plane function network elements according to a routing rule matched with the first data packet, wherein the first path type comprises one or more of a loop interface type and a branch interface type, and then the first user plane function network element determines the sending path according to the first path type. When the first user plane function network element forwards the data packet, the first user plane function network element only forwards the data packet through the transmission path of the specific path type, that is, when a certain transmission path is different from the specific path type, the first user plane function network element does not forward the data packet from the transmission path, so that the problem of loop forwarding caused by forwarding the data packet through all the transmission paths of the first user plane function network element can be avoided.

Description

Data forwarding method, device and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data forwarding method, apparatus, and system.

Background

Fifth generation mobile communication system local area network (5) ^th Generation local area network, 5G LAN) service is a service provided by a 5G system, and is capable of providing private communication of an Internet Protocol (IP) type or an ethernet (ethernet) type for terminals belonging to the same LAN group. For example, devices in a factory form a LAN group, and devices belonging to the LAN group may send ethernet packets or IP packets to each other.

There is a case where a networking architecture of a plurality of User Plane Function (UPF) network elements constituting the 5GLAN may be a ring architecture or a branch architecture. Thus, when broadcasting data is transmitted in the 5GLAN of the ring architecture or the branch architecture, there may be a loop forwarding problem.

Disclosure of Invention

The embodiment of the application provides a data forwarding method, a data forwarding device and a data forwarding system, which are used for solving the problem of loop forwarding in a 5GLAN of a ring architecture or a branch architecture.

In a first aspect, a method for forwarding data is provided, in which after a first user plane functional network element receives a first data packet, a first path type of a transmission path for forwarding the first data packet to another user plane functional network element is determined according to a routing rule matched with the first data packet, where the first path type includes one or more of a loop interface type and a branch interface type, and then the first user plane functional network element determines the transmission path according to the first path type.

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

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

In one 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 network element determines not to forward the first data packet.

In the above technical solution, if the first user plane function network element is capable of determining 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, so that a 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 one possible design, the routing rule includes a packet detection rule PDR for detecting the first packet or a forwarding behavior rule FAR for forwarding the first packet.

In the above solution, the first data packet may be a data packet whose destination address is a broadcast address. Because the problem probability of loop forwarding is high in the process of forwarding the data packet with the broadcast address as the destination address, the forwarding method can be used in the forwarding scene of the data packet with the broadcast address as the destination address.

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

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

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

and if the PDR comprises the tunnel information parameter of the receiving path, the first user plane function network element 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 first user plane function network element.

In the above technical solution, the second path type may be determined in different manners according to different parameters carried in the PDR, so that flexibility of the scheme may be increased.

In one 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, the path type of the sending path is the branch interface type and the loop interface type.

The preset transmission rule is only an example, and those skilled in the art may set other transmission rules, which is not limited herein.

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

In the above technical solution, the first user plane functional network element may directly determine the first path type according to the parameter in the FAR, and the implementation manner is simple.

In one possible design, the first user plane function network element may receive, from a session management function network element, a first indication indicating a path type of at least one transmission path of the first user plane 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, so that the accuracy of the path type of the at least one transmission path can be ensured.

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

In a second aspect, a method for forwarding data is provided, in which a session management function network element first generates a set of routing rules corresponding to a transmission path of a first user plane function network element according to a path type of the transmission path and a preset transmission rule, where 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 a receiving path is the loop interface type, the path type of a 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, the path type of each transmission path of the first user plane function network element is already considered, for example, when the path type of one transmission path in the first user plane function network element is a loop interface type, the routing rule corresponding to the transmission path will instruct that the data packet received from the transmission path is forwarded through the transmission path of the branch interface type, but not through the transmission path of the loop interface type, so that the problem of loop forwarding caused by forwarding the data packet through all transmission paths of the first user plane function network element can be avoided.

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

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

the first mode is as follows:

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

a first FAR associated with the first PDR, the first FAR comprising tunnel information for a second N19 path, the transmission path of the first user plane function network element comprising the second N19 path.

Specifically, 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, and if the path type of the first N19 path is a branch interface type, the second N19 path is an N19 path other than the first N19 path in the transmission path of the first user plane function network element.

The second mode is as follows:

the set of routing rules includes a first PDR configured to detect the first packet received from a first N19 path, the transmission path included in the first user plane function network element including the first N19 path; and the number of the first and second groups,

a first FAR associated with the first PDR, the first FAR configured to forward the first packet to an internal interface of the first user plane function network element, the first FAR including a path type parameter of an outgoing interface, wherein the path type parameter of the outgoing interface includes the ring interface type or the branch interface type; and the number of the first and second groups,

a second PDR for detecting the first data packet received from the internal interface, the second PDR including a path type parameter of an incoming interface; and the number of the first and second groups,

a second FAR associated with the second PDR, the second FAR including tunnel information for a second N19 path, the transmission path for the first user plane function network element including the second N19 path, the second N19 path being one or more of transmission paths with path types of the ring interface type and the branch interface type.

Specifically, if the path type of the first N19 path is a loop interface type, the path type parameter of the outgoing interface takes a value of a loop interface type, and if the path type of the first N19 path is a branch interface type, the path type parameter of the outgoing interface takes a value of a branch interface type; and the number of the first and second groups,

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, and if the path type parameter of the incoming interface is a branch interface type, the second N19 path is another N19 path except 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 may determine a set of routing rules corresponding to the first user plane function network element in multiple ways, which may increase flexibility of the scheme.

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

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

In a third aspect, a communication device is provided, where the communication device includes a processor configured to implement the method performed 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, so as to implement any one of the methods performed by the first user plane function network element in the first aspect. The communication device may also include a transceiver for the communication device to communicate with other devices. Illustratively, the other device is a session management function network element.

In a fourth aspect, an embodiment of the present application provides a communication apparatus, including: a transceiving unit for receiving a first data packet; a processing unit, configured to determine a first path type of a sending path according to a routing rule matched with the first data packet, where the first path type includes one or more of a loop interface type and a branch interface type, and the sending path is used to forward the first data packet to other user plane functional network elements; and determining the sending path according to the first path type.

In addition, the communication apparatus provided in the fourth aspect may be configured to execute the method corresponding to the first user plane function network element in the first aspect, and for implementation manners that are not described in detail in the communication apparatus provided in the fourth aspect, reference may be made to the foregoing embodiments, and details are not described here again.

In a fifth aspect, a communication device is provided, which includes a processor for implementing the method performed by the session management function network element in the second 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, so as to implement any one of the methods performed by the session management function network element in the second aspect. The communication device may also include a transceiver for the communication device to communicate with other devices. Illustratively, the other device is a first user plane function network element.

In a sixth aspect, an embodiment of the present application provides a communication apparatus, including: a processing unit, configured to generate a set of routing rules corresponding to a first user plane function network element according to a path type of a transmission path of the first user plane function network element and a preset transmission rule, where 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 reception 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 reception path is the branch interface type, the path type of the transmission path is the branch interface type and the loop interface type; a transceiver unit, configured to send the set of routing rules to the first user plane function network element.

In addition, the communication apparatus provided in the sixth aspect may be configured to execute the method corresponding to the session management function network element in the second aspect, and for implementation manners not described in detail in the communication apparatus provided in the sixth aspect, reference may be made to the foregoing embodiments, and details are not described here again.

In a seventh aspect, an embodiment of the present application further provides a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the method performed by the first user plane function network element in the first aspect or the session management function network element in the second aspect.

In an eighth aspect, this application further provides a computer program product, which includes instructions that, when run on a computer, cause the computer to perform the method performed by the first user plane function network element in the first aspect or the session management function network element in the second aspect.

In a ninth aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor and may further include a memory, and is configured to implement the method executed by the first user plane function network element in the first aspect or the session management function network element in the second aspect. The chip system may be formed by a chip, and may also include a chip and other discrete devices.

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

Advantageous effects of the third to tenth aspects and their implementations described above reference may be made to the description of the method of the first aspect and its implementations or the advantageous effects of the method of the first aspect and its implementations.

Drawings

Fig. 1 is a diagram of an exemplary network architecture for a communication system to which the present application is applicable;

FIG. 2 is a diagram of a specific network architecture suitable for use in the present application;

FIG. 3A is a diagram illustrating an example of an application scenario according to an embodiment of the present application;

FIG. 3B is a diagram illustrating another example of an application scenario according to an embodiment of the present application;

fig. 4A is a flowchart of an example of an UPF network element internal forwarding flow;

fig. 4B is a flowchart of another example of an internal forwarding flow of a UPF network element;

fig. 5 is a flowchart of an example of a data forwarding method provided in an embodiment of the present application;

fig. 6 is a flowchart of another example of a data forwarding method provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of another communication device provided in the embodiment of the present application;

fig. 9 is a schematic structural diagram of another communication device provided in the embodiment of the present application;

fig. 10 is a schematic structural diagram of another communication device provided in the embodiment of the present application;

fig. 11 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

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

Referring to fig. 1, a network architecture diagram of an example of a communication system to which the present application is applicable is shown. 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 (RAN). In the network architecture, terminals, AN, and cores are main parts constituting the network architecture. For the network elements in the AN and the Core, the network elements can be logically divided into two parts, namely a user plane and a control plane, wherein the control plane is responsible for management of the mobile network, and the user plane is responsible for transmission of service data. For example, in the network architecture shown in fig. 1, the NG2 reference point is located between the RAN control plane and the Core control plane, the NG3 reference point is located between the RAN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the DN.

In the network architecture shown in fig. 1, a terminal, which is also referred to as a terminal equipment (terminal equipment), a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device having a wireless transceiving function, and is an entry for a mobile user to interact with a network, and is capable of providing basic computing capability and storage capability, displaying a service window to the user, and receiving an input operation of the user. In a 5G communication system, a terminal establishes signal connection and data connection with AN using a new air interface technology, thereby transmitting a control signal and service data to a network.

The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). For example, the terminal may include a mobile phone (or "cellular" phone), a computer with a mobile terminal, a portable, pocket, hand-held, computer-included or vehicle-mounted mobile device, a smart wearable device, and the like. For example, Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like.

Alternatively, the terminal may also include limited devices, such as devices with lower power consumption, or devices with limited storage capability, or devices with limited computing capability, etc. Examples of information sensing devices include bar codes, Radio Frequency Identification (RFID), sensors, Global Positioning Systems (GPS), laser scanners, and the like.

By way of example and not limitation, in the embodiments of the present application, the smart wearable device is a generic term for intelligently designing daily wearing by applying wearable technology, and developing wearable devices, such as glasses, gloves, watches, clothes, shoes, and the like. The smart wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The intelligent wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. Generalized intelligent wearable device includes that the function is full, size is big, can not rely on the smart mobile phone to realize complete or partial function, for example: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets, smart helmets, smart jewelry and the like for monitoring physical signs.

Alternatively, the terminal may be a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (drive), a wireless terminal in remote medical supply (remote), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like.

In the network architecture shown in fig. 1, the AN is similar to a (radio) access network (R) AN device in a conventional communication network, and for example, includes a base station (e.g., AN access point), which is deployed at a position close to a terminal, and provides a network access function for authorized users in a specific area, and can determine transmission tunnels of different qualities according to a level of the user, a service requirement, and the like to transmit user data. The AN can manage and reasonably utilize own resources, provide access service for the terminal according to needs, and is responsible for forwarding control signals and service data between the terminal and the Core.

In the network architecture shown in fig. 1, Core is responsible for maintaining subscription data of a mobile network, managing network elements of the mobile network, and providing functions such as session management, mobility management, policy management, security authentication, and the like for a terminal. For example, when the terminal is attached, the network access authentication is provided for the terminal; when a terminal has a service request, network resources are allocated to the terminal; updating network resources for the terminal when the terminal moves; when the terminal is idle, a fast recovery mechanism is provided for the terminal; when the terminal is detached, releasing network resources for the terminal; when the terminal has service data, a data routing function is provided for the terminal, such as forwarding uplink data to the DN, or receiving downlink data from the DN and forwarding to the AN.

In the network architecture shown in fig. 1, the DN is a data network that provides service to subscribers. In the actual communication process, the client is usually located at the terminal, and the server is usually located at the DN. The DN may be a private network, such as a local area network, or an external network not controlled by an operator, such as the Internet, or a private network co-deployed by an operator, such as a network providing an IP multimedia network subsystem (IMS) service.

Please refer to fig. 2, which is a schematic diagram of a specific network architecture applicable to the present application. The network architecture is a 5G network architecture. The network element in the 5G architecture includes a terminal, a Radio Access Network (RAN), and a Data Network (DN), and in fig. 2, the terminal is taken as User Equipment (UE) as an example. In addition, the network architecture also comprises a core network element, wherein the core network element comprises a UPF network element and a control plane function network element. Specifically, the control plane function network element includes, but is not limited to, an access and mobility management function (AMF) network element, an SMF network element, an authentication server function (AUSF) network element, an Application Function (AF) network element, a Unified Data Management (UDM) network element, a policy control function (policy control function) network element, a network open function (network) network element, a NF Repository Function (NRF) network element, and a Network Slice Selection Function (NSSF) network element.

It should be noted that, in a conventional core network architecture, a point-to-point communication mode is adopted between control plane function network elements, that is, interface communication between control plane function network elements adopts a set of specific messages, and control plane function network elements at two ends of an interface can only use the set of specific messages for communication. In the 5G core network architecture, the control plane adopts a service architecture, that is, the interaction between the control plane functional network elements adopts a service call mode, and the control plane functional network elements open services to other control plane functional network elements for the other control plane functional network elements to call.

The functions of each network element in the network architecture shown in fig. 2 are described in detail below. Since the functions of the UE, the (R) AN, and the DN have been introduced in the description related to the network architecture shown in fig. 1, the following description focuses on the functions of the network elements of the respective core networks.

The UPF network element is a functional network element of a user plane, and is mainly responsible for connecting an external network, and includes related functions of a Serving Gateway (SGW) and a packet data network gateway (PDN-GW) of Long Term Evolution (LTE). Specifically, the UPF may perform user packet forwarding according to the routing rule of the SMF, such as sending uplink data to the DN or other UPFs; the downlink data is forwarded to other UPFs or RANs.

The AMF network element is responsible for access management and mobility management of the UE, such as state maintenance of the UE, reachability management of the UE, forwarding of a non-mobility management access stratum (MM NAS) message, and forwarding of a Session Management (SM) N2 message. In practical application, the AMF network element can implement a mobility management function in the MME in the LTE network framework, and can also implement an access management function.

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

And the AUSF network element is used for executing the safety authentication of the UE.

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

The UDM network element may store subscription information for the UE.

The PCF network element is used for performing user policy management, and is similar to a Policy and Charging Rules Function (PCRF) network element in LTE, and is mainly responsible for generating policy authorization, quality of service and charging rules, generating routing rules for corresponding rules through the SMF network element, and issuing the routing rules to the UPF network element, thereby completing installation of corresponding policies and rules.

The NEF network element is configured to open a network function to a third party in a manner of an Application Programming Interface (API).

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

And the NSSF network element is used for selecting a network slice for the UE.

In the network architecture shown in fig. 2, the SMF network element is further configured to manage local area network communication for the UEs in the group.

In the network architecture shown in fig. 2, network elements related to the present application mainly include: UPF and SMF.

Next, an application scenario of the present application is described. The method and the device are mainly applied to the scene that the 5G system provides 5GLAN services.

Please refer to fig. 3A, which is a schematic diagram illustrating an example of a user plane architecture for a 5GLAN service according to the present application. Wherein, UPF 1-UPF 4 belong to a 5 GLAN. The UE 1-UE 4 are respectively connected with a UPF network element in the 5GLAN through a RAN. In fig. 3A, a UE1 is connected with a UPF1, a UE2 is connected with a UPF2, a UE3 is connected with a UPF3, and a UE4 is connected with a UPF4, so that a corresponding User Plane (UP) of 5GLAN is accessed through a UPF network element. The user plane of the 5GLAN may communicate with existing LANs among the DNs over an N6 interface. Alternatively, the user plane of the 5GLAN may also be connected through N19 between the UPFs (e.g., UPFs 1 to UPF4) in the 5GLAN, and associate Protocol Data Unit (PDU) sessions (sessions) of different UEs, thereby implementing private communication between UEs. In fig. 3A, the UPF1 is connected to the UPF2 and the UPF4, respectively, and the UPF3 is connected to the UPF2 and the UPF4, respectively, so that the UPFs 1 to 4 form a ring-shaped structure.

Please refer to fig. 3B, which is a schematic diagram illustrating another example of the user plane architecture of the 5GLAN service according to the present application. Unlike fig. 3A, in fig. 3B, the UPFs 1-3 form a ring-shaped architecture, the UPF4 is connected only with the UPF2, and the UPF4 can be understood as a branch of the UPF2, so that the UPFs 1-4 form a branch architecture.

The numbers of UPFs, RANs and UEs in fig. 3A and 3B are only examples, and in practical applications, the user plane architecture of the 5GLAN service provided by the present application may serve more terminals and may include more UPFs. Further, in the user plane architecture of the 5GLAN service as shown in fig. 3A and 3B, although the UPF, the UE, and the DN are shown, the user plane architecture of the 5GLAN service may not be limited to include the above. For example, an SMF network element, a PCF network element, a device for carrying a virtualized network function, a wireless relay device, and the like may also be included. These are obvious to one of ordinary skill in the art and are not described in detail herein.

It should be noted that the technical term "5 GLAN" in the present application may be used interchangeably with "5G LAN-type (type) service", "5G LAN-Virtual Network (VN)" or "5G VN".

To facilitate understanding of the schemes of the embodiments of the present application by those skilled in the art, technical terms referred to in the present application will be described below.

1) N4 sessions, including N4 sessions at the UE level and N4 sessions at the group (group) level.

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 a Protocol Data Unit (PDU) session when creating the PDU session (session) of the UE, which may also be referred to as a UE-level N4 session (in this application, a UE-level N4 session and an N4 session corresponding to the PDU session may be used interchangeably). For example, in fig. 3B, the UE1 is connected with the UPF1 through the RAN1, and the SMF may instruct the UPF1 to create an N4 session corresponding to the PDU session of the UE1 when creating the PDU session of the UE 1. The routing rules in the UE-level N4 session may be used to detect and forward data related to this UE. And when the SMF receives a PDU session deletion request of the UE, triggering the UPF network element to delete the N4 session corresponding to the PDU session.

For convenience of illustration, the N4 session corresponding to the PDU session is distinguished below by "identity of the UE," e.g., the N4 session corresponding to the PDU session of the UE1 may be referred to as the N4 session of the UE1, and so on.

In order to support communication between different UPF network elements and communication between UPF network elements and DNs in a 5G ran service, the SMF network element further needs to create a group-level N4 session for the corresponding 5G VN group (or 5G ran) at each UPF network element providing the 5G ran service, the routing rules in the group-level N4 session are used to detect data belonging to any one UE in the 5G VN group (which can be understood as data belonging to the 5G VN group) and forward data belonging to the 5G VN group, wherein forwarding data belonging to the 5G VN group may include forwarding across UPF network elements (different UPF network elements in a 5G ran group), or forwarding through N6 tunnel or forwarding locally. The N4 session corresponding to the group and the N4 session corresponding to the tunnel may be understood as being group-level N4 sessions in the present application. For example, in fig. 3A, UEs 1-4 belong to a 5-g lan, then the SMF network element creates a group-level N4 session for this 5-g lan at each UPF network element. The SMF network element creates a group level N4 session corresponding to the 5g lan when creating a first PDU session established to the 5g lan, and deletes a group level N4 session corresponding to the 5g lan when releasing a last PDU session to the 5g lan.

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 the PDU session of each UE. And, a UPF network element may include one or more group-level N4 sessions. The number of N4 sessions is not limited by the present application.

2) Routing rules, in the context of an N4 session, are used to detect and forward packets, and include an uplink packet detection rule (UL PDR) and an uplink forward action rule (UL FAR) associated with the UL PDR, a downlink packet detection rule (DL PDR) and a DL FAR associated with the DL PDR. The PDRs (UL PDRs and DL PDRs) are used to detect data transmitted from the outside to the UPF network element or data forwarded from an internal interface of the UPF network element, and the FARs (UL FARs and DL FARs) are used to instruct the UPF network element to perform actions such as forwarding, copying, buffering, discarding, notifying and the like on the detected data. When the SMF network element instructs the UPF to create the N4 session, a corresponding routing rule is set for the N4 session. The data incoming from the outside can be understood as data received by the UPF network element through the GTP-U tunnel or the N6 interface.

For an N4 session corresponding to a PDU session:

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

The UL FAR associated with the UL PDR includes target interface parameters for passing packets matching the UL PDR to the target interface. The SMF sets the value of the target interface parameter to a value corresponding to the internal interface of the UPF (e.g., "5 GLAN internal"). It will be appreciated that the UL FAR in N4 session corresponding to a PDU session is used to forward packets matching the UL PDR in this N4 session locally 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 parameters of the external tunnel for egress of 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 parameter of the external tunnel sets the tunnel information of the PDU session (e.g., the tunnel header GTP-U TEID of the PDU session on the AN or UPF network element). It will be appreciated that the DL FAR in the N4 session corresponding to the PDU session is used to egress packets matching the DL PDR in the N4 session to the designated PDU session tunnel.

For group-level N4 sessions:

the UL PDR specifically includes source interface parameters, filter parameters.

The UL FAR associated with the UL PDR includes target interface parameters and/or parameters of the outer tunnel for forwarding packets matching the UL PDR to the target interface. The SMF sets the value of the target interface parameter to "core side", and sets the value of the parameter of the external tunnel to the information of the N19 tunnel (for example, the tunnel header GTP-U TEID of the opposite-end UPF connected to the UPF). It will be appreciated that the UL FAR in N4 session at group level is used to forward packets matching the UL PDR in N4 session at group level to the N19 tunnel where the UPF is connected to 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 for egress of data packets matching the DL PDR to the target interface. The value of the target interface parameter of the SMF is set to a value (for example, "5 global") corresponding to the internal interface of the UPF. It will be appreciated that the DL FAR in the group level N4 session is used to forward packets matching the DLPDR in the group level N4 session locally to the UPF's internal interface.

3) And matching the data packet with the PDR.

When the UPF network element receives a packet, the packet is detected, and it is determined that the packet matches the PDR (or the packet may be successfully matched to the PDR, or the PDR may be successfully matched to the packet). The method specifically comprises the following four matching processes:

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

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

(3) And detecting the data packet according to the interface information of the incoming data packet and the packet 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 N4 session at the group level match one by one, the UL PDR of the N4 session at the group level is successfully matched to the incoming data packet.

(4) The packet is detected based on the interface information of the incoming packet and/or the N19 tunnel information of the incoming packet. If the interface information of the incoming packet, and/or the tunnel information of the incoming packet, matches the corresponding parameters in the DL PDR of the N4 session at the group level one-to-one, the DL PDR of the N4 session at the group level is successfully matched to the incoming packet.

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

4) And forwarding the data packet based on the PDR and the FAR in the N4 session.

Please refer to fig. 4A-4B, which are schematic diagrams illustrating packet forwarding based on PDR and FAR. Fig. 4A and 4B include UPF1 and UPF2, where UE1 to UE2 are connected to UPF1, UE3 is connected to UPF2, and UE1 to UE3 are 5G VN groups (groups 1). The UPF1 includes N4 sessions for UE1, N4 sessions for UE2, and N4 sessions for group 1.

A first forwarding procedure, please refer to fig. 4A, is an internal forwarding procedure of a UPF network element:

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

(2) The UPF1 receives the packet 1, performs a packet to PDR matching process, and detects that the packet 1 matches the UL PDR of the N4 session for the UE 1.

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

(4) The UPF1 receives the packet transmitted over the internal interface, performs a matching procedure of the packet with the PDR, and detects that the packet matches the DL PDR of the N4 session of the UE 2.

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

Referring to fig. 4B, a second forwarding procedure is a forwarding procedure across the UPF network element:

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

(2) The UPF1 receives the packet 2, performs a packet to PDR matching process, and detects that the packet 2 matches the UL PDR of the N4 session for the UE 1.

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

(4) The UPF1 receives the packet 2 transmitted over the internal interface, performs a matching process of the packet 2 with the PDR, and detects that the packet 2 matches the UL PDR of the N4 session of group 1.

(5) The UPF1 obtains the UL FAR associated with the UL PDR of the N4 session of group1, determines the N19 tunnel between the UPF1 and the UPF2, and then tunnels the packet 2 to the UPF2 via the N19 tunnel.

(6) The UPF2 receives the packet 2 transmitted through the N19 tunnel, performs a matching procedure of the packet 2 with the PDR, and detects that the packet 2 matches the DL PDR of the N4 session of group 1.

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

(8) The UPF2 receives packet 2 transmitted over the internal interface, performs a matching procedure of packet 2 with the PDR, and detects that packet 2 matches the DL PDR of the N4 session of the UE 3.

(9) The UPF2 obtains the DL FAR associated with the DL PDR of the N4 session of the UE3, determines the tunnel information of the PDU session of the UE3, and then sends the data packet 2 to the PDU session of the UE3, so that the UE3 receives the data packet 2 through the PDU session of the UE 3.

5) The internal interface of the UPF is a virtual port or a specific port in the UPF network element, and is used for locally forwarding the received data packet by the UPF network element. The local forwarding to the internal interface of the UPF network element means that the UPF network element receives the data packet again at the internal interface, so that the data packet is detected by the UPF network element again, and is classified and matched to the corresponding routing rule, and forwarded to the correct path. The UPF network element may decapsulate the packet with an external tunnel header prior to re-detection. Optionally, new external tunnel header information may be encapsulated for the data packet, and 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 the present application, "a plurality" means two or more, and in view of this, a plurality may also be understood as "at least two" in the embodiments of the present application. "at least one", is to be understood as meaning one or more, for example one, two or more. For example, including at least one means 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 including may 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, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" generally indicates that the preceding and following related objects are in an "or" relationship, unless otherwise specified. The terms "system" and "network" in the embodiments of the present application may be used interchangeably.

Unless stated to the contrary, the embodiments of the present application refer to the ordinal numbers "first", "second", etc., for distinguishing between a plurality of objects, and do not define the order, sequence, priority, or importance of the plurality of objects.

In addition, the user plane architecture of the 5GLAN service described in this embodiment of the present application is for more clearly explaining the technical solution of this embodiment of the present application, and does not constitute a limitation to the technical solution provided in this embodiment of the present application, and as a person having ordinary skill in the art knows, along with the evolution of the network architecture, the technical solution provided in this embodiment of the present application is also applicable to similar technical problems.

The technical features related to the embodiments of the present application are described below.

Data transmission by a broadcast method is one of data transmission methods used in a communication system. In 5GLAN, data may be transmitted in a broadcast manner in a user plane of 5GLAN according to service requirements, or may be understood as transmitting broadcast data in a user plane of 5 GLAN.

The application scenario shown in fig. 3B illustrates a transmission process of broadcast data in the user plane of 5 GLAN.

Assume that the UPF1 first receives broadcast data and then transmits the broadcast data to next-hop UPFs, i.e., UPF2 and UPF3, through the N19 interface. In order to allow all the UPFs in the 5GLAN to receive the broadcast data, the next hop UPF continues to forward the broadcast data after receiving the broadcast data, so that the UPF2 transmits the broadcast data to the next hop UPF connected thereto, i.e., the UPF3, and the UPF3 also transmits the broadcast data to the next hop UPFs connected thereto, i.e., the UPFs 2 and 4. Thus, the UPFs 2 and 3 may receive the broadcast data again and then continue to forward to the next hop UPF, forwarding the broadcast data to the UPF1, causing loop forwarding problems.

In view of this, embodiments of the present application provide a data forwarding method to solve the loop forwarding problem in a 5g lan of a ring architecture or a branch architecture.

A data forwarding method provided by the present application will be described below in two embodiments (i.e., embodiment one and embodiment two). The main difference between the first embodiment and the second embodiment is that the execution subject of the interface for forwarding the broadcast data is determined to be different. In the first embodiment, an interface for forwarding broadcast data is determined by a UPF network element; in the second embodiment, the SMF network element determines the interface for forwarding the broadcast data.

It should be noted that, in this embodiment of the present 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 UPF network elements shown in fig. 3A or fig. 3B. In addition, the UPF network element and the SMF network element may be used as independent physical functional entities or logical functional entities in actual applications, which is not limited herein.

Example one

Please refer to fig. 5, which is a flowchart illustrating a data forwarding method according to an embodiment of the present application, where the flowchart is described as follows:

s501, the SMF network element determines the path type of the N19 interface between the UPF network elements.

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

The first type, the loop interface type.

As an example, in fig. 3A, the UPFs 1-4 form a ring, and the path type of the N19 interface between any two UPF network elements in the UPFs 1-4 (e.g., the N19 interface between the UPF1 and the UPF2, the N19 interface between the UPF2 and the UPF3, etc.) is a loop interface type.

As another example, in fig. 3B, the UPFs 1-3 form a ring, and the path type of the N19 interface between any two UPF network elements in the UPFs 1-3 is a ring interface type.

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

The second type, the tributary interface type.

As an example, in fig. 3B, the UPF4 is connected only with the UPF2, and the UPF4 does not form a ring with other UPF network elements, so the UPF4 can be understood as one branch of the ring formed by the UPFs 1-3, and thus the path type of the N19 interface between the UPF4 and the UPF network element connected with it (i.e., the UPF2) is a branch interface type.

It can be understood that the path type of the N19 interface between the branching UPF network element and the UPF network element connected thereto is a branching interface type.

In one possible implementation, 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 of the 5GLAN it manages.

Specifically, the SMF network element obtains all UPFs serving terminal devices in the 5GLAN, that is, anchor UPFs of PDU sessions of all member UEs, and then determines the network topology of the 5GLAN user plane according to whether an N19 tunnel exists between every two UPFs or whether a physical connection exists in a deployment. Of course, the SMF network element may also obtain the network topology of the 5GLAN in other ways, which is not limited herein.

Then, the SMF network element determines the path type of the N19 interface between the UPF network elements in the 5GLAN according to the obtained network topology. As an example, the SMF network element may first determine that a plurality of UPF network elements in the 5g lan form a ring, and then the path type of the N19 interface between adjacent UPF network elements forming the ring is a ring interface type. Then, the remaining UPF network elements which do not form a ring are determined to be branch UPF network elements, and the path type of the N19 interface between the branch UPF network element and the UPF network element connected with the branch UPF network element is determined to be a branch interface type. As shown in fig. 3B, a network topology structure obtained by an SMF network element is a ring, and path types of an N19 interface between UPF1 and UPF2, an N19 interface between UPF1 and UPF3, and an N19 interface between UPF2 and UPF3 are all loop interface types because UPFs 1 to UPF3 form a ring; since the UPFs 4 do not form a ring and the UPF4 is connected with the UPF3, the path type of the N19 interface between the UPF3 and the UPF4 is a branch interface type.

For convenience of explanation, hereinafter, an N19 interface between the UPF1 and the UPF2 is denoted as an N19A interface, an N19 interface between the UPF2 and the UPF3 is denoted as an N19B interface, an N19 interface between the UPF1 and the UPF3 is denoted as an N19C interface, and an N19 interface between the UPF3 and the UPF4 is denoted as an N19D interface.

It should be noted that, in the embodiment of the present application, the path types of the N19 interface are divided into two types, and a loop interface type and a branch interface type are taken as examples for illustration, but it should not be understood that the method in the embodiment of the present application is limited thereto, that is, in other embodiments, the path types of the N19 interface may be more than two, and the name of the path type of the N19 interface may also be other names, and is not limited herein.

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

In the embodiment of the present application, the indication is used to indicate the path type of the N19 interface between the UPF network elements, and the indication includes the identifier of the N19 interface and the path type of the N19 interface. And after the SMF network element determines the path type of the N19 interface between the UPF network elements in the 5GLAN, sending the indication to each UPF network element in the 5 GLAN. For convenience of description, taking the example that the SMF network element sends the first indication to the first UPF network element, it may 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 is any one of the UPFs 1-4 shown in fig. 3B, and in this embodiment, the first UPF network element is the UPF 1.

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

in the first case:

the first indication is used to indicate a path type of an N19 interface associated with a UPF network element in the 5g lan. 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 may generate 4 indications, which are the first indication, the second indication, the third indication, and the fourth indication, respectively. Wherein the first indication is used for indicating the path type of the N19 interface associated with the UPF1, namely the path type comprising the N19A interface and the N19C interface; the second indication is used for indicating the path type of the N19 interface associated with the UPF2, namely the path type comprising the N19A interface and the N19B interface; the third indication is used for indicating the path type of the N19 interface associated with the UPF3, namely the path type including the N19B interface, the N19C interface and the N19D interface; the fourth indication is used to indicate the path type of the N19 interface associated with the UPF4, i.e., the path type including the N19D interface. Then, the SMF network element sends the first to fourth indications to the corresponding UPF network element, for example, the first indication is sent to the UPF1, the second indication is sent to the UPF2, and so on. Since only the path type of the N19 interface associated with one UPF is in one indication, redundant information in different indications can be reduced, and the resource occupied by each indication can be reduced.

In this case, the indication (for example, the first indication to the fourth indication) corresponding to each UPF network element may be understood as one indication that indicates the path type of the N19 interface associated with the UPF network element, but the SMF network element transmits the indication to different UPF network elements, and therefore the indication is classified into the first indication to the fourth indication according to the object to which the indication is transmitted. Fig. 5 illustrates an example in which the SMF network element transmits the first to fourth instructions.

In the second case:

to further simplify the resources occupied by each indication, the first indication may be used only for the interface indicating the path type as the loop interface type, and thus, the interface not indicated by the first indication is the branch interface type. In this case, only the identity of the interface of the loop interface type may be included in the first indication. For example, the first indication is used to indicate an interface belonging to a loop interface type in the N19 interface associated with the UPF1, that is, the first indication includes the identifications of the N19A interface and the N19C interface. Similarly, the second indication is used for indicating an interface belonging to a loop interface type in the N19 interface associated with the UPF2, that is, the second indication includes the identifications of the N19A interface and the N19B interface; the third indication is used for indicating an interface belonging to a loop interface type in the N19 interface associated with the UPF3, and since the N19D interface is a branch interface type in the N19 interface associated with the UPF3, only the identifications of the N19B interface and the N19C interface are included in the third indication.

Of course, the first indication may also be used only for indicating an interface whose path type is a branch interface type, and the specific indication manner is similar to that of the interface whose path type is only used for indicating a loop interface type, which is not described herein again.

In this case, the identifier of the N19 interface may be a number or a tunnel information parameter of the N19 interface, and the like, which is not limited herein.

In the third case:

the first indication is used to indicate the path type of one or more of the N19 interfaces. For example, the first indication is used to indicate a path type of an N19 interface, and the first indication includes tunnel information of the N19 interface indicated by the first indication and the path type of the N19 interface. After the UPF network element receives the first indication, it may 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 may be understood that the N19 interface indicated in the first indication does not necessarily have an association relationship with the receiver of the first indication, for example, the first indication may indicate a path type of the N19A interface and a path type of the N19D interface, the SMF network element may send the first indication to the UPF1, and after the UPF1 receives the first indication, it 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 path type of the N19A interface according to the first indication, and the tunnel information of the other N19 interface is different from the other N19 interfaces in the UPF1, so as to ignore the information related to the N19 interface in the first indication.

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

In the first transmission mode, the first indication is transmitted in a creation request (or an N4 message) of the N4 session.

The SMF network element sends a first indication to the first UPF network element during the creation of the N4 session. As an example, after receiving a PDU session creation request sent by a terminal, an SMF network element sends a first indication to a UPF network element anchored with the PDU session, for example, if the SMF network element determines that a session of the terminal is anchored at a first UPF network element, 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 an embodiment of the present application, the N4 session creation request includes a creation request of an N4 session at a group level of the 5G LAN. In particular, the SMF network element may indicate the path type of the N19 interface to the first UPF network element in a create request sent to the first UPF network element for creating a group-level N4 session, by one or more Information Elements (IEs). For example, an extended IE may be added at the creation request, and the path type of the N19 interface associated with the first UPF network element may be indicated by an extended value of the extended IE.

In the second transmission mode, the first indication is transmitted in the modification request (or N4 message) of the N4 session.

The SMF network element may also send the first indication to the first UPF network element during the modification of the N4 session. For example, after determining that the N4 session needs to be modified (for example, receiving an N4 session modification request sent by a PCF network element or a change in the network topology of a 5GLAN user plane), the SMF network element sends the first indication to the corresponding UPF network element. The carrying manner of the first indication in the N4 session modification request is similar to that in the first sending manner, and is not described herein again.

After the first indication is received by the first UPF network element, the path type of the N19 interface associated with the UPF network element may be determined according to the first indication.

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

In the embodiment of the present application, the routing rule is used to instruct forwarding of the detected broadcast data to the N19 interface, or it may be understood as forwarding of the destination address as a broadcast address (e.g., a broadcast MAC address or a broadcast IP address (FFFFFF)) to the N19 interface. For convenience of explanation, the SMF network element generates 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 may be understood as a routing rule of an N4 session at a UE level and a group level associated with 5GLAN in the first UPF network element, or may be understood as belonging to an N4 session where a PDR matched to broadcast data is located.

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

A first routing rule, where the routing rule corresponding to the first UPF network element includes PDRs and FARs that detect incoming broadcast data from a PDU session of the end device and forward the broadcast data to 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 for the N4 session of each terminal device and the N4 session of the group level, respectively.

N4 session for each terminal device:

UL PDR: the source interface parameter is set to be 'access side' or 'core side', the tunnel information parameter is set to be tunnel header information of the PDU session of the UE at the first UPF network element side, and the related Rule identification (Rule ID) of the FAR is also set;

UL FAR: the target interface parameter is set to a value corresponding to the internal interface of the first UPF network element (e.g., to "5 GLAN internal"), and the path type parameter of the outgoing interface is set to a non-loop interface type (or may be understood to be a branch interface type).

For example, after receiving the PDU session creation request sent by the UE1 and the UE2, the SMF network element determines that the UPF network element anchored with the UE1 and the UE2 is the UPF1 shown in fig. 3B, and then the SMF network element may generate a first UL PDR and a first UL FAR corresponding to the PDU session of the UE1 for the UE1 and generate a second UL PDR and a second UL FAR corresponding to the PDU session of the UE2 for the UE2, respectively. The first UL PDR and the second UL PDR both include a source interface parameter, a tunnel information parameter and a Rule ID, wherein in the first UL PDR, the source interface parameter is set to be "access side" or "core side", and the tunnel information parameter is set to be tunnel header information of a PDU session of the UE1 in the UPF 1; 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 tunnel header information of the PDU session of the UE2 at the UPF 1.

The first UL FAR and the second UL FAR both include target interface parameters and path type parameters of the outgoing interface, and values of each parameter in the first UL FAR and the second UL FAR are the same, the target interface parameters may both be set to "5 GLAN internal", and the path type parameters of the outgoing interface are both set to a non-loop interface type. In this case, only one UL FAR may be set, and all UEs anchored with the UPF1 use the UL FAR.

The N4 session for the group level includes the following two forms:

in a first form:

UL PDR: setting a source interface parameter as a value corresponding to an internal interface of a first UPF network element, setting a target address in an Ethernet filter parameter as a broadcast address, setting a path type parameter of an incoming interface as a non-loop interface type, and setting Rule ID of associated FAR;

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

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

In a second form:

unlike the first form, in the UL FAR, it is also possible to set a path type parameter of an outgoing interface, for example, to ALL (ALL) or to a loop interface type and a branch interface type.

And a second routing rule, wherein the routing rule corresponding to the first UPF network element comprises PDR and FAR for detecting broadcast data incoming from one N19 interface and forwarding the broadcast data to a corresponding N19 interface on the first UPF network element. In this case, the SMF network element needs to generate the following DL PDRs and DL FAR in the group level N4 session:

in a first form:

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

DL FAR: the target interface parameter is set as 'core side';

for example, when the first UPF network element is the UPF1 shown in fig. 3B, the SMF network element determines that the UPF1 includes 2N 19 interfaces, which are an N19A interface and an N19C interface, respectively, the SMF network element may generate two DL PDRs and a DL FAR corresponding to each DL PDR for the UPF1, where a first DL PDR is used to detect broadcast data received through the N19A interface, a second DL PDR is used to detect broadcast data received through the N19C interface, and a value of a tunnel information parameter in the first DL PDR is information of the N19A interface, that is, a GTP-U TEID of the UPF1 network element; the tunnel information parameter in the second DLPDR takes the value of the N19C interface information, i.e. the GTP-U TEID of the UPF1 network element. In this case, the values of the parameters of the target interface 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 may determine and store the path type of the N19 interface locally according to the tunnel information parameter in the DL PDR and the UPF network element according to the first indication, and determine the type of the incoming interface, for example, the 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, thereby determining that the type of the incoming interface is the loop interface type, and determine that the type of the incoming interface corresponding to the second DL PDR is the loop interface type in the same manner. The UPF network element then determines the type of outgoing interface according to the transmission rules (forwarding only to the interface of the branch interface type if data is received from the interface of the loop interface type, and forwarding to the interfaces of the other branch interface type and the interface of the loop interface type if data is received from the interface of the branch interface type). For example, the outgoing interface of the DL FAR corresponding to the first PDR is determined to be of a non-loop interface type, and the outgoing interface of the DL FAR corresponding to the second PDR is determined to be of a non-loop interface type.

In a second form:

unlike the first form, in the DL PDR, in addition to the content of the first form, a path type parameter of an incoming interface is included, and the path type parameter of the incoming interface may be a loop interface type or a non-loop interface type.

For example, if the UPF1 includes 2N 19 interfaces, i.e., an N19A interface and an N19C interface, respectively, the SMF network element may generate two DL PDRs and a DL FAR corresponding to each DL PDR for the UPF1, where each DL PDR includes a type of an incoming interface in addition to the content of the DL PDR in the first form, and since the N19A interface and the N19C interface are both loop interface types, the type of the incoming interface in each DL PDR is set to be the loop interface type. In this form, the UPF network element may determine the type of outgoing interface according to the aforementioned transmission rules. For example, the outgoing interface of the DL FAR corresponding to the first PDR is determined to be of a non-loop interface type, and the outgoing interface of the DL FAR corresponding to the second PDR is determined to be of a non-loop interface type.

As an example, a field (e.g., a bit) may be added to the source interface parameter of the PDR, by which the path type of the incoming interface is indicated, where "0" represents a loop interface type and "1" represents a non-loop interface type.

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

In a third form:

unlike the first form, in the DL FAR, in addition to the content of the first form, a path type parameter of an outgoing interface is included, and the path type parameter of the outgoing interface may be ALL or a non-loop interface type.

For example, when the first UPF network element is the UPF1 shown in fig. 3B, the SMF network element may further set a non-ring value in the outgoing interface parameter of the FAR of the first PDR, and since the N19A interface is a ring interface type, the non-ring interface type is set in the outgoing interface parameter of the DL FAR corresponding to the first PDR according to the foregoing transmission rule. Similarly, 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 (e.g., a bit) may be added to the target interface parameter of the FAR, and the path type of the outgoing interface is indicated by the field, where "0" indicates ALL and "1" indicates the non-loop interface type.

A fourth form:

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

DL FAR: the target interface parameter is set to a value corresponding to the internal interface of the UPF (e.g., "5 GLAN internal"), and further includes a path type parameter of the outgoing interface, which may be a loop interface type or a non-loop interface type, for example. 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 of the incoming broadcast data. For example, broadcast data is incoming from the N19A interface, the path type of the N19A interface is the loop interface type, and 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 PDRs and UL FAR in a group level N4 session:

UL PDR: the source interface parameter is set as a value corresponding to an internal interface of the first UPF network element, a target address in the filter parameter is set as a broadcast address, and the target address also has Rule ID of associated FAR; optionally, the method further includes a path type parameter of an internal interface that transmits 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 as the loop interface type;

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

It should be noted that the SMF may generate the routing rule corresponding to the other UPFs in the 5GLAN in the same manner as described above, and details are not described here again.

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

In this embodiment, the configuration information includes an identifier of the N4 session and a routing rule corresponding to the UPF network element. And after the SMF network element generates the routing rule corresponding to each UPF network element, respectively sending the routing rule corresponding to each UPF network element 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 one example, the configuration message may be an N4 message.

For convenience of illustration, in fig. 5, the configuration information sent by the SMF network element to different UPF network elements is marked with the first to fourth configuration information, for example, the configuration information sent by the SMF network element to the first UPF network element is marked as the first configuration information, where the first configuration information includes an identifier of the N4 session and a routing rule corresponding to the first UPF network element; and marking the configuration information sent by the SMF network element to the second UPF network element as second configuration information, wherein the second configuration information comprises an identifier of the N4 session and a 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 may directly associate the PDR indicated in the configuration information with the existing FAR, and set the FAR ID parameter of the PDR indicated in the configuration information as a rule identifier (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 this embodiment, the destination address of the first data packet is a broadcast address, the UPF network element receives the first data packet through a PDU session tunnel, and the first UE may be a UE anchored with the UPF1 network element, for example, UE 1.

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

And after receiving the first data packet, the first UPF network element executes a matching process of the first data packet and the PDR, detects that the first data packet is matched with the UL PDR of the N4 session of the first UE, and forwards the data packet to an internal interface of the first UPF network element through a corresponding UL FAR.

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 that the first data packet matches with the UL PDR of the group-level N4 session of the 5GLAN in which the first UPF network element is located.

And 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 packet matches the UL PDR of the group-level N4 session of the first UPF network element, the first interface for forwarding the first packet may be determined according to the UL FAR associated with the UL PDR. In this embodiment of the present application, for a group-level N4 session, the SMF network element may configure a different form of routing rule in the first UPF network element, so that according to the different form of routing rule configured by the SMF network element in the first UPF network element, the manner in which the first UPF network element determines the target interface for forwarding the first packet according to the UL FAR may include, but is not limited to, the following several manners.

First, a first form of the routing rule for the group-level N4 session in step S503:

the first UPF network element determines the first interface by the path type parameter of the incoming interface in the UL PDR in the group level N4 session and the transmission rule that match the first packet.

As an example, in the UL FAR corresponding to the N4 session at the group level, the target interface parameter is "core side", and thus, the first UPF network element determines that the target interface is the N19 interface. As shown in fig. 3B, in the 5GLAN, if the first packet with the destination address being the broadcast address is forwarded through all the N19 interfaces, there is a problem of loop forwarding, and therefore, in this embodiment of the present application, when the first UPF network element determines to forward the first packet with the destination address being the broadcast address through the N19 interface, it needs to further screen the N19 interface to determine the first interface actually used for forwarding the first packet.

Then, the first UPF network element determines the N19 interface actually used for forwarding the first packet according to the path type parameter of the incoming interface in the UL PDR of the group-level N4 session and the aforementioned 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 forwarding the first packet is an N19 interface of all types, so that the first UPF network element determines that the first interface actually used for forwarding the first packet is all N19 interfaces associated with the first UPF network element, and 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 that the first interfaces are the N19A interface and the N19C interface.

Second way, a second form of the routing rule for the group-level N4 session in step S503:

the first UPF network element determines the first interface based on 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 to a ring interface type and a branch interface type, and the N19 interfaces associated with the first UPF network element are the N19A interface and the N19C interface, so that the first UPF network element determines that the first interface actually used to forward the first 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 forwards the data to the target interface, the replication process of the data packet is executed, and the first data packet is replicated, so that the second data packet is obtained.

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

The first copy method:

when the SMF network element sets a corresponding routing rule for the group-level N4 session, a replication label for replicating a packet may be set in the UL FAR associated with the UL PDR, so that, after the first UPF network element detects that the packet matches the UL PDR of the group-level N4 session, the first UPF network element may trigger a packet replication process according to the replication label in the UL FAR associated with the UL PDR, and replicate the first packet.

The second copy method:

and when each UPF network element forwards the broadcast data to the target interface, triggering the copying function of the UPF network element, executing the copying process of the data packet, and copying the first data packet.

In addition, it should be noted that the number of the first UPF network element copies the first data packet is the same as the number of the first interface. Specifically, when the first UPF network element determines a first interface for forwarding the first packet, the first packet may be duplicated according to the number of the first interfaces. For example, if the first UPF network element is the UPF1 shown in fig. 3B, and the number of the first interfaces is 2, the UPF1 may duplicate the first packet.

And S510, the first UPF network element sends a second data packet to the second UPF network element and sends the 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 this 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, the first interfaces are an N19A interface and an N19C interface, the second UPF network element and the third UPF network element are respectively an UPF2 and an UPF3, and as an example, the second UPF network element is an UPF3, and the third UPF network element is an UPF 2.

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 with the DL PDR of the group-level N4 session.

In the embodiment of the present application, the subsequent execution steps of the method in the embodiment of the present application are different according to the difference of the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface. If the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface is the first form to the third form of the second routing rule in step S503, the method in the embodiment of the present application performs steps S514 to S518, and if the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface is the fourth form of the second routing rule in step S503, the method in the embodiment of the present application performs steps S512 to S518. That is, steps S512 to S513 are optional steps, and therefore, these two steps are indicated by broken lines in fig. 5.

And S512, the second UPF network element sends the second data packet to an internal interface of the second UPF network element.

And in the DL FAR corresponding to the DL PDR matched with 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, and meanwhile, a non-ring indication may also be transmitted, where the non-ring indication is used to indicate that the interface where the second data packet is transmitted is a non-ring interface.

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

Note 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, a second interface for forwarding the second data packet may be determined according to the transmission rule, or an indication in the associated FAR.

If the second data packet is received through the internal 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 in 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 group-level N4 session matched with the second packet includes the path type parameter of the N19 interface of the incoming broadcast data, the second UPF network element determines the second interface according to the transmission rule and the path type parameter of the N19 interface of the incoming broadcast data; and when the path type parameter of the outgoing interface is included in the UL FAR corresponding to the UL PDR of the N4 session of the group level matched with the second data packet, the second UPF network element determines the second interface according to the path type parameter of the outgoing interface. The specific implementation process is similar to that in step S508, and is not described herein again.

If the second data packet is received from the N19 interface, that is, in step S512, the routing rules configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface are the first form to the third form of the second routing rule 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.

The first determination method corresponds to the first form of 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 indication sent in step S502.

Specifically, the second UPF network element obtains a value of a tunnel information parameter in the DL PDR matched with the second data packet, for example, the value of the tunnel information parameter is a second UPF network element GTP-U TEID, and then the second UPF network element determines that the second data packet is received through an N19 interface between the first UPF network element and the second UPF network element. And then, according to the second indication sent by the SMF network element, determining that the path type of the N19 interface between the first UPF network element and the second UPF network element is a branch interface type or a loop interface type.

For example, if the UPF3 determines that the tunnel information parameter in the DL PDR matching the second packet is GTP-UTEID of the UPF3, the UPF3 determines that the incoming interface of the second packet is the N19 interface between the UPF3 and the UPF1, i.e., the N19C interface. Then, the path type of the incoming interface of the second packet is determined to be the loop interface type according to the path type of the N19 interface associated with the UPF3 indicated in the second indication, for example, the second indication is "the path type of the N19B interface is the loop interface type, the path type of the N19C interface is the loop interface type, and the path type of the N19D interface is the branch interface type".

And 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 process is similar to step S508, and is not described in detail here. Thus, the second UPF network element then determines the N19 interface that matches the outgoing interface type from the plurality of N19 interfaces associated therewith as the second interface. For example, if the UPF3 determines that the N19 interface of the second packet is a ring interface type, the forwarding rule indicates that the type of the outgoing interface is a branch interface type. The N19 interface associated with the UPF3 includes an N19B interface, an N19C interface, and an N19D interface, wherein the N19 interface, the type of interface being a branch interface type, is an N19D interface, such that the UPF3 determines the N19D interface to be the second interface for forwarding the second packet.

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

and 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 matched with the second data packet. If the path type of the incoming interface in the DL PDR takes a value of a ring value, the type of the incoming interface is determined to be a ring interface type, and if the path type of the incoming interface in the DL PDR takes a value of a non-ring value, the type of the incoming interface is determined to be a branch interface type.

For example, the path type of the interface is indicated by a field in the source interface parameter of the DL PDR, where "0" represents a ring value and "1" represents a non-ring value. When detecting the DL PDR matched with the second data packet, the UPF3 determines whether the value of the field in the source interface parameter of the DL PDR is "0", if so, the UPF3 determines that the type of the incoming interface is a branch interface type, otherwise, determines that the type of the incoming interface is a loop interface type.

And 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 is not described herein again.

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

and 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 matched with the second data packet. If the values of the path type parameters of the outgoing interface in the DL FAR are all, determining that the type of the outgoing interface is a loop interface type or a branch interface type, and if the values of the path type parameters of the outgoing interface in the DL FAR are non-circular values, determining that the type of the outgoing interface is a branch interface type. The second UPF network element then determines an N19 interface, from the plurality of N19 interfaces associated therewith, that matches the type of the outgoing interface as the second interface.

For example, the path type of the interface is indicated by a field in the target interface parameter of the DL FAR, where "0" indicates all and "1" indicates a non-circular value. When detecting the DL PDR matched with the second data packet, the UPF3 determines whether the value of the field in the DL FAR corresponding to the DL PDR is "0", if so, the UPF3 determines that the type of the outgoing interface is a loop interface type or a branch interface type, otherwise, determines that the type of the outgoing interface is a branch interface type. For example, the UPF3 determines that the type of outgoing interface is a tributary interface type, and only the N19D interface of the N19 interface associated with the UPF3 is a tributary interface type, such that the UPF3 determines that the N19D interface is the second interface for forwarding the second packet.

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

After receiving the second data packet, the third UPF network element also needs to perform steps S512 to S515, which is not described herein again. In the embodiment of the present application, since the UPF2 determines that the type of the N19 interface used for forwarding the second packet is a branch interface type, and there is no N19 interface of the branch interface type in the N19 interface associated with the UPF2, the UPF2 determines not to forward the second packet.

And S516, the second UPF network element generates a third data packet.

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

In this embodiment of the application, the second UPF network element is a UPF network element connected to the second interface, for example, if the second interface is an N19D interface, the fourth UPF network element is a UPF 4.

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, the processing procedure similar to that of the second UPF network element is executed (i.e., step S512 to step S514, step S516, and step S517), which is not described herein again.

As an example, the UPF4 determines the type of the third interface used to forward the third packet to be a ring interface type or an interface of another branch interface type different from the incoming interface. Since the UPF4 does not have an interface of the other branch interface type and does not have an interface of the ring interface type, the UPF4 determines not to forward the third packet.

In the above technical solution, after the UPF network element receives the broadcast data, the type of the interface for forwarding the broadcast data may be determined according to the path type (for example, a loop interface type or a branch interface type) of the N19 interface set by the SMF network element and a corresponding routing rule, and then according to the determined type of the interface for forwarding the broadcast data, which interfaces to forward the broadcast data are determined, so that a loop forwarding problem caused by forwarding the broadcast data through all interfaces may be avoided.

In the embodiment shown in fig. 5, a description is given of a forwarding process of broadcast data incoming from a PDU session of a terminal device. In actual use, the broadcast data may also be incoming from the N19 interface. When the broadcast data is transmitted 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 is not described herein again.

Example two

Referring to fig. 6, a flowchart of another example of a data forwarding method provided in an embodiment of the present application is described 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 is not described in detail here.

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

In the embodiment of the present application, the routing rule is used to instruct forwarding of the detected broadcast data to the N19 interface, or it may be understood as forwarding of the destination address as a broadcast address (e.g., a broadcast MAC address or a broadcast IP address (FFFFFF)) to the N19 interface. For convenience of description, the SMF network element generates a routing rule corresponding to the first UPF network element, and the first UPF network element may be understood as any one UPF network element in the 5 GALN.

The routing rule of the N4 session for each terminal device is similar to that in step S503, and is not described herein again.

For group-level N4 sessions, the generated UL PDR includes: the source interface parameter is set to a value corresponding to an internal interface of the first UPF network element, a target address in the filter parameter is set to a broadcast address, and the target address also has Rule ID of 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 determines an outgoing interface of the broadcast data received from the internal interface according to the transmission rule (if the broadcast data is received through the N19 interface of the ring interface type, the broadcast data is forwarded only through the N19 interface of the tributary interface type, and if the broadcast data is received from the N19 interface of the tributary interface type, the broadcast data is forwarded to the N19 interface of the other tributary interface type and the N19 interface of the ring interface type). Since the internal interface is not a loop interface type, the SMF network element determines that the broadcast data received from the internal interface needs to be forwarded to all N19 interfaces associated with the first UPF network element, and thus, the SMF network element determines that the target interface parameter is set to the tunnel information of all N19 interfaces associated with the first UPF network element in the UL FAR corresponding to the UL PDR.

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

And a second routing rule corresponding to the first UPF network element includes PDRs and FARs for detecting incoming broadcast data from one N19 interface and forwarding the broadcast data to a corresponding N19 interface on the first UPF network element. In this case, the SMF network element generates a routing rule corresponding to the first UPF network element, which includes but is not limited to the following two forms:

in a first form:

after the SMF network element determines the path type of each N19 interface, the SMF network element determines a routing rule corresponding to the first UPF network element according to the path type of each N19 interface associated with the first UPF network element and the transmission rule. For example, if there are N19 interfaces associated with the first UPF network element, the SMF network element may generate N routing rules for the first UPF network element, where the N routing rules are in one-to-one correspondence with the N19 interfaces for detecting incoming broadcast data from each of the N19 interfaces.

As an example, the first UPF network element is the UPF1 shown in fig. 3B, and the N19 interfaces associated with the UPF1 are the N19A interface and the N19C interface. The SMF network element may generate two DL PDRs and DL FARs corresponding to each DL PDR in a group-level N4 session, where the first DL PDR is used to detect broadcast data received over the N19A interface and the second DL PDR is used to detect broadcast data received over the N19C interface.

For the routing rule corresponding to the N19A interface, since the N19A interface is of the ring interface type, the SMF network element determines that the broadcast data incoming from the N19A interface should be forwarded to the interface of the branch interface type, so as to generate the routing rule corresponding to the N19A interface as follows:

the first DL PDR comprises: the source interface parameter is set as the tunnel information of the N19A interface, the target address in the filter parameter is set as the broadcast address, and the Rule ID of the associated FAR;

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

It should be noted that, since there is no interface of the tributary interface type in the N19 interface associated with the UPF1 network element, the SMF network element may set the routing rule corresponding to the N19A interface, so that the broadcast data incoming from the N19 interface is not forwarded.

For the routing rule corresponding to the N19C interface, the way in which the SMF network element generates the routing rule corresponding to the N19C interface is similar to the way in which the routing rule corresponding to the N19A interface is generated, and details are not described here.

As another example, the first UPF network element is the UPF3 shown in fig. 3B, and the N19 interfaces associated with the UPF3 are the N19B interface, the N19C interface, and the N19D interface. The SMF network element may generate three DL PDRs for detecting broadcast data received through the N19B interface, a second DL PDR for detecting broadcast data received through the N19C interface, and a DL FAR corresponding to each DL PDR, respectively, in a group-level N4 session of the UPF3, and a third DL PDR for detecting broadcast data received through the N19D interface.

For the routing rule corresponding to the N19B interface, since the N19B interface is of the ring interface type, the SMF network element determines that the broadcast data incoming from the N19B interface should be forwarded to an interface of the branch interface type. The interface of the branch interface type in the N19 interface associated with the UPF3 network element is an N19D interface, and therefore, the SMF network element determines that the broadcast data incoming from the N19B interface is forwarded to the N19D interface, so as to generate a routing rule corresponding to the N19B interface as follows:

the first DL PDR comprises: setting source interface parameters as values corresponding to an N19B interface, setting tunnel parameter information parameters as tunnel information of the N19B interface, setting target addresses in filter parameters as broadcast addresses and Rule IDs of associated FARs;

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.

For the routing rule corresponding to the N19C interface, the routing rule corresponding to the N19B interface is similar, and is not described herein again.

For the routing rule corresponding to the N19D interface, since the N19D interface is a branch interface type, the SMF network element determines that the broadcast data received from the N19D interface is forwarded to the N19 interface of another branch interface type and the N19 interface of a ring interface type, and therefore, the SMF network element determines that the broadcast data incoming from the N19D interface is forwarded to the N19B interface and the N19C interface, so as to generate the routing rule corresponding to the N19D interface as follows:

the third DL PDR comprises: setting source interface parameters as values corresponding to an N19D interface, setting tunnel parameter information parameters as tunnel information of the N19D interface, setting target addresses in filter parameters as broadcast addresses and Rule IDs of associated FARs;

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.

In a second form:

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

DL FAR: the target interface parameter is set to a value corresponding to the internal interface of the first UPF network element (for example, "5 GLAN internal"), and the target interface parameter further includes a 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 of the incoming broadcast data. For example, broadcast data is incoming from the N19A interface, the path type of the N19A interface is the loop interface type, and 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 a group level N4 session.

The SMF network element determines that the broadcast data incoming from the ring interface is not to be forwarded, and the data incoming from the branch interface is to be transmitted to all other N19 interfaces, so as to generate the routing rule corresponding to:

UL PDR: the source interface parameter is set as a value corresponding to an internal interface of the first UPF network element, a target address in the filter parameter is set as a broadcast address, and the path type parameter of an interface for transmitting the broadcast data is set as a branch interface type;

UL FAR: the target interface parameter is set as "core side", and the tunnel information parameter is set as the tunnel information of all the N19 interfaces in the first UPF network element. Alternatively, the first and second electrodes may be,

UL PDR: the source interface parameter is set as a value corresponding to an internal interface of the first UPF network element, a target address in the filter parameter is set as a broadcast address, and the path type parameter of an interface for transmitting the broadcast data is set as a 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 interface of the branch interface type 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 the UPF3 shown in fig. 3B, and the N19 interfaces associated with the UPF3 are the N19B interface, the N19C interface, and the N19D interface. The SMF network element may generate two UL PDRs for detecting broadcast data received through an interface of a branch interface type and a UL FAR corresponding to each UL PDR respectively in a group-level N4 session of the UPF3, where the first UL PDR is for detecting broadcast data received through an interface of a loop interface type.

The first UL PDR includes: setting a source interface parameter as a value corresponding to an internal interface of UPF3, setting a target address in a filter parameter as a broadcast address, setting a Rule ID of a correlated FAR, and setting a path type parameter of an interface for transmitting the broadcast data as a 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 the tunnel information of the N19B interface, the N19C interface, and the N19D interface.

The second DL PDR comprises: setting a source interface parameter as a value corresponding to an internal interface of the UPF3, setting a target address in a filter parameter as a broadcast address, setting a Rule ID of an associated FAR, and setting a path type parameter of an interface for transmitting the broadcast data as a loop interface type;

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

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

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

In this embodiment, the destination address of the first packet is a broadcast address, the UPF network element receives the first packet through a PDU session tunnel, and the first UE may be a UE anchored to the UPF1 network element, for example, UE 1.

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 the first data packet to the internal interface of the UPF.

Steps S603 to S605 are similar to steps S504 to S506, and are not described herein again.

S606, 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 that the first data packet matches with the UL PDR of the group level N4 session of the 5GLAN in which the first UPF network element is located.

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

And S607, the first UPF network element generates a second data packet.

As an example, the first UPF network element is the UPF1, and the UPF1 determines that the target interfaces indicated in the UL FAR corresponding to the UL PDR in the first routing rule of step S602 are the N19A interface and the N19C interface, then the UPF1 duplicates the first packet, generates two second packets, and then sends the two second packets to the N19A interface and the N19C interface, respectively.

The manner of copying the first data packet by the UPF1 is similar to that in step S509, and is not described herein again.

S608, the first UPF network element sends the second data packet to the second UPF network element and sends the 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, when the UPF1 generates the second packet, the second packet is forwarded according to the UL FAR corresponding to the UL PDR that matches the first packet. The target interfaces indicated in the UL FAR are the N19A interface and the N19C interface, the UPF1 sends the second packet to the UPF2 through the N19A interface, and sends the second packet to the UPF3 through the N19C interface.

And S609, the second UPF network element executes the matching process of the data packet and the PDR, and detects the PDR matched with the second data packet.

In the embodiment of the present application, the subsequent execution steps of the method in the embodiment of the present application are different according to the difference of the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface. 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 performs steps S610 to S615, and if the routing rule configured in the second UPF network element for detecting the broadcast data incoming from the N19 interface is the first form of the second routing rule in step S602, the method in the embodiment of the present application performs steps S612 to S615. That is, steps S610 to S612 are optional steps, and therefore, these two steps are indicated by broken lines in fig. 6.

For convenience of explanation, the second UPF network element is referred to as UPF3 in the following.

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 with the second data packet is the second form of the second routing rule in step S602, and sends the second data packet to the internal interface of the second UPF network element according to the DL FAR corresponding to the DL PDR matched with the second data packet, and sends the ring interface value at the same time. The ring interface value is used to indicate that the path type of the interface into which the second packet is transmitted is a ring interface type.

S611, the second UPF network element receives the second data packet through the 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 packet is the UL PDR in the routing rule corresponding to the N19C interface in the second form of the second routing rule in step S602.

And S612, the second UPF network element generates a third data packet.

As an example, if the UPF3 determines that the destination interface indicated in the UL FAR corresponding to the UL PDR matching the second packet is the N19D interface, the UPF3 duplicates the second packet and generates a third packet.

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

And the third UPF network element receives the second data packet through the internal interface, executes the matching process of the data packet and the PDR, and cannot detect the PDR matched with the second data packet, thereby determining not to forward the second data packet.

And 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 matched with the second data packet, and the fourth UPF network element receives the third data packet.

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

And 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 a matching process between the data packet and the PDR, and after the DL PDR corresponding to N19D is matched, forwards the data packet to the internal interface, and then detects no UL PDR matching the third data packet, thereby determining that the third data packet is not forwarded.

In the above technical solution, the SMF network element configures a corresponding routing rule for each UPF network element according to a preset transmission rule and a path type (for example, a loop interface type or a branch interface type) of each N19 interface, so that, after receiving broadcast data, a UPF network element can forward the broadcast data according to the routing rule configured in the UPF network element, and thus, a problem of loop forwarding caused by forwarding the broadcast data through all interfaces can be avoided.

In the embodiments provided by the present application, the method provided by the embodiments of the present application is introduced from the perspective of interaction among the terminal device, the user plane function network element, and the session management function network element. In order to implement each function in the method provided in the embodiment of the present application, the user plane functional network element and the session management functional network element may include a hardware structure and/or a software module, and implement each function in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether any of the above-described functions is implemented as a hardware structure, a software module, or a hardware structure plus a software module depends upon the particular application and design constraints imposed on 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 to fourth user plane function network elements, and may implement the function of any one of the first to fourth user plane function network elements in the method provided in this embodiment of the present application; the communication apparatus 700 may also be an apparatus capable of supporting any one of the first to fourth user plane function network elements to implement the corresponding function in the method provided in the embodiment of the present application. The communication device 700 may be a hardware structure, a software module, or a hardware structure plus a software module. The communication apparatus 700 may be implemented by a system-on-chip. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

The communication apparatus 700 may comprise a processing unit 701 and a transceiving unit 702.

The processing unit 701 may be configured to perform steps S506 to S509 in the embodiment shown in fig. 5, or to perform steps S511 to S514 and S516 in the embodiment shown in fig. 5, or to perform step S515 in the embodiment shown in fig. 5, or to perform step S518 in the embodiment shown in fig. 5, or to perform steps S605 to S607 in the embodiment shown in fig. 6, or to perform steps S609 to S612 in the embodiment shown in fig. 6, or to perform step S613 in the embodiment shown in fig. 6, or to perform step S615 in the embodiment shown in fig. 6, and/or to support other processes of the techniques described herein.

The transceiver unit 702 is used for communication between the communication device 700 and other modules, and may be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device capable of implementing communication.

The transceiving unit 702 may be configured to perform steps S502, S504, S505, and S510 in the embodiment shown in fig. 5, or to perform step S517 in the embodiment shown in fig. 5, or to perform steps S603 to S604, S608 in the embodiment shown in fig. 6, or to perform step S614 in the embodiment shown in fig. 6, and/or to support other processes of the techniques described herein.

All relevant contents of the steps related to the method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Fig. 8 shows a schematic structural diagram of a communication device 800. The communication device 800 may be a session management function network element, and may implement the function of the session management function network element in the method provided in this embodiment; the communication apparatus 800 may also be an apparatus capable of supporting a session management function network element to implement the function of the session management function network element in the method provided in the embodiment of the present application. The communication device 800 may be a hardware structure, a software module, or a hardware structure plus a software module. The communication apparatus 800 may be implemented by a system-on-chip. In the embodiment of the present application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

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

The processing unit 801 may be configured to perform steps S501 and S503 in the embodiment shown in fig. 5, or to perform steps S601-S602 in the embodiment shown in fig. 6, and/or to support other processes of the techniques described herein.

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

The transceiving unit 802 may be configured to perform step S502 and step S504 in the embodiment shown in fig. 5, or to perform step S603 in the embodiment shown in fig. 6, and/or to support other processes of the techniques described herein.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

Fig. 9 shows a communication apparatus 900 according to this embodiment, where the communication apparatus 900 may be any one of the first to fourth user plane function network elements, and can implement the function of any one of the first to fourth user plane function network elements in the method according to this embodiment; the communication apparatus 900 may also be an apparatus capable of supporting any one of the first to fourth user plane function network elements to implement the corresponding function in the method provided in the embodiment of the present application. The communication device 900 may be a chip system. In the embodiment of the present application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

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

The communication apparatus 900 includes at least one processor 920 configured to implement or support the communication apparatus 900 to implement the function of the first user plane functional network element in the method provided by the embodiment of the present application. For example, the processor 920 may determine that the path type of the transmission path for forwarding the data packet is determined according to the PDR matched with the data packet, which refers to the detailed description in the method example and is not described herein again.

The communications apparatus 900 can also include at least one memory 930 for storing program instructions and/or data. A memory 930 is coupled to the processor 920. 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 an electrical, mechanical or other form, which is used for information interaction between the devices, units or modules. The processor 920 may operate in conjunction with the memory 930. Processor 920 may execute program instructions stored in memory 930. At least one of the at least one memory may be included in the processor.

The communications apparatus 900 can also include a communication interface 910 for communicating with other devices over a transmission medium such that the apparatus used in the apparatus 900 can communicate with other devices. Illustratively, the other device may be a terminal. Processor 920 may transceive data using communication interface 910. The communication interface 910 may specifically be a transceiver.

The specific connection medium among the communication interface 910, the processor 920 and the memory 930 is not limited in the embodiments 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 manner between other components is merely illustrative and not limited. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 9, but this does not mean only one bus or one type of bus.

In the embodiments 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, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a 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), and may also be a volatile memory (RAM), for example, a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

Fig. 10 shows a communication apparatus 1000 according to this embodiment of the present application, where the communication apparatus 1000 may be a session management function network element, and is capable of implementing a function of the session management function network element in the method according to this embodiment of the present application; the communication apparatus 1000 may also be an apparatus capable of supporting a terminal to implement the function of the session management function network element in the method provided by the embodiment of the present application. The communication device 1000 may be a chip system. In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

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

The communication apparatus 1000 includes at least one processor 1020 configured to implement or support the communication apparatus 1000 to implement the functions of the session management function network element in the method provided in the embodiment of the present application. For example, the processor 1020 may generate a routing rule corresponding to each UPF network element, which is specifically described in the detailed description of the method example and is not described herein again.

The communications apparatus 1000 can also include at least one memory 1030 for storing program instructions and/or data. A memory 1030 is coupled to the processor 1020. The coupling in the embodiments of the present application is an indirect coupling or a communication connection between devices, units or modules, and may be an electrical, mechanical or other form for information interaction between the devices, units or modules. Processor 1020 may operate in conjunction with memory 1030. Processor 1020 may execute program instructions stored in memory 1030. At least one of the at least one memory may be included in the processor.

Communications apparatus 1000 may also include a communications interface 1010 for communicating with other devices over a transmission medium such that the apparatus used in apparatus 1000 may communicate with other devices. Illustratively, the other device may be a terminal. The processor 1020 may transmit and receive data using the communication interface 1010. The communication interface 1010 may specifically be a transceiver.

The specific connection medium among the communication interface 1010, the processor 1020 and the memory 1030 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 1030, the processor 1020, and the communication interface 1010 are connected by a bus 1040 in fig. 10, the bus is represented by a thick line in fig. 10, and the connection manner between other components is merely illustrative and not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but it is not intended that there be only one bus or one type of bus.

In the embodiment of the present application, the processor 1020 may be a general 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, and may implement or execute the methods, steps, and logic blocks disclosed in the embodiment of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a 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), and may also be a volatile memory (RAM), for example, a random-access memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

As shown in fig. 11, in particular, a communication system 1100 includes a first user plane function network element and a session management function network element, optionally, a second user plane function network element and/or a third user plane function network element, or may further include more user plane function network elements, where the second user plane function network element and the third user plane function network element are taken as examples in fig. 11.

The first user plane function network element, the second user plane function network element, and the session management function network element are respectively configured to implement the functions of the related network elements in fig. 5 or fig. 6. Please refer to the related description in the above method embodiments, which is not repeated herein.

An embodiment of the present application further provides a computer-readable storage medium, which includes instructions, when executed on a computer, to enable the computer to execute the method performed by the first to fourth user plane functional network elements and the session management functional network element in fig. 5 or fig. 6.

There is also provided in an embodiment of the present application a computer program product, which includes instructions that, when run on a computer, cause the computer to perform the method performed by the first to fourth user plane functionality network elements and the session management functionality network element in fig. 5 or 6.

The embodiment of the present application provides a chip system, where the chip system includes a processor and may further include a memory, and is configured to implement the functions of the first to fourth user plane functional network elements and the session management functional network element in the foregoing method. The chip system may be formed by a chip, and may also include a chip 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 in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the invention may be performed in whole or in part when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a computer network, a network appliance, a user device, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another, for example, from one website, computer, server, or datacenter, through wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL), for short) or wireless (e.g., infrared, wireless, microwave, etc.) means to another website, computer, server, or datacenter. DVD for short), or a semiconductor medium (e.g., SSD).

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include such modifications and variations.

Claims

1. A method for forwarding data, comprising:

a first user plane function network element receives a first data packet;

the first user plane functional network element determines a first path type of a sending path according to a routing rule matched with the first data packet, wherein the first path type comprises one or more of a loop interface type and a branch interface type, and the sending path is used for forwarding the first data packet to other user plane functional network elements;

and the first user plane function network element determines the sending path according to the first path type.

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

the first user plane functional network element determines, from at least one transmission path of the first user plane functional network element, a transmission path with a path type of the first path type as the transmission path;

the method further comprises the following steps:

and the first user plane functional network element forwards the first data packet to the other user plane functional network elements through the sending path.

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

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 with the same type as the first path;

the method further comprises the following steps:

and 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 to 3,

the routing rule includes a packet detection rule PDR for detecting the first packet or a forwarding behavior rule FAR for forwarding the first packet.

5. The method of claim 4, wherein the determining, by the first user plane function network element, the first path type according to the routing rule matched with the first packet comprises:

the first user plane functional network element determines a second path type of a receiving path according to the PDR, and the first user plane functional network element receives the first data packet through the receiving path;

and 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 of claim 5, wherein the determining, by the first user plane function network element, the second path type of the receive path according to the PDR comprises:

the PDR comprises a path type parameter of a receiving path, and the first user plane functional network element determines the second path type according to the value of the path type parameter of the receiving path; or the like, or a combination thereof,

the PDR includes a tunnel information parameter of a receiving path, and the first user plane functional network element determines the second path type according to a value of the tunnel information parameter of the receiving path and a path type of at least one transmission path of the first user plane functional network element.

7. The method according to claim 5 or 6, wherein the preset transmission rule comprises:

8. The method of claim 4, wherein the determining, by the first user plane function network element, the first path type according to the routing rule matched with the first packet comprises:

and the first user plane functional 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 of claim 5 or 6, further comprising:

the first user plane function network element receives a first indication from a session management function network element, where the first indication indicates 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-3, further comprising:

the first user plane function network element receives the routing rule from a session management function network element.

11. A method for forwarding data, comprising:

a session management function network element generates a set of routing rules corresponding to a first user plane function network element according to a path type of a transmission path of the first user plane function network element and a preset transmission rule, wherein the path type of the transmission path includes one or more of a loop interface type and a branch interface type, the preset transmission rule includes that if the path type of a receiving path is the loop interface type, the path type of a 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;

and the session management function network element sends the set of routing rules to the first user plane function network element.

12. The method of claim 11,

the set of routing rules includes a packet detection rule PDR for detecting a first packet and a forwarding behavior rule FAR for forwarding the first packet.

13. The method according to claim 11 or 12, wherein the set of routing rules generated by the session management function network element and corresponding to the first user plane function network element comprises:

a first PDR for detecting a first packet received from a first N19 path, the transmission path of the first user plane function network element comprising the first N19 path; and the number of the first and second groups,

a first FAR associated with the first PDR, the first FAR including tunnel information for a second N19 path, the transmission path of the first user plane function network element including the second N19 path.

14. The method of claim 13,

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 functional network element, and if the path type of the first N19 path is a branch interface type, the second N19 path is another N19 path except the first N19 path in the transmission path of the first user plane functional network element.

15. The method according to claim 11 or 12, wherein the generating, by the session management function network element, a set of routing rules corresponding to the first user plane function network element comprises:

a first PDR configured to detect a first packet received from a first N19 path, wherein a transmission path included in the first user plane function network element includes the first N19 path; and the number of the first and second groups,

a first FAR associated with the first PDR, the first FAR configured to forward the first packet to an internal interface of the first user plane function network element, the first FAR including a path type parameter of an outgoing interface, wherein the path type parameter of the outgoing interface includes the ring interface type or the branch interface type; and (c) a second step of,

a second PDR for detecting the first data packet received from the internal interface, the second PDR including a path type parameter of an incoming interface therein; and the number of the first and second groups,

a second FAR associated with the second PDR, the second FAR including tunnel information of a second N19 path, the transmission path of the first user plane function network element including the second N19 path, the second N19 path being one or more of transmission paths with path types of the loop interface type and the branch interface type.

16. The method of claim 15,

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, the value of the path type parameter of the outgoing interface is a branch interface type; and (c) a second step of,

17. The method according to claim 11 or 12, characterized in that the method further comprises:

and the session management function network element determines the path type of a transmission path of the first user plane function network element according to a network topology interface of a user plane of a 5G Local Area Network (LAN) group, wherein the first user plane function network element belongs to the 5GLAN group.

18. A communication apparatus, comprising a transceiving unit and a processing unit, wherein:

the receiving and sending unit is used for receiving a first data packet;

the processing unit is configured to determine a first path type of a transmission path according to a routing rule matched with the first data packet, where 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 functional network elements; and determining the sending path according to the first path type.

19. The apparatus according to claim 18, wherein the processing unit is specifically configured to:

determining a transmission path of which a path type is the first path type as the transmission path from among at least one transmission path of the communication apparatus;

the transceiver unit is further configured to:

and forwarding the first data packet to the other user plane functional network elements through the sending path.

20. The apparatus according to claim 18, wherein the processing unit is specifically configured to:

determining that a transmission path of the same type as the first path is not included in at least one transmission path of the communication device;

the processing unit is further to:

determining not to forward the first packet.

21. The apparatus of any one of claims 18-20,

22. The apparatus according to claim 21, wherein the processing unit is specifically configured to:

determining a second path type of a receiving path according to the PDR, and receiving the first data packet by the communication device through the receiving path;

and determining the first path type according to the second path type and a preset transmission rule.

23. The apparatus according to claim 22, wherein the processing unit is specifically configured to:

the PDR comprises a path type parameter of a 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 like, or, alternatively,

the PDR includes a tunnel information parameter of a receiving path, and the processing unit determines the second path type according to a value of the tunnel information parameter of the receiving path and a path type of at least one transmission path of the communication device.

24. The apparatus according to claim 22 or 23, wherein the preset transmission rule comprises:

25. The apparatus according to claim 21, wherein the processing unit is specifically configured to:

and determining the first path type according to the value of the path type parameter of the sending path included in the FAR.

26. The apparatus according to claim 22 or 23, wherein the transceiver unit is further configured to:

receiving a first indication from a session management function network element, the first indication indicating a path type of at least one transmission path of the communication device.

27. The apparatus according to any of claims 18-20, wherein the transceiver unit is further configured to:

receiving the routing rule from a session management function network element.

28. A communication apparatus, comprising a transceiving unit and a processing unit, wherein:

the processing unit is configured to generate a set of routing rules corresponding to a first user plane function network element according to a path type of a transmission path of the first user plane function network element and a preset transmission rule, where 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 a reception path is the loop interface type, the path type of a transmission path is the branch interface type, and if the path type of the reception 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 apparatus of claim 28,

30. The apparatus according to claim 28 or 29, wherein the processing unit is specifically configured to:

31. The apparatus of claim 30,

32. The apparatus according to claim 28 or 29, wherein the processing unit is specifically configured to:

a second PDR for detecting the first data packet received from the internal interface, the second PDR including a path type parameter of an incoming interface therein; and (c) a second step of,

33. The apparatus of claim 32,

34. The apparatus according to claim 28 or 29, wherein the processing unit is further configured to:

and determining the path type of a transmission path of the first user plane function network element according to a network topology interface of a user plane of a 5G Local Area Network (LAN) group, wherein the first user plane function network element belongs to the 5GLAN group.

35. A data forwarding system 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 a first user plane function network element according to a path type of a transmission path of the first user plane function network element and a preset transmission rule, where 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 a reception path is the loop interface type, the path type of a transmission path is the branch interface type, and if the path type of the reception path is the branch interface type, the path type of the transmission 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 matched with the first data packet;

the first user plane functional network element is used for receiving a first data packet; determining a first path type of a sending path of the first data packet according to a routing rule matched with the first data packet, wherein the first path type comprises one or more of the loop interface type and the branch interface type, and the sending path of the first data packet is used for forwarding the first data packet to other user plane functional network elements; and determining the sending path of the first data packet according to the first path type.