Data offloading methods, devices, equipment and storage media

Abstract

This application provides a data offloading method, apparatus, device, and storage medium that receives session data sent by a User Equipment (UE) through a Home Routing Protocol Data Unit (HR PDU) session, including roaming session data; and offloads the roaming session data to a target Edge Application Server (EAS) according to acquired data offloading rules. This solution requires only one HR PDU to offload roaming session data to the target EAS, enabling the use of MEC services in the roaming location. This solution simplifies inter-network traffic transmission and reduces operational complexity.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data splitting method, apparatus, device and storage medium. Background Technology

[0002] Mobile edge computing (MEC) technology migrates computing and storage capabilities and business service capabilities to the network edge, minimizing the need to transmit data back to the cloud. This reduces the waiting time and network costs associated with data traveling to and from the cloud, and it is now widely used.

[0003] MEC technology is based on 5G's distributed cloud infrastructure. It builds 5G User Plane Function (UPF) nodes and 5G MEC nodes in the edge cloud. The 5G MEC nodes provide an MEC application platform, thereby enabling the deployment and management of third-party applications, allowing users to obtain corresponding services through the MEC application platform.

[0004] In related technologies, 5G roaming networking includes Local Breakout (LBO, also known as "roaming location routing") and Home-Routed (HR). When a user needs to use MEC services in the roaming location and other services in the home location, it is necessary to establish roaming location routing protocol data unit (LBO PDU) sessions and HR PDU sessions respectively, which is a relatively complex process. Summary of the Invention

[0005] This application provides a data offloading method, apparatus, device, and storage medium to simplify the process of using MEC services in roaming locations.

[0006] Firstly, this application provides a data offloading method applied to the User Plane Functional Element (UPF) network element. The data offloading method includes:

[0007] Receive session data sent by the user equipment (UE) through the Home Routing Protocol Data Unit (HR PDU) session, including roaming session data;

[0008] According to the acquired data routing rules, the roaming session data is routed to the target edge application server (EAS).

[0009] Optional data offloading methods also include:

[0010] Based on the URR contained in the data diversion rules, determine the billing information for roaming session data. The billing information includes any one or more of the following: billing identifier, HR PDU session information, user permanent identifier SUPI, and the data volume of roaming session data.

[0011] The billing information is sent to the billing function CHF network element so that the CHF network element can bill the roaming session data according to the billing information.

[0012] Optionally, billing information may be sent to CHF network elements, including:

[0013] The billing information is sent to the SMF network element so that the SMF network element can forward it to the CHF network element.

[0014] Optionally, roaming session data may be routed to the target EAS according to the acquired data routing rules, including:

[0015] Based on the destination address and / or application identifier carried in the roaming session data, and the traffic routing rules contained in the data splitting rules, determine the target EAS corresponding to the destination address and / or application identifier;

[0016] Roaming session data will be diverted to the target EAS.

[0017] Optionally, before routing roaming session data to the target EAS according to the acquired data routing rules, the following steps are also included:

[0018] Based on the traffic detection rules included in the data routing rules, determine whether the roaming session data is data sent to EAS.

[0019] Optionally, roaming session data can be offloaded to the Edge Application Server (EAS), including:

[0020] If the UPF network element is the home UPF network element, the roaming session data will be sent to the roaming UPF network element, which will then distribute the roaming session data to the target EAS.

[0021] Optionally, data splitting rules can be obtained in the following ways:

[0022] Data splitting rules are obtained from the Session Management Function (SMF) network element, wherein the data splitting rules include any one or more of the following rules:

[0023] Use reporting rules, traffic routing rules, and traffic detection rules.

[0024] Secondly, this application provides a data offloading method applied to the Session Management Function (SMF) network element. The data offloading method includes:

[0025] Based on the roaming location traffic splitting policy and / or relevant information from EAS, determine the UPF network elements and data splitting rules;

[0026] Send data offloading rules to the UPF network element so that the UPF network element can offload the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data offloading rules.

[0027] Optionally, the roaming location diversion strategy includes at least one of the following: the UPF network element selection method and the EAS address range and the service types provided by the EAS.

[0028] Optionally, based on the roaming location offloading policy and / or relevant EAS information, the UPF network elements are determined, including:

[0029] The UPF network element is determined based on the UPF network element selection method in the roaming location offloading strategy, the data network access identifier (DNAI), and / or relevant information of the UE.

[0030] Optionally, before determining the UPF network elements and data offloading rules based on the roaming offloading policy and / or EAS-related information, the following may also be included:

[0031] Receive a session establishment request sent by the UE;

[0032] Establish an HR PDU session with the UE based on the session establishment request.

[0033] Thirdly, this application provides a data offloading device applied to a User Plane Functional Entity (UPF) network element. The data offloading device includes:

[0034] The receiving module is used to receive session data sent by the user equipment (UE) through the Home Routing Protocol Data Unit (HR PDU) session, including roaming session data.

[0035] The routing module is used to route roaming session data to the target edge application server (EAS) according to the acquired data routing rules.

[0036] Optionally, the data offloading device further includes: a determination module, used to determine the billing information of roaming session data according to the URR contained in the data offloading rules, wherein the billing information includes any one or more of the following: billing identifier, HR PDU session information, user permanent identifier SUPI and the data volume of roaming session data;

[0037] The sending module is used to send billing information to the billing function CHF network element so that the CHF network element can bill roaming session data according to the billing information.

[0038] Optionally, the sending module is specifically used to send billing information to the SMF network element so that the SMF network element can forward it to the CHF network element.

[0039] Optionally, according to the acquired data routing rules, the routing module is specifically used to: determine the target EAS corresponding to the destination address and / or application identifier based on the destination address and / or application identifier carried in the roaming session data and the traffic routing rules contained in the data routing rules;

[0040] Roaming session data will be diverted to the target EAS.

[0041] Optionally, the determination module is also used to determine whether roaming session data is data sent to EAS based on the traffic detection rules contained in the data diversion rules.

[0042] Optionally, the diversion module is specifically used to send roaming session data to the roaming UPF network element if the UPF network element is the home UPF network element, and then the roaming UPF network element diverts the roaming session data to the target EAS.

[0043] Optionally, the receiving module is also used to obtain data splitting rules in the following ways:

[0044] Data splitting rules are obtained from the Session Management Function (SMF) network element, wherein the data splitting rules include any one or more of the following rules:

[0045] Use reporting rules, traffic routing rules, and traffic detection rules.

[0046] Fourthly, this application provides a data splitting device applied to a Session Management Function (SMF) network element. The data splitting device includes:

[0047] The determination module is used to determine the UPF network elements and data offloading rules based on the roaming offloading policy and / or relevant information of EAS;

[0048] The sending module is used to send data offloading rules to the UPF network element so that the UPF network element can offload the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data offloading rules.

[0049] Optionally, the roaming location diversion strategy includes at least one of the following: the UPF network element selection method and the EAS address range and the service types provided by the EAS.

[0050] Optionally, a determination module is used to determine the UPF network element based on the UPF network element selection method in the roaming location offloading strategy, the data network access identifier (DNAI), and / or relevant information of the UE.

[0051] Optionally, the data splitting device further includes: a receiving module for receiving session establishment requests sent by the UE;

[0052] Establish an HR PDU session with the UE based on the session establishment request.

[0053] Fifthly, this application also provides a UPF network element, including: a memory for storing computer programs;

[0054] A transceiver is used to send and receive data under the control of a processor.

[0055] A processor is used to read computer programs from memory and perform the following operations:

[0056] Receive session data sent by the user equipment (UE) through the Home Routing Protocol Data Unit (HR PDU) session, including roaming session data;

[0057] According to the acquired data routing rules, the roaming session data is routed to the target edge application server (EAS).

[0058] Optionally, the processor is also used to perform the following operations:

[0059] Based on the URR contained in the data diversion rules, determine the billing information for roaming session data. The billing information includes any one or more of the following: billing identifier, HR PDU session information, user permanent identifier SUPI, and the data volume of roaming session data.

[0060] The billing information is sent to the billing function CHF network element so that the CHF network element can bill the roaming session data according to the billing information.

[0061] Optionally, billing information may be sent to CHF network elements, including:

[0062] The billing information is sent to the SMF network element so that the SMF network element can forward it to the CHF network element.

[0063] Optionally, roaming session data may be routed to the target EAS according to the acquired data routing rules, including:

[0064] Based on the destination address and / or application identifier carried in the roaming session data, and the traffic routing rules contained in the data splitting rules, determine the target EAS corresponding to the destination address and / or application identifier;

[0065] Roaming session data will be diverted to the target EAS.

[0066] Optionally, the processor is also used to perform the following operations:

[0067] Based on the traffic detection rules included in the data routing rules, determine whether the roaming session data is data sent to EAS.

[0068] Optionally, roaming session data can be offloaded to the Edge Application Server (EAS), including:

[0069] If the UPF network element is the home UPF network element, the roaming session data will be sent to the roaming UPF network element, which will then distribute the roaming session data to the target EAS.

[0070] Optionally, the processor obtains the data splitting rules in the following ways:

[0071] Data splitting rules are obtained from the Session Management Function (SMF) network element, wherein the data splitting rules include any one or more of the following rules:

[0072] Use reporting rules, traffic routing rules, and traffic detection rules.

[0073] Sixthly, this application provides an SMF network element, including:

[0074] Memory, used to store computer programs;

[0075] A transceiver is used to send and receive data under the control of a processor.

[0076] A processor is used to read computer programs from memory and perform the following operations:

[0077] Based on the roaming location traffic splitting policy and / or relevant information from EAS, determine the UPF network elements and data splitting rules;

[0078] Send data offloading rules to the UPF network element so that the UPF network element can offload the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data offloading rules.

[0079] Optionally, the roaming location diversion strategy includes at least one of the following: the UPF network element selection method and the EAS address range and the service types provided by the EAS.

[0080] Optionally, based on the roaming location offloading policy and / or relevant EAS information, the UPF network elements are determined, including:

[0081] The UPF network element is determined based on the UPF network element selection method in the roaming location offloading strategy, the data network access identifier (DNAI), and / or relevant information of the UE.

[0082] Optionally, the processor is also used to perform the following operations:

[0083] Receive a session establishment request sent by the UE;

[0084] Establish an HR PDU session with the UE based on the session establishment request.

[0085] In a seventh aspect, embodiments of this application provide a processor-readable storage medium storing a computer program for causing a processor to perform a data offloading method as described in the first and / or second aspects.

[0086] Eighth aspect, computer program products, including: computer programs that, when executed by a processor, implement data diversion methods as described in the first and / or second aspects.

[0087] Ninthly, this application also provides a communication system, including: the UPF network element as described in the fifth aspect and the SMF network element as described in the sixth aspect.

[0088] In a tenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program for causing a computer to perform a data offloading method as described in the first and / or second aspects.

[0089] This application provides a data offloading method, apparatus, device, and storage medium that receives session data sent by a User Equipment (UE) through a Home Routing Protocol Data Unit (HR PDU) session, including roaming session data; and offloads the roaming session data to a target Edge Application Server (EAS) according to acquired data offloading rules. This solution requires only one HR PDU to offload roaming session data to the target EAS, enabling the use of MEC services in the roaming location. This solution simplifies inter-network traffic transmission and reduces operational complexity.

[0090] It should be understood that the content described in the foregoing summary section is not intended to limit the key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

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

[0092] Figure 1 A schematic diagram of an edge computing network architecture for roaming routing;

[0093] Figure 2 A schematic diagram of an edge computing network architecture for home routing;

[0094] Figure 3 A schematic diagram of the network architecture for the data offloading process in existing technologies;

[0095] Figure 4 Signaling interaction diagram of a data offloading method provided in this application embodiment Figure 1 ;

[0096] Figure 5 A network architecture diagram of a data offloading process provided in this application embodiment. Figure 1 ;

[0097] Figure 6 A network architecture diagram of a data offloading process provided in this application embodiment. Figure 2 ;

[0098] Figure 7 Signaling interaction diagram of a data offloading method provided in this application embodiment Figure 2 ;

[0099] Figure 8 Signaling interaction diagram of a data offloading method provided in this application embodiment Figure 3 ;

[0100] Figure 9 A signaling interaction diagram illustrating a roaming offloading strategy configuration method provided in an embodiment of this application;

[0101] Figure 10 A schematic diagram of the structure of a data splitting device provided in this application embodiment. Figure 1 ;

[0102] Figure 11 A schematic diagram of the structure of a data splitting device provided in this application embodiment. Figure 2 ;

[0103] Figure 12 A schematic diagram of the structure of a UPF network element provided in an embodiment of this application;

[0104] Figure 13 This is a schematic diagram of the structure of an SMF network element provided in an embodiment of this application. Detailed Implementation

[0105] In this application, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

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

[0107] Mobile edge computing (MEC) technology migrates computing and storage capabilities and business service capabilities to the network edge, minimizing the need to transmit data back to the cloud. This reduces the waiting time and network costs associated with data traveling to and from the cloud, and it is now widely used.

[0108] MEC technology is based on 5G's distributed cloud infrastructure. It builds 5G user plane function nodes and 5GMEC nodes at the edge cloud and provides an MEC application platform through 5G MEC nodes, thereby enabling the deployment and management of third-party applications and allowing users to obtain corresponding services through the MEC application platform.

[0109] 5G defines an Application Function (AF) that sends an AFRequest to either the Untrusted Domain (NEF) or the Trusted Domain (PCF), containing a series of parameters such as the target DNN, application ID, N6 routing requirements, and application location. Based on these parameters provided by the AF and its own policy control, the PCF generates PCC rules for the target PDU Session service flow and selects a suitable UPF for it through the SMF.

[0110] MEC provides functions such as application infrastructure resource orchestration, application instantiation, and application rule configuration. Therefore, when MEC is deployed in a 5G system, MEC can also act as an Application Function, representing the applications deployed on MEC to interact with the 5G system control plane.

[0111] 5G international roaming network deployment can be divided into roaming location routing / local breakout scheme and home-routed scheme.

[0112] For example, Figure 1 and Figure 2 The diagrams above illustrate edge computing network architectures for roaming routing and home routing, respectively. The main network functions involved in these architectures are described below:

[0113] AMF (Access and Mobility Management Function): Primarily responsible for access and mobility management functions, such as registration and connection management.

[0114] UPF (User Plane Function): Primarily responsible for the routing and forwarding of messages from external PDU (Protocol Data Unit) session nodes that interconnect with the data network.

[0115] SMF (Session Management Function): Primarily responsible for session establishment and deletion, user plane selection and control, UE IP allocation, etc.

[0116] Application Function (AF): Used to interact with the 3GPP core network to provide services. Depending on the operator's deployment, trusted AFs can interact directly with relevant network functions (NFs), while untrusted AFs cannot interact directly with NFs and should use the publicly available framework through the Network Function (NEF).

[0117] DNAI (Data Network Access Identifier);

[0118] PCF (Policy Control Function) supports a unified policy framework to manage network behavior and provides policy rules for the control plane (NF) to enforce.

[0119] NEF (Network Exposure Function);

[0120] NRF (Network Repository Function) supports service discovery functionality;

[0121] UDM (Unified Data Management) is used to store UE information, such as subscription information and information about established PDU sessions;

[0122] NEF (Network Exposure Function) is a function that provides secure exposure of services and capabilities provided by 3GPP networks to external networks.

[0123] UDR (Unified Data Repository) is used to store subscription data and for UDMFE to retrieve subscription data, or to store policy information and for PCF to retrieve policy information.

[0124] EASDF (Edge Application Server Discovery Function) is used to process DNS messages based on SMF instructions;

[0125] UDR (Unified Data Repository);

[0126] EAS (Edge Application Server) is used to provide edge services;

[0127] PSA (PDU session anchor).

[0128] To support selective data routing to the DN, the SMF can control the data path of the PDU session to ensure that the PDU session can correspond to multiple N6 interfaces simultaneously. Each anchor point supporting the PDU session provides different access paths to the same DN, realizing local traffic splitting. This can be achieved through the UL CL (Uplink Classifier) ​​function and the IPv6 multi-homing function BP (Branching Point). This architecture is called the session breakout connection model.

[0129] In related technologies, 5G roaming users cannot access Edge Computing Service (EAS) via HR PDU sessions in the roaming area. Figure 3 This is a schematic diagram of the network architecture for data offloading processes in existing technologies. For example... Figure 3 As shown, when a roaming user establishes an HR PDU session to use services in the HPLMN, if they need to use the MEC services in the roaming area, they also need to create a new LBO PDU session to access the local MEC services, so that they can use local and home services through two PDU sessions. This process is relatively complicated.

[0130] Furthermore, when the UE is located outside the SMF service area or the SMF cannot support DNAI for traffic routing to the local network, an I-SMF can be inserted between the SMF and AMF. In non-roaming and local offloading (LBO) scenarios, it supports inserting a UL CL / BP UPF into the non-roaming / LBO PDU session established during VPLMN establishment to offload traffic to the local network. The SMF sends local offloading information to the I-SMF to instruct the UPF controlled by the I-SMF on how to perform traffic monitoring and execution. The I-SMF determines PDR, URR, and other rules based on the information provided by the SMF.

[0131] However, in I-SMF insertion scenarios, only UL CL / BPUPF insertion is supported in non-roaming and LBO PDU sessions. When establishing an HR PDU session, UL CL / BP UPF cannot be inserted for local traffic offloading. Furthermore, the traffic usage information reporting and billing method used is the same as that of non-roaming / LBO PDU sessions; V-UPF UL CL / BP cannot send traffic usage and billing information between the UE and EAS to the H-SMF via V-SMF. Similarly, when roaming MEC services and other home services are required, two separate PDU sessions—one for local offloading and one for home routing—must be established.

[0132] In summary, existing methods increase the difficulty of deployment for operators and the complexity of UEs using edge services while roaming. Furthermore, when accessing local services through LBO PDU sessions, the home location cannot control the services; for example, the home location cannot bill users.

[0133] In view of this, embodiments of this application provide a data offloading method, apparatus and storage medium. Based on the edge computing services required in the session, the UPF network element and data offloading rules are determined. Then, the roaming session data sent by the UE through the HR PDU session is offloaded to the target EAS through the UPF network element in accordance with the data offloading rules, so as to enable 5G roaming users to access the edge computing service EAS through the HR PDU session in the roaming area.

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

[0135] Furthermore, the User Equipment (UE) mentioned in this application may have different names in different systems. For example, the aforementioned terminal may also be called a wireless terminal. The wireless terminal can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). The wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) or a computer with a mobile terminal. For example, it can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that exchanges voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless terminal can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0136] Next, with reference to specific embodiments and the accompanying drawings, the various embodiments of this application will be described in detail. It should be noted that the order in which the embodiments of this application are presented only represents the chronological order of the embodiments and does not represent the superiority or inferiority of the technical solutions provided by the embodiments.

[0137] In practical applications, there are various ways to select UPF network elements. This application does not limit the specific methods. For example, on the one hand, a roaming UPF network element can be selected when visiting a public terrestrial mobile network (VPLMN). The roaming UPF network element includes a PSA UPF network element and a UL CL UPF network element. Alternatively, the roaming UPF network element includes a PSA UPF network element and a BP UPF network element. Then, the roaming data can be offloaded by using at least one of the PSA UPF network element and the UL CL UPF network element or the BP UPF network element.

[0138] On the other hand, a roaming location UPF element (V-UPF) can be selected in the VPLMN, wherein the roaming location UPF element includes a PSA UPF element, and roaming data can be offloaded through the roaming location UPF element and / or the UPF element (H-UPF) in the home public land mobile network HPLMN.

[0139] Figure 4 Signaling interaction diagram of a data offloading method provided in this application embodiment Figure 1 .like Figure 4 As shown, this data offloading method includes the following steps:

[0140] S101. The roaming SMF network element determines the roaming UPF network element and data splitting rules based on the roaming splitting strategy and / or relevant information of EAS.

[0141] In practical applications, when a UE roams to a VPLMN, it will establish a PDU session through the roaming SMF network element (i.e., V-SMF) deployed in the VPLMN (the PDU session can be established in the same way as the HR PDU session). Correspondingly, during the session establishment process, the roaming SMF network element will select EASDF based on preset rules and perform EAS-related information discovery operations to obtain the EAS-related information sent by EASDF for providing edge computing services.

[0142] It should be noted that this embodiment does not limit the method for discovering EAS-related information. For example, it can be queried through C-DNS or L-DNS. The relevant information of EAS may include the IP address of EAS, the types of edge services that EAS can provide, etc.

[0143] Furthermore, based on the EAS information sent by EASDF and the roaming location diversion policy, the required UPF network element and data diversion rules are determined.

[0144] The roaming location diversion strategy includes at least one of the following: the selection method of UPF network elements and the address range of EAS, and the service types provided by EAS.

[0145] In some embodiments, when determining the UPF network element to be selected based on the EAS-related information sent by EASDF and the roaming area traffic offloading policy, the specific steps are as follows:

[0146] If the address range of the EAS provided in the roaming location traffic splitting policy is within the address range of the EAS sent by EASDF, and / or, the service type of the EAS provided in the roaming location traffic splitting policy is within the service type range of the EAS sent by EASDF, then the corresponding UPF network element shall be selected according to the UPF network element selection method provided in the roaming location traffic splitting policy.

[0147] The UPF network element selection method provided in the roaming location traffic splitting strategy includes at least one of the following:

[0148] (1) Select the roaming location UPF network element in VPLMN, wherein the roaming location UPF network element includes at least one of UL CL UPF network element or BP UPF network element and PSA UPF network element, and then realize the roaming data splitting through at least one of UL CL UPF network element or BP UPF network element and PSA UPF network element;

[0149] (2) Select the roaming location UPF network element (V-UPF) in the VPLMN, wherein the roaming location network element includes the PSA UPF network element, and then distribute the roaming session data to the target EAS through the roaming location UPF network element and / or the home location UPF network element (H-UPF) in the HPLMN.

[0150] Specifically, UPF network elements can be selected in VPLMN based on the Data Network Access Identifier (DNAI) and / or relevant information of the UE (e.g., UE location information). The Data Network Access Identifier (DNAI) is determined based on relevant information of the EAS.

[0151] Optionally, if the selected UPF network element in the VPLMN does not meet the DNAI requirements, the UPF network element can be reselected in the VPLMN based on the DNAI and / or UE information.

[0152] On the one hand, when selecting at least one of the UL CL UPF or BP UPF network elements and a PSA UPF network element in the VPLMN, and implementing roaming data offloading through at least one of the UL CL UPF or BP UPF network elements and a PSA UPF network element, the network architecture of the data offloading process is described in [link to relevant documentation]. Figure 5 .

[0153] In this network architecture, please refer to the scheme for data offloading by the UPF network element. Figure 4 Steps S102-S104 are shown below:

[0154] S102, The roaming SMF network element sends data diversion rules to the UPF network element.

[0155] S103, the roaming UPF network element receives session data sent by the user equipment (UE) through the HR PDU session.

[0156] The session data includes types of data such as roaming session data and local session data.

[0157] S104. The roaming UPF network element distributes the roaming session data to the target EAS according to the acquired data distribution rules.

[0158] It should be noted that, in Figure 5 In the network architecture shown, the scheme for the roaming UPF network element to offload session data between the UE and the edge target EAS through the PSA UPF network element can refer to existing technologies, and will not be elaborated here.

[0159] On the other hand, when a UPF network element (V-UPF) is selected in the VPLMN, and data is offloaded between the roaming UPF network element and the UPF network element (H-UPF) in the HPLMN, the network architecture of the data offloading process is described in [link to relevant documentation]. Figure 6 .

[0160] exist Figure 6 In the network architecture shown, data offloading rules also need to be configured for the home UPF network elements. Next, combined with... Figure 7 The above plan will be explained in detail:

[0161] Figure 7 Signaling interaction diagram of a data offloading method provided in this application embodiment Figure 2 ,like Figure 7 As shown, the data splitting method in this embodiment includes the following steps:

[0162] S112. The roaming SMF network element sends data diversion rules to the roaming UPF network element.

[0163] S113. The roaming SMF network element sends data diversion rules to the home SMF network element.

[0164] Specifically, roaming SMF network elements can send a data offloading rule configuration instruction to H-SMF by calling Nsmf_PDUSession_Update Request. This data offloading rule configuration instruction carries the data offloading rules.

[0165] S114. The home SMF network element sends data diversion rules to the home UPF network element.

[0166] S115. The UE sends session data to the home UPF network element and / or the roaming network element through the HR PDU session.

[0167] The session data includes roaming session data.

[0168] S116. The home UPF network element and / or the roaming UPF network element shall, in accordance with the obtained data diversion rules, divert the roaming session data to the target EAS.

[0169] It should be noted that the specific scheme for roaming session data offloading will be shown in subsequent embodiments and will not be repeated here.

[0170] This application provides a data offloading method that receives session data sent by a User Equipment (UE) through a Home Routing Protocol Data Unit (HRPDU) session, including roaming session data; and offloads the roaming session data to a target Edge Application Server (EAS) according to the acquired data offloading rules. This solution requires only one HRPDU to offload roaming session data to the target EAS, enabling the use of MEC services in the roaming location. This solution simplifies the inter-network traffic transmission process and reduces operational complexity.

[0171] In some embodiments, the AF network element in the HPLMN can configure the roaming location offloading policy to the PCF network element by requesting configuration during the data offloading process, so that the PCF network element can configure the roaming location offloading policy to the SMF network element; or the AF network element can pre-configure the PCF network element or the SMF network element before the data offloading.

[0172] It should be noted that the configuration scheme of the roaming location traffic splitting strategy will be shown in subsequent embodiments and will not be repeated here.

[0173] In some embodiments, the data splitting rule includes any one or more of the following rules: Usage Reporting Rule (URR), traffic routing rule, and traffic detection rule. Next, combining... Figure 8 The specific scheme for the above data splitting rules is explained in detail:

[0174] Figure 8 Signaling interaction diagram of a data offloading method provided in this application embodiment Figure 3 .like Figure 8 As shown, the roaming UPF network element and / or the home UPF network element will offload the roaming session data to the target EAS according to the following steps S301-S304 (the UPF network element mentioned below refers to the roaming UPF network element or the home UPF network element):

[0175] S301, the UE sends session data through the HR PDU session.

[0176] S302 and UPF network elements determine whether roaming session data is data sent to EAS based on the traffic detection rules included in the data diversion rules.

[0177] In this step, the roaming session data carries the destination address of the target EAS. Based on the traffic detection rules, which contain address information of multiple target EAS and the destination address of the target EAS, it is determined whether the roaming session data is data sent to the EAS.

[0178] Specifically, the roaming session data can be detected as data sent to EAS based on the IP Packet Filter Set (e.g., the target IP address or IPv6 prefix) or the Application Identifier.

[0179] Correspondingly, if so, the roaming session data will be diverted to the target EAS according to the scheme in steps S303-S304; otherwise, the roaming session data will not be diverted.

[0180] S303 and UPF network elements determine the target EAS corresponding to the destination address and / or application identifier based on the destination address and / or application identifier carried in the roaming session data and the traffic routing rules contained in the data diversion rules.

[0181] S304. Distribute roaming session data to the target EAS.

[0182] On the one hand, when the UPF network element is a roaming UPF network element, the application with the destination address as the EAS IP address and / or for a specific application identifier is directed to the target EAS. For example, the application with Routing info = EAS IP Address / port number / IP prefix@local PSA and application identifier = 01 / meta data = position is directed to the target EAS.

[0183] For UL CL UPF, the target EAS can be determined by matching information such as destination IP address and destination port number. For BP UPF, the target EAS can be determined by matching IP prefix@local PSA.

[0184] On the other hand, for the uplink roaming session data sent by the UE, the roaming UPF network element sends the data to the home UPF network element through a preset tunnel to offload the roaming session data to the target EAS.

[0185] The preset tunnel can be determined based on the tunnel mapping relationship between the roaming UPF network element and the home UPF.

[0186] For downlink roaming session data received from the home UPF network element, the home UPF network element sends the downlink roaming session data to the target EAS corresponding to the destination address based on the destination address of the downlink roaming session data.

[0187] In some embodiments, roaming session data can also be billed according to traffic splitting rules. The specific billing scheme includes the following steps S305-S307:

[0188] S305 and UPF network elements determine the billing information for roaming session data based on the URR (Usage Reporting Rule) included in the data diversion rules.

[0189] The billing information includes any one or more of the following: billing identifier (e.g., charging ID), HRPDU session information (PDU session information), user permanent identifier SUPI, and the data volume of roaming session data (e.g., Uplink / Downlink Volume).

[0190] S306, UPF network element sends billing information to billing function CHF network element.

[0191] Optionally, in step S306 above, the billing information can be directly sent from the UPF network element to the CHF network element, or it can be forwarded by the SMF network element. Specifically, when forwarded by the SMF network element, S306 includes the following steps:

[0192] (1) The UPF network element sends the billing information to the SMF network element;

[0193] (2) The SMF network element sends the billing information to the CHF network element.

[0194] S307 and CHF network elements charge for roaming session data based on billing information.

[0195] It should be noted that the billing method for CHF network elements can refer to existing technologies, and will not be elaborated here.

[0196] Next, combined Figure 9 The specific configuration process of the roaming location diversion strategy is explained in detail.

[0197] Figure 9 This is a signaling interaction diagram of a roaming offloading strategy configuration method provided in an embodiment of this application.

[0198] like Figure 9As shown, the HPLMN is equipped with home SMF network elements (H-SMF), home PCF network elements (H-PCF), home UDR network elements (H-UDR), home NEF network elements (H-NEF), and home AF network elements (H-AF); the VPLMN is equipped with roaming SMF network elements (V-SMF) and roaming PCF network elements (V-PCF).

[0199] Specifically, the roaming location traffic splitting strategy configuration method provided in this embodiment includes the following steps:

[0200] S401. The home AF network element sends a roaming location traffic splitting policy configuration request to the home NEF network element.

[0201] Specifically, the home AF network element sends a roaming traffic offloading policy configuration request to the home NEF network element by calling the Nnef_TrafficInfluence_Create / Update service operation. The roaming traffic offloading policy includes: the selection method of the UPF network element, relevant information of EAS, etc.

[0202] The relevant information of EAS may include: the service range that EAS can provide (e.g., the FQDN requested by the UE and the application identifier), the address range of EAS, etc.

[0203] The UPF network element selection method provided in the roaming location traffic splitting strategy includes at least one of the following:

[0204] (1) Select the roaming location UPF network element in VPLMN, wherein the roaming location UPF network element includes at least one of UL CL UPF network element or BP UPF network element and PSA UPF network element, and then realize the roaming data distribution through at least one of UL CL UPF network element or BP UPF network element and PSA UPF network element.

[0205] (2) Select the roaming location UPF network element (V-UPF) in the VPLMN, wherein the roaming location UPF network element includes the PSA UPF network element, and then distribute the roaming session data to the target EAS through the roaming location UPF network element and / or the home location UPF network element (H-UPF) in the HPLMN.

[0206] S402. The home NEF network element stores the configuration request in the home UDR network element, and the configuration request carries the roaming location traffic offloading policy.

[0207] Specifically, the home NEF network element stores configuration requests to the home UDR network element. The home PCF network element subscribes to the home UDR network element for changes in configuration requests sent by the AF network element in order to obtain information about the configuration requests sent by the AF network element from the notification information, thereby obtaining the roaming location traffic distribution strategy.

[0208] Optionally, the AF network element can directly send the roaming location diversion policy to the home PCF network element.

[0209] S403. The home PCF network element obtains the configuration request from the home UDR network element and obtains the roaming location traffic distribution policy according to the configuration request.

[0210] Specifically, the home UDR network element notifies the home PCF network element of the roaming location offloading policy contained in the configuration request sent by the AF by calling Nudr_DM_Notify notification.

[0211] It should be noted that the roaming location traffic offloading policy can be sent from the home PCF network element to the roaming PCF network element (see step S404 below), or it can be forwarded by the home SMF network element (see steps S405-S406 below).

[0212] S404. The home PCF network element sends the roaming location traffic diversion policy to the roaming PCF network element.

[0213] S405, the home PCF network element sends the roaming location diversion policy to the home SMF.

[0214] S406. The home SMF network element sends the roaming location traffic diversion policy to the roaming PCF network element.

[0215] S407. The roaming PCF network element sends the roaming traffic splitting policy to the roaming SMF network element.

[0216] On the UPF network element side, this application embodiment provides a data splitting device. Figure 10 A schematic diagram of the structure of a data splitting device provided in this application embodiment. Figure 1 .like Figure 10 As shown, the data splitting device 500 includes:

[0217] The receiving module 501 is used to receive session data sent by the user equipment (UE) through the Home Routing Protocol Data Unit (HR PDU) session, including roaming session data.

[0218] The routing module 502 is used to route roaming session data to the target edge application server (EAS) according to the acquired data routing rules.

[0219] Optionally, the data splitting device 500 may further include: a determining module 503 and a sending module 504;

[0220] The determination module 503 is used to determine the billing information of roaming session data based on the URR contained in the data diversion rules. The billing information includes any one or more of the following: billing identifier, HR PDU session information, user permanent identifier SUPI and the data volume of roaming session data.

[0221] The sending module 504 is used to send billing information to the billing function CHF network element so that the CHF network element can bill the roaming session data according to the billing information.

[0222] Optionally, the sending module 504 is specifically used to send the billing information to the SMF network element so that the SMF network element can forward it to the CHF network element.

[0223] Optionally, according to the acquired data routing rules, the routing module is specifically used to: determine the target EAS corresponding to the destination address and / or application identifier based on the destination address and / or application identifier carried in the roaming session data and the traffic routing rules contained in the data routing rules;

[0224] Roaming session data will be diverted to the target EAS.

[0225] Optionally, the determination module 503 is also used to determine whether the roaming session data is data sent to EAS based on the traffic detection rules contained in the data diversion rules.

[0226] Optionally, the diversion module 502 is specifically used to send roaming session data to the roaming UPF network element if the UPF network element is the home UPF network element, and the roaming UPF network element will then divert the roaming session data to the target EAS.

[0227] Optionally, the receiving module 501 is also used to obtain data splitting rules in the following ways:

[0228] Data splitting rules are obtained from the Session Management Function (SMF) network element, wherein the data splitting rules include any one or more of the following rules:

[0229] Use reporting rules, traffic routing rules, and traffic detection rules.

[0230] It should be noted that the data diversion device provided in this application can implement all the steps of the data diversion method implemented by the UPF network element in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0231] On the SMF network element side, this application embodiment provides a data splitting device. Figure 11 A schematic diagram of the structure of a data splitting device provided in this application embodiment. Figure 2 .like Figure 11 As shown, the data splitting device 600 includes:

[0232] The determination module 601 is used to determine the UPF network element and data offloading rules based on the roaming offloading policy and / or relevant information of EAS;

[0233] The sending module 602 is used to send data diversion rules to the UPF network element so that the UPF network element can divert the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data diversion rules.

[0234] Optionally, the roaming location diversion strategy includes at least one of the following: the UPF network element selection method and the EAS address range and the service types provided by the EAS.

[0235] Optionally, the determining module 601 is specifically used to determine the UPF network element based on the UPF network element selection method, the data network access identifier (DNAI), and / or relevant information of the UE in the roaming location traffic offloading strategy.

[0236] Optionally, the data splitting device 600 further includes: a receiving module 603, used to receive a session establishment request sent by the UE;

[0237] Establish an HR PDU session with the UE based on the session establishment request.

[0238] It should be noted that the data diversion device provided in this application can implement all the steps of the data diversion method implemented by the SMF network element in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0239] Figure 12 This is a schematic diagram of the structure of a UPF network element provided in an embodiment of this application. Figure 12 As shown, the UPF network element includes: transceiver 701, processor 702 and memory 703.

[0240] Memory 703 is used to store computer programs;

[0241] Transceiver 701 is used to send and receive data under the control of processor 702;

[0242] Among them, Figure 12In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 702) and memory (memory 703). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 701 can be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. The processor 702 is responsible for managing the bus architecture and general processing, and the memory 703 can store data used by the processor 702 during operation.

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

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

[0245] The processor 702 executes any terminal access method for the target relay terminal provided in this application embodiment by calling a computer program stored in the memory 703, according to the obtained executable instructions. The processor 702 and the memory 703 may also be physically separated.

[0246] Specifically, processor 702 is used to read the computer program in memory 703 and perform the following operations:

[0247] Receive session data sent by the user equipment (UE) through the Home Routing Protocol Data Unit (HR PDU) session, including roaming session data;

[0248] According to the acquired data routing rules, the roaming session data is routed to the target edge application server (EAS).

[0249] Optionally, the processor 702 is also used to perform the following operations:

[0250] Based on the URR contained in the data diversion rules, determine the billing information for roaming session data. The billing information includes any one or more of the following: billing identifier, HR PDU session information, user permanent identifier SUPI, and the data volume of roaming session data.

[0251] The billing information is sent to the billing function CHF network element so that the CHF network element can bill the roaming session data according to the billing information.

[0252] Optionally, billing information may be sent to CHF network elements, including:

[0253] The billing information is sent to the SMF network element so that the SMF network element can forward it to the CHF network element.

[0254] Optionally, roaming session data may be routed to the target EAS according to the acquired data routing rules, including:

[0255] Based on the destination address and / or application identifier carried in the roaming session data, and the traffic routing rules contained in the data splitting rules, determine the target EAS corresponding to the destination address and / or application identifier;

[0256] Roaming session data will be diverted to the target EAS.

[0257] Optionally, the processor 702 is also used to perform the following operations:

[0258] Based on the traffic detection rules included in the data routing rules, determine whether the roaming session data is data sent to EAS.

[0259] Optionally, roaming session data can be offloaded to the Edge Application Server (EAS), including:

[0260] If the UPF network element is the home UPF network element, the roaming session data will be sent to the roaming UPF network element, which will then distribute the roaming session data to the target EAS.

[0261] Optionally, the processor 702 obtains the data routing rules in the following ways:

[0262] Data splitting rules are obtained from the Session Management Function (SMF) network element, wherein the data splitting rules include any one or more of the following rules:

[0263] Use reporting rules, traffic routing rules, and traffic detection rules.

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

[0265] Figure 13 This is a schematic diagram of the structure of an SMF network element provided in an embodiment of this application. Figure 13 As shown, the SMF network element includes: transceiver 801, processor 802, and memory 803.

[0266] Memory 803 is used to store computer programs;

[0267] Transceiver 801 is used to send and receive data under the control of processor 802;

[0268] Among them, Figure 13 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 802) and memory (memory 803). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 801 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 802 is responsible for managing the bus architecture and general processing, and the memory 803 can store data used by the processor 802 during operation.

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

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

[0271] The processor 802 executes any terminal access method for the target relay terminal provided in this application embodiment by calling a computer program stored in the memory 803, according to the obtained executable instructions. The processor 802 and the memory 803 may also be physically separated.

[0272] Specifically, processor 802 is used to read the computer program in memory 803 and perform the following operations:

[0273] Based on the roaming location traffic splitting policy and / or relevant information from EAS, determine the UPF network elements and data splitting rules;

[0274] Send data offloading rules to the UPF network element so that the UPF network element can offload the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data offloading rules.

[0275] Optionally, the roaming location diversion strategy includes at least one of the following: the UPF network element selection method and the EAS address range and the service types provided by the EAS.

[0276] Optionally, based on the roaming location offloading policy and / or relevant EAS information, the UPF network elements are determined, including:

[0277] The UPF network element is determined based on the UPF network element selection method in the roaming location offloading strategy, the data network access identifier (DNAI), and / or relevant information of the UE.

[0278] Optionally, the processor 802 is also used to perform the following operations:

[0279] Receive a session establishment request sent by the UE;

[0280] Establish an HR PDU session with the UE based on the session establishment request.

[0281] It should be noted that the SMF network element provided in this application can implement all the method steps implemented by the SMF network element in the above method embodiment and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail here.

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

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

[0284] On the UPF network element side, this application embodiment provides a processor-readable storage medium storing a computer program. The computer program enables the processor to implement the steps of all data offloading methods implemented in the UPF network element in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0285] On the SMF network element side, this application embodiment provides a processor-readable storage medium storing a computer program. The computer program enables the processor to implement all the steps of the data offloading method implemented on the SMF network element side in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0286] The processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs)), optical storage (e.g., CDs, DVDs, BDs, HVDs), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0287] On the UPF network element side, one embodiment of this application also provides a computer program product containing instructions. The computer program is stored in a storage medium. At least one processor can read the computer program from the storage medium. When the at least one processor executes the computer program, it can implement all the steps of the data diversion method implemented by the UPF network element in the above method embodiment and achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0288] On the SMF network element side, one embodiment of this application also provides a computer program product containing instructions. The computer program is stored in a storage medium. At least one processor can read the computer program from the storage medium. When the at least one processor executes the computer program, it can implement all the steps of the data diversion method implemented by the SMF network element in the above method embodiment and achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0289] This application also provides a communication system including a UPF network element and an SMF network element. The UPF network element can execute all the steps of the data splitting methods executed on the UPF network element side in the above method embodiments, and can achieve the same technical effect. The SMF network element can execute all the steps of the data splitting methods executed on the SMF network element side in the above method embodiments, and can achieve the same technical effect. The parts that are the same as those in the method embodiments and their beneficial effects will not be described in detail here.

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

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

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

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

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

Claims

1. A data splitting method, characterized in that, The data offloading method, applied to the User Plane Functional Element (UPF) network element, includes: Receive session data sent by user equipment (UE) through Home Routing Protocol Data Unit (HR PDU) session, the session data including roaming session data; According to the acquired data routing rules, the roaming session data is routed to the target edge application server (EAS); wherein the data routing rules include any one or more of the following rules: The system uses reporting rules, traffic routing rules, and traffic detection rules; the reporting rules are used to determine the billing information of the roaming session data; the traffic detection rules are used to determine whether the roaming session data is data sent to the Edge Application Server (EAS); and the traffic routing rules are used to determine the target EAS corresponding to the roaming session data.

2. The data splitting method according to claim 1, characterized in that, The data splitting method further includes: Based on the URR (Usage Reporting Rule) included in the data diversion rules, the billing information of the roaming session data is determined. The billing information includes any one or more of the following: billing identifier, HR PDU session information, user permanent identifier SUPI, and the data volume of the roaming session data. The billing information is sent to the billing function CHF network element so that the CHF network element can bill the roaming session data according to the billing information.

3. The data splitting method according to claim 2, characterized in that, Sending billing information to the CHF network element includes: The billing information is sent to the SMF network element so that the SMF network element forwards it to the CHF network element.

4. The data splitting method according to claim 1, characterized in that, The step of diverting the roaming session data to the target EAS according to the acquired data diversion rules includes: Based on the destination address and / or application identifier carried in the roaming session data, and the traffic routing rules contained in the data splitting rules, determine the target EAS corresponding to the destination address and / or application identifier; The roaming session data is diverted to the target EAS.

5. The data splitting method according to claim 1, characterized in that, Before routing the roaming session data to the target EAS according to the acquired data routing rules, the process also includes: Based on the traffic detection rules included in the data splitting rules, determine whether the roaming session data is data sent to EAS.

6. The data splitting method according to any one of claims 1-5, characterized in that, The step of offloading the roaming session data to the Edge Application Server (EAS) includes: If the UPF network element is the home UPF network element, the roaming session data is sent to the roaming UPF network element, which then distributes the roaming session data to the target EAS.

7. The data splitting method according to any one of claims 1-5, characterized in that, Obtain data splitting rules through the following methods: The data routing rules are obtained from the SMF network element of the session management function.

8. A data splitting method, characterized in that, The data offloading method, applied to the SMF network element for session management functions, includes: Based on the roaming location traffic splitting policy and / or EAS-related information, determine the UPF network elements and data splitting rules; wherein, the data splitting rules include any one or more of the following rules: The system uses reporting rules, traffic routing rules, and traffic detection rules. The reporting rules are used to determine the billing information for roaming session data. The traffic detection rules are used to determine whether the roaming session data is data sent to the Edge Application Server (EAS). The traffic routing rules are used to determine the target EAS corresponding to the roaming session data. The data offloading rule is sent to the UPF network element so that the UPF network element offloads the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data offloading rule.

9. The data splitting method according to claim 8, characterized in that, The roaming location diversion strategy includes at least one of the following: UPF network element selection method and EAS address range and EAS service type.

10. The data splitting method according to claim 9, characterized in that, Based on the roaming location offloading policy and / or EAS-related information, determine the UPF network elements, including: The UPF network element is determined based on the UPF network element selection method in the roaming location offloading strategy, the data network access identifier (DNAI), and / or the relevant information of the UE.

11. The data splitting method according to any one of claims 8-10, characterized in that, Before determining the UPF network elements and data offloading rules based on the roaming location offloading policy and / or EAS information, the following steps are also included: Receive the session establishment request sent by the UE; Based on the session establishment request, establish an HR PDU session with the UE.

12. A data splitting device, characterized in that, The data offloading device, applied to the User Plane Functional Element (UPF) network element, includes: The receiving module is used to receive session data sent by the user equipment (UE) through the Home Routing Protocol Data Unit (HR PDU) session, wherein the session data includes roaming session data; The data routing module is used to route the roaming session data to the target edge application server (EAS) according to the acquired data routing rules; wherein the data routing rules include any one or more of the following rules: The system uses reporting rules, traffic routing rules, and traffic detection rules; the reporting rules are used to determine the billing information of the roaming session data; the traffic detection rules are used to determine whether the roaming session data is data sent to the Edge Application Server (EAS); and the traffic routing rules are used to determine the target EAS corresponding to the roaming session data.

13. A data splitting device, characterized in that, The data offloading device, applied to the SMF network element for session management functions, includes: The determination module is used to determine the UPF network element and data offloading rules based on the roaming offloading policy and / or relevant information of EAS; wherein the data offloading rules include any one or more of the following rules: The system uses reporting rules, traffic routing rules, and traffic detection rules. The reporting rules are used to determine the billing information for roaming session data. The traffic detection rules are used to determine whether the roaming session data is data sent to the Edge Application Server (EAS). The traffic routing rules are used to determine the target EAS corresponding to the roaming session data. The sending module is used to send the data diversion rule to the UPF network element so that the UPF network element can divert the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data diversion rule.

14. A UPF network element, characterized in that, include: Memory, used to store computer programs; A transceiver is used to send and receive data under the control of a processor. Processor, configured to read the computer program in the memory and perform the following operations: Receive session data sent by user equipment (UE) through Home Routing Protocol Data Unit (HR PDU) session, the session data including roaming session data; According to the acquired data routing rules, the roaming session data is routed to the target edge application server (EAS); wherein the data routing rules include any one or more of the following rules: The system uses reporting rules, traffic routing rules, and traffic detection rules; the reporting rules are used to determine the billing information of the roaming session data; the traffic detection rules are used to determine whether the roaming session data is data sent to the Edge Application Server (EAS); and the traffic routing rules are used to determine the target EAS corresponding to the roaming session data.

15. An SMF network element, characterized in that, include: Memory, used to store computer programs; A transceiver is used to send and receive data under the control of a processor. Processor, configured to read the computer program in the memory and perform the following operations: Based on the roaming location traffic splitting policy and / or EAS-related information, determine the UPF network elements and data splitting rules; wherein, the data splitting rules include any one or more of the following rules: The system uses reporting rules, traffic routing rules, and traffic detection rules. The reporting rules are used to determine the billing information for roaming session data. The traffic detection rules are used to determine whether the roaming session data is data sent to the Edge Application Server (EAS). The traffic routing rules are used to determine the target EAS corresponding to the roaming session data. The data offloading rule is sent to the UPF network element so that the UPF network element offloads the roaming session data sent by the UE through the HR PDU session to the target EAS according to the data offloading rule.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for causing a computer to perform the data splitting method according to any one of claims 1 to 11.

Images