WO2018205756A1 - 一种数据包的分流方法、装置和计算机存储介质 - Google Patents

一种数据包的分流方法、装置和计算机存储介质 Download PDF

Info

Publication number
WO2018205756A1
WO2018205756A1 PCT/CN2018/080091 CN2018080091W WO2018205756A1 WO 2018205756 A1 WO2018205756 A1 WO 2018205756A1 CN 2018080091 W CN2018080091 W CN 2018080091W WO 2018205756 A1 WO2018205756 A1 WO 2018205756A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
local
policy
address
offloading
Prior art date
Application number
PCT/CN2018/080091
Other languages
English (en)
French (fr)
Inventor
王丹
蔡慧
孙滔
Original Assignee
***通信有限公司研究院
***通信集团有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ***通信有限公司研究院, ***通信集团有限公司 filed Critical ***通信有限公司研究院
Publication of WO2018205756A1 publication Critical patent/WO2018205756A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data packet shunting method, apparatus, and computer storage medium.
  • the technical solutions of local offloading based on 5G network architecture mainly include:
  • FIG. 1 is a schematic diagram of a process of establishing a protocol data unit (PDU) session provided by the prior art.
  • the UE triggers, and establishes a slave terminal (UE, User Entity) to a local user.
  • UP (User Plane) function The local PDU session of the device. Specifically, the UE establishes a connection with an access network (AN, Access Network) device, and the AN establishes a connection with two UP function devices, where an UP function device establishes a connection with a data network device. Another UP function device establishes a connection with a local data network device. At this time, the PDU session between the UE and the two UP function devices is established.
  • AN Access Network
  • the UE performs data interaction with the local UP function device through a PDU session established by the local UP function device, where the local UP function device is an UP function device that establishes a connection with the Local Data Network, and the two UP function devices and the AN device can communicate with the core network.
  • CN Core Network
  • Control Plane devices perform data interaction to support local offloading.
  • FIG. 2 is a schematic diagram of packet splitting implemented by the uplink classifier (UL-CL, UPFLink Classifier) provided by the prior art.
  • the User Plane Function (UPF) device supports UL.
  • the -CL function performs data offload by querying the destination address of the data packet, and offloads the data packet that satisfies the condition to the local network.
  • the terminal only needs to support one network protocol (IP, Internet Protocol) address.
  • IP Internet Protocol
  • the UPF device receives the data packet sent by the UE through the AN, and offloads the data packet according to the destination IP address in the data packet and the local UL-CL function.
  • FIG. 3 are schematic diagrams of the multi-homing branching point method provided by the prior art to implement packet splitting.
  • the UPF supports the Multi-homing branching point function by querying the data packet.
  • the source IP address (the IP address of the UE) is used to implement data offloading, and the data packet that satisfies the condition is offloaded to the local network, and the terminal needs to support multiple IP addresses.
  • the UPF device receives the data packet sent by the UE through the AN, and offloads the data packet according to the source IP address and the local UL-CL function in the data packet.
  • the source IP address in the data packet satisfies the first condition, Send the data packet to the PDU session anchor 1 (Anchor1) of the UPF device. If the source IP address in the data packet satisfies the second condition, the data packet is sent to the PDU session anchor point 2 (Anchor2) of the UPF device, and the UPF device will The corresponding data packet is sent to the DN.
  • data interaction can be completed between different devices as shown in FIG. 2 through the corresponding interface.
  • the second and third mechanisms need to be configured with the corresponding traffic splitting policy for the different destination IP addresses or source IP addresses on the UPF device. If you need to configure the destination IP address or source IP address of the traffic split policy. Too many, the session management (SM, Session Management) function device or the network management system performs complex configuration on the UPF device, resulting in a complicated traffic distribution mechanism. In addition, the existing traffic distribution process requires the UPF device to use the IP address of the data packet. The shunting is performed, and the processing pressure of the UPF device is relatively large, which has a certain influence on the processing speed of the data packet, resulting in the network processing efficiency being too low.
  • SM Session Management
  • the embodiment of the invention provides a method, a device and a computer storage medium for data packet shunting, which are used to solve the problem that the shunting mechanism is complicated and the network processing efficiency is too low in the prior art.
  • an embodiment of the present invention provides a method for distributing a data packet, which is applied to a terminal, and the method includes: determining, according to a data packet to be sent, and a local offloading policy, whether the data packet is a local traffic distribution data. And obtaining a judgment result; when the judgment result is that the data packet is a local offload data packet, carrying the offload identifier in the data packet, and sending the data packet carrying the offload identifier through a user plane data transmission channel Give the UPF device.
  • the local offloading policy is the first offloading policy determined according to the source IP address of the data packet
  • the data packet to be sent, and the local offloading policy determine whether the data packet is local.
  • the offloading data packet includes: determining, according to the source IP address of the data packet, and the first offloading policy, whether the data packet is a local offload data packet, where the source IP address includes an Internet Protocol version 4 IPv4 address or an internet protocol. Version 6 IPv6 prefix address.
  • the local offloading policy is a second offloading policy determined according to the destination IP address of the data packet
  • the data packet to be sent, and the local offloading policy determine whether the data packet is local.
  • the offloading data packet includes: determining, according to the destination IP address of the data packet, and the second offloading policy, whether the data packet is a local offload data packet, where the destination IP address includes an IPv4 address or an IPv6 prefix address.
  • the local offloading policy is a third offloading policy determined according to the type of the terminal, the data packet to be sent, and the local offloading policy, determine whether the data packet is a local offloading data packet.
  • the method includes: determining whether the terminal type of the terminal is a type of the terminal saved in the third offloading policy.
  • the local offloading policy is a fourth offloading policy determined according to the feature information of the application
  • the data packet to be sent, and the local offloading policy determine whether the data packet is a local offloading data.
  • the packet includes: acquiring, according to the application corresponding to the data packet, feature information corresponding to the application; determining whether the feature information is feature information saved in the fourth traffic off policy.
  • the method further includes: receiving a local offloading policy sent by the AMF (Access and Mobility Management Function) device.
  • AMF Access and Mobility Management Function
  • the embodiment of the present invention further provides a method for distributing a data packet, which is applied to a UPF device, and the method includes: identifying whether a data packet sent by the received terminal carries a traffic distribution identifier;
  • the data packet If it is recognized that the data packet carries the offload identifier, the data packet is locally uninstalled.
  • the method further includes: before receiving the data packet sent by the received terminal, the method further includes: receiving, by the SMF device, request information added to the user plane data transmission channel; Information is added to the user plane data transmission channel.
  • the embodiment of the present invention further provides a data packet shunting device, which is applied to a terminal, and the device includes:
  • the determining module is configured to determine, according to the data packet to be sent, and the local offloading policy, whether the data packet is a local offload data packet, and obtain a judgment result; when the judgment result is that the data packet is a local offload data packet, Trigger the sending module;
  • the sending module is configured to carry the offloaded identifier in the data packet, and send the data packet carrying the offloaded identifier to the UPF device through the user plane data transmission channel.
  • the determining module is configured to: when the local offloading policy is the first offloading policy determined according to the source IP address of the data packet, according to the source IP address of the data packet, and the first offloading policy And determining whether the data packet is a local offload data packet, where the source IP address includes an Internet Protocol version 4 IPv4 address or an Internet Protocol version 6 IPv6 prefix address.
  • the determining module is configured to: when the local offload policy is a second offload policy determined according to a destination IP address of the data packet, according to the destination IP address of the data packet, and the second offload policy And determining whether the data packet is a local offload data packet, where the destination IP address includes an IPv4 address or an IPv6 prefix address.
  • the determining module is configured to determine, when the local offloading policy is the third offloading policy determined according to the type of the terminal, whether the terminal type of the terminal is the terminal saved in the third offloading policy. Types of.
  • the determining module is configured to: when the local offloading policy is a fourth offloading policy determined according to the feature information of the application, obtain the feature information corresponding to the application according to the application corresponding to the data packet. Determining whether the feature information is feature information saved in the fourth offloading policy.
  • the apparatus further includes: a receiving module configured to receive a local offloading policy sent by the AMF device.
  • the present invention provides a data packet shunting device, which is applied to a UPF device, and the device includes:
  • the identification module is configured to identify whether the data packet sent by the received terminal carries a traffic distribution identifier; if the data packet is identified to carry the traffic distribution identifier, the traffic distribution module is triggered;
  • the offloading module is configured to locally uninstall the data packet.
  • the apparatus further includes:
  • a receiving module configured to receive request information sent by the SMF device and added to the user plane data transmission channel
  • the module is added to be configured to be added to the user plane data transmission channel according to the request information.
  • the embodiment of the present invention provides a data packet shunting method, a device, and a computer storage medium.
  • the method for distributing the data packet includes: the terminal determining whether the data packet is local for the data packet to be sent and the local traffic distribution policy. Dividing the data packet to obtain a judgment result; when the judgment result is that the data packet is a local offload data packet, carrying the traffic distribution identifier in the data packet, and transmitting the data packet carrying the traffic distribution identifier through user plane data The channel is sent to the UPF device.
  • the terminal determines that the data packet is a local offload data packet
  • the data packet carries the traffic distribution identifier
  • the data packet carrying the traffic distribution identifier is sent to the UPF device, so that the UPF device identifies the received data.
  • the packet carries the traffic distribution identifier
  • the data packet is locally unloaded, and the traffic of the traffic distribution is distributed to each terminal.
  • the UPF device does not need to configure a complex traffic distribution mechanism, but identifies the data packet carrying the local traffic distribution identifier. Local offloading makes the offloading mechanism simpler and further improves network processing efficiency.
  • FIG. 1 is a schematic diagram of a process of establishing a local PDU session provided by the prior art
  • FIG. 2 is a schematic diagram of implementing a packet splitting in a UL-CL manner provided by the prior art
  • FIG. 3 is a schematic diagram of a Multi-homing Branching Point method provided by the prior art for implementing packet splitting
  • FIG. 4 is a schematic diagram of a flow splitting process of a data packet according to Embodiment 1 of the present invention.
  • FIG. 5 is a schematic diagram of a 5G network architecture based on the TS23.501 standard according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic diagram of a flow splitting process of a data packet defined by a PCF device according to Embodiment 3 of the present invention.
  • FIG. 7 is a structural diagram of a traffic distribution system for a data packet that is configured by a UDM device according to Embodiment 3 of the present invention.
  • FIG. 8 is a schematic flowchart of a flow splitting of a data packet according to Embodiment 4 of the present invention.
  • FIG. 9 is a structural diagram of a data packet shunting apparatus according to Embodiment 6 of the present invention.
  • FIG. 10 is a structural diagram of another data packet shunting apparatus according to Embodiment 6 of the present invention.
  • FIG. 11 is a schematic flowchart of a flow splitting of a data packet according to Embodiment 6 of the present invention.
  • the embodiment of the present invention provides a data packet shunting method and device.
  • FIG. 4 is a schematic diagram of a process for distributing a data packet according to an embodiment of the present invention, where the process includes the following steps:
  • Step S401 determining, according to the data packet to be sent, and the local offloading policy, whether the data packet is a local offload data packet, and obtaining a judgment result; when the judgment result is that the data packet is a local offload data packet, performing steps S402. When the result of the determination is that the data packet is a local offload data packet, step S403 is performed.
  • the method for distributing data packets according to the embodiment of the present invention is applied to a terminal, and the terminal may be a terminal capable of transmitting a data packet, such as a PC (personal computer), a notebook computer, a mobile phone, etc., and the terminal pre-stores the data packet. Local distribution strategy.
  • the local offloading policy saved by the terminal may be pre-stored to the local device when the terminal is shipped from the factory, or may be sent by the network side device to the terminal, and the terminal receives and saves.
  • the local offloading policy may be a first offloading policy determined according to a source IP address of the data packet, or a second offloading policy determined according to the destination IP address of the data packet, but it should be noted that only the terminal is saved in the terminal.
  • a local distribution strategy. The terminal can determine whether the data packet is a local offload data packet according to a pre-saved local offload policy, that is, whether local shunting can be implemented.
  • the source IP address may be an Internet Protocol Version 4 (IPv4) address or an Internet Protocol Version 6 (IPv6) prefix address, and the corresponding destination IP address may also be an IPv4 address or IPv6 prefix address.
  • IPv4 Internet Protocol Version 4
  • IPv6 Internet Protocol Version 6
  • the first offload policy determined according to the source IP address saves whether the data packet corresponding to each source IP address is locally offloaded, or in order to reduce the amount of data, only the local save policy can be saved locally.
  • the source IP address corresponding to the offloaded data packet, or the source IP address corresponding to the non-local offloaded data packet; the corresponding second offload policy determined according to the destination IP address stores whether the data packet corresponding to each destination IP address is local In the second offloading policy, only the destination IP address corresponding to the local offloaded data packet or the destination IP address corresponding to the non-local offloaded data packet may be stored in the second offloading policy.
  • S402 Carry the offloaded identifier in the data packet, and send the data packet carrying the offloaded identifier to the UPF device through the user plane data transmission channel.
  • the terminal can identify which data packets are local offloaded data packets, that is, which data packets are locally shunted, and when determining that the data packet is a local offload data packet, add a corresponding offload identifier to the data packet, where the offload identifier is added.
  • the UPF device determines whether to perform local offload processing on the data packet according to whether the data packet carries the traffic distribution identifier.
  • the terminal when the terminal identifies the data packet as a local offload data packet, the terminal carries the traffic distribution identifier, where the traffic distribution identifier may be carried in a preset location of the data packet, for example, a data header or data carried in the data packet.
  • the terminal when the terminal identifies that the data packet is a local offload data packet, it determines that the traffic distribution identifier corresponding to the data packet is 1, and the pre-agreed preset location is a data tail, and carries the traffic distribution identifier 1 at the data tail of the data packet; After receiving the data packet carrying the traffic distribution identifier, the device identifies that the data tail of the data packet carries the traffic distribution identifier 1, and then determines that the data packet needs to be locally distributed.
  • the UPF device that performs local offloading is a local UPF device, that is, a UPF device that has a local offload function and accesses the same evolved base station (eNB) with the terminal.
  • a local UPF device that is, a UPF device that has a local offload function and accesses the same evolved base station (eNB) with the terminal.
  • eNB evolved base station
  • the data exchange between the terminal and the UPF device is performed by using a user plane data transmission channel, where the user plane data transmission channel is a PDU session, and the process of the terminal establishing a PDU session with the UPF device is in the embodiment of the present invention. Do not repeat them.
  • S403 Send the data packet to the UPF device by using a user plane data transmission channel.
  • the terminal determines that the data packet is not a local offload data packet
  • the data packet is directly sent to the UPF device through the user plane transmission channel, and the UPF device determines whether the data packet is performed according to whether the data packet carries the traffic distribution identifier. Local offload processing.
  • the set of the offload identifiers is pre-stored in the UPF device.
  • the UPF device may identify whether the traffic distribution identifier is carried in the preset location of the data packet, and if the traffic distribution identifier is carried, determine whether the traffic distribution identifier is different from the traffic distribution identifier in the collection of the traffic distribution identifier saved by the terminal. Match, if it matches, determine that the packet is a local offloaded packet. If it does not match, determine that the packet is not locally shunted.
  • the UPF device may be a UPF device that supports the UL-CL function, or may be a UPF device that supports the Multi-homing Branching Point function.
  • the terminal determines, according to the data packet to be sent, and the local offloading policy, whether the data packet is a traffic data packet, and when the data packet is a local traffic data packet, carrying the traffic distribution in the data packet. And the data packet that carries the offloaded identifier is sent to the UPF device, so that when the UPF device identifies that the received data packet carries the offloaded identifier, the data packet is locally uninstalled, and the pressure of the splitting is distributed to each terminal.
  • the UPF device does not need to configure a complex traffic distribution mechanism, but locally identifies the data packet carrying the local traffic distribution identifier, which makes the traffic distribution mechanism simpler, reduces the pressure on the UPF device, and further improves the network processing efficiency.
  • the terminal may determine, according to the local offloading policy, whether the data packet to be sent is a local offload data packet, and determine that it is a local offload data packet.
  • the data packet carries the traffic distribution identifier, so that the UPF device directly identifies whether the data packet carries the traffic distribution identifier, so as to determine whether the data packet is locally distributed, and the UPF device omits the information by analyzing the IP address of the data packet. Whether the data packet satisfies the corresponding local offloading strategy step, thereby improving network processing efficiency.
  • the local offloading policy pre-stored in the terminal includes: a first offload policy determined according to a source IP address of the data packet, a second offload policy determined according to a destination IP address of the data packet, and a third offload policy determined according to a type of the terminal. And one of a fourth offloading policy determined according to the feature information of the application corresponding to the data packet.
  • the local offloading policy is the first offloading policy determined according to the source IP address of the data packet, the data packet to be sent, and the pre-saved local offloading policy, determine whether the data packet is a local offload data packet.
  • the method includes: determining, according to the source IP address of the data packet, the first offload policy, whether the data packet is a local offload data packet, and obtaining a judgment result; wherein the source IP address includes an IPv4 address or an IPv6 prefix address;
  • the result of the judgment is that the data packet is a local offload data packet, the data packet is determined to be a local offload data packet; when the judgment result is that the data packet is not a local offload data packet, it is determined that the data packet is not local. Divert packets.
  • the first offloading policy is determined according to a source IP address of the data packet.
  • determining whether the data packet is a local offloading data packet may be, determining whether the source IP address of the data packet is located in a source saved in the first offloading policy. Within the IP address range, if yes, determining that the data packet is a local offload data packet; or determining whether the source IP address of the data packet is a specific source IP address saved in the first offload policy, if And determining that the data packet is a local offload data packet.
  • the local offloading policy is a second offloading policy determined according to the destination IP address of the data packet, the data packet to be sent, and the pre-saved local offloading policy, determine whether the data packet is a local offload data packet.
  • the method includes: determining, according to the destination IP address of the data packet, and the second offloading policy, whether the data packet is a local offload data packet, and obtaining a judgment result; wherein the destination IP address includes an IPv4 address or an IPv6 prefix address;
  • the result of the judgment is that the data packet is a local offload data packet, the data packet is determined to be a local offload data packet; when the judgment result is that the data packet is not a local offload data packet, it is determined that the data packet is not local. Divert packets.
  • the first offloading policy is determined according to a source IP address of the data packet.
  • determining whether the data packet is a local offloading data packet may be, determining whether the destination IP address of the data packet is saved in the second offloading policy. Within the destination IP address range, if yes, determining that the data packet is a local offload data packet; or determining whether the destination IP address of the data packet is a specific destination IP address saved in the second offload policy, if Yes, it is determined that the data packet is a local offload data packet.
  • determining whether the data packet is a local offloading data packet includes: determining Whether the type of the terminal is the type of the terminal saved in the third offloading policy, and obtains the result of the determination; when the result of the determination is that the type of the terminal is the type of the terminal saved in the third offloading policy, The data packet is a local offload data packet; when the judgment result is that the terminal type of the terminal is not the type of the terminal saved in the third offload policy, the data packet is determined to be a non-local shunt data packet.
  • the third offloading policy is determined according to the type of the terminal. Specifically, the terminal determines whether the terminal type of the terminal is the type of the terminal saved in the third offloading policy, and may identify the operating system installed on the terminal. The type of the operating system is determined to be the type of the operating system saved in the third offloading policy. For example, the type of the operating system saved in the third offloading policy is an Android operating system, if the terminal determines that it is installed by itself. The operating system is an Android operating system, and the data packet is determined to be a local offload data packet. If the terminal determines that the operating system installed by itself is an iOS operating system, it is determined that the data packet is not a local offload data packet.
  • determining whether the data packet is a local offloading data packet includes: Acquiring the feature information corresponding to the application according to the application corresponding to the data packet; determining whether the feature information is the feature information saved in the fourth offloading policy, obtaining a determination result; and when the determining result is the feature
  • the information is the feature information saved in the fourth offloading policy, determining that the data packet is a local offload data packet; and when the determining result is not that the feature information is the feature information saved in the fourth offloading policy, Determining that the data packet is not locally offloaded.
  • the fourth offloading policy is determined according to the feature information of the application, where the feature information includes attribute information of the application, and the attribute information of the application may be function attribute information corresponding to the application, source attribute information of the application, and identification information of the application.
  • the identification information of the application may be an APPID (APPLICATION Identification).
  • the process of acquiring the feature information corresponding to the application according to the application corresponding to the data packet may be: determining, according to the application corresponding to the data packet, an installation path in the application terminal, where the installation path is Obtaining feature information corresponding to the application.
  • the terminal saves the installation information locally after the application is installed, and determines the identification information corresponding to the application according to the installation information corresponding to the application, and the terminal determines the acquisition.
  • Whether the feature information of the application is the feature information saved in the fourth offloading policy may be: determining whether the feature information of the acquired application is the identification information of the instant messaging application saved in the fourth offloading policy, and if yes, determining the The data packet is a local offload data packet, otherwise, it is determined that the data packet is not locally shunted.
  • the terminal may determine whether the data packet to be sent is a local offload data packet, and carry the offload identifier in the data packet determined to be the local offload data packet, so that the UPF device directly identifies the data. Whether the packet carries the offloading identifier to determine whether to perform local offloading on the data packet, and omits the step of the UPF device determining whether the data packet satisfies the corresponding local offloading policy by analyzing information such as the IP address of the data packet. Thereby improving the efficiency of network processing.
  • the method further includes:
  • the local offloading policy sent by the AMF device is sent by the PCF (Policy Control Function) device, or is sent after the User Data Management (UDM) device is specified.
  • PCF Policy Control Function
  • UDM User Data Management
  • the terminal After receiving the local offloading policy sent by the AMF, the terminal may locally save the local offloading policy.
  • the saved offloading policy and the offloaded identifier in the terminal are sent by the network side device, and the terminal receives the local offloading policy and the offloaded identifier and saves the terminal, and the terminal may locally according to the local offloading policy sent by the network side device.
  • the process of offloading ensures the flexibility of terminal shunting.
  • the PCF device or the UDM device performs the data exchange between the PCF device or the UDM device and the AF device according to the data interaction result, and formulates a traffic distribution policy and a distribution offload identifier for the data packet of the AF, or And the terminal accessing the AF device formulates a traffic off policy and assigns a traffic off identifier.
  • FIG. 5 is a schematic diagram of a 5G network architecture based on the TS23.501 standard according to an embodiment of the present invention.
  • a process for a PCF device or a UDM device to send a splitting policy and an assigned offload identifier to an endpoint through an AMF device includes The PCF device sends the specified traffic distribution policy and the assigned traffic distribution identifier to the AMF device through the N15 interface, or the UDM device sends the specified traffic distribution policy and the assigned traffic distribution identifier to the device through the N8 interface AMF, or may be formulated by the PCF device.
  • the offloading policy and the assigned offloading identifier are sent to the SMF (Session Management Function) device through the N7 interface, or the UDM device sends the splitting policy and the assigned offloading identifier to the SMF device through the N10 interface, and then the SMF device receives the After the offloading policy and the offloading identifier sent by the PCF device or the UDM device, the traffic distribution policy and the traffic distribution identifier are sent to the AMF device through the N11 interface. Finally, the AMF device sends the traffic distribution policy and the traffic distribution identifier to the terminal through the interface N1. After the traffic distribution policy and the traffic distribution identifier are saved to the local device, the traffic distribution policy and the traffic distribution identifier are configured. Set.
  • the 5G network architecture separates the control plane from the user plane, and the UPF device implements the packet forwarding function, which can be deployed on the edge of the network as needed.
  • the control plane function SMF device manages the establishment of the data transmission path, that is, configures the UPF device according to the network policy to construct a reasonable data transmission path.
  • Control plane function PCF devices can perform different policy management for different data packets.
  • the control plane function UDM device mainly manages the terminal UE subscription information.
  • the core network control plane device includes an access user session function (AUSF, Access User Session Function) device, a UDM device, an AMF device, an SMF device, a PCF device, and an application function (AF, Application Function) device, and the user plane function device includes the UE, Resident Access Network/Access Network (RAN/AN) device, UPF device, and Data Network (DN) device.
  • AUSF Access User Session Function
  • UDM User Data Management Function
  • AMF Access Management Function
  • SMF Serving Mobility Management Function
  • PCF Packet Control Function
  • AF Application Function
  • RAN/AN Resident Access Network/Access Network
  • UPF User Planet Control Function
  • DN Data Network
  • the data exchange between the control devices of the core network is performed through the interface.
  • the data is directly exchanged between the AUSF device and the UDM device through the N13 interface.
  • the data between the AUSF device and the SMF device can be performed through the N13 interface and then through the N10 interface.
  • the interaction may also be an indirect data interaction through the N12 interface and then through the N11 interface, and direct or indirect data interaction between the control devices of the core network, similar to the process of the AUSF device and the SMF device or the AUSF device and the UDM device, in the present invention There is not much detail in the embodiment.
  • the direct or indirect data interaction between the core network control plane device and the user plane function device is also performed through the interface.
  • the process is similar to the AUSF device and the SMF device or the AUSF device and the UDM device process, and is not described in detail in the embodiment of the present invention.
  • the data interaction between the user plane function devices is completed through the user plane data transmission channel, and the process of performing data interaction between the user plane function devices through the user plane data transmission channel belongs to the prior art, and is not performed in the embodiment of the present invention. Narration.
  • FIG. 6 is a schematic flowchart of a splitting policy formulated by a PCF device according to an embodiment of the present invention, where the steps are as follows:
  • Step 1 The AF device interacts with the core network control plane PCF device through a Network Exposure Function (NEF) device.
  • NEF Network Exposure Function
  • the AF device and the PCF device perform data exchange. If the application corresponding to the AF device is an operator-owned service or an operator-trusted service, the AF device can directly communicate with the PCF device; if the application corresponding to the AF device is a third-party application The communication between the AF device and the PCF device needs to be implemented by the NEF device.
  • Step 2 The AF device interacts with the PCF device through the NEF device.
  • the PCF device establishes a local traffic distribution policy for the data packets of the AF device, and allocates a corresponding local traffic distribution identifier.
  • the PCF device may send the local offloading policy and the local offloading identifier to the AMF device, which may include the following methods:
  • Step 3 The PCF device sends the local offload policy and the local offload identifier to the SMF device.
  • Step 4 The PCF device sends the local offload policy and the local offload identifier to the AMF device.
  • Step 3 The PCF device sends the local offload policy and the local offload identifier to the SMF device.
  • Step 4 The SMF device sends the local offload policy and the local offload identifier to the AMF device.
  • Both the SMF device and the AMF device have a local offloading policy and a local offloading identifier.
  • the SMF device and the AMF device can send the local offloading policy and the local offloading identifier to the UE. If the SMF device sends the message to the UE, the SMF device needs to first The local offloading policy and the local offloading identifier are sent to the AMF device, and the AMF device sends the local offloading policy and the local offloading identifier to the UE. If the AMF device sends the signal to the UE, the AMF device can directly send the local offloading policy and the local offloading identifier. Give the UE.
  • Step 5 The AMF device sends the local offload policy and the local offload identifier to the terminal through the N1 interface.
  • the specific implementation is that the AMF device sends the local offloading policy and the local offloading identifier to the AN device first.
  • Step 6 The AN device sends the local offload policy and the local offload identifier to the UE.
  • FIG. 7 is a schematic flowchart of a splitting policy formulated by a UDM device according to an embodiment of the present invention, where the steps are as follows:
  • Step 1 The AF device interacts with the core network control plane UDM device through the NEF device.
  • the communication between the AF device and the PCF device needs to be implemented by the NEF device.
  • Step 2 The AF device interacts with the UDM device through the NEF device.
  • the UDM device creates a local traffic distribution policy for the data packet of the AF device, and allocates a corresponding local traffic distribution identifier.
  • the UDM device can send the local offloading policy and the local offloading identifier to the AMF device.
  • the specific methods include the following:
  • Step 3 The UDM device sends the local offload policy and the local offload identifier to the SMF device.
  • Step 4 The UDM device sends the local offload policy and the local offload identifier to the AMF device.
  • Step 3 The UDM device sends the local offload policy and the local offload identifier to the SMF device.
  • Step 4 The SMF device sends the local offload policy and the local offload identifier to the AMF device.
  • Both the SMF device and the AMF device have a local offloading policy and a local offloading identifier.
  • the SMF device and the AMF device can send the local offloading policy and the local offloading identifier to the UE. If the SMF device sends the message to the UE, the SMF device needs to first The local offloading policy and the local offloading identifier are sent to the AMF device, and the AMF device sends the local offloading policy and the local offloading identifier to the UE. If the AMF device sends the signal to the UE, the AMF device can directly send the local offloading policy and the local offloading identifier. Give the UE.
  • Step 5 The AMF device sends the local offload policy and the local offload identifier to the terminal UE through the N1 interface.
  • Step 6 The AN device sends the local offload policy and the local offload identifier to the UE.
  • the data interaction process as shown in FIG. 6 and FIG. 7 is all based on the 5G network architecture shown in FIG. 5.
  • the saved offloading policy and the offloaded identifier in the terminal are sent by the network side device, and the terminal receives the local offloading policy and the offloaded identifier and saves the terminal, and the terminal may locally according to the local offloading policy sent by the network side device.
  • the process of offloading ensures the flexibility of terminal shunting.
  • FIG. 8 is a schematic diagram of a process for offloading a data packet according to an embodiment of the present invention, where the process includes the following steps:
  • Step S801 Identify whether the data packet sent by the received terminal carries the traffic distribution identifier; if it is found that the data packet carries the traffic distribution identifier, step S802 is performed; if the data packet does not identify the traffic distribution identifier, step S803 is performed. .
  • the method for distributing the data packet provided in the embodiment of the present invention is applied to the UPF device, and the UPF device can receive the data packet sent by the terminal, and identify whether the data packet carries the traffic distribution identifier.
  • the UPF device stores a fifth offloading policy, which is received and saved locally by data transmission.
  • the fifth offloading policy instructs the UPF device to determine whether to perform local offloading processing on the data packet according to whether the data packet carries the traffic distribution identifier.
  • the UPF device and the terminal may pre-arrange the preset location in the data packet. Carrying the offloading identifier, after receiving the data packet, the UPF device determines whether the shunting identifier is carried in the preset location of the data packet, and determines whether the data packet is locally shunted, and the preset location is a data packet. Data header or data tail, etc.
  • the UPF device may be a UPF device that supports the UL-CL function, or may be a UPF device that supports the Multi-homing Branching Point function.
  • the data exchange between the terminal and the UPF device is performed by using a user plane data transmission channel.
  • the user plane data transmission channel is a PDU session, and the process of establishing a PDU session between the terminal and the UPF device belongs to the prior art. The description of the embodiments of the present invention will not be repeated.
  • the UPF device may also be pre-stored with a set of the offloaded identifiers.
  • the UPF device may determine whether the data packet is locally distributed by the received data packet to determine whether the data packet is locally distributed, or may be a data packet. Whether the offload identifier carried in the packet matches the offload identifier in the set of the offloaded identifiers saved by itself, thereby determining whether to locally offload the data packet. Therefore, in order to ensure that the result of the localized offloading of the data packet is more accurate, the set of the pre-storing identifiers in the UPF device includes at least one of the shunt identifiers saved in the terminal, which is preferred.
  • the offload identifier in the set of the split identifiers pre-stored in the UPF device is consistent with each offload identifier saved in the terminal. For example, if there are a total of 10 offloading identifiers for each application in the terminal, the same 10 outflow identifiers are also included in the set of pre-stored shunt identifiers in the UPF device.
  • the data packet carries a offload identifier, and the data packet is locally uninstalled.
  • the UPF device determines that the data packet carries the traffic distribution identifier, it determines that the data packet needs to be locally distributed; or after the UPF device receives the data packet sent by the terminal, the UPF device identifies whether to carry the traffic distribution identifier in the data packet. If the offloaded identifier is carried, it is determined whether the offloaded identifier matches the offloaded identifier in the set of the offloaded identifiers that are saved by itself. If the matching, the data packet needs to be locally distributed.
  • the UPF device performs local unloading for the data packet that is locally offloaded, and the UPF device that performs the local offloading is the local UPF device, that is, the UPF device that has the local offload function and accesses the same eNB as the terminal.
  • the fifth offloading policy and the offloading identifier saved in the UPF device are: the receiving offloading policy and the offloading identifier sent by the SMF device after being set by the PCF device, and saving the localizing manner; or receiving the shunting sent by the SMF device after the UDM device is established. Policies and offloads are identified and saved locally.
  • the PCF device or the UDM device performs the data exchange between the PCF device or the UDM device and the AF device according to the data interaction result, and formulates a traffic distribution policy and a distribution offload identifier for the data packet of the AF, or And the terminal accessing the AF device formulates a traffic off policy and assigns a traffic off identifier.
  • the offloading policies and the assigned offloading identifiers set by the PCF device or the UDM device for different applications may be the same and may be different.
  • the UE in the PDU session data transmission, the UE carries the offload identifier in the data packet that needs to be locally offloaded according to the local offload policy.
  • the UPF device When the uplink data packet is transmitted to the UPF device, the UPF device locally unloads the data packet carrying the traffic distribution identifier by identifying the traffic distribution identifier on the data packet.
  • the UPF device performs local offloading of the data packet carrying the offloaded identifier, that is, the data packet is offloaded to the local network.
  • S803 Send the data packet to a remote UPF device for processing.
  • the UPF device determines that the data packet does not carry the offloading identifier, the UPF device determines that the data packet does not need to be locally distributed, and the UPF device sends the data packet to the remote UPF device for processing; or is the UPF.
  • the device After receiving the data packet sent by the terminal, the device identifies whether the data packet carries the traffic distribution identifier. If the traffic distribution identifier is carried, the device determines whether the traffic distribution identifier matches the traffic distribution identifier in the set of the traffic distribution identifiers saved by the terminal. The data packet is sent to the remote UPF device for processing. The process of processing the data packet by the remote UPF device is not described in detail in the embodiment of the present invention.
  • the UPF device when the UPF device identifies that the received data packet carries the traffic distribution identifier, the data packet is locally uninstalled, and the UPF device does not need to configure a complicated traffic distribution mechanism, and the UPF device does not need to determine the source IP address in the data packet. Or whether the destination IP is in compliance with the offloading mechanism, but locally identifies the data packet carrying the local offload identifier, which makes the offloading mechanism simpler and further improves the network processing efficiency.
  • the corresponding device can be added to the user plane data transmission channel, and for subsequent data transmission convenience, after the user plane data transmission channel is established, the corresponding device is added, and the corresponding device is added to the user plane. After the data transmission channel, it can interact with the device located in the user plane data transmission channel. Therefore, on the basis of the foregoing embodiment, before the method for determining whether the received data packet is sent by the received terminal, the method further includes:
  • the UF After the UF device is added to the user plane data transmission channel, the UF needs to be configured with a traffic distribution policy and a traffic distribution identifier.
  • the UPF configuration traffic distribution policy and the traffic distribution identifier are as shown in steps 7 and 8 in FIG. 6 and FIG. 7, step 7:
  • the SMF device selects a local offloading UPF device according to the network policy, and configures the local offloading policy and the local offloading identifier to the UPF device.
  • Step 8 The AN device replies to the AMF device, and the related information is successfully sent.
  • the related information is related information used for local offloading, that is, a local offloading policy and a local offloading identifier.
  • the offloading policy sent by the SMF device to the terminal and the offloading policy sent to the UPF device may be the same, and are generally the same, that is, the shunting policy sent by the SMF device to the terminal and the UPF device.
  • Each of the first offloading policy, the second offloading policy, the third offloading policy, and the fourth offloading policy, and the fifth offloading policy, in the offloading process of the data packet, the terminal usually only uses the first trafficking policy.
  • One of the second offloading policy, the third offloading policy, and the fourth offloading policy, and the UPF device generally only uses the fifth offloading policy.
  • the UPF device can be flexibly added and deleted in the user plane data transmission channel.
  • the UPF device receives the request information in the deleted user plane data transmission channel sent by the SMF device; according to the request information, locally deletes the user plane data transmission channel with the terminal, and the SMF device and the terminal
  • the user plane data transmission channel between the UPF device and the terminal saved by itself is also deleted. of course. If there is a need for data transmission with the UPF device, the UPF device may be added to the user plane data transmission channel by using the manner provided in the embodiment of the present invention.
  • the corresponding device is added, and the corresponding device joins the user plane data transmission channel to interact with the device located in the user plane data transmission channel, which facilitates subsequent data. Transfer and user use.
  • FIG. 9 is a structural diagram of a data packet shunting apparatus according to an embodiment of the present disclosure, which is applied to a terminal, where the apparatus includes:
  • the determining module 91 is configured to determine, according to the data packet to be sent, and the local offloading policy, whether the data packet is a local offload data packet, and obtain a judgment result; when the judgment result is that the data packet is a local offload data packet, , triggering the sending module 92;
  • the sending module 92 is configured to carry the offloaded identifier in the data packet, and send the data packet carrying the offloaded identifier to the UPF device through the user plane data transmission channel.
  • the determining module 91 is configured to: when the local offloading policy is the first offloading policy determined according to the source IP address of the data packet, according to the source IP address of the data packet, and the first offloading And determining, by the policy, whether the data packet is a local offload data packet, where the source IP address includes an IPv4 address or an IPv6 prefix address.
  • the determining module 91 is configured to: when the local offload policy is a second offload policy determined according to a destination IP address of the data packet, according to the destination IP address of the data packet, and the second The offloading policy determines whether the data packet is a local offload data packet, where the destination IP address includes an IPv4 address or an IPv6 prefix address.
  • the determining module 91 is configured to determine, when the local offloading policy is a third offloading policy that is determined according to the type of the terminal, whether the terminal type of the terminal is saved in the third offloading policy. The type of terminal.
  • the determining module 91 is configured to: when the local offloading policy is a fourth offloading policy that is determined according to the feature information of the application, obtain the corresponding application according to the application corresponding to the data packet. Feature information; determining whether the feature information is feature information saved in the fourth offload policy.
  • the apparatus further includes: a receiving module 93, configured to receive a local offloading policy sent by the AMF device.
  • the shunting device of the data packet may be implemented by the terminal in an actual application; the judging module 91 in the shunting device of the data packet may be implemented by a central processing unit (CPU) in an actual application. a digital signal processor (DSP), a Microcontroller Unit (MCU), or a Field-Programmable Gate Array (FPGA); the transmitting module 92 in the shunting device of the data packet
  • the receiving module 93 can be implemented in a practical application by a communication module (including: a basic communication suite, an operating system, a communication module, a standardized interface, a protocol, etc.) and a transceiver antenna.
  • the traffic distribution device of the foregoing embodiment only exemplifies the division of each of the foregoing program modules. In actual applications, the foregoing processing may be allocated differently according to requirements.
  • the program module is completed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the embodiment of the method for distributing the data packet provided by the foregoing embodiment is the same as the embodiment of the method for distributing the data packet, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • FIG. 10 is a structural diagram of another apparatus for distributing a data packet according to an embodiment of the present disclosure, which is applied to a UPF device, where the apparatus includes:
  • the identification module 101 is configured to identify whether the data packet sent by the received terminal carries a traffic distribution identifier; if it is identified that the data packet carries the traffic distribution identifier, the traffic distribution module 102 is triggered;
  • the offloading module 102 is configured to locally offload the data packet.
  • the apparatus further includes:
  • the receiving module 103 is configured to receive request information sent by the SMF device and added to the user plane data transmission channel;
  • the adding module 104 is configured to be added to the user plane data transmission channel according to the request information.
  • the data offloading device of the data packet may be implemented by the UPF device in an actual application; the identification module 101, the shunt module 102, and the adding module 104 in the shunting device of the data packet may be used by the CPU in actual applications.
  • DSP, MCU or FPGA implementation; the receiving module 103 in the shunt device of the data packet can be sent and received through a communication module (including: basic communication suite, operating system, communication module, standardized interface, protocol, etc.) in practical applications. Antenna implementation.
  • the traffic distribution device of the foregoing embodiment only exemplifies the division of each of the foregoing program modules. In actual applications, the foregoing processing may be allocated differently according to requirements.
  • the program module is completed, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above.
  • the embodiment of the method for distributing the data packet provided by the foregoing embodiment is the same as the embodiment of the method for distributing the data packet, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • the embodiment of the present invention further provides a data packet shunting device, comprising: a processor and a memory for storing a computer program capable of running on the processor, wherein, as an implementation manner, the data packet shunting device
  • the processor When the processor is used to run the computer program, the processor performs: for the data packet to be sent, and the local offload policy, determining whether the data packet is a local offload data packet, and obtaining a judgment result;
  • the data packet is a local offload data packet
  • the data packet carries the traffic distribution identifier, and the data packet carrying the traffic distribution identifier is sent to the UPF device through the user plane data transmission channel.
  • the processor when the processor is configured to run the computer program, performing: determining, according to a source IP address of the data packet, and a first offload policy, whether the data packet is a local offload data packet, where
  • the source IP address includes an IPv4 address or an IPv6 prefix address.
  • the processor when the processor is configured to run the computer program, performing: determining, according to the destination IP address of the data packet, and the second offload policy, whether the data packet is a local offload data packet, where The destination IP address includes an IPv4 address or an IPv6 prefix address.
  • the processor when the processor is configured to run the computer program, perform: determining whether the terminal type of the terminal is a type of the terminal saved in the third offloading policy.
  • the processor is configured to: when the computer program is executed, perform: acquiring feature information corresponding to the application according to an application corresponding to the data packet; and determining whether the feature information is the fourth current Feature information saved in the policy.
  • the processor when the processor is configured to run the computer program, performing: receiving a local offloading policy sent by the AMF device.
  • the data offloading device is applied to the UPF device, and the processor is configured to: when the computer program is executed, perform: identifying whether the data packet sent by the received terminal carries the offloading identifier; The data packet is identified to carry a offload identifier, and the data packet is locally uninstalled.
  • the method is: before receiving, by the received terminal, whether the data packet sent by the terminal carries the traffic distribution identifier, and receiving the request sent by the SMF device to join the user plane data transmission channel.
  • Information added to the user plane data transmission channel according to the request information.
  • the memory can be either volatile memory or non-volatile memory, and can include both volatile and nonvolatile memory.
  • the non-volatile memory may be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), or an Erasable Programmable Read (EPROM). Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM), Ferromagnetic Random Access Memory (FRAM), Flash Memory, Magnetic Surface Memory , CD-ROM, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface memory can be a disk storage or a tape storage.
  • the volatile memory can be a random access memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • SRAM Static Random Access Memory
  • SSRAM Synchronous Static Random Access Memory
  • SSRAM Dynamic Random Access
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM enhancement Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Dynamic Random Access Memory
  • DRRAM Direct Memory Bus Random Access Memory
  • the method disclosed in the foregoing embodiments of the present invention may be applied to a processor or implemented by a processor.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above described processors may be general purpose processors, DSPs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • the processor may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present invention.
  • a general purpose processor can be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiment of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a storage medium, the storage medium being located in the memory, the processor reading the information in the memory, and completing the steps of the foregoing methods in combination with the hardware thereof.
  • the data packet shunting device may be configured by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), and Complex Programmable Logic Devices. (CPLD, Complex Programmable Logic Device), FPGA, general purpose processor, controller, MCU, microprocessor, or other electronic component implementation for performing the aforementioned method.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal processors
  • PLDs Programmable Logic Devices
  • CPLD Complex Programmable Logic Device
  • FPGA field-programmable Logic Device
  • controller controller
  • MCU microprocessor
  • embodiments of the present invention also provide a computer storage medium, such as a memory including a computer program, which may be executed by a processor of a stream splitting device of a data packet to perform the steps described in the foregoing methods.
  • the computer storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.
  • the computer storage medium provided by the embodiment of the present invention has a computer program stored thereon.
  • the computer program when executed by a processor of a shunt device applied to a data packet of the terminal, the computer program is executed by the processor.
  • the implementation is implemented: determining, for the data packet to be sent, and the local offloading policy, whether the data packet is a local offload data packet, and obtaining a judgment result; when the judgment result is that the data packet is a local offload data packet, The data packet carries the traffic distribution identifier, and the data packet carrying the traffic distribution identifier is sent to the UPF device through the user plane data transmission channel.
  • the computer program when executed by the processor, determining, according to the source IP address of the data packet, and the first offload policy, whether the data packet is a local offload data packet, where the source IP address is Includes IPv4 address or IPv6 prefix address.
  • the computer program is executed by the processor to: determine, according to the destination IP address of the data packet, and the second offload policy, whether the data packet is a local offload data packet, where the destination IP address Includes IPv4 address or IPv6 prefix address.
  • the computer program when executed by the processor, it is implemented to determine whether the terminal type of the terminal is the type of the terminal saved in the third offloading policy.
  • the computer program when executed by the processor, obtaining, according to the application corresponding to the data packet, acquiring feature information corresponding to the application; determining whether the feature information is saved in the fourth trafficking policy Feature information.
  • the computer program is executed by the processor to: receive a local offloading policy sent by the AMF device.
  • the computer program when executed by a processor of a shunt device of a data packet applied to the UPF device, the computer program is executed by the processor to: identify whether the received data packet sent by the terminal is Carrying the offloading identifier; if it is identified that the data packet carries the offloading identifier, the data packet is locally uninstalled.
  • the computer program when executed by the processor, it is implemented to: before receiving, by the received terminal, whether the data packet sent by the terminal carries the shunt identifier, and receiving the request information sent by the SMF device to join the user plane data transmission channel; The request information is added to the user plane data transmission channel.
  • FIG. 11 is a structural diagram of a data packet shunting system according to an embodiment of the present invention.
  • the embodiment of the present invention provides a data packet shunting system, where the system includes: a shunting device for the data packet and a shunting device for the data packet described above in FIG. 10 applied to the UPF device 112; wherein
  • the terminal 111 is configured to determine, according to the data packet to be sent, and the local offload policy, whether the data packet is a local offload data packet, and obtain a judgment result; when the judgment result is that the data packet is a local offload data packet.
  • the data packet carries the traffic distribution identifier, and the data packet carrying the traffic distribution identifier is sent to the UPF device 112 through the user plane data transmission channel;
  • the UPF device 112 is configured to identify whether the data packet sent by the terminal 111 carries a traffic off identifier; if it is identified that the data packet carries a traffic off identifier, the data packet is locally uninstalled.
  • the terminal 111 is configured to: when the local offload policy is the first offload policy determined according to the source IP address of the data packet, according to the source IP address of the data packet, and the first offload a policy, determining whether the data packet is a local offload data packet, and obtaining a judgment result; wherein the source IP address includes an IPv4 address or an IPv6 prefix address; and when the determining result is that the data packet is a local offload data packet, determining The data packet is a local offload data packet; when the judgment result is that the data packet is not a local offload data packet, it is determined that the data packet is not locally shunted.
  • the terminal 111 is configured to: when the local offload policy is a second offload policy determined according to a destination IP address of the data packet, according to the destination IP address of the data packet, and the second offload a policy, determining whether the data packet is a local offload data packet, and obtaining a judgment result; wherein the destination IP address includes an IPv4 address or an IPv6 prefix address; and when the determining result is that the data packet is a local offload data packet, determining The data packet is a local offload data packet; when the judgment result is that the data packet is not a local offload data packet, it is determined that the data packet is not locally shunted.
  • the terminal 111 is configured to determine, according to the third offload policy determined according to the type of the terminal, whether the terminal type of the terminal is a terminal saved in the third offload policy.
  • the type of the judgment result is obtained; when the judgment result is that the terminal type of the terminal is the type of the terminal saved in the third offloading policy, determining that the data packet is a local offload data packet; when the judgment result is itself
  • the terminal type is not the type of the terminal saved in the third offloading policy, it is determined that the data packet is not locally shunted.
  • the terminal 111 is configured to acquire, according to an application corresponding to the data packet, a feature corresponding to the application, when the local traffic distribution policy is a fourth traffic distribution policy determined according to the feature information of the application. Determining whether the feature information is the feature information saved in the fourth offloading policy, and obtaining a determination result; and when the determining result is that the feature information is the feature information saved in the fourth offloading policy, determining The data packet is a local offload data packet; when the determination result is that the feature information is the feature information saved in the fourth offload policy, determining that the data packet is not locally shunted.
  • the terminal 111 is configured to receive a local offloading policy sent by the PCF device through the access and the AMF device, and save the local offloading policy, or receive the local offloading policy sent by the AMF device after the UDM device is configured. And save it locally.
  • the UPF device 112 is further configured to receive request information sent in the user plane data transmission channel sent by the SMF device, and join the user plane data transmission channel according to the request information.
  • the technical solution of the embodiment of the present invention distributes the pressure of the offloading to each terminal, and the UPF device does not need to configure a complicated traffic distribution mechanism, but locally identifies the data packet carrying the local traffic distribution identifier, so that the traffic distribution mechanism is simpler. And further improve the efficiency of network processing.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer 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 computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the terminal determines that the data packet is a local offload data packet, carries the traffic distribution identifier in the data packet, and sends the data packet carrying the traffic distribution identifier to the UPF device, so that the UPF device identifies the received data packet.
  • the offloaded identifier is carried, the data packet is locally unloaded, and the pressure of the offloading is distributed to each terminal.
  • the UPF device does not need to configure a complicated traffic distribution mechanism, but identifies the data packet carrying the local traffic distribution identifier locally. Unloading makes the shunting mechanism simpler and further improves network processing efficiency.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例公开了一种数据包的分流方法、装置和计算机存储介质，所述数据包的分流方法包括：终端针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给用户面功能(UPF)设备。

Description

一种数据包的分流方法、装置和计算机存储介质
相关申请的交叉引用
本申请基于申请号为201710322244.5、申请日为2017年05月09日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本发明涉及通信技术领域，尤其涉及一种数据包的分流方法、装置和计算机存储介质。
背景技术
由于***移动通信技术(4G，the 4th Generation mobile communication)网络中的公用数据网网关(PGW，Public Data Network GateWay)是集中式部署，并且在4G网络中所有的数据包都需要通过回传网络返回核心PGW，所以这样集中回传方式，PGW的处理压力较大，并且数据包经过回传网络长距离传输会造成端到端时延的增加。这些问题在第五代移动通信技术(5G，the 5th Generation mobile communication)网络架构下，可以采用本地分流即边缘计算来解决。
基于5G网络架构的本地分流的技术方案主要包括：
第一种，图1为现有技术提供的建立本地协议数据单元(PDU，Protocol Data Unit)会话的过程示意图，如图1所示，UE触发，建立从终端(UE，User Entity)到本地用户面(UP，User Plane)功能(function)设备的本地PDU会话。具体地，所述UE与接入网(AN，Access Network)设备之间建立连接，所述AN与两个UP function设备建立连接，其中一个UP function 设备与数据网(Data Network)设备建立连接，另一个UP function设备与本地数据网(Local Data Network)设备建立连接，此时，所述UE与两个UP function设备之间的PDU会话建立完成。所述UE在与本地UP function设备可以通过建立的PDU会话进行数据交互，其中本地UP function设备即为与Local Data Network建立连接的UP function设备，同时两个UP function设备和AN设备可以与核心网(CN，Core Network)控制面(Control Plane)设备进行数据交互，从而支持本地分流。
第二种，图2为现有技术提供的上行分类器(UL-CL，UPFLink Classifier)方式实现数据包分流的示意图，如图2所示，用户面功能(UPF，User Plane Function)设备支持UL-CL功能，通过查询数据包的目的地址来实现数据分流，将满足条件的数据包卸载到本地网络中，终端只需要支持一个网络协议(IP，Internet Protocol)地址。具体地，UPF设备接收到UE通过AN发送的数据包，根据数据包中的目的IP地址及本地的UL-CL功能，对数据包进行分流，如果数据包中目的IP地址满足第一条件，则将数据包发送给UPF设备的PDU会话(PDU Session)锚点1(Anchor1)，如果数据包中目的IP地址满足第二条件，则将数据包发送给UPF设备的PDU会话锚点2(Anchor2)，UPF设备将对应的数据包发送给DN，此外，如图2中所示的不同设备之间可以通过对应的接口完成数据交互。
第三种、图3为现有技术提供的多归属分支点(Multi-homing Branching Point)方式实现数据包分流的示意图，如图3所示，UPF支持Multi-homing branching point功能，通过查询数据包的源IP地址(UE的IP地址)来实现数据分流，将满足条件的数据包卸载到本地网络中，终端需要支持多个IP地址。具体地，UPF设备接收到UE通过AN发送的数据包，根据数据包中的源IP地址及本地的UL-CL功能，对数据包进行分流，如果数据包中源IP地址满足第一条件，则将数据包发送给UPF设备的PDU会话锚点1 (Anchor1)，如果数据包中源IP地址满足第二条件，则将数据包发送给UPF设备的PDU会话锚点2(Anchor2)，UPF设备将对应的数据包发送给DN，此外，如图2中所示的不同设备之间可以通过对应的接口完成数据交互。
目前的三种方案中，第二种和第三种机制需要在UPF设备上针对不同的目的IP地址或源IP地址分别配置对应的分流策略，如果需要配置分流策略的目的IP地址或源IP地址过多，则需要会话管理(SM，Session Management)功能设备或网管在UPF设备上进行较复杂的配置，导致分流机制复杂；另外，现有的分流过程都是需要UPF设备根据数据包的IP地址进行分流，UPF设备的处理压力较大，对数据包处理速度有一定的影响，导致网络处理效率过低。
发明内容
本发明实施例提供了一种数据包的分流方法、装置和计算机存储介质，用以解决现有技术中存在的分流机制复杂和网络处理效率过低的问题。
为了解决上述问题，本发明实施例提供了一种数据包的分流方法，应用于终端，所述方法包括：针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。
在一实施例中，当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，所述针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包包括：根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括互联网协议第4版IPv4地址或互联网协议第6版IPv6前缀地址。
在一实施例中，当所述本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，所述针对待发送的数据包，及本地分流策略，判断所 述数据包是否为本地分流数据包包括：根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其中所述目的IP地址包括IPv4地址或IPv6前缀地址。
在一实施例中，当所述本地分流策略为根据终端的类型确定的第三分流策略时，所述针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包包括：判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
在一实施例中，当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，所述针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包包括：根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息。
在一实施例中，还包括：接收AMF(接入和移动性管理功能)设备发送的本地分流策略。
本发明实施例还提供了一种数据包的分流方法，应用于UPF设备，所述方法包括：识别接收到的终端发送的数据包中是否携带分流标识；
若识别出所述数据包中携带分流标识，对所述数据包进行本地卸载。
在一实施例中，所述识别接收到的终端发送的数据包中是否携带分流标识之前，所述方法还包括：接收SMF设备发送的加入用户面数据传输通道中的请求信息；根据所述请求信息，加入到所述用户面数据传输通道中。
本发明实施例还提供了一种数据包的分流装置，应用于终端，所述装置包括：
判断模块，配置为针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，触发发送模块；
发送模块，配置为在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。
在一实施例中，所述判断模块，配置为当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括互联网协议第4版IPv4地址或互联网协议第6版IPv6前缀地址。
在一实施例中，所述判断模块，配置为当所述本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其中所述目的IP地址包括IPv4地址或IPv6前缀地址。
在一实施例中，所述判断模块，配置为当所述本地分流策略为根据终端的类型确定的第三分流策略时，判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
在一实施例中，所述判断模块，配置为当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息。
在一实施例中，所述装置还包括：接收模块，配置为接收AMF设备发送的本地分流策略。
本发明提供了一种数据包的分流装置，应用于UPF设备，所述装置包括：
识别模块，配置为识别接收到的终端发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，触发分流模块；
分流模块，配置为对所述数据包进行本地卸载。
在一实施例中，所述装置还包括：
接收模块，配置为接收SMF设备发送的加入用户面数据传输通道中的请求信息；
加入模块，配置为根据所述请求信息，加入到所述用户面数据传输通道中。
本发明实施例提供了一种数据包的分流方法、装置和计算机存储介质，所述数据包的分流方法包括：终端针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。采用本发明实施例的技术方案，在终端判定数据包为本地分流数据包时，在数据包中携带分流标识，并将携带有分流标识的数据包发送给UPF设备，使得UPF设备识别接收的数据包中携带有分流标识时，对所述数据包进行本地卸载，将分流的压力分散到每个终端，UPF设备不需要配置复杂的分流机制，而是将识别到携带有本地分流标识的数据包进行本地卸载，使得分流机制更加简单，并进一步提高了网络处理效率。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为现有技术提供的建立本地PDU会话的过程示意图；
图2为现有技术提供的UL-CL方式实现数据包分流的示意图；
图3为现有技术提供的Multi-homing Branching Point方式实现数据包分流的示意图；
图4为本发明实施例1提供的一种数据包的分流过程的示意图；
图5为本发明实施例3提供的基于TS23.501标准的5G网络架构图；
图6为本发明实施例3提供的一种由PCF设备制定分流策略的数据包的分流过程的示意图；
图7为本发明实施例3提供的一种由UDM设备制定分流策略的数据包的分流***的结构图；
图8为本发明实施例4提供的一种数据包的分流的流程示意图；
图9为本发明实施例6提供的一种数据包的分流装置的结构图；
图10为本发明实施例6提供的另一种数据包的分流装置的结构图；
图11为本发明实施例6提供的一种数据包的分流的流程示意图。
具体实施方式
为了使得分流机制更加简单，并进一步提高网络处理效率，本发明实施例提供了一种数据包的分流方法及装置。
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明的一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
实施例1：
图4为本发明实施例提供的一种数据包的分流过程的示意图，该过程包括以下步骤：
步骤S401：针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，执行步骤S402，当所述判断结果不是所述数据包为本地分流数据包时，执行步骤S403。
本发明实施例提供的数据包的分流方法应用于终端，所述终端可以是PC(个人计算机)、笔记本电脑、手机等能够发送数据包的终端，所述终端中预先保存有对数据包进行分流的本地分流策略。
所述终端保存的本地分流策略可以是在终端出厂时预先保存到本地的，也可以是网络侧设备发送给终端，终端接收并保存的。所述本地分流策略可以是根据数据包的源IP地址确定的第一分流策略，也可以是根据数据包目的IP地址确定的第二分流策略，但需要注意的是，所述终端中只会保存一种本地分流策略。所述终端根据预先保存的本地分流策略，可以判断所述数据包是否为本地分流数据包，也就是是否可实现本地分流。
所述源IP地址可以是互联网协议第4版(IPv4，Internet Protocol Version4)地址或互联网协议第6版(IPv6，Internet Protocol Version 6)前缀地址，对应的所述目的IP地址也可以是IPv4地址或IPv6前缀地址。
其中该根据源IP地址确定的第一分流策略中，保存的是每个源IP地址对应的数据包是否本地分流数据包，或者为了减小数据量，在该第一分流策略中可以只保存本地分流数据包对应的源IP地址，或者非本地分流数据包对应的源IP地址；相应的根据目的IP地址确定的第二分流策略中，保存的是每个目的IP地址对应的数据包是否为本地分流数据包，或者同样地为了减小数据量，在该第二分流策略中可以只保存本地分流数据包对应的目的IP地址，或者非本地分流数据包对应的目的IP地址。
S402：在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。
终端根据分流策略可以识别哪些数据包是本地分流数据包，即对哪些数据包进行本地分流，并在确定数据包为本地分流数据包时，在数据包中添加对应的分流标识，所述分流标识为任意能够标识所述数据包为本地分流数据包的标识信息即可，UPF设备根据数据包中是否携带分流标识，确 定是否对数据包进行本地分流处理。
具体的，终端当识别该数据包为本地分流数据包时，则在该数据包中携带分流标识，其中该分流标识可以携带在数据包的预设位置，例如携带在数据包的数据头或者数据尾等，具体的在哪里携带分流标识可以在终端和UPF设备中预先约定，只要保证终端在数据包中携带了分流标识后，UPF设备能够识别出即可。
例如当终端识别到该数据包为本地分流数据包时，确定该数据包对应的分流标识为1，预先约定的预设位置为数据尾，则在该数据包的数据尾携带分流标识1；UPF设备接收到携带有分流标识的数据包后，识别到所述数据包的数据尾的携带有分流标识1，则可确定需要对所述数据包进行本地分流。
进行本地分流的UPF设备为本地UPF设备，即具有本地分流功能且与所述终端接入相同演进型基站(eNB)的UPF设备。
所述终端与UPF设备进行数据交互是通过用户面数据传输通道来完成的，所述用户面数据传输通道为PDU会话，所述终端与所述UPF设备建立PDU会话的过程在本发明实施例中不做赘述。
S403：将所述数据包通过用户面数据传输通道发送给UPF设备。
如果所述终端判断所述数据包不为本地分流数据包，则直接将所述数据包通过用户面传输通道发送给UPF设备，UPF设备根据数据包中是否携带分流标识，确定是否对数据包进行本地分流处理。
如果终端可以在数据包中携带不同的分流标识，则UPF设备中预先保存有分流标识的集合。UPF设备可以是接收到终端发送的数据包后，在该数据包的预设位置识别是否携带分流标识，如果携带分流标识，则判断该分流标识是否与自身保存的分流标识的集合中的分流标识匹配，如果匹配，则确定该数据包为本地分流数据包，如果不匹配，确定该数据包非本地分 流数据包。
所述UPF设备可以是支持UL-CL功能的UPF设备，也可以是支持Multi-homing Branching Point功能的UPF设备。
在本发明实施例中终端针对待发送的数据包，及本地分流策略，判断所述数据包是否为分流数据包，当所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带有分流标识的数据包发送给UPF设备，使得UPF设备识别接收的数据包中携带有分流标识时，对所述数据包进行本地卸载，将分流的压力分散到每个终端，UPF设备不需要配置复杂的分流机制，而是将识别到携带有本地分流标识的数据包进行本地卸载，使得分流机制更加简单，减轻了UPF设备的压力，并进一步提高了网络处理效率。
实施例2：
为了提高网络处理效率，在上述实施例的基础上，本发明实施例中，所述终端根据本地分流策略，可以确定待发送的数据包是否为本地分流数据包，并在确定为本地分流数据包的数据包中携带分流标识，使得UPF设备直接识别数据包中是否携带有分流标识，从而确定是否对所述数据包进行本地分流处理，省略了UPF设备通过分析数据包的IP地址等信息来判断该数据包是否满足对应的本地分流策略这一步骤，从而提高了网络处理效率。
所述终端中预先保存的本地分流策略包括：根据数据包的源IP地址确定的第一分流策略、根据数据包的目的IP地址确定的第二分流策略、根据终端的类型确定的第三分流策略和根据数据包对应的应用的特征信息确定的第四分流策略中的其中一种。
当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，所述针对待发送的数据包，及预先保存的本地分流策略，判断所述数 据包是否为本地分流数据包包括：根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；其中所述源IP地址包括IPv4地址或IPv6前缀地址；当所述判断结果为所述数据包为本地分流数据包时，确定所述数据包为本地分流数据包；当所述判断结果为所述数据包不是本地分流数据包时，确定所述数据包非本地分流数据包。
所述第一分流策略为根据数据包的源IP地址确定的。当所述终端预先保存的本地分流策略为第一分流策略时，确定所述数据包是否为本地分流数据包可以是，判断所述数据包的源IP地址是否位于第一分流策略中保存的源IP地址范围内，如果是，确定所述数据包为本地分流数据包；也可以是判断所述数据包的源IP地址是否为第一分流策略中保存的某个特定的源IP地址，如果是，确定所述数据包为本地分流数据包。
当所述本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，所述针对待发送的数据包，及预先保存的本地分流策略，判断所述数据包是否为本地分流数据包包括：根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；其中所述目的IP地址包括IPv4地址或IPv6前缀地址；当所述判断结果为所述数据包为本地分流数据包时，确定所述数据包为本地分流数据包；当所述判断结果为所述数据包不是本地分流数据包时，确定所述数据包非本地分流数据包。
所述第一分流策略为根据数据包的源IP地址确定的。当所述终端预先保存的本地分流策略为第二分流策略时，则确定所述数据包是否为本地分流数据包可以是，判断所述数据包的目的IP地址是否位于第二分流策略中保存的目的IP地址范围内，如果是，确定所述数据包为本地分流数据包；也可以是判断所述数据包的目的IP地址是否为第二分流策略中保存的某个 特定的目的IP地址，如果是，确定所述数据包为本地分流数据包。
当所述本地分流策略为根据终端的类型确定的第三分流策略时，所述针对待发送的数据包，及预先保存的本地分流策略，判断所述数据包是否为本地分流数据包包括：判断自身的终端类型是否为所述第三分流策略中保存的终端的类型，获得判断结果；当所述判断结果为自身的终端类型为所述第三分流策略中保存的终端的类型时，确定所述数据包为本地分流数据包；当所述判断结果为自身的终端类型不是所述第三分流策略中保存的终端的类型时，确定所述数据包非本地分流数据包。
所述第三分流策略为根据终端的类型确定的，具体地，所述终端判断自身的终端类型是否为所述第三分流策略中保存的终端的类型可以是，识别安装在终端上的操作***的类型，判断该操作***的类型是否为第三分流策略中保存的操作***的类型，例如所述第三分流策略中保存的操作***的类型为安卓操作***，如果所述终端确定自身安装的操作***为安卓操作***，则确定所述数据包为本地分流数据包，如果所述终端确定自身安装的操作***为iOS操作***，则确定所述数据包不为本地分流数据包。
当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，所述针对待发送的数据包，及预先保存的本地分流策略，判断所述数据包是否为本地分流数据包包括：根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息，获得判断结果；当所述判断结果为所述特征信息为所述第四分流策略中保存的特征信息时，确定所述数据包为本地分流数据包；当所述判断结果不是所述特征信息为所述第四分流策略中保存的特征信息时，确定所述数据包非本地分流数据包。
所述第四分流策略为根据应用的特征信息确定的，其中该特征信息包括应用的属性信息，所述应用的属性信息可以是应用对应的功能属性信息、 应用的来源属性信息和应用的标识信息中的一种或几种，所述应用的标识信息可以是应用唯一编码(APPID，APPlication Identification)。
所述终端根据所述数据包对应的应用，获取所述应用对应的特征信息的过程可以是根据所述数据包对应的应用，确定所述应用所述终端中的安装路径，在所述安装路径下获取所述应用对应的特征信息。
当所述特征信息为应用的标识信息时，终端在所述应用安装完成后会在本地保存安装信息，根据所述应用对应的安装信息，确定所述应用对应的标识信息，所述终端判断获取的应用的特征信息是否为第四分流策略中保存的特征信息可以是，判断获取的应用的特征信息是否为所述第四分流策略中保存的即时通讯应用的标识信息，如果是，则确定所述数据包为本地分流数据包，否则，确定所述数据包非本地分流数据包。
本发明实施例中，所述终端根据本地分流策略，可以确定待发送的数据包是否为本地分流数据包，并在确定为本地分流数据包的数据包中携带分流标识，使得UPF设备直接识别数据包中是否携带有分流标识，从而确定是否对所述数据包进行本地分流处理，省略了UPF设备通过分析数据包的IP地址等信息来判断该数据包是否满足对应的本地分流策略这一步骤，从而提高了网络处理效率。
实施例3：
在上述各实施例的基础上，为了保证终端分流的灵活性，本发明实施例中，所述方法还包括：
接收通过接入和移动性管理功能(AMF，Access Management Function)设备发送的本地分流策略。
其中所述AMF设备发送的本地分流策略为策略控制功能(PCF，Policy Control Function)设备制定后发送的；或为用户数据管理(UDM，User Data Management)设备制定后发送的。
所述终端在接收到AMF发送的本地分流策略后，可以在本地保存所述本地分流策略。
本发明实施例中，所述终端中的保存的分流策略及分流标识为网络侧设备发送的，终端接收本地分流策略及分流标识并保存的，终端可以根据网络侧设备发送的本地分流策略进行本地分流的过程，从而保证了终端分流的灵活性。
PCF设备或UDM设备在制定分流策略和分配分流标识的过程为：PCF设备或UDM设备与AF设备进行数据交互，根据数据交互结果，为该AF的数据包制定分流策略和分配分流标识，或/和访问该AF设备的终端制定分流策略和分配分流标识。
图5为本发明实施例提供的基于TS23.501标准的5G网络架构图，如图5所示，PCF设备或UDM设备将制定的分流策略和分配的分流标识通过AMF设备发送给终端的过程包括：PCF设备将制定的分流策略和分配的分流标识通过N15接口发送给AMF设备，或UDM设备将制定的分流策略和分配的分流标识通过N8接口AMF发送给设备，还可以是PCF设备将制定的分流策略和分配的分流标识通过N7接口发送给会话管理功能(SMF，Session Management Function)设备，或UDM设备将制定的分流策略和分配的分流标识通过N10接口发送给SMF设备，然后SMF设备在接收到PCF设备或UDM设备发送的分流策略和分流标识后，通过N11接口将分流策略和分流标识发送给AMF设备，最后再由AMF设备通过接口N1将分流策略和分流标识发送给终端，终端接收到分流策略和分流标识后保存到本地，完成终端的分流策略和分流标识的配置。
此外，如图5所示，5G网络架构实现控制面与用户面分离，UPF设备实现数据包转发功能，可以按需部署在网络边缘。控制面功能SMF设备管理数据传输路径的建立，即根据网络策略配置UPF设备，构建合理的数据 传输路径。控制面功能PCF设备可以针对不同数据包进行不同的策略管理。控制面功能UDM设备主要对终端UE签约信息进行管理。
核心网控制面设备包括接入用户会话功能(AUSF，Access User Session Function)设备、UDM设备、AMF设备、SMF设备、PCF设备和应用功能(AF，Application Function)设备，用户面功能设备包括UE、居民接入网/接入网(RAN/AN，Residential Access Network/Access Network)设备、UPF设备和数据网(DN，Data Network)设备。
核心网控制面设备之间数据交互是通过接口完成的，例如AUSF设备和UDM设备之间直接通过N13接口进行数据交互，AUSF设备和SMF设备之间可以是先通过N13接口再通过N10接口进行数据交互，也可以是先通过N12接口再通过N11接口进行间接数据交互，核心网控制面设备之间的直接或间接数据交互，与AUSF设备和SMF设备或AUSF设备和UDM设备过程相似，在本发明实施例中不多赘述。
核心网控制面设备与用户面功能设备之间的直接或间接数据交互也是通过接口完成的，过程与AUSF设备和SMF设备或AUSF设备和UDM设备过程相似，在本发明实施例中不多赘述。
用户面功能设备之间的数据交互为通过用户面数据传输通道完成，所述用户面功能设备之间通过用户面数据传输通道完成数据交互的过程属于现有技术，在本发明实施例中不做赘述。
图6为本发明实施例提供的一种由PCF设备制定分流策略的流程示意图，步骤如下：
步骤①：AF设备通过能力开放功能(NEF，Network Exposure Function)设备，与核心网控制面PCF设备进行交互。
AF设备与PCF设备进行数据交互，若该AF设备对应的应用为运营商自有业务或运营商可信赖业务，则AF设备可与PCF设备直接通信；若该 AF设备对应的应用为第三方应用，则AF设备与PCF设备的通信需要通过NEF设备实现。图6中所示的所述AF设备对应的应用的第三方应用。
步骤②：AF设备通过NEF设备与PCF设备进行交互，PCF设备为该AF设备的数据包制定本地分流策略，并分配相应的本地分流标识。
在一个PDU会话建立或修改的过程中，PCF设备可以将本地分流策略及本地分流标识发送给AMF设备，具体的可以包括以下几种方式：
方式一：
步骤③：PCF设备将本地分流策略及本地分流标识发送给SMF设备。
步骤④：PCF设备将本地分流策略及本地分流标识发送给AMF设备。
方式二：
步骤③：PCF设备将本地分流策略及本地分流标识发送给SMF设备。
步骤④：SMF设备将本地分流策略及本地分流标识发送给AMF设备。
SMF设备和AMF设备中均保存有本地分流策略及本地分流标识，SMF设备和AMF设备均可以将本地分流策略及本地分流标识发送给UE，如果是SMF设备发送给UE，则SMF设备需要先将本地分流策略及本地分流标识发送给AMF设备，再由AMF设备将本地分流策略及本地分流标识发送给UE；如果是AMF设备发送给UE，则AMF设备可以直接将本地分流策略及本地分流标识发送给UE。
步骤⑤：AMF设备通过N1接口将本地分流策略及本地分流标识发送给终端。
具体实现为AMF设备将本地分流策略及本地分流标识先发送给AN设备。
步骤⑥：AN设备将本地分流策略及本地分流标识发送给UE。
图7为本发明实施例提供的一种由UDM设备制定分流策略的流程示意图，步骤如下：
步骤①：AF设备通过NEF设备，与核心网控制面UDM设备进行交互。
如图7所示的所述AF设备对应的应用的第三方应用，则AF设备与PCF设备的通信需要通过NEF设备实现。
步骤②：AF设备通过NEF设备与UDM设备进行交互，UDM设备为该AF设备的数据包制定本地分流策略，并分配相应的本地分流标识。
在一个PDU会话建立或修改的过程中，UDM设备可以将本地分流策略及本地分流标识发送给AMF设备，具体的可以包括以下几种方式：
方式一：
步骤③：UDM设备将本地分流策略及本地分流标识发送给SMF设备。
步骤④：UDM设备将本地分流策略及本地分流标识发送给AMF设备。
方式二：
步骤③：UDM设备将本地分流策略及本地分流标识发送给SMF设备。
步骤④：SMF设备将本地分流策略及本地分流标识发送给AMF设备。
SMF设备和AMF设备中均保存有本地分流策略及本地分流标识，SMF设备和AMF设备均可以将本地分流策略及本地分流标识发送给UE，如果是SMF设备发送给UE，则SMF设备需要先将本地分流策略及本地分流标识发送给AMF设备，再由AMF设备将本地分流策略及本地分流标识发送给UE；如果是AMF设备发送给UE，则AMF设备可以直接将本地分流策略及本地分流标识发送给UE。
步骤⑤：AMF设备通过N1接口将本地分流策略及本地分流标识发送给终端UE。
步骤⑥：AN设备将本地分流策略及本地分流标识发送给UE。
如图6和图7所述的数据交互过程都是基于图5所示的5G网络架构来完成的。
本发明实施例中，所述终端中的保存的分流策略及分流标识为网络侧 设备发送的，终端接收本地分流策略及分流标识并保存的，终端可以根据网络侧设备发送的本地分流策略进行本地分流的过程，从而保证了终端分流的灵活性。
实施例4：
图8为本发明实施例提供的一种数据包的分流过程的示意图，该过程包括以下步骤：
步骤S801：识别接收到的终端发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，执行步骤S802；若未识别出所述数据包中携带分流标识，执行步骤S803。
本发明实施例中提供的数据包的分流方法应用于UPF设备，所述UPF设备可以接收终端发送的数据包，并识别所述数据包中是否携带有分流标识。
所述UPF设备保存有第五分流策略，所述第五分流策略为通过数据传输接收到并保存到本地的。
所述第五分流策略指示UPF设备根据数据包中是否携带分流标识，确定是否对数据包进行本地分流处理，具体地，所述UPF设备和终端中可以预先约定在数据包中的预设位置处携带分流标识，所述UPF设备接收到数据包后，判断在数据包的预设位置处是否携带有分流标识，则确定是否对该数据包进行本地分流处理，所述预设位置为数据包的数据头或者数据尾等。
所述UPF设备可以是支持UL-CL功能的UPF设备，也可以是支持Multi-homing Branching Point功能的UPF设备。
所述终端与UPF设备进行数据交互是通过用户面数据传输通道来完成的，所述用户面数据传输通道为PDU会话，所述终端与所述UPF设备建立PDU会话的过程属于现有技术，在本发明实施例中不做赘述。
当然UPF设备中还可以预先保存有分流标识的集合，所述UPF设备可以是在接收到的数据包识别是否携带有分流标识，来确定是否对数据包进行本地分流处理，还可以是判断数据包中携带的分流标识是否与自身保存的分流标识的集合中的分流标识匹配，从而确定是否对数据包进行本地分流。因此为了保证所述UPF设备在对数据包是否需要进行本地分流的判断结果更加准确，所述UPF设备中预先保存有分流标识的集合中至少包括所述终端中保存的每种分流标识，较优地，所述UPF设备中预先保存有分流标识的集合中的分流标识与所述终端中保存的各分流标识一致。例如终端中各应用对应的分流标识一共是10个，则UPF设备中预先保存有分流标识的集合中也包括相同的10个分流标识。
S802：所述数据包中携带分流标识，对所述数据包进行本地卸载。
UPF设备如果识别出所述数据包中携带有分流标识，则确定所述数据包需要进行本地分流；或者是UPF设备接收到终端发送的数据包后，在所述数据包中识别是否携带分流标识，如果携带分流标识，则判断该分流标识是否与自身保存的分流标识的集合中的分流标识匹配，如果匹配，则确定所述数据包需要进行本地分流。
UPF设备针对进行本地分流的数据包，进行本地卸载，进行本地卸载的UPF设备为本地UPF设备，即具有本地分流功能且与所述终端接入相同eNB的UPF设备。
所述UPF设备中保存的第五分流策略和分流标识为，接收PCF设备制定后通过SMF设备发送的分流策略和分流标识，并保存在本地的；或接收UDM设备制定后通过SMF设备发送的分流策略和分流标识，并保存在本地的。
PCF设备或UDM设备在制定分流策略和分配分流标识的过程为，PCF设备或UDM设备与AF设备进行数据交互，根据数据交互结果，为该AF 的数据包制定分流策略和分配分流标识，或/和访问该AF设备的终端制定分流策略和分配分流标识。PCF设备或UDM设备为不同应用制定的分流策略和分配的分流标识可以相同，可以不同。
PCF设备或UDM设备将制定的分流策略和分配的分流标识通过SMF设备发送给终端的过程依据如图5所示的基于TS23.501标准的5G网络架构图来完成。
如图6和图7所示的步骤⑨：该PDU会话数据传输中，UE根据本地分流策略，在需要本地分流的数据包中携带分流标识。当上行数据包传输到所述UPF设备上时，所述UPF设备通过识别数据包上的分流标识，将携带有分流标识的数据包进行本地卸载。
所述UPF设备将携带有分流标识的数据包进行本地卸载即将所述数据包分流到本地网络。
S803：将所述数据包发送给远端UPF设备进行处理。
UPF设备如果识别出所述数据包中未携带分流标识，则所述UPF设备确定所述数据包不需要进行本地分流，UPF设备将所述数据包发送给远端UPF设备进行处理；或者是UPF设备接收到终端发送的数据包后，识别所述数据包中是否携带分流标识，如果携带分流标识，则判断该分流标识是否与自身保存的分流标识的集合中的分流标识匹配，如果不匹配，则确定所述数据包不需要进行本地分流，UPF设备将所述数据包发送给远端UPF设备进行处理。所述远端UPF设备对所述数据包进行处理的过程在本发明实施例中不做赘述。
在本发明实施例中UPF设备识别接收的数据包中携带有分流标识时，对所述数据包进行本地卸载，UPF设备不需要配置复杂的分流机制，UPF设备不需要判断数据包中的源IP或目的IP是否符合分流机制，而是将识别到携带有本地分流标识的数据包进行本地卸载，使得分流机制更加简单， 并进一步提高了网络处理效率。
实施例5：
在建立用户面数据传输通道中可以将相应的设备中加入用户面数据传输通道中，而为了后续数据传输方便，可以在建立用户面数据传输通道后，再加入相应的设备，相应设备加入用户面数据传输通道后即可与位于用户面数据传输通道中的设备进行交互了。因此在上述实施例的基础上，在本发明实施例中所述识别接收到的终端发送的数据包中是否携带分流标识之前，所述方法还包括：
接收SMF设备发送的加入用户面数据传输通道中的请求信息；根据所述请求信息，加入到所述用户面数据传输通道中。
当UPF设备加入到用户面数据传输通道后需要对UPF配置分流策略和分流标识，所述对UPF配置分流策略和分流标识如图6和图7中的步骤⑦和步骤⑧所示，步骤⑦：SMF设备根据网络策略选择支持本地分流的UPF设备，并将本地分流策略及本地分流标识配置到所述UPF设备上。步骤⑧：AN设备回复AMF设备，相关信息发送成功。所述相关信息为用于本地分流的相关信息，即本地分流策略及本地分流标识。
SMF设备向所述终端发送的分流策略和向所述UPF设备发送的分流策略可以相同可以不同，通常情况下是相同的，也就是说SMF设备向所述终端和所述UPF设备发送的分流策略均包括第一分流策略、第二分流策略、第三分流策略和第四分流策略中的其中一种和第五分流策略，在数据包的分流过程中，所述终端通常只使用第一分流策略、第二分流策略、第三分流策略和第四分流策略中的其中一种，而所述UPF设备通常只使用第五分流策略。
当然为了方便用户的使用，也可以在用户面数据传输通道中删除一些设备，通过上述实施方式，可以在用户面数据传输通道灵活的增删UPF设 备。
具体地，所述UPF设备接收SMF设备发送的删除用户面数据传输通道中的请求信息；根据所述请求信息，在本地删除与所述终端之间的用户面数据传输通道，并且SMF设备和终端也删除自身保存的UPF设备和终端之间的用户面数据传输通道。当然。如果之后存在与所述UPF设备进行数据传输的需求，可以利用本发明实施例中的提供的方式在用户面数据传输通道中加入所述UPF设备即可。
在本发明实施例中，建立用户面数据传输通道后，再加入相应的设备，相应设备加入用户面数据传输通道后即可与位于用户面数据传输通道中的设备进行交互了，方便了后续数据传输和用户使用。
实施例6：
图9为本发明实施例提供的一种数据包的分流装置的结构图，应用于终端，所述装置包括：
判断模块91，配置为针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，触发发送模块92；
所述发送模块92，配置为在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。
作为一种实施方式，所述判断模块91，配置为当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括IPv4地址或IPv6前缀地址。
作为另一种实施方式，所述判断模块91，配置为当所述本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其 中所述目的IP地址包括IPv4地址或IPv6前缀地址。
作为又一种实施方式，所述判断模块91，配置为当所述本地分流策略为根据终端的类型确定的第三分流策略时，判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
作为再一种实施方式，所述判断模块91，配置为当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息。
在一实施例中，所述装置还包括：接收模块93，配置为接收AMF设备发送的本地分流策略。
本发明实施例中，所述数据包的分流装置在实际应用中可由终端实现；所述数据包的分流装置中的判断模块91，在实际应用中可由中央处理器(CPU，Central Processing Unit)、数字信号处理器(DSP，Digital Signal Processor)、微控制单元(MCU，Microcontroller Unit)或可编程门阵列(FPGA，Field－Programmable Gate Array)实现；所述数据包的分流装置中的发送模块92和接收模块93，在实际应用中可通过通信模组(包含：基础通信套件、操作***、通信模块、标准化接口和协议等)及收发天线实现。
需要说明的是：上述实施例提供的数据包的分流装置在进行数据包的分流处理时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将装置的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的数据包的分流装置与数据包的分流方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图10为本发明实施例提供的另一种数据包的分流装置的结构图，应用 于UPF设备，所述装置包括：
识别模块101，配置为识别接收到的终端发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，触发分流模块102；
所述分流模块102，配置为对所述数据包进行本地卸载。
在一实施例中，所述装置还包括：
接收模块103，配置为接收SMF设备发送的加入用户面数据传输通道中的请求信息；
加入模块104，配置为根据所述请求信息，加入到所述用户面数据传输通道中。
本发明实施例中，所述数据包的分流装置在实际应用中可由UPF设备实现；所述数据包的分流装置中的识别模块101、分流模块102和加入模块104，在实际应用中可由CPU、DSP、MCU或FPGA实现；所述数据包的分流装置中的接收模块103，在实际应用中可通过通信模组(包含：基础通信套件、操作***、通信模块、标准化接口和协议等)及收发天线实现。
需要说明的是：上述实施例提供的数据包的分流装置在进行数据包的分流处理时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将装置的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的数据包的分流装置与数据包的分流方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
实施例7：
本发明实施例还提供了一种数据包的分流装置，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，作为一种实施方式，所述数据包的分流装置应用于终端，则所述处理器用于运行所述计算机程序时，执行：针对待发送的数据包，及本地分流策略，判断所述数据 包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。
在一实施例中，所述处理器用于运行所述计算机程序时，执行：根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括IPv4地址或IPv6前缀地址。
在一实施例中，所述处理器用于运行所述计算机程序时，执行：根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其中所述目的IP地址包括IPv4地址或IPv6前缀地址。
在一实施例中，所述处理器用于运行所述计算机程序时，执行：判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
在一实施例中，所述处理器用于运行所述计算机程序时，执行：根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息。
在一实施例中，所述处理器用于运行所述计算机程序时，执行：接收AMF设备发送的本地分流策略。
作为另一种实施方式，所述数据包的分流装置应用于UPF设备，则所述处理器用于运行所述计算机程序时，执行：识别接收到的终端发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，对所述数据包进行本地卸载。
在一实施例中，所述处理器用于运行所述计算机程序时，执行：识别接收到的终端发送的数据包中是否携带分流标识之前，接收SMF设备发送的加入用户面数据传输通道中的请求信息；根据所述请求信息，加入到所述用户面数据传输通道中。
可以理解，存储器可以是易失性存储器或非易失性存储器，也可包括 易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(ROM，Read Only Memory)、可编程只读存储器(PROM，Programmable Read-Only Memory)、可擦除可编程只读存储器(EPROM，Erasable Programmable Read-Only Memory)、电可擦除可编程只读存储器(EEPROM，Electrically Erasable Programmable Read-Only Memory)、磁性随机存取存储器(FRAM，ferromagnetic random access memory)、快闪存储器(Flash Memory)、磁表面存储器、光盘、或只读光盘(CD-ROM，Compact Disc Read-Only Memory)；磁表面存储器可以是磁盘存储器或磁带存储器。易失性存储器可以是随机存取存储器(RAM，Random Access Memory)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(SRAM，Static Random Access Memory)、同步静态随机存取存储器(SSRAM，Synchronous Static Random Access Memory)、动态随机存取存储器(DRAM，Dynamic Random Access Memory)、同步动态随机存取存储器(SDRAM，Synchronous Dynamic Random Access Memory)、双倍数据速率同步动态随机存取存储器(DDRSDRAM，Double Data Rate Synchronous Dynamic Random Access Memory)、增强型同步动态随机存取存储器(ESDRAM，Enhanced Synchronous Dynamic Random Access Memory)、同步连接动态随机存取存储器(SLDRAM，SyncLink Dynamic Random Access Memory)、直接内存总线随机存取存储器(DRRAM，Direct Rambus Random Access Memory)。本发明实施例描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
上述本发明实施例揭示的方法可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、DSP，或者其他可编程 逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。处理器可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本发明实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成前述方法的步骤。
在示例性实施例中，数据包的分流装置可以被一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、FPGA、通用处理器、控制器、MCU、微处理器(Microprocessor)、或其他电子元件实现，用于执行前述方法。
实施例8：
在示例性实施例中，本发明实施例还提供了一种计算机存储介质，例如包括计算机程序的存储器，上述计算机程序可由数据包的分流装置的处理器执行，以完成前述方法所述步骤。计算机存储介质可以是FRAM、ROM、PROM、EPROM、EEPROM、Flash Memory、磁表面存储器、光盘、或CD-ROM等存储器；也可以是包括上述存储器之一或任意组合的各种设备。
本发明实施例提供的计算机存储介质，其上存储有计算机程序，作为一种实施方式，当所述计算机程序由应用于终端的数据包的分流装置的处理器执行时，该计算机程序被处理器执行时实现：针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备。
在一实施例中，该计算机程序被处理器执行时实现：根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括IPv4地址或IPv6前缀地址。
在一实施例中，该计算机程序被处理器执行时实现：根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其中所述目的IP地址包括IPv4地址或IPv6前缀地址。
在一实施例中，该计算机程序被处理器执行时实现：判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
在一实施例中，该计算机程序被处理器执行时实现：根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息。
在一实施例中，该计算机程序被处理器执行时实现：接收AMF设备发送的本地分流策略。
作为另一种实施方式，当所述计算机程序由应用于UPF设备的数据包的分流装置的处理器执行时，该计算机程序被处理器执行时实现：识别接收到的终端发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，对所述数据包进行本地卸载。
在一实施例中，该计算机程序被处理器执行时实现：识别接收到的终端发送的数据包中是否携带分流标识之前，接收SMF设备发送的加入用户面数据传输通道中的请求信息；根据所述请求信息，加入到所述用户面数据传输通道中。
实施例9：
图11为本发明实施例提供的一种数据包的分流***的结构图，本发明实施例提供了一种数据包的分流***，所述***包括：应用于终端111的上述图9所述的数据包的分流装置和应用于UPF设备112的上述图10所述 的数据包的分流装置；其中，
所述终端111，配置为针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给UPF设备112；
所述UPF设备112，配置为识别所述终端111发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，对所述数据包进行本地卸载。
作为第一种实施方式，所述终端111，配置为当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；其中所述源IP地址包括IPv4地址或IPv6前缀地址；当所述判断结果为所述数据包为本地分流数据包时，确定所述数据包为本地分流数据包；当所述判断结果为所述数据包不是本地分流数据包时，确定所述数据包非本地分流数据包。
作为第二种实施方式，所述终端111，配置为当所述本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；其中所述目的IP地址包括IPv4地址或IPv6前缀地址；当所述判断结果为所述数据包为本地分流数据包时，确定所述数据包为本地分流数据包；当所述判断结果为所述数据包不是本地分流数据包时，确定所述数据包非本地分流数据包。
作为第三种实施方式，所述终端111，配置为当所述本地分流策略为根据终端的类型确定的第三分流策略时，判断自身的终端类型是否为所述第三分流策略中保存的终端的类型，获得判断结果；当所述判断结果为自身 的终端类型为所述第三分流策略中保存的终端的类型时，确定所述数据包为本地分流数据包；当所述判断结果为自身的终端类型不是所述第三分流策略中保存的终端的类型时，确定所述数据包非本地分流数据包。
作为第四种实施方式，所述终端111，配置为当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息，获得判断结果；当所述判断结果为所述特征信息为所述第四分流策略中保存的特征信息时，确定所述数据包为本地分流数据包；当所述判断结果不是所述特征信息为所述第四分流策略中保存的特征信息时，确定所述数据包非本地分流数据包。
在一实施例中，所述终端111，配置为接收PCF设备制定后通过接入和AMF设备发送的本地分流策略，并保存在本地；或接收UDM设备制定后通过AMF设备发送的本地分流策略，并保存在本地。
在一实施例中，所述UPF设备112，还配置为接收SMF设备发送的加入用户面数据传输通道中的请求信息；根据所述请求信息，加入到所述用户面数据传输通道中。
在本发明实施例的技术方案将分流的压力分散到每个终端，UPF设备不需要配置复杂的分流机制，而是将识别到携带有本地分流标识的数据包进行本地卸载，使得分流机制更加简单，并进一步提高了网络处理效率。
对于***/装置实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
本领域内的技术人员应明白，本申请的实施例可提供为方法、***、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不 限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权 利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。
工业实用性
本发明实施例的技术方案在终端判定数据包为本地分流数据包时，在数据包中携带分流标识，并将携带有分流标识的数据包发送给UPF设备，使得UPF设备识别接收的数据包中携带有分流标识时，对所述数据包进行本地卸载，将分流的压力分散到每个终端，UPF设备不需要配置复杂的分流机制，而是将识别到携带有本地分流标识的数据包进行本地卸载，使得分流机制更加简单，并进一步提高了网络处理效率。

Claims (18)

  1. 一种数据包的分流方法，应用于终端，所述方法包括：
    针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；
    当所述判断结果为所述数据包为本地分流数据包时，在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给用户面功能UPF设备。
  2. 如权利要求1所述的方法，其中，当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，所述针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包包括：
    根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括互联网协议第4版IPv4地址或互联网协议第6版IPv6前缀地址。
  3. 如权利要求1所述的方法，其中，当所述本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，所述针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包包括：
    根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其中所述目的IP地址包括IPv4地址或IPv6前缀地址。
  4. 如权利要求1所述的方法，其中，当所述本地分流策略为根据终端的类型确定的第三分流策略时，所述针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包包括：
    判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
  5. 如权利要求1所述的方法，其中，当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，所述针对待发送的数据包，及本地分 流策略，判断所述数据包是否为本地分流数据包包括：
    根据所述数据包对应的应用，获取所述应用对应的特征信息；
    判断所述特征信息是否为所述第四分流策略中保存的特征信息。
  6. 如权利要求1所述的方法，其中，还包括：
    接收接入和移动性管理功能AMF设备发送的本地分流策略。
  7. 一种数据包的分流方法，应用于用户面功能UPF设备，所述方法包括：
    识别接收到的终端发送的数据包中是否携带分流标识；
    若识别出所述数据包中携带分流标识，对所述数据包进行本地卸载。
  8. 如权利要求7所述的方法，其中，所述识别接收到的终端发送的数据包中是否携带分流标识之前，所述方法还包括：
    接收SMF设备发送的加入用户面数据传输通道中的请求信息；
    根据所述请求信息，加入到所述用户面数据传输通道中。
  9. 一种数据包的分流装置，应用于终端，所述装置包括：
    判断模块，配置为针对待发送的数据包，及本地分流策略，判断所述数据包是否为本地分流数据包，获得判断结果；当所述判断结果为所述数据包为本地分流数据包时，触发发送模块；
    发送模块，配置为在所述数据包中携带分流标识，并将携带所述分流标识的数据包通过用户面数据传输通道发送给用户面功能UPF设备。
  10. 如权利要求9所述的装置，其中，所述判断模块，配置为当所述本地分流策略为根据数据包的源IP地址确定的第一分流策略时，根据所述数据包的源IP地址，及第一分流策略，判断所述数据包是否为本地分流数据包，其中所述源IP地址包括互联网协议第4版IPv4地址或互联网协议第6版IPv6前缀地址。
  11. 如权利要求9所述的装置，其中，所述判断模块，配置为当所述 本地分流策略为根据数据包的目的IP地址确定的第二分流策略时，根据所述数据包的目的IP地址，及第二分流策略，判断所述数据包是否为本地分流数据包，其中所述目的IP地址包括IPv4地址或IPv6前缀地址。
  12. 如权利要求9所述的装置，其中，所述判断模块，配置为当所述本地分流策略为根据终端的类型确定的第三分流策略时，判断自身的终端类型是否为所述第三分流策略中保存的终端的类型。
  13. 如权利要求9所述的装置，其中，所述判断模块，配置为当所述本地分流策略为根据应用的特征信息确定的第四分流策略时，根据所述数据包对应的应用，获取所述应用对应的特征信息；判断所述特征信息是否为所述第四分流策略中保存的特征信息。
  14. 如权利要求9所述的装置，其中，所述装置还包括：
    接收模块，配置为接收接入和移动性管理功能AMF设备发送的本地分流策略。
  15. 一种数据包的分流装置，应用于用户面功能UPF设备，所述装置包括：
    识别模块，配置为识别接收到的终端发送的数据包中是否携带分流标识；若识别出所述数据包中携带分流标识，触发分流模块；
    分流模块，配置为对所述数据包进行本地卸载。
  16. 如权利要求15所述的装置，其中，所述装置还包括：
    接收模块，配置为接收SMF设备发送的加入用户面数据传输通道中的请求信息；
    加入模块，配置为根据所述请求信息，加入到所述用户面数据传输通道中。
  17. 一种数据包的分流装置，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求1至6任一项所述方法的步骤；或者，执行权利要求7或8所述方法的步骤。
  18. 一种计算机存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现权利要求1至6任一项所述方法的步骤；或者，该计算机程序被处理器执行时实现权利要求7或8所述方法的步骤。
PCT/CN2018/080091 2017-05-09 2018-03-22 一种数据包的分流方法、装置和计算机存储介质 WO2018205756A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710322244.5 2017-05-09
CN201710322244.5A CN108882305A (zh) 2017-05-09 2017-05-09 一种数据包的分流方法及装置

Publications (1)

Publication Number Publication Date
WO2018205756A1 true WO2018205756A1 (zh) 2018-11-15

Family

ID=64105031

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/080091 WO2018205756A1 (zh) 2017-05-09 2018-03-22 一种数据包的分流方法、装置和计算机存储介质

Country Status (2)

Country Link
CN (1) CN108882305A (zh)
WO (1) WO2018205756A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111556530A (zh) * 2020-04-26 2020-08-18 中国铁塔股份有限公司 一种数据处理方法及upf单元
CN115835309A (zh) * 2023-01-05 2023-03-21 阿里巴巴（中国）有限公司 本地数据的分流方法、车辆控制方法及设备
WO2023061275A1 (zh) * 2021-10-12 2023-04-20 维沃移动通信有限公司 通信授权方法、装置、网元和存储介质

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111246453B (zh) * 2018-11-28 2021-06-15 华为技术有限公司 一种数据传输方法、用户面网元及控制面网元
CN111586602B (zh) * 2019-02-19 2021-07-09 华为技术有限公司 一种策略管理的方法及装置
CN110912835B (zh) * 2019-11-08 2023-04-07 腾讯科技（深圳）有限公司 业务分流方法、装置及***
CN110933061B (zh) * 2019-11-22 2022-02-18 中国联合网络通信集团有限公司 一种通信方法及装置
CN112822724B (zh) * 2020-12-30 2023-03-21 联想未来通信科技(重庆)有限公司 一种报文转发方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102711184A (zh) * 2012-06-18 2012-10-03 西安邮电学院 异构无线网络的分流***
US20140018067A1 (en) * 2012-07-14 2014-01-16 Tekelec, Inc. Methods, systems, and computer readable media for policy-based local breakout (lbo)
CN103685052A (zh) * 2012-09-21 2014-03-26 中国电信股份有限公司 一种对网络数据流量进行分流控制的方法和***
CN106559839A (zh) * 2015-09-30 2017-04-05 中国电信股份有限公司 用于实现多网络融合的方法、装置和***
CN107517480A (zh) * 2016-06-16 2017-12-26 中兴通讯股份有限公司 会话建立的方法、装置及***

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104254107B (zh) * 2013-06-27 2018-06-05 华为技术有限公司 数据分流方法、用户设备和网络***
CN103338483B (zh) * 2013-07-24 2016-08-10 成都西加云杉科技有限公司 数据分流方法、数据分流设备及异构网络

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102711184A (zh) * 2012-06-18 2012-10-03 西安邮电学院 异构无线网络的分流***
US20140018067A1 (en) * 2012-07-14 2014-01-16 Tekelec, Inc. Methods, systems, and computer readable media for policy-based local breakout (lbo)
CN103685052A (zh) * 2012-09-21 2014-03-26 中国电信股份有限公司 一种对网络数据流量进行分流控制的方法和***
CN106559839A (zh) * 2015-09-30 2017-04-05 中国电信股份有限公司 用于实现多网络融合的方法、装置和***
CN107517480A (zh) * 2016-06-16 2017-12-26 中兴通讯股份有限公司 会话建立的方法、装置及***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE CORPORATION ET AL.: "Session Management Model with UL-CL in RAN", SA WG2 MEETING #116 S 2-163253, 8 July 2016 (2016-07-08), pages 1 - 3, XP051117859 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111556530A (zh) * 2020-04-26 2020-08-18 中国铁塔股份有限公司 一种数据处理方法及upf单元
CN111556530B (zh) * 2020-04-26 2023-07-21 中国铁塔股份有限公司 一种数据处理方法及upf单元
WO2023061275A1 (zh) * 2021-10-12 2023-04-20 维沃移动通信有限公司 通信授权方法、装置、网元和存储介质
CN115835309A (zh) * 2023-01-05 2023-03-21 阿里巴巴（中国）有限公司 本地数据的分流方法、车辆控制方法及设备

Also Published As

Publication number Publication date
CN108882305A (zh) 2018-11-23

Similar Documents

Publication Publication Date Title
WO2018205756A1 (zh) 一种数据包的分流方法、装置和计算机存储介质
US11950155B2 (en) Session context conversion
US11758002B2 (en) Session processing method, apparatus, and system
US20220330361A1 (en) Method for establishing connection and obtaining relay service code and communications apparatus
WO2018137489A1 (zh) 一种策略控制方法、装置、***及存储介质
WO2018214638A1 (zh) 用户面功能实体重选的策略控制方法、设备及存储介质
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
US20190208572A1 (en) Method for dynamically creating local packet data network, apparatus, and system
BR112020016328A2 (pt) Método de comunicação, aparelho de comunicações, sistema de comunicações e um meio legível por computador
CN111417111B (zh) 一种数据处理方法和网络设备
US20120069797A1 (en) Method for a communication node with a plurality of communication interfaces to notify dynamic path setup and associates apparatus thereof
WO2019191927A1 (en) Methods and system for offloading data traffic
JP2019536342A (ja) 無線デバイスをハンドオーバするシステム及び方法
US20190260811A1 (en) Packet data unit session establishment method and network entity performing the same
EP3687259B1 (en) Communication method and device
WO2019196680A1 (zh) 通信方法和通信装置
US11792641B2 (en) UE capability transfer and storage
WO2018157551A1 (zh) 数据传输的方法与装置
WO2021068706A1 (zh) 一种信息处理方法和相关网络设备
WO2018195971A1 (zh) 获取上下文配置信息的方法、终端设备和接入网设备
JP7494262B2 (ja) セッションコンテキスト変換
WO2023246614A1 (zh) 一种通信方法、装置、通信设备和计算机存储介质
WO2021120058A1 (zh) 一种基于本地分流的通信方法、通信设备及存储介质
CN114630355A (zh) 基于核心网的故障恢复方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18798039

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM1205A DATED 18/06/2020 )

122 Ep: pct application non-entry in european phase

Ref document number: 18798039

Country of ref document: EP

Kind code of ref document: A1