User plane traffic routing configuration method, apparatus, and system

Abstract

This disclosure proposes a user plane traffic routing configuration method, apparatus, and system, relating to the field of mobile communication technology. The method includes: a first SMF entity obtaining the Service Functions (SFC) rules for a user equipment (UE) in a roaming scenario from a second SMF entity; the first SMF entity sending an SFC access request to a first SFC controller; upon receiving the SFC access request, the first SFC controller negotiating a Service Functions path between the visited and home networks with the second SFC controller, and sending an SFC access response carrying traffic routing information of the Service Functions path to the first SMF entity, thereby enabling the first SMF entity to perform session configuration on a first UPF entity. Through this method, Service Functions routing can be configured flexibly and efficiently for user plane traffic at the session level, allowing user plane traffic to flexibly select automatically orchestrated Service Functions chains when flowing out from either the visited or home network.

Description

Technical Field

[0001] This disclosure relates to the field of mobile communication technology, and in particular to a user plane traffic routing configuration method, apparatus and system. Background Technology

[0002] Specifications such as IETF RFC 7665 define the architecture and protocols related to Service Function Chain (SFC). However, the current 5G standard does not support the related functions of the Service Function Chain architecture in either the control plane or the user plane.

[0003] In mobile network roaming solutions, such as home-routed roaming, when user traffic flows out of or into a User Plane Function (UPF) entity anchored in the visited 5G network or the home 5G network, it may need to pass through one or more service function entities, such as firewall devices or Network Address Translation (NAT) devices. In related technologies, these service function entities are deployed based on manual pre-configuration. In this approach, all outbound traffic from either the visited or home mobile network must pass through the same service function entity, which is detrimental to the implementation of automated, customized, and dynamic services, such as application acceleration, HTTP header enhancement, and legitimate interception, and makes it difficult to meet the various customized needs under the trend of network convergence. Furthermore, this approach requires manual configuration of the service function entities through which user plane traffic passes, resulting in long configuration times and poor scalability and real-time performance. Summary of the Invention

[0004] One technical problem this disclosure aims to solve is to provide a solution that, through negotiating service function chain strategies between the home and visited mobile networks, enables flexible and efficient configuration of service function routes for user plane traffic at the session level. This allows user plane traffic to flexibly select automatically orchestrated service function chains when flowing out from either the visited or home network, thereby achieving linkage between the visited and home networks when deploying services such as traffic acceleration. This makes the deployment, activation, and maintenance of related services more flexible and automated.

[0005] According to a first aspect of this disclosure, a user plane traffic routing configuration method is proposed, applied to a first area in a roaming scenario. The first area corresponds to a first Session Management Function (SMF) entity, a first Service Function Chain (SFC) controller, and a first User Plane Function (UPF) entity. The method includes: the first SMF entity obtaining SFC rules for the user equipment (UE) in the roaming scenario from a second SMF entity; the first SMF entity sending an SFC access request to a first SFC controller, wherein the SFC access request includes the SFC rules for the UE in the roaming scenario; after receiving the SFC access request, the first SFC controller negotiating a service function path between the visited location and the home location with the second SFC controller, and sending an SFC access response to the first SMF entity, wherein the SFC access response includes traffic routing information for the service function path between the visited location and the home location; the first SMF entity sending the traffic routing information to a first UPF entity, so that the first UPF entity forwards data packets corresponding to the session of the UE according to the traffic routing information, wherein the second SMF entity and the second SFC controller correspond to a second area in the roaming scenario.

[0006] In some embodiments, the SFC rules of the user equipment in a roaming scenario include the SFC rules of the user equipment in a first region, and the negotiation of the service function path between the visited location and the home location with the second SFC controller includes: the first SFC controller setting the service function path corresponding to the first region according to the SFC rules of the user equipment in the first region; the first SFC controller obtaining the service function path access information corresponding to the second region from the second SFC controller; and the first SFC controller determining the service function path between the visited location and the home location based on the service function path corresponding to the first region and the service function path access information corresponding to the second region.

[0007] In some embodiments, the first SFC controller obtaining service function path access information corresponding to the second region from the second SFC controller includes: the first SFC controller obtaining access information of the second SFC controller from the SFC access request; the first SFC controller sending an SFC indirect access request to the second SFC controller according to the access information of the second SFC controller; and the first SFC controller receiving an SFC indirect access response returned by the second SFC controller, wherein the SFC indirect access response includes service function path access information corresponding to the second region.

[0008] In some embodiments, the SFC access request includes at least one of the following: access information of the first SFC controller and service function path access information corresponding to the first region.

[0009] In some embodiments, the first SMF entity obtaining the SFC rules of the user equipment in the roaming scenario from the second SMF entity includes: the first SMF entity sending a Protocol Data Unit (PDU) session establishment request to the second SMF entity; the first SMF entity receiving a PDU session establishment response sent by the second SMF entity, wherein the PDU session establishment response includes the SFC rules of the user equipment in the roaming scenario.

[0010] In some embodiments, the PDU session establishment request carries a first capability identifier, which is used to indicate that the first region supports the SFC function.

[0011] In some embodiments, the PDU session establishment response may also include access information for a second SFC controller.

[0012] In some embodiments, the method further includes: a first SMF entity sending traffic classification information of the user equipment in the SFC rules of the first area to a first UPF entity, wherein the traffic classification information is used to instruct the first UPF entity to classify the data packets corresponding to the session of the user equipment.

[0013] In some embodiments, the first region is the visited region and the second region is the home region.

[0014] According to a second aspect of this disclosure, another user plane traffic routing configuration method is also proposed, applied to a second area in a roaming scenario. The second area corresponds to a second Session Management Function (SMF) entity, a second Service Function Chain (SFC) controller, and a second User Plane Function (UPF) entity. The method includes: the second SMF entity obtaining the SFC rules of the user equipment (UE) in the roaming scenario and sending the SFC rules of the UE in the roaming scenario to a first SMF entity; in response to an SFC indirect access request from the first SFC controller, the second SFC controller and the first SFC controller negotiate a service function path between the visited location and the home location, and send traffic routing information of the service function path between the visited location and the home location to the second SMF entity; the second SMF entity sends the traffic routing information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the session of the UE according to the traffic routing information, wherein the first SMF entity and the first SFC controller correspond to a first area in the roaming scenario.

[0015] In some embodiments, the negotiation of the service function path between the visited location and the home location between the second SFC controller and the first SFC controller includes: the second SFC controller obtaining service function path access information corresponding to the first region from the SFC access request; the second SFC controller determining the service function path between the visited location and the home location based on the service function path corresponding to the second region and the service function path access information corresponding to the first region, wherein the service function path corresponding to the second region is determined according to the SFC rules of the user equipment in the second region.

[0016] In some embodiments, the negotiation of the service function path between the visited location and the home location between the second SFC controller and the first SFC controller further includes: the second SFC controller sending an SFC indirect access response to the first SFC controller, wherein the SFC indirect access response includes service function path access information corresponding to the second region.

[0017] In some embodiments, the second SFC controller sends an SFC indirect access response to the first SFC controller based on the access information of the first SFC controller carried in the SFC indirect access request.

[0018] In some embodiments, the second SMF entity obtains the Service Function Chain (SFC) rules of the user equipment in the roaming scenario by: the second SMF entity sending a new session management policy query request to the Policy and Accounting Function (PCF) entity, wherein the PCF entity corresponds to the second region; the second SMF entity receiving the new session management policy query response returned by the PCF entity, wherein the new session management policy query response includes the SFC rules of the user equipment in the roaming scenario.

[0019] In some embodiments, the method further includes: before the second SMF entity obtains the SFC rules of the user equipment in the roaming scenario, the second SMF entity receives a Protocol Data Unit (PDU) session establishment request sent by the first SMF entity, wherein the PDU session establishment request carries a first capability identifier, the first capability identifier being used to indicate that the first area supports the SFC function.

[0020] In some embodiments, sending the SFC rules of the user equipment in the roaming scenario to the first SMF entity includes: the second SMF entity sending a PDU session establishment response to the first SMF entity, wherein the PDU session establishment response includes the service function chain SFC rules of the user equipment in the roaming scenario.

[0021] In some embodiments, the PDU session establishment response may also include access information for a second SFC controller.

[0022] In some embodiments, the method further includes: a second SMF entity sending traffic classification information of the user equipment in the SFC rules of the second region to a second UPF entity, wherein the traffic classification information is used to instruct the second UPF entity to classify the data packets corresponding to the user equipment's session.

[0023] In some embodiments, the first region is the visited region and the second region is the home region.

[0024] According to a third aspect of this disclosure, another user plane traffic routing configuration method is proposed, applied to a roaming scenario. The first region corresponds to a first Session Management Function (SMF) entity, a first Service Function Chain (SFC) controller, and a first User Plane Function (UPF) entity; the second region corresponds to a second SMF entity, a second SFC controller, and a second UPF entity. The method includes: the second SMF entity obtaining the SFC rules of the user equipment (UE) in the roaming scenario and sending the SFC rules to the first SMF entity; the first SMF entity sending an SFC access request to the first SFC controller, wherein the SFC access request includes the SFC rules of the UE in the roaming scenario; and the first SFC controller negotiating with the second SFC controller after receiving the SFC access request. The service function path between the visited location and the home location is defined, and an SFC access response is sent to the first SMF entity. The SFC access response includes first traffic routing information for the service function path between the visited location and the home location. The first SMF entity sends the first traffic routing information to a first User Plane Function (UPF) entity, so that the first UPF entity forwards data packets corresponding to the user equipment's session according to the first traffic routing information. The second SFC controller sends second traffic routing information for the service function path between the visited location and the home location to a second SMF entity. The second SMF entity sends the second traffic routing information to a second UPF entity, so that the second UPF entity forwards data packets corresponding to the user equipment's session according to the second traffic routing information.

[0025] According to the fourth aspect of this disclosure, a user plane traffic routing configuration device is also proposed, applied to a first area in a roaming scenario, including a first session management function (SMF) entity, a first service function chain (SFC) controller, and a first user plane function (UPF) entity corresponding to the first area; the first SMF entity is configured to obtain the SFC rules of the user equipment in the roaming scenario from a second SMF entity; the first SMF entity is further configured to send an SFC access request to a first SFC controller, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario; the first SFC controller is configured to, after receiving the SFC access request, negotiate the service function path between the visited location and the home location with the second SFC controller, and send an SFC access response to the first SMF entity, wherein the SFC access response includes traffic routing information of the service function path between the visited location and the home location; the first SMF entity is configured to send the traffic routing information to a first UPF entity, so that the first UPF entity forwards the data packets corresponding to the session of the user equipment according to the traffic routing information, wherein the second SMF entity and the second SFC controller correspond to a second area in the roaming scenario.

[0026] According to the fifth aspect of this disclosure, another user plane traffic routing configuration device is also proposed, applied to a second area in a roaming scenario, including a second session management function (SMF) entity, a second service function chain (SFC) controller, and a second user plane function (UPF) entity corresponding to the second area; the second SMF entity is configured to obtain the SFC rules of the user equipment in the roaming scenario and send the SFC rules of the user equipment in the roaming scenario to the first SMF entity; the second SFC controller is configured to, in response to the SFC indirect access request of the first SFC controller, negotiate the service function path between the visited location and the home location with the first SFC controller, and send the traffic routing information of the service function path between the visited location and the home location to the second SMF entity; the second SMF entity is further configured to send the traffic routing information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the session of the user equipment according to the traffic routing information, wherein the first SMF entity and the first SFC controller correspond to the first area in the roaming scenario.

[0027] According to the sixth aspect of this disclosure, a user plane traffic routing configuration system is also proposed for use in roaming scenarios, comprising: a first session management function (SMF) entity, a first service function chain (SFC) controller, and a first user plane function (UPF) entity corresponding to a first region; and a second SMF entity, a second SFC controller, and a second UPF entity corresponding to a second region. The second SMF entity is configured to acquire the SFC rules of the user equipment in the roaming scenario and send the SFC rules of the user equipment in the roaming scenario to the first SMF entity. The first SMF entity is configured to send an SFC access request to the first SFC controller, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario. The first SFC controller is configured to negotiate access with the second SFC controller after receiving the SFC access request. The service function path between the visited location and the home location is configured to send an SFC access response to the first SMF entity, wherein the SFC access response includes first traffic routing information for the service function path between the visited location and the home location; the first SMF entity is further configured to send the first traffic routing information to a first UPF entity, so that the first UPF entity forwards data packets corresponding to the session of the user equipment according to the first traffic routing information; the second SFC controller is configured to send second traffic routing information for the service function path between the visited location and the home location to a second SMF entity; the second SMF entity is further configured to send the second traffic routing information to a second UPF entity, so that the second UPF entity forwards data packets corresponding to the session of the user equipment according to the second traffic routing information.

[0028] According to the seventh aspect of this disclosure, another user plane traffic routing configuration apparatus is also proposed, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the above-described user plane traffic routing configuration method based on instructions stored in the memory.

[0029] According to the eighth aspect of this disclosure, a computer-readable storage medium is also provided, having stored thereon computer program instructions that, when executed by a processor, implement the user plane traffic routing configuration method described above.

[0030] Compared with related technologies, in this embodiment, the first SMF entity obtains the SFC rules of the user equipment in the roaming scenario from the second SMF entity, sends an SFC access request carrying the SFC rules to the first SFC controller, and after receiving the SFC access request, the first SFC controller negotiates the service function path between the visited and home networks with the second SFC controller, and sends the traffic guidance information of the service function path to the first SMF entity, so that the first SMF entity can perform session configuration for the first UPF entity. These steps enable flexible and efficient configuration of service function routes for user plane traffic at the session level, so that user plane traffic can flexibly select automatically orchestrated service function chains when flowing out from the visited or home network side, thereby achieving linkage between the visited and home networks when deploying traffic acceleration and other service functions, making the deployment, activation and maintenance of related services more flexible and automated.

[0031] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0032] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0033] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein:

[0034] Figure 1 This is a schematic diagram of the reference network architecture for the 5G core network in related technologies.

[0035] Figure 2 This is a flowchart illustrating a user plane traffic routing configuration method according to some embodiments of the present disclosure.

[0036] Figure 3 This is a flowchart illustrating a user plane traffic routing configuration method according to other embodiments of the present disclosure.

[0037] Figure 4 This is a flowchart illustrating a user plane traffic routing configuration method according to some embodiments of the present disclosure.

[0038] Figure 5 This is a schematic diagram of the structure of a user plane traffic routing configuration apparatus according to some embodiments of the present disclosure.

[0039] Figure 6 This is a schematic diagram of the structure of a user plane traffic routing configuration apparatus according to other embodiments of the present disclosure.

[0040] Figure 7 This is a schematic diagram of the structure of a user plane traffic routing configuration system according to some embodiments of the present disclosure.

[0041] Figure 8 This is a schematic diagram of the structure of a user plane traffic routing configuration apparatus according to some embodiments of the present disclosure.

[0042] Figure 9 This is a schematic diagram of the structure of a computer system according to some embodiments of the present disclosure. Detailed Implementation

[0043] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0044] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0045] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0046] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0047] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0048] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0049] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0050] Figure 1 This is a schematic diagram of a reference network architecture for the 5G core network in related technologies. For example... Figure 1 As shown, the 5G core network reference network architecture includes multiple network functional entities (or "network elements"). The 5G core network achieves complete separation between the control plane and the user plane. The control plane can be centrally deployed to globally schedule forwarding resources, while the user plane can be flexibly deployed centrally or in a distributed manner as needed.

[0051] This disclosure primarily relates to user equipment 101, user plane function entity 103, session management function entity 107, and policy and charging function entity 111 in the 5G core network reference network architecture. These function entities are briefly described below.

[0052] User equipment 101, UE, such as a user's smartphone, tablet, or other terminal device. User equipment 101 forms a radio access network connection with radio access network node 102, which is connected to user plane function entity 103 via the N3 interface. User equipment 101 is also connected to access and mobility management function entity 106 via the N1 interface.

[0053] User plane function entity 103, UPF entity, is mainly responsible for forwarding data packets.

[0054] Session Management Function (SMF) entity 107 supports various functions, such as session establishment and modification, IP address allocation and management for user equipment, and user plane selection and control. The SMF entity can communicate with other core network function entities via the Nsmf interface, and can also connect to the UPF entity via the N4 interface.

[0055] Policy and Charging Function Entity 111, the PCF entity, is primarily responsible for managing network behavior based on a unified policy framework. For example, the PCF provides Policy and Charging Control (PCC) rules to the SMF entity.

[0056] In related technologies, neither the control plane nor the user plane of the 5G core network supports the relevant functions in the service function chain architecture. All outbound traffic from the visited or home mobile network side must pass through the same service function entity, which is not conducive to the development of automated, customized, and variable services. Moreover, in related technologies, the routing configuration of the service function entity through which user plane traffic passes needs to be performed manually, which takes a long time and has poor scalability and real-time performance.

[0057] In response to the shortcomings of related technologies, the inventors of this disclosure conceived of a service function chain negotiation strategy between the home and visited mobile networks. This strategy enables flexible and efficient configuration of service function routes for user plane traffic at the session level. As user plane traffic flows out from either the visited or home network, it can flexibly select automatically orchestrated service function chains. This allows for the linkage between the visited and home networks when deploying services such as traffic acceleration, making the deployment, activation, and maintenance of related services more flexible and automated.

[0058] Figure 2This is a flowchart illustrating a user plane traffic routing configuration method according to some embodiments of this disclosure. In the embodiments of this disclosure, the first SMF entity, the first SFC controller, and the first UPF entity correspond to a first area in a roaming scenario; the second SMF entity and the second SFC controller correspond to a second area in a roaming scenario. In some embodiments, the first area is the visited location, and the second area is the home location. Figure 2 As shown, the method includes the following steps:

[0059] Step S210: The first SMF entity obtains the SFC rules of the user device in the roaming scenario from the second SMF entity.

[0060] In step S210, the first SMF entity actively or passively obtains the SFC rules of the user equipment in the roaming scenario from the second SMF entity.

[0061] In some embodiments, step S210 includes: a first SMF entity sending a Protocol Data Unit (PDU) session establishment request to a second SMF entity; the first SMF entity receiving a PDU session establishment response returned by the second SMF entity; wherein the PDU session establishment response includes the SFC rules of the user equipment in a roaming scenario. Optionally, the PDU session establishment response also includes access information of the second SFC controller. The access information of the second SFC controller includes, but is not limited to, the IP address, port number, access key, and access identifier of the second SFC controller.

[0062] In one optional implementation, the PDU session establishment request carries a first capability identifier, which indicates that the first area supports the SFC function. In this optional implementation, after receiving the PDU session establishment request, the second SMF entity determines whether the request carries the first capability identifier. If the request carries the first capability identifier, it executes the subsequent processing steps in this embodiment; if the request does not carry the first capability identifier, it executes the relevant standard processing procedures for mobile network roaming scenarios, such as the standard processing procedures for 5G network roaming scenarios.

[0063] In other embodiments, step 210 includes: the first SMF entity receiving the SFC rules for the user equipment in the roaming scenario actively issued by the second SMF.

[0064] In this embodiment of the disclosure, the SFC rules for the user equipment in a roaming scenario obtained by the first SMF entity from the second SMF entity include at least the SFC rules for the user equipment in the first area. For example, when the first area is a visited network, the SFC rules obtained by the first SMF entity from the second SMF entity include at least the SFC rules for the visited network.

[0065] In one optional example, the SFC rules in a roaming scenario include, but are not limited to, the following: roaming visited or home location indication, traffic classification information, and a list of service functions.

[0066] The roaming visited location or home location indication is used to specify the SFC rule in this roaming scenario.

[0067] Is it the SFC rule for the visited location or the SFC rule for the home location? Traffic classification information includes...

[0068] However, it is not limited to a combination of one or more of the following: target IP address range, target port

[0069] Number, network protocol type, packet length, data network name (DNN), 5G QoS index

[0070] Displays (5QI), etc. The service function list information includes a sequence of service functions that reflects the flow of traffic.

[0071] In another optional example, the SFC rule in a roaming scenario includes, in addition to the roaming visited or home location indication, traffic classification information, and service function list, a traffic direction identifier. The traffic direction identifier is uplink, downlink, or uplink-downlink, indicating that the traffic to which the SFC rule applies is uplink traffic, downlink traffic, or uplink-downlink traffic.

[0072] Step S220: The first SMF entity sends an SFC access request to the first SFC controller.

[0073] After obtaining the SFC rules in the roaming scenario, the first SMF entity sends an SFC access request carrying the SFC rules of the user equipment in the first area to the first SFC controller.

[0074] In some embodiments, the SFC access request includes, in addition to the SFC rules for the user equipment in the first area, one or more of the following: the location of the user equipment and the data network name (DNN). By carrying information such as the user equipment location and DNN in the SFC access request, the SFC controller can select a more suitable service function path, thereby improving the service function routing effect.

[0075] In other embodiments, the SFC access request includes not only the SFC rules of the user equipment in the first area, but also access information of the second SFC controller. This access information can be obtained by the first SMF entity from the second SMF entity; for example, the first SMF entity can obtain the access information of the second SFC controller from the PDU session establishment response sent by the second SMF entity. By including the access information of the second SFC controller in the SFC access request, the first SFC controller can quickly establish communication with the second SFC controller, thereby improving the efficiency of service function path negotiation.

[0076] Step S230: After receiving the SFC access request, the first SFC controller negotiates the service function path between the visited location and the home location with the second SFC controller, and sends an SFC access response to the first SMF entity.

[0077] In some embodiments, the negotiation of the service function path between the visited location and the home location between the first SFC controller and the second SFC controller includes steps S231 to S233.

[0078] Step S231: The first SFC controller sets the service function path corresponding to the first area according to the SFC rules of the user equipment in the first area.

[0079] In one alternative implementation, the first SFC controller selects, modifies, or creates a corresponding Service Function Path (SFP) based on the SFC rules of the user equipment carried in the SFC access request in the first area.

[0080] In another optional implementation, the first SFC controller selects, modifies, or creates a service function path corresponding to the first area based on the SFC rules of the user equipment in the first area, the location of the user equipment, and the data network name carried in the SFC access request. For example, the first SFC controller selects an SFP that can support the service function requested by the SFC rules; the first SFC controller selects an SFP that is closer to the user equipment deployment based on the location of the user equipment; and the first SFC controller selects an SFP corresponding to the data network based on the data network name, so that traffic from different data networks does not share the same SFP.

[0081] Step S232: The first SFC controller obtains the service function path access information corresponding to the second area from the second SFC controller.

[0082] In one optional implementation, the SFC access request carries access information of the second SFC controller. In this optional implementation, the first SFC controller obtains the access information of the second SFC controller from the SFC access request; the first SFC controller sends an SFC indirect access request to the second SFC controller based on the access information of the second SFC controller; the first SFC controller receives an SFC indirect access response returned by the second SFC controller, wherein the SFC indirect access response includes service function path access information corresponding to the second area.

[0083] For example, the SFC indirect access request includes at least one of the following: access information of the first SFC controller and service function path access information corresponding to the first region. By carrying the access information of the first SFC controller in the SFC indirect access request, the second SFC controller can communicate with the first SFC controller accordingly; by carrying the service function path access information corresponding to the first region in the SFC indirect access request, the second SFC controller can quickly determine the service function path between the visited location and the home location, thus improving the SFP negotiation efficiency.

[0084] In another optional implementation, the SFC access request does not carry the access information of the second SFC controller. In this optional implementation, the first SFC controller first queries the access information of the second SFC controller, then sends an SFC access request to the second SFC controller accordingly, and receives the service function path access information corresponding to the second area sent by the second SFC controller.

[0085] For example, the service function path access information corresponding to the second region includes, but is not limited to: access IP and access port number.

[0086] Step S233: The first SFC controller determines the service function path between the visited location and the home location based on the service function path corresponding to the first region and the service function path access information corresponding to the second region.

[0087] In some embodiments, the first region is the visited network, and the first SFC controller determines the service function path between the visited and the home network based on the service function path corresponding to the visited network and the service function path access information corresponding to the home network, specifically the service function path from the visited to the home network.

[0088] In this embodiment of the disclosure, steps S231 to S233 enable the SFP of the first area to be connected to the SFP of the second area, which facilitates the subsequent service function routing of data packets corresponding to user equipment sessions.

[0089] After the first SFC controller obtains the service function path between the visited location and the home location, it generates traffic routing information for that service function path and sends an SFC access response carrying that traffic routing information to the first SMF entity. Optionally, the SFC access response may also include a negotiation success indicator to indicate that the two networks in a roaming scenario have successfully negotiated the service function path between the visited location and the home location.

[0090] In some embodiments, the traffic routing information of the SFP includes a Network Service Header (NSH). The NSH is an encapsulation format designed for service chains. The NSH includes basic header fields, service function path identifiers, and other fields.

[0091] In other embodiments, the traffic routing information of the SFP may include, in addition to NSH, a combination of one or more of the following: transport layer protocol type, network layer protocol type, access IP address of the service function path, access port number of the service function path, etc.

[0092] Step S240: The first SMF entity sends traffic guidance information to the first UPF entity so that the first UPF entity forwards the data packets corresponding to the user equipment session according to the traffic guidance information.

[0093] In some embodiments, the first SMF entity sends a session modification request to the first UPF entity. For example, in a 5G core network, the first SMF entity sends the session modification request to the first UPF entity via the N4 interface. The session modification request includes traffic guidance information for the service function path determined in steps 210 to 230. This traffic guidance information instructs the first UPF entity to forward data packets corresponding to the user plane session to the corresponding service function path. When the user equipment sends uplink traffic, the first UPF entity encapsulates different data packets based on the traffic guidance information. For example, it adds NSH to the original data packets and performs transport layer and network layer encapsulation, then forwards the encapsulated data packets to one or more SFPs.

[0094] In other embodiments, the session modification request sent by the first SMF entity to the first UPF entity includes, in addition to traffic guidance information for the service function path determined through steps 210 to 230, SFC rule parameters of the user equipment in the first area, such as traffic classification information in the SFC rules of the user equipment in the first area. This traffic classification information is used to instruct the first UPF entity to classify the data packets corresponding to the session. When the user equipment sends uplink traffic, the first UPF entity classifies the data packets corresponding to the session according to the traffic classification information in the SFC rules, encapsulates different data packets based on the traffic guidance information, for example, adding NSH to the original data packets and performing transport layer and network layer encapsulation, and then forwarding the encapsulated data packets to one or more SFPs.

[0095] In this embodiment, the above steps enable flexible and efficient configuration of service function routing for user plane traffic at the session granularity in roaming scenarios. This allows user plane traffic to flexibly select automatically orchestrated service function chains when flowing out of the first roaming area, thereby achieving linkage between the visited and home networks when deploying services such as traffic acceleration. This makes the deployment, activation, and maintenance of related services more flexible and automated. Furthermore, since services can be provided on demand according to users' customized needs, investment in high-end service hardware and software can be reduced to some extent. Therefore, the method of this embodiment has good prospects for domestic cross-provincial relocation and international application in 5G or 6G network scenarios.

[0096] Figure 3 This is a flowchart illustrating a user plane traffic routing configuration method according to other embodiments of this disclosure. In embodiments of this disclosure, the second SMF entity, the second SFC controller, the second UPF entity, and the Policy and Charging Function (PCF) entity correspond to a second region in a roaming scenario, and the first SMF entity and the first SFC controller correspond to a first region in a roaming scenario. In some embodiments, the first region is the visited region, and the second region is the home region.

[0097] like Figure 3 As shown, the method includes the following steps:

[0098] Step S310: The second SMF entity obtains the SFC rules of the user equipment in the roaming scenario and sends the SFC rules of the user equipment in the roaming scenario to the first SMF entity.

[0099] In step S310, the second SMF entity proactively, or in response to a request from the first SMF entity, sends the obtained SFC rules for the user equipment in the roaming scenario to the first SMF entity.

[0100] In some embodiments, after receiving a Protocol Data Unit (PDU) session establishment request from the first SMF entity, the second SMF entity obtains the SFC rules for the user equipment in the roaming scenario from the PCF entity, and then sends the SFC rules for the user equipment in the roaming scenario in the PDU session establishment response to the first SMF entity. Optionally, the PDU session establishment response also includes access information of the second SFC controller and interface tunnel information on the first area side, such as N9 interface tunnel information on the visited area side in a 5G network. By carrying the access information of the second SFC controller in the PDU session establishment response, it is easier for the first SFC controller and the second SFC controller to quickly establish communication, thereby improving the efficiency of service function path negotiation.

[0101] The second SMF entity can obtain the SFC rules of the user equipment in the roaming scenario from the PCF entity in the following exemplary manner: the second SMF entity sends a new session management policy query request to the PCF entity; the second SMF entity receives the new session management policy query response returned by the PCF entity, wherein the new session management policy query response includes the SFC rules of the user equipment in the roaming scenario.

[0102] In other embodiments, after receiving a PDU session establishment request, the second SMF entity first determines whether the request carries a first capability identifier. If the request carries a first capability identifier, it executes the subsequent processing steps in this embodiment; if the request does not carry a first capability identifier, it executes the standard processing procedures related to mobile network roaming scenarios, such as the standard processing procedures related to 5G network roaming scenarios. The first capability identifier indicates that the first area supports SFC functionality. By determining whether the PDU session establishment request carries a first capability identifier, unnecessary operations such as obtaining SFC rules can be avoided when the first area does not support SFC functionality, thus optimizing the service function routing configuration process in roaming scenarios.

[0103] The SFC rules of the user equipment in the roaming scenario obtained by the second SMF entity include the SFC rules of the user equipment in the first area and the SFC rules of the user equipment in the second area. The second SMF entity sends at least the SFC rules of the user equipment in the first area to the first SMF entity.

[0104] Step S320: In response to the SFC indirect access request of the first SFC controller, the second SFC controller negotiates the service function path between the visited location and the home location with the first SFC controller, and sends the traffic guidance information of the service function path to the second SMF entity.

[0105] In some embodiments, the negotiation of the service function path between the visited location and the home location between the second SFC controller and the first SFC controller includes: the second SFC controller obtaining service function path access information corresponding to the first region from the SFC access request; and the second SFC controller determining the service function path between the visited location and the home location based on the service function path corresponding to the second region and the service function path access information corresponding to the first region.

[0106] The service function path access information corresponding to the first region includes, but is not limited to, the following information: the access IP and access port number of the service function path corresponding to the first region.

[0107] The service function path corresponding to the second region is determined in advance by the second SFC controller according to the SFC rules of the user equipment in the second region before receiving the SFC indirect access request; or, after receiving the SFC indirect access request, it is determined by the second SFC controller according to the SFC rules of the user equipment in the second region.

[0108] In some embodiments, after step S320, the method further includes: the second SFC controller sending an SFC indirect access response to the first SFC controller. For example, the second SFC controller sends an SFC indirect access response to the first SFC controller based on the access information of the first SFC controller carried in the SFC indirect access request.

[0109] The SFC indirect access response includes the service function path access information corresponding to the second region, including but not limited to the following information: the access IP and access port number of the service function path corresponding to the second region.

[0110] Step S330: The second SMF entity sends traffic guidance information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the user equipment session according to the traffic guidance information.

[0111] In some embodiments, the second SMF entity sends a session modification request to the second UPF entity. For example, in a 5G core network, the second SMF entity sends the session modification request to the second UPF entity via the N4 interface. The session modification request includes traffic guidance information for the service function path determined in steps 310 to 320. This traffic guidance information instructs the second UPF entity to forward data packets corresponding to the user plane session to the corresponding service function path. When the user equipment sends uplink traffic, the second UPF entity encapsulates different data packets based on the traffic guidance information. For example, it adds NSH to the original data packets and performs transport layer and network layer encapsulation, then forwards the encapsulated data packets to one or more SFPs.

[0112] In other embodiments, the session modification request sent by the second SMF entity to the second UPF entity includes, in addition to traffic guidance information for the service function path determined through steps 310 to 320, SFC rule parameters of the user equipment in the second area, such as traffic classification information in the SFC rules of the user equipment in the second area. This traffic classification information is used to instruct the second UPF entity to classify the data packets corresponding to the session. Upon receiving downlink traffic, the second UPF entity classifies the data packets corresponding to the session according to the traffic classification information, encapsulates different data packets based on the traffic guidance information, for example, by adding NSH to the original data packets and performing transport layer and network layer encapsulation, and then forwards the encapsulated data packets to one or more SFPs.

[0113] In this embodiment, the above steps enable flexible and efficient configuration of service function routing for user plane traffic at the session granularity in roaming scenarios. This allows user plane traffic to flexibly select automatically orchestrated service function chains when flowing out of the second roaming area, thereby achieving linkage between the visited and home networks when deploying services such as traffic acceleration. This makes the deployment, activation, and maintenance of related services more flexible and automated. Furthermore, since services can be provided on demand according to users' customized needs, investment in high-end service hardware and software can be reduced to some extent. Therefore, the method of this embodiment has good prospects for domestic cross-provincial relocation and international application in 5G or 6G network scenarios.

[0114] Figure 4 This is a flowchart illustrating a user plane traffic routing configuration method according to some embodiments of the present disclosure. In embodiments of the present disclosure, the first region in a roaming scenario corresponds to a first Session Management Function (SMF) entity, a first Service Function Chain (SFC) controller, and a first User Plane Function (UPF) entity; the second region in a roaming scenario corresponds to a second SMF entity, a second SFC controller, and a second UPF entity. In some embodiments, the first region is the visited region, and the second region is the home region. Figure 4 As shown, the method includes:

[0115] Step 401: The first SMF entity sends a PDU session establishment request to the second SMF entity.

[0116] When a user equipment (UE) moves to a first-area mobile network, the relevant network elements in the first-area network determine that the UE session is subject to roaming mode. When creating a session for the UE in the first area during roaming, the method of this disclosure embodiment is executed. For example, when the UE moves to a visited 5G network, the access and mobility management function entity of the visited location determines that the UE session uses Home-routed roaming mode. This roaming mode refers to the roaming user accessing and obtaining services provided by the home network through the home network's gateway H-PGW. When creating a session for the UE in the visited location, the method of this disclosure embodiment is executed.

[0117] In step 401, optionally, the PDU session establishment request carries a first capability identifier, which indicates that the first area supports the SFC function. Additionally, the PDU session establishment request may also carry visited-side N9 interface tunnel information (CN Tunnel Info), etc.

[0118] In some embodiments, before step 401, the method further includes: the first SMF entity sending a session establishment request to the first UPF entity, and the first UPF entity returning a session establishment response to the first SMF entity. For example, in a 5G network, the first SMF entity sends an N4 session establishment request to the first UPF entity, and the first UPF entity returns an N4 session establishment response to the first SMF entity. This response carries basic session information, such as CN Tunnel Info.

[0119] Step 402: The second SMF entity sends a new session management policy query request to the PCF entity.

[0120] Step 403: The PCF entity returns a new session management policy query response to the second SMF entity.

[0121] In this embodiment of the disclosure, the PCF entity corresponds to the second area in the roaming scenario, and it stores the policy and charging (PCC) rules of the user equipment. If the PCC rules of the user equipment contain one or more SFC rules of the user equipment in the roaming scenario (i.e., roaming SFC rules), then after receiving the new session management policy query request from the second SMF entity, the roaming SFC rules of the user equipment are carried in the new session management policy query response and sent to the second SMF entity.

[0122] In some embodiments, if the roaming SFC rules of a user device include both default roaming SFC rules and dynamic roaming SFC rules, the dynamic roaming SFC rules shall prevail.

[0123] In other embodiments, if the roaming SFC rules of the user equipment include both default roaming SFC rules and dynamic roaming SFC rules, it is necessary to comprehensively determine, based on one or more factors, whether to follow the default roaming SFC rules or the dynamic roaming SFC rules.

[0124] In an optional example, the SFC rules for a user equipment in a roaming scenario include, but are not limited to, the following: roaming visited or home location indication, traffic classification information, and a service function list. The roaming visited or home location indication indicates whether the SFC rule in this roaming scenario is an SFC rule for the visited location or an SFC rule for the home location. The traffic classification information includes, but is not limited to, a combination of one or more of the following: destination IP address range, destination port number, network protocol type, packet length, data network name (DNN), 5G QoS indicator (5QI), etc. The service function list information includes a sequence of service functions that reflect the sequential path of the traffic.

[0125] In another optional example, the SFC rule for a user device in a roaming scenario includes, in addition to the roaming visited or home location indication, traffic classification information, and a list of service functions, a traffic direction identifier. The traffic direction identifier is uplink, downlink, or uplink-downlink, indicating that the traffic to which the SFC rule applies is uplink traffic, downlink traffic, or uplink-downlink traffic.

[0126] Step 404: The second SMF entity sends an SFC access request to the second SFC controller.

[0127] In some embodiments, the SFC rules for the user equipment in the roaming scenario obtained by the second SMF entity from the PCF entity include: the SFC rules for the user equipment in the first region and the SFC rules for the user equipment in the second region. The SFC rules for the user equipment in the first region and the SFC rules for the user equipment in the second region can be the same or different SFC rules.

[0128] After obtaining the SFC rules in the roaming scenario, the second SMF entity sends an SFC access request to the second SFC controller. The SFC access request carries the SFC rules of the user equipment in the second area.

[0129] In some embodiments, the SFC access request includes, in addition to the SFC rules for the user equipment in the second area, one or more of the following: the location of the user equipment and the data network name (DNN). By carrying information such as the user equipment location and DNN in the SFC access request, the second SFC controller can select a more suitable service function path, thereby improving the service function routing effect.

[0130] Step 405: Configure the SFP on the second SFC controller.

[0131] For example, the SFC controller selects, modifies, or creates a Service Function Path (SFP) corresponding to the second area based on the SFC rules carried in the SFC access request, as well as one or more of the location of the user equipment and the data network name.

[0132] Step 406: The second SFC controller returns an SFC access response to the second SMF entity.

[0133] The SFC access response sent by the second SFC controller includes traffic guidance information for the SFP corresponding to the second area.

[0134] For example, the traffic guidance information for the SFP corresponding to the second region includes: Network Service Header (NSH). NSH is an encapsulation format designed for service chains. NSH includes basic header fields, service function path identifier, etc. In addition, the traffic guidance information may also include one or more combinations of the following: transport layer protocol type, network layer protocol type, access IP address of the service function path, access port number of the service function path, etc.

[0135] Optionally, the SFC access response may also include access information of the second SFC controller. This access information includes, but is not limited to, the access IP address, access port number, access key, and access identifier of the second SFC controller.

[0136] Step 407: The second SMF entity sends a session establishment request to the second UPF entity.

[0137] For example, in a 5G network, the second SMF entity sends an N4 session establishment request to the second UPF entity.

[0138] In some embodiments, the session establishment request includes traffic classification information in the SFP corresponding to the second area and traffic routing information in the SFP corresponding to the second area. When the second UPF entity receives downlink traffic from the user equipment, it classifies the data packets in the downlink traffic according to the traffic classification information in the SFP corresponding to the second area; and encapsulates and forwards the data packets of different classifications according to the traffic routing information in the SFP corresponding to the second area.

[0139] In some embodiments, before step 407, the method further includes: the second SMF entity selecting a second UPF entity from multiple UPF entities corresponding to the second region based on one or more factors such as SFC function support and SFP location information.

[0140] Step 408: The second UPF entity returns a session establishment response to the second SMF entity.

[0141] For example, in a 5G network, the second UPF entity returns an N4 session establishment response to the second SMF entity.

[0142] Step 409: The second SMF entity returns a PDU session establishment response to the first SMF entity.

[0143] The PDU session establishment response includes the SFC rules of the user equipment in the first area. Optionally, the PDU session establishment response may also include access information of the second SFC controller.

[0144] Step 410: The first SMF entity sends an SFC access request to the first SFC controller.

[0145] In some embodiments, the SFC access request includes the SFC rules of the user equipment in a first area and access information of the second SFC controller. Optionally, the SFC access request may also include the location of the user equipment and information such as the DNN.

[0146] Step 411: Configure the SFP on the first SFC controller.

[0147] In some embodiments, the first SFC controller sets the SFP corresponding to the first region based on information such as the SFC rules of the user equipment in the first region.

[0148] Step 412: The first SFC controller sends an SFC indirect access request to the second SFC controller.

[0149] In some embodiments, the SFC indirect access request includes service function path access information corresponding to the first region. By carrying the service function path access information corresponding to the first region in the SFC indirect access request, the second SFC controller can quickly determine the service function path between the visited location and the home location, thus improving SFP negotiation efficiency.

[0150] In other embodiments, the SFC indirect access request also includes access information of the first SFC controller. By carrying the access information of the first SFC controller in the SFC indirect access request, it facilitates communication between the second SFC controller and the first SFC controller.

[0151] Step 413: The second SFC controller sends the updated SFP traffic guidance information to the second SMF entity.

[0152] In some embodiments, after receiving an SFC indirect access request, the second SFC controller obtains the service function path access information corresponding to the first region from the SFC indirect access request. Based on the service function path access information corresponding to the first region and the pre-set service function path of the second region, it determines the service function path between the visited location and the home location. Then, it generates the second traffic routing information of the service function path between the visited location and the home location, that is, the traffic routing information of the SFP from the second region to the first region, that is, the updated SFP traffic routing information, and then sends the updated SFP traffic routing information to the second SMF entity.

[0153] In other embodiments, the SFC indirect access request does not carry the service function path access information corresponding to the first region. In these embodiments, the second SFC controller obtains the service function path access information corresponding to the first region by actively querying the first SFC controller.

[0154] Step 414: The second SFC controller returns an SFC indirect access response to the first SFC controller.

[0155] For example, the SFC indirect access response includes service function path access information corresponding to the second region.

[0156] In this embodiment, the execution order of steps 413 and 414 is not limited. For example, step 413 can be executed first, followed by step 414; or step 414 can be executed first, followed by step 413; or both can be executed simultaneously. Without affecting the implementation of this embodiment, those skilled in the art can also adjust the execution order of other steps.

[0157] Step 415: The first SFC controller returns an SFC access response to the first SMF entity.

[0158] The SFC access response includes traffic routing information for SFPs between the visited and home locations, specifically traffic routing information for SFPs from the first area to the second area. For example, when the first area is the visited location, the SFC access response includes traffic routing information for SFPs from the visited location to the home location.

[0159] Step 416: The first SMF entity sends a session modification request to the first UPF entity.

[0160] For example, the session modification request includes first traffic routing information for the service function path between the visited location and the home location, namely, traffic routing information for the SFP from the first area to the second area, and traffic classification information of the user equipment in the SFC rule of the first area. Optionally, the session modification request may also include base station tunnel information, home location tunnel information, visited location tunnel information, etc.

[0161] Step 417: The first UPF entity returns a session modification response to the first SMF entity.

[0162] The first UPF entity modifies the user plane session based on the traffic guidance information of the SFPs from the first area to the second area carried in the session modification request, and the traffic classification information of the user equipment in the SFC rules of the first area. For example, in a 5G network, the first UPF entity modifies the N9 interface session based on the information carried in the session modification request. When the user equipment sends uplink traffic, the first UPF entity classifies the data packets corresponding to the session according to the traffic classification information in the SFC rules, and encapsulates different data packets based on the traffic guidance information. For example, it adds NSH to the original data packets and performs transport layer and network layer encapsulation, and then forwards the encapsulated data packets to one or more SFPs.

[0163] Step 418: The second SMF entity sends a session modification request to the second UPF entity.

[0164] After step 413, the second SMF entity sends a session modification request to the second UPF entity, wherein the session modification request carries updated SFP traffic guidance information. At this time, downlink traffic and downlink buffered traffic from the user equipment in the second area can enter the first area. For example, when the first area is the visited area and the second area is the home area, downlink traffic from the user equipment in the home area can enter the visited area network and then be sent to the base station and user equipment.

[0165] Step 419: The second UPF entity returns a session modification response to the second SMF entity.

[0166] In this embodiment, the above steps enable flexible and efficient configuration of service function routing for user plane traffic at the session granularity in roaming scenarios. This allows user plane traffic to flexibly select automatically orchestrated service function chains when flowing out from the roaming visited or home network. This facilitates the linkage between the visited and home networks when deploying services such as traffic acceleration, making the deployment, activation, and maintenance of related services more flexible and automated. Furthermore, because services can be provided on demand according to user customization needs, investment in high-end service hardware and software can be reduced to some extent. Therefore, the method of this embodiment has good prospects for domestic cross-provincial relocation and international application in 5G or 6G network scenarios.

[0167] Figure 5This is a schematic diagram of a user plane traffic routing configuration device according to some embodiments of the present disclosure. The user plane traffic routing configuration device of the present disclosure is applied to a first area in a roaming scenario, including a first SMF entity 510, a first SFC controller 520, and a first UPF entity 530 corresponding to the first area.

[0168] The first SMF entity 510 is configured to obtain the SFC rules of the user device in the roaming scenario from the second SMF entity.

[0169] The first SMF entity 510 is also configured to send an SFC access request to the first SFC controller 520, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario.

[0170] The first SFC controller 520 is configured to, upon receiving the SFC access request, negotiate the service function path between the visited location and the home location with the second SFC controller, and send an SFC access response to the first SMF entity.

[0171] The SFC access response includes traffic routing information for the service function path between the visited location and the home location.

[0172] The first SMF entity 510 is further configured to send the traffic steering information to the first UPF entity 530, so that the first UPF entity 530 forwards the data packets corresponding to the user equipment session according to the traffic steering information. The second SMF entity and the second SFC controller correspond to the second region.

[0173] In this embodiment, the above-described apparatus enables flexible and efficient configuration of service function routes for user plane traffic at the session granularity in roaming scenarios. This allows user plane traffic to flexibly select automatically orchestrated service function chains when flowing out of the first roaming area, thereby achieving linkage between the visited and home networks when deploying services such as traffic acceleration. This makes the deployment, activation, and maintenance of related services more flexible and automated. Furthermore, because it can provide services on demand according to users' customized needs, it can reduce investment in high-end service hardware and software to a certain extent. Therefore, the method of this embodiment has good prospects for domestic cross-provincial relocation and international application in 5G or 6G network scenarios.

[0174] Figure 6 This is a schematic diagram of a user plane traffic routing configuration device according to other embodiments of the present disclosure. The user plane traffic routing configuration device of the present disclosure is applied to a second area in a roaming scenario, including a second SMF entity 610, a second SFC controller 620, and a second UPF entity 630 corresponding to the second area.

[0175] The second SMF entity 610 is configured to obtain the SFC rules of the user equipment in the roaming scenario and send the SFC rules of the user equipment in the roaming scenario to the first SMF entity.

[0176] The second SFC controller 620 is configured to, in response to an SFC indirect access request from the first SFC controller, negotiate a service function path between the visited location and the home location with the first SFC controller, and send traffic routing information for the service function path between the visited location and the home location to the second SMF entity 610.

[0177] The second SMF entity 610 is also configured to send the traffic guidance information to the second UPF entity 630, so that the second UPF entity 630 forwards the data packets corresponding to the session of the user equipment according to the traffic guidance information, wherein the first SMF entity and the first SFC controller correspond to the first area in the roaming scenario.

[0178] In this embodiment, the above-described apparatus enables flexible and efficient configuration of service function routes for user plane traffic at the session granularity in roaming scenarios. This allows user plane traffic to flexibly select automatically orchestrated service function chains when flowing out of the second roaming area, thereby achieving linkage between the visited and home networks when deploying services such as traffic acceleration. This makes the deployment, activation, and maintenance of related services more flexible and automated. Furthermore, since it can provide services on demand according to users' customized needs, it can reduce investment in high-end service hardware and software to a certain extent. Therefore, the method of this embodiment has good prospects for domestic cross-provincial relocation and international application in 5G or 6G network scenarios.

[0179] Figure 7 This is a schematic diagram of the structure of a user plane traffic routing configuration system according to some embodiments of this disclosure. The embodiments of this disclosure are illustrated using a 5G mobile network as an example. Figure 7 As shown, the system includes: a first session management function entity 710, a first service function chain controller 720, and a first user plane function entity 730 corresponding to the visited 5G network; and a second session management function entity 740, a policy and charging function entity 750, a second service function chain controller 760, and a second user plane function entity 770 corresponding to the home 5G network.

[0180] The second session management function entity 740 is configured to obtain the SFC rules of the user equipment in the roaming scenario and send the SFC rules of the user equipment in the roaming scenario to the first session management function entity 710.

[0181] In some embodiments, after receiving a Protocol Data Unit (PDU) session establishment request sent by the first session management function entity 710, the second session management function entity 740 obtains the SFC rules of the user equipment in the roaming scenario from the policy and charging function entity 750, and then sends the SFC rules of the user equipment in the roaming scenario in the PDU session establishment response to the first session management function entity 710. Optionally, the PDU session establishment response also includes access information of the second service function chain controller 760 and interface tunnel information on the first area side, such as N9 interface tunnel information on the visited area side in a 5G network.

[0182] The first session management function entity 710 is configured to send an SFC access request to the first service function chain controller 720. The SFC access request includes the SFC rules for the user equipment in a roaming scenario.

[0183] In some embodiments, the SFC access request includes the SFC rules of the user equipment at the visited location and the access information of the second service function chain controller. Optionally, the SFC access request may also include the location of the user equipment and information such as the DNN.

[0184] The first service function chain controller 720 is configured to, upon receiving the SFC access request, negotiate the service function path between the visited location and the home location with the second service function chain controller 760, and send an SFC access response to the first session management function entity 710. The SFC access response includes first traffic routing information, i.e., traffic routing information from the visited location to the home location's SFP.

[0185] The first session management function entity 710 is further configured to send the first traffic guidance information to the first user plane function entity 730, so that the first user plane function entity 730 forwards the data packets corresponding to the user equipment session according to the first traffic guidance information.

[0186] In some embodiments, the first session management function entity 710 is further configured to send traffic classification information of the user equipment in the SFC rules of the visited location to the first user plane function entity 730, wherein the traffic classification information is used to instruct the first user plane function entity 730 to classify the data packets corresponding to the session of the user equipment.

[0187] The second service function chain controller 760 is configured to send second traffic routing information to the second session management function entity 740. In this embodiment of the disclosure, the second traffic routing information is traffic routing information from the home location to the visited location SFP.

[0188] The second session management function entity 740 is further configured to send the second traffic guidance information to the second user plane function entity 770, so that the second user plane function entity 770 forwards and processes the data packets corresponding to the session of the user equipment according to the second traffic guidance information.

[0189] In some embodiments, the second session management function entity 740 is further configured to send the traffic classification information in the SFC rule of the user equipment in the home location to the second user plane function entity 770, where the traffic classification information is used to instruct the second user plane function entity 770 to classify the data packets corresponding to the session of the user equipment.

[0190] In the embodiments of the present disclosure, through the above system, for the roaming scenario, the service function routing can be flexibly and efficiently configured for the user plane traffic at the session granularity, so that when the user plane traffic flows out from the roaming visited location or the home location, the automatically orchestrated service function chain can be flexibly selected, thereby achieving the linkage between the visited location and the home location networks when deploying service functions such as traffic acceleration, making the deployment, opening, operation and maintenance of related services more flexible and automated. At the same time, since the services can be provided on demand according to the customized requirements of the users, the investment in the construction of high-end service software and hardware settings can be reduced to a certain extent, making the embodiments of the present disclosure have good prospects for domestic cross-provincial return to the home location and international applications. It should be noted that the embodiments of the present disclosure are described by taking the 5G network as an example, but this does not mean that the system of the present disclosure can only be used in the 5G network. In addition to the 5G network, the system of the present disclosure can also be applied to application scenarios such as the 6G network.

[0191] Figure 8 FIG. shows a block diagram of a user plane traffic routing configuration device according to some other embodiments of the present disclosure.

[0192] As Figure 8 shown, the user plane traffic routing configuration device 800 includes a memory 8,10; and a processor 8,20 coupled to the memory 8,10. The memory 8,10 is used to store instructions corresponding to the embodiments of the user plane traffic routing configuration method. The processor 8,20 is configured to execute the user plane traffic routing configuration method in any of the embodiments of the present disclosure based on the instructions stored in the memory 8,10.

[0193] Figure 9 FIG. shows a block diagram of a computer system for implementing some embodiments of the present disclosure.

[0194] As Figure 9 shown, the computer system 900 may be presented in the form of a general-purpose computing device. The computer system 900 includes a memory 9,10, a processor 9,20, and a bus 9,30 connecting different system components.

[0195] The memory 910 may include, for example, system memory, non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs. The system memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. The non-volatile storage media may store, for example, instructions for executing at least one of the user plane traffic routing configuration methods in corresponding embodiments. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, etc.

[0196] The processor 920 can be implemented using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete hardware components such as discrete gates or transistors. Accordingly, each module, such as the decision module and the determination module, can be implemented by executing instructions in the central processing unit (CPU) memory to perform the corresponding steps, or by implementing dedicated circuitry to perform the corresponding steps.

[0197] Bus 930 can use any of a variety of bus architectures. For example, bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, and Peripheral Component Interconnect (PCI) bus.

[0198] The computer system 900 may also include an input / output interface 940, a network interface 950, and a storage interface 960. These interfaces 940, 950, and 960, as well as the memory 910 and processor 920, can be connected via a bus 930. The input / output interface 940 provides a connection interface for input / output devices such as a monitor, mouse, and keyboard. The network interface 950 provides a connection interface for various networked devices. The storage interface 960 provides a connection interface for external storage devices such as floppy disks, USB flash drives, and SD cards.

[0199] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.

[0200] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.

[0201] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.

[0202] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0203] The user plane traffic routing configuration method and apparatus in the above embodiments can flexibly and efficiently configure service function routes for user plane traffic at the session granularity, so that user plane traffic can flexibly select automatically orchestrated service function chains when flowing out from the mobile network side, and meet various customized needs under the trend of network convergence.

[0204] This concludes the detailed description of the user plane traffic routing configuration method and apparatus according to this disclosure. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art can fully understand how to implement the technical solutions disclosed herein based on the above description.

Claims

1. A user plane traffic routing configuration method, applied to a first area in a roaming scenario, the first area corresponding to a first session management function (SMF) entity, a first service function chain (SFC) controller, and a first user plane function (UPF) entity, the method comprising: The first SMF entity obtains the SFC rules for the user device in the roaming scenario from the second SMF entity; The first SMF entity sends an SFC access request to the first SFC controller, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario; After receiving the SFC access request, the first SFC controller negotiates the service function path between the visited location and the home location with the second SFC controller, and sends an SFC access response to the first SMF entity. The SFC access response includes traffic routing information for the service function path between the visited location and the home location. The first SMF entity sends the traffic guidance information to the first UPF entity, so that the first UPF entity forwards the data packets corresponding to the session of the user equipment according to the traffic guidance information. The second SMF entity and the second SFC controller correspond to the second area in the roaming scenario.

2. The user plane traffic routing configuration method according to claim 1, wherein, The SFC rules for the user equipment in the roaming scenario include the SFC rules for the user equipment in the first area, and the negotiation of the service function path between the visited location and the home location with the second SFC controller includes: The first SFC controller sets the service function path corresponding to the first area according to the SFC rules of the user equipment in the first area; The first SFC controller obtains the service function path access information corresponding to the second area from the second SFC controller; The first SFC controller determines the service function path between the visited location and the home location based on the service function path corresponding to the first region and the service function path access information corresponding to the second region.

3. The user plane traffic routing configuration method according to claim 2, wherein, The first SFC controller obtains the service function path access information corresponding to the second region from the second SFC controller, including: The first SFC controller obtains the access information of the second SFC controller from the SFC access request; The first SFC controller sends an SFC access request to the second SFC controller based on the access information of the second SFC controller. The first SFC controller receives the SFC indirect access response returned by the second SFC controller, wherein the SFC indirect access response includes service function path access information corresponding to the second region.

4. The user plane traffic routing configuration method according to claim 3, wherein, The SFC access request includes at least one of the following: access information of the first SFC controller and service function path access information corresponding to the first area.

5. The user plane traffic routing configuration method according to claim 1, wherein, The first SMF entity obtains the SFC rules for the user device in roaming scenarios from the second SMF entity, including: The first SMF entity sends a Protocol Data Unit (PDU) session establishment request to the second SMF entity; The first SMF entity receives a PDU session establishment response sent by the second SMF entity, wherein the PDU session establishment response includes the SFC rules of the user equipment in the roaming scenario.

6. The user plane traffic routing configuration method according to claim 5, wherein, The PDU session establishment request carries a first capability identifier, which is used to indicate that the first region supports the SFC function.

7. The user plane traffic routing configuration method according to claim 6, wherein, The PDU session establishment response also includes access information for the second SFC controller.

8. The user plane traffic routing configuration method according to claim 2 further includes: The first SMF entity sends the traffic classification information of the user equipment in the SFC rules of the first area to the first UPF entity, wherein the traffic classification information is used to instruct the first UPF entity to classify the data packets corresponding to the user equipment's session.

9. The user plane traffic routing configuration method according to claim 1, wherein, The first area is the place of visit, and the second area is the place of origin.

10. A user plane traffic routing configuration method, applied to a second area in a roaming scenario, the second area corresponding to a second session management function (SMF) entity, a second service function chain (SFC) controller, and a second user plane function (UPF) entity, the method comprising: The second SMF entity obtains the SFC rules of the user equipment in the roaming scenario and sends the SFC rules of the user equipment in the roaming scenario to the first SMF entity; In response to the SFC indirect access request of the first SFC controller, the second SFC controller negotiates the service function path between the visited location and the home location with the first SFC controller, and sends the traffic routing information of the service function path between the visited location and the home location to the second SMF entity. The second SMF entity sends the traffic guidance information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the session of the user equipment according to the traffic guidance information. The first SMF entity and the first SFC controller correspond to the first area in the roaming scenario.

11. The user plane traffic routing configuration method according to claim 10, wherein, The service function path negotiated between the second SFC controller and the first SFC controller between the visited location and the home location includes: The second SFC controller obtains the service function path access information corresponding to the first region from the SFC access request. The second SFC controller determines the service function path between the visited location and the home location based on the service function path corresponding to the second region and the service function path access information corresponding to the first region. The service function path corresponding to the second region is determined according to the SFC rules of the user equipment in the second region.

12. The user plane traffic routing configuration method according to claim 11, wherein, The negotiation of the service function path between the visited location and the home location between the second SFC controller and the first SFC controller also includes: The second SFC controller sends an SFC indirect access response to the first SFC controller, wherein the SFC indirect access response includes service function path access information corresponding to the second region.

13. The user plane traffic routing configuration method according to claim 12, wherein, The second SFC controller sends an SFC indirect access response to the first SFC controller based on the access information of the first SFC controller carried in the SFC indirect access request.

14. The user plane traffic routing configuration method according to claim 10, wherein, The second SMF entity obtains the Service Function Chain (SFC) rules for user equipment in roaming scenarios, including: The second SMF entity sends a new session management policy query request to the Policy and Charging Function (PCF) entity, wherein the PCF entity corresponds to the second region; The second SMF entity receives the new session management policy query response returned by the PCF entity, wherein the new session management policy query response includes the SFC rules of the user equipment in the roaming scenario.

15. The user plane traffic routing configuration method according to claim 14, further comprising: Before the second SMF entity obtains the SFC rules of the user equipment in the roaming scenario, the second SMF entity receives a Protocol Data Unit (PDU) session establishment request sent by the first SMF entity. The PDU session establishment request carries a first capability identifier, which is used to indicate that the first area supports the SFC function.

16. The user plane traffic routing configuration method according to claim 15, wherein, Sending the SFC rules of the user equipment in the roaming scenario to the first SMF entity includes: the second SMF entity sending a PDU session establishment response to the first SMF entity, wherein the PDU session establishment response includes the service function chain SFC rules of the user equipment in the roaming scenario.

17. The user plane traffic routing configuration method according to claim 16, wherein, The PDU session establishment response also includes access information for the second SFC controller.

18. The user plane traffic routing configuration method according to claim 11, further comprising: The second SMF entity sends the traffic classification information of the user equipment in the SFC rules of the second area to the second UPF entity, wherein the traffic classification information is used to instruct the second UPF entity to classify the data packets corresponding to the user equipment's session.

19. The user plane traffic routing configuration method according to claim 10, wherein, The first area is the place of visit, and the second area is the place of origin.

20. A user plane traffic routing configuration method, applied in a roaming scenario, wherein a first region corresponds to a first session management function (SMF) entity, a first service function chain (SFC) controller, and a first user plane function (UPF) entity, and a second region corresponds to a second SMF entity, a second SFC controller, and a second UPF entity, the method comprising: The second SMF entity obtains the SFC rules of the user equipment in the roaming scenario and sends the SFC rules of the user equipment in the roaming scenario to the first SMF entity; The first SMF entity sends an SFC access request to the first SFC controller, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario; After receiving the SFC access request, the first SFC controller negotiates the service function path between the visited location and the home location with the second SFC controller, and sends an SFC access response to the first SMF entity. The SFC access response includes first traffic routing information for the service function path between the visited location and the home location. The first SMF entity sends the first traffic guidance information to the first User Plane Function (UPF) entity, so that the first UPF entity forwards the data packets corresponding to the session of the user equipment according to the first traffic guidance information. The second SFC controller sends the second traffic routing information of the service function path between the visited location and the home location to the second SMF entity; The second SMF entity sends the second traffic guidance information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the user equipment session according to the second traffic guidance information.

21. A user plane traffic routing configuration device, applied to a first area in a roaming scenario, comprising a first session management function (SMF) entity, a first service function chain (SFC) controller, and a first user plane function (UPF) entity corresponding to the first area; The first SMF entity is configured to obtain the SFC rules of the user device in the roaming scenario from the second SMF entity; The first SMF entity is also configured to send an SFC access request to the first SFC controller, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario; The first SFC controller is configured to, upon receiving the SFC access request, negotiate the service function path between the visited location and the home location with the second SFC controller, and send an SFC access response to the first SMF entity, wherein the SFC access response includes traffic routing information for the service function path between the visited location and the home location. The first SMF entity is configured to send the traffic guidance information to the first UPF entity so that the first UPF entity forwards the data packets corresponding to the session of the user equipment according to the traffic guidance information, wherein the second SMF entity and the second SFC controller correspond to the second area in the roaming scenario.

22. A user plane traffic routing configuration device, applied to a second area in a roaming scenario, comprising a second session management function (SMF) entity, a second service function chain (SFC) controller, and a second user plane function (UPF) entity corresponding to the second area; The second SMF entity is configured to obtain the SFC rules of the user equipment in the roaming scenario and send the SFC rules of the user equipment in the roaming scenario to the first SMF entity; The second SFC controller is configured to, in response to an SFC indirect access request from the first SFC controller, negotiate a service function path between the visited location and the home location with the first SFC controller, and send traffic routing information for the service function path between the visited location and the home location to the second SMF entity. The second SMF entity is also configured to send the traffic guidance information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the session of the user equipment according to the traffic guidance information, wherein the first SMF entity and the first SFC controller correspond to the first area in the roaming scenario.

23. A user plane traffic routing configuration system, applied in roaming scenarios, comprising: The first region corresponds to the first Session Management Function (SMF) entity, the first Service Function Chain (SFC) controller, and the first User Plane Function (UPF) entity; the second region corresponds to the second SMF entity, the second SFC controller, and the second UPF entity. The second SMF entity is configured to obtain the SFC rules of the user equipment in the roaming scenario and send the SFC rules of the user equipment in the roaming scenario to the first SMF entity; The first SMF entity is configured to send an SFC access request to the first SFC controller, wherein the SFC access request includes the SFC rules of the user equipment in the roaming scenario; The first SFC controller is configured to, upon receiving the SFC access request, negotiate the service function path between the visited location and the home location with the second SFC controller, and send an SFC access response to the first SMF entity, wherein the SFC access response includes first traffic routing information for the service function path between the visited location and the home location. The first SMF entity is also configured to send the first traffic guidance information to the first UPF entity, so that the first UPF entity forwards the data packets corresponding to the session of the user equipment according to the first traffic guidance information; The second SFC controller is configured to send second traffic routing information for the service function path between the visited location and the home location to the second SMF entity; The second SMF entity is also configured to send the second traffic guidance information to the second UPF entity, so that the second UPF entity forwards the data packets corresponding to the session of the user equipment according to the second traffic guidance information.

24. A user plane traffic routing configuration device, applied in roaming scenarios, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the user plane traffic routing configuration method as described in any one of claims 1 to 20 based on instructions stored in the memory.

25. A computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the user plane traffic routing configuration method according to any one of claims 1 to 20.

Images