Communication method and device

Abstract

The invention provides a communication method and device, belongs to the technical field of communication, and is used for discovering a manager of an EDI (Electronic Data Interchange) under the condition that an SMF (System Management Function) is unknown to the EDI. In the method, after a first network element receives a first request message, the first network element can request a second network element to inquire a local session management function network element corresponding to an edge application server identified by first information according to the first information in the first request message, or the second network element can inquire the local session management function network element corresponding to the edge application server identified by the first information. And managing a local session management function network element of the edge application server. Therefore, under the condition that the deployment information of the edge application server identified by the first information is not known by the first network element, a manager of the deployment information of the edge application server identified by the first information, namely a local session management function network element for managing the deployment information of the edge application server, can be found; communication between the terminal equipment and the edge application server is supported, and the communication efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and in particular to a communication method and device. BACKGROUND

[0002] Currently, the discovery process of an edge application server (EAS) can be as follows: a terminal device can initiate a domain name system (DNS) query to an edge application server discovery function (EASDF) network element, the EASDF can feed back a query result to a session management function (SMF) network element. The SMF can select and insert a protocol data unit (PDU) session anchor (PSA) according to the query result to support communication between the terminal device and the EAS. In this process, if the SMF is a central SMF, the central SMF can be connected to at least one local SMF (L-SMF) network element to support communication between the terminal device and the EAS. The central SMF can store EAS deployment information (EDI) of the region it governs, and when there is no certain PSA in the region governed by the central SMF, the L-SMF can be required to be connected to the PSA to support communication between the terminal device and the EAS. The SMF storing the local EDI can find the corresponding EAS to support communication between the terminal device and the EAS.

[0003] However, in the case that the SMF is not aware of a certain EDI, the manager of the EDI can not be discovered. SUMMARY

[0004] Embodiments of the present application provide a communication method and device to discover the manager of a certain EDI in the case that the SMF is not aware of the EDI.

[0005] To achieve the above object, the embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a communication method is provided. The method can be performed by a first network element, a module (e.g., a processor, a chip, or a chip system) applied to the first network element, or a logic node, a logic module, or software that can implement all or part of the function of the first network element. For convenience of description, the method is described below by taking the first network element as an example. The method includes: receiving, by the first network element, a first request message, and querying, by the first network element, a local session management function network element corresponding to an edge application server identified by first information from a second network element; and sending, by the first network element, information of the local session management function network element to a third network element, or sending, by the first network element, information of the edge application server to the local session management function network element according to a result of the querying. The first request message includes first information, second information, and third information. The first information is used to identify the edge application server, the second information is used to indicate a terminal device, and the third information is used to indicate related information of a service between the terminal device and the edge application server.

[0007] According to the method of the first aspect, after the first network element receives the first request message, the first network element can request the second network element to query the local session management function network element corresponding to the edge application server identified by the first information according to the first information in the first request message, or the local session management function network element managing the edge application server. The first network element can send the information of the queried local session management function network element to the third network element, so that the third network element can determine the local session management function network element corresponding to the edge application server. Alternatively, the first network element can directly send the information of the edge application server to the queried local session management function network element, so that the local session management function network element can find the edge application server corresponding to the service. In this way, the deployment information of the edge application server identified by the first information can be discovered in a case where the first network element is not aware of the deployment information of the edge application server identified by the first information, or the deployment information of the edge application server identified by the first information is missing. The manager of the deployment information of the edge application server identified by the first information is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, so as to support the communication between the terminal device and the edge application server and improve the communication efficiency.

[0008] In a possible design, the first request message is used to request to perform the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server, and the third information is used to indicate the related information of the service between the terminal device and the edge application server, including: the third information is used to indicate the related information of the service between the terminal device and the source edge application server. For example, the location of the terminal device moves, and the like, the first request message can be used to request to switch the service from the source edge application server to the target edge application server, or to offload part of the traffic of the service from the source edge application server to the target edge application server to meet the demand of the service.

[0009] In a possible design, the first request message is used to request to perform the re-discovery of the edge application server. That is, the first request message can request to re-discover a new edge application server to provide better service for the service.

[0010] In a possible design, the first network element queries, from the second network element, a local session management function network element corresponding to the edge application server identified by the first information, including: the first network element sends, to the second network element, a second request message, and receives, from the second network element, information of the local session management function network element. The second request message is used to request to query the local session management function network element corresponding to the edge application server identified by the first information. That is, the first network element can trigger the second network element to query the local session management function network element corresponding to the edge application server by sending the second request message to the second network element, so that the on-demand query is implemented, and flexibility is achieved.

[0011] In a possible design, the second network element is configured to store a correspondence between a local session management function network element and an edge application server, and the edge application server includes an edge application server identified by the first information. That is, the second network element stores the deployment information of the edge application server identified by the first information, and the second network element can query, by itself, the local session management function network element corresponding to the edge application server identified by the first information, and simplicity is achieved.

[0012] In a possible design, the second network element is configured to query, from a data storage network element, a local session management function network element corresponding to an edge application server identified by the first information. That is, the second network element does not store the deployment information of the edge application server identified by the first information, and the second network element needs to query, through the data storage network element, to obtain the local session management function network element corresponding to the edge application server identified by the first information. In combination with the above description, the second network element queries by itself or through the data storage network element to meet the demand of different scenarios.

[0013] In a possible design, the first network element sends information of the local session management function network element to the third network element, including: the first network element sends a first message to the third network element. The first message includes the information of the local session management function network element, first information, second information, and third information.

[0014] Optionally, the first network element is a policy control function network element or any other possible network function / entity, which is not limited. The second network element is at least one of an edge application server discovery function network element, a network exposure function network element, or a network repository function network element, or can also be any other possible network function / entity, which is not limited. The third network element is a session management function network element of a terminal device or any other possible network function / entity, which is not limited. In this way, the needs of different scenarios can be met. It can be understood that the session management function network element can be understood as a central session management function network element (the specific function can refer to the function of a session management function (SMF) network element, and the function of session management is implemented), which is deployed in the network center. When the terminal needs to establish an edge application service, the central session management function network element is responsible for selecting and inserting a suitable local session management function network element to support the edge application service of the terminal. For example, the session management function network element can establish a connection with the determined local session management function network element.

[0015] That is, the policy control function network element can send the information of the local session management function network element, the first information, the second information, and the third information obtained through the edge application server discovery function network element, the network exposure function network element, or the network repository function network element to the session management function network element of the terminal device. In this way, the session management function network element of the terminal device can obtain the local session management function network element for managing the edge application server without storing the deployment information of the edge application server identified by the first information, to support the communication between the terminal device and the edge application server. Subsequently, the session management function network element instructs the queried local session management function network element to perform subsequent steps, which are not limited.

[0016] In a possible design, the first network element sends information of the edge application server to the local session management function network element, including: the first network element sends a second message to the local session management function network element. The second message includes the information of the edge application server, the second information, and the third information.

[0017] Optionally, the first network element is a session management function network element of the terminal device, or any other possible network function / entity, without limitation. The second network element is at least one of an edge application server discovery function network element, a network exposure function network element, a network repository function network element, or any other possible network function / entity, without limitation. In this way, the needs of different scenarios can be met.

[0018] That is, the session management function network element can query the local session management function network element through the edge application server discovery function network element, the network exposure function network element, or the network repository function network element, in the absence of the deployment information of the edge application server identified by the first information. In this way, the local session management function network element for managing the edge application server identified by the first information can be discovered to support communication between the terminal device and the edge application server. Meanwhile, the session management function network element can send the information of the edge application server, the second information, and the third information to the queried local session management function network element to trigger the local session management function network element to perform subsequent steps, without limitation.

[0019] Optionally, the first network element is a policy control function network element, or any other possible network function / entity, without limitation. The second network element is at least one of an edge application server discovery function network element, a network exposure function network element, a network repository function network element, or any other possible network function / entity, without limitation.

[0020] At this time, the policy control function network element can send the information of the edge application server, the second information, and the third information to the local session management function network element queried through the edge application server discovery function network element, the network exposure function network element, or the network repository function network element to trigger the local session management function network element to perform subsequent steps. In this way, the policy control function network element does not need to send the information of the local session management function network element queried to the session management function network element of the terminal device, but can directly send the information of the edge application server, the second information, and the third information to the local session management function network element queried, thereby reducing the overhead and improving the communication efficiency.

[0021] In a possible design, the local session management function network element is configured to determine a local protocol data unit session anchor point, which is on a transmission path of traffic between the terminal device and the edge application server. It can be understood that the purpose of querying the local session management function network element is to access the local protocol data unit session anchor point by the local session management function network element to perform subsequent steps, such as switching the local protocol data unit session anchor point, adding the local protocol data unit session anchor point, and the like, to meet the needs of traffic between the terminal device and the edge application server.

[0022] In a second aspect, a communication method is provided. The method can be performed by a second network element, a module (e.g., a processor, a chip, or a chip system) applied to the second network element, or a logic node, a logic module, or software that can implement all or part of the function of the second network element. For convenience of description, the method is described below by taking the second network element as an example. The method includes: receiving, by the second network element, a second request message from a first network element, and sending, by the second network element, information of a local session management function network element to the first network element according to the second request message. The second request message is used to request to query the local session management function network element corresponding to an edge application server identified by the first information.

[0023] In a possible design, the second network element is configured to store a correspondence between the local session management function network element and the edge application server, and the edge application server includes an edge application server identified by the first information.

[0024] In a possible design, the method of the second aspect further includes: sending, by the second network element, a third request message to a data storage network element, and receiving, by the second network element, the information of the local session management function network element from the data storage network element. The third request message is used to request to query the local session management function network element corresponding to the edge application server identified by the first information. That is, the second network element can send the third request message to the data storage network element to trigger the data storage network element to query the local session management function network element corresponding to the edge application server, so that the data storage network element can implement on-demand query.

[0025] In a possible design, the first network element is a session management function network element of a terminal device or a policy control function network element. The second network element is at least one of the following: an edge application server discovery function network element, a network exposure function network element, or a network storage function network element. It can be understood that the first network element is different from the session management function network element.

[0026] In addition, other technical effects of the method of the second aspect can refer to the technical effects of the method of the first aspect, which are not described herein again.

[0027] In a third aspect, a communication method is provided. The method can be performed by a first network element, a module (e.g., a processor, a chip, or a chip system) applied to the first network element, or a logic node, a logic module, or software that can implement all or part of the function of the first network element. For the convenience of description, the method performed by the first network element is taken as an example for description. The method includes: receiving, by the first network element, a first message from a session management function network element, querying, according to a stored correspondence between a local session management function network element and an edge application server, a local session management function network element corresponding to an edge application server identified by first information, and sending, by the first network element, a first request message to the local session management function network element. The first message includes the first request message and the first information, the first information is used to identify the edge application server, the first request message includes the first information, second information, and third information, the second information is used to indicate a terminal device, and the third information is used to indicate related information of a service between the terminal device and the edge application server.

[0028] According to the method of the third aspect, after the first network element receives the first information in the first message sent by the session management function network element, the first network element can directly determine the local session management function network element corresponding to the edge application server identified by the first information according to the stored correspondence between the local session management function network element and the edge application server, without the need to parse the first request message. The first network element can directly forward the first request message to the determined local session management function network element, so that the local session management function network element performs subsequent steps according to the first request message. In this way, in the case that the session management function network element is not aware of the deployment information of the edge application server identified by the first information, or in the case that the deployment information of the edge application server identified by the first information is missing, the first network element can discover the manager of the deployment information of the edge application server identified by the first information, which is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, to support the communication between the terminal device and the edge application server and improve the communication efficiency.

[0029] In a possible design, the first request message is used to request to perform the redeployment of the edge application server, and the edge application server includes a source edge application server and a target edge application server. The third information is used to indicate the related information of the service between the terminal device and the edge application server, and includes: the third information is used to indicate the related information of the service between the terminal device and the source edge application server.

[0030] In a possible design, the first request message is used to request to perform the rediscov ery of the edge application server.

[0031] In one possible design, the first network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element, or it can be any other possible network function / entity without limitation. This can meet the needs of different scenarios.

[0032] Furthermore, other technical effects of the method described in the third aspect can be referred to the technical effects of the method described in the first aspect, and will not be repeated here.

[0033] Fourthly, a communication method is provided. This method can be executed by a session management function network element, by a module (e.g., processor, chip, or chip system) applied to the session management function network element, or by a logical node, logical module, or software capable of implementing all or part of the session management function network element's functions. For ease of description, the following description uses the execution of the method by a session management function network element as an example. The method includes: the session management function network element obtaining a first request message and sending a first message to the first network element. The first request message includes first information, second information, and third information; the first information is used to identify the edge application server, the second information is used to indicate the terminal device, and the third information is used to indicate relevant information about the service between the terminal device and the edge application server; the first message includes the first request message and the first information.

[0034] Based on the method described in the fourth aspect, the session management function network element can obtain the first information according to the first request message, and send the first request message and the first information to the first network element through the first message. Subsequently, the first network element can directly determine the edge application server to be queried based on the first information without parsing the first request message. In this way, the processing difficulty can be reduced and the overhead can be reduced.

[0035] In one possible design, the first request message is used to request the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server. The third information is used to indicate relevant information about the business between the terminal device and the edge application server, including: the third information indicating relevant information about the business between the terminal device and the source edge application server.

[0036] In one possible design, the first request message is used to request the rediscovery of the edge application server.

[0037] In one possible design, the first network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0038] Furthermore, other technical effects of the method described in the fourth aspect can be referred to the technical effects of the method described in the third aspect, and will not be repeated here.

[0039] Fifthly, a communication method is provided. This method can be executed by a first network element, by a module applied to the first network element (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the functions of the first network element. For ease of description, the following description assumes that the method is executed by the first network element. The method includes: the first network element obtaining a first request message and determining a first local session management function network element corresponding to the source edge application server and a second local session management function network element corresponding to the target edge application server. The first request message includes first information, second information, and third information; the first information identifies the source edge application server and the target edge application server associated with the terminal device; the second information indicates the terminal device; the third information indicates relevant information about the service between the terminal device and the source edge application server; the first local session management function network element is determined by the session management function network element based on the stored correspondence between local session management function network elements and edge application servers; the second local session management function network element is queried by the session management function network element through the first local session management function network element.

[0040] As described in the fifth aspect, the first network element stores the correspondence between local session management function network elements and source edge application servers, but not the correspondence between local session management function network elements and target edge application servers. That is, the first network element stores the deployment information of the source edge application server, but not the deployment information of the target edge application server. In this case, the first network element can query the second local session management function network element corresponding to the target edge application server through the first local session management function network element corresponding to the source edge application server. Thus, even when the first network element is unaware of the deployment information of the target edge application server, or in other words, when the deployment information of the target edge application server is missing, the first network element can discover the manager of the deployment information of the target edge application server. This manager is a local session management function network element that can manage or store the deployment information of the target edge application server, thereby supporting communication between terminal devices, source edge application servers, and target edge application servers, and improving communication efficiency.

[0041] In one possible design, the method described in the fifth aspect further includes: the first network element determines the first local session management function network element based on the stored information, and does not store information about the local session management function network element corresponding to the target edge application server.

[0042] Optionally, after the first network element determines the first local session management function network element based on the stored information, and no information about the local session management function network element corresponding to the target edge application server is stored, the method in the fifth aspect further includes: the first network element sending a second request message to the first local session management function network element and receiving a second response message from the first local session management function network element. The second request message is used to request a query for the local session management function network element corresponding to the target edge application server; the second response message includes information about the second local session management function network element.

[0043] That is, the first network element can determine the first local session management function network element corresponding to the source edge application server based on the stored information. If the local session management function network element corresponding to the target edge application server is not found, the first network element can send a second request message to the first local session management function network element to trigger the first local session management function network element to query the local session management function network element corresponding to the target edge application server. In this way, querying can be realized and flexibility can be achieved.

[0044] In one possible design, a first local session management function network element stores information about one or more edge application servers corresponding to the first local session management function network element. These edge application servers include a target edge application server. The first local session management function network element is identified as a second local session management function network element corresponding to the target edge application server. That is, when the first local session management function network element stores deployment information about the target edge application server, the first and second local session management function network elements are the same. Thus, the first local session management function network element can directly determine the second local session management function network element based on the stored information, without needing to query other network elements, simplifying the process.

[0045] Optionally, the first request message is used to request the first network element to redeploy the edge application server. The method described in the fifth aspect further includes: the first network element sending indication information to the first local session management function network element according to the first request message. The indication information is used to instruct the first local session management function network element to modify the local protocol data unit session anchor point, where the modified local protocol data unit session anchor point is on the service transmission path between the terminal device and the target edge application server. That is, when the first local session management function network element and the second local session management function network element are the same local session management function network element, the first network element can directly send indication information to the first local session management function network element to instruct it to insert a new local protocol data unit session anchor point, switch from the source local protocol data unit session anchor point to the target local protocol data unit session anchor point, etc., to meet service requirements.

[0046] In one possible design, a first local session management function network element stores information about one or more edge application servers corresponding to the first local session management function network element, where the one or more edge application servers do not include the target edge application server. The first network element receives a second response message from the first local session management function network element, including: the first network element receiving a second response message from a second network element through the first local session management function network element. The first local session management function network element and the second local session management function network element are different. Optionally, the second local session management function network element is determined by the second network element. That is, the first local session management function network element does not manage the target edge application server; in this case, the first local session management function network element needs to query the second network element to obtain the second local session management function network element, thus achieving flexibility.

[0047] In one possible design, the second network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element; or it can be any other possible network function / entity without limitation. This can meet the needs of different scenarios.

[0048] In one possible design, the first request message is used to request the first network element to redeploy the edge application server. The method described in the fifth aspect further includes: the first network element sending indication information to the second local session management function network element according to the first request message. The indication information is used to instruct the second local session management function network element to modify the local protocol data unit session anchor point, where the modified local protocol data unit session anchor point is on the service transmission path between the terminal device and the target edge application server. That is, when the first and second local session management function network elements are the same local session management function network element, the first network element can send indication information to the second local session management function network element to instruct it to insert a new local protocol data unit session anchor point, switch from the source local protocol data unit session anchor point to the target local protocol data unit session anchor point, etc., to meet service requirements.

[0049] In one possible design, the method described in the fifth aspect further includes: the first network element updating the deployment information of the stored application server. The updated deployment information includes the correspondence between the second local session management function network element and the target edge application server. Thus, if the first network element subsequently needs to discover or query the local session management function network element that manages the target edge application server, it can directly determine the second local session management function network element based on the stored information, without needing to query through other network elements, simplifying the process.

[0050] In one possible design, the first network element can be a session management function network element, or any other possible network function / entity, without limitation. This allows the first network element to discover the second local session management function network element that manages the target edge application server, even when the session management function network element does not store deployment information of the target edge application server. This enables communication between the terminal device and the target edge application server, improving communication efficiency.

[0051] Furthermore, other technical effects of the method described in the fifth aspect can be referred to the technical effects of the method described in the first aspect, and will not be repeated here.

[0052] A sixth aspect provides a communication device. The communication device includes modules for performing the method described in the first aspect. For example, a transceiver module and a processing module. The transceiver module performs the transceiver functions of the communication device, and the processing module performs functions of the communication device other than the transceiver functions.

[0053] The transceiver module is used to receive a first request message and query a second network element for the local session management function network element corresponding to the edge application server identified by the first information. The processing module is used to send information about the local session management function network element to a third network element, or send information about the edge application server to the local session management function network element, based on the query result. The first request message includes first information, second information, and third information; the first information identifies the edge application server, the second information indicates the terminal device, and the third information indicates relevant information about the service between the terminal device and the edge application server.

[0054] In one possible design, the first request message is used to request the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server, and the third information is used to indicate relevant information about the business between the terminal device and the edge application server, including: the third information is used to indicate relevant information about the business between the terminal device and the source edge application server.

[0055] In one possible design, the first request message is used to request the rediscovery of the edge application server.

[0056] In one possible design, the transceiver module is further configured to send a second request message to the second network element and receive information from the local session management function network element of the second network element. The second request message is used to request a query of the local session management function network element corresponding to the edge application server identified by the first information identifier.

[0057] In one possible design, the second network element is used to store the correspondence between the local session management function network element and the edge application server, and the edge application server includes the edge application server identified by the first information identifier.

[0058] In one possible design, the second network element is used to query the data storage network element for the local session management function network element corresponding to the edge application server with the first information identifier.

[0059] In one possible design, the transceiver module is also used to send a first message to a third network element. This first message includes information about the local session management function network element, first information, second information, and third information.

[0060] Optionally, the communication device described in the sixth aspect is a policy control function network element. The second network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element. The third network element is a session management function network element of the terminal device.

[0061] In one possible design, the transceiver module is also used to send a second message to the local session management function network element. This second message includes information about the edge application server, second information, and third information.

[0062] Optionally, the communication device described in the sixth aspect is a session management function network element of a terminal device. The second network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0063] Optionally, the first network element is a policy control function network element. The second network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0064] In one possible design, the local session management function network element is used to determine the local protocol data unit session anchor point, which is located on the service transmission path between the terminal device and the edge application server.

[0065] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in the sixth aspect, and the receiving module implements the receiving function of the communication device described in the sixth aspect.

[0066] Optionally, the communication device described in the sixth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the first aspect.

[0067] It is understood that the communication device described in the sixth aspect may be a first network element, or a chip (system) or other component or assembly that can be disposed in the first network element, or a device that includes the first network element. This application does not limit this.

[0068] Furthermore, the technical effects of the communication device described in the sixth aspect can be referred to the technical effects of the method described in the first aspect, and will not be repeated here.

[0069] A seventh aspect provides a communication device. The communication device includes: a module for performing the method described in the second aspect, for example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0070] The transceiver module is used to receive a second request message from the first network element. The processing module is used to send information about the local session management function network element to the first network element based on the second request message. The second request message is used to request a query of the local session management function network element corresponding to the edge application server identified by the first information identifier.

[0071] In one possible design, the communication device described in the seventh aspect is used to store the correspondence between local session management function network elements and edge application servers, wherein the edge application server includes an edge application server with a first information identifier.

[0072] In one possible design, the transceiver module is further configured to send a third request message to the data storage network element and receive information from the local session management function network element of the data storage network element. The third request message is used to request a query of the local session management function network element corresponding to the edge application server identified by the first information identifier.

[0073] In one possible design, the first network element is a session management function network element or a policy control function network element of the terminal device. The communication device described in the seventh aspect is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0074] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the seventh aspect, and the receiving module implements the receiving function of the communication device described in the seventh aspect.

[0075] Optionally, the communication device described in the seventh aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the second aspect.

[0076] It is understood that the communication device described in the seventh aspect can be a second network element, or a chip (system) or other component or assembly that can be disposed in the second network element, or a device that includes the second network element. This application does not limit this.

[0077] Furthermore, the technical effects of the communication device described in the seventh aspect can be referred to the technical effects of the method described in the second aspect, and will not be repeated here.

[0078] Eighthly, a communication device is provided. The communication device includes: a module for performing the method described in the third aspect, for example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0079] The transceiver module is used to receive a first message from the session management function network element. The processing module is used to query the local session management function network element corresponding to the edge application server identified by the first information, based on the stored correspondence between local session management function network elements and edge application servers. The transceiver module is also used to send a first request message to the local session management function network element. The first message includes a first request message and first information, where the first information identifies the edge application server; the first request message includes first information, second information, and third information, where the second information instructs the terminal device, and the third information instructs the terminal device on relevant business information between the terminal device and the edge application server.

[0080] In one possible design, the first request message is used to request the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server. The third information is used to indicate relevant information about the business between the terminal device and the edge application server, including: the third information indicating relevant information about the business between the terminal device and the source edge application server.

[0081] In one possible design, the first request message is used to request the rediscovery of the edge application server.

[0082] In one possible design, the communication device described in the eighth aspect is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0083] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the eighth aspect, and the receiving module implements the receiving function of the communication device described in the eighth aspect.

[0084] Optionally, the communication device described in the eighth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the third aspect.

[0085] It is understood that the communication device described in the eighth aspect may be a first network element, or a chip (system) or other component or assembly that can be disposed in the first network element, or a device that includes the first network element. This application does not limit this.

[0086] Furthermore, the technical effects of the communication device described in the eighth aspect can be referred to the technical effects of the method described in the third aspect, and will not be repeated here.

[0087] A ninth aspect provides a communication device. The communication device includes: a module for performing the method described in the fourth aspect, for example, a transceiver module and a processing module. The transceiver module is used to perform the transceiver functions of the communication device, and the processing module is used to perform functions of the communication device other than the transceiver functions.

[0088] The processing module is used to acquire the first request message. The transceiver module is used to send the first message to the first network element. The first request message includes first information, second information, and third information; the first information is used to identify the edge application server, the second information is used to indicate the terminal device, and the third information is used to indicate the relevant information of the service between the terminal device and the edge application server; the first message includes the first request message and the first information.

[0089] In one possible design, the first request message is used to request the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server. The third information is used to indicate relevant information about the business between the terminal device and the edge application server, including: the third information indicating relevant information about the business between the terminal device and the source edge application server.

[0090] In one possible design, the first request message is used to request the rediscovery of the edge application server.

[0091] In one possible design, the first network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0092] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the ninth aspect, and the receiving module implements the receiving function of the communication device described in the ninth aspect.

[0093] Optionally, the communication device described in the ninth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fourth aspect.

[0094] It is understood that the communication device described in the ninth aspect may be a session management function network element, or a chip (system) or other component or assembly that can be set in the session management function network element, or a device that includes a session management function network element. This application does not limit this.

[0095] Furthermore, the technical effects of the communication device described in the ninth aspect can be referred to the technical effects of the method described in the fourth aspect, and will not be repeated here.

[0096] A tenth aspect provides a communication device. The communication device includes: a module for performing the method described in the fifth aspect, such as a transceiver module and a processing module. The transceiver module performs the transceiver function of the communication device, and the processing module performs functions of the communication device other than the transceiver function.

[0097] The processing module is used to acquire a first request message and determine a first local session management function network element corresponding to the source edge application server and a second local session management function network element corresponding to the target edge application server. The first request message includes first information, second information, and third information; the first information identifies the source and target edge application servers associated with the terminal device; the second information indicates the terminal device; and the third information indicates relevant information about the service between the terminal device and the source edge application server. The first local session management function network element is determined by the session management function network element based on the stored correspondence between local session management function network elements and edge application servers, and the second local session management function network element is queried by the session management function network element through the first local session management function network element.

[0098] In one possible design, the processing module is further configured to determine the first local session management function network element based on the stored information, and not to store information about the local session management function network element corresponding to the target edge application server.

[0099] Optionally, after the communication device described in the tenth aspect determines the first local session management function network element based on stored information, and does not store information about the local session management function network element corresponding to the target edge application server, the transceiver module is further configured to send a second request message to the first local session management function network element and receive a second response message from the first local session management function network element. The second request message is used to request a query of the local session management function network element corresponding to the target edge application server; the second response message includes information about the second local session management function network element.

[0100] In one possible design, the first local session management function network element is used to store information of one or more edge application servers corresponding to the first local session management function network element, the one or more edge application servers including the target edge application server, and the first local session management function network element is determined to be the second local session management function network element corresponding to the target edge application server.

[0101] Optionally, the first request message is used to request the communication device described in the tenth aspect to perform a redeployment of the edge application server. The transceiver module is further configured to send indication information to the first local session management function network element according to the first request message. The indication information is used to instruct the first local session management function network element to modify the local protocol data unit session anchor point, wherein the modified local protocol data unit session anchor point is on the transmission path of the service between the terminal device and the target edge application server.

[0102] In one possible design, the first local session management function network element is used to store information about one or more edge application servers corresponding to the first local session management function network element, wherein the one or more edge application servers do not include the target edge application server. The transceiver module is also used to receive a second response message from a second network element through the first local session management function network element. The first local session management function network element and the second local session management function network element are different.

[0103] Optionally, the second local session management function network element is determined by the second network element.

[0104] In one possible design, the second network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element.

[0105] In one possible design, the first request message is used to request the communication device described in the tenth aspect to perform a redeployment of the edge application server. The transceiver module is used to send indication information to the second local session management function network element according to the first request message. The indication information is used to instruct the second local session management function network element to modify the local protocol data unit session anchor point, and the modified local protocol data unit session anchor point is on the service transmission path between the terminal device and the target edge application server.

[0106] In one possible design, the processing module is also used to update the deployment information of the stored application server. The updated deployment information includes the mapping between the second local session management function network element and the target edge application server.

[0107] In one possible design, the communication device described in aspect ten is a session management function network element.

[0108] Optionally, the transceiver module may include a transmitting module and a receiving module. The transmitting module implements the transmitting function of the communication device described in the tenth aspect, and the receiving module implements the receiving function of the communication device described in the tenth aspect.

[0109] Optionally, the communication device according to the tenth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the method described in the fifth aspect.

[0110] It is understood that the communication device described in the tenth aspect may be a first network element, or a chip (system) or other component or assembly that can be disposed in the first network element, or a device that includes the first network element. This application does not limit this.

[0111] Furthermore, the technical effects of the communication device described in the tenth aspect can be referred to the technical effects of the method described in the fifth aspect, and will not be repeated here.

[0112] Eleventhly, a communication device is provided, comprising: a processor; the processor being coupled to a memory for storing a computer program, wherein when the processor executes the computer program, the communication device is configured to perform the method described in any one of the first to fifth aspects.

[0113] In one possible design, the communication device described in the eleventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eleventh aspect and other communication devices.

[0114] In the embodiments of this application, the communication device described in the eleventh aspect can be a first network element as described in any of the implementations of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in the eleventh aspect can be a second network element as described in the second aspect, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in the eleventh aspect can be a session management function network element as described in the fourth aspect, or a chip (system) or other component or assembly disposed in the session management function network element, or a device containing the session management function network element.

[0115] Furthermore, the technical effects of the communication device described in the eleventh aspect can be referred to the technical effects of the method described in any of the implementations of the first to fifth aspects, and will not be repeated here.

[0116] In a twelfth aspect, a communication device is provided. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program stored in the memory, such that the communication device performs the method described in any one of the possible implementations of the first to fifth aspects.

[0117] In one possible design, the communication device described in the twelfth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the twelfth aspect and other communication devices.

[0118] In the embodiments of this application, the communication device described in the twelfth aspect can be a first network element as described in any of the implementations of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in the twelfth aspect can be a second network element as described in the second aspect, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in the twelfth aspect can be a session management function network element as described in the fourth aspect, or a chip (system) or other component or assembly disposed in the session management function network element, or a device containing the session management function network element.

[0119] Furthermore, the technical effects of the communication device described in the twelfth aspect can be referred to the technical effects of the method described in any of the implementations of the first to fifth aspects, and will not be repeated here.

[0120] In a thirteenth aspect, a communication device is provided, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the method described in any one of the first to fifth aspects.

[0121] In one possible design, the communication device described in aspect thirteen may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in aspect thirteen and other communication devices.

[0122] In the embodiments of this application, the communication device described in the thirteenth aspect can be a first network element as described in any of the implementations of the first, third, or fifth aspects, or a chip (system) or other component or assembly disposed in the first network element, or a device containing the first network element; or, the communication device described in the thirteenth aspect can be a second network element as described in the second aspect, or a chip (system) or other component or assembly disposed in the second network element, or a device containing the second network element; or, the communication device described in the thirteenth aspect can be a session management function network element as described in the fourth aspect, or a chip (system) or other component or assembly disposed in the session management function network element, or a device containing the session management function network element.

[0123] Furthermore, the technical effects of the communication device described in aspect thirteen can be referred to the technical effects of the method described in any of the implementations of aspect one or two, and will not be repeated here.

[0124] Fourteenthly, a communication system is provided. The communication system includes: a first network element for performing the method described in the first aspect, and a second network element for performing the method described in the second aspect.

[0125] In a fifteenth aspect, a communication system is provided. The communication system includes: a first network element for performing the method described in the third aspect, and a session management function network element for performing the method described in the fourth aspect.

[0126] In a sixteenth aspect, a communication system is provided. The communication system includes: a first network element for performing the method described in the fifth aspect, and a first local session management function network element that interacts with the first network element, the first local session management function network element being able to provide feedback to the first network element on a queried second local session management function network element.

[0127] In a seventeenth aspect, a communication chip is provided, wherein instructions are stored that, when the chip is operated on a communication device, cause the communication method described in any one of the first to fifth aspects to be implemented.

[0128] Eighteenth aspect: A computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, the computer causes the computer to perform the method described in any one of the possible implementations of the first to fifth aspects.

[0129] Nineteenth aspect, a computer program product is provided, comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform the method described in any one of the possible implementations of the first to fifth aspects. Attached Figure Description

[0130] Figure 1 This is a schematic diagram of the architecture of a 5G mobile communication system.

[0131] Figure 2 A flowchart illustrating the edge service discovery process for UEs;

[0132] Figure 3 This is a schematic diagram of an architecture that includes multiple L-SMFs;

[0133] Figure 4 A schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application is applicable;

[0134] Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 1 ;

[0135] Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 2 ;

[0136] Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 3 ;

[0137] Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 4 ;

[0138] Figure 9 Flowchart of the communication method provided in the embodiments of this application Figure 5 ;

[0139] Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 7 ;

[0140] Figure 3 Schematic diagram of the communication device provided in the embodiments of this application Figure 8 ;

[0141] Figure 9 Schematic diagram of the communication device provided in the embodiments of this application Figure 4 . Detailed Implementation

[0142] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0143] 1. Fifth generation (5G) mobile communication system (5G system, 5GS):

[0144] Figure 10This is a schematic diagram of the 5GS architecture. Figure 5-10 As shown, 5GS includes: an access network (AN) and a core network (CN), and may also include: terminal devices.

[0145] The aforementioned terminal device can be a terminal with transceiver functions, or a chip or chip system that can be installed in the terminal. This terminal can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminals in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, roadside units (RSUs) with terminal functions, etc. The terminal device of this application may also be an on-board module, on-board unit, on-board component, on-board chip or on-board unit that is built into a vehicle as one or more components or units.

[0146] The aforementioned AN is used to implement access-related functions, providing network access capabilities to authorized users in specific areas, and determining transmission links of different quality levels to transmit user data based on user level, service requirements, etc. The AN forwards control signals and user data between the terminal device and the CN. The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining the mobile network's subscription data, providing terminal devices with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following network elements: User Plane Function (UPF), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), Unified Data Repository (UDR), and Application Function (AF).

[0147] like Figure 5 As shown, the UE accesses the 5G network through the RAN device. The UE communicates with the AMF through the N1 interface (N1 for short); the RAN communicates with the AMF through the N2 interface (N2 for short); the RAN communicates with the UPF through the N3 interface (N3 for short); the SMF communicates with the UPF through the N4 interface (N4 for short); and the UPF accesses the data network (DN) through the N6 interface (N6 for short). Furthermore, Figure 1The control plane functions shown, such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, or AF, interact using service-oriented interfaces. For example, the service-oriented interface provided by AUSF is Nausf; AMF is Namf; SMF is Nsmf; NSSF is Nnssf; NEF is Nnef; NRF is Nnrf; PCF is Npcf; UDM is Nudm; UDR is Nudr; and AF is Naf.

[0148] RAN equipment can be a device that provides access for terminal devices. For example, RAN equipment may include: access network equipment for next-generation mobile communication systems, such as 6G, such as 6G base stations, or in next-generation mobile communication systems, the network equipment may also have other naming conventions, all of which are covered within the protection scope of the embodiments of this application, and this application does not limit them in any way. Alternatively, RAN equipment may also include 5G, such as gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it may be a network node constituting a gNB, transmission and reception point (TRP or transmission point (TP)) or transmission measurement function (TMF), such as a building baseband unit (BBU), or a centralized unit (CU) or distributed unit (DU), an RSU with base station functionality, or a wired access gateway, or the core network of 5G. Alternatively, RAN equipment may also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted equipment, and so on.

[0149] The User-Defined Processing (UPP) is primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, a UPF can receive user data from a data network (DN) and forward it to the terminal device through access network equipment. A UPF can also receive user data from the terminal device through access network equipment and forward it to the DN. A DN refers to the operator's network that provides data transmission services to users. Examples include Internet Protocol (IP) multimedia services (IMS) and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminal devices. In a Protocol Data Unit (PDU) session, the UPF directly connected to the DN via N6 is also called the Protocol Data Unit Session Anchor (PSA).

[0150] AUSF is primarily used to perform security authentication for terminal devices.

[0151] AMF is primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0152] SMF is primarily used for session management in mobile networks. This includes session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting a UPF (User Provider for Packet Forwarding) to provide packet forwarding capabilities.

[0153] The PCF primarily supports providing a unified policy framework to control network behavior, delivering policy rules to control-layer network functions, and acquiring user subscription information related to policy decisions. The PCF can provide policies to the AMF and SMF, such as Quality of Service (QoS) policies and slice selection policies.

[0154] NSSF is primarily used to select network slices for terminal devices.

[0155] NEF is primarily used to support the opening of capabilities and events.

[0156] UDM is primarily used to store user data, such as contract data and authentication / authorization data.

[0157] UDR is primarily used to store structured data, including contract data, policy data, externally exposed structured data, and application-related data.

[0158] AF primarily supports interaction with CN to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0159] It is understandable that the CN may also include other possible network elements, such as the edge application server discovery function (EASDF) network element, which can be used to discover application edge servers, etc., without limitation.

[0160] It is understood that the functions mentioned in the embodiments of this application can also refer to functional network elements or functional entities. For example, UPF can be referred to as UPF network element, AMF can be referred to as AMF network element, SMF can be referred to as SMF network element, PCF can be referred to as PCF network element, and so on, without limitation.

[0161] It should be noted that this application uses a 5G system as an example to introduce the relevant technical solutions, but the application of these technical solutions is not limited to 5G systems. It is understood that the relevant technical solutions may also be applicable to subsequent evolved communication systems, such as 6G communication systems, and are not limited thereto.

[0162] 2. Content Delivery Network (CDN)

[0163] The basic idea of ​​a CDN is to bypass bottlenecks and points of failure on the internet that could affect data transmission speed and stability, making content delivery faster and more stable. A CDN caches website content at the network edge (the point closest to the user's network connection). When a user accesses the website content, a scheduling system routes or directs the user's request to the cache server closest to the user's network connection or with the best access performance. This cache server then provides the content service to the user. Compared to directly accessing the origin server, this method shortens the network distance between the user and the content, thus achieving a speedup effect.

[0164] For example, when a UE requests an image resource under a certain domain name, such as image #1, the UE will first initiate a domain name resolution request to the local domain name system (DNS). When the local DNS resolves the domain name, it can send the domain name resolution request to the application's own DNS server according to the configuration. This DNS server can allocate the best node access node Internet Protocol (IP) address for the domain name resolution request.

[0165] The local DNS retrieves the best access node IP returned by the application's own DNS server and sends it to the UE. The UE can then initiate a resource access request based on the CDN access node corresponding to that IP. If the CDN access node caches the requested resource, it can directly return the data to the UE, at which point the UE's request ends. If the CDN access node does not cache the requested resource, it can request the resource from the service's origin server through a CDN intermediate origin server. The service's origin server, after obtaining the resource, sends it to the CDN access node. The CDN access node can then cache the resource and send it to the UE, at which point the UE's request ends.

[0166] 3. Edge Application Server (EAS)

[0167] EAS can provide near-field computing resources to terminal devices, thereby reducing network transmission latency for terminal devices to access computing resources. EAS can be deployed on a local DN, or a local part of the DN. The network can select a UPF network element close to the local DN to establish a transmission path for the terminal device, which can then use this established path to access computing resources in the EAS. Each local DN can correspond to a data network access identifier (DNAI).

[0168] Edge Application Server (EAS) deployment information (EDI) can characterize the deployment information of EAS. EDI may include at least one of the following: AF identity (AF ID), DN name (DNN), fully qualified domain name (FQDN), DNAI, EAS internet protocol (IP) address range information, etc. For details, please refer to the relevant introduction of existing protocols, which will not be elaborated here.

[0169] It is understood that in the embodiments of this application, "deployment information of edge application server" and "deployment information of edge application server" can be interchanged and are not limited.

[0170] 4. Intermediate Session Management Function (I-SMF)

[0171] The introduction of I-SMF in 5G networks primarily addresses the issue of service access across SMF service areas. In large networks, especially across geographical regions, a single SMF may not be able to effectively manage all UPFs. Therefore, I-SMF is designed to insert between the SMF and UPF to support service continuity and accessibility across SMF service areas. For example, when a user moves across provinces or regions during service operations, or accesses regional services across SMFs, I-SMF can be inserted based on user location and slice selection to maintain service continuity. Furthermore, I-SMF can control UPFs that the SMF cannot directly control. For instance, when a user is not in the tracking area (TA) served by the SMF of the PDU session, the AMF inserts I-SMF to control the intermediate UPF (I-UPF) at the N3 interface with the 5G access network. In other words, when services involve cross-regional issues, the assistance of I-SMF is needed to connect to the target PSA.

[0172] In the current 5G architecture, an SMF (Service Management Function) connects to only one I-SMF (In-Service Management Function) at a time, and the SMF knows its uniquely connected I-SMF. When it comes to I-SMF insertion, switching, or removal, the SMF is not involved in I-SMF discovery. In the existing process, the selection of the I-SMF can be determined by the AMF (Application Management Function), and the triggering of I-SMF insertion, modification, and removal can be based on AF (Agent Request), AMF triggering, SMF triggering, etc. (due to reasons such as terminal device movement and load balancing). For example, in an SMF-triggered I-SMF insertion, modification, or removal process, the SMF can request the AMF to insert, modify, or remove the I-SMF, and the AMF is responsible for inserting the new I-SMF or removing or modifying the existing I-SMF. It can be understood that this I-SMF can manage the general session management function elements of intermediate user plane function network elements.

[0173] at present, Figure 5 A flowchart illustrating the edge service discovery process for a UE, as follows: Figure 6 As shown, the method may include:

[0174] S201, the UE sends a DNS query message to the EASDF.

[0175] DNS query messages may include fully qualified domain names (FQDNs).

[0176] Optionally, the FQDN can be used to identify the UE's services.

[0177] Optionally, the DNS query message may also include the UE's location information. The UE's location information can be used to indicate the UE's location.

[0178] S202, EASDF sends a DNS reporting message to SMF.

[0179] The DNS reporting message may include the FQDN carried in the DNS query message in step S201 above.

[0180] S203, SMF sends the EDNS client subnet (ECS) option to EASDF.

[0181] information.

[0182] EDNS can be an abbreviation for DNS Extension.

[0183] Optionally, the SMF can determine ECS option information based on the UE's location.

[0184] S204, EASDF sends a DNS query message to the DNS server.

[0185] Optionally, EASDF can also send the ECS option to the DNS server.

[0186] Optionally, EASDF can generate ECS options based on ECS option information.

[0187] S205, The DNS server sends the IP address of the EAS, determined according to the ECS option, to the EASDF.

[0188] Optionally, the DNS server can store the IP addresses of one or more EASs. After receiving the ECS option, the DNS server can determine the IP address of the EAS that is closest to the location of the UE indicated by the ECS option.

[0189] In step S205, the IP address of the EAS determined can be the address of the EAS corresponding to the service accessed by the UE.

[0190] S206, EASDF sends the IP address of EAS to SMF.

[0191] S207, SMF determines the first DNAI in the first EDI.

[0192] If the IP address of the EAS is within the range of EAS addresses included in the first EDI, then the SMF network element can determine the DNAI in the first EDI.

[0193] The first EDI may include at least one of the following: first address range information, first DNAI, first FQDN and identification information of the first DNS server, etc., without limitation.

[0194] Optionally, the first address range information, the first DNAI, the first FQDN, and the identification information of the first DNS server correspond to each other.

[0195] Optionally, the address range indicated by the first address range information can be the address of the first EAS. The first EAS can be one or more edge application servers deployed in the first operator network. The data network access point identified by the first DNAI can be used to access the first EAS. The first FQDN can be the service information of the first EAS. The first DNS server can be used to query the address of the first EAS.

[0196] Optionally, if the first EDI includes the first FQDN, the SMF network element can also determine whether the FQDN in the DNS query message is the first FQDN in the first EDI. If the FQDN in the DNS query message is the first FQDN in the first EDI, and the IP address of the EAS is within the address range indicated by the first address range information of the EAS included in the first EDI, then the SMF network element can determine the first DNAI in the first EDI.

[0197] S208, the SMF network element selects the PSA based on the DNAI and establishes a protocol data unit (PDU) session.

[0198] This PDU session can be used to access the EAS of the local DN.

[0199] It is understandable that the above Figure 2 The method shown is the edge application service discovery process, whereby the UE can access computing resources in the edge application server using the established PDU session. After step S208 above, the SMF can also insert an uplink classifier (ULCL) and / or PSA for the PDU session based on the selected EAS to support communication between the terminal device and the EAS.

[0200] In this process, if the SMF acts as the central SMF (an SMF deployed at the network center), the central SMF can connect to at least one local session management function (L-SMF) network element to support communication between the terminal device and the EAS. The L-SMF can be an SMF located at an edge node. In this embodiment, the local session management function network element can be a dedicated session management function network element that manages the local user plane function network element. For example, the L-SMF can be a campus-level SMF, serving as the control plane for the entire campus.

[0201] For example, Figure 6 A schematic diagram of an architecture including multiple L-SMFs, such as Figure 7 As shown, this architecture may include: PCF, SMF, AMF, ULCL or branch point (BP), PSA, multiple local PSAs (L-PSA), and multiple L-SMFs (e.g., two). The local PSA can be a PSA located at an edge node, responsible for connecting the UE and the local EAS. The local PSA is managed by its corresponding L-SMF.

[0202] The difference between L-SMF and I-SMF is that multiple L-SMFs can exist, and a central SMF can connect to an L-SMF. This L-SMF can be a dedicated session management function network element that manages local user plane function network elements, which can be dedicated user plane function network elements with specific network interfaces. The central SMF can store the EDI of its managed area. When a certain PSA is not present in the central SMF's managed area (e.g., the PSA could be a local PSA managed by the L-SMF, which the central SMF is unaware of), or when the central SMF is unaware of a certain EDI (e.g., the EDI could be a local EDI managed or stored by the L-SMF, but not stored by the central SMF), an L-SMF may be needed to connect to that PSA to support communication between the terminal device and the EAS. The SMF storing the local EDI can find the corresponding EAS to support communication between the terminal device and the EAS. The specific functions of the central session management function network element can be understood to be similar to those of the SMF, implementing session management functions and deployed at the network center. When a terminal needs to establish edge application services, the central session management function network element is responsible for selecting and inserting appropriate local session management function network elements to support the terminal's edge application services.

[0203] However, if the SMF is unaware of a particular EDI, it may be unable to identify the administrator of that EDI.

[0204] To address the aforementioned technical problems, this application proposes the following technical solutions, which will be described below with reference to the accompanying drawings.

[0205] The technical solutions of this application embodiment can be applied to various communication systems, such as wireless network systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, 4G mobile communication systems such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5G mobile communication systems such as NR systems, and future communication systems, etc.

[0206] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information (such as the first instruction information, second instruction information, or third instruction information below) is called the information to be instructed. In the specific implementation process, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a correlation between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement order of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the instruction overhead caused by individually indicating the same information.

[0207] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.

[0208] "Predefined" or "pre-configured" can be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0209] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0210] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0211] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0212] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0213] To facilitate understanding of the embodiments of this application, let's first take... Figure 3 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 7 This is a schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application is applicable.

[0214] like Figure 8As shown, this communication system is applicable to the aforementioned 5GS and mainly includes at least one of the following: a first network element, a second network element, a third network element, a local session management function network element (such as a first local session management function network element, a second local session management function network element, etc.), or a session management function network element. It is understood that any two network elements in this communication system can communicate directly or indirectly, without limitation.

[0215] To enable the discovery of the administrator of a given EDI when the SMF is unaware of it, this communication system provides three solutions:

[0216] Option 1: After receiving the first request message, the first network element can request the second network element to query the local session management function network element corresponding to the edge application server identified by the first information, or in other words, the local session management function network element that manages the edge application server, based on the first information in the first request message. The first network element can send the queried local session management function network element information to the third network element so that the third network element can determine the local session management function network element corresponding to the edge application server. In this way, even when the first network element is unaware of the deployment information of the edge application server identified by the first information, or in other words, lacks the deployment information of the edge application server identified by the first information, it can still discover the manager of the deployment information of the edge application server identified by the first information. This manager is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, thereby supporting communication between the terminal device and the edge application server and improving communication efficiency.

[0217] The first network element can be a policy control function network element (such as PCF), as detailed in the above introduction to 5GS, or a network element used in future communication systems to implement corresponding functions for user data processing, without limitation.

[0218] The second network element can be at least one of the following: edge application server discovery function network (such as EADSF), network open function network element (such as NEF), or network storage function network element (such as NRF), etc. For details, please refer to the relevant introduction of 5GS above. The second network element can also be any other network element that stores the EDI corresponding to L-SMF, or stores the correspondence between L-SMF and EAS (L-SMF provides services for the EAS), etc., without limitation.

[0219] The third network element can be the session management function network element of the terminal device (such as SMF, i.e., the central SMF). That is, the session management function network element can be: a session management function network element that provides services to the terminal device. For details, please refer to the relevant introduction of 5GS above, or the network element used to implement the corresponding function of session management in future communication systems. There is no limitation on this.

[0220] Alternatively, after receiving the first request message, the first network element can, based on the first information in the first request message, request the second network element to query the local session management function network element corresponding to the edge application server identified by the first information, or in other words, the local session management function network element that manages the edge application server. The first network element can directly send the edge application server information to the queried local session management function network element so that the local session management function network element can subsequently find the edge application server corresponding to the service. In this way, even when the first network element is unaware of the deployment information of the edge application server identified by the first information, or in other words, lacks the deployment information of the edge application server identified by the first information, it can still discover the manager of the deployment information of the edge application server identified by the first information. This manager is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, thereby supporting communication between the terminal device and the edge application server and improving communication efficiency.

[0221] The first network element can be a session management function network element for terminal devices (such as SMF, i.e., the central SMF), which provides services to terminal devices. For details, please refer to the relevant introduction to 5GS mentioned above. Alternatively, it could be a network element used in future communication systems to implement corresponding session management functions; there are no limitations on this. The second network element can be at least one of the following: an edge application server discovery function network element (such as EADSF), a network open function network element (such as NEF), or a network storage function network element (such as NRF), etc. For details, please refer to the relevant introduction to 5GS mentioned above. The second network element can also be any other network element that stores local EDI, or stores the correspondence between L-SMF and EAS (where L-SMF provides services to the EAS), etc. There are no limitations on this. For details on the local session management function network element (such as L-SMF), please refer to the relevant introduction in the technical terminology section above; further details are omitted here.

[0222] Option 2: After the first network element receives the first information from the first message sent by the session management function network element, it can directly determine the local session management function network element corresponding to the edge application server identified by the first information based on the stored correspondence between local session management function network elements and edge application servers, without needing to parse the first request message. The first network element can directly forward the first request message to the determined local session management function network element, so that the local session management function network element can execute subsequent steps based on the first request message. In this way, even when the session management function network element is unaware of the deployment information of the edge application server identified by the first information, or in other words, when the deployment information of the edge application server identified by the first information is lacking, the first network element can discover the manager of the deployment information of the edge application server identified by the first information. This manager is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, thereby supporting communication between the terminal device and the edge application server and improving communication efficiency.

[0223] The first network element can be at least one of the following: an edge application server discovery function network element (such as EADSF), a network open function network element (such as NEF), or a network storage function network element (such as NRF), etc. For details, please refer to the relevant introduction of 5GS above. The first network element can also be any other network element that stores local EDI, or stores the correspondence between L-SMF and EAS (where L-SMF provides services to the EAS), etc., without limitation. The session management function network element (such as SMF, i.e., the central SMF) can provide services to terminal devices. For details, please refer to the relevant introduction of 5GS above, and will not be elaborated further. The local session management function network element (such as L-SMF) can be referred to the relevant introduction in the technical terminology section above, and will not be elaborated further.

[0224] Option 3: The first network element stores the mapping between local session management function network elements and source edge application servers, but not the mapping between local session management function network elements and target edge application servers. That is, the first network element stores the deployment information of the source edge application server, but not the deployment information of the target edge application server. In this case, the first network element can query the second local session management function network element corresponding to the target edge application server through the first local session management function network element corresponding to the source edge application server. In this way, even when the first network element is unaware of the deployment information of the target edge application server, or in other words, when the deployment information of the target edge application server is missing, the first network element can discover the manager of the deployment information of the target edge application server. This manager is a local session management function network element that can manage or store the deployment information of the target edge application server, thus supporting communication between terminal devices and both the source and target edge application servers, improving communication efficiency.

[0225] The first network element can be a session management function network element (such as SMF, i.e., central SMF) of the terminal device. This session management function network element can provide services to the terminal device. For details, please refer to the relevant introduction of 5GS above. Alternatively, it can be a network element used to implement the corresponding function of session management in future communication systems. No limitation is made in this regard.

[0226] It is understood that the session management function network element in this application embodiment may refer to the central session management function network element, which can establish a connection with one or more local session management function network elements, and will not be elaborated further.

[0227] The following will combine Figure 4 This application provides a detailed description of the interaction process between various network elements / devices in the aforementioned communication system through method embodiments. The communication method provided in this application can be applied to the aforementioned communication system and specifically to various scenarios / processes mentioned in the aforementioned communication system, which will be described in detail below.

[0228] For example, Figure 9 Flowchart of the communication method provided in the embodiments of this application Figure 5 This communication method applies to Scheme 1 of the aforementioned communication system, mainly involving the interaction between the first network element, the second network element, and other network elements (such as the third network element and the local session management function network element). Specifically, as shown... Figure 6 As shown, the flow of this communication method is as follows:

[0229] S501, the first network element receives the first request message.

[0230] The first request message may include first information, second information, and third information.

[0231] The first piece of information can be used to identify the edge application server. For example, the first piece of information may include at least one of the following: the address of the edge application server (such as the IP address of the EAS), the data network access identifier (DNAI), or the identification information of the domain name system server (DNS), etc., without limitation. It is understood that the address of the edge application server, the data network access identifier, the fully qualified domain name, and the identification information of the domain name system server can be mutually mapped. For example, the EAS can be one or more edge application servers deployed on an operator's network. The data network access point identified by the DNAI can be used to access the EAS, and the DNS server can be used to query the address of the EAS.

[0232] The second information can be used to indicate the terminal device; for example, it may include the terminal device's identity (ID), the UE's IP address, etc., without limitation. The edge application server identified by the first information can be used to provide services to the terminal device.

[0233] The third piece of information can be used to indicate relevant information about the business between the terminal device and the edge application server. For example, the third piece of information can be an FQDN, application ID, etc., without limitation. For a detailed description of the FQDN and application ID, please refer to existing technologies, which will not be elaborated here. It is understood that the FQDN can also be used to identify the edge application server; that is, the aforementioned first piece of information can also include the FQDN, etc., without limitation.

[0234] In one possible design, the first request message can be used to request the redeployment of the edge application server.

[0235] The edge application server may include a source edge application server and a target edge application server. The third information is used to indicate relevant information about the business between the terminal device and the edge application server, including: [The third information is used to indicate relevant information about the business between the terminal device and the source edge application server.]

[0236] In other words, the services of this terminal device are currently being provided by the source edge application server. Due to reasons such as the movement of the terminal device or network load balancing (e.g., congestion or downtime of the source edge application server), the source edge application server can no longer meet the service requirements of the terminal device. At this time, the first request message can be used to request the session management function network element to perform a redeployment (process) of the edge application server. For example, the redeployment may include: switching the services of the terminal device from the source edge application server to the target edge application server (after the switch, the target edge application server will provide services for the terminal device); or the redeployment may also be: diverting a portion of the traffic of the terminal device's services from the source edge application server to the target edge application server, etc., without limitation.

[0237] In one possible design, the first request message is used to request the rediscovery of the edge application server.

[0238] In other words, the terminal device's services are currently being provided by the edge application server identified by the first information identifier. Due to reasons such as the terminal device's movement or network load balancing (e.g., congestion or outage of the source edge application server), the edge application server can no longer meet the terminal device's service requirements. In this case, the first request message can be used to request the session management function network element to perform a rediscovery (process) of the edge application server. For example, the rediscovery may include: rediscovering a new edge application server for the terminal device's services, and subsequently switching the terminal device's services to the newly discovered edge application server, where the new edge application server will provide services for the terminal device's services; or, offloading a portion of the terminal device's service traffic from the source edge application server to the rediscovered edge application server, etc., without limitation.

[0239] It is understandable that the specific implementation of the redeployment and rediscovery process of the edge application server by the session management function network element can refer to existing technologies and will not be elaborated here.

[0240] It is understandable that, due to reasons such as the mobility of terminal devices and network load balancing, the Application Function (AF) can trigger a request to the network function in the operator's network to request the execution of the redeployment / rediscovery process of the edge application server. That is, this first request message can be an AF influence message. For details, please refer to the relevant description in the protocol, which will not be elaborated here.

[0241] The following example illustrates how the first network element receives the first request message.

[0242] Case 1: The first network element can be a policy control function (PCF) network element.

[0243] At this point, the policy control function network element receiving the first request message can be achieved by receiving the first request message sent by the application function through the Network Open Function (NEF) network element. Alternatively, the application function can send the first request message to the policy control function network element through the NEF network element.

[0244] Case 2: The first network element can be the Session Management Function (SMF) network element of the terminal device.

[0245] At this point, the session management function network element can receive the first request message in the following ways: The session management function network element receives the first request message sent by the application function through the Network Open Function (NEF) network element and the Policy Control Function (PCF) network element. Alternatively, the application function can send the first request message to this session management function network element through the NEF and PCF network elements. This session management function network element can provide services to terminal devices. It can be a central session management function network element and can connect to multiple local session management function network elements. This session management function network element can be a central SMF, deployed at the network center, and its specific functions can refer to the functions of an SMF to implement session management. When a terminal needs to establish edge application services, the central session management function network element is responsible for selecting and inserting appropriate local session management function network elements to support the terminal's edge application services.

[0246] As you can understand, the above is an example of the first network element receiving the first request message from the AF. The first network element can also receive the first request message from any other possible network element, such as the AMF, etc. The implementation principle is similar, and you can refer to it for understanding. It will not be elaborated here.

[0247] It is understood that the aforementioned first request message, first information, second information, and third information may also include any other possible information, without limitation. The naming of the aforementioned first request message, first information, second information, and third information is merely an example and may be replaced with any other possible names, without limitation.

[0248] S502, the first network element queries the second network element for the local session management function network element corresponding to the edge application server of the first information identifier.

[0249] It is understandable that after the first network element receives the first request message, it needs to determine the local session management function network element (which can be denoted as L-SMF#1) that manages the edge application server (which can be denoted as EAS#1) with the first information identifier. This L-SMF#1 can provide services to EAS#1. This local session management function network element can be used to determine the local protocol data unit session anchor point (L-PSA). The local protocol data unit session anchor point can be on the transmission path of the service between the terminal device and the edge application server. That is, the local protocol data unit session anchor point can be used to connect the terminal device and the edge application server.

[0250] The implementation process of this step will be described in detail below.

[0251] In one possible design, the first network element queries the second network element for the local session management function network element corresponding to the edge application server of the first information identifier, including:

[0252] The first network element sends a second request message to the second network element. Correspondingly, the second network element receives the second request message from the first network element.

[0253] The second network element sends information about the local session management function network element to the first network element based on the second request message. Correspondingly, the first network element receives information about the local session management function network element from the second network element.

[0254] The second request message can be used to request a query for the local session management function network element corresponding to the edge application server identified by the first information identifier. For example, the second request message may include the aforementioned first information, etc., and the second network element can determine the local session management function network element corresponding to the edge application server identified by the first information identifier based on the first information. The first network element can send the second request message to the second network element to trigger the second network element to query the local session management function network element corresponding to the edge application server, thus enabling on-demand querying and flexibility. After the second network element finds the local session management function network element corresponding to the target edge application server, it can return the information of the local session management function network element to the first network element.

[0255] The following section details how the second network element can determine the local session management function network element corresponding to the edge application server identified by the first information.

[0256] In one possible implementation, the second network element can be used to store the correspondence between the local session management function network element and the edge application server (including EAS#1).

[0257] In other words, the second network element stores the deployment information of the edge application servers corresponding to each local session management function network element. The correspondence between the local session management function network element and the edge application server indicates that the local session management function network element can provide services to the edge application server. It can be understood that the edge application server may include the edge application server identified by the first information. For example, the second network element stores the correspondence between EAS#1 and L-SMF#1, or the second network element stores the deployment information of the edge application server managed by L-SMF#1 (including the deployment information of EAS#1). In this case, the second network element can query the local session management function network element corresponding to the edge application server identified by the first information based on the stored correspondence.

[0258] For example, suppose the second network element stores a corresponding relationship: L-SMF#1 is associated with (EAS#1, EAS#2, EAS#3, EAS#4); L-SMF#2 is associated with (EAS#4, EAS#5). In this case, the second network element can directly determine that EAS#1 is associated with L-SMF#1 based on the first information, such as EAS#1 IP and the stored corresponding relationship.

[0259] In another possible implementation, the second network element can be used to query the data storage network element for the local session management function network element corresponding to the edge application server of the first information identifier.

[0260] For example, the second network element sends a third request message to the data storage network element. Correspondingly, the data storage network element receives the third request message from the second network element.

[0261] Based on the third request message, the data storage network element sends information about the local session management function network element to the second network element. Correspondingly, the second network element receives the information from the local session management function network element.

[0262] The second network element sends information about the local session management function network element to the first network element.

[0263] It is understandable that if the correspondence between the local session management function network element and the edge application server determined by the second network element does not include the local session management function network element corresponding to the edge application server of the first information identifier, that is, the second network element cannot find it by itself, then the second network element can query the local session management function network element corresponding to the edge application server of the first information identifier through other network elements, such as data storage network elements (such as UDR).

[0264] The data storage network element can obtain the local session management function network element (EAS#1 corresponds to L-SMF#1) corresponding to the edge application server identified by the first information based on stored data, such as deployment information of the edge application server (including EAS#1) corresponding to each local session management function network element. It then sends the information of the local session management function network element to the second network element, which can then feed the information back to the first network element. This information can be used to indicate the local session management function network element of the edge application server identified by the first information. For example, this information may include the IP address and ID of L-SMF#1, without limitation.

[0265] Based on the above introduction, the second network element can be a network element that stores the correspondence between the local session management function network element and the edge application server. For example, the second network element can be at least one of the following: edge application server discovery function network element, network opening function network element, or network storage function network element, etc., without limitation.

[0266] It is understood that the second and third request messages described above may include any other possible information, without limitation. The naming of the second and third request messages described above is merely an example and may be replaced with any other possible names, without limitation.

[0267] It is understandable that after the first network element queries the second network element for the local session management function network element corresponding to the edge application server of the first information identifier, the first network element can execute subsequent steps based on the query result. The following two implementations will be used as examples for specific description.

[0268] In one possible implementation, S503a, based on the query result, the first network element sends the information of the local session management function network element (L-SMF#1) to the third network element.

[0269] The first network element can be a policy control function network element (corresponding to situation 1 above). The third network element can be a session management function network element of the terminal device (central session management function network element). That is, the policy control function network element can send the information of the local session management function network element corresponding to the edge application server with the first information identifier to the (central) session management function network element. The information of the local session management function network element can be used to instruct the local session management function network element, such as the IP address of L-SMF#1, the ID of L-SMF#1, etc. It can be understood that the central session management function network element can select L-SMF#1 for insertion when the terminal needs to establish edge application services.

[0270] In one possible design, the first network element sends information from the local session management function network element to the third network element, including:

[0271] The first network element sends a first message to the third network element. Correspondingly, the third network element receives the first message from the policy control function network element.

[0272] The first message may include information from the local session management function network element (L-SMF#1), first information, second information, and third information.

[0273] In other words, the policy control function network element can send the information of the queried local session management function network element, the first information, the second information, and the third information to the session management function network element through the first message. Thus, even without storing the deployment information of the edge application server identified by the first information, the session management function network element can obtain the local session management function network element that manages the edge application server and use it to trigger subsequent steps. For example, the SMF can instruct L-SMF#1 to perform subsequent EAS switching, deletion, or addition, L-PSA switching, deletion (disconnection), or addition (connection establishment), etc. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated further.

[0274] It is understandable that the policy control function network element can also directly send the information of the local session management function network element (L-SMF#1) and the first request message to the session management function network element through the first message, without any limitation.

[0275] In another possible implementation, S503b, based on the query result, the first network element sends information about the edge application server (EAS#1) to the local session management function network element.

[0276] In one possible design, the first network element sends information about the edge application server to the local session management function network element, including:

[0277] The first network element sends a second message to the local session management function network element. Correspondingly, the local session management function network element receives the second message from the first network element.

[0278] The second message may include information about the edge application server, second information, and third information.

[0279] The following will provide a detailed explanation using two examples.

[0280] Scenario 3: The first network element can be the session management function network element of the terminal equipment (central session management function network element). (Corresponding to Scenario 2 above)

[0281] In other words, after the session management function network element finds the local session management function network element corresponding to the edge application server identified by the first information identifier, it can directly send the EAS#1 information to the found local session management function network element (L-SMF#1). This EAS#1 information can be used to identify EAS#1, and it can be the same as the first information without limitation. The session management function network element can send the edge application server information, the second information, and the third information directly to the local session management function network element through the second message. The local session management function network element can trigger the execution of subsequent processes based on the second message. For example, L-SMF#1 can find EAS#1 based on its IP address, as well as the L-PSA connecting EAS#1 and the UE, for subsequent execution of EAS handover, deletion, or addition, L-PSA handover, deletion (disconnection), or addition (connection establishment), etc. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated further.

[0282] It is understandable that the session management function network element can also directly send the first request message to the local session management function network element, without any restrictions.

[0283] Scenario 4: The first network element can be a policy control function network element. (Corresponding to Scenario 1 above)

[0284] In other words, after the policy control function network element finds the local session management function network element corresponding to the edge application server identified by the first information identifier, it can directly send the EAS#1 information to the found local session management function network element (L-SMF#1). This EAS#1 information can be used to identify the EAS#1, and it can be the same as the first information without limitation. The policy control function network element can directly send the edge application server information, the second information, and the third information to the local session management function network element through the second message, without needing to send the queried information from the local session management function network element again. This reduces overhead and improves communication efficiency.

[0285] The local session management function network element can trigger the execution of subsequent processes based on the second message. For example, L-SMF#1 can find EAS#1 and the L-PSA connecting EAS#1 and UE based on the IP address of EAS#1, so as to perform subsequent EAS handover, deletion or addition, L-PSA handover, deletion (disconnection) or addition (connection establishment), etc. The implementation of these subsequent steps can refer to the existing technology and will not be elaborated here.

[0286] It is understandable that the policy control function network element can also directly send the first request message to the local session management function network element, without any restrictions.

[0287] If the aforementioned first information is used to identify edge application servers including a source edge application server and a target edge application server, then the local session management function network element corresponding to the edge application server identified by the first information may include: the local session management function network element corresponding to the source edge application server and the local session management function network element corresponding to the target edge application server. Subsequently, the local session management function network element corresponding to the source edge application server and the local session management function network element corresponding to the target edge application server can execute subsequent steps according to instructions. The implementation principle is similar and can be understood by reference, without further explanation. It should be noted that the local session management function network element corresponding to the source edge application server and the local session management function network element corresponding to the target edge application server can be the same or different, without limitation.

[0288] It is understood that the first and second messages mentioned above can also include any other possible information, without limitation. The naming of the first and second messages mentioned above is merely an example and can be replaced with any other possible names, without limitation.

[0289] In summary, after receiving the first request message, the first network element can, based on the first information in the first request message, request the second network element to query the local session management function network element corresponding to the edge application server identified by the first information, or in other words, the local session management function network element that manages the edge application server. The first network element can send the information of the queried local session management function network element to the third network element so that the third network element can determine the local session management function network element corresponding to the edge application server; or, the first network element can directly send the edge application server information to the queried local session management function network element so that the local session management function network element can subsequently find the edge application server corresponding to the service. In this way, even when the first network element is unaware of the deployment information of the edge application server identified by the first information, or in other words, lacks the deployment information of the edge application server identified by the first information, it can still discover the manager of the deployment information of the edge application server identified by the first information. This manager is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, thereby supporting communication between the terminal device and the edge application server and improving communication efficiency.

[0290] For example, Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 5-10 This communication method is applicable to Scheme 2 of the aforementioned communication system, mainly involving the interaction between the first network element, the session management function network element, and other network elements (such as the local session management function network element). Specifically, as shown... Figure 11-12 As shown, the flow of this communication method is as follows:

[0291] S601, the session management function network element obtains the first request message.

[0292] The first request message may include first information, second information, and third information. The first information may be used to identify the edge application server. The second information may be used to indicate the terminal device, and the third information may be used to indicate relevant information about the business between the terminal device and the edge application server.

[0293] In one possible design, the first request message can be used to request the redeployment of the edge application server.

[0294] The edge application server may include a source edge application server and a target edge application server. The third information is used to indicate relevant information about the business between the terminal device and the edge application server, including: [The third information is used to indicate relevant information about the business between the terminal device and the source edge application server.]

[0295] In one possible design, the first request message is used to request the rediscovery of the edge application server.

[0296] It is understood that the session management function network element can receive the first request message from the application function. For example, the session management function network element can receive the first request message sent by the application function through the network openness function and policy control function network elements. Alternatively, the application function can send the first request message to the session management function network element through the network openness function and policy control function network elements. This session management function network element can provide services to terminal devices, and it can be a central session management function network element, capable of connecting to multiple local session management function network elements.

[0297] The above is an example of the first network element receiving a first request message from the AF. The first network element can also receive first request messages from any other possible network element, such as AMF, etc. The implementation principle is similar and can be referred to for understanding, so it will not be elaborated here.

[0298] It is understood that the aforementioned first request message, first information, second information, and third information may also include any other possible information, without limitation. The naming of the aforementioned first request message, first information, second information, and third information is merely an example and may be replaced with any other possible names, without limitation.

[0299] Furthermore, for details regarding the first request message, please refer to the relevant description in step S501 above, which will not be repeated here.

[0300] S602, the session management function network element sends the first message to the first network element. Correspondingly, the first network element receives the first message from the session management function network element.

[0301] The first message may include a first request message and a first message.

[0302] In other words, the session management function network element can obtain the first information based on the first request message, and send the first request message and the first information to the first network element through the first message. Subsequently, the first network element can directly determine the edge application server to be queried based on the first information without parsing the first request message. This reduces processing difficulty and overhead.

[0303] The first network element can be a network element that stores the correspondence between local session management function network elements and edge application servers. For example, the first network element can be at least one of the following: edge application server discovery function network element, network opening function network element, or network storage function network element, etc., without limitation.

[0304] S603, the first network element queries the local session management function network element corresponding to the edge application server identified by the first information identifier based on the stored correspondence between the local session management function network element and the edge application server.

[0305] In other words, the first network element stores the deployment information of the edge application servers corresponding to each local session management function network element. The correspondence between the local session management function network element and the edge application server indicates that the local session management function network element can provide services to the edge application server. It can be understood that the edge application server may include the edge application server identified by the first information (which can be denoted as EAS#1). For example, the first network element stores the correspondence between EAS#1 and L-SMF#1. At this time, the first network element can query the local session management function network element corresponding to EAS#1 as L-SMF#1 based on the stored correspondence.

[0306] It is understandable that if the correspondence between the local session management function network element and the edge application server stored in the first network element does not include the local session management function network element corresponding to the edge application server of the first information identifier, that is, the first network element cannot find it itself, then the second network element can query the local session management function network element corresponding to the edge application server of the first information identifier by querying other network elements, such as data storage network elements (such as UDR). The implementation process can be referred to the relevant introduction in step S502 above, which will not be repeated here.

[0307] S604, the first network element sends a first request message to the local session management function network element. Correspondingly, the local session management function network element receives the first request message from the first network element.

[0308] That is, after the first network element queries the local session management function network element corresponding to the edge application server identified by the first information based on the first information, the first network element can directly forward the first request message to the queried local session management function network element so that the local session management function network element can perform subsequent steps based on the first request message. The implementation of the subsequent steps can refer to the relevant description in step S503 above, as well as the implementation of the existing technology, and will not be elaborated here.

[0309] In summary, after the first network element receives the first information from the first message sent by the session management function network element, it can directly determine the local session management function network element corresponding to the edge application server identified by the first information based on the stored correspondence between local session management function network elements and edge application servers, without needing to parse the first request message. The first network element can then directly forward the first request message to the determined local session management function network element, allowing the local session management function network element to execute subsequent steps based on the first request message. Thus, even when the session management function network element is unaware of the deployment information of the edge application server identified by the first information, or in other words, lacks the deployment information of the edge application server identified by the first information, the first network element can discover the manager of the deployment information of the edge application server identified by the first information. This manager is the local session management function network element that can manage or store the deployment information of the edge application server identified by the first information, thereby supporting communication between the terminal device and the edge application server and improving communication efficiency.

[0310] Based on the above introduction, the SMF storing local EDI can find the corresponding EAS to support communication between the terminal device and the EAS. The central SMF can store some local EAS EDIs (such as the EDI of the EAS currently providing services) to reduce the impact on the central SMF. When the AF requests an EAS switchover, the AF can send an AF request to the SMF to request the service to be switched from the source EAS to the target EAS. If the central SMF stores the source EAS EDI but not the target EAS EDI, how to find the L-SMF that manages the target EAS / target EDI to realize the service switchover from the source EAS to the target EAS is a technical problem that urgently needs to be solved. To address this problem, the embodiments of this application propose the following technical solutions.

[0311] For example, Figure 11 Flowchart of the communication method provided in the embodiments of this application Figure 1 This communication method is applicable to Scheme 3 of the aforementioned communication system, and mainly involves the interaction between the first network element and other network elements (such as the first local session management function network element).

[0312] Specifically, such asFigure 11 As shown, the flow of this communication method is as follows:

[0313] S701, the first network element receives the first request message.

[0314] S702, the first network element determines the first local session management function network element corresponding to the source edge application server and the second local session management function network element corresponding to the target edge application server.

[0315] The first network element can be the Session Management Function (SMF) network element of the terminal equipment. This Session Management Function network element can be the central SMF, which can connect to multiple L-SMFs.

[0316] The following is a detailed description of step S701.

[0317] The first request message may include first information, second information, and third information.

[0318] The first piece of information can be used to identify the source edge application server (which can be denoted as EAS#a) and the target edge application server (which can be denoted as EAS#b) associated with the terminal device.

[0319] For example, the first information may include first identification information and second identification information. The first identification information may be used to identify a source edge application server associated with a terminal device, and the first identification information may be used to identify a target edge application server. The source edge application server and the target edge application server are different.

[0320] The first identification information may include at least one of the following: the address of the first edge application server (such as the IP address of EAS#a), the first data network access identifier (first DNAI), or the identification information of the first domain name system server (first DNS), etc., without limitation. Optionally, the first identification information may also include: the first FQDN.

[0321] The second identification information may include at least one of the following: the address of the second edge application server (such as the IP address of EAS#b), the second data network access identifier (second DNAI), or the identification information of the second domain name system server (second DNS), etc., without limitation. Optionally, the second identification information may also include: a second FQDN.

[0322] The second piece of information can be used to instruct terminal devices.

[0323] The third piece of information can be used to indicate relevant information about the business between the terminal device and the source edge application server. For example, the third piece of information can be the first FQDN, the first application ID, etc., without limitation.

[0324] In one possible design, the first request message can be used to request the first network element to redeploy the edge application server.

[0325] In other words, the services of this terminal device are currently being provided by the source edge application server. Due to reasons such as the movement of the terminal device or network load balancing (e.g., congestion or downtime of the source edge application server), the source edge application server can no longer meet the service requirements of the terminal device. In this case, the first request message can be used to request the session management function network element to perform a redeployment of the edge application server. For example, redeployment may include: switching the terminal device's services from the source edge application server to the target edge application server (after the switch, the target edge application server will provide services for the terminal device); or redeployment may also include: diverting a portion of the terminal device's service traffic from the source edge application server to the target edge application server, etc., without limitation.

[0326] Furthermore, for a detailed description of the first request message, please refer to the relevant description in step S701 above, which will not be repeated here.

[0327] The following is a detailed description of step S702.

[0328] Specifically, the first local session management function network element (which can be denoted as L-SMF#a) can be determined by the session management function network element based on the stored correspondence between local session management function network elements and edge application servers, and the second local session management function network element (which can be denoted as L-SMF#b) can be queried by the session management function network element through the first local session management function network element. The first local session management function network element can provide services to the source edge application server, or in other words, the first local session management function network element can be used to manage the source edge application server; the second local session management function network element can provide services to the target edge application server, or in other words, the second local session management function network element can be used to manage the target edge application server.

[0329] In one possible design scheme, the above method embodiment may further include:

[0330] The first network element determines the first local session management function network element based on the stored information, but does not store information about the local session management function network element corresponding to the target edge application server.

[0331] In other words, the mapping relationships stored in the session management function network element include the mapping relationship between the source edge application server and the local session management function network element, but do not store the local session management function network element corresponding to the target edge application server. For example, the session management function network element stores: L-SMF#a is associated with (EAS#a, EAS#c); L-SMF#c is associated with (EAS#d, EAS#e). In this case, the session management function network element can directly determine that EAS#a is associated with L-SMF#a based on the first identifier information in the first information, such as the IP of EAS#a and the stored mapping relationship. If the session management function network element cannot find the L-SMF corresponding to EAS#b based on the stored mapping relationship, then the session management function network element can query the information of the local session management function network element corresponding to the target edge application server through the first local session management function network element.

[0332] The following is a detailed description. In one possible design scheme, after the first network determines the first local session management function network element based on the stored information, and has not stored information about the local session management function network element corresponding to the target edge application server, the above method implementation may further include:

[0333] S702a, the first network element sends a second request message to the first local session management function network element. Correspondingly, the first local session management function network element receives the second request message from the first network element.

[0334] In S702b, the first local session management function network element sends a second response message to the first network element based on the second request message. Correspondingly, the first network element receives the second response message from the first local session management function network element.

[0335] The second request message can be used to request the local session management function network element corresponding to the target edge application server. For example, the second request message may include the aforementioned second identification information, such as EAS#b IP address. The second response message may include information about the second local session management function network element.

[0336] In other words, if the first network element cannot find the local session management function network element corresponding to the target edge application server, it can send a second request message to the first local session management function network element to trigger the first local session management function network element to query the local session management function network element corresponding to the target edge application server based on the second identifier information. This allows for on-demand querying and flexibility. After the first local session management function network element finds the second local session management function network element corresponding to the target edge application server, the first local session management function network element can send a second response message back to the first network element with information about the second local session management function network element. This information can be used to instruct the second local session management function network element; for example, the information of the second local session management function network element can include the IP address of L-SMF#b, the ID of L-SMF#b, etc., without limitation.

[0337] The following section provides a detailed description of how the first local session management function network element queries the local session management function network element corresponding to the target edge application server based on the second identifier information.

[0338] In one possible implementation, the first local session management function network element can be used to store information about one or more edge application servers corresponding to the first local session management function network element. The one or more edge application servers include a target edge application server, and the first local session management function network element is determined to be a second local session management function network element corresponding to the target edge application server.

[0339] It is understood that the first local session management function network element can provide services to one or more edge application servers. The information of these one or more edge application servers can be used to identify them, such as their deployment information. That is, the first local session management function network element stores the deployment information of one or more edge application servers it manages, including the deployment information of the source edge application server.

[0340] For example, L-SMF#a stores the EDI of EAS#a, EDI of EAS#b, EDI of EAS#c, and so on; L-SMF#a can manage EAS#a, EAS#b, EAS#c, etc. In this case, L-SMF#a can determine the association between EAS#b and L-SMF#a based on second identification information, such as the EAS#b IP address. Therefore, L-SMF#a can be identified as the second local entity corresponding to the target edge application server. The management network element, i.e., L-SMF#b, is also identical to L-SMF#a.

[0341] In one possible implementation, the first local session management function network element is used to store information of one or more edge application servers corresponding to the first local session management function network element, wherein the one or more edge application servers do not include the target edge application server.

[0342] The first network element receives a second response message from the first local session management function network element, including:

[0343] The first network element receives the second response message from the second network element through the first local session management function network element.

[0344] The first local session management function network element and the second local session management function network element are different.

[0345] That is, the deployment information of one or more edge application servers stored in the first local session management function network element does not include the deployment information of the target edge application server. In this case, the first local session management function network element and the second local session management function network element are different.

[0346] In this scenario, the first local session management function network element can query the local session management function network element corresponding to the target edge application server through the second network element. That is, the second local session management function network element can be determined by the second network element. This second network element can be at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element, etc., without limitation.

[0347] For example, the first local session management function network element can send a request message, such as a third request message, to the second network element. This third request message can be used to request the second network element to query the local session management function network element corresponding to the target edge application server. For example, the third request message may include the aforementioned second identification information, such as EAS#b IP address. The second network element can determine the second local session management function network element corresponding to the target edge application server based on the second identification information.

[0348] The second network element can feed back the information of the second local session management function network element to the session management function network element through the first local session management function network element. For example, the second network element can send the second response message to the first local session management function network element, and the first local session management function network element can then forward the second response message to the session management function network element, etc., without limitation.

[0349] It is understood that the second and third request messages described above may include any other possible information, without limitation. The naming of the second and third request messages described above is merely an example and may be replaced with any other possible names, without limitation.

[0350] In summary, the first network element stores the correspondence between local session management function network elements and source edge application servers, but not the correspondence between local session management function network elements and target edge application servers. That is, the first network element stores the deployment information of the source edge application server, but not the deployment information of the target edge application server. In this case, the first network element can query the second local session management function network element corresponding to the target edge application server through the first local session management function network element corresponding to the source edge application server. In this way, even when the first network element is unaware of the deployment information of the target edge application server, or in other words, when the deployment information of the target edge application server is missing, the first network element can discover the manager of the deployment information of the target edge application server. This manager is a local session management function network element that can manage or store the deployment information of the target edge application server, thus supporting communication between terminal devices and both the source and target edge application servers and improving communication efficiency.

[0351] In conjunction with the above embodiments, optionally, the first local session management function network element and the second local session management function network element are the same, and the above method embodiments may further include:

[0352] The first network element sends an instruction message to the first local session management function network element based on the first request message. Correspondingly, the first local session management function network element receives the instruction message from the first network element.

[0353] The indication information can be used to instruct the first local session management function network element to modify the local protocol data unit session anchor point. The modified local protocol data unit session anchor point is on the service transmission path between the terminal device and the target edge application server.

[0354] In other words, after the session management function network element determines the first local session management function network element and the second local session management function network element (which are the same), the session management function network element can send indication information to the first local session management function network element to instruct it to perform L-PSA anchor point modification (such as insertion or replacement). The modified L-PSA can be used on the service transmission path between the terminal device and the target edge application server. It can be understood that the indication information can also instruct the first local session management function network element to perform other subsequent steps. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated here.

[0355] Optionally, the first local session management function network element and the second local session management function network element are different, and the above method embodiments may further include:

[0356] The first network element sends an instruction message to the second local session management function network element based on the first request message. Correspondingly, the second local session management function network element receives the instruction message from the first network element.

[0357] The indication information can be used to instruct the second local session management function network element to modify the local protocol data unit session anchor point. The modified local protocol data unit session anchor point is on the service transmission path between the terminal device and the target edge application server.

[0358] That is, after the session management function network element determines the first local session management function network element and the second local session management function network element (which are different from each other), the session management function network element can send an indication message (which can be denoted as indication message #1) to the second local session management function network element to instruct it to perform modifications to the L-PSA anchor point (such as insertion or replacement). The modified L-PSA can be used on the service transmission path between the terminal device and the target edge application server. It can be understood that the indication message can also instruct the second local session management function network element to perform other subsequent steps. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated here.

[0359] Optionally, the first network element may also send an instruction message, such as instruction message #2, to the first local session management function network element according to the first request message, to instruct the first local session management function network element to perform L-PSA anchor point modification, or to perform other subsequent steps. The implementation of these subsequent steps can refer to the existing technology and will not be elaborated here.

[0360] The above, in conjunction with the method embodiments, provides an overall overview of the communication method provided in this application. For ease of understanding, the method is further described below using three specific scenarios:

[0361] Scene 1: Figure 11 Flowchart of the communication method provided in the embodiments of this application Figure 5-10 This communication method mainly involves the interaction between the (central) SMF, L-SMF#1 (managing EAS#1, where EAS#1 is the source EAS), L-SMF#2 (managing EAS#2, where EAS#2 is the target EAS), EASDF / NRF, and AF. In scenario 1, the SMF stores the EDI of EAS#1 (denoted as EDI#1) but does not store the EDI of EAS#2 (denoted as EDI#2). In this case, the SMF can determine L-SMF#1 based on the stored EDI, and query the L-SMF#2 corresponding to EAS#2 through L-SMF#1. Thus, even when the SMF lacks EDI#2, it can discover the L-SMF#2 that manages EAS#2, supporting the UE to communicate with both EAS#1 and EAS#2, thereby improving communication efficiency.

[0362] It is understandable that in Scenario 1, each network element has already executed the PDU session establishment process, during which multiple L-SMFs have been inserted. That is, the SMF establishes a connection with multiple L-SMFs. This process can be considered a prerequisite for Scenario 1, and its specific implementation can be found in existing implementations, which will not be elaborated here.

[0363] Meanwhile, in Scenario 1, the SMF stores some EAS deployment information (such as EDI#1), or in other words, the SMF stores some L-SMFs (such as L-SMF#1), and their correspondence with at least one of FQDN, EAS IP, or DNAI. For ease of understanding, the following explanation uses the example of the SMF storing some L-SMFs and their correspondence with EAS IP. This correspondence between the L-SMFs and EAS IPs stored in the SMF can be considered a prerequisite.

[0364] Based on this preliminary process and prerequisites, specifically, such as Figure 5-10 As shown, the flow of this communication method is as follows:

[0365] S801, AF sends request message #1 to SMF. Correspondingly, SMF receives request message #1 from AF.

[0366] It is understandable that due to reasons such as UE mobility and load balancing, AF can trigger the sending of a request message to SMF to request SMF to execute the redeployment / rediscovery process of EAS.

[0367] Request message #1 may include EAS#1IP and EAS#2IP (as described in the first information above). The request message may also include information instructing the UE (as described in the second information above), and information instructing the services between the UE and EAS#1 (as described in the third information), etc., without limitation. For example, request message #1 may request the SMF to switch the UE's services from EAS#1 to EAS#2 (after the switch, EAS#1 will provide services for the UE's services, and a portion of the UE's service traffic will be diverted from EAS#1 to EAS#2, etc.), without limitation.

[0368] It is understandable that the UE's services are provided by EAS#1 before redeployment. EAS#1 can also be called the source EAS, and EAS#2 can also be called the target EAS. The AF can send request message #1 to the SMF through NEF and PCF.

[0369] S802, SMF determines the L-SMF#1 corresponding to EAS#1 based on the stored correspondence.

[0370] Based on the stored mapping between L-SMFs and EAS IPs (including EAS IP#1), the SMF can determine the L-SMF#1 corresponding to EAS IP#1 (also known as the source L-SMF), which can provide services for EAS IP#1. Since the SMF does not store the L-SMF corresponding to EAS#2 IP (the L-SMF providing services for EAS#2), the SMF can trigger the execution of step S803 below.

[0371] S803, SMF sends request message #2 to L-SMF#1. Correspondingly, L-SMF#1 receives request message #2 from SMF.

[0372] Request message #2 may include EAS#2IP, which is used to request L-SMF#1 to query the L-SMF corresponding to EAS#2.

[0373] In other words, if the SMF does not store the L-SMF corresponding to EAS#2IP, the SMF can query the L-SMF corresponding to EAS#2IP through L-SMF#1. That is, the discovery task of the target L-SMF (L-SMF#1) is offloaded to L-SMF#1.

[0374] S804, L-SMF#1 matches the L-SMF corresponding to EAS#2 based on the stored EDI.

[0375] If the EDI stored in L-SMF#1 includes EDI#2, then L-SMF#1 can determine that EAS#2 corresponds to L-SMF#1 / L-SMF#2. That is, L-SMF#1 and L-SMF#2 are the same, and L-SMF#1 can provide services for both EAS#1 and EAS#2. This L-SMF#1 can then execute subsequent S805.

[0376] If the EDI stored in L-SMF#1 does not include EDI#2, then L-SMF#1 can query other network functions, such as EASDF / NRF, for the L-SMF corresponding to EAS#2. EASDF / NRF stores the corresponding EDI for each L-SMF (e.g., L-SMF#2 corresponds to EDI#2), or in other words, it stores the mapping between L-SMFs and EAS IPs (including EAS IP#2). In this case, L-SMF#1 and L-SMF#2 are different. L-SMF#1 can then execute subsequent steps S806-S808.

[0377] S805, L-SMF#1 sends response message #1 to SMF. Correspondingly, SMF receives response message #1 from SMF.

[0378] The response message #1 may include information about the queried L-SMF#1, such as L-SMF#1IP.

[0379] Optionally, the response message #1 may also indicate that L-SMF#1 has successfully matched the L-SMF corresponding to EAS#2, etc., without limitation.

[0380] S806, L-SMF#1 sends request message #3 to EASDF / NRF. Correspondingly, L-SMF#2 receives request message #3 from the SMF.

[0381] Among them, request message #3 may include EAS#2IP, which is used to request L-SMF#2 to query the L-SMF corresponding to EAS#2.

[0382] EASDF / NRF can determine the L-SMF#2 corresponding to EAS#2 based on the stored correspondence.

[0383] S807, EASDF / NRF sends response message #2 to L-SMF#1. Correspondingly, L-SMF#1 receives response message #2 from EASDF / NRF.

[0384] The response message #2 may include information about the queried L-SMF#2, such as L-SMF#2IP.

[0385] Optionally, the response message #2 may also indicate that the EASDF / NRF has successfully matched the L-SMF corresponding to EAS#2, etc., without limitation.

[0386] S808, L-SMF#1 sends response message #3 to SMF. Correspondingly, SMF receives response message #3 from L-SMF#1.

[0387] L-SMF#1 can send response message #3 to the SMF based on the received response message #2. Response message #3 may include information retrieved from L-SMF#2, such as the L-SMF#2 IP address. It is understood that response message #2 and response message #3 can be the same (e.g., L-SMF#1 transmits them transparently) or different (e.g., L-SMF#1 processes them before sending), without limitation.

[0388] S809, the SMF sends indication information to L-SMF#1 and / or L-SMF#2. Correspondingly, L-SMF#1 and / or L-SMF#2 receive indication information from the SMF.

[0389] After the SMF determines that EAS#1 corresponds to L-SMF#1 and EAS#2 corresponds to L-SMF#2, the SMF can send instruction information to L-SMF#1 and / or L-SMF#2 according to request message #1, to instruct L-SMF#1 and / or L-SMF#2 to perform subsequent steps. For example, L-SMF#1 and / or L-SMF#2 can perform the switching, deletion, or addition of EAS; the switching, deletion, or addition of L-PSA. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated here.

[0390] S810, SMF stores the correspondence between L-SMF#2 and EAS#2IP.

[0391] In this way, when the SMF needs to discover or query the L-SMF that manages EAS#2, it can directly determine the L-SMF#2 based on the stored information without having to query through other network elements, which simplifies the process.

[0392] Scene 2: Figure 11 Flowchart of the communication method provided in the embodiments of this application Figure 11 This communication method mainly involves the interaction between the (central) SMF, L-SMF#1 (managing EAS#1), NEF, EASDF / NRF, and AF. In scenario 2, the SMF does not store the EDI of EAS#1 (denoted as EDI#1). In this case, the SMF can query the L-SMF corresponding to EAS#1 (denoted as L-SMF#1) through other network functions, such as NEF and EASDF / NRF. Thus, even if the SMF lacks EDI#1, it can discover the L-SMF#1 that manages EAS#1, thereby supporting communication between the UE and EAS#1 and improving communication efficiency. The NEF and EASDF / NRF store the corresponding EDI of each L-SMF (e.g., L-SMF#1 corresponds to EDI#1), or in other words, the EASDF / NRF stores the correspondence between L-SMF and EASIP (including EAS IP#1).

[0393] It is understandable that in scenario 2, each network element has already executed the PDU session establishment process. During this PDU session establishment process, the insertion of multiple L-SMFs has been completed, that is, the SMF establishes a connection with multiple L-SMFs. This process can be used as a pre-process for scenario 2, and its specific implementation can refer to existing implementations, which will not be elaborated here.

[0394] Based on this preliminary process, specifically, such as Figure 11 As shown, the flow of this communication method is as follows:

[0395] S901, AF sends request message #1 to SMF. Correspondingly, SMF receives request message #1 from AF.

[0396] The request message #1 may include EAS#1IP (as described in the first information above). The request message #1 may also include information indicating the UE (as described in the second information above), and information related to the service between the UE and EAS#1 (as described in the third information), etc., without limitation.

[0397] It is understandable that the specific implementation of this step can be referred to the relevant introduction in step S801 above, and will not be repeated here.

[0398] After receiving request message #1, the SMF needs to query the L-SMF corresponding to EAS#1. The following describes the process of the SMF querying the L-SMF corresponding to EAS#1 using three implementation examples.

[0399] Implementation 1: as follows, steps S902-S904; Implementation 2: as follows, steps S905-S907; Implementation 3: as follows, step S909.

[0400] S902, the SMF sends request message #2 to the EASDF / NRF. Correspondingly, the EASDF / NRF receives request message #2 from the SMF.

[0401] Request message #2 may include EAS#1IP, which is used to request EASDF / NRF to query the L-SMF corresponding to EAS#1.

[0402] EASDF / NRF can determine the correspondence between EAS#1 and L-SMF#1 based on the stored correspondence.

[0403] S903, EASDF / NRF sends response message #1 to SMF. Correspondingly, SMF receives response message #1 from EASDF / NRF.

[0404] The response message #1 may include information about the queried L-SMF#1, such as L-SMF#1IP.

[0405] Optionally, the response message #1 may also indicate that the EASDF / NRF has successfully matched the L-SMF corresponding to EAS#1, etc., without limitation.

[0406] S904, SMF determines that EAS#1 corresponds to L-SMF#1 based on response message #1.

[0407] SMF can determine the corresponding L-SMF#1 for EAS#1 based on the information in L-SMF#1.

[0408] S905, SMF sends request message #3 to NEF. Correspondingly, NEF receives request message #3 from SMF.

[0409] Among them, request message #3 can be used to request the EDI (including EDI #1) corresponding to each L-SMF of NEF storage.

[0410] S906, NEF sends response message #2 to SMF. Correspondingly, SMF receives response message #2 from NEF.

[0411] Response message #2 may include the EDI corresponding to each of the L-SMFs stored by the NEF. It can be understood that the NEF stores the EDI corresponding to L-SMF #1 (including EDI #1). That is, the NEF can send the stored EDI corresponding to each of the L-SMFs to the SMF via response message #2, based on request message #3.

[0412] S907, SMF determines that EAS#1 corresponds to L-SMF#1 based on response message #2.

[0413] SMF can determine the corresponding L-SMF#1 for EAS#1 based on the EDI of each L-SMF provided by NEF.

[0414] S908, the SMF sends an instruction message to L-SMF#1. Correspondingly, L-SMF#1 receives the instruction message from the SMF.

[0415] Based on Implementation 1 and Implementation 2 described above, after the SMF determines that EAS#1 corresponds to L-SMF#1, the SMF can send instruction information to L-SMF#1 according to request message #1 to instruct L-SMF#1 to perform subsequent steps. For example, L-SMF#1 can perform switching, deletion, or addition of EAS; switching, deletion, or addition of L-PSA, etc. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated further.

[0416] S909, the SMF sends request message #4 to the EASDF / NRF. Correspondingly, the EASDF / NRF receives the request from the SMF.

[0417] Among them, request message #4 may include EAS#1IP and request message #1, which is used to request EASDF / NRF to query the L-SMF corresponding to EAS#1.

[0418] EASDF / NRF can determine the correspondence between EAS#1 and L-SMF#1 based on the stored correspondence.

[0419] S910, EASDF / NRF sends request message #1 to L-SMF#1. Correspondingly, L-SMF#1 receives response message #1 from EASDF / NRF.

[0420] Based on implementation 3 above, after determining that EAS#1 corresponds to L-SMF#1, EASDF / NRF can directly forward request message #1 to L-SMF#1. L-SMF#1 can then execute subsequent steps based on this request message #1. For example, L-SMF#1 can perform switching, deletion, or addition of EAS; switching, deletion, or addition of L-PSA, etc. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated further.

[0421] Scene 3: Figure 5-10 Flowchart of the communication method provided in the embodiments of this application Figure 5-10 This communication method mainly involves the interaction between the (central) SMF, L-SMF#1 (managing EAS#1), PCF, NEF, UDR, and AF. In scenario 3, the SMF does not store the EDI of EAS#1 (denoted as EDI#1). In this case, the SMF can query the L-SMF corresponding to EAS#1 (denoted as L-SMF#1) through other network functions, such as NEF and UDR. Thus, even if the SMF lacks EDI#1, it can discover the L-SMF#1 that manages EAS#1, thereby supporting communication between the UE and EAS#1 and improving communication efficiency. The NEF and UDR store the corresponding EDI of each L-SMF (e.g., L-SMF#1 corresponds to EDI#1), or in other words, the EASDF / NRF stores the correspondence between L-SMF and EAS IP (including EAS IP#1).

[0422] It is understandable that in Scenario 3, each network element has already executed the PDU session establishment process. During this PDU session establishment process, the insertion of multiple L-SMFs has been completed, that is, the SMF establishes a connection with multiple L-SMFs. This process can be used as a pre-process for Scenario 3, and its specific implementation can refer to existing implementations, which will not be elaborated here. At the same time, the operator network configures rules on the PCF / NEF: when the PCF receives a request message from the AF (used to request the execution of the EAS redeployment / rediscovery process), the PCF can query the NEF for the L-SMF corresponding to the EAS based on the EAS identification information carried in the AF's request message.

[0423] Based on this pre-process and configured rules, specifically, such as Figure 12 As shown, the flow of this communication method is as follows:

[0424] S1001, AF sends request message #1 to PCF. Correspondingly, PCF receives request message #1 from AF.

[0425] The request message #1 may include EAS#1IP (as described in the first information above). The request message #1 may also include information indicating the UE (as described in the second information above), and information related to the service between the UE and EAS#1 (as described in the third information), etc., without limitation.

[0426] AF can send request message #1 to PCF via NEF.

[0427] It is understandable that the specific implementation of this step can be referred to the relevant introduction in step S801 above, and will not be repeated here.

[0428] S1002, PCF sends request message #2 to NEF. Correspondingly, NEF receives request message #2 from PCF.

[0429] Request message 2 may include EAS#1IP, which is used to request NEF to query the L-SMF corresponding to EAS#1.

[0430] For example, based on the configured rules, after receiving request message #1, PCF can request NEF to query the L-SMF corresponding to EAS#1.

[0431] S1003, NEF matches the L-SMF corresponding to EAS#1 based on the stored EDI.

[0432] If the EDI stored in NEF includes EDI#1, then NEF can determine that EAS#1 corresponds to L-SMF#1.

[0433] If the EDI stored by NEF does not include EDI#1, then NEF can obtain the L-SMF information corresponding to EAS#1 by querying the UDR. That is, NEF executes the subsequent steps S1004-S1005.

[0434] S1004, NEF sends request message #3 to UDR. Correspondingly, UDR receives request message #3 from NEF.

[0435] Among them, request message #3 may include EAS#1IP, which is used to request UDR to query the L-SMF corresponding to EAS#1.

[0436] UDR can determine the correspondence between EAS#1 and L-SMF#1 based on the storage correspondence.

[0437] S1005, UDR sends response message #1 to NEF. Correspondingly, NEF receives response message #1 from UDR.

[0438] The response message #1 may include information about the queried L-SMF#1, such as L-SMF#1 IP.

[0439] Optionally, the response message #1 may also indicate that the UDR has successfully matched the L-SMF corresponding to EAS #2, etc., without limitation.

[0440] S1006, NEF sends response message #2 to PCF. Correspondingly, PCF receives response message #1 from PCF.

[0441] Based on the received response message #1, NEF can send response message #2 to SMF. Response message #2 may include information about L-SMF #1, such as L-SMF #1 IP address. It is understood that response message #1 and response message #2 can be the same (e.g., NEF transmits them directly) or different (e.g., NEF processes them before sending), without limitation.

[0442] Based on the steps S1002-S1005 above, NEF can determine that EAS#1 corresponds to L-SMF#1. Subsequently, PCF can forward the L-SMF#1 IP and request message #1 to SMF (as described in step S1007 below); or, PCF can directly forward request message #1 to L-SMF#1 (as described in step S1009 below), which will be explained in detail below.

[0443] S1007, the PCF sends L-SMF#1IP and request message #1 to the SMF. Correspondingly, the SMF receives L-SMF#1IP and request message #1 from the PCF.

[0444] It is understandable that PCF can also process or map request message #1 before sending it to SMF, without any restrictions.

[0445] S1008, the SMF sends an instruction message to L-SMF#1. Correspondingly, L-SMF#1 receives the instruction message from the SMF.

[0446] After the SMF determines that EAS#1 corresponds to L-SMF#1 based on L-SMF#1IP, the SMF can send instruction information to L-SMF#1 according to request message #1 to instruct L-SMF#1 to perform subsequent steps. For example, L-SMF#1 can perform switching, deletion, or addition of EAS; switching, deletion, or addition of L-PSA, etc. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated further.

[0447] S1009, PCF sends request message #1 to L-SMF#1. Correspondingly, L-SMF#1 receives request message #1 from PCF.

[0448] In other words, after the PCF determines that EAS#1 IP corresponds to L-SMF#1, it can directly forward request message #1 to L-SMF#1. L-SMF#1 can then perform subsequent steps based on this request message #1. For example, L-SMF#1 can perform switching, deletion, or addition of EAS; switching, deletion, or addition of L-PSA, etc. The implementation of these subsequent steps can refer to existing technologies and will not be elaborated further.

[0449] It is understandable that PCF can also process or map request message #1 before sending it to L-SMF #1, without limitation.

[0450] The above combination Figure 2 The communication method provided in the embodiments of this application is described in detail below. Figure 12 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0451] Figure 12 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 5-10 For example, such as Figure 12 As shown, the communication device 1100 includes a transceiver module 1101 and a processing module 1102. For ease of explanation, Figure 12 Only the main components of the communication device 1100 are shown.

[0452] The transceiver module 1101 is used to perform the above-mentioned tasks. Figure 12 The sending and receiving functions of the method shown are executed by the processing module 1102. Figure 12 The method shown includes functions other than sending and receiving.

[0453] Optionally, the transceiver module 1101 may include a transmitting module ( Figure 12 (not shown in the image) and receiving module ( Figure 12 (Not shown in the diagram). The transmitting module is used to implement the transmitting function of the communication device 1100, and the receiving module is used to implement the receiving function of the communication device 1100.

[0454] Optionally, the communication device 1100 may also include a storage module. ​ (Not shown in the image), the storage module stores programs or instructions. When the processing module 1102 executes the program or instructions, the communication device 1100 can perform the above-described method. ​ The methods shown describe the functions of terminals and / or network devices (such as access and mobility management network elements).

[0455] It is understood that the communication device 1100 may be a network device, or a chip (system) or other component or assembly that can be set in the network device, or a device that includes the network device. This application embodiment does not limit this.

[0456] In addition, the technical effects of the communication device 1100 can be referenced. ​ The technical effects of the communication method shown will not be elaborated here.

[0457] For example, ​ Schematic diagram of the communication device provided in the embodiments of this application ​ The communication device can be a terminal device or a network device, or it can be a chip (system) or other component or assembly of the terminal device or network device. For example... ​ As shown, the communication device 1200 may include a processor 1201. Optionally, the communication device 1200 may also include a memory 1202 and / or a transceiver 1203. The processor 1201 is coupled to the memory 1202 and the transceiver 1203, for example, they may be connected via a communication bus.

[0458] The following is combined ​ A detailed description of each component of the communication device 1200 is provided below:

[0459] The processor 1201 is the control center of the communication device 1200. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1201 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0460] Optionally, the processor 1201 can perform various functions of the communication device 1200, such as the functions described above, by running or executing software programs stored in the memory 1202 and calling data stored in the memory 1202. ​ The communication method shown.

[0461] In a specific implementation, as one example, the processor 1201 may include one or more CPUs, for example... ​ CPU0 and CPU1 are shown in the diagram.

[0462] In a specific implementation, as one example, the communication device 1200 may also include multiple processors, for example... ​ The processors 1201 and 1204 are shown. Each of these processors can be a single-core processor (CPU) or a multi-core processor (CPU). Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0463] The memory 1202 is used to store the software program that executes the solution of this application, and is controlled by the processor 1201 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0464] Optionally, the memory 1202 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1202 may be integrated with the processor 1201 or exist independently, and may be connected via the interface circuit of the communication device 1200. ​ (Not shown in the image) is coupled to the processor 1201, and this embodiment does not specifically limit this.

[0465] Transceiver 1203 is used for communication with other communication devices. For example, if communication device 1200 is a terminal device, transceiver 1203 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1200 is a network device, transceiver 1203 can be used to communicate with a terminal device or with another network device.

[0466] Optionally, transceiver 1203 may include a receiver and a transmitter. ​ (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0467] Optionally, the transceiver 1203 can be integrated with the processor 1201, or it can exist independently and be connected via the interface circuit of the communication device 1200. ​ (Not shown in the image) is coupled to the processor 1201, and this embodiment does not specifically limit this.

[0468] It should be noted that, ​ The structure of the communication device 1200 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0469] Furthermore, the technical effects of the communication device 1200 can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0470] This application provides a communication system. The communication system may include the terminal device and network device described in the above method embodiments.

[0471] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0472] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0473] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0474] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0475] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0476] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0477] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0478] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0479] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0480] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0481] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0482] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0483] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The first network element receives a first request message; wherein the first request message includes first information, second information and third information; the first information is used to identify the edge application server, the second information is used to indicate the terminal device; and the third information is used to indicate the relevant information of the service between the terminal device and the edge application server. The first network element queries the second network element for the local session management function network element corresponding to the edge application server of the first information identifier; Based on the query results, the first network element sends the information of the local session management function network element to the third network element, or the first network element sends the information of the edge application server to the local session management function network element.

2. The method according to claim 1, characterized in that, The first request message is used to request the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server, and the third information is used to indicate relevant information about the service between the terminal device and the edge application server, including: the third information is used to indicate relevant information about the service between the terminal device and the source edge application server.

3. The method according to claim 1, characterized in that, The first request message is used to request the rediscovery of the edge application server.

4. The method according to any one of claims 1-3, characterized in that, The first network element queries the second network element for the local session management function network element corresponding to the edge application server of the first information identifier, including: The first network element sends a second request message to the second network element; wherein, the second request message is used to request a query of the local session management function network element corresponding to the edge application server of the first information identifier; The first network element receives information from the local session management function network element of the second network element.

5. The method according to any one of claims 1-4, characterized in that, The second network element is used to store the correspondence between the local session management function network element and the edge application server, and the edge application server includes the edge application server identified by the first information.

6. The method according to any one of claims 1-4, characterized in that, The second network element is used to query the data storage network element for the local session management function network element corresponding to the edge application server identified by the first information identifier.

7. The method according to any one of claims 1-6, characterized in that, The first network element sends information about the local session management function network element to the third network element, including: The first network element sends a first message to the third network element; wherein, the first message includes information of the local session management function network element, the first information, the second information, and the third information.

8. The method according to any one of claims 1-7, characterized in that, The first network element is a policy control function network element; the second network element is at least one of the following: an edge application server discovery function network element, a network open function network element, or a network storage function network element; the third network element is a session management function network element of the terminal device.

9. The method according to any one of claims 1-6, characterized in that, The first network element sends information about the edge application server to the local session management function network element, including: The first network element sends a second message to the local session management function network element; wherein, the second message includes information about the edge application server, the second information, and the third information.

10. The method according to any one of claims 1-6 or 9, characterized in that, The first network element is the session management function network element of the terminal device; the second network element is at least one of the following: edge application server discovery function network element, network opening function network element, or network storage function network element.

11. The method according to any one of claims 1-10, characterized in that, The local session management function network element is used to determine the local protocol data unit session anchor point, which is located on the service transmission path between the terminal device and the edge application server.

12. A communication method, characterized in that, include: The first network element receives a first message from the session management function network element; wherein, the first message includes a first request message and first information, the first information being used to identify the edge application server; the first request message includes the first information, second information and third information, the second information being used to indicate the terminal device, and the third information being used to indicate the relevant information of the service between the terminal device and the edge application server; The first network element queries the local session management function network element corresponding to the edge application server identified by the first information based on the stored correspondence between local session management function network elements and edge application servers. The first network element sends the first request message to the local session management function network element.

13. The method according to claim 12, characterized in that, The first request message is used to request the redeployment of the edge application server; the edge application server includes a source edge application server and a target edge application server, and the third information is used to indicate relevant information about the service between the terminal device and the edge application server, including: the third information is used to indicate relevant information about the service between the terminal device and the source edge application server.

14. The method according to claim 12, characterized in that, The first request message is used to request the rediscovery of the edge application server.

15. The method according to any one of claims 12-14, characterized in that, The first network element is at least one of the following: an edge application server discovery function network element, a network opening function network element, or a network storage function network element.

16. The method according to any one of claims 12-15, characterized in that, The local session management function network element is used to determine the local protocol data unit session anchor point, which is located on the service transmission path between the terminal device and the edge application server.

17. A communication method, characterized in that, include: The first network element obtains a first request message; wherein the first request message includes first information, second information, and third information; the first information is used to identify the source edge application server and the target edge application server associated with the terminal device; the second information is used to indicate the terminal device; and the third information is used to indicate relevant information about the service between the terminal device and the source edge application server. The first network element determines the first local session management function network element corresponding to the source edge application server and the second local session management function network element corresponding to the target edge application server; wherein, the first local session management function network element is determined by the session management function network element according to the stored correspondence between local session management function network elements and edge application servers, and the second local session management function network element is queried by the session management function network element through the first local session management function network element.

18. The method according to claim 17, characterized in that, The method further includes: The first network element determines the first local session management function network element based on the stored information, but does not store information about the local session management function network element corresponding to the target edge application server.

19. The method according to claim 18, characterized in that, After the first network element determines the first local session management function network element based on the stored information, and no information about the local session management function network element corresponding to the target edge application server is stored, the method further includes: The first network element sends a second request message to the first local session management function network element; wherein, the second request message is used to request a query of the local session management function network element corresponding to the target edge application server; The first network element receives a second response message from the first local session management function network element; wherein the second response message includes information from the second local session management function network element.

20. The method according to claim 19, characterized in that, The first local session management function network element is used to store information of one or more edge application servers corresponding to the first local session management function network element, the one or more edge application servers including the target edge application server, and the first local session management function network element is determined to be the second local session management function network element corresponding to the target edge application server.

21. The method according to claim 20, characterized in that, The first request message is used to request the first network element to perform a redeployment of the edge application server; the method further includes: The first network element sends an instruction message to the first local session management function network element according to the first request message; wherein, the instruction message is used to instruct the first local session management function network element to modify the local protocol data unit session anchor point, and the modified local protocol data unit session anchor point is on the transmission path of the service between the terminal device and the target edge application server.

22. The method according to claim 19, characterized in that, The first local session management function network element is used to store information of one or more edge application servers corresponding to the first local session management function network element, wherein the one or more edge application servers do not include the target edge application server; The first network element receives a second response message from the first local session management function network element, including: The first network element receives the second response message from the second network element through the first local session management function network element; wherein the first local session management function network element and the second local session management function network element are different.

23. The method according to claim 22, characterized in that, The second network element is at least one of the following: an edge application server discovery function network element, a network opening function network element, or a network storage function network element.

24. The method according to claim 22 or 23, characterized in that, The second local session management function network element is determined by the second network element.

25. The method according to any one of claims 22-24, characterized in that, The first request message is used to request the first network element to perform a redeployment of the edge application server, and the method further includes: The first network element sends an instruction message to the second local session management function network element according to the first request message; wherein, the instruction message is used to instruct the second local session management function network element to modify the local protocol data unit session anchor point, and the modified local protocol data unit session anchor point is on the transmission path of the service between the terminal device and the target edge application server.

26. The method according to any one of claims 17-25, characterized in that, The method further includes: The first network element updates the deployment information of the application server stored therein; wherein, the updated deployment information of the application server includes the correspondence between the second local session management function network element and the target edge application server.

27. The method according to any one of claims 17-26, characterized in that, The first network element is the session management function network element of the terminal device.

28. A communication device, characterized in that, The apparatus includes a module for performing the method as described in any one of claims 1-27.

29. A communication device, characterized in that, include: A processor for executing a computer program to cause the communication device to perform the method as described in any one of claims 1-27.

30. A communication chip, characterized in that, It stores a computer program or instructions that, when the chip is run on a communication device, cause the method as described in any one of claims 1-27 to be implemented.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1-27.

32. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1-27.

Images