CN111565404A

CN111565404A - Data distribution method and device

Info

Publication number: CN111565404A
Application number: CN202010296706.2A
Authority: CN
Inventors: 吕华章; 张力方; 朱常波; 冯毅
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2020-04-15
Filing date: 2020-04-15
Publication date: 2020-08-21
Anticipated expiration: 2040-04-15
Also published as: CN111565404B

Abstract

The embodiment of the application provides a data distribution method and device, relates to the technical field of communication, simplifies the interaction process of an MEC server and a core network, and can meet the requirements of low time delay and high reliability of edge calculation. The method is applied to a first network device, the first network device and a multi-access edge computing MEC server are in the same network level, and the data distribution method comprises the following steps: acquiring an MEC request generated by an MEC server; the MEC request includes an identification of a target session that needs to be modified; the MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element. And sending an MEC request to a Session Management Function (SMF) network element. The embodiment of the application is applied to data distribution.

Description

Data distribution method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a data distribution method and device.

Background

Multi-access edge computing (MEC) is an open platform that can merge network, computing, and storage application core capabilities at the network edge. The method can meet the key requirements of the industry digitization in various aspects of the application field, particularly has higher time delay requirements and generally corresponds to low-time delay services.

At present, MEC has been developed to evolve into one of the important technologies of the fifth generation mobile communication technology (5th-generation, 5G). In the 5G system, the MEC is embodied by an Application Function (AF) network element. In a scenario that a suitable User Plane Function (UPF) network element needs to be selected for the applied traffic data to forward and receive the user plane data, referring to fig. 1, an a1 and an AF (101) network element generate an MEC request according to the applied traffic data, and then send the MEC request to a network capability exposure function (NEF) (102) network element. A2, NEF (102) network element generates strategy request according to MEC request, then sends the strategy request to strategy function (PCF) (103) network element. Then, a3, PCF (103) network element generates target policy according to policy request, after that, PCF (103) network element sends session management modification request containing the target policy to Session Management Function (SMF) (104) network element. And finally, the A4 and SMF (104) network element realizes the reconfiguration of the UPF (105) network element of the user plane for the relevant session according to the target strategy in the session management modification request, selects the target UPF network element, then the target UPF network element is responsible for the modification of the relevant session, and the forwarding and receiving of the applied traffic data are carried out, thus completing the shunting of the applied traffic data.

However, in this scenario, the NEF network element is located at the core network side, the AF network element is located at the local network side, and the MEC request sent by the AF network element needs to be transmitted to the NEF network element at the core network side before the MEC request is responded to, which may cause higher MEC request response delay. Secondly, the NEF network element needs to interact with the PCF to form a target policy after receiving the MEC request, and then can issue the target policy to the SMF.

Disclosure of Invention

Embodiments of the present application provide a data offloading method and apparatus, which simplify an interaction flow between an MEC server and a core network, and can meet requirements of edge computation on low latency and high reliability.

In a first aspect, the present application provides a data offloading method, which is applied to a first network device, where the first network device and a multi-access edge computing MEC server are in the same network level. The method comprises the following steps: the first network device acquires an MEC request generated by an MEC server. After that, the first network device sends the MEC request to a session management function, SMF, network element. Wherein the MEC request includes an identification of the target session that needs to be modified. The MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element.

In the above scheme, after acquiring the MEC request generated by the MEC server, the first network device directly sends the MEC request to the SMF network element on the core network side, and requests the SMF network element to perform user plane reconfiguration on the UPF network element, so as to achieve the purpose of data offloading. Therefore, the process that the NEF network element interacts with the PCF network element to form the target strategy after receiving the MEC request and then issues the target strategy to the SMF network element is reduced, and the time delay of the whole process is reduced. And because the process of converting the MEC request into the target strategy is reduced, the error in the process of converting the MEC request into the target strategy can be avoided, and the reliability of the whole process can be improved. In conclusion, the method and the device can meet the requirement of high reliability of low-delay and medium-delay in edge calculation.

In a second aspect, the present application provides a data offloading device, configured to a first network device, where the first network device and an MEC server are in the same network layer. The data shunting device comprises: and the acquisition module is used for acquiring the MEC request generated by the MEC server. And the sending module is used for sending the MEC request to the SMF network element. Wherein the MEC request comprises an identification of a target session that needs to be modified; the MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element.

In a third aspect, the present application provides a data offloading device, configured to a first network device, where the first network device and an MEC server are in the same network layer. The data offloading device comprises a processor, and when the data offloading device is operated, the processor executes computer-executable instructions to cause the data offloading device to perform the data offloading method according to the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, which includes instructions that, when executed on a computer, cause the computer to perform the data offloading method according to the first aspect.

In a fifth aspect, a computer program product is provided, which comprises instruction codes for executing the data offloading method according to the first aspect.

It is to be understood that any one of the data offloading device, the computer readable storage medium, or the computer program product provided above is used for executing the method provided above, and therefore, the beneficial effects achieved by the data offloading device may refer to the beneficial effects of the method above and the corresponding solutions in the following detailed description, and are not repeated herein.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a 5G communication system in the prior art;

fig. 2 is a schematic structural diagram of a 5G communication system according to an embodiment of the present application;

fig. 3 is a schematic hardware structure diagram of a data offloading device according to an embodiment of the present disclosure;

fig. 4 is a schematic flowchart of a data offloading method according to an embodiment of the present application;

fig. 5 is a schematic user plane structure diagram of a 5G communication system according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a data offloading device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified.

The MEC is an open platform for fusing application core capabilities of network, computing, storage and the like at the network edge side close to a human, object or data source. The intelligent edge service system can provide edge intelligent service for business nearby, and meets the key requirements of industry digitization on aspects of agile connection, real-time business, data optimization, application intelligence, safety, privacy protection and the like. The platform provided by the MEC provides an open-source, open and friendly deployment environment for the application, and the application can also utilize various platform capabilities provided by the MEC to provide better service for users to the maximum extent. At present, MEC has been developed as one of the important technologies evolving into 5G.

In a 5G communication system, network entities are redefined in the form of Network Functions (NFs). Each NF can be used as an independent network element externally to provide functions for services. And each NF can be mutually called, thereby realizing the transformation from the traditional rigid network, such as network element fixing function, fixed connection between network elements, solidified signaling interaction and the like, to the flexible network based on the service.

Referring to fig. 1, the 5G communication system includes an authentication service function (AUSF), unified data management (UDR), a network element data repository function (nfretrieval function, NRF), an Access and Mobility management function (AMF), a terminal device (user equipment, UE), an Access network (RAN), a NEF, a PCF, an SMF, an UPF, a Local Area Data Network (LADN), a MEC (af), and an Application (APP) corresponding to the MEC. The local UPF, LADN, MEC (AF), and the Application (APP) corresponding to the MEC are located at the local network side.

In the 5G communication system shown in fig. 1, the functions may establish a connection through a next generation Network (NG) interface to implement communication, for example: the UE may establish a control plane signaling connection with the AMF over N interface 1 (abbreviated N1). The RAN may establish a user plane data connection with the UPF over the N interface 3 (abbreviated N3). The RAN may establish a control plane signalling connection with the AMF over N interface 2 (abbreviated N2). The UPF may establish a control plane signaling connection with the SMF over N interface 4 (abbreviated N4). The UPF may interact with the LADN via an N-interface 6 (abbreviated N6).

The NEF may open the capability through a service based serial peripheral interface (SBI). Such as: the NEF may interact with the AMF through an N interface AMF (called Namf for short), thereby implementing the opening of monitoring capabilities including connection loss, reachability, location information, communication failure, number of UEs in an area, and the like. The NEF may interact with the UDM through an N interface UDM (Nudm for short), thereby implementing capability openness such as roaming state and subscription information change. The NEF can interact with PCF through N interface PCF (Npcf for short), to realize the opening of policy control and charging capability.

In addition, the UE, (R) AN, UPF, and LADN are generally referred to as data plane network functions and entities, and data traffic of the user may be transmitted through a packet data unit Session (PDU Session) established between the UE and the LADN. The transmission of data traffic will go through two network functional entities, the (R) AN and the UPF. The other parts are called control plane network functions and entities and are mainly responsible for functions such as authentication and authorization, registration management, session management, mobility management, policy control and the like, so that reliable and stable transmission of user layer traffic is realized. The user plane is used for carrying service data, and the control plane is used for carrying signaling messages.

In the above 5G communication system, the MEC is embodied by an AF network element. In a scene that a proper UPF network element needs to be selected for the applied traffic data to forward and receive the user plane data. The data splitting method in the prior art refers to steps a1-a4 in fig. 1.

A1, the AF network element generates an MEC request according to the applied traffic data, and then sends the MEC request to the NEF network element.

A2, NEF network element generates strategy request according to MEC request, then sends the strategy request to PCF network element.

A3, PCF network element generates target strategy according to strategy request, then sends session management modification request containing the target strategy to SMF network element.

A4, SMF network element according to the target strategy in the session management modification request, realizing the reconfiguration of user plane UPF network element for the related session, and selecting the target UPF network element. And then the target UPF network element is responsible for modifying the related session, and forwarding and receiving the applied traffic data to complete the shunting of the applied traffic data.

However, in the scenario of the data offloading method, since the NEF network element is located on the core network side, the AF network element is located on the local network side. Therefore, the MEC request sent by the AF network element needs to be transmitted to the NEF network element on the core network side before the MEC request can be responded, which causes a higher delay for responding to the MEC request. Secondly, the NEF network element needs to interact with the PCF to form a target policy after receiving the MEC request, and then can issue the target policy to the SMF.

Therefore, in view of the above problem, the present application provides a 5G communication system, as shown in fig. 2. The system comprises: AUSF, UDR, NRF, AMF, UE, RAN, NEF, PCF, SMF, UPF, LADN, first network device, second network device, MEC (af), and an Application (APP) corresponding to MEC. The local UPF, the LADN, the first network device, the second network device, the MEC (af), and an Application (APP) corresponding to the MEC are located in the same network level, that is, the local network side.

Moreover, the present application provides a data offloading method and a data offloading device based on the 5G communication system shown in fig. 2, and the data offloading method and the data offloading device are applied to a first network device, and the first network device and the MEC server are in the same network level. The data distribution method comprises steps B1-B5 in FIG. 2.

And B1, the first network equipment acquires the MEC request generated by the MEC server. B2, the first network device sends the MEC request to the SMF network element. B3, the SMF network element distributes a target UPF network element for the target session corresponding to the MEC request, and shunts the data corresponding to the target session to the target UPF network element. And B4, the first network equipment stores the content carried in the MEC request to the second network equipment. And B5, synchronizing the content carried in the MEC request to the UDR of the core network by the second network equipment. According to the method and the device, the flows that the NEF network element interacts with the PCF network element to form the target strategy after receiving the MEC request and then issues the target strategy to the SMF network element are reduced, and the time delay of the whole flow can be reduced.

In addition, the data offloading device provided by the present application has components shown in fig. 3 when being implemented specifically. Fig. 3 is a data offloading device provided in an embodiment of the present application, and the data offloading device may include a processor 302, where the processor 302 is configured to execute an application program code, so as to implement a data offloading method in the present application.

The processor 302 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

As shown in fig. 3, the data splitting apparatus may further include a memory 303. The memory 303 is used for storing application program codes for executing the scheme of the application, and the processor 302 is used for controlling the execution.

The memory 303 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 303 may be separate and coupled to the processor 302 via a bus. The memory 303 may also be integrated with the processor 302.

As shown in fig. 3, the data offloading device may further include a communication interface 301, wherein the communication interface 301, the processor 302, and the memory 303 may be coupled to each other, for example, via a bus 304. The communication interface 301 is used for information interaction with other devices, for example, to support information interaction of the data offloading device with other devices, for example, to obtain data from other devices or send data to other devices.

It is noted that the device structure shown in fig. 3 does not constitute a limitation of the data splitting apparatus, and the data splitting apparatus may include more or less components than those shown in fig. 3, or combine some components, or arrange different components, in addition to the components shown in fig. 3.

The data offloading method provided by the embodiment of the present application is described below with reference to the 5G communication system shown in fig. 2 and the data offloading device shown in fig. 3.

Fig. 4 is a schematic flow chart of a data offloading method according to an embodiment of the present application. Referring to fig. 4, the data splitting method includes the following steps.

401. The first network device acquires an MEC request generated by an MEC server.

Wherein the MEC request includes an identification of the target session that needs to be modified. The MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element.

Specifically, the first network device may be referred to as a proxy device (Agent), and the application designs a signaling for transmitting the MEC request, for example, the signaling Agent _ trafficinfiliuence _ Update is used to transmit the MEC request.

Optionally, the MEC request further includes an identifier of the MEC request, an identifier of the MEC server, a network type of the target session, and an access type of the target session. The first network device stores the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session to the second network device, and is used for instructing the second network device to synchronize the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session to a unified data management (UDR) of a core network. The network type of the target session includes internet protocol version 4 (IPV 4) and internet protocol version 6 (IPV 6). The access type of the target session includes new, deleted and modified.

Specifically, the second network device may be a memory independent from the first network device, or may be a module capable of storing data on the first network device. But the second network device, as a subset of the UDR of the core network, is able to synchronize data to the UDR of the core network, wherein the process of synchronizing data may be performed in an idle state in order not to occupy network resources when the network is in a connected state.

Optionally, the MEC request further includes a General Public Subscription Identifier (GPSI), N6 interface traffic routing information, a new forking rule corresponding to the target session, and a data key. The data key refers to an internal identifier of the MEC server in signaling processing, that is, an identifier of the MEC server used by the MEC server for internal access control of the database, and may be an Identity (ID) of the MEC server.

In addition, in the data offloading process, if slice selection is involved, the MEC request should also include slice-related identification information, for example, network slice selection assistance information (S-NSSAI).

If the MEC request includes the original offload rule and information of the target session, the MEC request should also include traffic filter information, traffic rule information, and an offload Data Network Name (DNN).

Of course, when other parameters are included in the MEC request, the first network device should also store the other parameters to the second network device, so that the second network device synchronizes the relevant data to the UDR of the core network.

402. The first network equipment sends an MEC request to a Session Management Function (SMF) network element.

Optionally, before the first network device sends the MEC request to the SMF network element, the first network device needs to perform validity verification on the MEC request. For example, the MEC request includes an ID registered by the MEC server, and the first network device compares the ID registered by the MEC server with the related certificate to determine the validity of the MEC request.

And after the MEC request of the first network equipment is legal, sending the MEC request to the SMF network element.

Specifically, the first network device may send the MEC request to the SMF network element in the form of signaling. For example, a signaling Agent _ SMPolicyControl _ Update is designed to send a MEC request to an SMF network element. And requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element.

For example, fig. 5 provides a user plane structure of a 5G communication system. The user plane structure of the 5G communication system comprises an SMF network element and a UPF network element on the core network side. And a Data Network (DN) and a UPF anchor point on the local network side. The SMF establishes a control plane signaling connection with the UPF through an N interface 4 (N4 for short), the UPF establishes a control plane signaling connection with the UPF anchor point through an N interface 9 (N9 for short), and the UPF anchor point interacts user plane data with the DN through an N interface 6 (N6 for short).

The MEC request is used to request the SMF network element to allocate a target UPF network element for the target session, and to shunt data corresponding to the target session to the target UPF network element. The target UPF network element may be reconfigured according to the access type of the target session in the MEC request, for example, an uplink classifier (UL CL) is used to complete reconfiguration of the target UPF network element, where the UL CL can forward a packet meeting the service filtering rule to a specified path (i.e., the UPF anchor point and its corresponding DN in fig. 5). Specifically, the insertion and deletion of UL CL is performed by the SMF network element to the UPF through the N4 interface. Wherein the UPF network element corresponds to the UPF in fig. 5, and the target UPF network element corresponds to the UPF anchor point in fig. 5. For another example, the reconfiguration of the target UPF network element may also be completed by increasing the user plane branch point.

Illustratively, when the access type of the target session is modified, the SMF network element indicates that the configuration update is performed to a target UPF network element (UPF anchor) of a certain DN in the MEC request.

Optionally, the first network device replies an MEC request response to the MEC server.

In addition, the MEC request generated by the MEC server is directly transmitted to the first network device at the same network level as the MEC server. Then, an MEC request response is returned by the first network device for the MEC server. The method and the device avoid the problem of high MEC request response time delay caused by the fact that the MEC request sent by the AF network element can be responded by the MEC request after the MEC request needs to be transmitted to the NEF network element at the core network side. The latency of the MEC request response is reduced.

Referring to fig. 6, the present application provides a data offloading device, configured to be used for a first network device, where the first network device and an MEC server are in the same network layer, and the data offloading device includes: an acquisition module 61, a sending module 62 and a storage module 63.

The obtaining module 61 is configured to obtain an MEC request generated by an MEC server. For example, in conjunction with fig. 4, the obtaining module 61 may be configured to perform step 401. The MEC request includes an identification of a target session that needs to be modified; the MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element. A sending module 62, configured to send an MEC request to a session management function SMF network element. For example, in conjunction with fig. 4, the sending module 62 may be configured to perform step 402.

Optionally, the MEC request further includes an identifier of the MEC request, an identifier of the MEC server, a network type of the target session, and an access type of the target session; the data distribution device further comprises: a storage module 63, configured to store the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session to the second network device, and instruct the second network device to synchronize the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session to a unified data management UDR of the core network; the network type of the target session includes IPV4 and IPV 6; the access type of the target session includes new, deleted and modified.

Optionally, the sending module 62 is further configured to reply an MEC request response to the MEC server.

In addition, the present application also provides a computer-readable storage medium (or media) including instructions that, when executed, perform the operations of the data offloading method in the above embodiments. Additionally, a computer program product is also provided, comprising the above-described computer-readable storage medium (or media).

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

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art would appreciate that the various illustrative modules, elements, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative, e.g., multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data distribution method is characterized in that the method is applied to a first network device, and the first network device and a multi-access edge computing MEC server are in the same network level; the data distribution method comprises the following steps:

acquiring an MEC request generated by the MEC server; the MEC request includes an identification of a target session that needs to be modified; the MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element;

and sending the MEC request to a Session Management Function (SMF) network element.

2. The data offloading method of claim 1, wherein the MEC request further comprises an identification of the MEC request, an identification of the MEC server, a network type of the target session, and an access type of the target session; the data distribution method further comprises the following steps:

storing the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session to a second network device, for instructing the second network device to synchronize the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session into a unified data management UDR of a core network; the network type of the target session comprises IPV4 and IPV 6; the access type of the target session comprises addition, deletion and modification.

3. The data offloading method according to claim 1, wherein after obtaining the MEC request generated by the MEC server, the data offloading method further includes:

and replying an MEC request response to the MEC server.

4. The data distribution device is used for a first network device, wherein the first network device and an MEC server are in the same network level; the data distribution device comprises:

an obtaining module, configured to obtain an MEC request generated by the MEC server; the MEC request includes an identification of a target session that needs to be modified; the MEC request is used for requesting the SMF network element to distribute a target UPF network element for the target session, and shunting data corresponding to the target session to the target UPF network element;

and the sending module is used for sending the MEC request to a Session Management Function (SMF) network element.

5. The data offloading device of claim 4, wherein the MEC request further comprises an identification of the MEC request, an identification of the MEC server, a network type of the target session, an access type of the target session; the data distribution device further comprises:

a storage module, configured to store the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session to a second network device, and instruct the second network device to synchronize the identifier of the target session, the identifier of the MEC request, the identifier of the MEC server, the network type of the target session, and the access type of the target session into a unified data management UDR of a core network; the network type of the target session comprises IPV4 and IPV 6; the access type of the target session comprises addition, deletion and modification.

6. The data splitting device of claim 4,

the sending module is further configured to reply an MEC request response to the MEC server.

7. The data distribution device is used for a first network device, wherein the first network device and an MEC server are in the same network level; the data distribution device comprises a processor, and when the data distribution device runs, the processor executes computer-executable instructions to cause the data distribution device to execute the data distribution method according to any one of claims 1 to 3.

8. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the data offloading method of any of claims 1-3.

9. A computer program product, characterized in that the computer program product comprises instruction code for performing the data offloading method of any of claims 1-3.