CN114448913B

CN114448913B - Network communication method and device

Info

Publication number: CN114448913B
Application number: CN202011193949.XA
Authority: CN
Inventors: 于小博; 白常明
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-10-30
Filing date: 2020-10-30
Publication date: 2025-01-17
Anticipated expiration: 2040-10-30
Also published as: CN114448913A

Abstract

The embodiment of the invention provides a network communication method and device, wherein the method comprises the steps that a first network entity sends a first request message to a third network entity through a second network entity, the first request message comprises target distribution information, the target distribution information comprises first identification information and second identification information, the first request message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target distribution information, and the first network entity receives a first reply message aiming at the first request message from the third network entity through the second network entity. According to the embodiment of the invention, the feedback of the shunt strategy is realized, so that the data can be shunted according to the latest shunt strategy, and the network transmission efficiency is improved.

Description

Network communication method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for network communications.

Background

Edge computing is an evolution of cloud computing that, unlike centralized data centers, makes network communication logic closer to consumers by deploying decentralized data centers at the network edge.

Edge computation is considered to be one of the important means to meet key performance indicators (KeyPerformance Indicator, KPI) in 5G network demands, particularly playing a major role in terms of low latency and bandwidth efficiency. Since edge computation opens up network edges for applications and services, including those from third parties, edge computation in telecommunications networks not only becomes a technology facilitator of meeting 5G performance metrics, but also plays an important role in the transformation of the telecommunications field, which is being transformed into a multi-functional service platform for industry and other specific customer groups.

However, in a 5G network applying edge computing, the offloading policy may change, and if the offloading policy cannot be issued and updated in feedback in time, the transmission efficiency of the network will be affected.

Disclosure of Invention

In view of the above, a method and apparatus for providing a network communication that overcomes or at least partially solves the above-mentioned problems is presented, comprising:

a method of network communication, applied to a first network entity, comprising:

the first network entity sends a first request message to a third network entity through a second network entity, wherein the first request message comprises target distribution information, the target distribution information comprises first identification information and second identification information, and the first request message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target distribution information;

the first network entity receives a first reply message to the first request message from the third network entity through the second network entity.

A method of network communication, applied to a second network entity, comprising:

The second network entity receives a first request message from a first network entity and sends the first request message to a third network entity, wherein the first request message comprises target offloading information, the target offloading information comprises first identification information and second identification information, and the first request message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

The second network entity receives a first reply message for the first request message from the third network entity and sends the first reply message to the first network entity.

A method of network communication, applied to a third network entity, comprising:

The third network entity receives a first request message from a first network entity through a second network entity, wherein the first request message comprises target distribution information, the target distribution information comprises first identification information and second identification information, and the first request message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target distribution information;

The third network entity sends a first reply message for the first request message to the first network entity through the second network entity.

The first network entity sends a third request message to a fifth network entity through a second network entity, wherein the third request message comprises target distribution information, the target distribution information comprises first identification information and second identification information, the third request message is used for enabling the fifth network entity to create or update distribution information of the first network entity according to the target distribution information, and the target distribution information is used for enabling the third network entity to select a fourth network entity corresponding to a target session;

the first network entity receives a third reply message to the third request message from the fifth network entity through the second network entity.

the second network entity receives a third request message from the first network entity and sends the third request message to a fifth network entity, wherein the third request message comprises target offloading information, the target offloading information comprises first identification information and second identification information, the third request message is used for enabling the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is used for enabling the third network entity to select a fourth network entity corresponding to a target session;

the second network entity receives a third reply message for the third request message from the fifth network entity and sends the third reply message to the first network entity.

A method of network communication, applied to a fifth network entity, comprising:

The fifth network entity receives a third request message from the first network entity through the second network entity, wherein the third request message comprises target distribution information, the target distribution information comprises first identification information and second identification information, the third request message is used for enabling the fifth network entity to create or update distribution information of the first network entity according to the target distribution information, and the target distribution information is used for enabling the third network entity to select a fourth network entity corresponding to a target session;

The fifth network entity sends a third reply message for the third request message to the first network entity through the second network entity.

The third network entity sends a fourth request message to a fifth network entity, wherein the fourth request message is used for acquiring the distribution information of the first network entity from the fifth network entity;

the third network entity receives a fourth reply message for the fourth request message from the fifth network entity, wherein the fourth reply message comprises target offloading information, the target offloading information comprises first identification information and second identification information, and the fourth reply message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information.

An apparatus for network communication, applied to a first network entity, comprising:

A first request message sending module, configured to send a first request message to a third network entity through a second network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

A first reply message receiving module for receiving, by the second network entity, a first reply message for the first request message from the third network entity.

An apparatus for network communication, applied to a second network entity, comprising:

A first request message forwarding module, configured to receive a first request message from a first network entity, and send the first request message to a third network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

and the first reply message forwarding module is used for receiving a first reply message aiming at the first request message from the third network entity and sending the first reply message to the first network entity.

An apparatus for network communication, applied to a third network entity, comprising:

A first request message receiving module, configured to receive a first request message from a first network entity through a second network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

and the first reply message sending module is used for sending a first reply message aiming at the first request message to the first network entity through the second network entity.

a third request message sending module, configured to send a third request message to a fifth network entity through a second network entity, where the third request message includes target offloading information, where the target offloading information includes first identification information and second identification information, the third request message is configured to enable the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is configured to enable the third network entity to select a fourth network entity corresponding to a target session;

a third reply message receiving module, configured to receive, by the second network entity, a third reply message for the third request message from the fifth network entity.

A third request message forwarding module, configured to receive a third request message from a first network entity and send the third request message to a fifth network entity, where the third request message includes target offload information, the target offload information includes first identification information and second identification information, the third request message is configured to enable the fifth network entity to create or update offload information of the first network entity according to the target offload information, and the target offload information is configured to enable the third network entity to select a fourth network entity corresponding to a target session;

And a third reply message forwarding module, configured to receive a third reply message for the third request message from the fifth network entity, and send the third reply message to the first network entity.

An apparatus for network communication, applied to a fifth network entity, comprising:

a third request message receiving module, configured to receive, by using a second network entity, a third request message from a first network entity, where the third request message includes target offloading information, where the target offloading information includes first identification information and second identification information, the third request message is configured to cause the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is configured to cause the third network entity to select a fourth network entity corresponding to a target session;

and a third reply message sending module, configured to send, to the first network entity, a third reply message for the third request message through the second network entity.

A fourth request message sending module, configured to send a fourth request message to a fifth network entity, where the fourth request message is used to obtain offload information of the first network entity from the fifth network entity;

A fourth reply message receiving module, configured to receive a fourth reply message for the fourth request message from the fifth network entity, where the fourth reply message includes target offloading information, the target offloading information includes first identification information and second identification information, and the fourth reply message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information.

The embodiment of the invention has the following advantages:

In the embodiment of the invention, the first network entity sends the first request message to the third network entity through the second network entity, the first request message comprises the target distribution information, the target distribution information comprises the first identification information and the second identification information, the first request message is used for enabling the third network entity to select the fourth network entity corresponding to the target session according to the target distribution information, the first network entity receives the first reply message aiming at the first request message from the third network entity through the second network entity, the feedback of the distribution strategy is realized, and further the distribution data can be distributed according to the latest distribution strategy, and the network transmission efficiency is improved.

Drawings

In order to more clearly illustrate the technical solutions of the present invention, the drawings that are needed in the description of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.

FIG. 1a is a schematic diagram of a mobile edge computing system according to an embodiment of the present invention;

FIG. 1b is a schematic diagram of a mobile edge computing system and 5G core network combined architecture according to an embodiment of the present invention;

FIG. 2 is a flow chart of steps of a method for network communication according to an embodiment of the present invention;

FIG. 3 is a flow chart of steps of another method for network communication according to an embodiment of the present invention;

FIG. 4 is a flow chart of steps of another method for network communication according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an example of network communication according to an embodiment of the present invention;

FIG. 6 is a flow chart of steps of another method for network communication according to an embodiment of the present invention;

FIG. 7 is a flow chart of steps of another method for network communication according to an embodiment of the present invention;

FIG. 8 is a flow chart of steps of another method for network communication according to an embodiment of the present invention;

FIG. 9 is a flow chart of steps of another method for network communication according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of another example of network communication provided by an embodiment of the present invention;

FIG. 11 is a block diagram illustrating an apparatus for network communication according to an embodiment of the present invention;

FIG. 12 is a block diagram of another network communication device according to an embodiment of the present invention;

FIG. 13 is a block diagram illustrating an alternative network communication device according to one embodiment of the present invention;

FIG. 14 is a block diagram illustrating an alternative network communication device according to one embodiment of the present invention;

FIG. 15 is a block diagram illustrating an alternative network communication device according to one embodiment of the present invention;

FIG. 16 is a block diagram illustrating an alternative network communication device according to one embodiment of the present invention;

Fig. 17 is a block diagram of another network communication device according to an embodiment of the present invention.

Detailed Description

In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In a Mobile edge computing (MEC, mobile Edge Computing) system, such as in fig. 1a, the underlying network layer may employ a 3G network, a Local network (Local network), and other External networks (External networks), the intermediate host layer may include a Mobile edge host (Mobile edge host) and a Mobile edge host management function (Mobile edge host LEVEL MANAGEMENT), the Mobile edge host may include a Mobile edge platform (Mobile edge platform), a virtualization architecture (Virtualization), such as network function virtualization infrastructure solutions (NFVI, network Functions Virtualization Infrastructure), and a Mobile edge application (Mobile edge application), and the upper Mobile edge system layer may include a Mobile edge system management function (Mobile EDGE SYSTEM LEVEL MANAGEMENT) and a user terminal, among others.

In the case of a mobile edge computing system in combination with a 5G core network, as in fig. 1b, the mobile edge computing system has a system layer (SYSTEM LEVEL) and a distributed host layer (Distributed Host Level), the system layer may include a mobile edge computing coordinator (MEC Orchestrator), the distributed host layer may include a MEC Platform (MEC Platform), MEC Platform management (MEC Platform Management), and the mobile edge host may include an application and virtualization infrastructure (Virtualization Infrastructure).

Since the mobile edge computing system is combined with the 5G core network, the instantiated mobile edge computing coordinator may be used as an application Function (AF, applicationFunction) in the 5G core network, and the mobile edge host may be used as a Data Network (DN) in the 5G core network, the data network being communicatively connected to a User Plane Function (UPF).

In particular, the user plane functions may be connected to the session management function (SMF, session Management Function) through an N4 interface, and may be communicatively connected to the user terminal through a radio access Network (RAN, radioAccess Network), the radio access Network and the user terminal may be communicatively connected to the access and mobility management function (AMF, access andMobile ManagementFunction), the access and mobility management function, the session management function, the Network opening function (NEF, network Exposure Function), the policy control function (PCF, policy Control Function), the unified data management (UDM, unifiedDataManagement), the Network storage function (NRF, network Repository Function), the Network slice selection function (NSSF, network Slice Selection Function), the authentication server function (AUSF, authentication ServerFunction), and may be communicatively connected to the mobile edge computing system through the access and mobility management function (AMF, ACCESS AND Mobile ManagementFunction).

However, in a 5G network applying edge computing, the offloading policy may change, and if feedback update cannot be performed on the offloading policy in time, the transmission efficiency of the network will be affected.

In the embodiment of the invention, the application function can forward the distribution strategy information to the session management function through the network opening function or the strategy control function so as to influence the user plane function to select/reselect Traffic or session route, and the 5G core network distributes different data to different user plane functions by introducing the distribution mechanism so as to process by adopting the mobile edge computing system.

The following describes embodiments of the present invention in detail:

Wherein the first network entity may be a network entity for an Application Function (AF).

The second network entity may be a network entity for a network open function (NEF) or a network entity for a Policy Control Function (PCF).

In an example, the second network entity may also be a network entity for a packet traffic description function (PFDF, packetFlow Description Function), the PFDF may also be a sub-function in the NEF.

The third network entity may be a network entity of a Session Management Function (SMF).

The fourth network entity may be a network entity for a User Plane Function (UPF).

The fifth network entity may be a network entity for a universal data store (UDR).

The sixth network entity may be a network entity for access and mobility management functions (AMFs),

Referring to fig. 2, a flowchart illustrating steps of a method for network communication according to an embodiment of the present invention may be applied to a first network entity, where the first network entity may be communicatively connected to a second network entity, where the second network entity may be communicatively connected to a third network entity, where the third network entity may be communicatively connected to a plurality of fourth network entities, where each fourth network entity may correspond to one or more mobile edge computing systems, otherwise known as an edge computing platform or edge computing node.

Specifically, the method comprises the following steps:

Step 201, the first network entity sends a first request message to a third network entity through a second network entity, the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

The first identification information may be a data network access identification (DNAI, DN Access Identifier), and the second identification information may be identification information of the data network.

In particular, the identification information of the data network may be a data network name (DNN, datanetwork name), which may be used to uniquely identify one data network. In addition, the data network identifier may also be a fully qualified domain name (Fully Qualified Domain Name, FQDN) or an IP address of a DN, etc.

Alternatively, DNAI may not be included in the first request message, and accordingly, the AF may send quality of service (Quality ofService, qoS) parameters that the application needs to satisfy, such as a delay requirement, a throughput requirement, and the like, to the SMF through the NEF, and the SMF may select a corresponding UPF according to the data network access identifier and the corresponding QoS parameter. Alternatively, the SMF may decide on a preferred UPF selection based on interactions with the network data analysis network elements (Network DataAnalytics Function, NWDAF) and based on feedback of NWDAF. Optionally, the first request message further includes an identifier for changing the UPF, where the identifier is mainly used to trigger the SMF to change the UPF of the connection making DN according to the QoS parameter carried in the first request message.

As an example, the target split information may also include at least one of:

Data flow description information (Packet flow description), application identification information (Application ID), terminal location range information (Location ofthe subscriber), network slice identification information (S-NSSAI, singleNetwork Slice SelectionAssistance Information).

In the case of a mobile edge computing system in combination with a 5G core network, a first network entity at the mobile edge computing system may generate target offload information, e.g., the target offload information may be offload information generated according to offload policy requirements required for 5G edge applications.

After generating the target distribution information, the first network entity generates a first request message according to the distribution information, and can send the first request message to the second network entity, the second network entity can send the first request message to the third network entity, and after receiving the first request message, the third network entity can select a corresponding fourth network entity for the target session according to the target distribution information in the first request message, so that the corresponding session flow can be sent to a Data Network (DN) where the formulated application is located through the fourth network entity.

Specifically, the third network entity may generate a second request message according to the target offload information, where the second request message includes identification information of the user terminal, second identification information, and optionally an application identifier, and further may send the second request message to the fourth network entity, and the fourth network entity may update, according to the second request message, a route of a session corresponding to the application identifier, and may generate a second reply message for the second request message, and send the second reply message to the third network entity, and the third network entity may send the second reply message to the first network entity. The routing specifically refers to which fourth network entity the PDU session selects to send onto the data network where the specified application is located.

In some scenarios, the user terminal may be in a moving state, and the third network entity may detect the location of the user terminal in real time through the capability of the sixth network entity, and when the user terminal reaches the location requirement of the edge area or leaves the edge area, may trigger the user terminal to transit from the central network (CENTRAL DN) to the Local network (Local DN) or the Local network to transit to the central network. Optionally, the third network entity may also detect, through the terminal's own capability (e.g. GPS), that the geographical location information is sent to the third network entity through a service request procedure or a message of PDU session establishment or modification procedure.

Based on this, the first request message may further include terminal location range information, where the first request message may be used to enable the third network entity to obtain terminal location information of the user terminal through the sixth network entity, and when the terminal location information matches with the terminal location range information, may trigger to switch the current fourth network entity.

In an embodiment of the present invention, the case where the terminal position information matches the terminal position range information may include any of the following:

The terminal position information enters the terminal position range information, and the terminal position information leaves the terminal position range information.

Correspondingly, when the terminal position information matches with the terminal position range information, triggering the handover for the fourth network entity may include:

Triggering switching to a fourth network entity in a range when the terminal position information enters the terminal position range information, and triggering switching to a fourth network entity out of the range when the terminal position information leaves the terminal position range information. In particular, the fourth network entity within range may be a fourth network entity connected to the central data network (CENTRAL DN). The fourth network entity within range is connected to CENTRAL DN via an N6 interface. The out-of-range fourth network entity may be a fourth network entity connected to a Local data network (Local DN). When the location of the user terminal leaves the geographical location range that can be served by the Local DN, the third network entity may configure the in-range fourth network entity such that the user terminal may connect to the same application on CENTRAL DN through the in-range fourth network entity.

Specifically, the third network entity may determine whether the user terminal should be connected to the central data network or the local data network according to the terminal location information, when the user terminal reaches the location requirement of the edge area, i.e., when the terminal location information enters the terminal location range information, the current fourth network entity may be switched to the fourth network entity in the range so as to be connected to the central data network through the fourth network entity in the range, and when the user terminal leaves the edge area, i.e., when the terminal location information leaves the terminal location range information, the current fourth network entity may be triggered to be switched to the fourth network entity out of the range and connected to the local data network through the fourth network entity out of the range. In this scenario, the local data network may also be called an edge computing node or edge application server or edge computing platform.

It should be noted that, in the switching process, the current fourth network entity may send PDU session data corresponding to the application to be switched to the fourth network entity in the range through the N9 interface. Transfer of application layer data context can also be implemented at the application layer between CENTRAL DN and Local DN, so that the UE can continue data transmission of the current application when re-accessing CENTRAL DN or Local DN.

Step 202, the first network entity receives a first reply message for the first request message from the third network entity through the second network entity.

After receiving the first request message, the third network entity may generate a first reply message to the first request message, and may send the first reply message to the second network entity, which may send the first reply message to the first network entity.

Referring to fig. 3, a flowchart of steps of another method for network communication according to an embodiment of the present invention is shown, where the method may be applied to a second network entity.

Specifically, the method comprises the following steps:

Step 301, the second network entity receives a first request message from a first network entity, and sends the first request message to a third network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

Step 302, the second network entity receiving a first reply message to the first request message from the third network entity and sending the first reply message to the first network entity

Referring to fig. 4, a flowchart of steps of another method for network communication according to an embodiment of the present invention is shown, where the method may be applied to a third network entity.

Specifically, the method comprises the following steps:

Step 401, the third network entity receives a first request message from a first network entity through a second network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

Step 402, the third network entity sends a first reply message for the first request message to the first network entity through the second network entity.

In an embodiment of the present invention, the method may further include the following steps:

The third network entity sends a second request message to the fourth network entity, the second request message comprises target offloading information, the target offloading information comprises identification information of a user terminal, second identification information and optionally an application identification, the second request message is used for enabling the fourth network entity to update a route of a session corresponding to the application identification according to the second request message, and the third network entity receives a second reply message aiming at the second request message from the fourth network entity and sends the second reply message to the first network entity.

In an embodiment of the present invention, the first request message may further include terminal location range information, and the first request message may be used to enable the third network entity to obtain terminal location information of the user terminal through the sixth network entity, and trigger handover for the fourth network entity when the terminal location information matches with the terminal location range information.

In an embodiment of the present invention, the case where the terminal position information matches the terminal position range information includes any one of the following:

Correspondingly, when the terminal position information is matched with the terminal position range information, triggering the switching aiming at the fourth network entity, including:

Triggering switching to a fourth network entity in a range when the terminal position information enters the terminal position range information, and triggering switching to a fourth network entity out of the range when the terminal position information leaves the terminal position range information.

An embodiment of the present invention is illustrated below in conjunction with fig. 5:

1. The application function sends a first request message to the network opening function or the policy control function, which may use Nnef _ ParameterProvision _update_req message, or may use other Nnef messages, where the first request message may include target offload information, the target offload information includes first identification information and second identification information, and the target offload information may further include at least one of data flow description information, application identification information, terminal location range information and network slice identification information.

2. The network opening function or the policy control function may send the first request message to the session management function, which may use a message Nsmf _ EventExposure _ AppRelocationInfo _req message, a Npcf _ SMPolicyControl _ UpdateNotify _req message, or may use other messages, which may include target offload information, where the target offload information includes first identification information and second identification information, and the target offload information may further include at least one of data flow description information, application identification information, terminal location range information, and network slice identification information.

3. The session management function may send a first reply message to the application function for the first request message via the network opening function or the policy control function, which may take the form of Nsmf _ EventExposure _ AppRelocationInfo _res message, npcf _ SMPolicyControl _ UpdateNotify _res message, or other messages.

4. The session management function may send a second request message to the user plane function, which may be an N4Session Establishment/Modification Request message, or may be another message, which may include, for example, identification information of the user terminal, the second identification information, and optionally, an application identification, and optionally, network slice identification information.

5. The user plane function may return a second reply message to the session management function for the second request message, which may take the form of an N4 Session Establishment/Modification Response message, or other message.

6. The session management function may send a second reply message to the application function, which may take the form of Route change notification messages or other messages.

Referring to fig. 6, a flowchart of steps of another method for network communication according to an embodiment of the present invention is shown, where the method may be applied to a first network entity, where the first network entity may be communicatively connected to a second network entity, where the second network entity may be communicatively connected to a third network entity and a fifth network entity, where the third network entity may be communicatively connected to a plurality of fourth network entities, where each fourth network entity may correspond to one or more mobile edge computing systems, otherwise known as an edge computing platform or an edge computing node.

Specifically, the method comprises the following steps:

Step 601, the first network entity sends a third request message to a fifth network entity through a second network entity, where the third request message includes target offloading information, the target offloading information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is used to enable the third network entity to select a fourth network entity corresponding to a target session;

the first identification information may be a data network access identification, and the second identification information may be identification information of a data network.

In particular, the identification information of the data network may be a data network name, which may be used to uniquely identify one data network. In addition, the data network identifier may be a FQDN or an IP address of a DN, etc.

Alternatively, DNAI may not be included in the first request message, and accordingly, the AF may send quality of service (Quality ofService, qoS) parameters that the application needs to satisfy, such as a delay requirement, a throughput requirement, and the like, to the SMF through the NEF, and the SMF may select a corresponding UPF according to the data network access identifier and the corresponding QoS parameter. Alternatively, the SMF may decide the preferred UPF selection based on interactions with the network data analysis network element and based on NWDAF feedback. Optionally, the first request message further includes an identifier for changing the UPF, where the identifier is mainly used to trigger the SMF to change the UPF of the connection making DN according to the QoS parameter carried in the first request message.

As an example, the target split information may include any of the following:

Data flow description information, application identification information, terminal location range information, and network slice identification information.

After generating the target offloading information, the first network entity generates a third request message according to the offloading information, and may send the third request message to the second network entity, the second network entity may send the third request message to the fifth network entity, and after receiving the third request message, the fifth network entity may create or update offloading information of the first network entity according to the target offloading information in the third request message.

When the offloading information is updated, the third network entity may generate a fourth request message for acquiring the offloading information and send the fourth request message to the fifth network entity, and after receiving the fourth request message, the fifth network entity may generate a fourth reply message for the fourth request message, where the fourth reply message may include the target offloading information, and further may send the fourth reply message to the third network entity, and the third network entity may select a corresponding fourth network entity for the target session according to the target offloading information in the fifth network entity, so that a corresponding session flow may be sent to a Data Network (DN) where the formulated application is located through the fourth network entity.

Specifically, the third network entity may generate a fifth request message according to the target offload information, where the fifth request message may include identification information of the user terminal, the second identification information, and optionally an application identifier, and further may send the fifth request message to the fourth network entity, the fourth network entity may update a route of a session corresponding to the application identifier according to the fifth request message, and may generate a second reply message for the second request message, and send the second reply message to the third network entity, and the third network entity may send the second reply message to the first network entity. The routing specifically refers to which fourth network entity the PDU session selects to send onto the data network where the specified application is located.

Step 602, the first network entity receives a third reply message for the third request message from the fifth network entity through the second network entity.

After receiving the third request message, the fifth network entity may generate a third reply message to the third request message, and may send the third reply message to the second network entity, which may send the third reply message to the first network entity.

In the embodiment of the invention, the first network entity sends the third request message to the fifth network entity through the second network entity, the third request message comprises the target distribution information, the target distribution information comprises the first identification information and the second identification information, the third request message is used for enabling the fifth network entity to create or update the distribution information of the first network entity according to the target distribution information, the target distribution information is used for enabling the third network entity to select the fourth network entity corresponding to the target session, the first network entity receives the third reply message aiming at the third request message from the fifth network entity through the second network entity, the feedback of the distribution strategy is realized, and further the distribution data can be distributed according to the latest distribution strategy, and the network transmission efficiency is improved.

Referring to fig. 7, a flowchart of steps of another method for network communication according to an embodiment of the present invention is shown, where the method may be applied to a second network entity.

Specifically, the method comprises the following steps:

Step 701, the second network entity receives a third request message from the first network entity, and sends the third request message to a fifth network entity, where the third request message includes target offloading information, the target offloading information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is used to enable the third network entity to select a fourth network entity corresponding to a target session;

Step 702, the second network entity receives a third reply message for the third request message from the fifth network entity, and sends the third reply message to the first network entity.

Referring to fig. 8, a flowchart of steps of another method for network communication according to an embodiment of the present invention is shown, where the method may be applied to a fifth network entity.

Specifically, the method comprises the following steps:

Step 801, the fifth network entity receives a third request message from the first network entity through the second network entity, where the third request message includes target offloading information, the target offloading information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is used to enable the third network entity to select a fourth network entity corresponding to a target session;

step 802, the fifth network entity sends a third reply message for the third request message to the first network entity through the second network entity.

the fifth network entity receives a fourth request message from a third network entity, wherein the fourth request message is used for acquiring the distribution information of the first network entity from the fifth network entity, the fifth network entity sends a fourth reply message aiming at the fourth request message to the third network entity, the fourth reply message comprises target distribution information, the target distribution information comprises first identification information and second identification information, and the fourth reply message is used for enabling the third network entity to select a fourth network entity corresponding to a target session according to the target distribution information.

Referring to fig. 9, a flowchart of steps of another method for network communication according to an embodiment of the present invention is shown, where the method may be applied to a third network entity.

Specifically, the method comprises the following steps:

Step 901, the third network entity sends a fourth request message to a fifth network entity, where the fourth request message is used to obtain the offloading information of the first network entity from the fifth network entity;

step 902, the third network entity receives a fourth reply message for the fourth request message from the fifth network entity, where the fourth reply message includes target offloading information, the target offloading information includes first identification information and second identification information, and the fourth reply message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information.

the third network entity sends a fifth request message to the fourth network entity, wherein the fifth request message comprises identification information of a user terminal, second identification information and optionally an application identification, the fifth request message is used for enabling the fourth network entity to update a route of a session corresponding to the application identification according to the fifth request message, and the third network entity receives a fifth reply message aiming at the fifth request message from the fourth network entity and sends the fifth reply message to the first network entity.

An embodiment of the present invention is illustrated below with reference to fig. 10:

1. The application function sends a third request message to the network opening function or the policy control function, which may use Nnef _ ParameterProvision _update_req message, or may use other Nnef messages, where the target offload information may include target offload information, the target offload information includes first identification information and second identification information, and the target offload information may further include at least one of data flow description information, application identification information, terminal location range information, and network slice identification information.

2. The network opening function or the policy control function sends the third request message to the unified data store, which may use Nudr _dm_create/Update Req message, or may use other messages, where the target offload information may include target offload information, and the target offload information may include first identification information and second identification information, and the target offload information may further include at least one of data flow description information, application identification information, terminal location range information, and network slice identification information.

3. The unified data store sends a third reply message to the network opening function or policy control function for a third request, which may take the form of Nudr _dm_create/update_res message or other messages.

4. The network opening function or policy control function sends a third reply message to the application function, which may use Nnef _ ParameterProvision _update_res message or other messages.

5. The session management function sends a fourth request message to the unified data store, which may take the form of Nudr DM subsystem message or other messages.

6. The unified data store sends a fourth reply message for the fourth request message to the session management function, which may be a Nudr _dm_notify message, or may be other messages, and may include target offload information, where the target offload information includes first identification information, identification information of an application function, data flow description information, application identification information, terminal location range information, and network slice identification information.

7. The session management function may send a fifth request message to the user plane function, which may be an N4Session Establishment/Modification Request message, or may be another message, which may include identification information of the user terminal, the second identification information, and optionally, an application identification, and optionally, the network slice identification information.

8. The user plane function may return a fifth reply message to the session management function for the fifth request message, which may take the form of an N4 Session Establishment/Modification Response message, or other message.

9. The session management function may send a fifth reply message to the application function, which may take the form of Route change notification messages or other messages.

It should be noted that, for simplicity of description, the method embodiments are shown as a series of acts, but it should be understood by those skilled in the art that the embodiments are not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts are not necessarily required by the embodiments of the invention.

Referring to fig. 11, a schematic structural diagram of a network communication device according to an embodiment of the present invention is shown, where the device may be applied to a first network entity, and may specifically include the following modules:

A first request message sending module 1101, configured to send a first request message to a third network entity through a second network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

A first reply message receiving module 1102, configured to receive, by the second network entity, a first reply message for the first request message from the third network entity.

In an embodiment of the present invention, the target diversion information further includes at least one of the following:

In an embodiment of the present invention, the first request message further includes terminal location range information for a user terminal, and the first request message is configured to enable the third network entity to obtain terminal location information of the user terminal through a sixth network entity, and trigger handover for a fourth network entity when the terminal location information matches with the terminal location range information.

In an embodiment of the present invention, when the terminal location information matches the terminal location range information, triggering a handover for a fourth network entity includes:

Triggering switching to a fourth network entity in a range under the condition that the terminal position information enters the terminal position range information;

and triggering switching to a fourth network entity out of range under the condition that the terminal position information leaves the terminal position range information.

Referring to fig. 12, a schematic structural diagram of another network communication device according to an embodiment of the present invention is shown, where the device may be applied to a second network entity, and may specifically include the following modules:

a first request message forwarding module 1201, configured to receive a first request message from a first network entity, and send the first request message to a third network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

A first reply message forwarding module 1202, configured to receive a first reply message for the first request message from the third network entity, and send the first reply message to the first network entity.

Referring to fig. 13, a schematic structural diagram of another network communication device according to an embodiment of the present invention is shown, where the device may be applied to a third network entity, and may specifically include the following modules:

A first request message receiving module 1301, configured to receive, by using a second network entity, a first request message from a first network entity, where the first request message includes target offloading information, the target offloading information includes first identification information and second identification information, and the first request message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information;

A first reply message sending module 1302, configured to send, to the first network entity, a first reply message for the first request message through the second network entity.

In an embodiment of the present invention, further includes:

A second request message sending module, configured to send a second request message to the fourth network entity, where the second request message includes target offload information, where the target offload information includes first identification information and second identification information, and the second request message is configured to enable the fourth network entity to update a route of a session corresponding to the application identifier according to the second request message;

and the second reply message forwarding module is used for receiving a second reply message aiming at the second request message from the fourth network entity and sending the second reply message to the first network entity.

Referring to fig. 14, a schematic structural diagram of another network communication device according to an embodiment of the present invention is shown, where the device may be applied to a first network entity, and may specifically include the following modules:

A third request message sending module 1401, configured to send a third request message to a fifth network entity through a second network entity, where the third request message includes target offloading information, the target offloading information includes first identification information and second identification information, the third request message is configured to enable the fifth network entity to create or update offloading information of the first network entity according to the target offloading information, and the target offloading information is configured to enable the third network entity to select a fourth network entity corresponding to a target session;

A third reply message receiving module 1402, configured to receive, by the second network entity, a third reply message for the third request message from the fifth network entity.

In an embodiment of the present invention, the target split information includes any one of the following:

Referring to fig. 15, a schematic structural diagram of another network communication device according to an embodiment of the present invention is shown, where the device may be applied to a second network entity, and may specifically include the following modules:

A third request message forwarding module 1501, configured to receive a third request message from a first network entity and send the third request message to a fifth network entity, where the third request message includes target offload information, the target offload information includes first identification information and second identification information, the third request message is configured to enable the fifth network entity to create or update offload information of the first network entity according to the target offload information, and the target offload information is configured to enable the third network entity to select a fourth network entity corresponding to a target session;

A third reply message forwarding module 1502, configured to receive a third reply message for the third request message from the fifth network entity, and send the third reply message to the first network entity.

Referring to fig. 16, a schematic structural diagram of another network communication device according to an embodiment of the present invention is shown, where the device may be applied to a fifth network entity, and may specifically include the following modules:

A third request message receiving module 1601, configured to receive, by using a second network entity, a third request message from a first network entity, where the third request message includes target offload information, where the target offload information includes first identification information and second identification information, the third request message is configured to enable the fifth network entity to create or update offload information of the first network entity according to the target offload information, and the target offload information is configured to enable the third network entity to select a fourth network entity corresponding to a target session;

A third reply message sending module 1602, configured to send a third reply message for the third request message to the first network entity through the second network entity.

In an embodiment of the present invention, further includes:

a fourth request message receiving module, configured to receive a fourth request message from a third network entity, where the fourth request message is used to obtain, from the fifth network entity, offloading information of the first network entity;

A fourth reply message sending module, configured to send a fourth reply message for the fourth request message to the third network entity, where the fourth reply message includes target offloading information, the target offloading information includes first identification information and second identification information, and the fourth reply message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information.

Referring to fig. 17, a schematic structural diagram of another network communication device according to an embodiment of the present invention is shown, where the device may be applied to a third network entity, and may specifically include the following modules:

a fourth request message sending module 1701, configured to send a fourth request message to a fifth network entity, where the fourth request message is used to obtain the offloading information of the first network entity from the fifth network entity;

A fourth reply message receiving module 1702 configured to receive a fourth reply message for the fourth request message from the fifth network entity, where the fourth reply message includes target offloading information, the target offloading information includes first identification information and second identification information, and the fourth reply message is configured to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offloading information.

In an embodiment of the present invention, further includes:

A fifth request message sending module, configured to send a fifth request message to the fourth network entity, where the fifth request message includes identification information of a user terminal, second identification information, and an application identifier, and the fifth request message is used to enable the fourth network entity to update a route of a session corresponding to the application identifier according to the fifth request message;

A fifth reply message forwarding module, configured to receive a fifth reply message for the fifth request message from the fourth network entity, and send the fifth reply message to the first network entity.

An embodiment of the present invention also provides a server that may include a processor, a memory, and a computer program stored on the memory and capable of running on the processor, the computer program implementing the steps of the method of network communication as above when executed by the processor.

An embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the steps of the method of network communication as above.

For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.

In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.

It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable network communication terminal apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable network communication terminal apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable network communication terminal apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable network communication terminal apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the invention.

Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.

While the foregoing has described in detail the method and apparatus for network communication, specific examples have been provided herein to illustrate the principles and embodiments of the present invention, and the above examples are provided to assist in understanding the method and core ideas of the present invention, and to those of ordinary skill in the art, in light of the ideas of the present invention, there are variations in the specific embodiments and application scope, and in light of the above, the disclosure should not be construed as limiting the invention.

Claims

1. A network communication method, characterized in that it is applied to a first network entity, comprising:

In an edge computing network, the first network entity sends a first request message to a third network entity through a second network entity, the first request message including target offload information, the target offload information including first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offload information;

The first network entity receives a first reply message for the first request message from the third network entity through the second network entity;

Among them, the first network entity is a network entity for application functions; the second network entity is a network entity for network opening functions, or a network entity for policy control functions, or a network entity for data packet flow description functions; the third network entity is a network entity for session management functions; the fourth network entity is a network entity for user plane functions, and each fourth network entity corresponds to one or more mobile edge computing systems, or edge computing platforms or edge computing nodes.

2. The method according to claim 1, wherein the target diversion information further includes at least one of the following:

3. The method according to claim 1 or 2 is characterized in that the first request message also includes terminal location range information, and the first request message is used to enable the third network entity to obtain the terminal location information of the user terminal through the sixth network entity, and trigger switching for the fourth network entity when the terminal location information matches the terminal location range information.

4. The method according to claim 3, wherein the situation where the terminal location information matches the terminal location range information includes any of the following:

The terminal location information enters the terminal location range information, and the terminal location information leaves the terminal location range information.

5. The method according to claim 4, characterized in that when the terminal location information matches the terminal location range information, triggering switching for the fourth network entity comprises:

When the terminal location information enters the terminal location range information, triggering switching to a fourth network entity within the range;

When the terminal location information leaves the terminal location range information, a switch to a fourth network entity out of range is triggered.

6. A network communication method, characterized in that it is applied to a second network entity, comprising:

In an edge computing network, the second network entity receives a first request message from the first network entity, and sends the first request message to a third network entity, the first request message includes target offload information, the target offload information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offload information;

The second network entity receives a first reply message for the first request message from the third network entity, and sends the first reply message to the first network entity;

7. A network communication method, characterized in that it is applied to a third network entity, comprising:

In the edge computing network, the third network entity receives a first request message from the first network entity through the second network entity, the first request message includes target offload information, the target offload information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offload information;

The third network entity sends a first reply message to the first network entity through the second network entity in response to the first request message;

8. The method according to claim 7, further comprising:

The third network entity sends a second request message to the fourth network entity, where the second request message includes identification information of the user terminal, second identification information, and an application identifier, and the second request message is used to enable the fourth network entity to update a route of a session corresponding to the application identifier according to the second request message;

The third network entity receives a second reply message for the second request message from the fourth network entity, and sends the second reply message to the first network entity.

9. The method according to claim 7 or 8 is characterized in that the first request message also includes terminal location range information, and the first request message is used to enable the third network entity to obtain the terminal location information of the user terminal through the sixth network entity, and trigger switching for the fourth network entity when the terminal location information matches the terminal location range information.

10. The method according to claim 9, wherein the situation where the terminal location information matches the terminal location range information includes any of the following:

11. The method according to claim 10, characterized in that when the terminal location information matches the terminal location range information, triggering a handover for the fourth network entity comprises:

12. A network communication method, characterized in that it is applied to a first network entity, comprising:

In the edge computing network, the first network entity sends a third request message to the fifth network entity through the second network entity, the third request message includes target diversion information, the target diversion information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update the diversion information of the first network entity according to the target diversion information, and the target diversion information is used to enable the third network entity to select a fourth network entity corresponding to the target session;

The first network entity receives a third reply message for the third request message from the fifth network entity through the second network entity;

13. The method according to claim 12, wherein the target diversion information includes any one of the following:

14. A network communication method, characterized in that it is applied to a second network entity, comprising:

In the edge computing network, the second network entity receives a third request message from the first network entity, and sends the third request message to the fifth network entity, the third request message includes target diversion information, the target diversion information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update the diversion information of the first network entity according to the target diversion information, and the target diversion information is used to enable the third network entity to select a fourth network entity corresponding to the target session;

The second network entity receives, from the fifth network entity, a third reply message for the third request message, and sends the third reply message to the first network entity;

15. A network communication method, characterized in that it is applied to a fifth network entity, comprising:

In the edge computing network, the fifth network entity receives a third request message from the first network entity through the second network entity, the third request message includes target diversion information, the target diversion information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update the diversion information of the first network entity according to the target diversion information, and the target diversion information is used to enable the third network entity to select a fourth network entity corresponding to the target session;

The fifth network entity sends a third reply message to the first network entity through the second network entity for the third request message;

16. The method according to claim 15, further comprising:

The fifth network entity receives a fourth request message from the third network entity, where the fourth request message is used to obtain the offload information of the first network entity from the fifth network entity;

The fifth network entity sends a fourth reply message to the third network entity for the fourth request message, the fourth reply message including target diversion information, the target diversion information including first identification information and second identification information, and the fourth reply message is used to enable the third network entity to select a fourth network entity corresponding to the target session according to the target diversion information.

17. A network communication method, characterized in that it is applied to a third network entity, comprising:

In the edge computing network, the third network entity sends a fourth request message to the fifth network entity, where the fourth request message is used to obtain the offload information of the first network entity from the fifth network entity;

The third network entity receives a fourth reply message for the fourth request message from the fifth network entity, where the fourth reply message includes target offload information, where the target offload information includes first identification information and second identification information, and the fourth reply message is used to enable the third network entity to select a fourth network entity corresponding to the target session according to the target offload information;

18. The method according to claim 17, further comprising:

The third network entity sends a fifth request message to the fourth network entity, where the fifth request message includes identification information of the user terminal, the second identification information, and an application identifier, and the fifth request message is used to enable the fourth network entity to update a route of a session corresponding to the application identifier according to the fifth request message;

The third network entity receives a fifth reply message in response to the fifth request message from the fourth network entity, and sends the fifth reply message to the first network entity.

19. A network communication device, characterized in that it is applied to a first network entity, comprising:

In an edge computing network, a first request message sending module is used to send a first request message to a third network entity through a second network entity, wherein the first request message includes target offload information, the target offload information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offload information;

A first reply message receiving module, configured to receive a first reply message for the first request message from the third network entity through the second network entity;

20. A network communication device, characterized in that it is applied to a second network entity, comprising:

In an edge computing network, a first request message forwarding module is used to receive a first request message from a first network entity and send the first request message to a third network entity, wherein the first request message includes target offload information, the target offload information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offload information;

A first reply message forwarding module, configured to receive a first reply message for the first request message from the third network entity, and send the first reply message to the first network entity;

21. A network communication device, characterized in that it is applied to a third network entity, comprising:

In an edge computing network, a first request message receiving module is used to receive a first request message from a first network entity through a second network entity, the first request message includes target offload information, the target offload information includes first identification information and second identification information, and the first request message is used to enable the third network entity to select a fourth network entity corresponding to a target session according to the target offload information;

A first reply message sending module, configured to send a first reply message to the first request message to the first network entity through the second network entity;

22. A network communication device, characterized in that it is applied to a first network entity, comprising:

In the edge computing network, a third request message sending module is used to send a third request message to a fifth network entity through a second network entity, the third request message includes target diversion information, the target diversion information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update the diversion information of the first network entity according to the target diversion information, and the target diversion information is used to enable the third network entity to select a fourth network entity corresponding to the target session;

A third reply message receiving module, configured to receive a third reply message for the third request message from the fifth network entity through the second network entity;

23. A network communication device, characterized in that it is applied to a second network entity, comprising:

In an edge computing network, a third request message forwarding module is used to receive a third request message from a first network entity and send the third request message to a fifth network entity, wherein the third request message includes target diversion information, the target diversion information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update the diversion information of the first network entity according to the target diversion information, and the target diversion information is used to enable the third network entity to select a fourth network entity corresponding to a target session;

A third reply message forwarding module, configured to receive a third reply message for the third request message from the fifth network entity, and send the third reply message to the first network entity;

24. A network communication device, characterized in that it is applied to a fifth network entity, comprising:

In the edge computing network, a third request message receiving module is used to receive a third request message from the first network entity through the second network entity, the third request message includes target diversion information, the target diversion information includes first identification information and second identification information, the third request message is used to enable the fifth network entity to create or update the diversion information of the first network entity according to the target diversion information, and the target diversion information is used to enable the third network entity to select a fourth network entity corresponding to the target session;

A third reply message sending module, configured to send a third reply message to the first network entity through the second network entity for the third request message;

25. A network communication device, characterized in that it is applied to a third network entity, comprising:

In the edge computing network, a fourth request message sending module is used to send a fourth request message to a fifth network entity, where the fourth request message is used to obtain the diversion information of the first network entity from the fifth network entity;

a fourth reply message receiving module, configured to receive a fourth reply message for the fourth request message from the fifth network entity, the fourth reply message including target offload information, the target offload information including first identification information and second identification information, the fourth reply message being used to enable the third network entity to select a fourth network entity corresponding to the target session according to the target offload information;