Method, apparatus and system for requesting application functionality - Patents.com

Abstract

The present application provides a method, apparatus, and system for requesting an application function. The method includes: an enabler server determines whether to perform traffic influence in advance based on first judgment information. If it is determined to perform traffic influence in advance, the enabler server sends an application function request message in advance, where the application function request message is for requesting to perform traffic influence for one or more application servers. According to the technical solution provided in the present application, in order to help improve the efficiency of providing application services by edge data networks for various terminal devices, help improve the experience of obtaining application services by terminal devices, and help reduce the waste of network resources, a judgment is made first based on application information or instruction information before traffic influence is triggered, and then a corresponding operation is performed based on the judgment result.

Description

[Technical field]

[0001] This application claims priority to Chinese Patent Application No. 202210119272.8, entitled "Method, Apparatus, and System for Requesting Application Functions," filed with the China National Intellectual Property Office on February 8, 2022, which is incorporated herein by reference in its entirety.

[0002] The present application relates to the field of communications, and more particularly, to a method, apparatus, and system for requesting application functionality. [Background technology]

[0003] The standalone (SA) 6 standard defines an edge enabler server (EES) platform discovery procedure and an edge application server (EAS) discovery procedure. The edge data network requires the core network to trigger traffic influence for EASs determined using the EAS discovery procedure. The opportunity to perform EAS discovery and / or traffic influence is worth considering. Summary of the Invention

[0004] The present application provides methods, apparatus, and systems for requesting application functionality to determine opportunities to trigger application server discovery and / or opportunities to trigger traffic influence, help reduce waste of network resources, and help improve the experience of terminal device users. [Means for solving the problem]

[0005] According to a first aspect, there is provided a method for requesting an application function, the method including:

[0006] The enabler server determines whether to proactively perform traffic influence based on the first determination information.

[0007] To help the edge data network determine the opportunity to trigger traffic influence based on various circumstances, before performing traffic influence, the enabler server first determines whether to perform traffic influence in advance. If it is determined to perform traffic influence in advance, to help reduce delays in obtaining application services by application clients and to help improve the application service experience of terminal device users, for application clients with higher delay requirements, user plane path optimization may be completed for the application clients before the application clients exchange data with the application server. If it is determined not to perform traffic influence in advance, to help reduce situations where user plane function network elements included in the optimized user plane are uselessly occupied during a certain period (e.g., during the period between the completion of traffic influence and the application client's data exchange with the application server) and to help reduce waste of network resources, this helps reduce situations where user plane paths are pre-optimized for application clients with lower delay requirements or for application clients that do not temporarily require edge computing services.

[0008] In one possible implementation, if it is determined that traffic influence is to be performed in advance, the enabler server sends an application capability request message in advance to request that traffic influence be performed for one or more application servers.

[0009] The enabler server can obtain a positive judgment result based on the first judgment information. In order to help fully utilize the network resources of the edge data network, for an edge data network with more sufficient network resources, the enabler server can provide application services to more terminal devices as much as possible by obtaining a positive judgment result. In order to help improve the usage experience of the terminal device user, for an application client with a higher delay requirement, traffic influence is performed in advance for the application client, so that the delay in obtaining the application service by the application client can be reduced.

[0010] In another possible implementation, if it is determined that traffic influence is not to be performed in advance, the enabler server does not send an application capability request message in advance, which is to request that traffic influence be performed for one or more application servers.

[0011] The enabler server can obtain a negative judgment result based on the first judgment information, which can help reduce the situation where a user plane function network element included in the optimized user plane is occupied during a certain period (for example, during the period between the completion of traffic influence and the data exchange between the application client and the application server), help reserve network resources and edge data network resources, help ensure the application service quality of the terminal device that has performed the access, and help improve the stability of providing application services by the edge data network, so that in the case of an edge data network where the network resources are insufficient or insufficient, the enabler server can minimize the situation where a user plane path is optimized for a terminal device that does not temporarily require edge computing services by obtaining a negative judgment result.

[0012] In yet another possible implementation, if it is determined that traffic influence is not to be pre-executed, the enabler server stores a determination result indicating that traffic influence is not to be pre-executed.

[0013] To help improve the efficiency of the enabler server in determining whether to perform traffic influence in advance, the enabler server can determine whether the enabler client will perform traffic influence in advance next time based on a judgment result indicating not to perform traffic influence in advance, and does not need to determine whether to perform traffic influence in advance based on application information.

[0014] In yet another possible implementation, if it is determined that traffic influence is not to be pre-executed, the enabler server transmits a determination result indicating that traffic influence is not to be pre-executed to the enabler client.

[0015] In this specification, the determination result instructing not to proactively perform traffic influence may also be referred to as instruction information for not proactively performing traffic influence.

[0016] Optionally, the enabler client stores a decision result indicating not to proactively perform traffic influence.

[0017] The enabler client may determine whether the application client will proactively perform application server discovery and / or traffic influence next time based on the determination result indicating not to proactively perform traffic influence.

[0018] Optionally, the enabler server further sends information about the one or more application servers to the enabler client, and the enabler client determines the selected application server based on the information about the one or more application servers.

[0019] Optionally, the enabler server determines the selected application server based on the one or more application servers, and the enabler client sends information about the one or more application servers or about the selected application server to the application client.

[0020] Optionally, the application client can determine a selected application server based on information about the one or more application servers to request the selected application server to trigger traffic influence.

[0021] Optionally, the enabler client sends information about the selected application server to the enabler server.

[0022] To provide multiple criteria for the enabler server to determine whether to proactively perform traffic influence, the enabler server can determine whether to proactively trigger traffic influence based on the declared information or declared event about the selected application server, which helps to improve the efficiency of providing services to various terminal devices or application clients by the edge data network, and helps to improve the stability of obtaining application services of the edge data network by the terminal devices.

[0023] Optionally, the application client sends instruction information for triggering traffic influence to the selected application server, the instruction information being for requesting the selected application server to trigger traffic influence for the selected application server.

[0024] To help improve the efficiency with which application services provided by application servers are obtained by application clients, application clients can directly request selected application servers to trigger traffic influence.

[0025] Optionally, the application client sends instruction information to the enabler client for triggering application server discovery in advance and / or for performing traffic influence in advance based on a judgment result indicating not to perform traffic influence in advance.

[0026] Optionally, the enabler client sends instruction information to the enabler server for proactively performing application server discovery and / or proactively performing traffic influence.

[0027] The judgment result instructing not to proactively perform traffic influence may be sent to the enabler client and used by the enabler client to judge whether to proactively perform application server discovery and / or traffic influence for the same terminal device or application client next time. To improve the efficiency of the judgment execution by the enabler client, the enabler client does not need to judge whether to proactively perform application server discovery and / or traffic influence based on application information.

[0028] In this technical solution, the first determination information is used to determine an opportunity to trigger traffic influence. If it is determined to perform traffic influence in advance, this helps reduce the delay in obtaining application services by application clients with higher delay requirements. If it is determined not to perform traffic influence in advance, this helps reduce the situation in which the terminal device is not actually provided with services in an optimized user plane during a certain period (e.g., during the period between the completion of traffic influence and the data exchange between the application client and the application server), helps reduce the waste of network resources, and helps improve the application service experience of the terminal device user.

[0029] Referring to the first aspect, in some implementations of the first aspect, the first judgment information includes application information, which includes one or more of the following information: application type, application server type, delay requirements, etc.

[0030] The application type, application server type, delay requirement, etc. may represent the specific attributes of the application client. To help improve the adaptability of the enabler server in providing services to various terminal devices, whether to perform traffic influence in advance is determined based on the specific attributes of the application client.

[0031] In one possible implementation, the application server type may be determined based on the service key performance indicators of the server, which include one or more of the following information: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0032] The server type is determined based on one or more kinds of information. In order to help simplify the decision process and message content for the enabler server to determine whether to proactively perform traffic influence, and to help improve the efficiency of the enabler server to determine whether to proactively perform traffic influence, the enabler server determines the enabler service type based on some basic information of the application server, so as to determine whether to proactively perform traffic influence.

[0033] Referring to the first aspect, in some implementations of the first aspect, the first judgment information includes instruction information, which instructs to perform application server discovery in advance and / or to perform traffic influence in advance.

[0034] To determine whether to send a request message to perform traffic influence for the application server, the enabler server obtains indication information, and determines whether to perform traffic influence in advance based on the indication information. The enabler server can refer to the actual running state and actual requirements of the application client to perform corresponding responses. For each indication information, the enabler server can perform corresponding responses, so that the application server can better provide application services to the application client.

[0035] In one possible implementation, the delay requirement is a delay requirement of a first packet, the delay requirement of the first packet being a delay requirement of a first data packet sent by the application client to one or more application servers.

[0036] The first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, ie, the first data packet in a data exchange between the application client and the application server.

[0037] The delay requirement of the first packet may alternatively indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0038] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0039] In another possible implementation, the delay requirement further indicates the delay requirement of the application client or the delay requirement of an application server required by the application client.

[0040] In one possible implementation, the enabler server may further determine whether to proactively perform traffic influence based on one or more of the following information: Information regarding a selected application server declared by an enabler client or a declaration event, instruction information instructing an application client to transmit data declared by an enabler client or a declaration event, or a declaration event in which an enabler client declares a request message to perform traffic influence in advance.

[0041] In order to provide more decision-making methods for the enabler server and help improve the applicability of the enabler server in providing services for various terminal devices or in various operating conditions, the enabler server can determine whether to perform traffic influence in advance based on information content or declared events declared by the enabler client.

[0042] Referring to the first aspect, in some implementations of the first aspect, the enabler server sends a discovery response message, which indicates that traffic influence is being performed for one or more application servers.

[0043] The enabler server feeds back the selected application server and a result indicating that traffic influence is performed for the application server to the enabler client. The enabler client can select the application server based on the feedback information and can preferentially feed back the application server on which traffic influence is performed to the application client, so that the application client can be connected to the application server to obtain the application service.

[0044] Optionally, the discovery response message further indicates whether traffic influence has been completed for one or more application servers.

[0045] Alternatively, the discovery response message may further indicate whether one or more application servers have an optimized user plane path or whether user plane path optimization has been completed.

[0046] To help improve the efficiency of obtaining application services of application servers by application clients, the application clients can be directly connected to application servers where traffic influence has been completed.

[0047] Referring to the first aspect, in some implementations of the first aspect, the enabler server proactively sends a first instruction message to the selected application server, the first instruction message instructing to trigger traffic influence in advance, and the one or more application servers include the selected application server.

[0048] It should be understood that the first instruction message instructs the selected application server to pre-trigger traffic influence for the selected application server.

[0049] To help improve the efficiency of performing traffic influence by the core network and to help improve the efficiency of obtaining application services by terminal devices, the enabler server can directly request a selected application server to trigger traffic influence, without having to request the core network to perform traffic influence for one or more application servers.

[0050] In one possible implementation, the first instruction message further includes application information and / or instruction information, and the selected application server can determine whether to perform traffic influence in advance based on the application information and / or the instruction information.

[0051] To help the edge data network improve the mechanism for triggering traffic influence and to help improve the efficiency of providing application services to terminal devices by the edge data network, the application server determines whether to perform traffic influence.

[0052] According to a second aspect, there is provided a method for requesting an application function, the method including:

[0053] The enabler server determines whether to proactively perform traffic influence based on the first determination information.

[0054] To help the edge data network determine the opportunity to trigger traffic influence based on various circumstances, before performing traffic influence, the enabler server first determines whether to perform traffic influence in advance. If it is determined to perform traffic influence in advance, to help reduce the delay in obtaining application services by application clients and to help improve the application service experience of terminal device users, for application clients with higher delay requirements, user plane path optimization may be completed for the application clients before the application clients exchange data with the application server. If it is determined not to perform traffic influence in advance, to help reduce the situation where user plane function network elements included in the optimized user plane are occupied for a certain period of time (e.g., the period between the completion of traffic influence and the application client's data exchange with the application server) and to help reduce the waste of network resources, this helps reduce the situation where user plane paths are immediately optimized for application clients with lower delay requirements or for application clients that do not temporarily require edge computing services.

[0055] In one possible implementation, if it is determined that traffic influence is to be performed in advance, the enabler server sends an instruction message to the selected application server in advance to trigger traffic influence, the instruction message instructing that traffic influence is to be triggered in advance.

[0056] It should be appreciated that the instruction message instructs the selected application server to pre-trigger traffic influence for the selected application server.

[0057] The enabler server can obtain a positive judgment result based on the first judgment information. In order to help fully utilize the network resources of the edge data network, for an edge data network with more sufficient network resources, the enabler server can provide application services to more terminal devices as much as possible by obtaining a positive judgment result. In order to help improve the application service experience of the terminal device user, for an application client with a higher delay requirement, traffic influence is performed in advance for the application client, so that the delay in obtaining the application service by the application client can be reduced.

[0058] In another possible implementation, if it is determined that traffic influence is not to be performed in advance, the enabler server does not send an instruction message to trigger traffic influence in advance, and the instruction message instructs that traffic influence is to be triggered in advance.

[0059] It should be appreciated that the instruction message instructs the selected application server to pre-trigger traffic influence for the selected application server.

[0060] The enabler server can obtain a negative judgment result based on the first judgment information, which can help reduce the situation where a user plane function network element included in the optimized user plane is occupied during a certain period (for example, during the period between the completion of traffic influence and the data exchange between the application client and the application server), help reserve network resources and edge data network resources, help ensure the application service quality of the terminal device that has performed the access, and help improve the stability of providing application services by the edge data network, so that in the case of an edge data network where the network resources are insufficient or insufficient, the enabler server can minimize the situation where a user plane path is optimized for a terminal device that does not temporarily require edge computing services by obtaining a negative judgment result.

[0061] In yet another possible implementation, if it is determined that traffic influence is not to be pre-executed, the enabler server stores a determination result indicating that traffic influence is not to be pre-executed.

[0062] To help improve the efficiency of the enabler server in determining whether to perform traffic influence in advance, the enabler server can determine whether the enabler client will perform traffic influence in advance next time based on a judgment result indicating not to perform traffic influence in advance, and does not need to determine whether to perform traffic influence in advance based on application information.

[0063] In yet another possible implementation, if it is determined that traffic influence is not to be pre-executed, the enabler server transmits a determination result indicating that traffic influence is not to be pre-executed to the enabler client.

[0064] In this specification, the determination result instructing not to proactively perform traffic influence may also be referred to as instruction information for not proactively performing traffic influence.

[0065] Optionally, the enabler client stores a decision result indicating not to proactively perform traffic influence.

[0066] To help improve the efficiency of decision-making by the enabler client, the enabler client can determine whether the application client will proactively perform application server discovery and / or traffic influence next time based on a decision result indicating not to proactively perform traffic influence.

[0067] Optionally, the enabler client transmits a decision to the application client indicating not to proactively perform traffic influence.

[0068] To help improve the efficiency of obtaining application services by the application client, the application client may determine that a previous request failed based on the received judgment result indicating not to perform traffic influence in advance, and thereby change the request method or change the request path.

[0069] Optionally, the enabler server further sends information about the selected application server to the enabler client.

[0070] Optionally, the enabler client sends information about the selected application server to the application client.

[0071] Optionally, the application client sends instruction information for triggering traffic influence to the selected application server, the instruction information being for requesting the selected application server to trigger traffic influence for the selected application server.

[0072] To help simplify the procedure of triggering traffic influence and improve the efficiency of obtaining application services by application clients, after obtaining information about a selected application server, the application client can directly request the selected application server to perform traffic influence.

[0073] Optionally, the application client sends instruction information to the enabler client for triggering application server discovery in advance and / or for performing traffic influence in advance based on a judgment result indicating not to perform traffic influence in advance.

[0074] Optionally, the enabler client sends instruction information to the enabler server for proactively performing application server discovery and / or proactively performing traffic influence.

[0075] After obtaining a judgment result instructing not to pre-execute traffic influence, the application client directly sends instruction information to the enabler client, and then the enabler client sends the instruction information to the enabler server. To help improve the success rate of triggering traffic influence for the application client, traffic influence is pre-triggered by using the instruction information.

[0076] In this technical solution, the first judgment information is used to judge an opportunity to trigger traffic influence. If it is judged to perform traffic influence in advance, this helps to reduce the delay in obtaining application services by application clients with higher delay requirements. If it is judged not to perform traffic influence in advance, this helps to reduce the situation in which the user plane function network elements included in the optimized user plane are occupied for a certain period of time, helps to reduce the waste of network resources, and helps to improve the application service experience of the terminal device user.

[0077] Referring to the second aspect, in some implementations of the second aspect, the first judgment information includes application information, which includes one or more of the following information: application type, application server type, delay requirements, etc.

[0078] The application type, application server type, delay requirement, etc. may represent the specific attributes of the application client. To help improve the adaptability of the enabler server in providing services to various terminal devices, whether to perform traffic influence in advance is determined based on the specific attributes of the application client.

[0079] In one possible implementation, the application server type may be determined based on the service key performance indicators of the server, which include one or more of the following information: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0080] The server type is determined based on one or more kinds of information. In order to help simplify the decision process and message content for the enabler server to determine whether to proactively perform traffic influence, and to help improve the efficiency of the enabler server to determine whether to proactively perform traffic influence, the enabler server determines the enabler service type based on some basic information of the application server, so as to determine whether to proactively perform traffic influence.

[0081] Referring to the second aspect, in some implementations of the second aspect, the first judgment information includes instruction information, which instructs to perform application server discovery in advance and / or to perform traffic influence in advance.

[0082] To determine whether to send a request message to perform traffic influence for the application server, the enabler server obtains indication information, and determines whether to perform traffic influence in advance based on the indication information. The enabler server can refer to the actual running state and actual requirements of the application client to perform corresponding responses. For each indication information, the enabler server can perform corresponding responses, so that the application server can better provide application services to the application client.

[0083] In one possible implementation, the delay requirement is a delay requirement of a first packet, the delay requirement of the first packet being a delay requirement of a first data packet sent by the application client to one or more application servers.

[0084] The first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, ie, the first data packet in a data exchange between the application client and the application server.

[0085] The delay requirement of the first packet may alternatively indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0086] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0087] In another possible implementation, the delay requirement further indicates the delay requirement of the application client or the delay requirement of an application server required by the application client.

[0088] In one possible implementation, the enabler server may further determine whether to proactively perform traffic influence based on one or more of the following information: Information regarding a selected application server declared by an enabler client or a declaration event, instruction information instructing an application client to transmit data declared by an enabler client or a declaration event, or a declaration event in which an enabler client declares a request message to perform traffic influence in advance.

[0089] In order to provide more decision-making methods for the enabler server and help improve the applicability of the enabler server in providing services for various terminal devices or in various operating conditions, the enabler server can determine whether to perform traffic influence in advance based on information content or declared events declared by the enabler client.

[0090] Referring to the second aspect, in some implementations of the second aspect, the enabler server sends a discovery response message, which indicates that traffic influence is being performed for one or more application servers.

[0091] The enabler server feeds back the selected application server and the result indicating that traffic influence is being performed for the application server to the enabler client. The enabler client can select the application server based on the feedback information and can preferentially feed back the application server for which traffic influence is completed or the application server with the optimized user plane path to the application client, so that the application client can be connected to the application server to obtain the application service.

[0092] Optionally, the discovery response message further indicates whether traffic influence has been completed for one or more application servers.

[0093] Alternatively, the discovery response message may further indicate whether one or more application servers have an optimized user plane path or whether user plane path optimization has been completed.

[0094] To help improve the efficiency of obtaining application services of application servers by application clients, the application clients can be directly connected to application servers where traffic influence has been completed.

[0095] According to a third aspect, there is provided a method for requesting an application function, the method including:

[0096] The enabler client determines whether to pre-perform application server discovery based on the second determination information.

[0097] In order to help the enabler client determine the opportunity to trigger application server discovery based on various situations, before triggering application server discovery, the enabler client first determines whether to perform application server discovery in advance. In order to help reduce the delay in obtaining application services by the application client and help improve the application service experience of the terminal device user, if it is determined to perform application server discovery in advance, for an application client having a higher delay requirement, an application server may be discovered in advance for the application client, so that traffic influence is performed for the discovered application server before the application client exchanges data with the application server. In order to help improve the effectiveness of communication signaling exchange between the enabler client and the edge data network, to some extent help reduce the situation in which the user plane function network element included in the optimized user plane is occupied during a certain period, and to help reduce the waste of network resources, if it is determined not to perform application server discovery in advance, the edge data network does not perform application server discovery for the application client before the application client exchanges data with the application server, and does not trigger traffic influence for the application client during this period.

[0098] In one possible implementation, if it is determined that application server discovery is to be performed in advance, the enabler client sends an application server discovery request message in advance, which is to request the discovery of one or more application servers, and the one or more application servers are configured to provide application services to the application client.

[0099] In order to help fully utilize network resources of the edge data network, the enabler client can obtain a positive judgment result based on the second judgment information, and by obtaining the positive judgment result, the enabler client can provide services to more application clients as much as possible. For application clients with higher delay requirements, application server discovery is performed in advance for the application clients, in order to help the application clients further request to perform traffic influence in advance for the discovered application servers, thereby helping to reduce the delay in obtaining application services by the application clients, and helping to improve the application service experience of the terminal device user.

[0100] In another possible implementation, if it is determined that application server discovery is not to be performed in advance, the enabler client does not send an application server discovery request message in advance, which is for requesting to discover one or more application servers, and the one or more application servers are configured to provide application services to the application client.

[0101] In order to help guarantee the quality of application services obtained by the application client that has performed the access and to help reduce the power consumption of the terminal device, the enabler client can obtain a negative judgment result based on the second judgment information, and the enabler client can reduce the access to the edge data network for the new application client as much as possible by obtaining a negative judgment result. In addition, in order to help improve the effectiveness of communication signaling exchange between the enabler client and the edge data network, to some extent help reduce the situation in which the user plane function network element included in the optimized user plane is occupied during a certain period (e.g., during the period between the completion of traffic influence and the data exchange between the application client and the application server), and to help reduce the waste of network resources or edge data network resources, it is determined not to perform application server discovery in advance, so that the edge data network does not perform traffic influence for the application client before the application client exchanges data with the application server.

[0102] In yet another possible implementation, if it is determined that application server discovery should not be performed proactively, the enabler client stores a determination result indicating that application server discovery should not be performed proactively.

[0103] To help improve the efficiency of the enabler client's determination of whether to perform application server discovery in advance, the enabler client can determine whether to perform application server discovery in advance next time for the application client based on a determination result indicating not to perform application server discovery in advance.

[0104] Optionally, the enabler client sends a decision to the application client indicating not to pre-perform application server discovery.

[0105] Optionally, the application client sends instructions to the enabler client to perform application server discovery in advance and / or instructions to perform traffic influence in advance based on a judgment result indicating not to perform application server discovery in advance.

[0106] To help improve the efficiency of triggering application server discovery for an application client, the application client can re-prepare a next request to an enabler client based on a determination result indicating not to perform application server discovery in advance, for example, allowing the request message to include an instruction message to perform application server discovery in advance.

[0107] In one possible implementation, the enabler client determines whether to perform traffic influence in advance based on the second judgment information, and if it determines to perform traffic influence in advance, it decides to perform application server discovery in advance, and if it determines not to perform traffic influence in advance, it decides not to perform application server discovery in advance.

[0108] In order to help improve the efficiency of determining an application server having an optimized user plane path by an application client and to help improve the efficiency of obtaining an application service by an application client, it is determined to pre-perform application server discovery by determining to pre-perform traffic influence, so that traffic influence can be performed for the application server determined using the application server discovery procedure.

[0109] In order to help enabler clients provide services to application clients having different types and different operating states, and to improve the service efficiency and service quality of enabler clients, the implementation of this technical solution helps enabler clients improve the trigger mechanism for triggering application server discovery, so that the enabler client triggers application server discovery when a judgment condition is met.

[0110] In this technical solution, the second judgment information is used to judge the opportunity to perform application server discovery. If it is judged to perform application server discovery in advance, this helps to reduce the delay in obtaining application services by application clients with higher delay requirements. If it is judged not to perform application server discovery in advance, this helps to improve the effectiveness of communication signaling exchange between the enabler client and the edge data network, helps to reduce the situation in which the optimized user plane does not actually provide services to the terminal device within a certain period of time, and helps to reduce the waste of network resources.

[0111] Referring to the third aspect, in some implementations of the third aspect, the second judgment information includes application information, which includes one or more of the following information: application type, application server type, delay requirements, etc.

[0112] The application type, application server type, delay requirement, etc. may represent the specific attributes of the application client. To help improve the adaptability of the enabler server in providing services to various terminal devices, whether to perform application server discovery in advance is determined based on the specific attributes of the application client.

[0113] In one possible implementation, the application server type may be determined based on the service key performance indicators of the server, which include one or more of the following information: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0114] The server type is determined based on one or more kinds of information. In order to help simplify the decision process and message content for the enabler server to determine whether to proactively perform traffic influence, and to help improve the efficiency of determining whether to proactively perform application server discovery by the enabler server, the enabler server determines the enabler service type based on some basic information of the application server, so as to determine whether to proactively perform traffic influence.

[0115] The implementation of this technical solution helps the enabler client to make judgments and perform corresponding responses based on the attributes of the application clients, helps to improve the adaptability of providing services to different types of clients, helps to improve the overall service efficiency of the enabler client, helps to improve the application service experience of the terminal device user, and helps to improve the service quality of the edge data network.

[0116] Referring to the third aspect, in some implementations of the third aspect, the second judgment information includes instruction information, which instructs to perform application server discovery in advance and / or to perform traffic influence in advance.

[0117] The indication information can reflect the application client's relevant requirements for the application client's operating environment. The enabler client obtains the indication information, and thereby, based on the indication information, judges whether to pre-execute traffic influence for the application client, and judges whether to pre-send an application server discovery request message to trigger application server discovery. The enabler client can refer to the actual operating state and actual requirements of the application client to perform corresponding responses. In addition, for each indication information, the enabler client can perform corresponding responses, so that the enabler client can better provide services to the application client.

[0118] The implementation of this technical solution helps improve the triggering mechanism for enabler clients to trigger application server discovery, helps enable enabler clients to provide services to application clients with different operating states and operating requirements, helps improve the application service experience of terminal device users, and helps to improve the service quality of edge data networks to a certain extent.

[0119] In one possible implementation, the delay requirement is a delay requirement of a first packet, the delay requirement of the first packet being a delay requirement of a first data packet sent by the application client to one or more application servers.

[0120] The first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, ie, the first data packet in a data exchange between the application client and the application server.

[0121] The delay requirement of the first packet may alternatively indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0122] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0123] Referring to the third aspect, in some implementations of the third aspect, the enabler client receives a discovery response message sent by the enabler server, which indicates that traffic influence is being performed for one or more application servers.

[0124] The enabler client sends a first response message to the application client, the first response message including information regarding the one or more application servers, the first response message further indicating that traffic influence is being performed for the one or more application servers.

[0125] The enabler client can select one or more application servers based on the received discovery response message, and can preferentially feed back to the application client the application servers on which traffic influence has been performed, so that the application client can be connected to the application servers to obtain application services.

[0126] Optionally, the discovery response message further indicates whether traffic influence has been completed for one or more application servers, whether one or more application servers have optimized user plane paths, or whether user plane path optimization has been completed.

[0127] Optionally, the first response message further indicates whether traffic influence has been completed for one or more application servers, whether one or more application servers have optimized user plane paths, or whether user plane path optimization has been completed.

[0128] To help improve the efficiency of obtaining application services of application servers by application clients, the application clients can be directly connected to application servers where traffic influence has been completed.

[0129] After obtaining the information about the application server and the indication information indicating whether the traffic influence for the application server has been completed, the enabler client can further send the information about the application server and the indication information to the application client, and the application client can determine which application server is to obtain the application service based on the indication information.

[0130] The implementation of this technical solution helps to improve the service efficiency of the enabler client and the enabler server, helps to improve the application service experience of the terminal device user, helps to reduce the signaling waste caused by extra interactions between the enabler client and the enabler server, helps to reduce unnecessary user plane route optimization, and helps to reduce the waste of network resources.

[0131] According to a fourth aspect, there is provided a method for requesting an application function, the method including:

[0132] The enabler client determines whether to proactively perform traffic influence based on the second determination information.

[0133] To help the enabler client determine the opportunity to trigger traffic influence based on various circumstances, before triggering traffic influence, the enabler client first determines whether to pre-execute traffic influence. If it is determined to pre-execute traffic influence, the enabler client can pre-trigger application server discovery accordingly. For an application client with higher latency requirements, this helps trigger user plane route optimization for the application client before the application client exchanges data with the application server, helps reduce the latency in obtaining application services by the application client, and helps improve the application service experience of the terminal device user. In order to help reduce situations where the edge data network performs application server discovery in advance for application clients that do not need application server discovery to be performed in advance, or performs traffic influence in advance for application clients that do not need traffic influence to be performed in advance, help improve the effectiveness of communication signaling exchanges between the enabler client and the edge data network, help to some extent reduce situations where user plane function network elements included in the optimized user plane are occupied for a certain period of time (e.g., the period between completion of traffic influence and data exchange between the application client and the application server), and help reduce waste of network resources, if it is determined not to perform traffic influence in advance, the enabler client does not need to trigger application server discovery in advance accordingly.

[0134] In one possible implementation, if it is determined that traffic influence is to be performed in advance, the enabler client sends an application server discovery request message in advance, the application server discovery request message being to request discovery of one or more application servers, where the one or more application servers are configured to provide application services to the application client.

[0135] In order to help fully utilize network resources of the edge data network, the enabler client can obtain a positive judgment result based on the second judgment information, and the enabler client can provide services to more application clients as much as possible by obtaining a positive judgment result. In order to help reduce delay in obtaining application services by the application clients and help improve the application service experience of the terminal device user, for application clients with higher delay requirements, traffic influence is pre-performed for the application clients.

[0136] In another possible implementation, if it is determined that traffic influence is not to be performed in advance, the enabler client does not send an application server discovery request message in advance, the application server discovery request message being for requesting to discover one or more application servers, the one or more application servers being configured to provide application services to the application client.

[0137] In order to help guarantee the quality of application services obtained by the application client that has performed the access and to help reduce the power consumption of the terminal device, the enabler client can obtain a negative judgment result based on the second judgment information, and the enabler client can reduce the access to the edge data network for the new application client as much as possible by obtaining a negative judgment result. In addition, in order to help improve the effectiveness of communication signaling exchange between the enabler client and the edge data network, to some extent help reduce the situation in which the user plane function network element included in the optimized user plane is occupied during a certain period, and to help reduce the waste of network resources, it is determined not to perform traffic influence in advance, so the enabler client does not trigger application server discovery in advance, and the edge data network does not perform traffic influence for the application client before the application client exchanges data with the application server.

[0138] In one possible implementation, after receiving an application server discovery request, the enabler client determines whether to proactively perform traffic influence.

[0139] In another possible implementation, after receiving information about one or more candidate application servers sent by the enabler server, the enabler client determines whether to pre-perform traffic influence.

[0140] In yet another possible implementation, the enabler client determines whether to proactively perform traffic influence based on received information about the selected application server or an event in which information about the selected application server was received.

[0141] Optionally, the selected application server may be determined by the application client, the enabler client, or the enabler server.

[0142] To help enabler clients improve the mechanism for triggering traffic influence and to help improve the efficiency of triggering traffic influence by the enabler clients, the enabler clients can determine whether to perform traffic influence in advance based on information sent by the application clients, and can also determine whether to perform traffic influence in advance based on information sent by the enabler server.

[0143] In order to help enabler clients provide services to application clients having different types and different operating states, and to improve the service efficiency and service quality of enabler clients, the implementation of this technical solution helps enabler clients improve the trigger mechanism for triggering application server discovery, so that the enabler client triggers application server discovery when a judgment condition is met.

[0144] Referring to the fourth aspect, in some implementations of the fourth aspect, the second judgment information includes application information, which includes one or more of the following information: application type, application server type, delay requirements, etc.

[0145] The application type, application server type, delay requirement, etc. may represent the specific attributes of the application client. To help improve the adaptability of the enabler server in providing services to various terminal devices, whether to perform application server discovery in advance is determined based on the specific attributes of the application client.

[0146] In one possible implementation, the application server type may be determined based on the service key performance indicators of the server, which include one or more of the following information: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0147] The server type is determined based on one or more kinds of information. In order to help simplify the decision process and message content for the enabler server to determine whether to proactively perform traffic influence, and to help improve the efficiency of determining whether to proactively perform application server discovery by the enabler server, the enabler server determines the enabler service type based on some basic information of the application server, so as to determine whether to proactively perform traffic influence.

[0148] The implementation of this technical solution helps the enabler client to make judgments and perform corresponding responses based on the attributes of the application clients, helps to improve the adaptability of providing services to different types of clients, helps to improve the overall service efficiency of the enabler client, helps to improve the application service experience of the terminal device user, and helps to improve the service quality of the edge data network.

[0149] Referring to the fourth aspect, in some implementations of the fourth aspect, the second judgment information includes instruction information, which instructs to perform application server discovery in advance and / or to perform traffic influence in advance.

[0150] The indication information can reflect the application client's relevant requirements for the application client's operating environment. The enabler client obtains the indication information, and thereby, based on the indication information, judges whether to pre-execute traffic influence for the application client, and judges whether to pre-send an application server discovery request message to trigger application server discovery. The enabler client can refer to the actual operating state and actual requirements of the application client to perform corresponding responses. In addition, for each indication information, the enabler client can perform corresponding responses, so that the enabler client can better provide services to the application client.

[0151] The implementation of this technical solution helps improve the triggering mechanism for enabler clients to trigger application server discovery, helps enable enabler clients to provide services to application clients with different operating states and operating requirements, helps improve the application service experience of terminal device users, and helps to improve the service quality of edge data networks to a certain extent.

[0152] In one possible implementation, the delay requirement is a delay requirement of a first packet, the delay requirement of the first packet being a delay requirement of a first data packet sent by the application client to one or more application servers.

[0153] The first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, ie, the first data packet in a data exchange between the application client and the application server.

[0154] The delay requirement of the first packet may alternatively indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0155] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0156] With reference to the fourth aspect, in some implementations of the fourth aspect, determining whether to pre-perform traffic influence includes determining whether to pre-perform application server discovery.

[0157] The combination of determining whether to perform traffic influence in advance and determining whether to perform application server discovery in advance helps to simplify the process of determining to provide an application server with an optimized user plane path for an application client, and helps to improve the efficiency of obtaining application services by the application client.

[0158] Referring to the fourth aspect, in some implementations of the fourth aspect, the enabler client receives a discovery response message sent by the enabler server, which indicates that traffic influence is being performed for one or more application servers.

[0159] The enabler client sends a first response message to the application client, the first response message including information regarding the one or more application servers, the first response message further indicating that traffic influence is being performed for the one or more application servers.

[0160] The enabler client can select one or more application servers based on the received discovery response message, and can preferentially feed back to the application client the application servers on which traffic influence has been performed, so that the application client can be connected to the application servers to obtain application services.

[0161] Optionally, the discovery response message further indicates whether traffic influence has been completed for one or more application servers, whether one or more application servers have optimized user plane paths, or whether user plane path optimization has been completed.

[0162] Optionally, the first response message further indicates whether traffic influence has been completed for one or more application servers, whether one or more application servers have optimized user plane paths, or whether user plane path optimization has been completed.

[0163] To help improve the efficiency of obtaining application services of application servers by application clients, the application clients can be directly connected to application servers where traffic influence has been completed.

[0164] After obtaining the information about the application server and the indication information indicating whether the traffic influence for the application server has been completed, the enabler client can further send the information about the application server and the indication information to the application client, and the application client can determine which application server is to obtain the application service based on the indication information.

[0165] The implementation of this technical solution helps to improve the service efficiency of the enabler client and the enabler server, helps to improve the application service experience of the terminal device user, helps to reduce the signaling waste caused by extra interactions between the enabler client and the enabler server, helps to reduce unnecessary user plane route optimization, and helps to reduce the waste of network resources.

[0166] According to a fifth aspect, there is provided a method for requesting an application capability, the method including:

[0167] The application client determines whether to pre-perform application server discovery and / or pre-perform traffic influence based on application information, the application information including one or more of the following information: application type, application server type, delay requirement, etc.

[0168] The application type, application server type, delay requirement, etc. may represent the inherent attributes of the application client. To help improve the initiative of the application client in obtaining application services, the application client determines whether to perform application server discovery in advance and / or whether to perform traffic influence in advance, i.e., determines the opportunity to perform application server discovery and / or traffic influence, based on the inherent attributes of the application client. If it is determined to perform application server discovery and / or traffic influence in advance to reduce the delay in obtaining application services, for application clients with higher delay requirements, a user plane path may be required to be optimized before the application client exchanges data with the application server. To help improve the effectiveness of signaling exchanges between the application client and the enabler client, etc., and to help reduce waste of network resources, if it is determined not to perform application server discovery and / or traffic influence in advance, the application client does not need to send request or instruction information to perform application server discovery and / or traffic influence in advance.

[0169] In one possible implementation, if it is determined to proactively perform application server discovery and / or proactively perform traffic influence, the application client proactively sends a first request message to the enabler client.

[0170] In order to help fully utilize the network resources of the edge data network, the application client can obtain a positive judgment result based on the second judgment information, and the application client can actively request to obtain a service provided by the edge data network by obtaining the positive judgment result. In order to reduce the delay in obtaining the application service by the application client, for an application client with a higher delay requirement, it may be required that a user plane path is optimized before the application client exchanges data with the application server.

[0171] In one possible implementation, if it is determined that application server discovery is not to be performed proactively and / or traffic influence is not to be performed proactively, the application client does not proactively send the first request message to the enabler client.

[0172] In order to help guarantee the quality of the application service obtained by the application client that has performed the access and to help reduce the power consumption of the terminal device, the application client can obtain a negative judgment result based on the second judgment information, and the application client can reduce the probability of obtaining the application service of the edge data network by obtaining a negative judgment result. In addition, in order to help improve the effectiveness of signaling exchange between the application client and the enabler client, etc., and to help reduce the waste of network resources, the application client does not need to send request or instruction information to perform application server discovery and / or traffic influence in advance.

[0173] In one possible implementation, if the application client determines based on the application information not to perform application server discovery in advance and / or not to perform traffic influence in advance, and the terminal device or application client user specifies to perform application server discovery in advance or to perform traffic influence in advance, the application client proactively sends request instruction information for performing application server discovery in advance and / or instruction information for performing traffic influence in advance to the enabler client according to the user's requirements or instructions.

[0174] In another possible implementation, if the application client determines based on the application information that the current application server cannot meet the application requirements, the application client proactively sends request instruction information for proactively performing application server discovery and / or instruction information for proactively performing traffic influence to the enabler client.

[0175] In order to help improve the probability of an application client obtaining an application service and to help improve the initiative of the application client in obtaining an application service, it is determined based on the application information that application server discovery cannot be performed in advance and / or traffic influence cannot be performed in advance, and the application client can send request instruction information for performing application server discovery in advance and / or instruction information for performing traffic influence in advance to request the enabler client to perform corresponding operations.

[0176] In one possible implementation, the application server type may be determined based on the service key performance indicators of the server, which include one or more of the following information: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0177] The server type is determined based on one or more kinds of information. In order to help simplify the decision process and message content for the application client to determine whether to proactively perform traffic influence, and to help improve the efficiency of determining whether to proactively perform application server discovery by the application client, the application client can determine the enabler service type based on some basic information of the application server, and thus determine whether to proactively perform traffic influence.

[0178] In this technical solution, the application information is used to determine the opportunity to perform application server discovery and / or perform traffic influence. If it is determined to perform application server discovery and / or traffic influence in advance, this helps to reduce the delay in obtaining application services by application clients with higher delay requirements. If it is determined not to perform application server discovery and / or traffic influence in advance, this helps to improve the effectiveness of signaling exchanges between application clients and enabler clients. In addition, the implementation of the technical solution helps to improve the service quality and service efficiency of the enabler client and the enabler server, helps to improve the service experience of the application client, helps to reduce signaling waste to a certain extent, helps to reduce unnecessary user plane route optimization, and further helps to reduce network resource waste.

[0179] With reference to the fifth aspect, in some implementations of the fifth aspect, the first request message includes application information and / or instruction information, which instructs to perform application server discovery in advance and / or to perform traffic influence in advance.

[0180] The application client sends application information and / or instruction information to the enabler client. After receiving the information, the enabler client can first determine whether to trigger a corresponding operation based on the received message.

[0181] In order to help enabler clients provide services to application clients having different types and different operating states, and to improve the service efficiency and service quality of enabler clients, the implementation of this technical solution helps enabler clients improve the trigger mechanism for triggering application server discovery, so that the enabler client triggers application server discovery when a judgment condition is met.

[0182] In one possible implementation, the delay requirement is a delay requirement of a first packet, the delay requirement of the first packet being a delay requirement of a first data packet sent by the application client to one or more application servers.

[0183] The first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, ie, the first data packet in a data exchange between the application client and the application server.

[0184] The delay requirement of the first packet may alternatively indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0185] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0186] With reference to the fifth aspect, in some implementations of the fifth aspect, the application client receives a first response message, the first response message includes information regarding one or more application servers, and the first response message further indicates that traffic influence is being performed for the one or more application servers.

[0187] By receiving the first response message, the application client obtains information about one or more application servers and indication information indicating whether traffic influence has been completed for the one or more application servers. Based on the indication information, the application client can preferentially select an application server on which traffic influence has been performed to provide an application service to the application client. This helps to accelerate the speed at which the application client obtains the application service, and helps to improve the service experience of the application client.

[0188] Optionally, the first response message further indicates whether traffic influence has been completed for one or more application servers, or the first response message further indicates whether the one or more application servers have an optimized user plane path, or whether optimization of the user plane path has been completed.

[0189] To help improve the efficiency of obtaining application services of application servers by application clients, the application clients can be directly connected to application servers where traffic influence has been completed.

[0190] With reference to the fifth aspect, in some implementations of the fifth aspect, when it is determined to perform application server discovery in advance and / or to perform traffic influence in advance, the application client sends a second instruction message to the selected application server in advance, the second instruction message instructing to trigger traffic influence in advance, and the one or more application servers include the selected application server.

[0191] In one possible implementation, if the first response message indicates that traffic influence is not to be performed for one or more application servers, the application client determines whether to perform traffic influence in advance based on the application information.

[0192] If it is determined that traffic influence is to be performed in advance, the application client sends a second instruction message in advance to the selected application server, the second instruction message being to request that traffic influence be performed in advance.

[0193] If it is determined that traffic influence is not to be performed in advance, the application client does not send a second instruction message to the selected application server in advance, and the second instruction message is for requesting that traffic influence be performed in advance.

[0194] Optionally, the application client determines the selected application server based on information about one or more application servers.

[0195] If traffic influence is not completed for the fed back application server or the fed back application server does not have an optimized user plane path, the application client can determine based on the application information whether to send a request to trigger traffic influence for the application server to the fed back application server. To help reduce waste of signaling exchanged between the application client, the enabler client, and the enabler server, and help improve the application service experience of the terminal device user, the application server selected by the application client does not need to be fed back to the enabler client and fed back to the enabler server to trigger traffic influence.

[0196] According to a sixth aspect, there is provided a method for requesting an application capability, the method including:

[0197] The application client determines whether to perform traffic influence in advance based on application information, the application information including one or more of the following information: application type, application server type, delay requirement, etc.

[0198] The application type, application server type, delay requirement, etc. may represent the specific attributes of the application client. To help improve the application client's initiative in obtaining application services, the application client determines whether to perform application server discovery in advance and / or whether to perform traffic influence in advance, i.e., determines the opportunity to perform traffic influence, based on the specific attributes of the application client. If it is determined to perform traffic influence in advance to reduce the delay in obtaining application services, for application clients with higher delay requirements, it may be required that the user plane path is optimized before the application client exchanges data with the application server. To help improve the effectiveness of signaling exchanges between the application client and the enabler client, etc., and to help reduce waste of network resources, if it is determined not to perform traffic influence in advance, the application client does not need to send request or instruction information to perform traffic influence in advance.

[0199] In one possible implementation, if it is determined that traffic influence is to be performed in advance, the application client sends a second request message in advance to a selected application server, the second request message being for requesting that traffic influence be performed in advance, the selected application server being included in one or more application servers, and the one or more application servers being configured to provide application services to the application client.

[0200] It should be understood that the second request message is for requesting the selected application server to pre-perform traffic influence for the selected application server.

[0201] In order to help fully utilize the network resources of the edge data network, the application client can obtain a positive judgment result based on the second judgment information, and the application client can actively request to obtain a service provided by the edge data network by obtaining the positive judgment result. In order to reduce the delay in obtaining the application service by the application client, for an application client with a higher delay requirement, it may be required that a user plane path is optimized before the application client exchanges data with the application server.

[0202] In one possible implementation, if it is determined that traffic influence is not to be performed in advance, the application client does not send a second request message in advance to the selected application server, the second request message being for requesting that traffic influence be performed in advance, the selected application server being included in one or more application servers, and the one or more application servers being configured to provide application services to the application client.

[0203] In order to help guarantee the quality of the application service obtained by the application client that has performed the access and to help reduce the power consumption of the terminal device, the application client can obtain a negative judgment result based on the second judgment information, and the application client can reduce the probability of obtaining the application service of the edge data network by obtaining a negative judgment result. In addition, in order to help improve the effectiveness of signaling exchange between the application client and the enabler client, etc., and to help reduce the waste of network resources, the application client does not need to send request or instruction information to perform application server discovery and / or traffic influence in advance.

[0204] In one possible implementation, if it is determined that application server discovery is not to be performed in advance and / or traffic influence is not to be performed in advance, the application client proactively sends request instruction information for performing application server discovery in advance and / or instruction information for performing traffic influence in advance to the enabler client.

[0205] In order to help improve the probability of an application client obtaining an application service and to help improve the initiative of the application client in obtaining an application service, it is determined based on the application information that application server discovery cannot be performed in advance and / or traffic influence cannot be performed in advance, and the application client can send request instruction information for performing application server discovery in advance and / or instruction information for performing traffic influence in advance to request the enabler client to perform corresponding operations.

[0206] In one possible implementation, the application server type may be determined based on the service key performance indicators of the server, which include at least one of the following information: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0207] The server type is determined based on one or more kinds of information. In order to help simplify the decision process and message content for the application client to determine whether to proactively perform traffic influence, and to help improve the efficiency of determining whether to proactively perform application server discovery by the application client, the application client can determine the enabler service type based on some basic information of the application server, and thus determine whether to proactively perform traffic influence.

[0208] In this technical solution, the application information is used to determine the opportunity to perform traffic influence. If it is determined to perform traffic influence in advance, this helps to reduce the delay in obtaining application services by application clients with higher delay requirements. If it is determined not to perform traffic influence in advance, this helps to improve the effectiveness of signaling exchanges between application clients and enabler clients, etc. In addition, the implementation of the technical solution helps to improve the service quality and service efficiency of the enabler client and the enabler server, helps to improve the service experience of the application client, helps to reduce signaling waste to a certain extent, helps to reduce unnecessary user plane route optimization, and helps to reduce network resource waste.

[0209] Referring to the sixth aspect, in some implementations of the sixth aspect, before determining whether to pre-perform traffic influence, the application client sends a third request message, the third request message being to request discovery of one or more application servers.

[0210] If traffic influence is not completed for the fed back application server or the fed back application server does not have an optimized user plane path, the application client can determine based on the application information whether to send a request to trigger traffic influence for the application server to the fed back application server. To help reduce waste of signaling exchanged between the application client, the enabler client, and the enabler server, and help improve the application service experience of the terminal device user, the application server selected by the application client does not need to be fed back to the enabler client and fed back to the enabler server to trigger traffic influence.

[0211] According to a seventh aspect, there is provided a communication system including an enabler server, an enabler client, and an application client. The enabler server is configured to implement a method according to the first aspect or any one of the possible implementations of the first aspect, or a method according to the second aspect or any one of the possible implementations of the second aspect. The enabler client is configured to implement a method according to the third aspect or any one of the possible implementations of the third aspect, or a method according to the fourth aspect or any one of the possible implementations of the fourth aspect. The application client is configured to implement a method according to the fifth aspect or any one of the possible implementations of the fifth aspect, or a method according to the sixth aspect or any one of the possible implementations of the sixth aspect.

[0212] According to an eighth aspect, an apparatus for requesting an application function is provided, comprising a processing unit and a transceiver unit.

[0213] The processing unit is configured to determine whether to proactively perform traffic influence based on the first determination information.

[0214] In one possible implementation, when it is determined to perform traffic influence in advance, the transceiver unit is configured to send an application capability request message in advance, the application capability request message being for requesting to perform traffic influence for one or more application servers.

[0215] In another possible implementation, if it is determined not to perform traffic influence in advance, the transceiver unit is configured to not send an application capability request message in advance, the application capability request message being for requesting to perform traffic influence for one or more application servers.

[0216] Referring to the eighth aspect, in some implementations of the eighth aspect, the first determination information includes application information, and the application information includes one or more of the following information: application type, server type, delay requirement, etc., and the processing unit: It is specifically configured to determine whether to proactively perform traffic influence based on one or more of an application type, a server type, or a delay requirement.

[0217] Referring to the eighth aspect, in some implementations of the eighth aspect, the first determination information includes instruction information, and the instruction information instructs to pre-perform application server discovery and / or pre-perform traffic influence, and the processing unit: The device is specifically configured to determine to proactively perform traffic influence based on the instruction to proactively perform application server discovery and / or the instruction to proactively perform traffic influence.

[0218] With reference to the eighth aspect, in some implementations of the eighth aspect, the transceiver unit is further configured to transmit a discovery response message, the discovery response message indicating that traffic influence is being performed for one or more application servers.

[0219] According to a ninth aspect, an apparatus for requesting an application function is provided, comprising a processing unit and a transceiver unit.

[0220] The processing unit is configured to determine whether to proactively perform traffic influence based on the first determination information.

[0221] In one possible implementation, when it is determined to perform traffic influence in advance, the transceiver unit is configured to send an instruction message to trigger traffic influence in advance to the selected application server, the instruction message instructing to trigger traffic influence in advance.

[0222] In another possible implementation, if it is determined not to perform traffic influence in advance, the transceiver unit is configured to not send an instruction message to trigger traffic influence in advance to the selected application server, and the instruction message instructs to trigger traffic influence in advance.

[0223] Referring to the ninth aspect, in some implementations of the ninth aspect, the first determination information includes application information, and the application information includes one or more of the following information: application type, server type, delay requirement, etc., and the processing unit: It is specifically configured to determine whether to proactively perform traffic influence based on one or more of an application type, a server type, or a delay requirement.

[0224] Referring to the ninth aspect, in some implementations of the ninth aspect, the first determination information includes instruction information, and the instruction information instructs to pre-perform application server discovery and / or pre-perform traffic influence, and the processing unit: The device is specifically configured to determine to proactively perform traffic influence based on the instruction to proactively perform application server discovery and / or the instruction to proactively perform traffic influence.

[0225] With reference to the ninth aspect, in some implementations of the ninth aspect, the transceiver unit is further configured to transmit a discovery response message, the discovery response message indicating that traffic influence is being performed for one or more application servers.

[0226] According to a tenth aspect, an apparatus for requesting an application function is provided, comprising a processing unit and a transceiver unit.

[0227] The processing unit is configured to determine whether to pre-perform application server discovery based on the second determination information.

[0228] In one possible implementation, when it is determined to perform application server discovery in advance, the transceiver unit is configured to send an application server discovery request message in advance, the application server discovery request message being for requesting to discover one or more application servers, the one or more application servers being configured to provide application services to the application client.

[0229] In another possible implementation, if it is determined not to perform application server discovery in advance, the transceiver unit is configured to not send an application server discovery request message in advance, the application server discovery request message being for requesting to discover one or more application servers, and the one or more application servers being configured to provide application services to the application client.

[0230] Referring to the tenth aspect, in some implementations of the tenth aspect, the second determination information includes application information, and the application information includes one or more of the following information: application type, server type, delay requirement, etc., and the processing unit: It is specifically configured to determine whether to pre-perform application server discovery based on one or more of an application type, a server type, or a delay requirement.

[0231] Referring to the tenth aspect, in some implementations of the tenth aspect, the second judgment information includes instruction information, and the instruction information instructs to pre-perform application server discovery and / or pre-perform traffic influence, and the processing unit: Specifically configured to: determine to pre-perform traffic influence based on the instruction for pre-performing application server discovery and / or the instruction for pre-performing application server discovery.

[0232] With reference to the tenth aspect, in some implementations of the tenth aspect, the transceiver unit is further configured to receive a discovery response message, the discovery response message indicating that traffic influence is being performed for one or more application servers.

[0233] The transceiver unit is further configured to transmit a first response message, where the first response message includes information regarding the one or more application servers, and where the first response message further indicates that traffic influence is being performed for the one or more application servers.

[0234] According to an eleventh aspect, an apparatus for requesting an application function is provided, comprising a processing unit and a transceiver unit.

[0235] The processing unit is configured to determine whether to proactively perform traffic influence based on the second determination information.

[0236] In one possible implementation, when it is determined to perform traffic influence in advance, the transceiver unit is configured to proactively transmit an application server discovery request message, the application server discovery request message being for requesting to discover one or more application servers, the one or more application servers being configured to provide application services to the application client.

[0237] In another possible implementation, if it is determined not to perform traffic influence in advance, the transceiver unit is configured to not send an application server discovery request message in advance, the application server discovery request message being for requesting to discover one or more application servers, and the one or more application servers being configured to provide application services to the application client.

[0238] Referring to the eleventh aspect, in some implementations of the eleventh aspect, the second determination information includes application information, and the application information includes one or more of the following information: an application type, a server type, a delay requirement, and the like, and the processing unit: It is specifically configured to determine whether to perform traffic influence in advance based on one or more of application type, server type, latency requirements, and the like.

[0239] Referring to the eleventh aspect, in some implementations of the eleventh aspect, the second determination information includes instruction information, and the instruction information instructs to pre-perform application server discovery and / or pre-perform traffic influence, and the processing unit: The device is specifically configured to determine to proactively perform traffic influence based on the instruction to proactively perform application server discovery and / or the instruction to proactively perform traffic influence.

[0240] Referring to the eleventh aspect, in some implementations of the eleventh aspect, the processing unit is further configured to determine whether to pre-perform application server discovery.

[0241] With reference to the eleventh aspect, in some implementations of the eleventh aspect, the transceiver unit is further configured to receive a discovery response message, the discovery response message indicating that traffic influence is being performed for one or more application servers.

[0242] The transceiver unit is further configured to transmit a first response message, where the first response message includes information regarding the one or more application servers, and where the first response message further indicates that traffic influence is being performed for the one or more application servers.

[0243] According to a twelfth aspect, an apparatus for requesting an application function is provided, comprising a processing unit and a transceiver unit.

[0244] The processing unit is configured to determine whether to pre-perform application server discovery and / or whether to pre-perform traffic influence based on application information, the application information including one or more of the following information: application type, server type, delay requirement, etc.

[0245] In one possible implementation, if it is determined to proactively perform application server discovery and / or proactively perform traffic influence, the transceiver unit is configured to proactively send a first request message to the enabler client.

[0246] In one possible implementation, if it is determined that application server discovery is not to be performed in advance and / or traffic influence is not to be performed in advance, the transceiver unit is configured to not proactively send the first request message to the enabler client.

[0247] With reference to the twelfth aspect, in some implementations of the twelfth aspect, the transceiver unit is further configured to receive a first response message, the first response message including information regarding one or more application servers, and the first response message further indicates that traffic influence is being performed for the one or more application servers.

[0248] With reference to the twelfth aspect, in some implementations of the twelfth aspect, when it is determined to perform application server discovery in advance and / or to perform traffic influence in advance, the transceiver unit is specifically configured to send a second instruction message to the selected application server in advance, the second instruction message instructing to trigger traffic influence in advance, and the one or more application servers include the selected application server.

[0249] According to a thirteenth aspect, an apparatus for requesting an application function is provided, comprising a processing unit and a transceiver unit.

[0250] The processing unit is configured to determine whether to perform traffic influence in advance based on application information, where the application information includes one or more of the following information: application type, server type, or delay requirement.

[0251] In one possible implementation, when it is determined to perform traffic influence in advance, the transceiver unit is configured to send a second request message in advance to the selected application server, the second request message being for requesting to perform traffic influence in advance, the selected application server being included in one or more application servers, and the one or more application servers being configured to provide application services to the application client.

[0252] In one possible implementation, if it is determined not to perform traffic influence in advance, the transceiver unit is configured to not send a second request message in advance to the selected application server, the second request message being for requesting to perform traffic influence in advance, the selected application server being included in one or more application servers, and the one or more application servers being configured to provide application services to the application client.

[0253] With reference to the thirteenth aspect, in some implementations of the thirteenth aspect, the transceiver unit is further configured to transmit a third request message, the third request message being for requesting to discover one or more application servers.

[0254] According to a fourteenth aspect, there is provided an apparatus for requesting an application function, comprising a processor configured to execute computer instructions stored in a memory, such that the apparatus performs a method according to the first aspect or any one of the possible implementations of the first aspect, or a method according to the second aspect or any one of the possible implementations of the second aspect.

[0255] According to a fifteenth aspect, there is provided an apparatus for requesting an application function, comprising a processor configured to execute computer instructions stored in a memory, such that the apparatus performs a method according to the third aspect or any one of the possible implementations of the third aspect, or a method according to the fourth aspect or any one of the possible implementations of the fourth aspect.

[0256] According to a sixteenth aspect, there is provided an apparatus for requesting an application function, comprising a processor configured to execute computer instructions stored in a memory, such that the apparatus performs a method according to the fifth aspect or any one of the possible implementations of the fifth aspect, or a method according to the sixth aspect or any one of the possible implementations of the sixth aspect.

[0257] According to a seventeenth aspect, a computer program product is provided, the computer program product comprising computer program code, which, when executed on a computer, is enabled to perform a method according to the first aspect or any one of its possible implementations, or a method according to the second aspect or any one of its possible implementations.

[0258] According to an eighteenth aspect, there is provided a computer program product, the computer program product comprising computer program code, which, when executed on a computer, is enabled to perform a method according to the third aspect or any one of the possible implementations of the third aspect, or is enabled to perform a method according to the fourth aspect or any one of the possible implementations of the fourth aspect.

[0259] According to a nineteenth aspect, a computer program product is provided, the computer program product comprising computer program code, which, when executed on a computer, is enabled to perform a method according to the fifth aspect or any one of its possible implementations, or a method according to the sixth aspect or any one of its possible implementations.

[0260] According to a twentieth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, which, when executed on a computer, are enabled to perform a method according to the first aspect or any one of the possible implementations of the first aspect, or a method according to the second aspect or any one of the possible implementations of the second aspect.

[0261] According to a twenty-first aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, which, when executed on a computer, are enabled to perform a method according to the third aspect or any one of the possible implementations of the third aspect, or a method according to the fourth aspect or any one of the possible implementations of the fourth aspect.

[0262] According to a twenty-second aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, which, when executed on a computer, are enabled to perform a method according to the fifth aspect or any one of the possible implementations of the fifth aspect, or a method according to the sixth aspect or any one of the possible implementations of the sixth aspect.

[0263] According to a twenty-third aspect, a chip is provided, including a processor configured to read instructions stored in a memory, which when executed by the processor is enabled to implement a method according to the first aspect or any one of the possible implementations of the first aspect, or a method according to the second aspect or any one of the possible implementations of the second aspect.

[0264] According to a twenty-fourth aspect, a chip is provided, comprising a processor configured to read instructions stored in a memory, which when executed by the processor is enabled to implement a method according to the third aspect or any one of its possible implementations, or a method according to the fourth aspect or any one of its possible implementations.

[0265] According to a twenty-fifth aspect, a chip is provided, comprising a processor configured to read instructions stored in a memory, which when executed by the processor is enabled to implement a method according to the fifth aspect or any one of its possible implementations, or a method according to the sixth aspect or any one of its possible implementations. [Brief description of the drawings]

[0266] [Figure 1] FIG. 1 is a diagram of a network architecture applicable to one embodiment of the present application. [Diagram 2] FIG. 1 is a diagram of an EAS discovery procedure applicable to one embodiment of the present application. [Diagram 3]FIG. 1 is a diagram of an EES discovery procedure applicable to one embodiment of the present application. [Figure 4] FIG. 2 is a diagram of a method for triggering traffic influence according to an embodiment of the present application. [Diagram 5] FIG. 2 is a diagram of another method for triggering traffic influence according to an embodiment of the present application. [Figure 6] FIG. 2 is a diagram of a method for requesting application capabilities according to an embodiment of the present application. [Figure 7] FIG. 2 is a diagram of another method for requesting application capabilities according to an embodiment of the present application. [Figure 8] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 9] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 10] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 11] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 12] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 13] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 14] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application. [Figure 15] 1 is a diagram of a communication device according to an embodiment of the present application; [Figure 16] FIG. 1 is a diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0267] The technical solutions of the present application are described below with reference to the accompanying drawings.

[0268] In the embodiments of the present application, unless otherwise specified, the number of nouns refers to "singular or plural", i.e., "one or more". "At least one" means one or more, "multiple" means two or more, and "multiple" in "one or more" means two or more similar kinds. "And / or" describes a relationship between related objects, and indicates that three relationships may exist. For example, A and / or B can represent the following cases: only A is present, both A and B are present, and only B is present, and A and B may be singular or plural. The character " / " usually indicates an "or" relationship between related objects. For example, A / B indicates A or B. "At least one of" or similar expressions refer to any combination of items, including any combination of singular items or multiple items. For example, at least one of a, b, or c can represent a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be singular or plural.

[0269] The technical solutions of the embodiments of the present application may be applied to various communication systems, such as a global system for mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a fifth generation (5G) system, or a future sixth generation (6G) system.

[0270] The terminal device in the embodiment of the present application may be a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user equipment. Alternatively, the terminal device may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capability, a computing device, another processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device of a 5G network, or a terminal device of a public land mobile network (PLMN). This is not limited in the embodiment of the present application.

[0271] The network device in the embodiment of the present application may be a device configured to communicate with a terminal device. The network device may be a base transceiver station (BTS) of a global system for mobile communication (GSM) system or a code division multiple access (CDMA), a Node B (NB) of a wideband code division multiple access (WCDMA) system, an evolved Node B (eNB or eNodeB) of an LTE system, or a radio controller in a cloud radio access network (CRAN) scenario. Alternatively, the network device may be a relay station, an access point, an in-vehicle device, a wearable device, a network device of a 5G network, a network device of a PLMN network, etc. This is not limited in the embodiment of the present application.

[0272] FIG. 1 is a diagram of a network architecture applicable to one embodiment of the present application.

[0273] A user equipment (UE) includes one or more application clients (AC) and edge enabler clients (EEC). The user equipment can establish a connection to an edge data network through the application clients and / or edge enabler clients to obtain application services.

[0274] An application client (AC) is used by an application user to obtain application services from an application server. The application client is a client program of a terminal-side application. The application client can be connected to an application server on a cloud to obtain application services, or can be connected to an edge application server (EAS) deployed and running in one or more edge data networks (EDNs) to obtain application services.

[0275] The edge enabler client (EEC) is configured to register information about the EEC and information about the application client with an edge enabler server (EES), perform security authentication, obtain an internet protocol (IP) address of the EAS from the EES, and provide edge computing enabler functionality for the application client, e.g., provide an EAS discovery service and return the IP address of the EAS to the application client.

[0276] The edge data network (EDN) includes an edge application server (EAS) and an edge enabler server (EES). The edge data network can provide application services to user equipment through the cooperation of the edge application server and the edge enabler server.

[0277] An edge application server (EAS) may also be referred to as an edge application, application instance, edge application instance, muti-access edge computing (MEC) application (server), or EAS function. An EAS is an application deployed in an edge data network, specifically a server application (e.g., social media, augmented reality (AR), or virtual reality (VR)). One or more EASs may be deployed for one application in one or more EDNs. EASs deployed and running in separate EDNs may be considered separate EASs for the application. Multiple EASs may share a domain name and may use one IP address or separate IP addresses.

[0278] The edge enabler server (EES) is configured to provide some enabler functions for application instances deployed in the EDN, so as to better support the deployment requirements of applications in the MEC. The EES can support edge application registration and authentication for UE, provide IP address information of application instances for UE, etc., further support obtaining identifiers and IP address information of application instances, and further send the identifiers and IP address information of application instances to an edge data network configuration server (ECS).

[0279] The EES is deployed in the EDN. Typically, the EAS is registered in the EES or information about the EAS is configured on the EES using a management system. The EES is called the EES associated with the EAS. The EES can control and manage the EAS registered in the EES and configured on the EES.

[0280] The Edge Configuration Server (ECS) is responsible for configuring the EDN, e.g. providing information about the EES to the UE, or providing information about application instances directly to the UE, interacting with the application domain name system (DNS) to obtain information about application instances, and thus being able to obtain and store information about application instances and IP addresses from other functional entities.

[0281] As shown in FIG. 1, application data traffic (ADT) is established between the application client and the edge application server, and communication interfaces are established between the application client and the edge enabler client, between the edge application server and the edge enabler server, between the edge enabler server and the edge configuration server, etc.

[0282] In the network architecture shown in FIG. 1, an application user enters into a service contract with an application provider to provide services to the application user. The application user logs into an application client on a terminal and communicates through a connection between the application client and the EAS. An enabler client is a middle layer, typically located in an operating system or between the application client and the operating system. The application client can obtain edge enabler services from the enabler client through an application program interface (API).

[0283] Based on the network architecture shown in Figure 1, the process of application context relocation is as follows.

[0284] (1) Detection of application context relocation: It is determined that a context relocation may be required. In this case, the detection entity typically detects some event, such as a UE location change or a UE user plane route update.

[0285] (2) Decision regarding application context relocation: A decision entity determines that a context relocation is required.

[0286] (3) Performing application context relocation: This mainly involves transferring application context from the source EAS to the target EAS, and may further include notifying the terminal of information about the target EAS, and notifying the network that the context relocation has been completed and related information of the target EAS (e.g., the address of the target EAS, N6 traffic information corresponding to the target EAS).

[0287] (4) Cleanup after application context relocation: Multiple entities are involved. For example, the application client initiates a new socket connection to the target EAS.

[0288] Before formally describing the embodiments of the present application, some terminology that may be used in the following embodiments will first be explained.

[0289] 1. Edge computing, alternatively translated as edge operations, is a distributed computing architecture for transferring computing of applications, data, and services from a network central node to a network logical edge node for processing. Edge computing is for completely decomposing large services that are initially processed by a central node, cutting the services into smaller, more manageable parts, and distributing those parts to edge nodes for processing. Edge nodes are closer to the user's terminal devices, which can speed up data processing and transmission and reduce latency. In this architecture, data analysis and knowledge generation are closer to the data source. Therefore, this architecture is more suitable for processing big data.

[0290] 2. Multi-access Edge Computing (MEC) can use radio access networks to bring services required by information technology (IT) and cloud computing capabilities closer to telecommunications users, creating a carrier-class service environment with high performance, low latency, and high bandwidth, accelerating high-speed downloads of content, services, and applications in the network, and enabling consumers to experience an uninterrupted, high-quality network.

[0291] 3. Data network (DN) is an operator or third party service network that can provide services, such as operator services or Internet services, to user equipment.

[0292] 4. A local area data network (LADN) is a data network access point that is very close to the user's attachment point.

[0293] 5. A common understanding of an Edge Data Network (EDN) is as follows: an EDN corresponds to only one data network, is a special Local Data Network (LDN), includes edge enabler functionality, can be identified using a data network access identifier (DNAI) and a data network name (DNN), and is a network logical concept. Another understanding of an EDN is as follows: an EDN is a peer concept of a central cloud, can be understood as a local data center (geographic location concept), can be identified using a DNAI, and can include multiple local data networks.

[0294] 6. Application context refers to operational state information related to one user or a group of users, and may optionally further include a context that one or more users subscribe to at the source EAS from the core network, such as a subscribed transaction identifier. Optionally, the application context further includes a context of one or more users on the EES, such as a transaction identifier that the source EAS subscribes to for one or more users.

[0295] 7. Application context relocation is explained as follows: In the process of executing an edge application, when the UE moves out of the current service area, for example, when the UE moves between multiple EDNs, or when the UE moves between multiple LADNs, the edge application server currently providing the service may not be able to continue to provide the service to the currently running application, or the edge application server currently providing the service may not be the best application server that can provide the service to the UE, and another edge application server may be more suitable to serve the application client on the UE. Therefore, in order to better provide the service to the UE, a new edge application server needs to be used to replace the edge application server currently serving. In this process, the application service is temporarily suspended or suspended, and the application context needs to be transferred to the new edge application server to ensure that the impact of the application execution suspension is minimized.

[0296] 8. Data Network Access Identifier (DNAI) is an identifier for user plane access to a data network.

[0297] 9. Traffic influence refers to the process in which a session management function (SMF) network element or a network exposure function (NEF) network element in a core network determines an optimized user plane path between a terminal device and an application server. By performing traffic influence, an application client or terminal device can access an edge data network (EAS or EES) through an appropriate user plane function (UPF) network element to obtain a network application service. If there is an optimized user plane path between a terminal device and an application server, the session management function network element or the network exposure function network element does not need to perform traffic influence.

[0298] Traffic influence may be triggered by an enabler server, an application server, or a configuration server. Traffic influence may be performed in the form of direct triggering. For example, the enabler server directly sends an application capability request message to an SMF or NEF in the core network to request to trigger traffic influence. Traffic influence may alternatively be performed in the form of indirect triggering. For example, the enabler server sends an instruction message to trigger traffic influence to a selected application server, which then sends an application capability request message to an SMF or NEF to request to trigger traffic influence.

[0299] It should be noted that in this application, the session management function network element and the network exposure function network element are only used as an example to describe the process of performing traffic influence. In the future, traffic influence may alternatively be performed by another core network element, or the session management function network element and the network exposure function network element may alternatively have another name, which is not limited in the embodiment of this application.

[0300] In the description of this application, the session management function network element may be replaced by an SMF network element or an SMF, the network exposure function network element may be replaced by an NEF network element or an NEF, and the user plane function network element may be replaced by a UPF network element or an UPF.

[0301] In the following, first, with reference to FIG. 2, an EAS discovery procedure applicable to one embodiment of the present application will be described.

[0302] The EAS discovery procedure is for determining one or more application servers that can provide application services to an application client. After the EEC obtains uniform resource locator (URL) information, IP address, or other information of the EES, and the EES is configured with the EAS discovery policy of the edge computing service provider (ESCP), EAS discovery can be performed.

[0303] S101: The EEC sends an EAS discovery request message to the EES.

[0304] The EAS discovery request includes the EEC ID and security credentials, and may include an EAS discovery filter parameter to search for information about a particular EAS or a particular type of EAS (e.g., a gaming application).

[0305] Table 1 shows the information that the EAS discovery request message may contain.

[0306] [Table 1]

[0307] S102: The EES checks whether the EEC is authorized to discover the requested EAS.

[0308] If the EES checks and determines that EEC is permitted, it locates the EAS based on the EAS discovery filter parameters and the location of the user equipment.

[0309] Table 2 shows information that the EAS discovery filter parameters may include.

[0310] [Table 2]

[0311] Table 3 shows the information that an AC profile may include in the EAS discovery filter parameters.

[0312] [Table 3]

[0313] In some embodiments, the EES does not obtain an EAS discovery filter parameter, and the EES identifies the EAS based on user equipment-specific service information on the EES and the location of the terminal device.

[0314] In some embodiments, the EES does not obtain an EAS discovery filter parameter, and the EES identifies the EAS by applying an ESCP policy (eg, based solely on the location of the terminal device).

[0315] In some embodiments, the EES can select one or more EASs based on at least one of the following information: location information of the terminal device, terminal device-specific service information, an ECSP policy, or an EAS discovery filter parameter. The filter parameter may include one or more of an application client type, an application server type, and information regarding the latency requirements of the application client.

[0316] S103: The EES sends an EAS discovery response message to the EEC.

[0317] In some embodiments, the EES rejects the service provisioning request and provides a corresponding failure cause if it cannot determine the EAS information using the inputs in the EAS discovery request message, the terminal device specific service information on the EES, or the ESCP policy.

[0318] For example, the terminal device is located outside the geographic or topological service area of ​​the EAS.

[0319] In some embodiments, the EES successfully processes the request and the EAS discovery response message includes information about the discovered EAS and endpoint information of the EAS.

[0320] Table 4 shows the information that the EAS response message may contain.

[0321] [Table 4]

[0322] To perform the EAS discovery procedure, the EES must first be determined. The EES is determined using the EES discovery procedure. The EES discovery procedure is described below with reference to FIG. 3.

[0323] Before performing the EES discovery procedure, the ECS configures available relevant edge computing service information for the EEC based on information such as the terminal device's location, service requirements, service preferences, and connectivity, and the information is used by the EEC to discover available relevant EES.

[0324] S201: The EEC sends a service provisioning request message to the ECS.

[0325] The service provisioning request message is for requesting the ECS to trigger EES discovery, and the service provisioning request message includes an identifier of the terminal device, e.g., GPSI, connectivity information, the location of the terminal device, and AC profile information.

[0326] Specifically, the information that the service provisioning request message may contain is shown in Table 5.

[0327] [Table 5]

[0328] S202: The ECS processes the request information.

[0329] After receiving the request information, the ECS performs authentication and authorization.

[0330] S203: The ECS sends a service provisioning response message to the EEC.

[0331] In some embodiments, the ECS checks the EES registered in the ECS based on the AC profile and location information of the terminal device provided by the EEC. If the ECS cannot determine information about the EES based on the request message of the EEC, etc., the ECS rejects the service provisioning request and provides a failure cause.

[0332] In some embodiments, the ECS successfully processes the service request and sends a service provisioning response message to the EEC, providing EDN connection information, a list of EESs that meet the EEC's request information, address identification information of the EESs, and so on.

[0333] In some embodiments, Table 6 shows the information included in the service provisioning response message.

[0334] [Table 6]

[0335] The above describes the EAS discovery procedure and the EES discovery procedure with reference to Figures 2 and 3. In the following, a method for triggering traffic influence according to an embodiment of the present application will be described with reference to Figures 4 and 5.

[0336] FIG. 4 is a diagram of a method for triggering traffic influence according to the present application.

[0337] In this embodiment of the present application, the EES sends an application function request message to the SMF or NEF in the core network to request the performance of traffic influence.

[0338] S301: The EES sends an application function request message to the core network.

[0339] The application function request message instructs the SMF or NEF to perform traffic influence.

[0340] Specifically, the EES directly requests the SMF to perform traffic influence. Alternatively, the EES requests the NEF to perform traffic influence, and the NEF requests the SMF to perform traffic influence on behalf of an application client, a terminal device, or an application server.

[0341] In some embodiments, the EES sends an application capability request message to the SMF or NEF once, the application capability request message includes DNAI information of all EASs for which traffic influence needs to be performed, and the DNAI information of the EASs indicates the potential locations of the application servers.

[0342] In some other embodiments, the EES sends an application capability request message to the SMF or NEF multiple times, where the application capability request message includes DNAI information of one or more EASs for which traffic influence needs to be performed, and the DNAI information of the EASs indicates the likely locations of the application servers.

[0343] In some embodiments, the application capability request message may include information regarding one or more EASs and is to request an SMF or NEF in the core network to perform traffic influence for the one or more EASs.

[0344] Optionally, information regarding one or more EASs is included in an EAS list.

[0345] In some embodiments, the application capability request message includes information about the target EAS and is to request an SMF or NEF in the core network to perform traffic influence for the target EAS.

[0346] The target EAS is an EAS selected from one or more candidate EASs in an EAS discovery procedure, and the target EAS may also be called a selected EAS. The process of selecting a target EAS from the candidate EASs may be performed by the EES, may be performed by the EEC, or may be performed by the application client.

[0347] Optionally, the target EAS is determined by the application client. After the application client selects the target EAS, it sends the target EAS to the EEC. The EEC declares the received target EAS to the EES.

[0348] Optionally, the target EAS is determined by the EEC, and after the EEC selects the target EAS, it declares the target EAS to the EES.

[0349] The application capability request message further includes one or more of the following information: user equipment identity (UE identification, UE ID), EAS information (EAS or EAS list), information about a subscription type, and an application function transaction identifier, where the subscription type may be early notification or late notification.

[0350] S302: The SMF transmits the target DNAI to the EES.

[0351] Specifically, the SMF or NEF in the core network can send one or more of the following information to the EES by sending Nsmf_EventExposure_Notify: target DNAI, application function transaction identifier, identifier of EAS, etc. The target DNAI is a preferred DNAI for accessing the EAS.

[0352] By receiving the Nsmf_EventExposure_Notify message, the EES can determine that the target DNAI is the DNAI of an EAS that has optimized UE-EAS user plane information.

[0353] In some embodiments, the SMF or NEF separately selects a target DNAI for one or more EASs and performs traffic influence for the target DNAI, so that an optimized user plane path exists between the terminal device and the target DNAI.

[0354] S303: Perform UPF insertion, deletion, and modification operations.

[0355] Specifically, the SMF in the core network performs UPF insertion, deletion, and modification operations.

[0356] The SMF performs operations such as UPF insertion, deletion, and modification, i.e., performs traffic influence, so that an optimized user plane path may exist between the terminal device and the target DNAI.

[0357] In some embodiments, there is an optimized user plane path between the terminal device and the target DNAI, and the SMF does not need to perform operations such as inserting, deleting, or modifying user plane network elements, i.e., in this case, the SMF or NEF does not need to perform traffic influence.

[0358] Optionally, the SMF or NEF may first perform traffic influence for the target DNAI and then send the target DNAI to the EES, that is, S303 may be performed before S302.

[0359] FIG. 5 is a diagram of another method for performing traffic influence according to an embodiment of the present application.

[0360] In this embodiment of the present application, the target EAS sends an application function request message to an SMF or NEF in the core network to request the performance of traffic influence.

[0361] S401: The EAS sends an application function request message to the core network.

[0362] The application capability request message is to request the SMF or NEF to perform traffic influence on behalf of a terminal device, an application client, or an application server.

[0363] Specifically, the EAS directly requests the SMF to perform traffic influence. Alternatively, the EAS requests the NEF to perform traffic influence, and the NEF requests the SMF to perform traffic influence for an application client, a terminal device, or an application server.

[0364] In some embodiments, the application capability request message sent by the EAS may include one or more pieces of DNAI information for accessing the EAS, where the DNAI information of the EAS indicates the likely location of the application server.

[0365] In some other embodiments, the application capability request message for traffic influence sent by the EAS may include one or more of the following information: UE ID, EAS information, information about the subscription type, and an application capability transaction identifier, where the subscription type may be early notification or late notification.

[0366] Optionally, if it is determined that the target EAS has DNAI for the optimized user plane path, the target EAS does not need to send a message to the SMF or NEF to request the execution of traffic influence.

[0367] S402: The core network sends the target DNAI to the EAS.

[0368] By sending an Nsmf_EventExposure_Notify message, the SMF or NEF can send one or more of the following information to the EAS: a target DNAI, an application function transaction identifier, or an identifier of the EAS. The target DNAI is a preferred DNAI for accessing the EAS.

[0369] In some embodiments, the SMF or NEF performs traffic influence for the target DNAI, so that an optimized user plane path exists between the terminal device and the target DNAI.

[0370] In some embodiments, if the SMF or NEF determines that the target DNAI has an optimized user plane path, it does not need to perform traffic influence for the target DNAI.

[0371] S403: Execute UPF insertion, deletion and modification operations.

[0372] Specifically, the SMF in the core network performs UPF insertion, deletion, and modification operations.

[0373] The SMF performs operations such as UPF insertion, deletion, and modification, i.e., performs traffic influence, so that the target DNAI can be configured with an optimized user plane path.

[0374] In some embodiments, there is an optimized user plane path between the terminal device and the target DNAI, and the SMF does not need to perform operations such as inserting, deleting, or modifying user plane network elements, i.e., in this case, the SMF or NEF does not need to perform traffic influence.

[0375] Optionally, the SMF or NEF may first perform traffic influence for the target DNAI and then send the target DNAI to the EAS, that is, S403 may be performed before S402.

[0376] Above, the method for performing traffic influence according to the present application has been described in detail with reference to Figures 4 and 5. In the following, the focus will be on the method for requesting application functionality according to the present application with reference to Figures 6 to 15.

[0377] FIG. 6 is a diagram of a method for requesting application capabilities according to the present application.

[0378] S501: An application client determines whether to proactively perform application server discovery and / or whether to proactively perform traffic influence.

[0379] Pre-execution means execution before an application client is launched or before an application client exchanges data with an application server. Pre-execution is also sometimes called executing, pre-executing, executing ahead of time, executing immediately, etc.

[0380] The application server discovery procedure is performed by an enabler server, and the traffic influence procedure is performed by an SMF or NEF in the core network. In this specification, executing may be understood as triggering execution. Performing application server discovery and / or traffic influence in advance can prepare an application client to obtain an application service, and the application service can be obtained quickly when the application client is started.

[0381] The application client of the traffic influence can determine whether to pre-perform application server discovery and / or traffic influence based on the application information, which includes one or more of an application type, an application server type, a delay requirement, etc. When the enabler client obtains information about the application servers discovered by the enabler server using the application server discovery procedure, the enabler client can send a first response message to the application client, which may include information about the one or more application servers. Traffic influence may have been triggered for the one or more application servers, or traffic influence may not yet be triggered for the one or more application servers.

[0382] Optionally, traffic influence may be completed for one or more application servers, or traffic influence may not be completed for one or more application servers.

[0383] It should be understood that in this specification, an application server for which traffic influence may not be completed may refer to a case where the enabler server has been requested by an SMF or NEF in the core network to perform traffic influence and receives an acknowledgement message sent by the SMF or NEF indicating that traffic influence may be performed for the application server but the traffic influence is not completed, or may refer to a case where the enabler server has not requested the SMF or NEF to perform traffic influence.

[0384] In some embodiments, the first response message may further indicate whether traffic influence is triggered for one or more application servers returned to the application client.

[0385] Additionally, in some embodiments, the first response message may further indicate whether traffic influence has been completed for the one or more application servers returned to the application client.

[0386] In one embodiment, the first response message indicates that traffic influence has not been completed for one or more application servers, and the application client determines whether to pre-perform traffic influence based on the application information.

[0387] In some embodiments, an application client may determine to perform traffic influence in advance, and the application client may request an enabler client to perform traffic influence for a selected application server, whereupon the enabler client requests the enabler server to trigger traffic influence, and the enabler server sends an application capability request message to the SMF or NEF to trigger the traffic influence.

[0388] In some embodiments, after receiving a message from an enabler client to request the performance of traffic influence, the enabler server sends a message to perform traffic influence to a selected application server, which then sends an application function request message to the SMF or NEF to trigger the traffic influence.

[0389] In some other embodiments, the application client determines to proactively perform traffic influence, and the application client can proactively send a second request message to the selected application server. If the application client determines not to proactively perform traffic influence, the application client does not proactively send a second request message to the selected application server. The second request message is to request to perform traffic influence for the selected application server.

[0390] The selected servers are one or more application servers selected from one or more candidate application servers discovered using an application server discovery procedure. The selection process may be performed by the application client, or may be performed by an enabler client or enabler server.

[0391] In some embodiments, the selected application server has an optimized user plane path, in which case the SMF or NEF does not need to perform traffic influence for the selected application server, i.e., does not need to perform user plane path change operations such as UPF network element insertion, deletion, or modification for the selected application server.

[0392] In some other embodiments, the selected application server does not have an optimized user plane path, and the SMF or NEF may be required to perform traffic influence for the selected application server. In this specification, performing traffic influence for the selected application server may alternatively be understood as performing traffic influence for the selected application client or the selected terminal device.

[0393] S502: The application client sends a first request message to the enabler client.

[0394] In some embodiments, the first request message includes application information and / or instruction information. The application information includes one or more of the following information: application type, server type, or delay requirement. The instruction information includes instructions to proactively perform application server discovery and / or instructions to proactively perform traffic influence.

[0395] The delay requirement may be a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by an application client. In this specification, the first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, i.e., the first data packet in the data exchange between the application client and the application server.

[0396] The delay requirement of the first packet may indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0397] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0398] If the application client determines not to proactively perform application server discovery and / or not to proactively perform traffic influence, the application client does not send the first request message to the enabler client.

[0399] In some embodiments, the application client determines to pre-perform application server discovery and / or pre-perform traffic influence, and the application client sends a first request message to the enabler client. In some embodiments, the first request message sent by the application client does not include application information or instruction information, and the enabler client and the enabler server cannot obtain the second decision criterion or the first decision criterion. After obtaining information about the candidate application servers, the enabler client feeds back the information about the candidate servers to the application client.

[0400] The application server can determine whether to perform traffic influence in advance based on the application information. If traffic influence needs to be performed in advance, the application client sends an application function request message to the selected application server after selecting the application server to request the SMF or NEF to perform traffic influence for the application server, the application client, and / or the terminal device. Alternatively, the application client can send a message to request the performance of traffic influence to the enabler client in advance, and the enabler client requests the enabler server to perform traffic influence, so that the enabler server requests the selected application server to perform traffic influence or directly requests the SMF or NEF to perform traffic influence for the selected application server.

[0401] S503: The enabler client determines, based on the second judgment information, whether to proactively perform application server discovery and / or whether to proactively perform traffic influence.

[0402] The enabler client can obtain the second judgment information by receiving the first request message of the application client, and the second judgment information may be configured on the enabler client in a pre-configured manner, alternatively, or may be obtained by the enabler client in other manners.

[0403] In some embodiments, the second determination information includes application information, which includes one or more of the following information: application type, application server type, delay requirement, and so on.

[0404] The delay requirement may be a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by an application client. In this specification, the first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, i.e., the first data packet in the data exchange between the application client and the application server.

[0405] The delay requirement of the first packet may indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0406] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0407] In some embodiments, the second determination information includes instruction information, which instructs to proactively perform application server discovery and / or to proactively perform traffic influence.

[0408] In some embodiments, the second determination information includes application information and instruction information.

[0409] Upon obtaining information regarding the one or more candidate application servers fed back by the enabler server, the enabler client can feed back information regarding the one or more candidate application servers to the application client, or the enabler client can feed back indication information indicating whether traffic influence has been completed for the candidate application servers along with information regarding the one or more candidate application servers to the application client. In some embodiments, the enabler client feeds back information regarding application servers for which traffic influence has been completed among the candidate application servers to the application client.

[0410] S504: The enabler client sends an application server discovery request message to the enabler server.

[0411] When the enabler client determines not to proactively perform traffic influence based on the application type in the first request message, the enabler client does not proactively send an application server discovery request message to the enabler server.

[0412] When the enabler client determines not to proactively perform traffic influence based on the delay requirement in the first request message, the enabler client does not proactively send an application server discovery request message to the enabler server.

[0413] When the enabler client determines not to proactively perform traffic influence based on the application server type in the first request message, the enabler client does not proactively send an application server discovery request message to the enabler server.

[0414] In some embodiments, the enabler client determines to pre-perform application server discovery and / or pre-perform traffic influence based on the application type in the first request message, and the enabler client sends an application server discovery request message to the enabler server.

[0415] In some embodiments, the enabler client determines to perform application server discovery in advance and / or to perform traffic influence in advance based on a delay requirement in the first request message, and the enabler client proactively sends an application server discovery request message to the enabler server.

[0416] In some embodiments, the enabler client determines to pre-perform application server discovery and / or pre-perform traffic influence based on the application server type in the first request message, and the enabler client pre-sends an application server discovery request message to the enabler server.

[0417] In some embodiments, the enabler client determines to perform application server discovery in advance and / or perform traffic influence in advance based on the instruction information in the first request message, and the enabler client proactively sends an application server discovery request message to the enabler server.

[0418] In some embodiments, the enabler client determines whether to proactively perform application server discovery and / or whether to proactively perform traffic influence based on the application information and the instruction information in the first request message to determine whether to proactively send an application server discovery request message.

[0419] In some embodiments, the enabler client determines to pre-perform traffic influence based on the second judgment information, and determines to pre-perform application server discovery based on a judgment result that instructs to pre-perform traffic influence.

[0420] When the enabler client determines not to perform traffic influence in advance based on the second judgment information, the enabler client determines not to send an application server discovery request message in advance to perform application server discovery based on the judgment result instructing not to perform traffic influence in advance.

[0421] S505: The enabler server determines whether to pre-execute traffic influence based on the first determination information.

[0422] This first determination information may be obtained by receiving a message sent by the enabler client, or may be obtained in another manner, such as by pre-configuration.

[0423] In some embodiments, the first determination information includes application information, where the application information includes one or more of the following information: application type, application server type, delay requirement, and so on.

[0424] In some embodiments, the first determination information includes instructional information, where the instructional information includes instructions to proactively perform application server discovery and / or instructions to proactively perform traffic influence.

[0425] In some embodiments, the first determination information includes application information and instruction information.

[0426] If the enabler server determines not to pre-perform traffic influence based on the application type in the application server discovery request message, the enabler server does not send the application capability request message.

[0427] If the enabler server determines not to proactively perform traffic influence based on the delay requirement in the application server discovery request message, the enabler server does not send the application capability request message.

[0428] If the enabler server determines not to pre-perform traffic influence based on the application server type in the application server discovery request message, the enabler server does not send the application capability request message.

[0429] In some embodiments, the enabler server determines to pre-perform traffic influence based on the application type in the application server discovery request message, and the enabler server sends an application capability request message.

[0430] In some embodiments, the enabler server determines to proactively perform traffic influence based on a delay requirement in the application server discovery request message, and the enabler server sends the application capability request message.

[0431] In some embodiments, the enabler server determines to pre-perform traffic influence based on the application server type in the application server discovery request message, and the enabler server does not send an application capability request message.

[0432] In some embodiments, the enabler server determines to proactively perform traffic influence based on the instruction information in the application server discovery request message, and the enabler server sends an application capability request message.

[0433] The delay requirement may be a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by an application client. In this specification, the first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, i.e., the first data packet in the data exchange between the application client and the application server.

[0434] The delay requirement of the first packet may indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0435] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0436] In some embodiments, the enabler server determines whether to perform traffic influence in advance based on the application information and the instruction information in the application server discovery request message to determine whether to send an application capability request message.

[0437] The enabler server determines one or more candidate application servers after performing an application server discovery procedure. The enabler server can pre-request the SMF or NEF to perform traffic influence for one or more candidate application servers. The enabler server can alternatively directly feed back information about one or more candidate application servers to the enabler client. The enabler server can alternatively select an application server to be selected from the candidate application servers and send a message to the selected application server to request the execution of traffic influence to request the selected application server to trigger traffic influence.

[0438] After determining information about the selected application server, the enabler server requests the SMF or NEF to perform traffic influence for the selected application server, or the enabler server can directly request the selected application server to trigger traffic influence for the selected application server.

[0439] The enabler server may send information about one or more candidate application servers to the enabler client in a discovery response message. Traffic influence may have been triggered for one or more candidate application servers, or traffic influence may not yet have been triggered for one or more candidate application servers. The discovery response message may alternatively include indication information indicating whether "traffic influence has been triggered for one or more candidate application servers."

[0440] It should be understood that in this embodiment of the present application, the AC determines whether to pre-perform application server discovery and / or pre-perform traffic influence, the EEC determines whether to pre-perform application server discovery and / or pre-perform traffic influence, and the EES determines whether to pre-perform traffic influence may be performed separately or jointly. That is, at least one of S501, S503, or S505 needs to be performed.

[0441] It should be noted that in addition to determining whether to perform traffic influence in advance based on the first judgment information, the enabler server may determine whether to perform traffic influence in advance based on any one of the following manners:

[0442] 1. The enabler server determines whether to perform traffic influence in advance based on received declared information about the selected application server (e.g., application server type) or based on a received declaration event in which information about the selected application server is declared.

[0443] 2. The enabler client declares to the enabler server instruction information instructing that the application client should send data to the application server, and the enabler server determines whether to perform traffic influence in advance based on the declared event.

[0444] 3. The enabler client declares a request message for pre-executing traffic influence to the enabler server, and the enabler server determines whether to pre-execute traffic influence based on the declared event.

[0445] FIG. 7 is a diagram of a method for requesting application capabilities according to an embodiment of the present application.

[0446] In this embodiment of the present application, the EEC judges whether to pre-trigger EAS discovery based on application information. After receiving the EEC's EAS discovery request information, the EES judges whether to immediately perform traffic influence.

[0447] S601: The EAS sends an EAS registration request message to the EES.

[0448] The registration request message is for requesting that the EAS be registered in the EES. The registration request message may include an EAS profile. The EAS profile includes a DNAI list. A terminal device or an application client can access the EAS using a DNAI in the DNAI list to obtain an application service provided by the EAS.

[0449] In some embodiments, the EAS sends an EAS registration update request message to the EES, where the EAS registration update request message is to request an update of registration information of the EAS registered in the EES.

[0450] In some embodiments, the EAS DNAI information may be included directly in the registration request message.

[0451] It should be understood that the EES may alternatively obtain the relevant information of the EAS (e.g., DNAI information of the EAS) in a pre-configured manner. After the EES obtains the relevant information of the EAS in a pre-configured manner, the EAS may no longer send an EAS registration request to the EES, i.e., S601 and S602 may no longer be executed.

[0452] S602: The EES sends an EAS registration response message to the EAS.

[0453] The EAS registration response message indicates whether the EAS registration is successful or not. When the EES receives the registration update request message sent by the EAS, it sends an EAS registration update response message to the EAS.

[0454] If the EAS registration is successful, the registration response message may include the EAS registration ID, the expiration date of the EAS registration, etc. If the EAS registration is unsuccessful, the registration response message may include information about the cause of the EAS registration failure, etc.

[0455] It should be understood that if the EES obtains the relevant information of the EAS in a pre-configured manner, S601 and S602 do not need to be executed.

[0456] S603: The EEC decides whether to perform EAS discovery in advance.

[0457] The purpose of performing EAS discovery is to determine an EAS suitable for providing application services to an application client and a method for accessing the EAS. Performing EAS discovery in advance means performing EAS discovery before an application client is launched or before an application client exchanges data with an EAS. Performing in advance is also called performing in advance or performing immediately.

[0458] The EAS that is suitable for providing the application service to the application client, which is determined by using the EAS discovery procedure, may be referred to as a candidate EAS. For the specific EAS discovery procedure, please refer to the related description in FIG. 2.

[0459] In this embodiment of the present application, the EEC determines whether to perform EAS discovery in advance based on application information, where the application information includes one or more of the following information: application client type (or application type), application server type (or server type), or latency requirement (or latency requirement) of the application client.

[0460] The delay requirement may be a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by an application client. In this specification, the first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, i.e., the first data packet in the data exchange between the application client and the application server.

[0461] The delay requirement of the first packet may alternatively indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0462] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0463] In some embodiments, the EEC determines whether to pre-perform EAS discovery based on the application client type.

[0464] In one embodiment, the EEC determines that the application client is an application client having a lower latency requirement based on the application client type, and the EEC determines not to proactively perform EAS discovery.

[0465] In another embodiment, the EEC determines, based on the application client type, that the application client is an application client with a higher delay requirement, and the EEC determines to pre-perform EAS discovery.

[0466] For example, the application client type is an ultra reliable low latency communication (URLLC) type service, or the application client is an application with higher latency requirements, such as a gaming application, and the EEC pre-performs EAS discovery for such application clients.

[0467] In some embodiments, the EEC determines whether to pre-perform EAS discovery based on the latency requirement information of the application client, which may also be referred to as the latency requirement in this specification.

[0468] In one embodiment, the EEC determines, based on the latency requirements of the application client, that the application client is an application client having a lower latency requirement, and the EEC determines not to proactively perform EAS discovery.

[0469] In another embodiment, the EEC determines, based on the delay requirement of the application client, that the application client is an application client having a higher delay requirement, and the EEC determines to pre-perform EAS discovery.

[0470] For example, the EEC stores a preset delay threshold. After receiving a request message sent by an application client, the EEC obtains a delay requirement of the application client. If the delay requirement is less than the delay threshold, the EEC determines to pre-perform EAS discovery for the application client. If the delay requirement is greater than the delay threshold, the EEC determines not to pre-perform EAS discovery for the application client.

[0471] In some embodiments, the EEC determines whether to pre-perform EAS discovery based on the application server type. The application server may belong to an expected application server type or a basic application server type.

[0472] The expected application server is also called an ideal application server, which means that the key performance indicators for measuring the application server are that it can provide complete application services to application clients. The basic application server is also called a basic application server or a minimal application server, which means that the key performance indicators for measuring the application server are that it can only maintain basic application services for application clients.

[0473] The application server type may be distinguished based on the service key performance indicators of the application server. The service key performance indicators of the application server may include connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, and storage resources. The application server type may be determined based on one or more parameters of the aforementioned service key performance indicators.

[0474] In one embodiment, the EEC determines that the application server is a basic application server based on the connection bandwidth among the service key performance indicators of the application server, and the EEC determines not to perform application server discovery in advance based on the application server type.

[0475] In one embodiment, the EEC determines that an application server is an expected application server based on response time, availability, and memory resources among the service key performance indicators of the application server, and the EEC decides to perform application server discovery in advance based on the application server type.

[0476] In some embodiments, the application server type may alternatively be determined separately based on the application client type (AC type).

[0477] The EEC can further determine whether to perform traffic influence in advance based on the application information. The content of this determination method is similar to the content of determining whether to perform EAS discovery in advance based on the application information. For details, please refer to the above description.

[0478] Optionally, the EEC determines to perform traffic influence in advance based on the application information, and the EEC determines to perform EAS discovery in advance based on a determination result that indicates to perform traffic influence in advance.

[0479] The application information may include one or more of an application type, an application server type, a delay requirement, etc. The application information may be configured on the EEC in a pre-configured manner, may be sent to the EEC by an application client sending a message to the EEC, or may be obtained by the EEC in other manners. The manner in which the EEC obtains the information that the application information may include is not limited by this application.

[0480] Before sending a request message requesting to perform EAS discovery, the EEC first judges whether to perform EAS discovery in advance. The criterion is related information of the attributes of the application client. By making the judgment, the EEC can perform differentiated services based on each application client when serving the application client, so as to help improve the service efficiency of the terminal device, help properly allocate the resources of the terminal device, and help improve the user's application usage experience.

[0481] Optionally, the EEC determines not to pre-perform EAS discovery for the same application client based on a determination result indicating not to pre-perform EAS discovery for the application client.

[0482] Optionally, the EEC determines not to pre-perform EAS discovery for the same application client based on a determination result indicating not to pre-perform traffic influence for the application client.

[0483] If it is determined not to perform EAS discovery in advance, S604 to S607 may no longer be performed. Optionally, the EEC stores the determination result indicating not to perform EAS discovery in advance.

[0484] Optionally, the EEC may send instruction information to the application client to not perform EAS discovery in advance. For details of the contents of this part, please refer to the description of the embodiment shown in Figure 15 below. Details will not be described in this specification.

[0485] S604: The EEC proactively sends an EAS discovery request message to the EES.

[0486] The EAS discovery request message is for requesting the discovery of one or more EASs that provide application services to the application client. The discovery request may alternatively be carried in a message such as an EAS discovery subscription request message or an EAS discovery subscription update request message. The specific bearer message is not limited in this embodiment of the present application.

[0487] Sending in advance, which may also be referred to as sending, sending in advance, sending immediately, etc., means sending an EAS discovery request message before the application client is launched or before the application client exchanges data with the EAS.

[0488] The EAS discovery request message further includes one or more of the following information: EAS discovery filter parameters, location information of the terminal device, terminal device-specific service information, and ECSP policies. After receiving the EAS discovery request message, the EES can select a candidate EAS based on at least one of the aforementioned information in the EAS discovery request message.

[0489] In some embodiments, the EAS discovery request message includes an application client type.

[0490] In one embodiment, the EAS discovery request message includes an application client profile, and the application client profile includes an application client type.

[0491] In one embodiment, the EAS discovery request message includes an EAS discovery filter parameter, and the application client profile in the EAS discovery filter parameter includes an application client type.

[0492] In some other embodiments, the EAS discovery request message includes information regarding the latency requirements of the application client.

[0493] In one embodiment, a delay requirement related information element is newly added to the EAS discovery request message, which is for storing the delay requirement of the application client.

[0494] An example is used as follows:

[0495] Information element name: Delay requirement

[0496] Information element status: optional or required.

[0497] Information element description: 0.1 ms or less.

[0498] In another embodiment, an existing information element is used in the EAS discovery request message to store the delay requirement of the application client.

[0499] For example, the delay requirement may be carried in an EAS discovery filter parameter, an application client feature list, an application client profile in an application client feature list, an EAS feature list, or an EAS profile in an EAS feature list.

[0500] In some embodiments, the EAS discovery request message includes an application server type.

[0501] In one embodiment, the EAS discovery request message includes one or more service key performance indicators, which may be for determining the application server type.

[0502] For example, the EAS discovery request message includes one or more of the application server's service key performance indicator parameters, namely, connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources. S605: The EES determines whether to perform traffic influence in advance.

[0503] Immediate execution may also be referred to as executing, pre-executing, or pre-executing. Since traffic influence is performed by the SMF or NEF, executing herein may be understood as triggering execution.

[0504] In some embodiments, the EES determines whether to immediately perform traffic influence based on one or more of an application client type, an application server type, or information regarding the latency requirements of the application client.

[0505] In one embodiment, the EES determines based on the application client type that the application client is of an application client type having a higher delay requirement, and the EES determines to proactively perform traffic influence.

[0506] In another embodiment, the EES determines based on the application client type that the application client is of an application client type having a lower latency requirement, and the EES determines not to proactively perform traffic influence.

[0507] For example, the EES stores a list of different application client types, in which a correspondence is established between the application client types and whether to proactively perform traffic influence, and the EES can determine whether to proactively perform traffic influence for different types of application clients based on the list.

[0508] In one embodiment, the EES determines that the application server is a basic application server based on the application server type, and the EES determines not to pre-perform traffic influence based on the determination result.

[0509] In another embodiment, the EES determines that the application server is an expected application server based on the application server type, and the EES determines to pre-perform traffic influence based on the determination result.

[0510] For example, the EES determines that the application server is a basic application server based on the response time of the service key performance indicators, and the EES determines not to perform traffic influence in advance.

[0511] In one embodiment, the EES determines, based on the delay requirements of the application clients, that the application clients have higher delay requirements, and the EES determines to proactively perform traffic influence.

[0512] In another embodiment, the EES determines, based on the delay requirements of the application client, that the application client has a lower delay requirement, and the EES determines not to proactively perform traffic influence.

[0513] For example, the EES stores a preset delay threshold. After receiving the request message sent by the EEC, the EES obtains the delay requirement of the application client. If the delay requirement is less than the delay threshold, the EES determines to pre-perform traffic influence for the application client. If the delay requirement is greater than the delay threshold, the EES determines not to pre-perform traffic influence for the application client.

[0514] In some embodiments, after receiving the EAS discovery request message, the EES determines that the EAS discovery request message indicates a request to perform EAS discovery in advance, and based on the determination result, the EES determines to perform traffic influence in advance for an application client corresponding to the EAS discovery request message, or for a terminal device corresponding to the EAS discovery request message.

[0515] Optionally, the EES may further determine whether to perform traffic influence in advance according to the method described in S505. For detailed determination method, please refer to S505. For brevity, the details will not be described again in this specification.

[0516] The EES may perform an EAS discovery procedure as shown in FIG. 2 to determine one or more candidate EASs, and the candidate EAS list may consist of one or more candidate EASs.

[0517] In some embodiments, the EES may select one or more EASs from the candidate EAS list and request the SMF or NEF to perform traffic influence for the one or more EASs.

[0518] Before sending a message for triggering traffic influence, the EES first determines whether to pre-execute traffic influence for the application client based on related information of the attributes of the application client. The determination helps the edge data network provide services based on information such as the type of application client served and delay requirements, helps improve the service efficiency and service quality of the edge data network, helps improve the efficiency of obtaining application services by terminal devices, and helps improve the usage experience of terminal device users.

[0519] Optionally, the EES determines not to pre-perform traffic influence for the same application client based on a determination result indicating not to pre-perform traffic influence for the application client.

[0520] If it is determined not to perform traffic influence proactively, S606 and S607 may no longer be performed. Optionally, the EES stores the determination result indicating not to perform traffic influence proactively.

[0521] Optionally, the EES may send instruction information to the EEC to not perform traffic influence in advance. For details of the contents of this part, please refer to the description of the embodiment shown in Figure 14 below. Details will not be described in this specification.

[0522] S606: The EES triggers traffic influence.

[0523] For details of the process by which the EES triggers traffic influence, please refer to the embodiment shown in Figure 4. The details will not be described again in this specification.

[0524] S607: The EES sends an EAS discovery response message to the EEC.

[0525] The EAS discovery response message is for returning information about one or more candidate EASs to the EEC. The information about one or more EASs may alternatively be sent using an EAS discovery subscription response message, an EAS discovery subscription update response message, or an EAS discovery notification message. The specific bearer message is not limited in this application.

[0526] For example, if one or more discovered EASs meet the application service requirements of the application client, the EES sends an EAS discovery notification message to the EEC, where the EAS discovery notification message includes information about the one or more EASs that meet the requirements.

[0527] In some embodiments, the candidate EAS list may consist of multiple candidate EASs, and the EAS discovery response message includes the candidate EAS list.

[0528] In some embodiments, the EES may send an EAS discovery response message to the EEC. The EAS discovery response message may further include indication information indicating whether the SMF or NEF has been requested to perform traffic influence. If the EES requested to perform traffic influence before the EES sent the EAS discovery response message, the indication information included in the EAS discovery response message may indicate that the SMF or NEF has been requested to perform traffic influence. If the EES did not request to perform traffic influence before the EES sent the EAS discovery response message, the indication information included in the EAS discovery response message may indicate that the SMF or NEF has not been requested to perform traffic influence.

[0529] The EES determines whether the route optimization of the EAS is completed, and the EES returns the EAS with the optimized user plane path to the EEC, so that the EEC can further return the EAS with the optimized user plane path to the application client.

[0530] Specifically, the EES returns information about an EAS having an optimized user plane path and / or DNAI information of the EAS to the EEC. To help improve the efficiency of obtaining application services provided by an application server by an application client and help improve the application experience of a terminal device user, the application client obtains a UE / AC-EAS connection with an optimized user plane path.

[0531] Further, in some other embodiments, the EAS discovery response message further includes indication information indicating whether the EAS has an optimized user plane path, indication information indicating whether traffic influence for the EAS has been completed, or indication information indicating whether user plane path optimization for the EAS has been completed.

[0532] Specifically, the EES returns information about the EAS and DNAI information of the EAS to the EEC, where the DNAI information includes one or more DNAIs and indication information indicating whether the one or more DNAIs have an optimized user plane path.

[0533] For example, one or more DNAIs may be represented in the form of a DNAI list, and the DNAI list may include instruction information.

[0534] After obtaining the indication information indicating whether the EAS has an optimized user plane path, the application client can select an EAS having an optimized user plane path to connect to the EAS based on the indication information, and obtain the application service. The implementation of this embodiment of the present application helps improve the efficiency of obtaining the application service by the application client.

[0535] In this embodiment of the present application, the EEC judges whether to initiate an EAS discovery procedure in advance based on one or more of an application client type, a delay requirement of the application client, and an application server type. Further, after receiving the EAS discovery request message sent by the EEC, the EES judges whether to immediately trigger a traffic influence procedure, so that the SMF or NEF performs traffic influence for the candidate EAS so that the candidate EAS can have the DNAI of the optimized route, or determines that the candidate EAS has the DNAI of the optimized route and does not need to perform traffic influence for the EAS.

[0536] FIG. 8 is a diagram of another method for requesting application capabilities according to an embodiment of the present application.

[0537] In this embodiment of the present application, the EEC decides to perform EAS discovery in advance based on the application client's instruction information, and the EES decides to perform traffic influence in advance for the application client based on the EEC's instruction information.

[0538] S701: The EEC determines to pre-trigger EAS discovery.

[0539] An EAS configured to provide an application service is registered with the EES, stored in the EES, or relevant information of the EAS (e.g., DNAI information) is pre-configured on the EES.

[0540] The instructional information may include instructions for proactively performing EAS discovery and / or instructions for proactively performing traffic influence.

[0541] In some embodiments, the instruction information instructs to perform EAS discovery in advance, and the EEC determines to trigger EAS discovery in advance based on the instruction information for performing EAS discovery in advance.

[0542] In some other embodiments, the instruction information instructs to perform traffic influence in advance, and the EEC determines to trigger EAS discovery in advance based on the instruction information for performing traffic influence in advance.

[0543] In some embodiments, the EEC obtains the indication of the application client by receiving a message sent by the application client to the EEC (eg, a message to request discovery of the EAS).

[0544] In some other embodiments, the EEC obtains the application client's indication in another manner.

[0545] For example, in the process of registering with the enabler client, the application client may send instruction information to the enabler client and include the instruction information in the application client profile, or may include the instruction information in a request message requesting edge computing services sent by the application client to the enabler client.

[0546] The EEC may further determine whether to proactively perform traffic influence based on the instruction information.

[0547] In some embodiments, the instruction information instructs to perform EAS discovery in advance, and the EEC determines to trigger traffic influence in advance based on the instruction information for performing EAS discovery in advance.

[0548] In some other embodiments, the instruction information instructs to perform traffic influence in advance, and the EEC determines to trigger traffic influence in advance based on the instruction information for performing traffic influence in advance.

[0549] Optionally, the EEC determines to perform traffic influence in advance based on the instruction information, and the EEC determines to perform EAS discovery in advance based on a judgment result instructing to perform traffic influence in advance.

[0550] In order to help improve the overall efficiency of serving various application clients by the EEC and improve the usage experience of terminal device users, the EEC immediately triggers EAS discovery according to the application client's instruction information so that the EEC can serve application clients in various operating states.

[0551] S702: The EEC sends an EAS discovery request message to the EES.

[0552] The EAS discovery request message is for requesting the discovery of one or more EASs that provide application services to the application client. The discovery request may alternatively be implemented using a message such as an EAS discovery subscription request message or an EAS discovery subscription update request message. The specific bearer message is not limited in this embodiment of the present application.

[0553] The EAS discovery request message further includes at least one of the following information: EAS discovery filter parameters, terminal device location information, terminal device specific service information, or ECSP policy. After receiving the EAS discovery request message, the EES can determine a candidate EAS based on at least one of the information in the EAS discovery request message.

[0554] In some embodiments, the EAS discovery request message includes EAS discovery filter parameters and indication information indicating to perform traffic influence in advance.

[0555] In one embodiment, a new information element related to delay requirement is added to the EAS discovery request message, which is for storing indication information.

[0556] An example is used as follows:

[0557] Information element name: instructions.

[0558] Information element status: optional or required.

[0559] Information Element Description: Proactively perform EAS discovery and / or proactively perform traffic influence.

[0560] In another embodiment, an existing information element is used in the EAS discovery request message to store the indication information.

[0561] For example, the indication information may be carried in an EAS discovery filter parameter, an application client feature list, an application client profile within an application client feature list, an EAS feature list, or an EAS profile within an EAS feature list.

[0562] In some embodiments, the EAS discovery request message includes an EAS discovery filter parameter and indication information indicating that EAS discovery is to be performed in advance.

[0563] In some other embodiments, the EAS discovery request message includes EAS discovery filter parameters, instruction information instructing to perform traffic influence in advance, and instruction information instructing to perform EAS discovery in advance.

[0564] S703: The EES determines to immediately perform traffic influence.

[0565] The EES may select one or more candidate EASs. Specifically, the EES may select an EAS based on EAS discovery filter parameters, terminal device location information, terminal device specific service information, and / or ECSP policies. For specific EAS discovery procedures, please refer to the relevant description of FIG. 2. Details will not be described again in this specification.

[0566] In some embodiments, the EES determines to immediately perform traffic influence based on instruction information for proactively performing traffic influence included in the EAS discovery request message.

[0567] In some other embodiments, the EES determines to perform traffic influence immediately based on instruction information for performing EAS discovery in advance included in the EAS discovery request message.

[0568] In yet some other embodiments, the EAS discovery request message includes instruction information for instructing to perform EAS discovery in advance and instruction information for instructing to perform traffic influence in advance. After receiving the request message, the EES determines to perform traffic influence in advance based on the instruction information for instructing to perform EAS discovery in advance or the instruction information for instructing to perform traffic influence in advance.

[0569] In yet some other embodiments, the EES determines based on the EAS discovery request message that the request message is a request message to perform EAS discovery in advance, and the EES determines to perform traffic influence immediately based on the determination result.

[0570] Based on the indication information of the application client, it is determined to immediately perform traffic influence. In order to help improve the service quality of the EES and improve the service efficiency of the edge data network, when the EES provides services to multiple application clients simultaneously, the request of the application client that sends the indication information may be preferentially processed.

[0571] Optionally, the EES may further determine whether to perform traffic influence in advance according to the method described in S505. For detailed determination method, please refer to S305. Details will not be described again in this specification.

[0572] S704: The EES triggers traffic influence.

[0573] For details of the process by which the EES triggers traffic influence, please refer to the embodiment shown in Figure 4. The details will not be described again in this specification.

[0574] Optionally, the EES may alternatively send instruction information for triggering traffic influence to the selected EAS, and the instruction information instructs the selected EAS to trigger traffic influence for the EAS. For details of triggering traffic influence by the EAS, please refer to the related description of the embodiment shown in Figure 5. The selected EAS may be determined by the EES, may be determined by the EEC and then declared to the EES, may be determined by the application client and then declared to the EEC, and may be declared to the EES by the EEC.

[0575] S705: The EES sends an EAS discovery response message.

[0576] The contents of S705 are similar to those of S607. For details, please refer to S607. The details will not be described again in this specification.

[0577] In this embodiment of the present application, the EEC determines to pre-initiate an EAS discovery procedure based on the instruction information of the application client, and the EES determines to pre-trigger a traffic influence procedure based on the instruction information of the application client, etc., so that the SMF or NEF is triggered to perform user plane route optimization of the EAS, or the SMF or NEF does not need to perform traffic influence when it determines that the EAS has DNAI of the optimized route.

[0578] FIG. 9 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application.

[0579] In this embodiment of the present application, the application client determines, based on application information, to pre-request the EEC to trigger EAS discovery. The request message sent by the application client to the EEC includes application information and instruction information. After receiving the request message of the application client, the EEC determines whether to pre-perform EAS discovery. The EES determines, based on the EAS discovery message of the EEC, whether to pre-perform traffic influence.

[0580] S801 and S802 are the process by which the EAS is registered with the EES. This process is similar to S601 and S602. For details, please refer to S601 and S602. For the sake of brevity, the details will not be described again in this specification.

[0581] S803: The application client determines whether to proactively perform EAS discovery and / or whether to proactively perform traffic influence.

[0582] In some embodiments, the application client determines to proactively initiate EAS discovery based on the application client's application type.

[0583] In some other embodiments, the application client determines to proactively perform traffic influence based on the application type of the application client.

[0584] In some embodiments, the application client decides to proactively initiate EAS discovery based on the latency requirements of the application client.

[0585] In some other embodiments, the application client determines to proactively perform traffic influence based on the latency requirements of the application client.

[0586] The delay requirement may be a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by an application client. In this specification, the first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, i.e., the first data packet in the data exchange between the application client and the application server.

[0587] The delay requirement of the first packet may indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0588] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0589] In some embodiments, the application client determines to proactively initiate EAS discovery based on the application client's application server type.

[0590] In some other embodiments, the application client determines to proactively perform traffic influence based on the application client's application server type.

[0591] S804: The application client sends a first request message to the EEC.

[0592] The first request message includes application information and instruction information. The application information includes one or more of the following information: application type, application server type, delay requirement, etc. The instruction information includes instructions to pre-perform EAS discovery and / or instructions to pre-perform traffic influence.

[0593] In some embodiments, the EAS discovery request message is to trigger the EEC to perform service provisioning and EAS discovery.

[0594] The application information may include one or more of an application type, an application server type, a delay requirement, etc. The application information may be configured on the EEC in a pre-configured manner, may be sent to the EEC by an application client sending a message to the EEC, or may be obtained by the EEC in other manners. The manner in which the EEC obtains the information that the application information may include is not limited by this application.

[0595] If the first request message does not include one or more pieces of information in the application information, the one or more pieces of information that are not included may be configured on the EEC in a manner such as pre-configuration. In this way, the EEC can make a comprehensive judgment by referring to the contents of the application information and the instruction information obtained through multiple channels.

[0596] S805: The EEC decides whether to conduct EAS discovery in advance.

[0597] The purpose of performing EAS discovery is to determine an EAS suitable for providing an application service to an application client and a manner of accessing the EAS. In this specification, performing EAS discovery in advance means performing EAS discovery before an application client is launched or before an application client exchanges data with an EAS.

[0598] The EEC performs a comprehensive judgment based on the application information and the instruction information to decide to pre-perform EAS discovery.

[0599] For example, the application type and / or delay requirement in the application information indicates not to proactively perform EAS discovery for the application client, but the instruction information indicates to proactively perform EAS discovery, in which case, after separately completing respective determinations based on the application information and the instruction information, the EEC determines to proactively perform EAS discovery for the application client.

[0600] Referring to the application information and instruction information to comprehensively judge whether to perform EAS discovery in advance helps to improve the adaptability of the EEC in a complex service environment (e.g., various application clients and various service requirements), improves the quality of services provided to users by terminal devices, and helps to improve the user's application service experience.

[0601] Optionally, the EEC performs a comprehensive judgment based on the application information and the instruction information to judge to perform traffic influence in advance, and the EEC judges to perform EAS discovery in advance based on the judgment result instructing to perform traffic influence in advance. For the content of the EEC's judgment to perform traffic influence in advance, please refer to S503. For the sake of brevity, the details will not be described again in this specification.

[0602] S806: The EEC sends an EAS discovery request message to the EES.

[0603] The EAS discovery request message includes application information and / or indication information.

[0604] In some embodiments, the EAS discovery request message further includes one or more of the following information: EAS discovery filter parameters, terminal device location information, terminal device specific service information, or ECSP policies. After receiving the EAS discovery request message, the EES can select a candidate EAS based on at least one of the aforementioned information in the EAS discovery request message.

[0605] In some other embodiments, the EAS discovery request message further includes indication information indicating that the EAS discovery request is a request to pre-perform EAS discovery.

[0606] S807: The EES determines whether to immediately trigger traffic influence.

[0607] In some embodiments, the EES performs a comprehensive decision based on the application information and the indication information to determine whether to immediately trigger traffic influence.

[0608] For example, the application type and / or delay requirement in the application information indicates not to pre-perform traffic influence for the application client, while the indication information is to request to pre-perform traffic influence, in which case, after separately completing respective determinations based on the application information and the indication information, the EES determines to pre-perform traffic influence for the application client.

[0609] The EES can select one or more candidate EASs based on one or more of the following information: EAS discovery filter parameters, terminal device location information, terminal device specific service information, or ECSP policies. The candidate EAS list can consist of one or more candidate EASs. The EES can select one or more EASs from the candidate EAS list and trigger the SMF or NEF to perform traffic influence for the one or more EASs.

[0610] In some embodiments, the EES receives application information and instruction information for proactively triggering EAS discovery. The EES determines not to proactively perform traffic influence for the application client based on the application information, and the EES determines to proactively perform EAS discovery based on the instruction information for proactively triggering EAS discovery.

[0611] In some other embodiments, the EES receives application information and instruction information for pre-triggering traffic influence, and the EES directly decides to perform EAS discovery and traffic influence in advance based on the instruction information for pre-triggering traffic influence.

[0612] Referring to the application information and the instruction information to comprehensively judge whether to perform EAS discovery in advance helps to improve the adaptability of the EES in a complex service environment (e.g., various application clients and various service requirements), helps to improve the quality of services provided to application clients by the edge data network, and helps to improve the efficiency of obtaining application services by application clients.

[0613] S808: The EES triggers traffic influence.

[0614] For details of the process by which the EES triggers traffic influence, please refer to the embodiment shown in Figure 4. The details will not be described again in this specification.

[0615] S809: The EES sends an EAS discovery response message.

[0616] In some embodiments, the EES pre-performs EAS discovery, and the discovery response message includes information regarding one or more EASs.

[0617] In some other embodiments, the EES pre-triggers EAS discovery and traffic influence, and the discovery response message includes information about one or more EASs and / or indication information indicating that traffic influence has been triggered for one or more EASs.

[0618] Optionally, the EAS discovery response message may further include indication information indicating that traffic influence for one or more EASs has been completed.

[0619] S810: The EEC sends a first response message to the application client.

[0620] The first response message is for transmitting information about the candidate EAS to the application client.

[0621] In some embodiments, the EEC selects an EAS for which traffic influence is triggered from the candidate EASs, and sends the EAS to the application client. Optionally, the EEC further includes, in the information about the selected EAS, indication information indicating that "traffic influence is triggered for the EAS".

[0622] In some embodiments, the EEC selects an EAS for which traffic influence has been completed from the candidate EASs, and sends the EAS to the application client. Optionally, the EEC further includes, in the information about the selected EAS, indication information indicating that traffic influence has been completed for the EAS.

[0623] Specifically, the EEC returns information about an EAS having an optimized user plane path and / or DNAI information of that EAS to the application client.

[0624] In some other embodiments, the EEC does not select the candidate EASs, and the EEC sends information about one or more EASs to the application client in a first response message, the first response message further including indication information indicating whether traffic influence for the EASs has been completed.

[0625] Specifically, the EEC returns information about the EAS and DNAI information of the EAS to the application client, where the DNAI information includes one or more DNAIs and indication information indicating whether the one or more DNAIs have an optimized user plane path.

[0626] For example, one or more DNAIs may be represented in the form of a DNAI list, and the instruction information may alternatively be included in the DNAI list.

[0627] S811: The application client detects whether traffic influence has been completed for the returned EAS.

[0628] In some embodiments, the application client transmits a selected EAS to the EEC and requests to obtain an indication indicating whether traffic influence has been completed for the selected EAS.

[0629] In some other embodiments, the first response message includes indication information (e.g., DNAI information of the EAS) indicating whether traffic influence has been completed for the candidate EAS, and the application client determines whether traffic influence has been completed for the selected EAS based on the indication information.

[0630] It should be understood that if the application client determines that traffic influence has been completed for the returned EAS, that the returned EAS has an optimized user plane path, or that user plane path optimization for the returned EAS has been completed, then S812 and S813 do not need to be executed.

[0631] S812: The application client sends a message to the EAS to request execution of traffic influence.

[0632] In some embodiments, after receiving the EAS discovery response message, the application client detects that the returned EAS does not have an optimized user plane path. The application client determines to perform traffic influence in advance based on information such as application type and delay requirement. The application client sends a connection request message to the selected EAS before the application client is launched, and the connection request message includes the UE ID. After receiving the connection request message, the EAS triggers traffic influence.

[0633] Since the DNAI for accessing the EAS has been obtained, the application client can directly connect to the EAS and request the EAS to directly trigger traffic influence. To help improve the stability of obtaining an application service by the application client, when the application client cannot establish a connection to the EEC and cannot use the EES to trigger traffic influence for the target EAS, the technical solution provides the application client with another way to obtain an application service.

[0634] In some other embodiments, an application client sends a message to an EEC to request performance of traffic influence.

[0635] The message for requesting to perform traffic influence may include application information and / or instruction information. After receiving the message, the EEC can determine whether to perform traffic influence in advance based on the application information and / or instruction information. For a specific determination process, see S503. For brevity, details will not be described again in this specification.

[0636] Optionally, the message for requesting to perform traffic influence may further carry identification information, which identifies the target EAS for which traffic influence is requested to be performed as an EAS discovered using a pre-executed EAS discovery procedure. After obtaining the identification information, the EEC decides to pre-trigger traffic influence for the target EAS.

[0637] Optionally, the EEC stores information about an EAS discovery procedure for obtaining a target EAS. The EEC can identify the target EAS and determine that the EAS is an EAS discovered using a pre-executed EAS discovery procedure, and thereby pre-trigger traffic influence for the target EAS.

[0638] After determining to pre-trigger traffic influence for the target EAS, the EEC declares relevant information of the target EAS to the EES. After the EES receives information about the target EAS, it triggers traffic influence for the target EAS or the target application client, or the EES sends a message to the target EAS to request the execution of traffic influence, and the target EAS triggers traffic influence.

[0639] In yet some other embodiments, if the selected EAS determines that it has DNAI for the optimized user plane path, the application client may not need to request the selected EAS to perform traffic influence.

[0640] S813: The EAS triggers traffic influence.

[0641] For specific details of triggering traffic influence by EAS, please refer to the description of the embodiment shown in Figure 5. Details will not be described again in this specification.

[0642] In this embodiment of the present application, the application client decides to perform EAS discovery or traffic influence in advance based on the type of the client or the delay requirement of the application client. The EEC decides whether to initiate the EAS discovery procedure in advance based on the application information and the indication information. Furthermore, the EES decides whether to immediately trigger the traffic influence procedure, i.e., whether to trigger the SMF or NEF to perform traffic influence, or whether the target EAS has an optimized user plane path based on the application information, the indication information, etc.

[0643] FIG. 10 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application.

[0644] In this embodiment of the present application, the EEC comprehensively judges whether to perform EAS discovery in advance based on application information and instruction information. After performing EAS selection, the EES directly feeds back candidate EASs to the EEC. The EEC selects an EAS from the candidate EASs, sends the selected EAS to the EES, and requests the EES to perform traffic influence for the selected EAS. The EES judges whether to perform traffic influence in advance after receiving related information (e.g., application server type) of the selected EAS declared by the EEC, or after receiving a declaration event in which information about the selected application server is declared.

[0645] S901 and S902 are the process by which the EAS is registered with the EES. This process is similar to S601 and S602. For details, please refer to S601 and S602. For the sake of brevity, the details will not be described again in this specification.

[0646] S903 and S904 are similar to S805 and S806, respectively. For details, please refer to S805 and S806. For the sake of brevity, the details will not be described again in this specification.

[0647] S905: The EES sends an EAS discovery response message to the EEC.

[0648] In some embodiments, the EES may not be configured to have the function of determining whether to perform traffic influence in advance based on application information and / or instruction information. After receiving the EEC's EAS discovery request message, the EES performs EAS discovery and feeds back information about one or more candidate EASs to the EEC.

[0649] For detailed procedures of performing EAS discovery by EES, please refer to the related description of Figure 2.

[0650] The information about one or more candidate EASs may alternatively be sent using an EAS discovery subscription response message, an EAS discovery subscription update response message, or an EAS discovery notification message. The specific bearer message is not limited in this application.

[0651] For example, if one or more discovered EASs meet the application service requirements of the application client, the EES sends an EAS discovery notification message to the EEC, where the EAS discovery notification message includes information about the one or more EASs that meet the requirements.

[0652] S906: The EEC selects the target EAS.

[0653] A target EAS, sometimes referred to as a selected EAS, is an EAS that is selected from one or more obtained candidate EASs and that is configured to provide an application service to an application client.

[0654] The EEC selects a target EAS based on one or more candidate EASs fed back in the EAS discovery response message.

[0655] Optionally, the target EAS may alternatively be determined by the enabler server or the application client. After selecting the EAS, the application client can declare the selected EAS to the EEC. After receiving the EAS selected by the application client, the EEC declares the selected EAS to the EES.

[0656] S907: The EEC determines whether to pre-execute traffic influence based on the application information and the instruction information.

[0657] In some embodiments, the application information includes one or more of the following information: application type, application server type, and delay requirements.

[0658] In some embodiments, the instructional information includes instructions for proactively performing EAS discovery and / or instructions for proactively performing traffic influence.

[0659] In some other embodiments, the EEC determines to pre-trigger traffic influence based on instruction information of the application client.

[0660] In yet some other embodiments, the EEC determines to proactively perform traffic influence based on application information of the application client.

[0661] In yet some other embodiments, the EEC determines to pre-trigger EAS discovery by reference to the application information and the instruction information.

[0662] For example, the application type and / or delay requirement in the application information indicates not to pre-perform traffic influence for the application client, while the indication information is to request to pre-perform traffic influence, in this case, after separately completing respective determinations based on the application information and the indication information, the EEC determines to pre-perform traffic influence for the application client.

[0663] The EEC may determine whether to perform traffic influence in advance based on a request from an application client, or may determine whether to perform traffic influence in advance based on a request from an application client. If the EES is not configured to have the function of determining whether to perform traffic influence in advance based on application information or instruction information, the EEC may request the EES to trigger traffic influence for a selected EAS after obtaining information about the candidate EAS. This technical solution helps improve the stability of providing application services to application clients by edge data networks, and helps improve the experience of obtaining application services by application clients.

[0664] S908: The EEC sends an instruction message to the EES to perform traffic influence for the target EAS.

[0665] The instruction message includes information about the target EAS and one or more DNAIs that may be for accessing the target EAS.

[0666] In some embodiments, the instructional message may further include instructional information and / or application information for proactively performing traffic influence.

[0667] In some embodiments, the EEC first sends information about the target EAS and one or more DNAIs for accessing the target EAS to the EES, and then determines to perform traffic influence in advance based on the application information and / or instruction information, and then the EEC sends instruction information for performing traffic influence in advance to the EES based on the determination result.

[0668] The target EAS may also be referred to as a selected EAS. Information about the target EAS may be carried in a selected edge application server declaration message or in another message, which is not limited in this application. The selected edge application server declaration message may further include application information and / or instruction information. After receiving the selected edge application server declaration message, the EES can determine whether to pre-execute traffic influence for the selected EAS. For the determination process, please refer to S505. Details will not be described again in this specification.

[0669] S909: The EES determines whether to perform traffic influence in advance.

[0670] In some embodiments, the EES decides to proactively perform traffic influence based on information about selected application servers declared by the EEC.

[0671] In some other embodiments, the EES decides to proactively perform traffic influence based on a declaration event of information about the selected application server declared by the EEC.

[0672] For example, after getting an announcement event of a selected application server announced by the EEC, the EES immediately triggers a pre-executed traffic influence for the selected application server.

[0673] In this technical solution, the declaration information or declaration event of the terminal device is used as a criterion for the EES to judge whether to perform traffic influence in advance. The criterion may be generated by the terminal device, and the judgment process is performed by the edge data network. Implementing the technical solution helps the edge data network manage the process of obtaining application services by various terminal devices, helps improve the efficiency of providing application services by the edge data network, helps maintain the service stability of the edge data network, helps improve the efficiency of obtaining application services by the terminal devices, and helps reduce the waste of network resources.

[0674] S910: The EES triggers traffic influence.

[0675] For details of the process by which the EES triggers traffic influence, please refer to the embodiment shown in Figure 4. The details will not be described again in this specification.

[0676] S911: The EES sends an acknowledgement message to the EEC.

[0677] This acknowledgement message indicates that traffic influence is being performed for the selected EAS.

[0678] Optionally, the acknowledgement message further indicates whether traffic influence has been completed for the selected EAS.

[0679] In this embodiment of the present application, the EEC judges to pre-initiate an EAS discovery procedure based on the indication information and / or the application information of the application client. After the EES feeds back the candidate EASs to the EEC, the EEC again judges to pre-perform traffic influence and sends the selected EAS to the EES. The EES triggers traffic influence to perform user plane path optimization for the target EAS based on the declared information about the selected EAS or the declared event in which the selected EAS is selected, or judges that the target EAS has the DNAI of the optimized user plane path and does not need to perform traffic influence.

[0680] FIG. 11 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application.

[0681] In this embodiment of the present application, after performing the EAS discovery procedure, the application client determines whether to proactively perform traffic influence based on the application type, application server type, delay requirements, and so on.

[0682] S1001 and S1002 are the process by which the EAS is registered with the EES. This process is similar to S601 and S602. For details, please refer to S601 and S602. For the sake of brevity, the details will not be described again in this specification.

[0683] S1003: The EEC determines whether to perform EAS discovery in advance.

[0684] The contents of S1003 are similar to those of S603. For details, please refer to S603. For the sake of brevity, the details will not be described again in this specification.

[0685] Optionally, the EEC may further determine whether to pre-perform EAS discovery based on the application information and / or instruction information.

[0686] Optionally, the application information and / or the instruction information may be sent by the application client to the EEC, that is, a step of receiving the application information and / or the instruction information from the application client by the EEC may be further included before S1003.

[0687] S1004: The EEC transmits an EAS discovery request message to the EES.

[0688] The contents of S1004 are similar to those of S604. For details, please refer to S604. For the sake of brevity, the details will not be described again in this specification.

[0689] S1005: The EES transmits an EAS discovery response message to the EEC.

[0690] The contents of S1005 are similar to those of S607. For details, please refer to S607. For the sake of brevity, the details will not be described again in this specification.

[0691] S1006: The EEC sends a first response message to the application client.

[0692] The contents of S1006 are similar to those of S810. For details, please refer to S810. For the sake of brevity, the details will not be described again in this specification.

[0693] S1007: The application client determines whether to preliminarily request the EAS to perform traffic influence.

[0694] In some embodiments, the application client decides to pre-perform traffic influence based on the delay requirements of the service.

[0695] In some other embodiments, the application client decides not to proactively perform traffic influence based on the delay requirements of the service.

[0696] In some embodiments, the application client pre-determines to perform traffic influence based on the application client type.

[0697] In some other embodiments, the application client determines not to pre-perform traffic influence based on the application client type.

[0698] In some embodiments, the application client pre-determines to perform traffic influence based on the application server type.

[0699] In some other embodiments, the application client determines not to pre-perform traffic influence based on the application server type.

[0700] In some embodiments, the application client decides to pre-perform traffic influence based on one or more of the following information: service type, application client type, application server type, or delay requirement.

[0701] In some other embodiments, the application client decides not to proactively perform traffic influence based on one or more of the following information: service type, application client type, application server type, or delay requirements.

[0702] In some other embodiments, the application client determines to pre-perform traffic influence based on the determination result stored in S1003.

[0703] In yet some other embodiments, the application client sends a query message to the EEC to obtain indication information indicating whether traffic influence for one or more application servers has been completed. After determining whether traffic influence for the application servers has been completed, the application client determines whether to pre-perform traffic influence.

[0704] S1008: The application client sends a message to the EAS to request execution of traffic influence.

[0705] The application client sends instruction information to request triggering of traffic influence to a selected EAS, which may be determined by the application client, or by the EEC or EES.

[0706] The contents of S1008 are similar to those of S812. For details, please refer to S812. For the sake of brevity, the details will not be described again in this specification.

[0707] In the case of an EEC that is not configured to determine whether to pre-perform EAS discovery based on application information or instruction information and an EES that is not configured to determine whether to pre-perform traffic influence based on application information or instruction information, the application client may determine whether to pre-perform traffic influence after obtaining a manner to connect to a candidate EAS. If traffic influence needs to be pre-performed, the application client may directly request the target EAS to trigger a request to perform traffic influence for the target EAS. This technical solution helps to improve the stability of obtaining application services by the application client, and helps to improve the quality of application services and the efficiency of obtaining application services by the application client.

[0708] S1009: The EAS triggers traffic influence.

[0709] For details of the process by which the EAS triggers traffic influence, please refer to the embodiment shown in Figure 5. The details will not be described again in this specification.

[0710] That is, after determining the selected EAS, the application client can directly request the selected EAS to trigger traffic influence, or the application client can declare the selected EAS to the EEC, and finally the EES triggers traffic influence, or the EES requests the selected EAS to trigger traffic influence.

[0711] S1010: The EAS sends an acknowledgement message to the application client.

[0712] In some embodiments, after receiving information about the target DNAI sent by the SMF or NEF, the EAS determines that the EAS has an optimized user plane path, and the EAS sends an acknowledgement message to the application client, where the acknowledgement message indicates that the returned EAS has an optimized user plane path.

[0713] In this embodiment of the present application, after the EAS discovery procedure is performed, the application client obtains the candidate EAS list. Before needing to obtain an application service, the application client determines to pre-perform traffic influence based on the application client's application type or delay requirement, and thereby triggers the EAS to pre-perform traffic influence.

[0714] FIG. 12 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application.

[0715] In this embodiment of the present application, the ECS determines whether to perform traffic influence in advance based on application information and / or instruction information, and the traffic influence is for establishing an optimized user plane path between the UE and the EES.

[0716] S1101: The EES transmits an EES registration request message to the ECS.

[0717] This registration request message is for requesting to register the EES in the ECS. The registration request message may include an EES profile. The EES profile includes a DNAI list. A terminal device or an application client can access the EES using a DNAI in the DNAI list.

[0718] In some embodiments, the EES sends an EES registration update request message to the ECS, where the EES registration update request message is to request an update of registration information of the EES registered with the ECS.

[0719] Optionally, the DNAI information of the EES may be included directly in the registration request message.

[0720] Alternatively, optionally, relevant information of the EES (e.g., DNAI information of the EES) may be configured in a pre-configured manner on the ECS.

[0721] S1102: The ECS transmits a registration response message to the EES.

[0722] The registration response message indicates whether the EES registration is successful. When the ECS receives the registration update request message sent by the EES, it sends an EES registration update response message to the EES.

[0723] If the EES registration is successful, the registration response message may include an EES registration ID and an expiration date of the EES registration. If the EES registration is unsuccessful, the registration response message may include information regarding the cause of the EES registration failure.

[0724] S1103: The application client determines whether to proactively perform EES discovery and / or whether to proactively perform traffic influence.

[0725] In some embodiments, if the application client determines to proactively initiate EES discovery based on the application client's application type, the application client can proactively request the EEC to discover the EES.

[0726] In some other embodiments, the application client can pre-request the EEC to discover the EES if the application client pre-determines to perform traffic influence based on the application type of the application client.

[0727] In some embodiments, if the application client determines to proactively initiate EES discovery based on the application client's latency requirements, the application client proactively requests the EEC to discover the EES.

[0728] In some other embodiments, the application client can proactively request the EEC to discover the EES if it determines to proactively perform traffic influence based on the application client's delay requirements.

[0729] The delay requirement may be a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by an application client. In this specification, the first packet is the first data packet sent by the application client to the application server in the course of communication between the application client and the application server, i.e., the first data packet in the data exchange between the application client and the application server.

[0730] The delay requirement of the first packet may indicate the overall delay requirement or the average delay requirement of all data packets in the course of a data exchange between the application client and the application server.

[0731] Alternatively, the delay requirement of the first packet may indicate a characteristic value of the delay requirements of some or all of the data packets within a certain period of time in the course of data exchange between the application client and the application server, for example the arithmetic or geometric mean value of the delay requirements of all data packets in the course of the first interaction between the application client and the application server.

[0732] In some embodiments, if the application client determines to proactively initiate EES discovery based on the application client's application server type, the application client proactively requests the EEC to discover the EES.

[0733] In some other embodiments, the application client can pre-request the EEC to discover the EES if the application client pre-determines to perform traffic influence based on the application server type of the application client.

[0734] In some embodiments, the application client does not determine whether to proactively perform EES discovery and / or whether to proactively perform traffic influence. The determination may be made using the EEC. That is, S1103 is optional.

[0735] S1104: The application client sends a first request message to the EEC.

[0736] The first request message includes application information and / or instruction information. The application information includes one or more of the following information: application type, application server type, delay requirement, etc. The instruction information includes instructions to pre-perform EES discovery and / or instructions to pre-perform traffic influence.

[0737] In some embodiments, the application information of the application client is configured on the EEC in a pre-configured manner, and the application client does not send the first request message to the EEC, that is, S1104 is optional.

[0738] The application information may include one or more of an application type, an application server type, a delay requirement, etc. The application information may be configured on the EEC in a pre-configured manner, may be sent to the EEC by an application client sending a message to the EEC, or may be obtained by the EEC in other manners. The manner in which the EEC obtains the information that the application information may include is not limited by this application.

[0739] If the first request message does not include one or more pieces of information in the application information, the one or more pieces of information that are not included may be configured on the EEC in a manner such as pre-configuration. In this way, the EEC can make a comprehensive judgment by referring to the contents of the application information and the instruction information obtained through multiple channels.

[0740] S1105: The EEC decides whether to conduct EES discovery in advance.

[0741] The purpose of performing EES discovery is to determine an EES suitable for providing services to an end device and a manner of accessing the EES. Performing EES discovery in advance means performing EES discovery before an application client is launched or before an end device exchanges data with an EES. Performing in advance is also called performing in advance or performing immediately.

[0742] The EES determined using the EES discovery procedure and suitable for serving the terminal device may be referred to as a candidate EES. For the specific EES discovery procedure, please refer to the relevant description in FIG. 3.

[0743] The EEC can determine whether to perform EES discovery in advance based on the application information, where the application information includes one or more of the following information: application type, application server type, delay requirement, and so on.

[0744] The EEC may alternatively determine whether to perform EES discovery in advance based on instruction information, where the instruction information includes instructions for performing EES discovery in advance and / or instructions for performing traffic influence in advance.

[0745] Alternatively, the EEC may determine whether to perform EES discovery in advance based on the application information and the instruction information.

[0746] Alternatively, the EEC may determine to perform traffic influence in advance based on the application information and / or the instruction information, and the EEC determines to perform EES discovery in advance based on the determination result.

[0747] The content of determining whether to perform EES discovery in advance by the EEC based on the application information and / or instruction information is similar to the content of determining whether to perform EAS in advance by the EEC based on the application information and / or instruction information. For details, please refer to S304, S603, S501, S805, etc. For brevity, the details will not be described again in this specification.

[0748] If it is determined not to perform EES discovery in advance, S1106 to S1110 may no longer be performed. Optionally, the EEC stores a determination result indicating not to perform EES discovery in advance.

[0749] Optionally, the EEC may send instruction information to the application client to not perform EES discovery in advance. The content of this part is the same as the description of the embodiment shown in Fig. 15 below. For details, please refer to the embodiment shown in Fig. 15. Details are not described in this specification.

[0750] Before sending a request message requesting to perform EES discovery, the EEC first judges whether to perform EES discovery in advance. The judging criterion is related information of attributes of the application client and / or the operating status of the terminal device. By judging, the EEC can perform differentiated services based on each application client and each operating status when serving the application client, so as to help improve the service efficiency of the terminal device, help appropriately allocate the resources of the terminal device, and help improve the user's application usage experience.

[0751] S1106: The EEC sends a service provisioning request message to the ECS.

[0752] The service provisioning request message is for requesting to discover one or more EESs to provide services to the terminal device. The service provisioning request may alternatively be carried in a message such as an EES discovery subscription request message or an EES discovery subscription update request message. The specific bearer message is not limited in this embodiment of the present application.

[0753] The service request message includes one or more of the following information: the location of the terminal device, service requirements, service preferences, or connectivity. The ECS can determine one or more EESs that can provide services to the terminal device based on one or more of the aforementioned information.

[0754] In some embodiments, the service request message includes an application client type.

[0755] In one embodiment, the service request message includes an application client profile, which includes an application client type.

[0756] In some other embodiments, the service provisioning request message includes information regarding the latency requirements of the application client.

[0757] In one embodiment, a delay requirement related information element is added to the service provisioning request message, which is for storing the delay requirement of the application client.

[0758] An example is used as follows:

[0759] Information element name: Delay requirement

[0760] Information element status: optional or required.

[0761] Information element description: 0.1 ms or less.

[0762] In another embodiment, an existing information element is used in the service provisioning request message to store the delay requirement of the application client.

[0763] In some embodiments, the service provisioning request message includes an application server type.

[0764] In one embodiment, the service provisioning request message includes one or more service key performance indicators that may be for determining the application server type.

[0765] For example, the service provisioning request message includes at least one of the service key performance indicator parameters of the application server: connection bandwidth, request rate, response time, availability, required computing resources, image computing resources, memory resources, or storage resources.

[0766] In some embodiments, the service provisioning request message includes instruction information instructing to pre-perform traffic influence and / or instruction information instructing to pre-perform EES discovery.

[0767] In one embodiment, a new information element related to delay requirement is added to the EAS discovery request message, which is for storing indication information.

[0768] An example is used as follows:

[0769] Information element name: instructions.

[0770] Information element status: optional or required.

[0771] Information Element Description: Proactively perform EES discovery and / or proactively perform traffic influence.

[0772] In another embodiment, an existing information element is used in the EES discovery request message to store the indication information.

[0773] S1107: ECS determines whether to perform traffic influence in advance.

[0774] Immediately executing traffic influence may also be referred to as pre-executing, pre-executing, etc. Because traffic influence is executed by either the SMF or the NEF, executing herein may be understood as triggering the execution.

[0775] The content of the ECS determining whether to perform traffic influence based on the application information and / or the instruction information is similar to the content of the EES determining whether to perform traffic influence in advance based on the application information and / or the instruction information. For details, please refer to S505, S605, S503, and S803. For brevity, the details will not be described again in this specification.

[0776] S1108: The ECS triggers traffic influence.

[0777] The content of triggering traffic influence by ECS in S1108 is similar to the content of triggering traffic influence by EES in Fig. 4. For example, in the process of triggering traffic influence by ECS, ECS sends an application function request message to SMF. The content is similar to the content of sending an application function request message to SMF by EES in S301 in Fig. 4. For specific content, please refer to the related description in Fig. 4. Details will not be described again in this specification.

[0778] Optionally, the EES may alternatively trigger traffic influence. The content of triggering traffic influence by the EES is similar to the content of triggering traffic influence by the EAS in FIG. 5. For example, in the process of triggering traffic influence by the EES, the EES sends an application function request message to the SMF. The content is similar to the content of sending an application function request message to the SMF by the EAS in S401 in FIG. 5. For specific content, please refer to the related description of FIG. 5. Details will not be described again in this specification.

[0779] If it is determined not to perform traffic influence in advance, S1108 to S1110 may no longer be performed. Optionally, the ECS stores the determination result indicating not to perform traffic influence in advance.

[0780] Optionally, the ECS can send instruction information to the EEC to not perform traffic influence in advance. The content of this part is the same as the description of the embodiment shown in Figure 14 below. For details, please refer to the embodiment shown in Figure 14. Details will not be described in this specification.

[0781] S1109: The ECS sends a service provisioning response message to the EEC.

[0782] The service provisioning response message is for returning information about one or more candidate EESs to the EEC. The information about one or more EESs may alternatively be sent using an EES discovery subscription response message, an EES discovery subscription update response message, or an EES discovery notification message. The specific bearer message is not limited in this application.

[0783] In some embodiments, the ECS may send a service provisioning response message to the EEC. The service provisioning response message further includes indication information indicating whether the SMF or NEF has been requested to perform traffic influence. If the ECS requested to perform traffic influence before the ECS sent the service provisioning response message, the indication information included in the service provisioning response message indicates that the SMF or NEF has been requested to perform traffic influence. If the ECS did not request to perform traffic influence before the ECS sent the service provisioning response message, the indication information included in the service provisioning response message indicates that the SMF or NEF has not been requested to perform traffic influence.

[0784] In some embodiments, the ECS determines whether route optimization of the EES is completed, and the ECS returns the EES with the optimized user plane path to the EEC, so that the EEC can further return the EES with the optimized user plane path to the application client.

[0785] Specifically, the EES returns information about the EES with the optimized user plane path and / or DNAI information of the EES to the EEC. To help improve the efficiency of obtaining application services provided by the application server by the application client and help improve the application experience of the terminal device user, the application client obtains a UE / AC-EAS connection with the optimized user plane path.

[0786] In some other embodiments, the service provisioning response message includes information about the EES and an indication of whether the EES has an optimized user plane path.

[0787] Specifically, the ECS returns information regarding the EES and DNAI information to the EEC, where the DNAI information includes one or more DNAIs and indication information, and the indication information indicates whether the one or more DNAIs have an optimized user plane path.

[0788] For example, one or more DNAIs may be represented in the form of a DNAI list, and the DNAI list may include instruction information.

[0789] After obtaining the indication information indicating whether the EES has an optimized user plane path, the application client can select an EES with an optimized user plane path to connect to the EES based on the indication information, and obtain the application service. The implementation of this embodiment of the present application helps improve the efficiency of obtaining the application service by the application client.

[0790] S1110: The EEC sends a first response message to the application client.

[0791] The first response message is for transmitting information about one or more candidate EESs to the application client.

[0792] In some embodiments, the EEC selects an EES for which traffic influence has been completed from one or more candidate EESs, and sends the EES to the application client. Optionally, the first response message further indicates that "traffic influence has been triggered for the EES."

[0793] Specifically, the EEC returns information regarding an EES having an optimized user plane path and / or DNAI information of the EES to the application client.

[0794] In some other embodiments, the EEC does not select one or more candidate EESs, and the EEC sends information about the one or more EESs to the application client in a first response message, the first response message further including indication information indicating whether traffic influence is triggered for the one or more EESs.

[0795] Specifically, the EEC returns information about the EES and DNAI information of the EES to the application client, where the DNAI information includes one or more DNAIs and indication information indicating whether the one or more DNAIs have an optimized user plane path.

[0796] For example, one or more DNAIs may be represented in the form of a DNAI list, and the instruction information may alternatively be included in the DNAI list.

[0797] Optionally, the first response message further indicates whether traffic influence has been completed for one or more EES.

[0798] It should be understood that Figure 12 illustrates a possible implementation case in which the ECS triggers traffic influence for the EES based on the judgment information. The technical contents described in Figures 4 to 11 of triggering traffic influence for the EAS by the application client, the EEC, or the EES based on the judgment information may be applied to the embodiments shown in Figure 12 by those skilled in the art without creative efforts to form a new implementation. For the sake of clarity and conciseness, this application does not provide the description one by one.

[0799] The above describes in detail some embodiments used when it is determined to perform traffic influence in advance with reference to Figures 4 to 12. In the following, with reference to Figures 13 and 14, embodiments used when the EEC determines not to perform EAS discovery in advance and / or not to perform traffic influence in advance and the EES determines not to perform traffic influence in advance will be described in detail. Implementations used when the EEC determines not to perform EES discovery in advance and / or not to perform traffic influence in advance and the ECS determines not to perform traffic influence in advance are similar to this and may be performed with reference thereto.

[0800] FIG. 13 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application.

[0801] In this embodiment of the present application, the EEC decides to proactively perform EAS discovery, and the EES decides not to proactively perform traffic influence based on application information.

[0802] S1201: The EEC decides whether to perform EAS discovery in advance.

[0803] The method of determining whether to perform EAS discovery in advance by the EEC is similar to the content described in S501 of Figure 6. For details, please refer to S501. The details will not be described again in this specification.

[0804] S1202: The EEC transmits an EAS discovery request message.

[0805] The EAS discovery request message sent by the EEC to the EES includes application information, which includes one or more of the following information: application type, application server type, delay requirement, and so on.

[0806] Optionally, the EAS discovery request message may further include instruction information for performing EAS discovery in advance.

[0807] S1203: The EES determines whether to perform traffic influence in advance.

[0808] The EES determines not to perform traffic influence in advance based on the application information included in the EAS discovery request message.

[0809] S1204: Optionally, the EES stores decision result information instructing not to perform traffic influence in advance.

[0810] The determination result information includes one or more of the following information: a determination result indicating not to pre-perform traffic influence, an identifier of the application client, or information regarding one or more EASs, where the one or more EASs are determined using an EAS discovery procedure.

[0811] The stored decision result information indicating not to proactively perform traffic influence is used by the EES to determine whether to proactively perform traffic influence for the same application client (target application client) next time.

[0812] Specifically, the EES that receives the application information of the target application client sent by the EEC does not determine whether to pre-perform traffic influence based on the application information, and the EES may determine not to pre-perform traffic influence for the target application client based on the determination result information instructing not to pre-perform traffic influence. When the EES receives the instruction information sent by the EEC to pre-perform traffic influence for the target application client, the EES determines to pre-perform traffic influence.

[0813] In some embodiments, the EAS discovery request message sent by the EEC and received by the EES includes instruction information for pre-performing EAS discovery. The EES pre-performs an EAS discovery procedure based on the instruction information for pre-performing EAS discovery to determine one or more EASs for the target application client. The one or more EASs may also be referred to as candidate EASs.

[0814] If the EES has previously performed an EAS discovery procedure, the determination result information may include information about one or more EASs.

[0815] S1205: Optionally, the EES transmits instruction information to the EEC.

[0816] The indication information indicates that traffic influence is not to be performed in advance. The indication information may include one or more of the following information: a determination result indicating that traffic influence is not to be performed in advance, an identifier of the application client, or information regarding one or more EASs. The one or more EASs are one or more EASs determined by the EES using an EAS discovery procedure.

[0817] If the instruction information includes a judgment result instructing not to pre-perform traffic influence and an identifier of the application client, the EEC can determine not to pre-perform EAS discovery for the target application client based on the received judgment result information, and does not need to perform a judgment based on the application information.

[0818] If the instruction information includes a judgment result instructing not to perform traffic influence in advance, an identifier of the application client, and information regarding one or more EASs, the EEC can determine a selected EAS from the one or more EASs, and the EEC can declare the selected EAS to the EES to trigger the EES to perform traffic influence for the selected EAS.

[0819] Optionally, the EEC may alternatively send information about the selected EAS to the application client. After obtaining the information about the selected EAS, the application client can directly request the selected EAS to trigger traffic influence.

[0820] Optionally, the EEC may alternatively send information about one or more EASs to the application client. The application client determines a selected EAS from one or more EASs and then sends the selected EAS to the EEC, so that the EEC requests the EES to trigger traffic influence for the selected EAS. Alternatively, the application client requests the selected EAS to trigger traffic influence.

[0821] In some embodiments, the EEC stores the instruction information, and the stored judgment result can be used by the EEC to determine whether to proactively perform EAS discovery or traffic influence for the application client next time.

[0822] In some embodiments, the EEC sends a judgment result instructing not to pre-execute traffic influence to the application client, and the application client performs corresponding operations based on the judgment result instructing not to pre-execute traffic influence.

[0823] For example, based on a judgment result instructing not to perform traffic influence in advance, the application client sends instruction information for performing traffic influence in advance to the EEC, instructing to perform traffic influence in advance for the application client.

[0824] For example, when an application client receives a determination result indicating not to perform traffic influence in advance and information regarding one or more EASs or information regarding a selected EAS, the application client may request the selected EAS to perform traffic influence in advance.

[0825] FIG. 14 is a diagram of yet another method for requesting application capabilities according to an embodiment of the present application.

[0826] In this embodiment of the present application, the EEC determines, based on application information, not to perform EAS discovery proactively and / or not to perform traffic influence proactively.

[0827] S1301: The EEC determines whether to perform EAS discovery in advance and / or whether to perform traffic influence in advance.

[0828] The content of determining whether the EEC performs EAS discovery in advance and / or traffic influence in advance in S1301 is similar to the content of S501 in Fig. 6. For details, please refer to S501. The details will not be described again in this specification.

[0829] S1302: Optionally, the EEC stores a determination result instructing not to perform EAS discovery in advance and / or not to perform traffic influence in advance.

[0830] If the EEC determines not to pre-perform EAS discovery based on the application information, the EEC may store a determination result indicating not to pre-perform EAS discovery, and the determination result may be used by the EEC to determine whether to pre-perform EAS discovery and / or whether to pre-perform traffic influence for the same application client (target application client) at a later time.

[0831] S1303: Optionally, the EEC sends instruction information to the application client.

[0832] The instruction information may indicate not to perform EAS discovery in advance, and the instruction information may include a judgment result indicating not to perform EAS discovery in advance. The target application client performs a corresponding operation according to the judgment result indicating not to perform EAS discovery in advance.

[0833] Optionally, when the application client requests and / or subscribes to a determination result from the EEC, the application client sends instruction information to the application client after determining the determination result instructing not to perform EAS discovery in advance.

[0834] For example, the target application client sends instruction information to the EEC to pre-perform EAS discovery and / or pre-perform traffic influence based on the judgment result instructing not to pre-perform EAS discovery. It should be understood that Fig. 2 to Fig. 14 are some embodiments provided in the present application. Those skilled in the art can further obtain new embodiments by combining steps across various embodiments or adjusting the execution order of steps. For example, S605 in Fig. 7 may be combined with S903 in Fig. 12, S601 or S602 may be performed after S603 in Fig. 7, and S608 may be performed before S607 in Fig. 7. For the sake of brevity, the present application does not enumerate the embodiments obtained in the above manner. It should be understood that this part of the embodiment should also fall within the protection scope of the present application.

[0835] Based on the same inventive concept as the aforementioned method embodiment, an embodiment of the present application further provides a communication device. The communication device may have the functions of the enabler server, the enabler client, and the application client in the aforementioned method embodiment, and may be configured to execute steps performed using the functions of the enabler server, the enabler client, or the application client in the aforementioned method embodiment. The functions may be implemented by hardware, or by software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0836] In one possible implementation, the communication device 1500 shown in FIG. 15 may function as an enabler server in the above-described method embodiments and perform the steps performed by the enabler server in the above-described method embodiments.

[0837] 15, the communications device 1500 may include a transceiver unit 1510 and a processing unit 1520. The transceiver unit 1510 and the processing unit 1520 are coupled to each other.

[0838] The transceiver unit 1510 may be configured to support the communication device 1100 in performing communications, for example, transmitting and / or receiving operations such as S101, S103, S301, S504, S602, S604, S702, S705, S806, S908, and S1005 performed by the enabler server in Figures 2, 4, 6, 7, 8, 9, 10, and 11.

[0839] The processing unit 1520 may be configured to support the communication device 1500 in performing processing operations in the aforementioned method embodiments, such as processing operations S102, S505, S605, S606, S703, S704, and S807 performed by the enabler server in Figures 2, 6, 7, 8, and 9.

[0840] In another possible implementation, the communication device 1500 shown in FIG. 15 may function as an enabler client in the above-described method embodiments and perform the steps performed by the enabler client in the above-described method embodiments.

[0841] 15, the communications device 1500 may include a transceiver unit 1510 and a processing unit 1520. The transceiver unit 1510 and the processing unit 1520 are coupled to each other.

[0842] The transceiver unit 1510 may be configured to support the communications device 1500 in performing communications, such as, for example, transmitting and / or receiving operations such as S101, S103, S201, S203, S502, S504, S804, S807, S702, S705, S804, S806, S809, S810, S904, S905, S1004, S1005, S1008, S1010, S1104, S1106, S1109, and S1110 performed by the enabler client in Figures 2, 3, 6, 7, 8, 9, 10, 11, and 12.

[0843] The processing unit 1520 may be configured to support the communication device 1500 in performing processing operations in the aforementioned method embodiments, such as, for example, processing operations S503, S603, S701, S805, S903, and S1003 performed by the enabler client in Figures 6, 7, 8, 9, 10, and 11.

[0844] In yet another possible implementation, the communications device 1500 shown in FIG. 15 may function as an application client in the above-described method embodiments and perform the steps performed by the application client in the above-described method embodiments.

[0845] 15, the communications device 1500 may include a transceiver unit 1510 and a processing unit 1520. The transceiver unit 1510 and the processing unit 1520 are coupled to each other.

[0846] The transceiver unit 1510 may be configured to support the communications device 1500 in performing communications, such as transmitting and / or receiving operations such as S501, S804, S810, S1006, S1103, and S1303 performed by the application client in Figures 6, 9, 11, 12, and 14.

[0847] The processing unit 1520 may be configured to support the communications device 1500 in performing processing operations in the aforementioned method embodiments, such as processing operations S501, S803, S811, S1007, and S1103 performed by the application client in Figures 6, 9, 11, and 12.

[0848] In yet another possible implementation, the communication device 1500 shown in FIG. 15 may function as an application server in the above-described method embodiments and perform the steps performed by the application server in the above-described method embodiments.

[0849] 15, the communications device 1500 may include a transceiver unit 1510 and a processing unit 1520. The transceiver unit 1510 and the processing unit 1520 are coupled to each other.

[0850] The transceiver unit 1510 may be configured to support the communications device 1500 in performing communications, e.g., transmitting and / or receiving operations such as S401, S402, S601, S602, S801, S802, S812, S901, S901, and S1010 performed by the application server in Figures 5, 7, 9, 10, and 11.

[0851] The processing unit 1520 may be configured to support the communication device 1500 in performing processing operations in the above-described method embodiments, such as processing operations S813 and S1009 performed by the application server in Figures 9 and 11.

[0852] In yet another possible implementation, the communication device 1500 shown in FIG. 15 may function as an edge configuration server in the above-described method embodiment and perform the steps performed by the application server in the above-described method embodiment.

[0853] 15, the communications device 1500 may include a transceiver unit 1510 and a processing unit 1520. The transceiver unit 1510 and the processing unit 1520 are coupled to each other.

[0854] The transceiver unit 1510 may be configured to support the communication device 1500 in performing communications, e.g., transmitting and / or receiving operations such as S201, S203, S1101, S1102, S1106, and S1109 performed by the edge configuration server in Figures 3 and 12.

[0855] The processing unit 1520 may be configured to support the communication device 1500 in performing processing operations in the above-described method embodiments, such as processing operations S202, S1107, and S1108 performed by the edge configuration server in FIGS. 3 and 12.

[0856] Optionally, communications device 1500 may further include a memory unit 1530 configured to store program codes and data for communications device 1500 .

[0857] 16 is a schematic block diagram of a communication device 1600 according to one embodiment of the present application. As shown in this figure, the communication device 1600 includes at least one processor 1610 and a transceiver 1620. The processor 1610 is coupled to a memory and configured to execute instructions stored in the memory to control the transceiver 1620 to transmit signals and / or receive signals.

[0858] Optionally, the communications device 1600 further includes a memory 1630 configured to store instructions.

[0859] In some embodiments, the processor 1610 and the memory 1630 may be integrated into a processing unit. The processor 1610 is configured to execute program code stored in the memory 1630 to implement the functions described above. In a specific implementation, the memory 1630 may alternatively be integrated into the processor 1610 or may be separate from the processor 1610.

[0860] In some embodiments, the transceiver 1620 may include a receiver and a transmitter.

[0861] The transceiver 1620 may further include an antenna, of which there may be one or more. The transceiver 1620 may be a communications interface or interface circuit.

[0862] When the communication device 1600 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit may be an input / output circuit or a communication interface. The processing unit may be a processor, a microprocessor, or an integrated circuit integrated on a chip.

[0863] In the course of implementation, the steps of the aforementioned method may be completed by using integrated logic circuits of hardware in a processor, or by using instructions in the form of software. The steps of the method disclosed with reference to the embodiments of the present application may be directly executed and completed by a hardware processor, or may be executed and completed using a combination of hardware and software modules in a processor. The software modules may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the aforementioned method in cooperation with the hardware in the processor. To avoid repetition, details will not be described again in this specification.

[0864] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions for implementing a method performed by a communication device in the aforementioned method embodiments.

[0865] For example, the computer program, when executed by a computer, enables the computer to implement the methods performed by the communications device in the method embodiments described above.

[0866] For the description of the relevant contents and beneficial effects of any one of the devices provided above, please refer to the corresponding method embodiments provided above, and the details will not be described again in this specification.

[0867] Those skilled in the art can see that the present application can be implemented by electronic hardware or by a combination of computer software and electronic hardware with reference to the units and algorithm steps in the examples described in the embodiments disclosed herein. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can implement the described functions using various methods for each specific application, but the implementation should not be considered to go beyond the scope of the present application.

[0868] It will be clearly understood by those skilled in the art that for the sake of convenience, the detailed operation steps of the aforementioned systems, devices and units should be referred to the corresponding processes of the aforementioned method embodiments, and the details will not be described again in this specification.

[0869] In some embodiments provided in the present application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the above-mentioned device embodiment is only an example. For example, the division into units is only a logical division of functions, and may be divided differently in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some functions may be ignored or not performed. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.

[0870] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one place or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

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

[0872] When functions are implemented in the form of software functional units and sold or used as independent products, the functions may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application, essentially, the part that contributes to the prior art, or part of the technical solutions, may be implemented in the form of a software product. The computer software product includes some instructions stored in a storage medium, instructing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the method in the embodiments of the present application. The aforementioned storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disk, etc.

[0873] The above description is merely a specific implementation of the present application, and the protection scope of the present application is not limited thereto. Any modifications or replacements that are easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims. [Explanation of symbols]

[0874] 1500 Communication Equipment 1510 Transceiver Unit 1520 Processing Unit 1530 Storage Unit 1600 Communication Devices 1610 Processor 1620 Transceiver 1630 Memory

Claims

1. 1. A method for requesting an application feature, comprising: determining, by the enabler server, whether to pre-execute traffic influence based on the first determination information; sending, by the enabler server, an application capability request message if it is determined that traffic influence is to be pre-performed, the application capability request message being for requesting to perform traffic influence for one or more application servers; A method comprising:

2. The method of claim 1 , wherein the first determination information includes application information, the application information including one or more of the following information: an application type, an application server type, or a delay requirement.

3. The method of claim 1 or 2, wherein the first determination information includes instruction information, the instruction information instructing to pre-perform application server discovery and / or to pre-perform traffic influence.

4. The method comprises: sending, by the enabler server, a discovery response message, the discovery response message indicating that traffic influence is being performed for the one or more application servers; 4. The method of claim 1, further comprising:

5. If it is determined to perform traffic influence proactively, the method further comprises: sending, by the enabler server, a first instruction message to a selected application server, the first instruction message instructing to pre-trigger the traffic influence, the one or more application servers including the selected application server; 5. The method of claim 1, further comprising:

6. The method of claim 2 , wherein the delay requirement comprises any one of a delay requirement of a first packet, a delay requirement of an application client, or a delay requirement of an application server required by the application client.

7. 7. The method of claim 1, wherein the step of performing traffic influence in advance comprises performing traffic influence before the application client is launched or performing traffic influence before the application client exchanges data with an application server.

8. 1. A method for requesting an application feature, comprising: determining, by the enabler client, whether to proactively perform traffic influence based on the second determination information; sending, by the enabler client, an application server discovery request message when it is determined to proactively perform traffic influence, the application server discovery request message being for requesting to discover one or more application servers, the one or more application servers being configured to provide application services to the application client; A method comprising:

9. The method of claim 8 , wherein the second determination information includes application information, the application information including one or more of the following information: an application type, an application server type, or a delay requirement.

10. The method of claim 8 or 9, wherein the second determination information includes instruction information, the instruction information instructing to proactively perform application server discovery and / or to proactively perform traffic influence.

11. The step of determining whether to proactively perform traffic influence includes: determining, by the enabler client, whether to pre-perform application server discovery; 11. The method according to any one of claims 8 to 10, comprising:

12. The method comprises: receiving, by the enabler client, a discovery response message sent by an enabler server, the discovery response message indicating that traffic influence is being performed for the one or more application servers; sending, by the enabler client, a first response message to the application client, the first response message including information about the one or more application servers, the first response message further indicating that traffic influence is being performed for the one or more application servers; 12. The method of any one of claims 8 to 11, further comprising:

13. 10. The method of claim 9, wherein the delay requirement comprises any one of a delay requirement of a first packet, a delay requirement of the application client, or a delay requirement of an application server required by the application client.

14. 14. The method of claim 8, wherein the step of performing traffic influence in advance comprises performing traffic influence before the application client is launched or performing traffic influence before the application client exchanges data with an application server.

15. 1. A method for requesting an application feature, comprising: determining, by an application client, whether to pre-perform application server discovery and / or whether to pre-perform traffic influence based on application information, wherein the application information includes one or more of the following information: application type, application server type, or delay requirement; sending, by the application client, a first request message to an enabler client when it is determined to pre-perform application server discovery and / or pre-perform traffic influence; A method comprising:

16. 16. The method of claim 15, wherein the first request message includes the application information and / or instruction information, and the instruction information instructs to pre-perform application server discovery and / or to pre-perform traffic influence.

17. The method comprises: receiving, by the application client, a first response message, the first response message including information regarding one or more application servers, the first response message further indicating that traffic influence is being performed for the one or more application servers; 17. The method of claim 15 or 16, further comprising:

18. If it is determined to proactively perform application server discovery and / or traffic influence, the method further comprises: sending, by the application client, a second instruction message to a selected application server, the second instruction message instructing to pre-trigger the traffic influence, the one or more application servers including the selected application server; 18. The method of any one of claims 15 to 17, further comprising:

19. 19. The method of claim 15, wherein the delay requirement comprises any one of a delay requirement of a first packet, a delay requirement of the application client, or a delay requirement of an application server required by the application client.

20. 20. The method of claim 15, wherein the step of performing traffic influence in advance comprises performing traffic influence before the application client is launched or performing traffic influence before the application client exchanges data with an application server.

21. A communication system comprising an enabler server, an enabler client and an application client, the enabler server being configured to perform a method according to any one of claims 1 to 7, the enabler client being configured to perform a method according to any one of claims 8 to 14 and the application client being configured to perform a method according to any one of claims 15 to 20.

22. A device for requesting an application functionality, comprising a unit for implementing the method according to any one of claims 1 to 7, claims 8 to 14 or claims 15 to 20.

23. A device that requests an application function, A processor configured to execute computer instructions stored in a memory to enable the device to carry out the method according to any one of claims 1 to 7. A device for requesting an application function comprising:

24. A device that requests an application function, A processor configured to execute computer instructions stored in a memory to enable the device to carry out the method according to any one of claims 8 to 14. A device for requesting an application function comprising:

25. A device that requests an application function, A processor configured to execute computer instructions stored in a memory to enable the device to carry out the method of any one of claims 15 to 20. A device for requesting an application function comprising:

26. A computer readable storage medium having a computer program stored thereon, the computer program being enabled to implement a method according to any one of claims 1 to 7, claims 8 to 14 or claims 15 to 20 when executed by a computer.

27. 21. A computer program product comprising computer program code which, when run on a computer, performs the method of any one of claims 1 to 7, claims 8 to 14 or claims 15 to 20.

28. A chip comprising a processor configured to read instructions stored in a memory, the instructions, when executed by the processor, enabling the chip to implement a method according to any one of claims 1 to 7, claims 8 to 14 or claims 15 to 20.

Images