CN114143185A

CN114143185A - Network communication method and device, electronic equipment and storage medium

Info

Publication number: CN114143185A
Application number: CN202011105436.9A
Authority: CN
Inventors: 于小博; 刘大鹏; 白常明
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-08-13
Filing date: 2020-10-15
Publication date: 2022-03-04

Abstract

The embodiment of the invention provides a method and a device for network communication, electronic equipment and a storage medium, wherein the method comprises the following steps: the first network entity sends a first request message to a second network entity, wherein the first request message comprises at least one piece of first network parameter type information, the first request message is used for enabling the second network entity to send a first message to a third network entity according to a preset event trigger, and the first message comprises at least one piece of partial network parameter information corresponding to the first network parameter type information; and the first network entity receives a first reply message returned by the second network entity aiming at the first request message. By the embodiment of the invention, the instantiation of the third network entity can be dynamically managed by the first network entity, the authority of the third network entity for acquiring the network parameters can be dynamically managed by the first network entity, and the deployment flexibility of the third network entity is enhanced.

Description

Network communication method and device, electronic equipment and storage medium

The present application claims priority from the application entitled "a method and apparatus for network communication, electronic device, storage medium," filed by the national patent office on 13/08/2020, application No. 202010814518.4, the entire contents of which are incorporated herein by reference.

Technical Field

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

Background

Edge computing is an evolutionary approach to cloud computing, which differs from centralized data centers by deploying decentralized data centers at the edge of the network, making the data processing logic closer to the consumer.

Edge computing is considered as one of the important means for meeting Key Performance Indicators (KPIs) in 5G network requirements, and plays a large role particularly in terms of low delay and bandwidth efficiency. Since edge computing opens up a network edge for applications and services (including applications and services from third parties), edge computing in telecommunications networks is not only a technical enabler to meet 5G performance metrics, but also plays an important role in the transition to the telecommunications field, which is transitioning to a multi-functional service platform for industry and other specific customer groups.

Currently, 3GPP (3)^rdGenerationpartnership project, third generation partnership project) proposes edge network open function (edgenetworkexposurgefunc)Station) to solve the problem of delay when 5G network parameters are exposed to an Application Function (AF).

However, in the prior art, the edge network open function deployment mode is relatively single, which results in the increase of deployment and docking costs. For example, the prior art does not provide a solution how to manage the edge network open function full lifecycle.

In the solution of the present invention, the edge computing platform may be equivalent to an edge application server. In particular, the edge computing platform may also be an edge-enabled server that maintains connection to edge application servers. The edge-enabled server is directly connected with the 5G core network element and manages the edge application on the edge application server through an interface with the edge application server.

Disclosure of Invention

In view of the above, it is proposed to provide a method and apparatus for network communication, an electronic device, and a storage medium, which overcome the above problems or at least partially solve the above problems, including:

a method of network communication applied to a first network entity includes:

the first network entity sends a first request message to a second network entity, wherein the first request message comprises at least one piece of first network parameter type information, the first request message is used for enabling the second network entity to send a first message to a third network entity according to a preset event trigger, and the first message comprises at least one piece of partial network parameter information corresponding to the first network parameter type information;

and the first network entity receives a first reply message returned by the second network entity aiming at the first request message.

Optionally, the first request message includes identification information of a third network entity.

Optionally, the first request message further includes identification information of a fourth network entity, where the identification information of the fourth network entity is used to enable the second network entity to send the first message to the third network entity according to an application corresponding to the fourth network entity.

Optionally, the second network entity includes a session management function entity, and when the second network entity is the session management function entity, the first network parameter type information includes at least one of the following:

type information of quality parameters and type information of route change parameters;

the first message includes at least one of:

data network access identification, routing information.

Optionally, the second network entity includes an access management function entity, and when the second network entity is the access management function entity, the first network parameter type information includes type information of a location of the user equipment, and the first message includes location information of the user equipment.

Optionally, the second network entity includes a user plane function entity, and when the second network entity is the user plane function entity, the first network parameter type information includes at least one of the following:

type information of the delay, type information of the buffer status,

the first message includes at least one of:

round trip delay information, buffering information.

Optionally, the second network entity includes a management service function entity, and when the second network entity is the management service function entity, the first network parameter type information includes type information of wireless network information, and the first message includes the wireless network information.

Optionally, the second network entity includes a session management function entity, and before the first network entity sends the first request message to the second network entity, the method further includes:

the first network entity receives a second request message sent by a fourth network entity, wherein the second request message is used for requesting instantiation of the third network entity.

and the first network entity and the fourth network entity perform bidirectional authentication.

Optionally, the second network entity includes a user plane function entity, and after the first network entity sends the first request message to the second network entity, the method further includes:

and the user plane functional entity sends the information of the quality parameters to a session management functional entity, and the session management functional entity forwards the information to the third network entity.

Optionally, the second network entity includes a management service function entity, and after the first network entity sends the first request message to the second network entity, the method further includes:

and the management service function entity sends the first message to the fourth network entity through the third network entity.

Optionally, the second network entity includes a session management function entity, and further includes:

the first network entity sends a third request message to the second network entity, wherein the third request message is used for canceling the operation of reporting parameters to the fourth network entity by the second network entity through the third network entity;

the first network entity de-instantiates a third network entity.

Optionally, the second network entity includes a session management function entity, the process of sending the first request message is implemented by sending a fourth request message and a fifth request message, and the sending, by the first network entity, the first request message to the second network entity includes:

when the second network entity is a session management function entity, the first network entity sends the fourth request message to a fifth network entity, so that the fifth network entity sends the fifth request message to the second network entity according to the fourth request message.

Optionally, the method further comprises:

and the session management functional entity sends a sixth request message to the user plane functional entity, so that the user plane functional entity sends a third message to a fourth network entity through a seventh network entity, wherein the third message comprises the first parameter information.

Optionally, the second network entity includes a session management function entity, the process of sending the first request message is implemented by sending a seventh request message and an eighth request message, and the sending, by the first network entity, the first request message to the second network entity includes:

when the second network entity is a session management function entity, the first network entity sends the seventh request message to a sixth network entity, so that the sixth network entity sends the eighth request message to the second network entity according to the seventh request message.

A method of network communication applied to a second network entity, where the second network entity may include a session management function entity, comprising:

the session management functional entity receives a first request message sent by the first network entity and returns a first reply message aiming at the first request message to the first network entity, wherein the first request message comprises at least one piece of first network parameter type information, the first request message is used for enabling the session management functional entity to send the first message to a third network entity according to the triggering of a preset event, and the first message comprises at least one piece of partial network parameter information corresponding to the first network parameter type information;

and according to the first request message, the session management function entity triggers the route change of the user equipment and sends a first message to a third network entity.

Optionally, the first network parameter type information includes at least one of:

the first message includes at least one of:

data network access identification, routing information.

Optionally, the method further comprises:

the session management functional entity receives the quality parameter information sent by the user plane functional entity;

and the session management function entity forwards a second message to the third network entity, wherein the second message comprises the information of the quality parameter.

Optionally, the method further comprises:

and the session management functional entity receives a third request message sent by the first network entity, where the third request message is used to cancel an operation of the session management functional entity reporting parameters to the fourth network entity through the third network entity.

Optionally, the receiving the first request message sent by the first network entity is implemented by receiving a fourth request message and a fifth request message, and the receiving, by the session management function entity, the first request message sent by the first network entity includes:

the session management functional entity receives the fifth request message sent by a fifth network entity, where the fifth request message is sent according to the fourth request message sent by the first network entity and received by the fifth network entity.

Optionally, the method further comprises:

Optionally, the receiving the first request message sent by the first network entity is implemented by receiving a seventh request message and an eighth request message, and the receiving, by the session management function entity, the first request message sent by the first network entity includes:

the session management functional entity receives the eighth request message sent by a sixth network entity, where the eighth request message is sent according to the seventh request message sent by the first network entity and received by the sixth network entity.

An apparatus for network communication, applied to a first network entity, the apparatus is configured to:

sending a first request message to a second network entity, wherein the first request message comprises at least one piece of first network parameter type information, the first request message is used for enabling the second network entity to send a first message to a third network entity according to a preset event trigger, and the first message comprises at least one piece of partial network parameter information corresponding to the first network parameter type information;

and receiving a first reply message returned by the second network entity aiming at the first request message.

An apparatus for network communication, applied to a second network entity, where the second network entity may include a session management function entity, the apparatus being configured to:

receiving a first request message sent by the first network entity, and returning a first reply message aiming at the first request message to the first network entity, wherein the first request message comprises at least one piece of first network parameter type information, the first request message is used for enabling a session management function entity to send the first message to a third network entity according to a preset event trigger, and the first message comprises at least one piece of partial network parameter information corresponding to the first network parameter type information;

An electronic device comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, the computer program, when executed by the processor, implementing a method of network communication as described above.

A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, implements a method of network communication as described above.

The embodiment of the invention has the following advantages:

in the embodiment of the present invention, a first network entity sends a first request message to a second network entity, where the first request message includes at least one piece of first network parameter type information, and the first request message is used to enable the second network entity to send the first message to a third network entity according to a preset event trigger, where the first message includes at least one piece of partial network parameter information corresponding to the first network parameter type information, and the first network entity receives a first reply message returned by the second network entity for the first request message, so as to implement dynamic management of instantiation of the third network entity by the first network entity, and the first network entity can dynamically manage the right of the third network entity to acquire network parameters, thereby enhancing the flexibility of deployment of the first network entity.

Drawings

In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the description of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

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

FIG. 1b is a diagram of another moving edge computing system according to an embodiment of the invention;

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

FIG. 3a is a diagram of an exemplary domain instantiated in an operator domain, according to an embodiment of the invention;

FIG. 3b is a diagram illustrating an edge domain instantiation according to an embodiment of the present invention;

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

FIG. 5 is a diagram illustrating an example of network communications provided by an embodiment of the present invention;

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

FIG. 7 is a diagram illustrating another example of network communications provided by an embodiment of the present invention;

FIG. 8 is a flow chart of steps in another method of network communication provided by an embodiment of the present invention;

FIG. 9 is a diagram illustrating another example of network communications provided by an embodiment of the present invention;

FIG. 10 is a flow chart of steps in another method of network communication provided by an embodiment of the present invention;

fig. 11 is a flow chart illustrating steps of another method for network communication according to an embodiment of the present invention.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all 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 invention.

In a Mobile Edge Computing (MEC) system, as shown in fig. 1a, the underlying Network layer may adopt a 3G Network, a local area Network (Localnetwork), 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), the Mobile edge host may include a Mobile edge platform (Mobile edge platform), a Virtualization architecture (Virtualization), such as Network function Virtualization infrastructure solution (NFVI), 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 management), a user terminal, and the like.

In the case of a mobile edge computing system combined with a 5G core network, as shown in fig. 1b, the mobile edge computing system has a system layer (system level) which may include a mobile edge computing coordinator (mecco coordinator), and a distributed host layer (distributed host level) which may include a mecc platform (mecc platform), a mecc platform Management (mecc platform Management), and a mobile edge host which may include an application and virtualization infrastructure (virtualisation infrastructure).

Since the mobile edge computing system is combined with the 5G core network, the instantiated mobile edge computing coordinator can be used as an Application Function (AF) in the 5G, and the mobile edge host can be used as a Data Network (DN) in the 5G core network, and the data network is in communication connection with a User Plane Function (UPF).

Specifically, the user plane Function may be connected to a Session Management Function (SMF) through an N4 interface, and may be communicatively connected to the user terminal through a Radio Access Network (RAN), and the radio access Network and the user terminal may be communicatively connected to an access and mobility management Function (AMF), and the access and mobility management Function, a session management Function, a Network open Function (NEF), a Policy Control Function (PCF), a Unified Data Management (UDM), a unified data management Function (unicedatam), a Network storage Function (NRF), a Network replication Function, a Network slice selection Function (nsslnetwork selection Function), an authentication server Function (sf), and may be communicatively connected to the Network management Function (SMF) and the mobility management Function (RAN), and may be communicatively connected to the user terminal through a mobile access Network (RAN) and a mobility management Function (Naf).

Currently, 3GPP proposes the concept of edge network open function to solve the problem of delay when the 5G network parameters are exposed to the application function. However, in the prior art, the deployment mode of the edge network open function is single, which leads to the improvement of deployment and docking costs. For example, the prior art does not provide a solution how to manage the edge network open function full lifecycle.

Moreover, the instantiation of the third network entity can be dynamically managed by the first network entity, so that the third network entity can be deployed in an operator domain or an edge domain. Meanwhile, the first network entity can manage the network elements and the data types for reporting the parameters to the third network entity, so that the flexibility of the third network entity in deployment and data reporting to the fourth network entity is enhanced.

The following examples illustrate the invention in detail:

wherein, the first network entity can be a central network open function (centrelnef); the second network entity may include a Session management function entity, an access management function entity, a user plane function entity, and a management service function entity, where the Session management function entity may be a Session Management Function (SMF), the access management function entity may be an access and mobility management function (AMF), the user plane function entity may be a User Plane Function (UPF), and the management service function entity may be a management service function (mnsprroducer); the third network entity may be an edge network open function (edgenetworkexposurgefunction); the fourth network entity may be an Application Function (AF); the fifth network entity may be a Policy Control Function (PCF); the sixth network entity may be a Unified Data Management (UDM); the seventh network entity may be a local network open function (LocalNEF).

Wherein, the identification information of the third network entity may be an edge network open function ID, the identification information of the fourth network entity may be an application function ID, the type information of the quality parameter may be QoS type information (for example, at least one of uplink and downlink data caching condition, uplink and downlink delay or round-trip delay (round-trip delay), throughput, uplink and downlink transmission rate, etc.), the type information of the route change parameter may be type information of a user plane route change uplink, the data network access identifier may be dnai (data network access identifier), the routing information may be N6routing information of an N6 interface, the type information of the user equipment location may be type information of a UE location, the user equipment location information may be UE location information, the type information of the delay may be type information of roundtrip, the type information of the buffer condition may be type information of buffer condition, the round-trip delay information may be roundtrip delay, the buffer information may be buffer condition, the type information of the radio network information may be radiodata information, and the quality parameter information may be QoS related parameters (including bidirectional delay of a packet, and may also be at least one of uplink and downlink data buffering conditions, uplink and downlink delay or round-trip delay (round-trip delay), throughput, uplink and downlink transmission rates, and the like).

Referring to fig. 2, a flowchart illustrating steps of a 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 side, and specifically may include the following steps:

step 201, the first network entity sends a first request message to a second network entity, the first request message includes at least one first network parameter type information, the first request message is used for enabling the second network entity to send a first message to a third network entity according to a preset event trigger, the first message includes at least one part of network parameter information corresponding to the first network parameter type information;

as an example, the first request message may include identification information of the third network entity.

The first request message may further include identification information of the fourth network entity, and the identification information of the fourth network entity may be used to enable the second network entity to send the first message to the third network entity according to an application corresponding to the fourth network entity.

In the process of dynamically managing instantiation of the edge network open function by the central network open function, the central network open function may send a first request message to the second network entity, where the first request message includes at least one piece of first network parameter type information, and the first request message may be used to enable the second network entity to send the first message to the edge network open function according to a preset event trigger, where the first message includes at least one piece of partial network parameter information corresponding to the first network parameter type information.

In practical applications, the second network entity may include a session network entity, an access network entity, a user plane network entity, and a message service network entity, where in a case that the second network entity is a different network entity, the first network parameter type information in the first request message may be different network parameter type information, the first message sent by the second network entity to the edge network open function may be a different message, and the first message may include at least one piece of partial network parameter information corresponding to the first network parameter type information.

In an embodiment of the present invention, the second network entity may include a session management function entity, and when the second network entity is the session management function entity, the first network parameter type information may include at least one of the following:

the first message may include at least one of: data network access identification, routing information.

For example, the central network open function may send a first Request message to the session management function, where the first Request message may be a parameter exposure available Request (parameterexposure enable), such as an SMF event exposure subscription Request message (Nsmf _ EventExposure _ Subscribe Request) or an SMF event exposure registration message (Nsmf _ EventExposure _ Register), which may also be named otherwise, but the functions are the same.

The request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, where the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-trip delay), throughput, uplink and downlink transmission rate, and the like), type information of a route change parameter UProute change, and a response message corresponding to the first request message sent by the session management function may be received, and for example, the response message may be an SMF event exposure notification message (Nsmf _ EventExposure _ Notify), which may also be named otherwise, but the functions of the response message are the same.

After receiving the first request message, the session management function may trigger a route change to the ue, for example, a new user plane function may be selected, and the session management function may send a first message to the edge network open function, where the first message may be an SMF event exposure notification message (Nsmf _ evendexposurenotifiy), which may also be named otherwise, but has the same function, where the first message may include a data network access identifier DNAI, routing information N6routing information, and the like.

In an embodiment of the present invention, the second network entity may include an access management function entity, and when the second network entity is the access management function entity, the first network parameter type information may include type information of a location of the user equipment, and the first message may include the location information of the user equipment.

For example, the central network open function may send a first request message, which may be an AMF Event expose subscription request message (Namf _ EventExposure _ subscribe request) or an AMF Event expose registration message (Namf _ EventExposure _ Register), to the access and mobility management function, which may also be named with another name but have the same function, and may receive an access and a response message corresponding to the first request message sent by the mobility management function, which may also be an AMF Event expose registration message (Namf _ Location _ Event _ notification), which may also be named with another name but have the same function.

The first request message may include an edge network openfunction ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of a location of the user equipment.

After receiving the first request message, the access and mobility management function may send a first message to the edge network openness function, where the first message may include location information ue location of the user equipment.

In an embodiment of the present invention, the second network entity may include a user plane function entity, and when the second network entity is the user plane function entity, the first network parameter type information may include at least one of the following:

type information of the delay, type information of the buffer status,

the first message may include at least one of:

round trip delay information, buffering information.

For example, the central network openness function may send a first request message to the user plane function, where the first request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of delay, type information of buffer status, and the like.

After the access and mobility management function receives the first request message, a first message may be sent to the edge network openness function, where the first message may include round trip delay information roundtrip, buffering information, and the like.

In one example, the network parameter information may be sent to the session management function through N4, and then the session management function may send the network parameter information to the edge network openness function through an SMF event exposure notification message (Nsmf _ EventExposure _ Notify), which may also be named otherwise, but the function of which is the same.

In an embodiment of the present invention, the second network entity may include a management service function entity, and when the second network entity is the management service function entity, the first network parameter type information may include type information of the wireless network information, and the first message may include the wireless network information.

For example, the central network open function may send a first Request message to the management service function, where the first Request message may be a parameter exposure availability Request (parameterExposeleblerequest), such as a Request may be a MNF event exposure subscription Request message (Nmnf _ EventExposureSubscribe Request) or a MNF event exposure registration message (Nmnf _ EventExposureRegister), which may also use other names but have the same function, and may receive a response message corresponding to the first Request message sent by the management service function, such as a response message may be a MNF event exposure notification message (Nmnf _ EventExposureNotification), which may also use other names but have the same function.

The request message may include an edge network openness function ID and first network parameter type information, NetworkParametertype, and the first network parameter type information may include type information of radio network information, and may receive a first reply message for the first request message sent by the management service function.

After receiving the first request message, the management service function may send a first message to the edge network open function, where the first message may include wireless network information, that is, the wireless network information may be directly sent to the edge network open function, and then the edge network open function may directly send the relevant parameter information to the application function.

Step 202, the first network entity receives a first reply message returned by the second network entity for the first request message.

In an embodiment of the present invention, the second network entity may include a session management function entity, and before the first network entity sends the first request message to the second network entity, the method further includes:

Wherein the second request message may be a third network entity instantiation request sent by the fourth network entity to the first network entity.

In practical applications, the fourth network entity may send a second request message of the third network entity to the first network entity, where the second request message may be an instantiation request, and the instantiation request may be implemented by calling a third network entity instantiation request interface in the network open function CAPIF interface, and may further instantiate the third network entity, for example, the central network open function may instantiate the edge network open function in the operator domain or the edge domain. The instantiation may also be achieved by other techniques.

In an example, as shown in fig. 3a, the central network opening function may instantiate an edge network opening function in the operator domain, and may authorize the edge network opening function to receive network parameters of the radio access network side and the 5G core network side through dynamic management. An operator domain may refer to a 5G core network and a UPF related server or server cluster. The interface from the edge network open function to the core network element (e.g., policy control function, etc.), and the interface from the edge network open function to the application function may both multiplex the interface from the original central network open function to the core network element, and from the edge network open function to the application function. The edge network open function may be instantiated on the UPF or on an operator domain server near the UPF.

In yet another example, as shown in fig. 3b, the central network opening function may instantiate an edge network opening function in the edge domain, and may authorize the edge network opening function to receive network parameters of the radio access network side and the 5G core network side through dynamic management. The edge domain may specifically refer to a third party deployed edge computing server, which may include a DN as well as an AF. The interface from the edge network open function to the core network element (e.g., policy control function, etc.), and the interface from the edge network open function to the application function may both multiplex the interface from the original central network open function to the core network element, and from the edge network open function to the application function.

The edge network open function is instantiated through the central network open function, the edge network open function can be instantiated in an operator domain and serves as a network element functional entity NF of the 5G core network, and can also be instantiated in an application function, so that the edge network open function can dynamically instantiate the edge network open function in the operator domain or the edge domain, and the central network open function can dynamically manage the authority of the edge network open function for acquiring network parameters.

After the first network entity receives the second request message sent by the fourth network entity, the first network entity may perform bidirectional authentication with the fourth network entity, for example, after the central network open function receives the second request message sent by the application function, the central network open function may perform bidirectional authentication with the application function.

In an embodiment of the present invention, the second network entity may include a user plane function entity, and after the first network entity sends the first request message to the second network entity, the method further includes:

In practical applications, the user plane function may send the information of the quality parameter to the session management function, and forward the information to the edge network open function by the session management function, for example, the application function may send a QoS parameter monitoring (QoS monitoring) request to the user plane function through the policy control function and the session management function, and after receiving the QoS parameter monitoring (QoS monitoring) request, the user plane function may send the information of the quality parameter, that is, the QoS related parameter (including a bidirectional delay of a packet, and at least one of an uplink and downlink data buffering condition, an uplink and downlink delay or a round-trip delay (round-trip delay), a throughput, and a transmission rate of the uplink and the downlink) to the session management function through a message (for example, an N4report message) of the N4 interface.

In an embodiment of the present invention, the second network entity may include a management service function entity, and after the first network entity sends the first request message to the second network entity, the method further includes:

In practical application, the management service function may directly send the wireless network information to the edge network open function after receiving the first request message, and then the edge network open function may directly send the relevant parameter information to the application function.

In an embodiment of the present invention, the second network entity may include a session management function entity, and further include:

the first network entity sends a third request message to the second network entity, wherein the third request message is used for canceling the operation of reporting parameters to the fourth network entity by the second network entity through the third network entity; the first network entity de-instantiates a third network entity.

In a specific implementation, the first network entity may send a third request message to the session management function entity, where the third request message may be used to cancel an operation of the session management function entity reporting the parameter to the fourth network entity through the third network entity, and the central network open function may cancel instantiation of the third network entity.

Specifically, the central network openness function may send a third request message to the session management function, where the third request message may be a parameter disable request (Parameterdisablerequest) or an event exposure subscription request (eventeExpo _ subscribe) or an event exposure unsubscribe request (eventeExpo _ unsubscribe), where the third request message includes indication information for cancelling direct delivery of the network parameter to the edgeNEF, and may also adopt other names, but the functions of the third request message are the same, and the request may be used to cancel an operation of the session management function reporting the parameter to the application function directly through the edge network openness function, and the central network openness function may configure and cancel instantiation of the central network openness function.

Referring to fig. 4, a flowchart illustrating 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, a second network entity may include a session management function entity, and a process of sending a first request message may be implemented by sending a fourth request message and a fifth request message, and specifically may include the following steps:

step 401, when the second network entity is a session management function entity, the first network entity sends the fourth request message to a fifth network entity, so that the fifth network entity sends the fifth request message to the second network entity according to the fourth request message;

in the process of dynamically managing instantiation of the edge network open function by the central network open function, when the second network entity is the session management function entity, the central network open function may send a fourth request message to the fifth network entity, so that the fifth network entity may send the fifth request message to the second network entity according to the fourth request message.

In an example, the first network entity may send the first request message to the second network entity through sending the fourth request message and the fifth request message, that is, the parameter information in the first request message may be obtained through the fourth request message and the fifth request message.

For example, as shown in fig. 5, the central network openness function may send a fourth request message to the fifth network entity, where the fourth request message may be a PCF policy authentication subscription request message (Npcf _ policy authorization _ subscribe), or a PCF policy authentication creation or update request message (Npcf _ policy authorization _ Create/update request), which may also be named otherwise, but has the same function. The request message may include an edge network openness function ID and, optionally, first network parameter type information, network parameter type, where the first network parameter type information may also be an event identifier (EventID), and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink-downlink data caching condition, uplink-downlink delay or round-trip delay (round-trip delay), throughput, uplink-downlink transmission rate, and the like), type information of a route change parameter UProutechange, and the like. Optionally, the fourth request message may not include the network parameter type information. When no relevant network parameter type information is indicated, the 5G core network element (e.g., SMF or AMF) may notify the AF of the specified default parameters or all parameters through localNEF. And, the central network open function may receive a related reply message for the fourth request message sent by the fifth network entity. Optionally, the fourth request message may further include an AF identifier and a local event notification (localnotification) identifier. The fifth network entity may instruct, through the local event notification identifier, a corresponding 5G core network element (e.g., SMF or AMF) to notify the specified AF of the specified type of network parameters through the edge network open function.

After the fifth network entity receives the fourth request message sent by the central network openness function, the fifth network entity may send a fifth request message to the session management function entity according to the fourth request message, where the fifth request message may be an SMF event exposure subscription request message (Nsmf _ evendexposurebscriberequest) or a PCF session management policy control update notification request message (Npcf _ SMPolicyControl _ UpdateNotifyRequest), and may also use other names, but the functions of the fifth request message are the same. The request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rate, and the like), type information of a route change parameter UProutechange, and the like. And, the fifth network entity may receive a related reply message for the fifth request message sent by the session management function entity. The PCF may notify the local time as part of a policy and charging control rule (PCCrule). The apparatus is configured to instruct the corresponding UPF to notify the AF of the specified QoS related parameter (e.g., at least one of uplink and downlink data buffering condition, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rate, etc.) through the localNEF.

In an example, if the unsubscribe request message (unsubscripte) is sent, the process may also be performed by a similar procedure, for example, a request message may be sent to the policy control function by the central network open function, where the request message may be an PCF policy authentication unsubscribe request message (Npcf _ PolicyAuthorization _ unpubscription request), or an PCF policy authentication creation or update request message (Npcf _ PolicyAuthorization _ Create/update request), which may also be named otherwise, but the functions of the messages are the same. The request message may include an edge network openness function ID and, optionally, first network parameter type information, network parameter type, where the first network parameter type information may also be an event identifier (EventID), and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink-downlink data caching condition, uplink-downlink delay or round-trip delay (round-trip delay), throughput, uplink-downlink transmission rate, and the like), type information of a route change parameter UProutechange, and the like. Optionally, the request message may not include the network parameter type information. When no relevant network parameter type information is indicated, the 5G core network element (e.g., SMF or AMF) may notify the AF of the specified default parameters or all parameters through localNEF. And, the central network open function may receive a relevant reply message for the request message sent by the policy control function. Optionally, the request message may further include an AF identifier and a local event notification (localnotification) identifier. The policy control function may instruct, through the local event notification identifier, a corresponding 5G core network element (e.g., SMF or AMF) to notify the specified AF of the specified type of network parameters through the edge network open function.

After the policy control function receives the Request message sent by the central network openness function, the policy control function may send a Request message to the session management function entity according to the Request message, where the Request message may be an SMF event exposure subscription Request message (Nsmf _ EventExposure _ unpubscribes Request) or a PCF session management policy control update notification Request message (Npcf _ SMPolicyControl _ UpdateNotifyRequest), and may also use other names, but the functions are the same. The request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rate, and the like), type information of a route change parameter UProutechange, and the like. And, the policy control function may receive a relevant reply message for the request message sent by the session management function entity. The PCF may remove the local time notification from the policy and charging control rules (pccrile), in which case the UPF cannot notify the AF of the relevant parameters via LocalNEF.

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

As an example, the first parameter information may be at least one of an uplink and downlink data buffering condition, an uplink and downlink delay or round-trip delay (round-tripdelay), a throughput, a transmission rate of the uplink and the downlink, and the like.

In practical applications, the session management function entity may send a sixth request message to the user plane function entity, so that the user plane function entity may send a third message to the application function through the local network openness function, where the third message may include at least one of uplink and downlink data buffering conditions, uplink and downlink delay or round-trip delay (round-trip delay), throughput, uplink and downlink transmission rates, and the like.

In an example, if the session management function entity is far from the edge domain or is a local network open function, the session management function entity may send a request message to the user plane function entity through the N4report interface, so that the user plane function entity may send the QoS parameters to the application function through the local network open function.

Step 402, the first network entity receives a first reply message returned by the second network entity for the first request message.

Referring to fig. 6, a flowchart illustrating 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, a second network entity may include a session management function entity, and a process of sending a first request message may be implemented by sending a seventh request message and an eighth request message, and specifically may include the following steps:

step 601, when the second network entity is a session management function entity, the first network entity sends the seventh request message to a sixth network entity, so that the sixth network entity sends the eighth request message to the second network entity according to the seventh request message;

in the process of dynamically managing instantiation of the edge network open function by the central network open function, when the second network entity is the session management function entity, the central network open function may send a seventh request message to the sixth network entity, so that the sixth network entity may send an eighth request message to the second network entity according to the seventh request message.

In an example, the first network entity may send the first request message to the second network entity through sending the seventh request message and the eighth request message, that is, the parameter information in the first request message may be obtained through the seventh request message and the eighth request message.

For example, as shown in fig. 7, the central network open function may send a seventh request message to the sixth network entity, where the seventh request message may expose a subscription request message (numdm _ EventExposure _ SubscribeRequest) for the UDM event, which may also be named otherwise, but its functions are the same. The request message may include an edge network openness function ID and first network parameter type information, NetworkParametertype, where the first network parameter type information may also be an event identifier (EventID), and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rates, and the like), type information of a route change parameter routechange, and the like. Optionally, the seventh request message may not include the network parameter type information. When no relevant network parameter type information is indicated, the 5G core network element (e.g., SMF or AMF) may notify the AF of the specified default parameters or all parameters through localNEF. And, the central network open function may receive a related reply message for the seventh request message sent by the sixth network entity. Optionally, the seventh request message may further include an AF identifier and a local event notification (localnotification) identifier. The sixth network entity may instruct, through the local event notification identifier, a corresponding 5G core network element (e.g., SMF or AMF) to notify the specified AF of the specified type of network parameters through the edge network open function.

After receiving the seventh request message sent by the central network openness function, the sixth network entity may send, according to the seventh request message, an eighth request message to the session management function entity, where the eighth request message may be an SMF event exposure subscription request message (Nsmf _ evendexposure _ SubscribeRequest), the request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching, uplink and downlink delay, or round-trip delay), throughput, and uplink and downlink transmission rate), and type information of a routing change parameter UProutechange. And, the sixth network entity may receive a related reply message for the eighth request message sent by the session management function entity.

Step 602, the first network entity receives a first reply message returned by the second network entity for the first request message.

Referring to fig. 8, a flowchart illustrating steps of a 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, and the second network entity may include a session management function entity side, and specifically may include the following steps:

step 801, the session management functional entity receives a first request message sent by the first network entity, and returns a first reply message for the first request message to the first network entity, where the first request message includes at least one piece of first network parameter type information, the first request message is used to enable the session management functional entity to send a first message to a third network entity according to a preset event trigger, and the first message includes at least one piece of partial network parameter information corresponding to the first network parameter type information;

The first network parameter type information may include at least one of:

the first message may include at least one of:

data network access identification, routing information.

In the process of dynamically managing instantiation of the edge network openness function by the central network openness function, the central network openness function may send a first request message to the session management function, where the first request message may be a parameter exposure available request (parameteravailable), and for example, the request may be an SMF event exposure subscription request message (Nsmf _ EventExposure _ SubscribeRequest) or an SMF event exposure registration message (Nsmf _ EventExposure _ Register), which may be named otherwise, but has the same function.

Step 802, according to the first request message, the session management function entity triggers a route change of the user equipment, and sends a first message to a third network entity.

After receiving the first request message, the session management function may trigger a route change to the ue, for example, a new user plane function may be selected, and the session management function may send a first message to the edge network open function, where the first message may be an SMF event exposure notification message (Nsmf _ evendexposurejnotify), which may also be named otherwise, but has the same function, where the first message may include a data network access identifier DNAI, routing information N6routing information, and the like.

In an embodiment of the present invention, the method further includes:

the session management functional entity receives the quality parameter information sent by the user plane functional entity; and the session management function entity forwards a second message to the third network entity, wherein the second message comprises the information of the quality parameter.

In practical application, the session management function may receive the information of the quality parameter sent by the user plane function, and then the session management function may forward the second message to the edge network open function, where the second message may include the information of the quality parameter.

For example, a QoS parameter monitoring (qosmontoring) request may be sent by the application function to the user plane function through the policy control function and the session management function, and the user plane function, upon receiving a QoS parameter monitoring (qosmoniting) request, may send information of the quality parameters, that is, the QoS related parameter (including the bidirectional delay of the packet, and may also be at least one of the uplink and downlink data buffering conditions, the uplink and downlink delay or the round-trip delay (round-tripdelay), the throughput, and the uplink and downlink transmission rate), is sent to the session management function through the N4 interface, and then the session management function may report the QoS related parameter to the edge network openness function by sending a second message, where the second message may be an SMF event exposure notification message (Nsmf _ EventExposure _ notify), it may also use other nomenclature but the functions are the same, and the edgeNEF may send the QoS related parameter information to the application function.

In an embodiment of the present invention, the method further includes:

In the process of dynamically managing the instantiation of the third network entity by the first network entity, the session management functional entity may receive a third request message sent by the first network entity, where the third request message may be used to cancel an operation of the session management functional entity reporting parameters to the fourth network entity through the third network entity, so that the first network entity may cancel the instantiation of the third network entity.

Specifically, the central network openness function may send a third request message to the session management function, where the third request message may be a parameter exposure disable request (Parameterdisablerequest) or an event exposure subscription request (eventeExpo _ subscribe) or an event exposure unsubscribe request (eventeExpo _ unsubscribe), where the third request message includes an indication information for cancelling the direct delivery of the network parameter to the edgeNEF, and the third request message may also be named otherwise, but has the same function, and may be used to cancel an operation of the session management function reporting the parameter to the application function directly through the edge network openness function, and the central network openness function may configure and cancel the instantiation of the central network openness function.

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

1. the application function may send a second request message of the edge network open function to the central network open function, where the second request message may be an instantiation request, and the instantiation request may be implemented by calling an edge network open function instantiation request interface in a network open function CAPIF interface;

2. the application function can perform bidirectional authentication with the open function of the central network;

3. the central network open function can instantiate an edge network open function, and the edge network open function can be instantiated in an operator domain, serves as a network element functional entity NF of the 5G core network, and can also be instantiated in an application function;

4. the central network openness function may send a first request message to the session management function, for example, the first request message may be a parameter exposure request (parameter exposure), which may also be named in other ways, but the functions of the first request message are the same, the request message may include an edge network openness function ID and first network parameter type information network parameter type, the first network parameter type information may include type information of a quality parameter QoS (for example, type information of an uplink and downlink data caching condition, an uplink and downlink delay or a round-trip delay (round-trip delay), throughput, a transmission rate of the uplink and the downlink, and the like), type information of a route change parameter uplink, and may receive a first reply message for the first request message sent by the session management function;

5. after receiving the first request message, the session management function may trigger a route change to the ue, for example, may select a new user plane function;

6. the session management function may send a first message to the edge network openness function, where the first message may include data network access identifier DNAI, routing information N6routing information, and the like, for example, the first message may be an SMF event exposure notification message (Nsmf _ evendexexposure _ notify), which may also adopt other names, but the functions are the same;

7. the application function may send a QoS parameter monitoring (qosmoniting) request to the user plane function through the policy control function and the session management function;

8. after receiving a QoS parameter monitoring (qosmoniting) request, the user plane function may send information of the quality parameter, that is, QoS related parameters (including bidirectional delay of a packet, and also at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, and uplink and downlink transmission rates) to the session management function through an N4 interface;

9. the session management function may report the QoS related parameter to the edge network open function by sending a second message, for example, the second message may be an SMF event exposure notification message (Nsmf _ eventeexposure _ notification), which may also be named by other names but has the same function, and the edge network open function may send the QoS related parameter information to the application function;

10. the central network openness function may send a first request message to the management service function, for example, the first request message may be parameter exposure availability requests (parameter exposure availability requests), which may also use other names, but the functions of the first request message are the same, the request message may include an edge network openness function ID and first network parameter type information networkparameter type, the first network parameter type information may include type information of wireless network information radioworkinformation, and may receive a first reply message for the first request message sent by the management service function;

11. after receiving the first request message, the management service function may directly send the wireless network information to the edge network open function, and the edge network open function may further directly send the relevant parameter information to the application function;

12. the central network openness function may send a third request message to the session management function, for example, the third request message may be a parameter exposure disable request (Parameterdisablerequest) or an event exposure subscription request (eventeExpo _ subscribe) or an event exposure unsubscribe request (eventeExpo _ unsubscribe), where the third request message includes an indication information for cancelling the direct delivery of the network parameter to the edgeNEF, and may also adopt other names, but the functions of the third request message are the same, and the third request message may be used to cancel the operation of the session management function reporting the parameter to the application function directly through the edge network openness function;

13. the central network open function may configure and un-instantiate the edge network open function.

Referring to fig. 10, a flowchart illustrating 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, where the second network entity may include a session management function entity, and the process of receiving a first request message sent by a first network entity may be implemented by receiving a fourth request message and a fifth request message, and specifically may include the following steps:

1001, the session management functional entity receives the fifth request message sent by a fifth network entity, where the fifth request message is sent according to the fourth request message sent by the first network entity and received by the fifth network entity;

in the process of dynamically managing instantiation of the edge network open function by the central network open function, the session management function entity may receive a fifth request message sent by the fifth network entity, where the fifth request message may be sent according to a fourth request message sent by the first network entity to the fifth network entity.

In an example, by receiving the fourth request message and the fifth request message, the session management function entity may receive the first request message sent by the first network entity, that is, the parameter information in the first request message may be obtained through the fourth request message and the fifth request message.

For example, the central network openness function may send a fourth request message to the fifth network entity, where the fourth request message may be an PCF policy authentication subscription request message (Npcf _ PolicyAuthorization _ subscribe request), or an PCF policy authentication creation or update request message (Npcf _ PolicyAuthorization _ Create/update request), and may also use other names, but the functions are the same. The request message may include an edge network openness function ID and, optionally, first network parameter type information, network parameter type, where the first network parameter type information may also be an event identifier (EventID), and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink-downlink data caching condition, uplink-downlink delay or round-trip delay (round-trip delay), throughput, uplink-downlink transmission rate, and the like), type information of a route change parameter UProutechange, and the like. Optionally, the fourth request message may not include the network parameter type information. When no relevant network parameter type information is indicated, the 5G core network element (e.g., SMF or AMF) may notify the AF of the specified default parameters or all parameters through localNEF. And, the central network open function may receive a related reply message for the fourth request message sent by the fifth network entity. Optionally, the fourth request message may further include an AF identifier and a local event notification (localnotification) identifier. The fifth network entity may instruct, through the local event notification identifier, a corresponding 5G core network element (e.g., SMF or AMF) to notify the specified AF of the specified type of network parameters through the edge network open function.

After the fifth network entity receives the fourth request message sent by the central network openness function, the session management function entity may receive a fifth request message sent by the fifth network entity according to the fourth request message, where the fifth request message may be an SMF event exposure subscription request message (Nsmf _ evendexposurebscriberequest) or a PCF session management policy control update notification request message (Npcf _ SMPolicyControl _ updatenotyrequest), and may also use other names, but the functions of the messages are the same. The request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rate, and the like), type information of a route change parameter UProutechange, and the like. And, the session management function entity may send a relevant reply message for the fifth request message to the fifth network entity. The PCF may notify the local time as part of a policy and charging control rule (PCCrule). The apparatus is configured to instruct the corresponding UPF to notify the AF of the specified QoS related parameter (e.g., at least one of uplink and downlink data buffering condition, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rate, etc.) through the localNEF.

Step 1002, according to the first request message, the session management function entity triggers a route change of the user equipment, and sends a first message to a third network entity.

Referring to fig. 11, a flowchart illustrating 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, a second network entity may include a session management function entity, and a process of receiving a first request message sent by the first network entity may be implemented by receiving a seventh request message and an eighth request message, and specifically may include the following steps:

step 1101, the session management functional entity receives the eighth request message sent by a sixth network entity, where the eighth request message is sent according to the seventh request message sent by the first network entity and received by the sixth network entity;

in the process of dynamically managing instantiation of the edge network open function by the central network open function, the session management function entity may receive an eighth request message sent by the sixth network entity, where the eighth request message may be sent according to a seventh request message sent by the first network entity to the sixth network entity.

In an example, the session management function entity may receive the first request message sent by the first network entity by receiving the seventh request message and the eighth request message, that is, the parameter information in the first request message may be obtained through the seventh request message and the eighth request message.

For example, the central network open function may send a seventh request message to the sixth network entity, where the seventh request message may be a UDM event exposure subscription request message (numdm _ EventExposure _ subscribe request), which may also be named otherwise, but the functions of the seventh request message are the same. The request message may include an edge network openness function ID and first network parameter type information, NetworkParametertype, where the first network parameter type information may also be an event identifier (EventID), and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching conditions, uplink and downlink delay or round-trip delay (round-tripdelay), throughput, uplink and downlink transmission rates, and the like), type information of a route change parameter routechange, and the like. Optionally, the seventh request message may not include the network parameter type information. When no relevant network parameter type information is indicated, the 5G core network element (e.g., SMF or AMF) may notify the AF of the specified default parameters or all parameters through localNEF. And, the central network open function may receive a related reply message for the seventh request message sent by the sixth network entity. Optionally, the seventh request message may further include an AF identifier and a local event notification (localnotification) identifier. The sixth network entity may instruct, through the local event notification identifier, a corresponding 5G core network element (e.g., SMF or AMF) to notify the specified AF of the specified type of network parameters through the edge network open function.

After the sixth network entity receives the seventh request message sent by the central network openness function, the session management function entity may receive an eighth request message sent by the sixth network entity according to the seventh request message, where the eighth request message may be an SMF event exposure subscription request message (Nsmf _ EventExposure _ subscribe request), the request message may include an edge network openness function ID and first network parameter type information NetworkParametertype, and the first network parameter type information may include type information of a quality parameter QoS (for example, at least one of uplink and downlink data caching condition, uplink and downlink delay or round-trip delay (round-trip), throughput, uplink and downlink transmission rate, etc.), type information of a routing change parameter UProutechange, etc. And, the session management function entity may send a relevant reply message for the eighth request message to the sixth network entity.

Step 1102, according to the first request message, the session management function entity triggers a route change of the user equipment, and sends a first message to a third network entity.

It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.

An embodiment of the present invention provides an apparatus for network communication, which may be applied to a first network entity, and the apparatus may be configured to:

In an embodiment of the invention, the first request message includes identification information of the third network entity.

In an embodiment of the present invention, the first request message further includes identification information of a fourth network entity, where the identification information of the fourth network entity is used to enable the second network entity to send the first message to the third network entity according to an application corresponding to the fourth network entity.

In an embodiment of the present invention, the second network entity includes a session management function entity, and when the second network entity is the session management function entity, the first network parameter type information includes at least one of the following:

the first message includes at least one of:

data network access identification, routing information.

In an embodiment of the present invention, the second network entity includes an access management function entity, and when the second network entity is the access management function entity, the first network parameter type information includes type information of a location of a user equipment, and the first message includes location information of the user equipment.

In an embodiment of the present invention, the second network entity includes a user plane function entity, and when the second network entity is the user plane function entity, the first network parameter type information includes at least one of the following:

type information of the delay, type information of the buffer status,

the first message includes at least one of:

round trip delay information, buffering information.

In an embodiment of the present invention, the second network entity includes a management service function entity, and when the second network entity is the management service function entity, the first network parameter type information includes type information of wireless network information, and the first message includes the wireless network information.

In an embodiment of the present invention, the second network entity includes a session management function entity, and before the first network entity sends the first request message to the second network entity, the method further includes:

In an embodiment of the present invention, the second network entity includes a user plane function entity, and after the first network entity sends the first request message to the second network entity, the method further includes:

In an embodiment of the present invention, the second network entity includes a management service function entity, and after the first network entity sends the first request message to the second network entity, the method further includes:

In an embodiment of the present invention, the second network entity includes a session management function entity, and further includes:

the first network entity de-instantiates a third network entity.

The second network entity includes a session management function entity, the process of sending the first request message is realized by sending a fourth request message and a fifth request message, and the sending of the first request message by the first network entity to the second network entity includes:

Further comprising:

The second network entity includes a session management function entity, the process of sending the first request message is realized by sending a seventh request message and an eighth request message, and the sending of the first request message by the first network entity to the second network entity includes:

An embodiment of the present invention provides an apparatus for network communication, which may be applied to a second network entity, where the second network entity may include a session management function entity, and the apparatus may be configured to:

In an embodiment of the present invention, the first network parameter type information includes at least one of the following:

the first message includes at least one of:

data network access identification, routing information.

In an embodiment of the present invention, the session management functional entity receives information of the quality parameter sent by the user plane functional entity;

In an embodiment of the present invention, the apparatus is further configured to:

The process of receiving the first request message sent by the first network entity is implemented by receiving a fourth request message and a fifth request message, and the receiving, by the session management function entity, the first request message sent by the first network entity includes:

Further comprising:

The process of receiving the first request message sent by the first network entity is implemented by receiving a seventh request message and an eighth request message, and the receiving, by the session management function entity, the first request message sent by the first network entity includes:

An embodiment of the present invention also provides an electronic device, which may include a processor, a memory, and a computer program stored on the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the method for network communication as above.

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 for network communication as above.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one skilled in the art, 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 present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, 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 data processing terminal 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 data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal 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 of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be 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. Also, 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 an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The method and apparatus for network communication, the electronic device, and the storage medium provided above are introduced in detail, and a specific example is applied in this document to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understand the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A method for network communication, applied to a first network entity, comprising:

2. The method of claim 1, wherein the first request message comprises identification information of a third network entity.

3. The method according to claim 1 or 2, wherein the first request message further includes identification information of a fourth network entity, and the identification information of the fourth network entity is used to enable the second network entity to send the first message to the third network entity according to an application corresponding to the fourth network entity.

4. The method of claim 1, wherein the second network entity comprises a session management function entity, and when the second network entity is the session management function entity, the first network parameter type information comprises at least one of the following:

the first message includes at least one of:

data network access identification, routing information.

5. The method of claim 1, wherein the second network entity comprises an access management function entity, and when the second network entity is the access management function entity, the first network parameter type information comprises type information of a user equipment location, and the first message comprises user equipment location information.

6. The method of claim 1, wherein the second network entity comprises a user plane function entity, and when the second network entity is the user plane function entity, the first network parameter type information comprises at least one of the following:

type information of the delay, type information of the buffer status,

the first message includes at least one of:

round trip delay information, buffering information.

7. The method of claim 1, wherein the second network entity comprises a management service function entity, and when the second network entity is the management service function entity, the first network parameter type information comprises type information of wireless network information, and the first message comprises the wireless network information.

8. The method of claim 1, wherein the second network entity comprises a session management function entity, and before the first network entity sends the first request message to the second network entity, the method further comprises:

9. The method of claim 8, wherein the second network entity comprises a session management function entity, and before the first network entity sends the first request message to the second network entity, the method further comprises:

10. The method of claim 1, wherein the second network entity comprises a user plane function entity, and further comprising, after the first network entity sends the first request message to the second network entity:

11. The method of claim 1, wherein the second network entity comprises a management service function entity, and further comprising, after the first network entity sends the first request message to the second network entity:

12. The method of claim 11, wherein the second network entity comprises a session management function entity, further comprising:

the first network entity de-instantiates a third network entity.

13. The method of claim 1, wherein the second network entity comprises a session management function entity, and wherein the sending the first request message is performed by sending a fourth request message and a fifth request message, and wherein the sending the first request message by the first network entity to the second network entity comprises:

14. The method of claim 13, further comprising:

15. The method of claim 1, wherein the second network entity comprises a session management function entity, and wherein the sending the first request message is performed by sending a seventh request message and an eighth request message, and wherein the sending the first request message by the first network entity to the second network entity comprises:

16. A method for network communication, applied to a second network entity, wherein the second network entity includes a session management function entity, and comprising:

17. The method of claim 16, wherein the first request message comprises identification information of a third network entity.

18. The method according to claim 16 or 17, wherein the first request message further includes identification information of a fourth network entity, and the identification information of the fourth network entity is used to enable the second network entity to send the first message to the third network entity according to an application corresponding to the fourth network entity.

19. The method of claim 16, wherein the first network parameter type information comprises at least one of:

the first message includes at least one of:

data network access identification, routing information.

20. The method of claim 16, further comprising:

21. The method of claim 16, further comprising:

22. The method according to claim 16, wherein the receiving the first request message sent by the first network entity is implemented by receiving a fourth request message and a fifth request message, and the receiving, by the session management function entity, the first request message sent by the first network entity includes:

23. The method of claim 22, further comprising:

24. The method according to claim 16, wherein the receiving the first request message sent by the first network entity is implemented by receiving a seventh request message and an eighth request message, and the receiving, by the session management function entity, the first request message sent by the first network entity includes:

25. An apparatus for network communication, applied to a first network entity, the apparatus configured to:

26. An apparatus for network communication, wherein the apparatus is applied to a second network entity, and the second network entity includes a session management function entity, and the apparatus is configured to:

27. An electronic device comprising a processor, a memory, and a computer program stored on the memory and capable of running on the processor, the computer program, when executed by the processor, implementing a method of network communication according to any one of claims 1 to 24.

28. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of network communication according to any one of claims 1 to 24.