Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. The communication method comprises: receiving a first message from a first local SMF network element, wherein the first message comprises the address of a first EAS, and the address of the first EAS does not fall within the range of first EAS deployment information (EDI) of the first local SMF network element; determining whether a second partial EDI of a second EDI of a central SMF comprises the address of the first EAS; and if the second partial EDI comprises the address of the first EAS, sending a first DNAI corresponding to the address of the first EAS to an NRF network element, wherein the first DNAI is used for determining a second local SMF network element, and the second local SMF network element is configured to determine an L-PSA for accessing the first EAS. In this way, failures in the EAS discovery process can be effectively addressed.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application with application number 202410418442.1 filed with the State Intellectual Property Office of China on April 8, 2024, and priority to the Chinese patent application with the invention name “Communication Method and Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a communication method and device. Background Art

[0003] In some communication systems, for example, in the fifth generation (5 th In 5G (5G) generation communication systems, edge application servers (EASs) in edge computing (EC) can be discovered using domain name system (DNS) technology. An edge application server discovery function (EASDF) network element is introduced into edge computing. The EASDF network element receives DNS message processing rules from the session management function (SMF) network element, processes the DNS messages according to the processing rules, and exchanges information between the SMF network element, the EASDF network element, and the DNS server to determine the EAS closest to the user equipment (UE).

[0004] Since the SMF network element is responsible for the EAS discovery process within its service range, in order to reduce the load on the SMF network element, the session rule granularity of the EASDF network element is configured separately through the local SMF (L-SMF) network element and the SMF network element. However, since the DNS server needs to comprehensively consider factors such as the load of different EASs when determining the target EAS, this may result in the target EAS obtained by the EASDF network element from the DNS server not being within the service range of the L-SMF network element, making it impossible for the L-SMF to identify the target EAS, ultimately causing the EAS discovery process to fail.

[0005] Therefore, how to deal with the situation where the EAS discovery process fails is an urgent problem to be solved. Summary of the Invention

[0006] The application provides a communication method and device, which can effectively deal with the situation that the EAS discovery process fails.

[0007] In a first aspect, a communication method is provided, which includes: a first local session management function (SMF) network element receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request including an address of a first edge application server (EAS). When the address of the first EAS is not within a range of first EAS deployment information of the first local SMF network element, the first local SMF network element sends a first message to a central SMF network element, the first message including the address of the first EAS. If a second part of second EAS deployment information (EDI) of the central SMF network element includes the address of the first EAS, the central SMF network element sends a first data network access identifier (DNAI) corresponding to the address of the first EAS to a network repository function (NRF) network element. The NRF network element determines a second local SMF network element corresponding to the first DNAI, and the second local SMF network element is used to determine a local protocol data unit session anchor point (L-PSA) for accessing the first EAS.

[0008] In the above technical solution, when the first local SMF network element cannot identify the address of the first EAS, the central SMF network element and the NRF network element can be used to determine a second local SMF network element that can identify the address of the first EAS, so that the second local SMF network element can complete the EAS discovery process in the future, thereby avoiding the situation that the EAS discovery process fails due to the first local SMF network element being unable to identify the address of the first EAS, and improving the success rate of discovering the EAS.

[0009] In the above technical solution, when the first local SMF network element cannot identify the address of the first EAS, the central SMF network element and the NRF network element can be used to determine a second local SMF network element that can identify the address of the first EAS, so that the second local SMF network element can complete the EAS discovery process in the future, thereby avoiding the situation that the EAS discovery process fails due to the first local SMF network element being unable to identify the address of the first EAS, and improving the success rate of discovering the EAS.

[0010] In combination with the first aspect, in some implementations of the first aspect, before the central SMF network element sends the first data network access identifier (DNAI) corresponding to the address of the first edge application server (EAS) to the network repository function (NRF) network element, the method further includes: the central SMF network element determining whether the second part of the second EAS deployment information (EDI) of the central SMF network element includes the address of the first EAS.

[0011] In combination with the first aspect, in some implementations of the first aspect, the first message further includes first indication information, and the first indication information is used to indicate whether the central SMF network element determines whether the second part of the second EAS deployment information (EDI) of the central SMF network element includes the address of the first EAS.

[0012] In this way, the displayed indication information can more directly indicate whether the second part EDI of the second EAS deployment information EDI of the central SMF network element determines the address of the first EAS.

[0013] With reference to the first aspect, in some implementations of the first aspect, the central SMF network element sending, to a network storage function NRF network element, a first data network access identifier DNAI corresponding to the address of the first EAS comprises: the central SMF network element sending, to the network storage function NRF network element, the first DNAI through an access and mobility management function AMF network element.

[0014] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: the NRF network element sending, to the AMF network element, the address of the second local SMF network element. The AMF network element sending, to the second local SMF network element, the related information of the session management, the related information of the session management comprising the address of the central SMF network element, and / or the address of the first local SMF.

[0015] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: the NRF network element sending, to the central SMF network element, the address of the second local SMF network element. The central SMF network element sending, to the second local SMF network element, the related information of the session management, the related information of the session management comprising the address of the central SMF network element, and / or the address of the first local SMF.

[0016] In the above technical solution, the second local SMF obtains the related information of the session management, which can help the second local SMF more conveniently obtain the first EAS, thereby helping to complete the EAS discovery process.

[0017] With reference to the first aspect, in some implementations of the first aspect, the method further comprises: the second local SMF network element obtaining the address of the first EAS. The second local SMF network element determining a local protocol data unit session anchor L-PSA accessing the first EAS.

[0018] With reference to the first aspect, in some implementations of the first aspect, the DNS context notification request further comprises identification information of the DNS response message, the first message further comprising the identification information, and the method further comprises: the central SMF network element notifying the EAS DF network element of a DNS message processing rule, the updated DNS message processing rule being used to instruct the EAS DF network element to send the cached DNS response message to the UE, and the updated DNS message processing rule comprising the identification information.

[0019] With reference to the first aspect, in some implementations of the first aspect, the central SMF network element notifying the EAS DF network element to update the DNS message processing rule comprises: the central SMF network element sending, to the EAS DF, the updated DNS message processing rule.

[0020] In some implementations of the first aspect, the center SMF network element informs the EAS DF network element of the DNS message processing rule, including: the center SMF network element sending a second message to the first local SMF network element, the second message including identification information. The first local SMF network element generates and sends an updated DNS message processing rule to the EAS DF network element.

[0021] In some implementations of the first aspect, the second message further includes second indication information, the second indication information being used to instruct the first local SMF network element to send the updated DNS message processing rule to the EAS DF network element.

[0022] In the above technical solution, the EAS DF is informed to update the DNS message processing rule, and then the EAS DF is instructed to forward the cached DNS response message to the user equipment, thereby completing the EAS discovery process.

[0023] In some implementations of the first aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The second EAS deployment information includes a second part of EDI and a first part of EDI. The first part of EDI is EAS deployment information corresponding to an edge computing service supported by the center SMF network element. The second part of EDI includes a DNAI corresponding to a local SMF network element maintained by the center SMF network element, an address range of the EAS, and an association relationship between the DNAI and the address range of the EAS.

[0024] In some implementations of the first aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The second EAS deployment information includes a second part of EDI and a first part of EDI. The first part of EDI is EAS deployment information corresponding to an edge computing service supported by the center SMF network element. The second part of EDI includes a DNAI corresponding to a local SMF network element maintained by the center SMF network element, an address range of the EAS, and an association relationship between the DNAI and the address range of the EAS.

[0025] In the technical solution, after the central SMF network element receives the address of the first EAS from the first local SMF network element, if the second part of the second EDI of the central SMF network element includes the address of the first EAS, the central SMF network element can determine the second local SMF network element corresponding to the address of the first EAS by sending the first DNAI corresponding to the address of the first EAS to the NRF network element, so as to complete the discovery process of the EAS by the second local SMF in the future, thereby avoiding the situation that the discovery process of the EAS fails due to the fact that the first local SMF network element cannot identify the address of the first EAS, and improving the success rate of discovering the EAS.

[0026] With reference to the second aspect, in some implementations of the second aspect, before sending the first data network access identifier (DNAI) corresponding to the address of the first EAS to the network repository function (NRF) network element, the method further includes: determining whether the second part of the second EAS deployment information (EDI) of the central SMF includes the address of the first EAS.

[0027] With reference to the second aspect, in some implementations of the second aspect, the first message further includes first indication information, and the first indication information is used to indicate whether the central SMF network element determines whether the second part of the second EAS deployment information (EDI) of the central SMF includes the address of the first EAS.

[0028] With reference to the second aspect, in some implementations of the second aspect, sending the first data network access identifier (DNAI) corresponding to the address of the first EAS to the network repository function (NRF) network element includes: sending the first DNAI to the network repository function (NRF) network element through an access and mobility management function (AMF) network element.

[0029] With reference to the second aspect, in some implementations of the second aspect, the method further includes: receiving the address of the second local SMF from the NRF network element. Sending, to the second local SMF network element, session management related information, wherein the session management related information includes the address of the central SMF network element and / or the address of the first local SMF network element.

[0030] With reference to the second aspect, in some implementations of the second aspect, the method further includes: receiving a first request message from the second local SMF network element, wherein the first request message is used to request edge computing related information. Sending, to the second local SMF network element, the address of the first EAS.

[0031] With reference to the second aspect, in some implementations of the second aspect, the first message further includes the identification information, and the method further includes: notifying an edge application server discovery function, EASDF, network element to update a DNS message processing rule, wherein the updated DNS message processing rule is used to instruct the EASDF network element to send the cached DNS response message to the UE, and the updated DNS message processing rule includes the identification information.

[0032] With reference to the second aspect, in some implementations of the second aspect, notifying the edge application server discovery function, EASDF, network element to update the DNS message processing rule includes: sending, by the central SMF network element, the updated DNS message processing rule to the EASDF.

[0033] With reference to the second aspect, in some implementations of the second aspect, notifying the edge application server discovery function, EASDF, network element to update the DNS message processing rule includes: sending, to the first local SMF network element, a second message, wherein the second message includes the identification information, and the identification information is used to instruct the first local SMF network element to generate and send, to the EASDF network element, the updated DNS message processing rule.

[0034] With reference to the second aspect, in some implementations of the second aspect, the second message further includes second indication information, and the second indication information is used to instruct the first local SMF network element to generate and send, to the EASDF network element, the updated DNS message processing rule.

[0035] With reference to the second aspect, in some implementations of the second aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The second EAS deployment information includes a second part EDI and a first part EDI, the first part EDI is EAS deployment information corresponding to an edge computing service supported by the central SMF network element, and the second part EDI includes a DNAI corresponding to a local SMF network element maintained by the central SMF network element, an address range of an EAS, and an association relationship between the DNAI and the address range of the EAS.

[0036] According to a third aspect, a communication method is provided, which is applied to a first local session management function SMF network element, comprising: receiving a domain name system DNS context notification request from an edge application server discovery function EASDF network element, the DNS context notification request including the address of a first edge application server EAS. Determine whether the address of the first EAS falls within the scope of the first EAS deployment information of the first local SMF network element. If the address of the first EAS does not fall within the scope of the first EAS deployment information of the first local SMF network element, send a first message to the central SMF network element, the first message including the address of the first EAS, the address of the first EAS is used to instruct the central SMF network element to determine whether the second part EDI of the second EAS deployment information EDI of the central SMF includes the address of the first EAS, the first data network access identifier DNAI corresponding to the first EAS is used to determine the second local SMF network element, and the second local SMF network element is used to determine the local protocol data unit session anchor L-PSA for accessing the first EAS.

[0037] Among them, the address of the first EAS does not belong to the first EDI of the first local SMF network element, which can be understood as the first local SMF network element cannot recognize the address of the first EAS.

[0038] In the above technical solution, if the first local SMF network element cannot recognize the address of the first EAS, the first local SMF network element can send the address of the first EAS to the central SMF network element, which will help the subsequent central SMF network element to determine whether the second part of the EDI includes the address of the first EAS, and then help to subsequently determine the second local SMF corresponding to the address of the first EAS, so that the subsequent second local SMF can complete the EAS discovery process, thereby avoiding the failure of the EAS process discovery due to the inability of the first local SMF network element to recognize the address of the first EAS, thereby improving the success rate of discovering the EAS.

[0039] In combination with the third aspect, in certain implementations of the third aspect, the first message further includes first indication information, and the first indication information is used to indicate whether the second part EDI of the second EAS deployment information EDI of the central SMF includes the address of the first EAS.

[0040] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: receiving a first request message from a second local SMF network element, the first request message being used to request relevant information about edge computing, the second local SMF network element being used to maintain the first EAS. Sending an address of the first EAS to the second local SMF network element.

[0041] In conjunction with the third aspect, in certain implementations of the third aspect, the DNS context notification request further includes identification information of the DNS response message, the first message further includes the identification information, and the method further includes: receiving a second message from a central SMF network element, the second message including the identification information of the DNS response message. Generating and sending an updated DNS message processing rule to the EASDF network element, the updated DNS message processing rule being used to instruct the EASDF network element to send a cached DNS response message to the UE, the updated DNS message processing rule including the identification information.

[0042] In combination with the third aspect, in certain implementations of the third aspect, the second message also includes second indication information, and the second indication information is used to instruct the first local SMF network element to generate and send updated DNS message processing rules to the EASDF network element.

[0043] In a fourth aspect, a communication method is provided, applied to a second local session management function (SMF) network element, comprising: obtaining an address of a first edge application server (EAS), where the address of the first EAS does not belong to first EAS deployment information of the first local SMF network element; and determining a local protocol data unit session anchor (L-PSA) for accessing the first EAS.

[0044] Among them, the address of the first EAS does not belong to the first EDI of the first local SMF network element, which can be understood as the first local SMF network element cannot recognize the address of the first EAS.

[0045] In the above technical solution, the L-PSA accessing the first EAS is determined by the second local SMF network element, and the second local SMF completes the EAS discovery process, thereby avoiding the failure of the EAS process discovery caused by the first local SMF network element being unable to identify the address of the first EAS, thereby improving the success rate of discovering EAS.

[0046] In conjunction with the fourth aspect, in some implementations of the fourth aspect, obtaining the address of the first edge application server EAS includes: sending a first request message to a central SMF network element, the first request message being used to request relevant information about edge computing. Receiving a first response message from the central SMF network element, the first response message including the address of the first EAS.

[0047] In conjunction with the fourth aspect, in some implementations of the fourth aspect, obtaining the address of the first edge application server EAS includes: sending a first request message to a first local SMF network element, where the first request message is used to request relevant information about edge computing. Receiving a first response message from the first local SMF network element, where the first response message includes the address of the first EAS.

[0048] In combination with the fourth aspect, in some implementations of the fourth aspect, before obtaining the address of the first edge application server EAS, the method further comprises: receiving session management related information from a mobility management function AMF network element; or, receiving session management related information from a central SMF network element, the session management related information comprising an address of the central SMF network element, and / or an address of the first local SMF.

[0049] In combination with the fourth aspect, in some implementations of the fourth aspect, before obtaining the address of the first edge application server EAS, the method further comprises: receiving session management related information from a mobility management function AMF network element; or, receiving session management related information from a central SMF network element, the session management related information comprising an address of the central SMF network element, and / or an address of the first local SMF.

[0050] In combination with the fourth aspect, in some implementations of the fourth aspect, before obtaining the address of the first edge application server EAS, the method further comprises: receiving session management related information from a mobility management function AMF network element; or, receiving session management related information from a central SMF network element, the session management related information comprising an address of the central SMF network element, and / or an address of the first local SMF.

[0051] In the above technical solution, the second local SMF network element that can identify the address of the first EAS is determined directly through the central SMF network element and the NRF network element, so that the second local SMF can complete the EAS discovery process subsequently, directly avoiding the situation that the first local SMF cannot identify the first EAS, that is, directly avoiding the situation that the address of the first EAS is not included in the first EDI of the first local SMF, thereby improving the success rate of discovering the EAS.

[0052] In combination with the fourth aspect, in some implementations of the fourth aspect, before obtaining the address of the first edge application server EAS, the method further comprises: receiving session management related information from a mobility management function AMF network element; or, receiving session management related information from a central SMF network element, the session management related information comprising an address of the central SMF network element, and / or an address of the first local SMF.

[0053] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the DNS context notification request further includes first indication information, the first indication information being used to indicate whether the second part of the second EAS deployment information EDI of the central SMF network element includes the address of the first EAS.

[0054] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the sending, by the central SMF network element, of the first data network access identifier DNAI to the network repository function NRF network element includes: sending, by the central SMF network element, the first DNAI to the network repository function NRF network element through an access and mobility management function AMF network element.

[0055] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the method further includes: sending, by the NRF network element, the address of the second local SMF network element to the AMF network element. Sending, by the AMF network element, the session management related information to the second local SMF network element, the session management related information including the address of the central SMF network element.

[0056] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the method further includes: sending, by the NRF network element, the address of the second local SMF network element to the central SMF network element. Sending, by the central SMF network element, the session management related information to the second local SMF network element, the session management related information including the address of the central SMF network element.

[0057] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the method further includes: obtaining, by the second local SMF network element, the address of the first EAS. Determining, by the second local SMF network element, a local protocol data unit session anchor L-PSA that accesses the first EAS.

[0058] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the DNS context notification request further includes identification information of the DNS response message, and the method further includes: notifying, by the central SMF network element, the EAS DF network element to update the DNS message processing rule, the updated DNS message processing rule being used to instruct the EAS DF network element to send the cached DNS response message to the UE, and the updated DNS message processing rule including the identification information.

[0059] In some implementations of the fifth aspect, in conjunction with the fifth aspect, the notifying, by the central SMF network element, of the EAS DF network element to update the DNS message processing rule includes: sending, by the central SMF network element, the updated DNS message processing rule to the EAS DF.

[0060] In a fifth aspect, in some implementations of the fifth aspect, the center SMF network element notifying the EAS DF network element to update the DNS message processing rule includes: the center SMF network element sending a second message to the first local SMF network element, the second message including the identification information. The first local SMF network element generates and sends the updated DNS message processing rule to the EAS DF network element.

[0061] In a fifth aspect, in some implementations of the fifth aspect, the second message further includes second indication information, the second indication information being used to instruct the first local SMF network element to send the updated DNS message processing rule to the EAS DF network element.

[0062] In a fifth aspect, in some implementations of the fifth aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element; the center SMF network element includes second EAS deployment information, the second EAS deployment information including: EAS deployment information corresponding to an edge computing service supported by the center SMF network element, and a DNAI and an EAS address range corresponding to the local SMF network element.

[0063] In a sixth aspect, a communication method applied to a center session management function (SMF) network element is provided, including: receiving a domain name system (DNS) context notification request from an edge application server discovery function (EAS DF) network element, the DNS context notification request including an address of a first edge application server (EAS), the center SMF network element being a notification endpoint for a DNS response message configured by a first local SMF network element to the EAS DF network element. If a second part of a second EAS deployment information (EDI) of the center SMF network element includes the address of the first EAS, a first data network access identifier (DNAI) corresponding to the address of the first EAS is sent to a network repository function (NRF) network element, the first DNAI being used to determine a second local SMF network element, the second local SMF network element being used to determine a local protocol data unit session anchor (L-PSA) that accesses the first EAS.

[0064] In the above technical solution, the center SMF network element directly receives the address of the first EAS from the EAS DF network element, and if the center SMF network element can recognize the address of the first EAS, the address of the first EAS can be used to further determine the second local SMF network element, so that the second local SMF network element can complete the discovery process of the EAS in the future, directly avoiding the situation that the first local SMF network element cannot recognize the first EAS, that is, directly avoiding the situation that the first EDI of the first local SMF network element does not include the address of the first EAS, thereby improving the success rate of discovering the EAS.

[0065] In the above technical solution, the center SMF network element directly receives the address of the first EAS from the EAS DF network element, and if the center SMF network element can recognize the address of the first EAS, the address of the first EAS can be used to further determine the second local SMF network element, so that the second local SMF network element can complete the discovery process of the EAS in the future, directly avoiding the situation that the first local SMF network element cannot recognize the first EAS, that is, directly avoiding the situation that the first EDI of the first local SMF network element does not include the address of the first EAS, thereby improving the success rate of discovering the EAS.

[0066] With reference to the sixth aspect, in some implementations of the sixth aspect, before sending, to a network repository function, NRF, network element, a first data network access identifier, DNAI, corresponding to the address of the first EAS, if the second part of the second EAS deployment information, EDI, of the central SMF network element includes the address of the first EAS, the method further includes determining whether the second part of the EDI includes the address of the first EAS.

[0067] With reference to the sixth aspect, in some implementations of the sixth aspect, the DNS context notification request further includes first indication information, the first indication information being used to indicate whether the central SMF network element determines whether the second part of the second EAS deployment information, EDI, of the central SMF network element includes the address of the first EAS.

[0068] With reference to the sixth aspect, in some implementations of the sixth aspect, sending, to a network repository function, NRF, network element, a first data network access identifier, DNAI, corresponding to the address of the first EAS includes sending, by an access and mobility management function, AMF, network element, the first DNAI to the NRF network element.

[0069] With reference to the sixth aspect, in some implementations of the sixth aspect, the method further includes receiving an address of a second local SMF from the NRF network element. Sending, to the second local SMF network element, information related to session management includes an address of the central SMF network element.

[0070] With reference to the sixth aspect, in some implementations of the sixth aspect, the method further includes receiving a first request message from the second local SMF network element, the first request message being used to request information related to edge computing. Sending, to the second local SMF network element, the address of the first EAS.

[0071] With reference to the sixth aspect, in some implementations of the sixth aspect, the DNS context notification request further includes identification information of the DNS response message, and the method further includes notifying an edge application server discovery function, EASDF, network element to update a DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF network element to send, to the UE, the cached DNS response message, the updated DNS message processing rule including the identification information.

[0072] With reference to the sixth aspect, in some implementations of the sixth aspect, the central SMF network element notifying the EASDF network element to update the DNS message processing rule includes the central SMF network element sending, to the EASDF network element, the updated DNS message processing rule.

[0073] In a sixth aspect, in some implementations of the sixth aspect, the notifying the edge application server discovery function (EASDF) network element to update the DNS message processing rule includes sending a second message to the first local SMF network element, the second message including the identification information, the identification information indicating the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0074] In a sixth aspect, in some implementations of the sixth aspect, the second message further includes second indication information, the second indication information indicating the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0075] In a sixth aspect, in some implementations of the sixth aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The central SMF network element includes second EAS deployment information, the second EAS deployment information including: EAS deployment information corresponding to an edge computing service supported by the central SMF network element, and a DNAI and an EAS address range corresponding to the local SMF network element.

[0076] In a seventh aspect, a communication method is provided. The method includes a first local session management function (SMF) network element receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request including an address of a first edge application server (EAS), identification information of a DNS response message, and a fully qualified domain name (FQDN). When the address of the first EAS is not within a first EAS deployment information of the first local SMF network element, the first local SMF network element sends a third message to a central SMF network element, the third message including the identification information. The central SMF network element notifies the EASDF network element to update a DNS message processing rule, the updated DNS message processing rule indicating the EASDF network element to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message, the updated DNS message processing rule including the identification information.

[0077] In a seventh aspect, a communication method is provided. The method includes a first local session management function (SMF) network element receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request including an address of a first edge application server (EAS), identification information of a DNS response message, and a fully qualified domain name (FQDN). When the address of the first EAS is not within a first EAS deployment information of the first local SMF network element, the first local SMF network element sends a third message to a central SMF network element, the third message including the identification information. The central SMF network element notifies the EASDF network element to update a DNS message processing rule, the updated DNS message processing rule indicating the EASDF network element to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message, the updated DNS message processing rule including the identification information.

[0078] In the above technical solution, when the first local SMF network element cannot identify the first EAS, the central SMF network element can update the DNS message processing rule to generate a DNS query message with an empty ECS option for the FQDN. This can return the service for the FQDN to the processing mode of non-edge computing services, thereby avoiding the situation of EAS flow discovery failure due to the first local SMF network element being unable to identify the first EAS.

[0079] In some implementations of the seventh aspect, in combination with the seventh aspect, the third message further includes third indication information, the third indication information being used to instruct the central SMF network element to notify the EASDF network element to update the DNS message processing rule.

[0080] In some implementations of the seventh aspect, in combination with the seventh aspect, the third message further includes an address of the first EAS and the FQDN, and the central SMF network element sending the updated DNS message processing rule to the EASDF network element includes: determining whether the second part EDI of the second EAS deployment information of the central SMF network element includes the address of the first EAS, and if the second part EDI does not include the address of the first EAS, the central SMF network element notifies the EASDF network element to update the DNS message processing rule.

[0081] In some implementations, the central SMF network element sending the updated DNS message processing rule to the EASDF network element includes: determining whether the first part EDI of the second EAS deployment information includes the address of the first EAS, and if the first part EDI does not include the address of the first EAS, the central SMF network element notifies the EASDF network element to update the DNS message processing rule.

[0082] In some implementations, the central SMF network element sending the updated DNS message processing rule to the EASDF network element includes: determining whether the first part EDI of the second EAS deployment information includes the FQDN, and if the first part EDI does not include the FQDN, the central SMF network element notifies the EASDF network element to update the DNS message processing rule.

[0083] It should be understood that the above determination conditions can be used in combination, for example, when the second part EDI does not include the address of the first EAS, it is determined whether the first part EDI includes the address of the first EAS. The embodiments of the present application do not limit the number of determination conditions used, and in addition, when the above determination conditions are used in combination, the embodiments of the present application do not limit the order of use of the determination conditions.

[0084] In some implementations of the seventh aspect, in combination with the seventh aspect, the central SMF network element notifying the EASDF network element to update the DNS message processing rule includes: the central SMF network element sending the updated DNS message processing rule to the EASDF network element.

[0085] In some implementations of the seventh aspect, in combination with the seventh aspect, the central SMF network element notifying the EASDF network element to update the DNS message processing rule includes: the central SMF network element sending a fourth message to the first local SMF network element, the fourth message including identification information. The first local SMF network element generates and sends the updated DNS message processing rule to the EASDF network element.

[0086] In some implementations of the seventh aspect, in conjunction with the seventh aspect, the fourth message further includes fourth indication information, and the fourth indication information is used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0087] In some implementations of the seventh aspect, in conjunction with the seventh aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The second EAS deployment information includes a second part EDI and a first part EDI, the first part EDI is EAS deployment information corresponding to an edge computing service supported by the central SMF network element, and the second part EDI includes a DNAI corresponding to a local SMF network element maintained by the central SMF network element, an address range of the EAS, and an association relationship between the DNAI and the address range of the EAS.

[0088] In some implementations of the eighth aspect, in conjunction with the eighth aspect, the third message further includes third indication information, and the third indication information is used to instruct the central SMF network element to instruct the EASDF network element to update the DNS message processing rule.

[0089] In the above technical solution, after the central SMF network element receives the third message from the first local SMF network element, the EASDF network element is instructed to update the DNS message processing rule, so that the EASDF network element generates a DNS query message with an empty ECS option for the FQDN. In this way, the service for the FQDN can be returned to the processing mode of the non-edge computing service, thereby avoiding the situation that the EAS flow discovery fails due to the inability of the first local SMF network element to identify the first EAS.

[0090] In some implementations of the eighth aspect, in conjunction with the eighth aspect, the third message further includes third indication information, and the third indication information is used to instruct the central SMF network element to instruct the EASDF network element to update the DNS message processing rule.

[0091] In some implementations of the eighth aspect, in conjunction with the eighth aspect, the third message further includes an address of a first edge application server (EAS). Instructing the edge application server discovery function (EASDF) network element to update the DNS message processing rule includes: when the first part EDI of the second EAS deployment information of the central SMF network element does not include the address of the first EAS, and the first part EDI does not include the FQDN, instructing the EASDF network element to update the DNS message processing rule.

[0092] With reference to the eighth aspect, in some implementations of the eighth aspect, notifying the EASDF network element to update the DNS message processing rule comprises: sending, to the EASDF network element, the updated DNS message processing rule.

[0093] With reference to the eighth aspect, in some implementations of the eighth aspect, notifying the EASDF network element to update the DNS message processing rule comprises: sending, to the first local SMF network element, a fourth message, the fourth message comprising identification information, the identification information being used to instruct the first local SMF network element to generate and send, to the EASDF network element, the updated DNS message processing rule.

[0094] With reference to the eighth aspect, in some implementations of the eighth aspect, the fourth message further comprises fourth indication information, the fourth indication information being used to instruct the first local SMF network element to generate and send, to the EASDF network element, the updated DNS message processing rule.

[0095] The ninth aspect provides a communication method applied to a first local session management function (SMF) network element, comprising: receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request comprising an address of a first edge application server (EAS), identification information of a DNS response message, and a fully qualified domain name (FQDN); and when the address of the first EAS is not within a range of first EAS deployment information of the first local SMF network element, sending a third message to a central SMF network element, the third message comprising the identification information and the FQDN, the identification information being used to instruct the central SMF network element to notify the EASDF network element to update a DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF network element to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message.

[0096] In the above technical solution, if the first local SMF network element cannot identify the address of the first EAS, the first local SMF network element can send the identification information of the DNS response message and the FQDN to the central SMF network element, which is helpful for the central SMF network element to subsequently notify the EASDF to update the DNS message processing rule, thereby avoiding the situation of EAS flow discovery failure caused by the first local SMF network element being unable to identify the address of the first EAS.

[0097] In the above technical solution, if the first local SMF network element cannot identify the address of the first EAS, the first local SMF network element can send the identification information of the DNS response message and the FQDN to the central SMF network element, which is helpful for the central SMF network element to subsequently notify the EASDF to update the DNS message processing rule, thereby avoiding the situation of EAS flow discovery failure caused by the first local SMF network element being unable to identify the address of the first EAS.

[0098] In some implementations of the ninth aspect, the third message further includes third indication information, and the third indication information is used to instruct the central SMF network element to inform the EASDF network element to update the DNS message processing rule.

[0099] In some implementations of the ninth aspect, the method further includes: receiving a fourth message from the central SMF network element, and the fourth message includes the identification information. Generating and sending the updated DNS message processing rule to the EASDF network element, and the updated DNS message processing rule includes the identification information.

[0100] In some implementations of the ninth aspect, the fourth message further includes fourth indication information, and the fourth indication information is used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0101] The tenth aspect provides a communication method, which includes: a first local session management function (SMF) network element receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, and the DNS context notification request includes an address of a first edge application server (EAS) and a fully qualified domain name (FQDN). When the address of the first EAS is not within a range of first EAS deployment information of the first SMF network element, the first local SMF network element sends a third message to a central SMF network element, and the third message includes the address of the first EAS and the FQDN. The central SMF network element determines whether the first part of the second EAS deployment information (EDI) includes the FQDN when the address of the first EAS is not included in the first part of the EDI of the central SMF network element. The central SMF network element informs the EASDF network element to update a DNS message processing rule according to a determination result.

[0102] In some implementations of the tenth aspect, the address of the first EAS is not within the first EDI of the first local SMF network element, which means that the first local SMF network element cannot identify the address of the first EAS.

[0103] In the above technical solution, when the first local SMF network element cannot identify the address of the first EAS, the central SMF determines the appropriate processing mode through multiple judgments on the address of the first EAS and the FQDN, thereby avoiding the situation that the EAS flow discovery fails due to the first local SMF network element being unable to identify the address of the first EAS, and improving the success rate of discovering the EAS.

[0104] In some implementations of the tenth aspect, the third message further includes fifth indication information, and the fifth indication information is used to instruct the central SMF network element to determine whether the first part of the EDI includes the address of the first EAS.

[0105] In some implementations of the tenth aspect, the third message further includes identification information of the DNS response message.

[0106] In the eleventh aspect, a communication method is provided, which includes: a first local session management function (SMF) network element configuring a central SMF network element as a notification endpoint for a domain name system (DNS) response message for an edge application server discovery function (EASDF) network element; the central SMF network element receiving a DNS context notification request from the EASDF network element, the DNS context notification request including an address of a first edge application server (EAS) and a fully qualified domain name (FQDN); and determining whether a first part of second EAS deployment information (EDI) includes the FQDN when the first part of the second EDI does not include the address of the first EAS; and notifying the EASDF network element to update a DNS message processing rule according to a determination result.

[0107] In the above technical solution, the central SMF network element directly receives the address of the first EAS and the FQDN from the EASDF network element, and directly determines an appropriate processing mode by multiple judgments on the address of the first EAS and the FQDN, thereby directly avoiding a situation that the first local SMF cannot recognize the address of the first EAS, i.e., directly avoiding a situation that the first EDI of the first local SMF does not include the address of the first EAS, and thus improving a success rate of discovering the EAS.

[0108] In some implementations of the eleventh aspect, the DNS context notification request further includes fifth indication information, and the fifth indication information is used to instruct the central SMF network element to determine whether the first part of the second EDI includes the address of the first EAS.

[0109] In some implementations of the tenth aspect or the eleventh aspect, the DNS context notification request further includes identification information of the DNS response message, and the central SMF network element notifying the EASDF network element to update the DNS message processing rule according to the determination result includes: if the first part of the second EDI includes the FQDN, the central SMF network element generates information used to indicate a location of a user equipment (UE) according to the FQDN, location information of the UE, and the second EDI; and the central SMF network element notifying the EASDF network element to update the DNS message processing rule includes: the updated DNS message processing rule being used to instruct the EASDF network element to generate an ECS option, the ECS option including the information used to indicate the location of the UE, and the EASDF network element adding the ECS option to a DNS query message and deleting the DNS response message, the DNS query message being regenerated for the FQDN, and the updated DNS message processing rule including the first information and the identification information, the first information being the information used to indicate the location of the UE.

[0110] In the technical solution, since the central SMF supports edge computing services for FQDN, the central AMF can generate information indicating the location of the UE to implement the discovery process of the subsequent EAS by the central AMF. In this way, in combination with the current discovery process of the central SMF, the situation that the first local SMF cannot identify the first EAS and causes the failure of the EAS discovery process can be effectively addressed.

[0111] In combination with the tenth aspect or the eleventh aspect, in some implementations, the central SMF network element notifying the EAS DF network element to update the DNS message processing rule includes: the central SMF network element sending the updated DNS message processing rule to the EAS DF network element.

[0112] In combination with the tenth aspect or the eleventh aspect, in some implementations, the central SMF network element notifying the EAS DF network element to update the DNS message processing rule includes: the central SMF network element sending a fifth message to the first local SMF network element, the fifth message including the identification information and the first information, the first information being the information indicating the location of the UE. The first local SMF network element generates and sends the updated DNS message processing rule to the EAS DF network element.

[0113] In combination with the tenth aspect or the eleventh aspect, in some implementations, the fifth message further includes sixth indication information, the sixth indication information being used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EAS DF network element.

[0114] In combination with the tenth aspect or the eleventh aspect, in some implementations, the DNS context notification request further includes identification information of the DNS response message. The central SMF network element generating and sending the updated DNS message processing rule to the EAS DF network element according to the determination result includes: if the first part of the EDI does not include the FQDN, the central SMF network element notifying the EAS DF network element to update the DNS message processing rule, the updated DNS message processing rule being used to instruct the EAS DF network element to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message, and the updated DNS message processing rule including the identification information.

[0115] In combination with the tenth aspect or the eleventh aspect, in some implementations, the central SMF network element notifying the EAS DF network element to update the DNS message processing rule includes: the central SMF network element sending the updated DNS message processing rule to the EAS DF network element.

[0116] In some implementations, in combination with the tenth aspect or the eleventh aspect, the center SMF network element notifying the EAS DF network element to update the DNS message processing rule comprises: the center SMF network element sending a fourth message to the first local SMF network element, the fourth message comprising the identification information. The first local SMF network element generates and sends the updated DNS message processing rule to the EAS DF network element.

[0117] In some implementations, in combination with the tenth aspect or the eleventh aspect, the fourth message further comprises fourth indication information, the fourth indication information being used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EAS DF network element.

[0118] In some implementations, in combination with the tenth aspect or the eleventh aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The second EAS deployment information comprises a second part EDI and a first part EDI, the first part EDI being EAS deployment information corresponding to an edge computing service supported by the center SMF network element, and the second part EDI comprising a DNAI corresponding to a local SMF network element maintained by the center SMF network element, an address range of the EAS, and an association relationship between the DNAI and the address range of the EAS.

[0119] The twelfth aspect provides a communication method applied to a center session management function (SMF) network element, comprising: receiving a third message from a first local SMF network element, the third message comprising an address of a first EAS and a fully qualified domain name (FQDN). When a first part EDI of second EAS deployment information (EDI) of the center SMF network element does not comprise the address of the first EAS, determining whether the first part EDI comprises the FQDN. According to a determination result, notifying an EAS DF network element to update a DNS message processing rule.

[0120] In the above technical solution, the center SMF determines the appropriate processing mode through multiple judgments on the address of the first EAS and the FQDN, thereby avoiding the situation that the EAS process discovery fails due to the first local SMF network element being unable to recognize the address of the first EAS, that is, avoiding the situation that the EAS process discovery fails due to the first part EDI of the first local SMF network element not comprising the address of the first EAS, thereby improving the success rate of discovering the EAS.

[0121] In some implementations of the twelfth aspect, in combination with the twelfth aspect, the third message further comprises fifth indication information, the fifth indication information being used to instruct the center SMF network element to determine whether the first part EDI comprises the address of the first EAS.

[0122] In some implementations of the twelfth aspect, in combination with the twelfth aspect, the third message further comprises identification information of a DNS response message.

[0123] In a thirteenth aspect, a communication method is provided, applied to a central session management function (SMF) network element, comprising: receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request comprising an address of a first edge application server (EAS) and a fully qualified domain name (FQDN), the central SMF network element being a notification endpoint of the first local SMF network element configured to the EASDF network element for a DNS response message; and determining whether the first part of the second EAS deployment information (EDI) includes the address of the first EAS, when the first part of the EDI does not include the address of the first EAS. According to the determination result, notifying the EASDF network element to update the DNS message processing rule.

[0124] In the above technical solution, the central SMF network element directly receives the address of the first EAS and the FQDN from the EASDF network element, and directly determines the appropriate processing mode by multiple judgments on the address of the first EAS and the FQDN, thereby directly avoiding the case that the first local SMF cannot recognize the address of the first EAS, i.e., directly avoiding the case that the first EDI of the first local SMF does not include the address of the first EAS, thereby improving the success rate of discovering the EAS.

[0125] In combination with the thirteenth aspect, in some implementations of the thirteenth aspect, the DNS context notification request further comprises fifth indication information, the fifth indication information being used to instruct the central SMF network element to determine whether the first part of the EDI includes the address of the first EAS.

[0126] In combination with the twelfth aspect or the thirteenth aspect, in some implementations, the DNS context notification request further comprises identification information of the DNS response message, and according to the determination result, notifying the EASDF network element to update the DNS message processing rule comprises: if the first part of the EDI includes the FQDN, the central SMF network element generates information used to indicate the location of the user equipment (UE) according to the FQDN, the location information of the UE and the second EAS deployment information. The updated DNS message processing rule comprises the identification information, and the updated DNS message processing rule is used to instruct the EASDF network element to generate an ECS option, the ECS option comprises the information used to indicate the location of the UE, the ECS option is added to a DNS query message and the DNS response message is deleted, and the DNS query message is regenerated for the FQDN.

[0127] In combination with the twelfth aspect or the thirteenth aspect, in some implementations, notifying the EASDF network element to update the DNS message processing rule comprises: sending the updated DNS message processing rule to the EASDF network element.

[0128] In some implementations, in conjunction with the twelfth aspect or the thirteenth aspect, notifying the EASDF network element to update the DNS message processing rule comprises: sending a fifth message to the first local SMF network element, the fifth message comprising the identification information and first information, the first information being information for instructing the first local SMF network element to generate information for indicating the UE's location according to the first information, and the first information further being used to instruct the first local SMF network element to generate information for instructing the EASDF network element to generate an ECS option in the updated DNS message processing rule.

[0129] In some implementations, in conjunction with the twelfth aspect or the thirteenth aspect, the fifth message further comprises sixth indication information, the sixth indication information being used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0130] In some implementations, in conjunction with the twelfth aspect or the thirteenth aspect, according to the determination result, notifying the EASDF network element to update the DNS message processing rule comprises: if the first part of the EDI does not comprise the FQDN, notifying the EASDF network element to update the DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF network element to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message, and the updated DNS message processing rule comprising identification information of the DNS response message.

[0131] In some implementations, in conjunction with the twelfth aspect or the thirteenth aspect, notifying the EASDF network element to update the DNS message processing rule comprises: sending the updated DNS message processing rule to the EASDF network element.

[0132] In some implementations, in conjunction with the twelfth aspect or the thirteenth aspect, notifying the EASDF network element to update the DNS message processing rule comprises: the central SMF network element sending a fourth message to the first local SMF network element, the fourth message comprising identification information, the identification information being used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0133] In some implementations, in conjunction with the twelfth aspect or the thirteenth aspect, the fourth message further comprises fourth indication information, the fourth indication information being used to instruct the first local SMF network element to generate and send the updated DNS message processing rule to the EASDF network element.

[0134] In some implementations, in combination with the twelfth aspect or the thirteenth aspect, the first EAS deployment information is EAS deployment information corresponding to an edge computing service supported by the first local SMF network element. The second EAS deployment information includes a second part of EDI and a first part of EDI, the first part of EDI being EAS deployment information corresponding to an edge computing service supported by the central SMF network element, and the second part of EDI including a DNAI corresponding to a local SMF network element maintained by the central SMF network element, an address range of the EAS, and an association relationship between the DNAI and the address range of the EAS.

[0135] In a fourteenth aspect, a communication method is provided, which is applied to a first local session management function (SMF) network element, and includes: receiving a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request including an address of a first edge application server (EAS) and a fully qualified domain name (FQDN). When the address of the first EAS does not belong to first EAS deployment information of the first SMF network element, sending a third message to a central SMF network element, the third message including the address of the first EAS and the FQDN, the address of the first EAS and the FQDN being used to instruct the central SMF network element to notify the EASDF network element to update a DNS message processing rule according to the address of the first EAS and the FQDN.

[0136] In some implementations, in combination with the fourteenth aspect, the address of the first EAS does not belong to the first EDI of the first local SMF network element, which means that the first local SMF network element cannot recognize the address of the first EAS.

[0137] In the above technical solution, if the first local SMF network element cannot recognize the address of the first EAS, the first local SMF network element can send the address of the first EAS and the FQDN to the central SMF network element, which is helpful for the central SMF network element to make multiple judgments to determine the appropriate processing mode, thereby avoiding the situation that the EAS flow discovery fails due to the first local SMF network element being unable to recognize the address of the first EAS, and improving the success rate of discovering the EAS.

[0138] In some implementations, in combination with the fourteenth aspect, the third message further includes fifth indication information, the fifth indication information being used to instruct the central SMF network element to determine whether the first part of EDI of the second EAS deployment information includes the address of the first EAS.

[0139] In some implementations of the fourteenth aspect, in conjunction with the fourteenth aspect, the DNS context notification request further includes identification information of the DNS response message, the third message further includes the identification information, and the method further includes: receiving a fourth message from the central SMF network element, the fourth message including the identification information; and generating and sending, to the EASDF network element, an updated DNS message processing rule, the updated DNS message processing rule including the identification information, the updated DNS message processing rule being used to instruct the EASDF network element to generate a DNS query message with an ECS option that is empty for the FQDN and to delete the DNS response message.

[0140] In some implementations of the fourteenth aspect, in conjunction with the fourteenth aspect, the fifth message further includes sixth indication information, the sixth indication information being used to instruct the first local SMF network element to generate and send, to the EASDF network element, the updated DNS message processing rule.

[0141] In some implementations of the fourteenth aspect, in conjunction with the fourteenth aspect, the DNS context notification request further includes identification information of the DNS response message, the third message further includes the identification information, and the method further includes: receiving a fourth message from the central SMF network element, the fourth message including the identification information; and generating and sending, to the EASDF network element, an updated DNS message processing rule, the updated DNS message processing rule including the identification information, the updated DNS message processing rule being used to instruct the EASDF network element to generate a DNS query message with an ECS option that is empty for the FQDN and to delete the DNS response message.

[0142] In some implementations of the fourteenth aspect, in conjunction with the fourteenth aspect, the fourth message further includes fourth indication information, the fourth indication information being used to instruct the first local SMF network element to generate and send, to the EASDF network element, the updated DNS message processing rule.

[0143] A fifteenth aspect provides a communication apparatus, which includes a module or unit for performing any possible method in the second aspect, the sixth aspect, the eighth aspect, the twelfth aspect, or the thirteenth aspect.

[0144] In conjunction with the fifteenth aspect, the communication apparatus is a central SMF network element.

[0145] A sixteenth aspect provides a communication apparatus, which includes a module or unit for performing any possible method in the third aspect, the ninth aspect, or the fourteenth aspect.

[0146] In conjunction with the sixteenth aspect, the communication apparatus is a first local SMF network element.

[0147] In a seventeenth aspect, a communication apparatus is provided, which comprises modules or units for performing any possible method in the fourth aspect.

[0148] In connection with the seventeenth aspect, the communication apparatus is a second local SMF network element.

[0149] In an eighteenth aspect, a communication apparatus is provided, which comprises a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to execute the computer program stored in the memory, so that the apparatus performs any possible method in the second aspect, the sixth aspect, the eighth aspect, the twelfth aspect or the thirteenth aspect.

[0150] In connection with the eighteenth aspect, the communication apparatus is a central SMF network element.

[0151] In a nineteenth aspect, a communication apparatus is provided, which comprises a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to execute the computer program stored in the memory, so that the apparatus performs any possible method in the third aspect, the ninth aspect or the fourteenth aspect.

[0152] In connection with the nineteenth aspect, the communication apparatus is a first local SMF network element.

[0153] In a twentieth aspect, a communication apparatus is provided, which comprises a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to execute the computer program stored in the memory, so that the apparatus performs any possible method in the fourth aspect.

[0154] In connection with the twentieth aspect, the communication apparatus is a second local SMF network element.

[0155] In a twenty-first aspect, a communication system is provided, which comprises a communication apparatus performing any possible method in the second aspect, a communication apparatus performing any possible method in the third aspect, and a communication apparatus performing any possible method in the fourth aspect.

[0156] In a twenty-second aspect, a communication system is provided, which comprises a communication apparatus performing any possible method in the sixth aspect.

[0157] In a twenty-third aspect, a communication system is provided, which comprises a communication apparatus performing any possible method in the eighth aspect and a communication apparatus performing any possible method in the ninth aspect.

[0158] In a twenty-fourth aspect, a communication system is provided, which comprises a communication apparatus performing any possible method in the twelfth aspect and a communication apparatus performing any possible method in the fourteenth aspect.

[0159] In a twenty-fifth aspect, a communication system is provided, the system comprising a communication device performing any of the possible methods of the thirteenth aspect.

[0160] In a twenty-sixth aspect, a computer program product is provided, the computer program product comprising: computer program code which, when run on a computer, causes the computer to perform any of the possible methods of the first aspect to the fourteenth aspect.

[0161] It should be noted that the computer program code can be stored in whole or in part on a first storage medium, wherein the first storage medium can be packaged together with the processor or packaged separately from the processor, and the embodiments of the present application do not make a specific limitation in this regard.

[0162] In a twenty-seventh aspect, a computer readable medium is provided, the computer readable medium storing program code which, when run on a computer, causes the computer to perform any of the possible methods of the first aspect to the fourteenth aspect.

[0163] In a twenty-eighth aspect, a chip system is provided, the chip system comprising a processor, configured to invoke a computer program or computer instructions stored in a memory, so as to cause the processor to perform any of the possible methods of the first aspect to the fourteenth aspect.

[0164] In combination with the twenty-eighth aspect, in a possible implementation manner, the processor is coupled with the memory through an interface.

[0165] In combination with the twenty-eighth aspect, in a possible implementation manner, the chip system further comprises the memory, and the memory stores the computer program or computer instructions. BRIEF DESCRIPTION OF DRAWINGS

[0166] FIG. 1 is a schematic block diagram of an example wireless communication system architecture suitable for use with the present application;

[0167] FIG. 2 is a flow diagram of an example EAS discovery according to an embodiment of the present application;

[0168] FIG. 3 is a flow diagram of another example EAS discovery according to an embodiment of the present application;

[0169] FIG. 4 is a flow diagram of an example communication method according to an embodiment of the present application;

[0170] FIG. 5 is a flow diagram of another example communication method according to an embodiment of the present application;

[0171] FIG. 6 is a flow diagram of yet another example communication method according to an embodiment of the present application;

[0172] FIG. 7 is a flow diagram of another communication method according to an embodiment of the present application;

[0173] FIG. 8 is a flow diagram of another communication method according to an embodiment of the present application;

[0174] FIG. 9 is a flow diagram of another communication method according to an embodiment of the present application;

[0175] FIG. 10 is a flow diagram of another communication method according to an embodiment of the present application;

[0176] FIG. 11 is a flow diagram of another communication method according to an embodiment of the present application;

[0177] FIG. 12 is a flow diagram of another communication method according to an embodiment of the present application;

[0178] FIG. 13 is a flow diagram of another communication method according to an embodiment of the present application;

[0179] FIG. 14 is a flow diagram of another communication method according to an embodiment of the present application;

[0180] FIG. 15 is a flow diagram of another communication method according to an embodiment of the present application;

[0181] FIG. 16 is a flow diagram of another communication method according to an embodiment of the present application;

[0182] FIG. 17 is a schematic diagram of a communication apparatus 1700 according to an embodiment of the present application;

[0183] FIG. 18 is a schematic diagram of a communication apparatus 1800 according to an embodiment of the present application;

[0184] FIG. 19 is a schematic diagram of a chip system 1900 according to an embodiment of the present application. DETAILED DESCRIPTION

[0185] The technical solutions in the present application will be described below with reference to the drawings.

[0186] In order to facilitate understanding of the embodiments of the present application, the following points are explained:

[0187] First, in the present application, the terms and / or descriptions of different embodiments are consistent and can be mutually referenced if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0188] Secondly, in the present application, "at least one" means one or more, and "multiple" means two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In the textual description of the present application, the character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions means any combination of these items, including any combination of single item or multiple items. For example, at least one of a, b and c can represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple.

[0189] Thirdly, in the present application, "first", "second", and various numerical numbers (for example, #1, #2, etc.) indicate the differentiation for the convenience of description, and are not used to limit the scope of the embodiments of the present application. For example, differentiating different local SMF network elements, etc., rather than being used to describe a specific order or sequence. It should be understood that the objects thus described can be interchanged under appropriate circumstances, so as to be able to describe schemes other than the embodiments of the present application.

[0190] Fourthly, in the present application, the descriptions such as "when", "in the case of", and "if" all mean that the corresponding processing will be made under certain objective circumstances, and are not limited to time, and do not require a judgment action when implemented, nor does it mean that there are other limitations. In addition, it also does not mean that the judgment action after these conditional conjunctions is the only condition to achieve the result, and other additional conditions can also be included to achieve the result.

[0191] Fifthly, in the present application, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0192] Sixthly, in the present application, "for indicating" can include "for directly indicating" and "for indirectly indicating". When describing that certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and it does not mean that A must be carried in the indication information.

[0193] The indication manner involved in the embodiments of the present application should be understood as covering various methods that can enable the to-be-indicated party to know the to-be-indicated information. The to-be-indicated information can be sent as a whole, or can be sent separately in multiple sub-information, and the sending period and / or sending occasion of the sub-information can be the same or different, and the present application does not limit the specific sending method.

[0194] The "indication information" in the embodiments of the present application can be explicit indication, that is, direct indication through signaling, or obtained according to the parameters indicated by the signaling, in combination with other rules or in combination with other parameters or through derivation. It can also be implicit indication, that is, obtained according to rules or relationships, or according to other parameters, or through derivation. The present application does not make specific limitations on this.

[0195] Seventhly, in the present application, "protocol" can refer to a standard protocol in the communication field, which can include 5G protocol, new radio (NR) protocol and related protocols applied in future communication systems, and the present application does not limit this. "Predefined" can include predefinition. For example, protocol definition. "Preconfigured" can be realized by pre-storing corresponding codes, tables or other methods that can be used to indicate related information in the device, and the present application does not limit the specific implementation method thereof.

[0196] Eighthly, in the present application, "storage" can mean saving in one or more memories. The one or more memories can be separately arranged, or integrated in the encoder or decoder, processor or communication device. The one or more memories can also be partially separately arranged and partially integrated in the decoder, processor or communication device. The type of memory can be any form of storage medium, and the present application does not limit this.

[0197] The technical solutions provided by the present application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, wireless local area network (WLAN) system, satellite communication system, future communication system such as 6th generation mobile communication system, or a fusion system of multiple systems, etc.

[0198] The technical solutions provided in the application can also be applied to machine type communication (MTC), Long Term Evolution-machine (LTE-M), device to device (D2D) network, machine to machine (M2M) network, internet of things (IoT) network or other network. The IoT network may, for example, include a vehicle internet. In the vehicle internet system, the communication modes are collectively referred to as vehicle to X (V2X, X can represent any thing), for example, the V2X can include vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.

[0199] FIG. 1 is a schematic block diagram of an example wireless communication system architecture suitable for use with the present application, which can include the following network elements, as shown:

[0200] 1. User Equipment (UE): can be referred to as a terminal device, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0201] The terminal device can be a device providing voice / data to a user, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals are: mobile phone, tablet computer, notebook computer, palm computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0202] By way of example and not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction and cloud interaction. The general wearable smart device includes a device with full functions and large size, which can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and a device that focuses on a certain application function and needs to cooperate with other devices such as a smart phone, such as various smart wristbands and smart jewelry for monitoring vital signs.

[0203] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection.

[0204] It should be noted that the terminal device and the access network device can communicate with each other by using a certain air interface technology (such as NR or LTE technology, etc.). The terminal device and the terminal device can also communicate with each other by using a certain air interface technology (such as NR or LTE technology, etc.).

[0205] In the embodiments of the present application, the device for implementing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0206] 1, (radio) access network ((R)AN): can provide access to a communication network for authorized users in a specific area, which can specifically include a wireless network device in a 3rd generation partnership project (3GPP) network, and can also include an access point in a non-3GPP (non-3GPP) network. The following is for convenience, using AN device to represent.

[0207] AN device can be of different radio access technologies. There are two types of current radio access technologies: 3GPP radio access technology (e.g., radio access technology adopted in third generation (3G), fourth generation (4G) or 5G system) and non-3GPP radio access technology. 3GPP radio access technology refers to access technology conforming to 3GPP standard specification, for example, access network device in 5G system is called next generation Node Base station (gNB) or RAN device. Non-3GPP radio access technology can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA) and the like. AN device can allow terminal device and 3GPP core network to be interconnected and communicated by using non-3GPP technology.

[0208] AN device can be responsible for functions such as radio resource management on the air interface side, quality of service (QoS) management, data compression and encryption. AN device provides access service for terminal device, and then completes the forwarding of control signals and user data between terminal device and core network.

[0209] The AN device may include, but is not limited to, a macro base station, a micro base station (also referred to as a small station), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved NodeB or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), and the like, and can also be a gNB or a transmission point (TRP or TP) in a 5G (for example, NR) system, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a distributed unit (DU), or a base station in a next-generation communication 6G system, and the like. Embodiments of the present application do not limit the specific technology and specific device form adopted by the AN device.

[0210] 3. Data network (DN): an operator network mainly used to provide data services for UEs. For example, the Internet, a third-party service network, an IP multi-media service (IMS) network, and the like.

[0211] In the edge computing scenario, the edge application server EAS is an application deployed in the edge DN, such as EAS#1, EAS#2, or EAS#3 shown in FIG. 1.

[0212] 4. Access and mobility management function network element (AMF): used for mobility management and access management, and can be used to implement other functions in the mobility management entity (MME) function except for session management, for example, access authorization / authentication functions, and the like.

[0213] 5. Session management function (SMF): mainly used for session management, IP address allocation and management of terminal devices, selection of manageable user plane functions, termination of policy control and charging function interfaces, and downlink data notification.

[0214] The network architecture shown in FIG. 1 also includes a local SMF (L-SMF), which is mainly used for discovery of local EAS, and the L-SMF maintains EDI within its service range.

[0215] 6. Network exposure function (NEF): mainly used for securely exposing services and capabilities provided by 3GPP network functions to the outside.

[0216] 7. Policy control function (PCF): a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.).

[0217] 8. Application function (AF): used for data routing affected by applications, accessing network exposure function, and interacting with policy framework for policy control.

[0218] 9. Network repository function (NRF): used to save the description information of network function entities and their service provision, and support service discovery, network element entity discovery, etc.

[0219] 10. Edge application server discovery function (EASDF) network element: mainly responsible for discovering EAS, including functions such as registering with NRF for discovery and selection, processing DNS messages according to SMF instructions (e.g., receiving DNS message processing rules sent by SMF, sending DNS messages to local DNS server or central DNS server, adding ECS option to DNS query message, exchanging DNS messages sent by UE, notifying SMF of EASDF-related information, etc.), and terminating DNS security.

[0220] 11、User plane function (UPF): mainly used for receiving and forwarding user plane data. For example, the UPF can receive user plane data from a data network (DN) and send the user plane data to a user equipment through an AN device. The UPF can also receive user plane data from a terminal device through an AN device and forward it to a DN.

[0221] Exemplarily, the UPF can be divided into a protocol data unit session anchor (PSA) and an uplink classifier functionality (UL CL), as shown in FIG. 1.

[0222] A protocol data unit (PDU) session refers to a process of communication between a user equipment (UE) and a data network (DN). After the PDU session is established, a data transmission channel between the UE and the DN is established. A PDU session can have multiple PDU session anchors.

[0223] The SMF can insert an uplink classifier (UL CL) in the data transmission path of the PDU session. The UL CL function can be provided in the UPF, and its purpose is to forward data packets that meet the service filtering rules to the specified path, similar to the role of a routing table. The insertion and deletion of the UL CL are controlled by the SMF. The SMF can operate the UPF through the N4 interface, and of course the SMF also needs to consider the capability of the UPF, that is, whether the UPF supports the UL CL. When a UL CL is inserted into a PDU session data channel, the PDU session has multiple PSAs, which provide multiple different paths to access the same DN. The function of the UL CL is to forward the uplink service data to different PSAs according to the requirements of the filter, and to combine the downlink data from multiple PSAs of the UE.

[0224] As shown in FIG. 1, the UPF (UL CL / BP) can represent a UPF that provides a UL CL function or a common UPF, that is, the UPF can transmit uplink data to different PSAs, and the data channels corresponding to the respective PSAs will eventually converge at the UPF, and the downlink data will be combined to the UE.

[0225] It can be understood that the above-mentioned network elements or functions can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform).

[0226] For the convenience of description, the access management function network element is taken as an AMF network element, the session management network element is taken as an SMF network element, and the like in the following of the present application.

[0227] Further, the AMF network element can be referred to as an AMF, the SMF network element can be referred to as an SMF, and the PCF network element can be referred to as a PCF. That is, the AMF described in the following of the present application can be replaced by an access management function network element, the SMF can be replaced by a session management network element, and the PCF can be replaced by a policy control network element.

[0228] For the convenience of description, the device is taken as an AMF entity and an SMF entity in the present application, and the method for information transmission is described. For the implementation method of the device being a chip in the AMF entity and a chip in the SMF entity, reference can be made to the specific description of the device being an AMF entity and an SMF entity, and no repeated introduction is made.

[0229] In the network architecture shown in FIG. 1, different network elements are connected through interfaces. For example, the UE is connected with the AMF through an N1 interface, the RAN is connected with the AMF through an N2 interface, and the RAN is connected with the UPF through an N3 interface. The UPFs are connected through an N9 interface, and the UPF is interconnected with the DN through an N6 interface. The SMF controls the UPF through an N4 interface.

[0230] In FIG. 1, N1, N2, N3, N4, N6, N9, and the like are interface serial numbers. The meanings of these interface serial numbers can be referred to the meanings defined in the current standard protocol, which are not limited herein.

[0231] It should be understood that the network architecture applied to the embodiments of the present application is only a network architecture described from the perspective of the traditional point-to-point architecture and the service-oriented architecture, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of realizing the functions of the above-mentioned various network elements is applicable to the embodiments of the present application.

[0232] In order to facilitate the understanding of the scheme of the embodiments of the present application, the technical terms involved in the embodiments of the present application are first explained briefly.

[0233] 1. Content delivery network (content delivery network, CDN) addressing

[0234] The CDN caches website content at the network edge, so that when the user equipment accesses the website, the request of the user equipment can be routed to the cache server closest to the user access network or the cache server with the best access effect through the scheduling system, and the cache server provides content service for the user. Compared with directly accessing the source station, this way shortens the network distance between the user and the content, thereby achieving the effect of acceleration.

[0235] 2. DNS message handling rule

[0236] The DNS message handling rule can also be referred to as a DNS context, and the EASDF processes the DNS message according to the DNS message handling rule configured by the SMF. The DNS message includes a DNS query message or a DNS response message. Specifically, the SMF can service the interface to configure the DNS message handling rule on the EASDF, for example, create, delete, or update the DNS message handling rule on the EASDF. Among them, the corresponding service interface for deletion can be Neasdf_DNSContext_Delete, the corresponding service interface for creation can be Neasdf_DNSContext_Create, and the corresponding service interface for updating can be Neasdf_DNSContext_Update.

[0237] The DNS message handling rule includes a detection rule, a reporting action, a forwarding action, and a control action. Among them, the detection rule can also be that the EASDF references an existing pre-configuration rule on the EASDF, for example, a Baseline DNS message detection template ID.

[0238] The detection rule can include the following contents: if the DNS message is a DNS query message, the detection rule specifically includes the range of the source IP address and the fully qualified domain name (FQDN). Since the DNS query message is generally issued by the UE, the source address can also be understood as the IP address of the UE. If the DNS message is a DNS response message, the detection rule specifically includes the range of the FQDN and / or the range of the IP address of the EAS.

[0239] Reporting action: whether to report the information in the DNS message to the SMF, that is, when the information in the DNS message (for example, the FQDN in the DNS query message, or the FQDN and the IP address of the EAS in the DNS response message) matches the detection rule, it is determined whether to report the information in the DNS message to the SMF.

[0240] Forwarding action: add the address information indicated by the SMF as an extended mechanisms for DNS (EDNS) client subnet option (hereinafter referred to as ECS option) to the DNS query message, and forward to the DNS server.

[0241] Control action: including caching the DNS response message, or forwarding the cached DNS response message to the UE.

[0242] In addition to the above-mentioned four types of rules, the DNS message processing rule can also include elements such as DNS handling rule identity, precedence of the DNS message handling rule, DNS message identifier, etc. It should be understood that the detailed process of the above-mentioned DNS message processing rule will be described in detail in conjunction with Figure 2.

[0243] 3. EAS deployment information (EDI)

[0244] EDI is the relevant information about the EAS deployment situation sent by the AF network element to the SMF network element through the NEF network element, which is used to complete the entire EAS discovery process. The EDI can include the following information:

[0245] FQDN(s): FQDN(s) supported by the application deployed in the edge network.

[0246] Data network access identifier (DNAI): DNAI corresponding to the EAS deployment information. It should be understood that the service range of each SMF can be divided into multiple edge networks, and different edge networks correspond to different DNAIs. Each NDAI corresponds to an edge network including multiple FQDN(s).

[0247] DNS server information (DNS server information): including a list of DNS server identifiers corresponding to each DNAI, wherein the DNS server identifier includes the IP address and port number of the DNS server.

[0248] IP address service range of EAS: IP address or IP address range of EAS in the edge network identified by the DNAI.

[0249] N6 traffic routing information: information related to how to forward edge traffic identified by the DNAI.

[0250] It should be understood that the DNAI, the DNS server information, the IP address service range of the EAS, or the N6 traffic routing information is optional information in the EDI.

[0251] 4. EASDF context

[0252] The EASDF context is related information generated by the EASDF network element after the first reception of the DNSD message processing rule sent by the SMF. The ID of the EASDF context is a unique identifier. The EASDF context can also be referred to as a DNS context. The EASDF context can include the IP address of the UE, the data network name (DNN), the notification endpoint, and the DNS message processing rule. It should be understood that the same PDU session corresponds to an ID of the EASDF context. The notification endpoint is the target network element address of the EASDF network element initiating the notification, which can be an IP address or a uniform resource locator (URL) of the target network element, and the like.

[0253] In the conventional mobile network architecture and deployment of 4G and before, the user plane equipment is basically deployed in a tree topology. The uplink user message passes through the access network equipment and the backhaul network, and finally accesses the data network through the centrally deployed anchor gateway. These anchor gateways are generally deployed in a higher position in the network, for example, in a large area central machine room. This topology structure is relatively simple, and it is convenient for operators to centrally manage and process messages at the anchor point. With the explosive growth of mobile service traffic, this deployment method is increasingly difficult to support the rapidly growing mobile service traffic model. On the one hand, in the network with centralized deployment of anchor gateways, the growing traffic is finally concentrated in the gateway and the core room, which puts higher and higher requirements on the backhaul network bandwidth, the machine room throughput, and the gateway specification. On the other hand, the long-distance backhaul network from the access point to the anchor gateway and the complex transmission environment result in large delay and jitter of user message transmission.

[0254] Based on the above background, the industry proposes the concept of edge computing (EC). EC realizes local processing of distributed service traffic by moving UPF and service processing capabilities down to the network edge, avoids excessive concentration of traffic, and thus can greatly reduce the specification requirements of core machine rooms and centralized gateways, reduce the end-to-end (E2E) delay and jitter of user messages, and make it possible to deploy ultra-low latency services.

[0255] In the scenario of EC deployment, some services can be provided by multiple edge application servers (EASs) deployed in edge data networks (EDNs). The EAS can also be referred to as an application instance, an edge application instance, an MEC application (server), an EAS function, etc. The edge application can specifically refer to an instance of a server application (for example, social media software, augmented reality (AR), virtual reality (VR)) deployed and running in an EDN. An application can deploy one or more EASs in one or more EDNs, and EASs deployed and running in different EDNs can be considered as different EASs of an application, which can share a domain name or use different domain names from the application deployed in the cloud. The domain name FQDN can use an arbitrary IP address or different IP addresses.

[0256] Among them, the edge data network EDN can be a local data network, and the local DN can also be understood as an access point of a data network that is close to the user's attachment point. The data network refers to an operator or third-party service network, which can provide operator services or Internet services for user equipment. The local DN can be identified by DNAI and DNN.

[0257] When the UE needs to access a certain service, the EC scenario requires it to access the available EAS close to the UE. Therefore, the UE needs to obtain the IP address of the appropriate EAS. The 3rd Generation Partnership Project (3GPP) standard TS23.548 defines a new network element that assists in discovering EAS, that is, the EASDF network element shown in FIG. 1, which mainly functions to process domain name system (DNS) messages according to the instructions of the SMF.

[0258] FIG. 2 is a flowchart of an EAS discovery method according to an embodiment of the present application.

[0259] S201a, in the PDU session establishment process, the SMF configures a DNS message processing rule to the EASDF after selecting the EASDF, and the DNS message processing rule.

[0260] The DNS message processing rule is determined by the SMF according to the EAS deployment information.

[0261] S201b, in the PDU session establishment process, the SMF sends the IP address of the EASDF to the UE, and the IP address of the EASDF will be used as the default address of the UE sending the DNS query message.

[0262] S202, the EASDF receives the DNS query message from the UE, and the DNS query message includes a source address and a FQDN.

[0263] The source address can be the IP address of the UE. For example, the FQDN can be the domain name of www.abc.com.

[0264] S203, the EASDF determines whether the information in the DNS query message matches the DNS message processing rule.

[0265] Specifically, the EASDF matches the source address in the DNS query message with the source address included in the DNS message processing rule. If the two match, the EASDF determines whether the FQDN in the DNS query message matches the FQDN range in the DNS message processing rule.

[0266] It should be understood that one EASDF can serve multiple PDU sessions, and there are different DNS message processing rules for each PDU session. Therefore, when the EASDF receives a DNS query message, it needs to first determine the PDU session corresponding to the DNS query message according to the source address and the corresponding DNS message processing rule.

[0267] Optionally, if the FQDN in the DNS query message is not within the range indicated by the DNS message processing rule, the EASDF sends the DNS query message to the default DNS server. At this time, the server determined by the default DNS server can be a remote server, such as a central cloud server.

[0268] S204, according to the reporting action in the DNS message processing rule, when the results in S203 match, the EASDF sends the FQDN included in the DNS query message to the SMF.

[0269] For example, the reporting action in the DNS message processing rule indicates that the EASDF needs to report to the SMF when it receives the DNS query message with the FQDN www.abc.com.

[0270] S205, the SMF determines first information, the first information being used to indicate the location information of the UE, and sends the first information to the EASDF.

[0271] Specifically, the SMF determines the first information according to the FQDN, the EAS deployment information and the UE location information, the first information being used to represent the location information of the UE. The first information can be an address, for example, the address can be an IP address of a local PSA controlled by the SMF in a region corresponding to a DNAI close to the location of the UE in the EDI.

[0272] S206, the EASDF adds the first information as an ECS option to the DNS query message to obtain a new DNS query message, and sends the new DNS query message to a central DNS server (C-DNS server).

[0273] The ECS option is an extension item of the DNS query message and is used to represent the location information of the UE.

[0274] S207, the C-DNS server determines an IP address of an EAS closest to the address in the ECS option, and sends a DNS response message including the IP address of the EAS to the EASDF. Optionally, the DNS response message can also include the FQDN.

[0275] S208, the EASDF judges whether the information in the DNS response message matches the DNS message processing rule.

[0276] Specifically, the EASDF matches the FQDN and / or the IP address of the EAS in the DNS response message with the FQDN and / or the IP range of the EAS indicated in the DNS message processing rule.

[0277] S209, if the result of the judgment in S208 matches, the EASDF sends the DNS response message including the IP address of the EAS to the SMF according to the reporting action. And the EASDF caches the DNS response message in the EASDF before receiving the indication of the SMF according to the control action.

[0278] Optionally, if the result of the judgment in S208 does not match, the EASDF sends the DNS response message including the IP address of the EAS to the UE according to the control action.

[0279] S210, the SMF inserts a splitting point (ULCL / BP) and a local anchor point (L-PSA) according to the IP address of the EAS and the locally configured EAS deployment information, and configures a splitting rule on the splitting point.

[0280] S211, after the SMF configures the split point, instructs the EASDF to send the buffered DNS response message to the UE.

[0281] S212, the EASDF sends the DNS response message to the UE, and the DNS response message includes the IP address of the EAS.

[0282] The discovery process of the EAS described above is the discovery process of all PDU sessions in the service range of the SMF network element, and since the service range of the SMF is large, it will cause the load of the SMF in implementing the discovery process of the EAS to be large. Therefore, at present, the discovery process of the EAS is performed by introducing a local network element, for example, a local session management function (L-SMF) network element, so as to reduce the load of the SMF. The main idea of this scheme is that the L-SMF and the SMF respectively configure the DNS message processing rule for the EASDF according to the respective EDI, so as to complete the discovery of the EAS.

[0283] FIG. 3 is a flowchart of another EAS discovery process provided by an embodiment of the present application.

[0284] S301, when the UE establishes a PDU session or moves, the AMF determines to insert the L-SMF.

[0285] Specifically, since the UE moves, it can not be in the service range of the SMF, and the AMF sends the SM context creation request (Nsmf_PDUSession_CreatSMContext Request) to the L-SMF.

[0286] Exemplarily, the AMF can trigger the insertion according to the business requirement, or trigger the insertion according to the location of the UE, or trigger the insertion according to the subscription when the PDU session is established, or trigger the insertion according to the AF related policy. It should be understood that the insertion triggered according to the location of the UE is only taken as an example for illustration in FIG. 3.

[0287] S302, after the L-SMF receives the SM context creation request sent by the AMF, it judges whether the local EDI is locally configured.

[0288] S303, if the L-SMF locally configures the first local EDI, it sends the PDU session creation request (Nsmf_PDUSession_Creat Request) to the SMF.

[0289] The creation request includes indication information, which can be used to indicate that the L-SMF configures the first local EDI, or request to provide the IP address of the EASDF, or indicate the priority of the SMF configuring the EASDF to perform the DNS message processing rule.

[0290] The SMF receives the indication information and provides the EASDF IP in step 6, and optionally, performs step 4.

[0291] S304, the SMF sends a DNS context creation or update message (Neasdf_DNSContext_Creat / Update) to the EASDF.

[0292] Specifically, the SMF generates the DNS message processing rule of the SMF according to the second local EDI, and configures the EASDF through S304.

[0293] S305, the SMF performs a PDU session establishment or modification process.

[0294] S306, the SMF sends a PDU session establishment response (Nsmf_PDUSession_Creat Response) to the L-SMF.

[0295] The PDU session establishment response includes the IP address of the UE and the IP address of the EASDF.

[0296] S307, the L-SMF sends a DNS context creation message (Neasdf_DNSContext_Creat) to the EASDF.

[0297] Specifically, the L-SMF generates the DNS message processing rule of the L-SMF according to the first local EDI, and configures the EASDF through S307.

[0298] S308, the EASDF creates multiple DNS contexts for the same UE according to S304 and S307.

[0299] For the DNS message processing rules in the multiple DNS contexts, the PDU session of the same UE can be indicated by the L-SMF or the SMF to be configured with different DNS message processing rules by the multiple SMFs, and the DNS message processing rule configured by the L-SMF has higher priority.

[0300] Method one, the message of S304 can include the IP address of the L-SMF, the IP address of the UE, and indication information, the indication information is used to indicate the priority of the rule. The EASDF determines that the PDU session of the UE will be configured with different DNSD message processing rules by the SMF and the L-SMF according to the IP address of the L-SMF and the IP address of the UE, and determines the priority of the DNS message processing rule configured by the L-SMF according to the indication information.

[0301] The second mode, the EASDF allows the session to be configured by multiple SMFs according to the local configuration, and the rules configured later have higher priority.

[0302] The third mode, the S307 can include the IP address of the UE and indication information, the indication information is used to indicate the priority of the rule. The EASDF determines that the PDU session of the UE will be configured with different DNSD message processing rules by the SMF and the L-SMF according to the IP address of the L-SMF and the IP address of the UE, and determines the priority of the DNS message processing rule configured by the L-SMF according to the indication information.

[0303] It should be understood that the indication information of the rule priority can be carried in the S304 or in the S307.

[0304] Specifically, the indication information can be to add a priority option in the optional item of the Neasdf_DNSContext_Create / Update, and the priority information of the DNS context created by the SMF or the L-SMF can be represented by the number 0 or 1, and the specific number corresponding to the priority is not limited by the embodiments of the present application.

[0305] It should also be understood that the EASDF can determine to allow multiple DNS contexts to be created for the same UE IP address instead of being overwritten by the above-mentioned three modes. For example, the SMF and the L-SMF respectively create one DNS context, which has different DNS context IDs or has the same DNS context ID, but both of the two DNS contexts correspond to the same UE IP.

[0306] The S309a, the UE sends a DNS query message to the EASDF, and the DNS query message includes the local FQDN. The S309b, the UE sends a DNS query message to the EASDF, and the DNS query message includes the central FQDN.

[0307] The S310a, the S310b, the EASDF executes the DNS message processing rules in the DNS contexts of the L-SMF and the SMF in turn according to the priority. If the local FQDN has met the high-priority rule (i.e. the DNS message processing rule of the L-SMF), the DNS message processing rule in the high-priority DNS context is executed, and the low-priority rule (i.e. the DNS message processing rule of the SMF) does not need to be executed. If the high-priority rule is not met, the low-priority rule is executed.

[0308] The S311, the EAS discovery process is completed according to the DNS message processing rules respectively configured by the L-SMF or the SMF.

[0309] It should be understood that the subsequent EAS discovery process can refer to the S204 to S212 in FIG. 2, which will not be described here.

[0310] The load of the SMF can be reduced by configuring different DNS contexts for the IP address of the same UE to the EASDF through the L-SMF and the SMF respectively. However, when the DNS server parses the ECS option in the DNS request message, the load of different EASs needs to be considered comprehensively. Therefore, even if the DNS server is expected to return the IP address of the EAS in the region corresponding to a specified DNAI to the L-SMF through the ESC option, in the case that the load of the EAS in the region corresponding to the DNAI is too high or other cases, the DNS server may return the IP address of the EAS in the region corresponding to another DNAI to the L-SMF. Since the L-SMF can only maintain the EDI in its service range, the IP address of the EAS in the region corresponding to another DNAI is not within the maintenance range of the L-SMF, the L-SMF cannot identify the IP address of the EAS, and thus cannot complete the subsequent EAS discovery process, ultimately resulting in the failure of EAS discovery.

[0311] To solve the above problems, embodiments of the present application provide a communication method and device. The following will be described in detail in combination with FIGS. 4-19.

[0312] FIG. 4 is a flowchart of a communication method according to an embodiment of the present application. It should be understood that the method shown in FIG. 4 is exemplified by taking the EASDF network element, the central SMF network element, the first local SMF network element, the second local SMF network element, the AMF network element and the NRF network element as the execution subject of the interaction, and the corresponding method is exemplified accordingly, but the present application does not limit the execution subject of the interaction. For example, the method implemented by the central SMF network element can also be implemented by a module (such as a chip, a chip system or a processor) of the central SMF network element, and can also be implemented by a logical node, a logical module or software capable of implementing all or part of the functions of the central SMF network element. When the execution subject is other network elements, similar understanding can be made, which will not be described here.

[0313] It should be understood that in the following embodiments, the EASDF network element is referred to as EASDF, and other network elements are similar, which will not be described here.

[0314] S401, the EASDF sends a DNS context notification request to the first local SMF network element, and the DNS context notification request includes the address of the first EAS.

[0315] It should be understood that in the method shown in FIG. 4, after the EASDF receives the DNS response message sent by the DNS server, the notification endpoint corresponding to the DNS response message is the first local SMF network element.

[0316] S402, the first local SMF network element determines whether the address of the first EAS is within the range of the first EAS deployment information (first EDI).

[0317] When the address of the first EAS is not within the scope of the first EDI, S403, the first local SMF sends a first message to the central SMF, the first message comprising the address of the first EAS.

[0318] Optionally, when the address of the first EAS is within the scope of the first EDI, the first local SMF inserts a split point (UL CL / BP) and a local anchor point (L-PSA) according to the IP address of the first EAS and the first EDI, and configures a split rule on the split point.

[0319] As a possible implementation, the first message can further comprise first indication information, the first indication information being used to indicate whether the central SMF determines whether the second part EDI of the second EAS deployment information (second EDI) of the central SMF comprises the address of the first EAS.

[0320] S404a, the central SMF determines whether the second part EDI of the second EDI comprises the address of the first EAS.

[0321] The first EDI is EAS deployment information corresponding to EC services supported by the first local SMF. For example, the first EDI comprises FQDN(s) corresponding to EC services supported by the first local SMF, DNAI, IP range of EAS corresponding to the DNAI, and N6 transmission routing information of the EAS, the N6 transmission routing information being information about how to forward edge traffic in the local part of DN corresponding to the DNAI.

[0322] The second EDI comprises a first part EDI and a second part EDI, the first part EDI comprising EAS deployment information of EC services supported by the central SMF. The second part EDI can comprise DNAI corresponding to each local SMF maintained by the central SMF network element, address range of EAS, and association relationship between the address range of the EAS and the DNAI. For example, the first part EDI is EAS deployment information of EC services supported by the central SMF, which specifically comprises FQDN(s) corresponding to EC services supported by the central SMF, DNAI, IP range of EAS corresponding to the DNAI, and N6 transmission routing information of the EAS, and the like.

[0323] Optionally, the second EDI can further comprise only the second part EDI.

[0324] S404b, if the second part EDI includes the address of the first EAS, the central SMF determines the first DNAI corresponding to the address of the first EAS.

[0325] Specifically, the central SMF determines the first DNAI corresponding to the address of the first EAS according to the second part EDI of the second EDI.

[0326] Optionally, if the second part EDI does not include the address of the first EAS, the central SMF can generate and notify the EASDF of an updated DNS message processing rule, and the updated DNS message processing rule can be used to instruct the EASDF to generate a DNS query message with an ECS option of the FQDN being empty and delete the DNS response message. It should be understood that specific steps can refer to S804 in FIG. 8.

[0327] Optionally, if the second part EDI does not include the address of the first EAS, the central SMF can determine whether the first part EDI includes the address of the first EAS.

[0328] Optionally, if the second part EDI does not include the address of the first EAS, the central SMF can determine whether the first part EDI includes the FQDN.

[0329] S405, the central SMF sends the first DNAI to the NRF.

[0330] As a possible implementation, the central SMF sends the first DNAI to the NRF through the AMF.

[0331] Specifically, S405a-1, the central SMF sends the first DNAI to the AMF, and the AMF sends the first DNAI to the NRF.

[0332] As a possible implementation, S405b, the central SMF directly sends the first DNAI to the NRF.

[0333] S406, the NRF determines the second local SMF corresponding to the first DNAI, and the second local SMF is used to determine the L-PSA accessing the first EAS.

[0334] In the above technical solution, when the first local SMF network element cannot identify the first EAS, the second local SMF network element that can identify the first EAS can be determined through the central SMF network element and the NRF network element, so that the second local SMF completes the EAS discovery process in the future, thereby avoiding the situation that the EAS process discovery fails due to the first local SMF network element cannot identify the first EAS, thereby improving the success rate of discovering the EAS.

[0335] S407a, the NRF sends the address of the second local SMF network element to the AMF;

[0336] S408a, the AMF sends the related information of the session management to the second local SMF, and the related information of the session management includes the address of the central SMF and / or the address of the first local SMF.

[0337] Optionally, the related information of the session management can further include the session management context ID and the like, and the session management context ID can point to the first local SMF.

[0338] S407b, the NRF sends the address of the second local SMF network element to the central SMF;

[0339] S408b, the central SMF sends the related information of the session management to the second local SMF, and the related information of the session management includes the address of the central SMF and / or the address of the first local SMF.

[0340] It should be understood that in the implementation mode of S407b and S408b, the central SMF can obtain the related information of the session management from the AMF.

[0341] In the above technical solution, the second local SMF obtains the related information of the session management, which can help the second local SMF more conveniently obtain the first EAS, thereby helping to complete the EAS discovery process.

[0342] S409, the second local SMF obtains the address of the first EAS.

[0343] Specifically, in mode one, the second local SMF sends a first request message to the central SMF, the first request message is used to request the related information of edge computing, and the central SMF sends the address of the first EAS to the second local SMF.

[0344] In mode two, the second local SMF sends a first request message to the first local SMF, the first request message is used to request the related information of edge computing, and the first local SMF sends the address of the first EAS to the second local SMF.

[0345] S410, the second local SMF determines the L-PSA accessing the first EAS.

[0346] Optionally, the second local SMF can also determine the UL CL / BP accessing the first EAS.

[0347] S411, the central SMF and the second local SMF implement the construction of the forwarding tunnel of the node including the first EAS by inserting a splitting point.

[0348] Specifically, if the central SMF network element determines the UL CL / BP of the first EAS, the UL CL / BP split point is inserted by the central SMF and the split rule is configured, the L-PSA insertion split point is inserted by the first local SMF and the split rule is configured.

[0349] Specifically, if the first local SMF network element can also determine the UL CL / BP of the first EAS, the UL CL(BP) split point and the L-PSA split point are inserted by the first local SMF, and the split rule is configured to both.

[0350] S412, the central SMF notifies the EASDF to update the DNS message processing rule. The updated DNS message processing rule is used to instruct the EASDF network element to send the buffered DNS response message to the UE. The updated DNS message processing rule includes the identification information.

[0351] The identification information is the identification information of the DNS response message, the DNS context notification request in S401 can also include the identification information, and the first message in S403 can also include the identification information.

[0352] As a possible implementation manner, S412a-1, the central SMF sends a second message to the first local SMF, and the second message includes the identification information. S412a-2, the first local SMF generates and sends the updated DNS message processing rule to the EASDF.

[0353] In some implementation manners, the second message further includes second indication information, and the second indication information is used to instruct the first local SMF to generate and send the updated DNS message processing rule to the EASDF.

[0354] As a possible implementation manner, S412b, the central SMF directly generates and sends the updated DNS message processing rule to the EASDF.

[0355] In the above technical solution, the EASDF is notified to update the DNS message processing rule, and then the EASDF is instructed to forward the buffered DNS response message to the user equipment, and then the EAS discovery process is completed.

[0356] It should be understood that in the case where the first local SMF determines that it cannot identify the address of the first EAS, the steps of S404b to S412 are the manner one of completing the EAS discovery through the second local SMF corresponding to the address of the first EAS.

[0357] FIG. 5 is a flow diagram of another communication method according to an embodiment of the present application. The method shown in FIG. 5 is illustrated by taking the DNS server, the EASDF network element, the central SMF network element, the first local SMF network element, the second local SMF network element, the AMF network element, the NRF network element, and the UE as the execution subject of the interaction as an example, but the present application does not limit the execution subject of the interaction. For example, the method implemented by the central SMF network element can also be implemented by a module (such as a chip, a chip system, or a processor) of the central SMF network element, and can also be implemented by a logic node, a logic module, or software that can implement all or part of the function of the central SMF network element. When the execution subject is other network elements, similar understanding can be made, which will not be described here.

[0358] S501, the first local SMF implements the pre-step of the EAS discovery process.

[0359] It should be understood that the pre-step can include steps such as establishing a PDU session, selecting an EASDF, selecting a first local SMF, and configuring a DNS message processing rule. For details, refer to the steps shown in FIG. 3.

[0360] S502, the DNS server sends a DNS response message to the EASDF, and the EASDF receives the DNS response message from the DNS server.

[0361] The DNS response message includes the address of the first EAS and the FQDN.

[0362] S503, the EASDF sends a DNS context notification request to the first local SMF, and the first local SMF receives the DNS context notification request from the EASDF.

[0363] The DNS context notification request can include the address of the first EAS.

[0364] Optionally, the DNS context notification request can also include the FQDN, the notification endpoint, or the identification information (for example, the DNS message ID) of the DNS response message, which is used to identify the DNS response message.

[0365] It should be understood that the identification information of the DNS response message is obtained by the EASDF according to the DNS message processing rule. Specifically, the EASDF matches the DNS response message according to the FQDN to generate the identification information of the DNS response message.

[0366] It should also be understood that in the S501 step, the EASDF generates a DNS context according to the configuration of the first local SMF network element, and the DNS context includes the information of the notification endpoint, which is the address of the first local SMF in the embodiment shown in FIG. 5.

[0367] It should also be understood that the embodiments of the present application do not limit the number of addresses of the first EAS, and the first EAS can be one or more.

[0368] Optionally, the DNS context notification request can further include the FQDN.

[0369] S504a, the first local SMF determines whether the address of the first EAS is within the range of the first EDI.

[0370] In other words, the first local SMF determines whether the address range of the EAS in the first EDI stored by the first local SMF includes the address of the first EAS reported by the EASDF. Wherein, S404a is explained in detail for the first EDI, which will not be repeated here.

[0371] Optionally, if the first EAS is within the range of the first EDI, the L-PSA corresponding to the first EAS is determined according to the address of the UE, the load of the first EAS or the N6 delay. The subsequent detailed steps can be referred to in FIG. 3, which will not be repeated here.

[0372] S504b, if the address of the first EAS is not within the range of the first EDI, the first local SMF sends a first message to the central SMF, and the first message includes the address of the first EAS.

[0373] Optionally, the first message can further include the identification information of the DNS response message, the identification information of the EASDF context (for example, EASDF context ID), the FQDN or the address information of the EASDF. Wherein, the identification information of the EASDF context can also be referred to as the identification information of the DNS context, and the identification information of the EASDF context corresponds to the PDU session.

[0374] In one possible implementation, the first message can further include first indication information, and the first indication information is used to indicate that the central SMF determines whether the second part EDI of the second EDI of the central SMF includes the address of the first EAS.

[0375] It should be understood that S404a is explained in detail for the second EDI, which will not be repeated here.

[0376] S505a, the central SMF determines whether the second part EDI of the second EDI includes the address of the first EAS.

[0377] In other words, the central SMF determines whether the address of the first EAS is within the address range of the EAS corresponding to the local SMF maintained by the central SMF.

[0378] S505b, if the second part of the EDI includes the address of the first EAS, the central SMF determines the first DNAI corresponding to the address of the first EAS according to the second part of the EDI.

[0379] It should be understood that if the second part of the EDI does not include the address of the first EAS, the subsequent possible implementation manner can refer to S404b, which is not described here.

[0380] In some implementation manners, if the number of the first EAS is multiple, that is, there are multiple addresses of the first EAS, the central SMF determines the optimal address of the first EAS according to the load information of the first EAS and the location of the UE. Wherein, the multiple addresses of the first EAS correspond to different DNAIs.

[0381] It should be understood that if the multiple addresses of the first EAS correspond to the same DNAI, the first DNAI is directly determined.

[0382] The first local SMF is determined in the following manner:

[0383] S506a-1, the central SMF sends the first DNAI to the AMF.

[0384] S506a-2, the AMF sends the first DNAI to the NRF.

[0385] S507a, the NRF determines the second local SMF corresponding to the first DNAI.

[0386] S508a, the NRF sends the address of the second local SMF to the AMF.

[0387] S509a, the AMF sends the related information of the session management to the second local SMF, and the related information of the session management includes the address of the central SMF and / or the address of the first local SMF.

[0388] Optionally, the AMF can also send the location information of the UE to the second local SMF.

[0389] The second local SMF is determined in the following manner:

[0390] S506b, the central SMF sends the first DNAI to the NRF.

[0391] S507b, the NRF determines the second local SMF corresponding to the first DNAI.

[0392] S508b, the NRF sends the address of the second local SMF to the central SMF.

[0393] S509b, the central SMF sends session management related information to the second local SMF, the session management related information comprising an address of the central SMF, and / or an address of the first local SMF.

[0394] Optionally, in the above two manners, the session management related information can further comprise session management context ID and the like, which can point to the first local SMF.

[0395] The second local SMF can obtain the first EAS in the following two manners:

[0396] Manner one: S510a, the second local SMF sends a first request message to the central SMF, the first request message being used to request edge computing related information. S511a, the central SMF sends an address of the first EAS to the second local SMF.

[0397] Optionally, the second local SMF can further obtain the first DNAI corresponding to the address of the first EAS through S511a.

[0398] Manner two: S510b, the second local SMF sends a first request message to the first local SMF, the first request message being used to request edge computing related information. S511b, the first local SMF sends an address of the first EAS to the second local SMF.

[0399] S512, the second local SMF determines a target anchor network element according to the address of the first EAS and a third EDI.

[0400] The third EDI is EAS deployment information corresponding to an EC service supported by the second local SMF.

[0401] Specifically, if the number of the address of the first EAS is one, the optimal L-PSA is determined according to the address of the first EAS, location information of the UE and N6 latency information. If the number of the address of the first EAS is multiple, the optimal address of the first EAS and the optimal L-PSA are determined according to the address of the first EAS, location information of the UE, N6 latency information and / or N6 load information.

[0402] Optionally, the target anchor network element can further comprise UL CL / BP in addition to the L-PSA.

[0403] S513, the second local SMF and the central SMF jointly complete insertion of the target anchor network element and construct a forwarding tunnel.

[0404] Specifically, the central SMF determines the UL CL / BP according to the address of the first EAS.

[0405] Optionally, the second local SMF determines the insertion of the UL CL / BP, at this time, the insertion of the target anchor network element is completed between the second local SMF and the target anchor network element, and a forwarding tunnel is constructed.

[0406] The first way of updating the DNS message processing rule is as follows:

[0407] S514a-1, the central SMF sends a second message to the first local SMF, and the second message includes the identification information of the DNS response message.

[0408] Optionally, the second message further includes second indication information, and the second indication information is used to instruct the first local SMF to generate and send the updated DNS message processing rule to the EASDF.

[0409] Optionally, the second message can further include one or more of the identification information of the EASDF context or the FQDN information.

[0410] S514a-2, the first local SMF generates the updated DNS message processing rule, and the updated DNS message processing rule is used to instruct the EASDF network element to send the cached DNS response message to the UE.

[0411] S514a-3, the first local SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the identification information of the DNS response message.

[0412] The second way of updating the DNS message processing rule is as follows:

[0413] S514b-1, the central SMF generates the updated DNS message processing rule, and the updated DNS message processing rule is used to instruct the EASDF network element to send the cached DNS response message to the UE.

[0414] S514b-2, the central SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the identification information of the DNS response message.

[0415] Optionally, the central SMF can further send the identification information of the EASDF context to the EASDF.

[0416] S515: The EASDF forwards the cached DNS response message to the UE.

[0417] Specifically, the EASDF matches the cached DNS response message in the EASDF according to the identification information of the DNS response message, and sends the matched DNS response message to the UE.

[0418] It should be understood that in the case where the first local SMF determines that the address of the first EAS cannot be identified, the steps of S505b to S515 are a way of completing the EAS discovery by the second local SMF corresponding to the address of the first EAS.

[0419] FIG. 6 is a flow diagram of another communication method provided by the embodiments of the present application. It should be understood that the related description of the execution subject in FIG. 6 can refer to FIG. 4, which will not be repeated here.

[0420] S601, the first local SMF configures the EASDF with a notification endpoint for the DNS response message as the center SMF.

[0421] Specifically, the first local SMF sends the DNS message processing rule to the EASDF, the EASDF generates the EASDF context (or called DNS context), and the EASDF context includes the notification endpoint for the DNS response message as the center SMF.

[0422] S602, the EASDF sends a DNS context notification request to the center SMF, and the DNS context notification request includes the address of the first EAS.

[0423] Optionally, the DNS context notification request can also include the identification information of the DNS response message, the FQDN, or the identification information of the EASDF context.

[0424] Optionally, the DNS context notification request can also include first indication information, the first indication information being used to indicate whether the second part EDI of the second EAS deployment information EDI of the center SMF network element includes the address of the first EAS.

[0425] S603a, the center SMF determines whether the second part EDI of the second EDI includes the address of the first EAS.

[0426] S603b, if the second part EDI includes the address of the first EAS, the center SMF determines the first DNAI corresponding to the address of the first EAS.

[0427] It should be understood that if the second part EDI does not include the address of the first EAS, the subsequent possible implementation can refer to the related part of S404b, which will not be repeated here.

[0428] S604, the center SMF sends the first DNAI to the NRF.

[0429] S605, the NRF determines the second local SMF corresponding to the first DNAI, and the second local SMF network element is used to determine the L-PSA accessing the first EAS.

[0430] It should be understood that the detailed processes of S603a, S603b, S604 and S605 can refer to S404a, S404b, S405 and S406 respectively, which will not be repeated here.

[0431] It should be understood that in the method shown in FIG. 6, the first local SMF and the second local SMF can be the same or different.

[0432] In the above technical solution, the second local SMF network element capable of identifying the first EAS is determined directly through the central SMF network element and the NRF network element, so that the second local SMF completes the discovery process of the EAS in the subsequent process, directly avoiding the situation that the first local SMF cannot identify the first EAS, thereby improving the success rate of discovering the EAS.

[0433] S606a, the NRF sends the address of the second local SMF network element to the AMF;

[0434] S607a, the AMF sends the session management related information to the second local SMF, and the session management related information includes the address of the central SMF.

[0435] Optionally, the session management related information can also include session management context ID, address of the first local SMF and the like, and the session management context ID points to the first local SMF.

[0436] S606b, the NRF sends the address of the second local SMF network element to the central SMF;

[0437] S607b, the central SMF sends the session management related information to the second local SMF, and the session management related information includes the address of the central SMF.

[0438] It should be understood that in the method shown in FIG. 6, since the first local SMF cannot obtain the address of the first EAS, the second local SMF obtains the address of the first EAS from the central SMF.

[0439] S608, the second local SMF obtains the address of the first EAS.

[0440] Specifically, the second local SMF sends a first request message to the central SMF, the first request message is used to request edge computing related information, and the central SMF sends the address of the first EAS to the second local SMF.

[0441] S609, the second local SMF determines the L-PSA accessing the first EAS.

[0442] S610, the central SMF and the second local SMF realize the construction of the forwarding tunnel including the nodes of the first EAS by inserting the splitting point.

[0443] S611, the central SMF informs the EASDF to update the DNS message processing rule. The updated DNS message processing rule is used to instruct the EASDF network element to send the buffered DNS response message to the UE. The updated DNS message processing rule includes the identification information.

[0444] It should be understood that the detailed processes of S609, S610 and S611 can be referred to S410, S411 and S412 respectively, which will not be repeated here.

[0445] It should be understood that in the case where the first local SMF configures the notification endpoint for the DNS response message to the central SMF, the steps S603b to S611 are the second mode of EAS discovery through the second local SMF corresponding to the address of the first EAS.

[0446] FIG. 7 is a flow diagram of another communication method according to an embodiment of the present application. It should be understood that the related description of the execution subject in FIG. 7 can be referred to FIG. 5, which will not be repeated here.

[0447] S701, the pre-step of the EAS discovery process is implemented through the first local SMF.

[0448] It should be understood that the pre-step can include steps such as establishing a PDU session, selecting an EASDF, selecting a first local SMF, configuring a DNS message processing rule, etc. For details, please refer to the steps shown in FIG. 3.

[0449] Among them, the first local SMF configures the notification endpoint for the DNS response message to the central SMF.

[0450] S702, the DNS server sends the DNS response message to the EASDF, and the EASDF receives the DNS response message from the DNS server.

[0451] Among them, the DNS response message includes the address of the first EAS and the FQDN.

[0452] S703, the EASDF sends a DNS context notification request to the central SMF, and the central SMF receives the DNS context notification request from the EASDF.

[0453] Among them, the DNS context notification request includes the address of the first EAS.

[0454] Optionally, the DNS context notification request can also include identification information of the DNS response message, which is used to identify the DNS response message.

[0455] It should be understood that the identification information of the DNS response message is obtained by the EASDF according to the DNS message processing rule. Specifically, the EASDF matches the DNS response message according to the FQDN to generate the identification information of the DNS response message.

[0456] It should also be understood that the embodiments of the present application do not limit the number of addresses of the first EAS, and the first EAS can be one or more.

[0457] Optionally, the DNS context notification request can further include identification information of the EASDF context, the FQDN, or address information of the EASDF. The identification information of the EASDF context can also be referred to as the identification information of the DNS context, and the identification information of the EASDF context corresponds to the PDU session.

[0458] In a possible implementation, the DNS context notification request can further include first indication information, the first indication information being used to indicate whether the second part EDI of the second EDI of the central SMF determines the address of the first EAS.

[0459] It should be understood that the second part EDI of the second EDI can refer to S404a, which will not be repeated here.

[0460] S704a, the central SMF determines whether the second part EDI includes the address of the first EAS.

[0461] S704b, the central SMF determines the first DNAI corresponding to the address of the first EAS according to the second part EDI.

[0462] It should be understood that the detailed processes of S704a and S704b can refer to S505a and S505b respectively, which will not be repeated here.

[0463] The first local SMF is determined in the following steps:

[0464] S705a-1, the central SMF sends the first DNAI to the AMF.

[0465] S705a-2, the AMF sends the first DNAI to the NRF.

[0466] S706a, the NRF determines the second local SMF corresponding to the first DNAI.

[0467] S707a, the NRF sends the address of the second local SMF to the AMF.

[0468] S708a, the AMF sends the related information of the session management to the second local SMF, and the related information of the session management includes the address of the central SMF.

[0469] Optionally, the AMF can also send the location information of the UE to the second local SMF.

[0470] The second way of determining the second local SMF includes the following steps:

[0471] S705b, the central SMF sends the first DNAI to the NRF.

[0472] S706b, the NRF determines the second local SMF corresponding to the first DNAI.

[0473] S707b, the NRF sends the address of the second local SMF to the central SMF.

[0474] S708b, the central SMF sends the related information of the session management to the second local SMF, and the related information of the session management includes the address of the central SMF.

[0475] Optionally, in the above two ways, the related information of the session management can also include the session management context ID or the address of the first local SMF, and the session management context ID points to the first local SMF.

[0476] The second local SMF obtains the first EAS in the following way:

[0477] S709, the second local SMF sends a first request message to the central SMF, and the first request message is used to request the related information of edge computing.

[0478] S710, the central SMF sends the address of the first EAS to the second local SMF.

[0479] Optionally, the second local SMF can also obtain the first DNAI corresponding to the address of the first EAS through S710.

[0480] S711, the second local SMF determines the target anchor network element according to the address of the first EAS and the third EDI.

[0481] S712, the second local SMF and the central SMF jointly complete the insertion of the target anchor network element and construct a forwarding tunnel.

[0482] The first way of updating the DNS message processing rule:

[0483] S713a-1, the central SMF sends a second message to the first local SMF, and the second message includes the identification information of the DNS response message.

[0484] S713a-2, the first local SMF generates an updated DNS message processing rule, and the updated DNS message processing rule is used to instruct the EASDF network element to send the cached DNS response message to the UE.

[0485] S713a-3, the first local SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the identification information of the DNS response message.

[0486] The second updating manner of the DNS message processing rule:

[0487] S713b-1, the central SMF generates an updated DNS message processing rule, and the updated DNS message processing rule is used to instruct the EASDF network element to send the buffered DNS response message to the UE.

[0488] S713b-2, the central SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the identification information of the DNS response message.

[0489] S714: The EASDF forwards the buffered DNS response message to the UE.

[0490] It should be understood that the detailed processes of S711, S712, S713a-1, S713a-2, S713a-3, S713b-1, S713b-2 and S714 can be respectively referred to S512, S513, S514a-1, S514a-2, S514a-3, S514b-1, S514b-2 and S515, which will not be described here.

[0491] It should be understood that in the case that the first local SMF configures the notification endpoint for the DNS response message as the central SMF to the EASDF, the steps of S704b to S714 are the second manner of completing the EAS discovery by the second local SMF corresponding to the address of the first EAS.

[0492] FIG. 8 is a flow diagram of another communication method provided by the embodiments of the present application. It can be understood that the method shown in FIG. 8 is taken as an example to illustrate the corresponding method with the EASDF network element, the central SMF network element and the first local SMF network element as the execution subject of the interaction, but the present application does not limit the execution subject of the interaction. For example, the method implemented by the central SMF network element can also be implemented by the module (such as a chip, a chip system or a processor) of the central SMF network element, and can also be implemented by a logical node, a logical module or software capable of implementing all or part of the functions of the central SMF network element. When the execution subject is other network elements, similar understanding can be made, which will not be described here.

[0493] S801, the EASDF sends a DNS context notification request to the first local SMF network element, and the DNS context notification request includes the address of the first EAS, the identification information of the DNS response message and the FQDN.

[0494] It should be understood that in the method shown in FIG. 8, after the EASDF receives the DNS response message sent by the DNS server, the notification endpoint corresponding to the DNS response message is the first local SMF network element.

[0495] S802, the first local SMF determines whether the address of the first EAS is within the scope of the first EAS deployment information (first EDI).

[0496] When the address of the first EAS is not within the scope of the first EDI, S803, the first local SMF sends a third message to the central SMF, and the third message includes identification information of the DNS response message.

[0497] Optionally, when the address of the first EAS is within the scope of the first EDI, the first local SMF inserts a split point (ULCL / BP) and a local anchor point (L-PSA) according to the IP address of the first EAS and the first EDI, and configures a split rule on the split point.

[0498] As a possible implementation, the third message can further include third indication information, and the third indication information is used to instruct the central SMF to notify the EASDF to update the DNS message processing rule.

[0499] S804, the central SMF notifies the EASDF to update the DNS message processing rule, and the updated DNS message processing rule is used to instruct the EASDF to generate a DNS query message with an ECS option for the FQDN. Empty and delete the DNS response message, and the updated DNS message processing rule includes the identification information of the DNS response message.

[0500] Specifically, one way to send the updated DNS message processing rule can include the following steps:

[0501] S804a-1, the central SMF sends a fourth message to the first local SMF, and the fourth message includes the identification information.

[0502] Optionally, the fourth message further includes fourth indication information, and the fourth indication information is used to instruct the first local SMF to generate and send the updated DNS message processing rule to the EASDF.

[0503] S804a-2, the first local SMF sends the updated DNS message processing rule to the EASDF.

[0504] Specifically, another way to send the updated DNS message processing rule can include the following steps:

[0505] S804b, the central SMF sends the updated DNS message processing rule to the EASDF.

[0506] In a possible implementation, the updated DNS message processing rule is specifically used to instruct the EASDF to extract the FQDN from the original DNS query message, and generate a new DNS query message with an empty ECS option for the FQDN and delete the DNS response message.

[0507] It should be understood that in this implementation, the fourth message does not include the FQDN, and the updated DNS message processing rule also does not include the FQDN.

[0508] In a possible implementation, the updated DNS message processing rule is specifically used to instruct the EASDF network element to directly generate a new DNS query message with an empty ECS option for the FQDN and delete the DNS response message.

[0509] It should be understood that in this implementation, the fourth message also includes the FQDN, and the updated DNS message processing rule also includes the FQDN.

[0510] It should be understood that the original DNS query message and the new DNS query message are both for the FQDN, and the difference between the two is whether the ECS option is empty.

[0511] In the above technical solution, when the first local SMF network element cannot identify the first EAS, the DNS message processing rule can be updated by the central SMF network element, and a DNS query message with an empty ECS option for the FQDN is generated, so that the service for the FQDN can be returned to the processing mode of non-edge computing service, thereby avoiding the situation that the EAS flow discovery fails due to the first local SMF network element being unable to identify the first EAS, and thus the success rate of discovering the EAS is improved.

[0512] Optionally, after S803, the central SMF determines whether the address of the first EAS belongs to the range of the first part EDI of the second EDI. If the address of the first EAS does not belong to the range of the first part EDI, the central SMF determines whether the first part EDI includes the FQDN, and if the first part EDI does not include the FQDN, S804 is performed.

[0513] Optionally, after S803, if the central SMF determines that the first part EDI does not include the address of the first ESA, S804 is performed.

[0514] Optionally, after S803, if the central SMF determines that the first part EDI does not include the FQDN, S804 is performed.

[0515] Optionally, after S803, if the central SMF determines that the second part EDI does not include the address of the first EAS, S804 is performed.

[0516] It should be understood that the detailed explanation of the first EDI and the second EDI can refer to the related explanation in S404a of FIG. 4, which will not be repeated here.

[0517] It should also be understood that if the first part of the EDI whether including the address of the first EAS is regarded as condition one, the first part of the EDI whether including the FQDN is regarded as condition two, and the second part of the EDI whether including the address of the first EAS is regarded as condition three, the condition of performing S804 can be a combination of at least one of the condition one, the condition two or the condition three, and the order of the combination is not limited by the embodiments of the present application.

[0518] It should be understood that S804 is a processing manner of returning non-EC services.

[0519] FIG. 9 is a flow diagram of another communication method provided by the embodiments of the present application. The method shown in FIG. 9 is used to illustrate the corresponding method by taking the DNS server, the EASDF network element, the central SMF network element, the first local SMF network element, and the UE as the execution subject of the interaction, but the present application does not limit the execution subject of the interaction. For example, the method implemented by the central SMF network element can also be implemented by a module (such as a chip, a chip system or a processor) of the central SMF network element, and can also be implemented by a logical node, a logical module or software capable of implementing all or part of the functions of the central SMF network element. When the execution subject is other network elements, similar understanding can be made, which will not be repeated here.

[0520] S901, performing a pre-step of the EAS discovery process by the first local SMF.

[0521] S902, the DNS server sends a DNS response message to the EASDF, and the EASDF receives the DNS response message from the DNS server.

[0522] S903, the EASDF sends a DNS context notification request to the first local SMF, and the first local SMF receives the DNS context notification request from the EASDF.

[0523] S904, the first local SMF determines whether the address of the first EAS is within the range of the first EDI.

[0524] It should be understood that the detailed description of S901, S902, S903 and S904 in FIG. 9 can refer to S501, S502, S503 and S504a respectively, which will not be repeated here.

[0525] Optionally, if the address of the first EAS is within the range of the first EDI, the L-PSA corresponding to the first EAS is determined according to the address of the UE, the load of the first EAS or the N6 delay. The subsequent detailed steps can refer to FIG. 3, which will not be repeated here.

[0526] S905, if the address of the first EAS is not within the scope of the first EDI, the first local SMF sends a third message to the central SMF, the third message comprising the identification information of the DNS response message.

[0527] Optionally, the third message can further comprise the address of the first EAS, the identification information of the EASDF context, the FQDN or the address information of the EASDF. Wherein, the identification information of the EASDF context can also be referred to as the identification information of the DNS context, and the identification information of the EASDF context corresponds to the PDU session.

[0528] Optionally, the third message can further comprise third indication information, the third indication information being used to instruct the central SMF to inform the EASDF to update the DNS message processing rule.

[0529] S906, the central SMF informs the EASDF to update the DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message, and the updated DNS message processing rule comprising the identification information of the DNS response message.

[0530] Optionally, additional steps can be included between S905 and S906, which can be referred to S804 and will not be described here.

[0531] The third update mode of the DNS message processing rule:

[0532] S906a-1, the central SMF sends a fourth message to the first local SMF, the fourth message comprising the identification information of the DNS response message.

[0533] Optionally, the fourth message further comprises fourth indication information, the fourth indication information being used to instruct the first local SMF to generate and send the updated DNS message processing rule to the EASDF.

[0534] Optionally, the fourth message can further comprise the identification information of the EASDF context or the FQDN.

[0535] S906a-2, the first local SMF generates the updated DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF to generate a DNS query message with an empty ECS option for the FQDN and delete the DNS response message.

[0536] S906a-3, the first local SMF sends the updated DNS message processing rule to the EASDF, the updated DNS message processing rule comprising the identification information of the DNS response message.

[0537] In a possible implementation, if the fourth message does not include the FQDN, the updated DNS message processing rule also does not include the FQDN, and the updated DNS message processing rule is specifically used to instruct the EASDF to extract the FQDN from the original DNS query message, and generate a new DNS query message with the ECS option of the FQDN being empty and delete the DNS response message.

[0538] In a possible implementation, if the fourth message includes the FQDN, the updated DNS message processing rule also includes the FQDN, and the updated DNS message processing rule is specifically used to instruct the EASDF network element to directly generate a new DNS query message with the ECS option of the FQDN being empty and delete the DNS response message.

[0539] Optionally, the updated DNS message processing rule can also be used to instruct the EASDF to send a new DNS response message to the UE after receiving the new DNS response message including the FQDN.

[0540] The fourth updating manner of the DNS message processing rule:

[0541] S906b-1, the central SMF generates an updated DNS message processing rule, and the updated DNS message processing rule is used to instruct the EASDF to generate a DNS query message with the ECS option of the FQDN being empty and delete the DNS response message.

[0542] S906b-2, the central SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the identification information of the DNS response message.

[0543] Optionally, the central SMF can also send the identification information of the EASDF context or the FQDN to the EASDF.

[0544] It should be understood that the specific content instructed by the updated DNS message processing rule can refer to the related description in S906a-3, which is not described here.

[0545] S907, the EASDF generates a new DNS query message #1 with the ECS option of the FQDN being empty according to the updated processing rule.

[0546] It should be understood that if the updated processing rule includes the FQDN, the requirement for the capability of the EASDF is lower. If the updated processing rule does not include the FQDN, the requirement for the capability of the EASDF is higher, because the EASDF also needs to extract the FQDN from the original DNS query message.

[0547] S908, the EASDF sends a new DNS query message #1 to the DNS server.

[0548] S909, the EASDF receives a new DNS response message #1 from the DNS server.

[0549] S910, the EASDF sends the new DNS response message #1 to the UE.

[0550] Specifically, the EASDF sends the new DNS response message #1 to the UE directly after matching the FQDN included in the new DNS response message according to the updated DNS message processing rule.

[0551] It should be understood that S906 to S910 are the processing mode of returning non-EC services.

[0552] FIG. 10 is a flow diagram of another communication method according to an embodiment of the present application.

[0553] S1001, the EASDF sends a DNS context notification request to a first local SMF network element, the DNS context notification request including an address of the first EAS and a FQDN.

[0554] It should be understood that in the method shown in FIG. 10, after the EASDF receives the DNS response message sent by the DNS server, the notification endpoint corresponding to the DNS response message is the first local SMF network element.

[0555] S1002, the first local SMF network element determines whether the address of the first EAS belongs to the range of first EAS deployment information (first EDI).

[0556] When the address of the first EAS does not belong to the range of the first EDI, S1003, the first local SMF sends a third message to the central SMF, the third message including the address of the first EAS.

[0557] As a possible implementation, the third message further includes fifth indication information, the fifth indication information being used to indicate the central SMF to determine whether the address of the first EAS belongs to the range of a first part EDI of the second EDI of the central SMF network element.

[0558] Optionally, the third message can further include identification information of the DNS response message, identification information of the EASDF context, the FQDN, or address information of the EASDF. The identification information of the EASDF context can also be referred to as the identification information of the DNS context, and the identification information of the EASDF context corresponds to a PDU session.

[0559] It should be understood that the detailed explanation of the first EDI and the second EDI can be referred to the related part of FIG. 4, which will not be repeated here.

[0560] Optionally, when the address of the first EAS belongs to the scope of the first EDI, the first local SMF inserts a split point (UL CL / BP) and a local anchor point (L-PSA) according to the IP address of the first EAS and the first EDI, and configures a split rule on the split point.

[0561] S1004, the central SMF determines whether the first part EDI of the second EDI includes the address of the first EAS.

[0562] Optionally, when the first part EDI does not include the address of the first EAS, S804 is performed. The detailed steps of S804 can refer to FIG. 8.

[0563] Optionally, when the first part EDI does not include the address of the first EAS, the central SMF determines whether the first part EDI includes the FQDN.

[0564] Optionally, when the first part EDI does not include the address of the first EAS, the central SMF determines whether the second part EDI includes the address of the first EAS.

[0565] Optionally, when the first part EDI includes the address of the first EAS, the central SMF determines whether the FQDN corresponding to the address of the first EAS in the first part EDI is consistent with the FQDN included in the third message.

[0566] S1005, when the first part EDI includes the address of the first EAS, the central SMF inserts a split point according to the address of the first EAS, the split point can include UL CL / BP and / or L-PSA, and configures a split rule to the split point.

[0567] It should be understood that the specific process can refer to the related description of FIG. 2, which will not be repeated here.

[0568] Wherein, the first part EDI including the address of the first EAS can also be understood as the first part EDI including the first DNAI corresponding to the first EAS, and the N6 transmission routing information (for example, the L-PSA and / or UL CL / BP corresponding to the first DNAI) corresponding to the first DNAI. Alternatively, the first part EDI including the address of the first EAS can also be understood as the first part EDI including the L-PSA accessing the first EAS.

[0569] Optionally, when the first part EDI includes the address of the first EAS, and the FQDN corresponding to the address of the first EAS in the first part EDI is consistent with the FQDN included in the third message, the central SMF inserts a split point according to the address of the first EAS, the split point can include UL CL / BP and / or L-PSA, and configures a split rule to the split point.

[0570] S1006, the central SMF instructs the EASDF to forward the cached DNS response message to the UE.

[0571] S1007, the EASDF sends the DNS response message to the UE.

[0572] It should be understood that S1005 to S1007 are a discovery procedure of the first EAS implemented by the central SMF.

[0573] In the above technical solution, if the EAS deployment information corresponding to the EC service supported by the central SMF can include the address of the first EAS, it is further helpful for the central SMF to complete the discovery procedure of the EAS when the first local SMF cannot identify the address of the first EAS.

[0574] FIG. 11 is a flow diagram of another communication method provided by an embodiment of the present application.

[0575] S1101 and S1102 can refer to S1001 and S1002, which are not repeated here.

[0576] S1103, if the address of the first EAS is not in the range of the first EDI, the first local SMF sends a sixth message to the central SMF, and the sixth message includes the FQDN.

[0577] Optionally, the sixth message can also include seventh indication information, and the seventh indication is used to indicate whether the first part EDI of the second EDI includes the FQDN.

[0578] Optionally, the sixth message can also include identification information of the DNS response message, identification information of the EASDF context (for example, EASDF context ID), address information of the first EAS or the EASDF.

[0579] S1104, the central SMF determines whether the first part EDI of the second EDI includes the FQDN.

[0580] It should be understood that the related explanations of the first EDI and the second EDI can refer to S404a, which are not repeated here.

[0581] Optionally, if the first part EDI does not include the FQDN, S804 is executed. The detailed steps of S804 can refer to FIG. 8.

[0582] Optionally, when the first part EDI does not include the FQDN, the central SMF determines whether the first part EDI includes the address of the first EAS.

[0583] Optionally, when the first part of the EDI does not include the FQDN, the central SMF determines whether the second part of the EDI includes the address of the first EAS.

[0584] If the first part of the EDI includes the FQDN, S1105, generates, according to the FQDN, the location information of the user equipment UE, and the first part of the second EDI, the information indicating the location information of the UE.

[0585] In other words, if the central SMF supports the EC service of the FQDN, S1105 is performed.

[0586] S1106, the central SMF sends the updated DNS message processing rule to the EASDF, the updated DNS message processing rule being used to instruct the EASDF to generate the ECS option, the ECS option including the information indicating the location information of the UE, add the ECS option to the DNS query message and delete the DNS response message, the DNS query message being regenerated for the FQDN, and the updated DNS message processing rule including the first information and the identification information.

[0587] In the above technical solution, since the central SMF supports the edge computing service for the FQDN, the information indicating the location of the UE generated by the central AMF can be used to realize the completion of the subsequent EAS discovery process by the central AMF. In this way, in combination with the current central SMF discovery EAS process, the situation that the first local SMF cannot identify the first EAS and causes the EAS discovery process to fail can be effectively coped with.

[0588] S1106a-1, the central SMF sends a fifth message to the first local SMF, the fifth message including the identification information of the DNS response message and the first information, the first information being used to indicate the information of the location of the UE.

[0589] It should be understood that the first information is also used to indicate the information in the updated DNS message processing rule generated by the first local SMF network element according to the first information, which instructs the EASDF network element to generate the ECS option.

[0590] Optionally, the fifth message further includes sixth indication information, the sixth indication information being used to instruct the first local SMF to generate and send the updated DNS message processing rule to the EASDF.

[0591] Optionally, the fifth message can further include the identification information of the EASDF context or the FQDN.

[0592] S1106a-2, the first local SMF sends the updated DNS message processing rule to the EASDF, the updated DNS message processing rule comprising the second information and the identification information of the DNS response message. The second information is generated according to the first information, and the first information and the second information can be the same or different. The second information is used to indicate the location information of the UE.

[0593] Optionally, the updated DNS message processing rule can further comprise the identification information of the EASDF context or the FQDN.

[0594] In a possible implementation, if the fifth message does not comprise the FQDN, the updated DNS message processing rule also does not comprise the FQDN. The updated DNS message processing rule is specifically used to instruct the EASDF to extract the FQDN from the original DNS query message, generate an ECS option comprising the information indicating the location of the UE, add the ECS option to the DNS query message, and delete the DNS response message. The DNS query message is regenerated for the FQDN.

[0595] In a possible implementation, if the fifth message comprises the FQDN, the updated DNS message processing rule also comprises the FQDN. The updated DNS message processing rule is specifically used to instruct the EASDF network element to directly generate an ECS option comprising the information indicating the location of the UE, add the ECS option to the DNS query message, and delete the DNS response message. The DNS query message is regenerated for the FQDN.

[0596] Optionally, the updated DNS message processing rule can be further used to instruct the EASDF to, after receiving a new DNS response message comprising the FQDN, carry the address of a new EAS in the new DNS response message on a new DNS context notification request to the central SMF.

[0597] S1106b, the central SMF sends the updated DNS message processing rule to the EASDF, the updated DNS message processing rule comprising the information indicating the location of the UE and the identification information of the DNS response message.

[0598] Optionally, the central SMF can further send the identification information of the EASDF context or the FQDN to the EASDF.

[0599] It should be understood that the specific content instructed by the updated DNS message processing rule can refer to the related description in S1106a-2, which will not be repeated here.

[0600] S1107, the EASDF generates an ECS option, the ECS option includes information indicating the location of the UE, and adds the ECS option to a new DNS query message, wherein the new DNS query message is regenerated for the FQDN.

[0601] S1108, the EASDF sends the new DNS query message to the DNS server, and the ECS option included in the new DNS query message includes information indicating the location of the UE.

[0602] S1109, the DNS server sends a new DNS response message to the EASDF, and the new DNS response message includes the address of the new EAS, which is obtained according to the ECS option in the new DNS query message.

[0603] S1110, the EASDF sends a new DNS context notification request to the central SMF, and the new DNS context notification request includes the address of the new EAS.

[0604] It should be understood that S1105 to S1110 are steps of re-implementing the EAS discovery process for the FQDN through the central SMF.

[0605] FIG. 12 is a flow diagram of another communication method provided by an embodiment of the application.

[0606] S1201 to S1204 can refer to S1101 to S1104, which will not be repeated here.

[0607] Specifically, the fifth update manner of the DNS message processing rule is:

[0608] S1205a, the central SMF generates first information according to the FQDN, the location information of the user equipment UE, and the first part of the second EDI, and the first information is used to indicate the location information of the UE.

[0609] S1206a-1, the central SMF sends a fifth message to the first local SMF, and the fifth message includes identification information of the DNS response message and the first information.

[0610] It should be understood that the first information is also used to indicate information in the updated DNS message processing rule generated by the first local SMF network element according to the first information, which indicates that the EASDF network element generates an ECS option.

[0611] Optionally, the fifth message further includes sixth indication information, and the sixth indication information is used to indicate that the first local SMF generates and sends the updated DNS message processing rule to the EASDF.

[0612] Optionally, the fifth message can further include identification information of the EASDF context or the FQDN.

[0613] S1206a-2, the first local SMF generates an updated DNS message processing rule, the updated DNS message processing rule is used to instruct the EASDF to generate an ECS option, the ECS option includes the second information, and the ECS option is added to the DNS query message and the DNS response message is deleted, the DNS query message is regenerated for the FQDN.

[0614] Specifically, the first local SMF generates the second information according to the first information, and the second information is information indicating the EASDF network element to generate the ECS option in the updated DNS message processing rule. The first information and the second information can be the same or different.

[0615] S1206a-3, the first local SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the second information and the identification information of the DNS response message.

[0616] Optionally, the updated DNS message processing rule can also include identification information of the EASDF context or the FQDN.

[0617] It should be understood that the specific content of the updated DNS message processing rule for indication can refer to the related description in S1106a-2, which will not be repeated here.

[0618] Optionally, the updated DNS message processing rule can also be used to instruct the EASDF to report the address of the new EAS in the new DNS response message to the central SMF on the new DNS context notification request after receiving the new DNS response message including the FQDN.

[0619] S1207, the EASDF generates a new DNS query message #2 including the ECS option of the second information.

[0620] Sixth update mode of the DNS message processing rule:

[0621] S1205b, the central SMF generates third information according to the FQDN, the location information of the user equipment UE and the first part EDI of the second EDI, and the third information is used to indicate the location information of the UE.

[0622] S1206b-1, the central SMF generates an updated DNS message processing rule, and the updated DNS message processing rule includes the third information.

[0623] S1206b-2, the central SMF sends the updated DNS message processing rule to the EASDF, and the updated DNS message processing rule includes the third information and the identification information of the DNS response message.

[0624] Optionally, the central SMF can also send the identification information or the FQDN of the EASDF context to the EASDF.

[0625] It should be understood that the updated DNS message processing rule can refer to the relevant description in S1106a-2 for the indicated content, which will not be repeated here.

[0626] S1207b, the EASDF generates an ECS option including the third information and adds the ECS option to the new DNS query message #2, wherein the new DNS query message #2 is regenerated for the FQDN.

[0627] It should be understood that the first information, the second information and the third information can be the same or different, but the first information, the second information and the third information can all be information for indicating the UE location.

[0628] It should be understood that the ECS option information in the original DNS query message sent by the EASDF to the DNS server before S1201 is generated by the EASDF according to the address information received from the first local SMF and is for the FQDN. In contrast, the ECS option included in the new DNS query message #2 is generated according to the third information or the second information and is for the FQDN.

[0629] S1208, the EASDF sends the new DNS query message #2 to the DNS server, and the ECS option included in the new DNS query message #2 includes the third information or the second information.

[0630] S1209, the DNS server sends a new DNS response message #2 to the EASDF, and the new DNS response message #2 includes the address of the new EAS, which is obtained according to the ECS option in the new DNS query message #2.

[0631] S1210, the EASDF sends a new DNS context notification request to the central SMF, and the new DNS context notification request includes the address of the new EAS.

[0632] It should be understood that S1205a to S1207a and S1208 to S1210 are steps for re-implementing the EAS discovery process for the FQDN through the central SMF. Alternatively, S1205b to S1207b and S1208 to S1210 are steps for re-implementing the EAS discovery process for the FQDN through the central SMF.

[0633] If the first part of the second EDI of the central SMF includes the address of the first EAS is regarded as condition one, the first part of the second EDI of the central SMF includes the FQDN is regarded as condition two, and the second part of the second EDI of the central SMF includes the address of the first EAS is regarded as condition three, at least one of the condition one, the condition two or the condition three can be used to implement the discovery procedure of the EAS.

[0634] It should be understood that the embodiments of the present application do not limit the specific number of combined conditions, for example, the condition one, the condition two or the condition three can be used alone, or any two of the three conditions can be combined, or all of the three conditions can be used. In addition, the embodiments of the present application do not limit the execution order of the condition one, the condition two or the condition three.

[0635] Specific examples can include: if one condition is used alone, the condition one, the condition two or the condition three can be used alone. If two conditions are combined, the condition one and the condition two can be combined, the condition two and the condition one can be combined, the condition one and the condition three can be combined, the condition three and the condition one can be combined, the condition two and the condition three can be combined, and the condition three and the condition two can be combined. If three conditions are combined, the condition one, the condition two and the condition three can be combined, the condition one, the condition three and the condition two can be combined, the condition two, the condition one and the condition three can be combined, the condition two, the condition three and the condition one can be combined, the condition three, the condition one and the condition two can be combined, and the condition three, the condition two and the condition one can be combined. Among them, the execution order has been considered in the specific examples.

[0636] The following will be illustrated with reference to FIG. 13 to FIG. 16.

[0637] It should be understood that FIG. 13 and FIG. 14 are example illustrations under the premise that the first local SMF determines that the first EDI does not include the address of the first EAS. FIG. 15 and FIG. 16 are example illustrations under the premise that the central SMF directly receives the DNS context notification request.

[0638] FIG. 13 is a flow diagram of another communication method provided by the embodiments of the present application.

[0639] S1301 to S1305 can refer to S501 to S504b, and will not be repeated here.

[0640] S1306, the central SMF determines whether the first part of the second EDI includes the address of the first EAS.

[0641] If the first part of the EDI includes the address of the first EAS, S1307, the discovery procedure of the first EAS is implemented through the central SMF.

[0642] Specifically, S1307 may include steps S1005 to S1007 shown in FIG10 .

[0643] If the first part of the EDI does not include the address of the first EAS, S1308, it is determined whether the first part of the EDI of the second EDI includes the FQDN.

[0644] Optionally, if the first part of the EDI does not include the address of the first EAS, the processing method for returning the non-EC service may include S804 of FIG. 8 or S906 to S910 of FIG. 9 .

[0645] If the first part EDI of the second EDI includes the FQDN, S1309 , the EAS discovery process is re-implemented for the FQDN through the central SMF.

[0646] Specifically, S1309 may include S1105 to S1110 shown in FIG. 11 , or S1205 a to S1207 a and S1208 to S1210 shown in FIG. 12 , or S1205 b to S1207 b and S1208 to S1210 shown in FIG. 12 .

[0647] Optionally, if the first part EDI of the second EDI does not include the FQDN, the processing method for returning the non-EC service may include S804 of FIG. 8 or S906 to S910 of FIG. 9 .

[0648] Alternatively, if the first EDI portion of the second EDI includes the FQDN, S1310 , it is determined whether the second EDI portion of the second EDI includes the address of the first EAS.

[0649] Optionally, if the second part EDI of the second EDI includes the address of the first EAS, S1311 , the first method of EAS discovery is completed through the second local SMF corresponding to the address of the first EAS.

[0650] Specifically, S1311 may include S404b to S412 shown in FIG. 4 , or S505b to S515 shown in FIG. 5 .

[0651] Optionally, if the second part EDI of the second EDI does not include the address of the first EAS, S1312, a method for returning the non-EC service is used. Specifically, the method for returning the non-EC service may include S804 of FIG. 8 or S906 to S910 of FIG. 9 .

[0652] FIG14 is a flow chart of another communication method provided in an embodiment of the present application.

[0653] S1401 to S1405 can refer to S501 to S504b, which are not repeated here.

[0654] S1406, the central SMF determines whether the second part of the second EDI includes the address of the first EAS.

[0655] If the second part of the EDI includes the address of the first EAS, S1407, the first EAS discovery mode is completed through the second local SMF corresponding to the address of the first EAS.

[0656] Specifically, S1407 can include S404b to S412 shown in FIG. 4, or S505b to S515 shown in FIG. 5.

[0657] Alternatively, if the second part of the EDI does not include the address of the first EAS, the processing mode of the non-EC service is returned. Specifically, the processing mode of the non-EC service can include S804 of FIG. 8, or S906 to S910 of FIG. 9.

[0658] If the second part of the EDI does not include the address of the first EAS, S1408, the central SMF determines whether the first part of the second EDI includes the address of the first EAS.

[0659] If the first part of the EDI includes the address of the first EAS, S1409, the discovery process of the first EAS is implemented through the central SMF.

[0660] Specifically, S1409 can include steps S1005 to S1007 shown in FIG. 10.

[0661] Alternatively, if the first part of the EDI does not include the address of the first EAS, the processing mode of the non-EC service is returned. Specifically, the processing mode of the non-EC service can include S804 of FIG. 8, or S906 to S910 of FIG. 9.

[0662] If the first part of the EDI does not include the address of the first EAS, S1410, it is determined whether the first part of the second EDI includes the FQDN.

[0663] If the first part of the second EDI includes the FQDN, S1411, the EAS discovery process is re-implemented through the central SMF for the FQDN.

[0664] Specifically, S1411 can include S1105 to S1110 shown in FIG. 11, or S1205a to S1207a and S1208 to S1210 shown in FIG. 12, or S1205b to S1207b and S1208 to S1210 shown in FIG. 12.

[0665] Optionally, if the first part of the second EDI does not include the FQDN, the processing manner of the non-EC service is returned. Specifically, the processing manner of the non-EC service can include S804 of FIG. 8, or S906 to S910 of FIG. 9.

[0666] FIG. 15 is a flow diagram of another communication method provided by an embodiment of the present application.

[0667] S1501 to S1503 can refer to S701 to S703, and will not be repeated here.

[0668] S1504 to S1508 can refer to S1306 to 1310, and will not be repeated here.

[0669] If the second part of the EDI includes the address of the first EAS, S1509, the second local SMF corresponding to the address of the first EAS is used to complete the EAS discovery in the second manner.

[0670] Specifically, S1509 can include S603b to S611 shown in FIG. 6, or S704b to S714 shown in FIG. 7.

[0671] Optionally, if the second part of the EDI does not include the address of the first EAS, the processing manner of the non-EC service is returned. Specifically, the processing manner of the non-EC service can include S804 of FIG. 8, or S906 to S910 of FIG. 9.

[0672] FIG. 16 is a flow diagram of another communication method provided by an embodiment of the present application.

[0673] S1601 to S1603 can refer to S701 to S703, and will not be repeated here.

[0674] S1604, determine whether the second part of the second EDI includes the address of the first EAS.

[0675] If the second part of the EDI includes the address of the first EAS, S1605, the second local SMF corresponding to the address of the first EAS is used to complete the EAS discovery in the second manner.

[0676] Specifically, S1605 can include S603b to S611 shown in FIG. 6, or S704b to S714 shown in FIG. 7.

[0677] S1606 to S1610 can refer to S1408 to S1412, and will not be repeated here.

[0678] The above, in combination with FIG. 4 to FIG. 16, details the communication method provided by the embodiments of the present application. It can be understood that in order to realize the above functions, it contains the hardware structure and / or software module corresponding to the execution of each function.

[0679] Those skilled in the art should understand that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is realized in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to realize the described functions for specific applications, but such implementation should not be considered beyond the scope of the present application.

[0680] The following describes the communication apparatus provided by the embodiments of the present application in combination with FIG. 17 to FIG. 19. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments, and therefore, the content not described in detail can be referred to the method embodiments described above, and part of the content will not be described again for the sake of brevity.

[0681] FIG. 17 is a schematic diagram of a communication apparatus 1700 provided by an embodiment of the present application. The apparatus 1700 can include a transceiver unit 1710, which can realize corresponding communication functions. The transceiver unit 1710 can also be referred to as a communication interface or a communication unit or an interface unit. Optionally, the apparatus 1700 can also include a processing unit 1720 for data processing. It should be understood that, for the sending and receiving operations and the like involved in the present application, if not specifically stated, or if not contrary to the actual role or inherent logic in the related description, it can be more generally understood as output and input operations, rather than the sending and receiving operations directly performed by the radio frequency circuit and the antenna.

[0682] Optionally, the apparatus 1700 can also include a storage unit, which can be used to store instructions and / or data. The processing unit 1720 can read the instructions and / or data in the storage unit, so that the apparatus realizes the foregoing method embodiments.

[0683] The apparatus 1700 can be used to perform the actions performed by the terminal device in the foregoing method embodiments. At this time, the apparatus 1700 can be a communication device or a component configurable to a communication device. The transceiver unit 1710 is used to perform the transceiver-related operations of the terminal device in the foregoing method embodiments, and the processing unit 1720 is used to perform the processing-related operations of the terminal device in the foregoing method embodiments.

[0684] As a design, the apparatus 1700 is used to perform the actions performed by the central SMF network element of the method embodiments shown in FIG. 4 and FIG. 5. The execution subject can be a chip, a chip system or a processor supporting the implementation of the corresponding method by the central SMF network element, and can also be a logical module or software capable of realizing all or part of the functions of the central SMF network element.

[0685] Specifically, the transceiver 1710 is configured to receive a first message from a first local SMF network element, the first message comprising an address of a first edge application server EAS, the address of the first EAS not being within a scope of first EAS deployment information of the first local SMF network element. The processor 1720 is configured to determine whether a second part of second EAS deployment information EDI of a central SMF comprises the address of the first EAS. The transceiver 1710 is configured to send, to a network repository function NRF network element, a first data network access identifier DNAI corresponding to the address of the first EAS if the second part of the EDI comprises the address of the first EAS, the first DNAI being used to determine a second local SMF network element, the second local SMF network element being used to determine a local protocol data unit session anchor L-PSA that accesses the first EAS.

[0686] Implementations of the method not described in detail can refer to the above method embodiments.

[0687] As a design, the communication apparatus 1700 is configured to perform actions performed by a first local SMF network element in the above method embodiments shown in FIG. 4 and FIG. 5. The execution subject can be a chip, a chip system or a processor supporting the first local SMF network element to implement the corresponding method, and can also be a logical module or software capable of implementing all or part of the first local SMF network element.

[0688] Specifically, the transceiver 1710 is configured to receive a domain name system DNS context notification request from an edge application server discovery function EASDF network element, the DNS context notification request comprising an address of a first edge application server EAS. The processor 1720 is configured to determine whether the address of the first EAS is within a scope of first EAS deployment information of the first local SMF network element. The transceiver 1710 is configured to send, to a central SMF network element, a first message comprising the address of the first EAS if the address of the first EAS is not within the scope of the first EAS deployment information of the first local SMF network element, the address of the first EAS being used to instruct the central SMF network element to determine whether a second part of second EAS deployment information EDI of the central SMF comprises the address of the first EAS, a first data network access identifier DNAI corresponding to the first EAS being used to determine a second local SMF network element, the second local SMF network element being used to determine a local protocol data unit session anchor L-PSA that accesses the first EAS.

[0689] Implementations of the method not described in detail can refer to the above method embodiments.

[0690] As a kind of design, the communication device 1700 is used to execute the action performed by the second local SMF network element of the method embodiment shown in the above figures 4 and 5. The execution subject can be a chip, a chip system or a processor supporting the second local SMF network element to implement the corresponding method, and can also be a logic module or software capable of implementing all or part of the second local SMF network element.

[0691] Specifically, the transceiver 1710 is configured to obtain the address of the first edge application server EAS, and the address of the first EAS does not belong to the first EAS deployment information of the first local SMF network element. The processing unit 1720 is configured to determine a local protocol data unit session anchor L-PSA accessing the first EAS.

[0692] The part not described in detail can refer to the above method embodiment.

[0693] As a kind of design, the device 1700 is used to execute the action performed by the central SMF network element of the method embodiment shown in the above figures 6 and 7. The execution subject can be a chip, a chip system or a processor supporting the central SMF network element to implement the corresponding method, and can also be a logic module or software capable of implementing all or part of the central SMF network element function.

[0694] Specifically, the transceiver 1710 is configured to receive a domain name system DNS context notification request from an edge application server discovery function EASDF network element, and the DNS context notification request includes the address of the first edge application server EAS. The central SMF network element is the notification endpoint of the first local SMF network element configured for the DNS response message to the EASDF network element. The processing unit 1720 is configured to determine whether the second part EDI of the second EAS deployment information EDI of the central SMF network element includes the address of the first EAS. The transceiver 1710 is configured to send the first data network access identifier DNAI corresponding to the address of the first EAS to a network storage function NRF network element if the second part EDI includes the address of the first EAS, and the first DNAI is used to determine a second local SMF network element, and the second local SMF network element is used to determine a local protocol data unit session anchor L-PSA accessing the first EAS.

[0695] The part not described in detail can refer to the above method embodiment.

[0696] As a kind of design, the device 1700 is used to execute the action performed by the central SMF network element of the method embodiment shown in the above figures 8 and 9. The execution subject can be a chip, a chip system or a processor supporting the central SMF network element to implement the corresponding method, and can also be a logic module or software capable of implementing all or part of the central SMF network element function.

[0697] Specifically, the transceiver 1710 is configured to receive a third message from a first local session management function, SMF, network element, the third message comprising identification information and a fully qualified domain name, FQDN. The edge application server discovery function, EASDF, network element is notified to update a DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF network element to generate a DNS query message with an ECS option empty for the FQDN and delete a DNS response message, the updated DNS message processing rule comprising the identification information and the FQDN.

[0698] Implementations where details are not provided can be made according to the above method embodiments.

[0699] As a design, the communication apparatus 1700 is configured to perform actions performed by a first local SMF network element in the above method embodiments shown in FIG. 8 and FIG. 9. The execution subject can be a chip, a chip system or a processor supporting the first local SMF network element to implement the corresponding method, and can also be a logical module or software capable of implementing all or part of the first local SMF network element.

[0700] Specifically, the transceiver 1710 is configured to receive a domain name system, DNS, context notification request from an edge application server discovery function, EASDF, network element, the DNS context notification request comprising an address of a first edge application server, EAS, identification information of a DNS response message and a fully qualified domain name, FQDN. When the address of the first EAS is not within a range of first EAS deployment information of the first local SMF network element, a third message is sent to a central SMF network element, the third message comprising the identification information and the FQDN, the identification information being used to instruct the central SMF network element to notify the EASDF network element to update a DNS message processing rule, the updated DNS message processing rule being used to instruct the EASDF network element to generate a DNS query message with an ECS option empty for the FQDN and delete the DNS response message.

[0701] Implementations where details are not provided can be made according to the above method embodiments.

[0702] As a design, the apparatus 1700 is configured to perform actions performed by a central SMF network element in the above method embodiment shown in FIG. 13. The execution subject can be a chip, a chip system or a processor supporting the central SMF network element to implement the corresponding method, and can also be a logical module or software capable of implementing all or part of the central SMF network element function.

[0703] Specifically, the transceiver 1710 is configured to receive a third message from the first local SMF network element, the third message comprising an address of the first EAS and a fully qualified domain name FQDN. The processing unit 1720 is configured to determine whether the first part of the second EAS deployment information EDI of the central SMF network element includes the FQDN when the first part of the EDI does not include the address of the first EAS. According to the determination result, the EASDF network element is notified to update the DNS message processing rule.

[0704] For the part not described in detail, refer to the above method embodiments.

[0705] As a design, the communication apparatus 1700 is configured to perform the actions performed by the first local SMF network element in the method embodiments shown in FIG. 13. The execution subject can be a chip, a chip system or a processor supporting the first local SMF network element to implement the corresponding method, and can also be a logical module or software capable of implementing all or part of the first local SMF network element.

[0706] Specifically, the transceiver 1710 is configured to receive a domain name system DNS context notification request from an edge application server discovery function EASDF network element, the DNS context notification request comprising an address of a first edge application server EAS and a fully qualified domain name FQDN. When the address of the first EAS does not belong to the first EAS deployment information of the first SMF network element, a third message is sent to the central SMF network element, the third message comprising the address of the first EAS and the FQDN, the address of the first EAS and the FQDN being used to instruct the central SMF network element to notify the EASDF network element to update the DNS message processing rule according to the address of the first EAS and the FQDN.

[0707] For the part not described in detail, refer to the above method embodiments.

[0708] As a design, the apparatus 1700 is configured to perform the actions performed by the central SMF network element in the method embodiments shown in FIG. 15. The execution subject can be a chip, a chip system or a processor supporting the central SMF network element to implement the corresponding method, and can also be a logical module or software capable of implementing all or part of the central SMF network element function.

[0709] Specifically, the transceiver unit 1710 is configured to receive a domain name system (DNS) context notification request from an edge application server discovery function (EASDF) network element, the DNS context notification request including an address of a first edge application server (EAS) and a fully qualified domain name (FQDN), and the central SMF network element is a notification endpoint of the first local SMF network element configured to the EASDF network element for a DNS response message. The processing unit 1720 is configured to determine whether the first part of the EAS deployment information (EDI) includes the FQDN when the first part of the EDI does not include the address of the first EAS, and notify the EASDF network element to update a DNS message processing rule according to a determination result.

[0710] The details are described above in the method embodiments.

[0711] It should be understood that the specific process of each unit performing the corresponding steps described above has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0712] The processing unit 1720 in the above embodiments can be implemented by at least one processor or processor-related circuit. The transceiver unit 1710 can be implemented by a transceiver or transceiver-related circuit. The storage unit can be implemented by at least one memory.

[0713] FIG. 18 is a schematic structural diagram of a communication apparatus 1800 provided in an embodiment of the present application.

[0714] As shown in FIG. 18, the present application also provides a communication apparatus 1800. The apparatus 1800 includes a processor 1810. Optionally, the apparatus further includes a memory 1820. The processor 1810 is coupled to the memory 1820, and the memory 1820 is configured to store computer programs or instructions and / or data, and the processor 1810 is configured to execute the computer programs or instructions and / or data stored in the memory 1820, so that the method in the above method embodiments is executed.

[0715] Optionally, the processor 1810 included in the apparatus 1800 is one or more.

[0716] Optionally, as shown in FIG. 18, the apparatus 1800 can further include the memory 1820.

[0717] Optionally, the memory 1820 included in the apparatus 1800 can be one or more.

[0718] Optionally, the memory 1820 can be integrated with the processor 1810 or separately arranged.

[0719] Optionally, as shown in FIG. 18, the apparatus 1800 can further include a transceiver 1830 configured to receive and / or transmit signals. For example, the processor 1810 is configured to control the transceiver 1830 to receive and / or transmit signals.

[0720] As an example, the apparatus 1800 is configured to implement operations performed by a terminal device or a network device in the above method embodiments.

[0721] For example, the processor 1810 is configured to implement processing-related operations performed by a terminal device or a network device in the above method embodiments, and the transceiver 1830 is configured to implement transceiving-related operations performed by a terminal device or a network device in the above method embodiments.

[0722] FIG. 19 is a schematic diagram of a chip system 1900 according to an embodiment of the present application. As shown in FIG. 19, the chip system 1900 (which can also be referred to as a processing system) includes a logic circuit 1910 and an input / output interface 1920. The logic circuit is configured to be coupled with the input interface and transmit data parameters through the input / output interface to perform the method in the above method embodiments. A device in which the chip system 1900 is installed can implement the methods and functions of the embodiments of the present application. For example, the logic circuit 1910 can be a processing circuit in the chip system 1900, and is configured to control the device in which the chip system 1900 is installed. The logic circuit 1910 can also be coupled with a storage unit and invoke instructions in the storage unit, so that the device can implement the methods and functions of the embodiments of the present application. The input / output interface 1920 can be an input / output circuit in the chip system 1900, and is configured to output information processed by the chip system 1900 or input data or signaling information to be processed by the chip system 1900.

[0723] As an example, the chip system 1900 is configured to implement operations performed by a communication apparatus (such as a central SMF network element, a first local SMF network element, a second local SMF network element, an EASDF network element, or a DNS server) in the above method embodiments.

[0724] For example, the logic circuit 1910 is configured to implement processing-related operations performed by a central SMF network element, a first local SMF network element, a second local SMF network element, an EASDF network element, or a DNS server in the above method embodiments, and the input / output interface 1920 is configured to implement transceiving-related operations performed by a terminal device or a network device in the above method embodiments.

[0725] The embodiment of the present application further provides a communication system, which comprises at least one of the following: a central SMF network element, a first local SMF network element, a second local SMF network element, an EASDF network element or a DNS server, which implement the communication method in the method embodiments.

[0726] The embodiment of the present application further provides a computer readable storage medium, which stores computer instructions for implementing the method executed by the communication device (such as the central SMF network element, the first local SMF network element, the second local SMF network element, the EASDF network element or the DNS server) in the method embodiments.

[0727] For example, the computer program is executed by a computer, so that the computer can implement the method executed by the communication device (such as the central SMF network element, the first local SMF network element, the second local SMF network element, the EASDF network element or the DNS server) in the method embodiments.

[0728] The embodiment of the present application further provides a computer program product comprising instructions, which are executed by a computer to make the computer implement the method executed by the communication device (such as the central SMF network element, the first local SMF network element, the second local SMF network element, the EASDF network element or the DNS server) in the method embodiments.

[0729] The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0730] It should be understood that the processor mentioned in the embodiment of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0731] It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). For example, the RAM can be used as an external cache. As an example but not limitation, the RAM can include the following various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

[0732] It should be noted that when the processor is a general processor, a DSP, an ASIC, a FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, the memory (storage module) can be integrated in the processor.

[0733] It should also be noted that the memory described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0734] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be realized in electronic hardware, or a combination of computer software and electronic hardware. Whether the functions are performed 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 the present application.

[0735] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0736] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic. For example, the division of the units is only a logical function division. There can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0737] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place, or can be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.

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

[0739] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that make contributions to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and various media that can store program codes.

[0740] The above description is merely a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: receiving a domain name system context notification request from an edge application server discovery function network element, wherein the domain name system context notification request includes an address of a first edge application server; When the address of the first edge application server does not fall within the range of the first edge application server deployment information of the first local session management network element, the first local session management network element sends a first message to the central session management network element, where the first message includes the address of the first edge application server; determining, by the central session management network element, whether the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server; If the second part of the edge application server deployment information includes the address of the first edge application server, the central session management network element sends a first data network access identifier corresponding to the address of the first edge application server to the network storage function network element; The network storage function network element determines a second local session management network element corresponding to the first data network access identifier; the second local session management network element is used to determine a local protocol data unit session anchor point for accessing the first edge application server.

2. The method according to claim 1, characterized in that The first message further includes first indication information, where the first indication information is used to instruct the central session management network element to determine whether the second part of edge application server deployment information includes the address of the first edge application server.

3. The method according to claim 1 or 2, characterized in that The central session management network element sending the first data network access identifier corresponding to the address of the first edge application server to the network storage function network element includes: The central session management network element sends the first data network access identifier to the network storage function network element through the access and mobility management function network element.

4. The method according to claim 3, characterized in that The method further comprises: The network storage function network element sends the address of the second local session management network element to the access and mobility management function network element; The access and mobility management function network element sends session management related information to the second local session management network element, where the session management related information includes the address of the central session management network element and / or the address of the first local session management.

5. The method according to claim 1 or 2, characterized in that The method further comprises: The network storage function network element sends the address of the second local session management network element to the central session management network element; The central session management network element sends session management related information to the second local session management network element, where the session management related information includes an address of the central session management network element and / or an address of the first local session management network element.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The second local session management network element obtains the address of the first edge application server; The second local session management network element determines a local protocol data unit session anchor point for accessing the first edge application server.

7. The method according to claim 6, characterized in that The domain name system context notification request also includes identification information of the domain name system response message, the first message also includes the identification information, and the method further includes: the central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rules, the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to send a cached domain name system response message to the user equipment, and the updated domain name system message processing rules include the identification information.

8. The method according to claim 7, characterized in that The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: The central session management network element sends the updated domain name system message processing rule to the edge application server discovery function network element.

9. The method according to claim 7, characterized in that The central session management network element notifies the edge application server discovery function network element of a domain name system message processing rule including: The central session management network element sends a second message to the first local session management network element, where the second message includes the identification information; The first local session management network element generates and sends the updated domain name system message processing rule to the edge application server discovery function network element.

10. The method according to claim 9, characterized in that The second message also includes second indication information, where the second indication information is used to instruct the first local session management network element to send the updated domain name system message processing rule to the edge application server discovery function network element.

11. The method according to any one of claims 1 to 10, characterized in that The first edge application server deployment information is edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The second edge application server deployment information includes the second part of edge application server deployment information and the first part of edge application server deployment information. The first part of edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the central session management network element. The second part of edge application server deployment information includes the data network access identifier corresponding to the local session management network element maintained by the central session management network element, the address range of the edge application server, and the association between the data network access identifier and the address range of the edge application server.

12. A communication method, characterized in that: include: receiving a first message from a first local session management network element, where the first message includes an address of a first edge application server, where the address of the first edge application server does not fall within a range of first edge application server deployment information of the first local session management network element; Determine whether the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server; If the second part of the edge application server deployment information includes the address of the first edge application server, a first data network access identifier corresponding to the address of the first edge application server is sent to the network storage function network element, and the first data network access identifier is used to determine a second local session management network element, and the second local session management network element is used to determine a local protocol data unit session anchor point for accessing the first edge application server.

13. The method according to claim 12, characterized in that The first message further includes first indication information, where the first indication information is used to instruct the central session management network element to determine whether the second part of edge application server deployment information includes the address of the first edge application server.

14. The method according to claim 12 or 13, characterized in that The sending of the first data network access identifier corresponding to the address of the first edge application server to the network storage function network element includes: The first data network access identifier is sent to the network storage function network element through the access and mobility management function network element.

15. The method according to claim 12 or 13, characterized in that The method further comprises: Receiving the address of the second local session management from the network storage function network element; Sending session management related information to the second local session management network element, where the session management related information includes the address of the central session management network element and / or the address of the first local session management network element.

16. The method according to claim 15, characterized in that The method further comprises: receiving a first request message from the second local session management network element, where the first request message is used to request relevant information about edge computing; Send the address of the first edge application server to the second local session management network element.

17. The method according to claim 16, characterized in that The first message further includes the identification information, and the method further includes: Notify the edge application server discovery function network element to update the domain name system message processing rule, where the updated domain name system message processing rule is used to instruct the edge application server discovery function network element to send a cached domain name system response message to the user equipment, and the updated domain name system message processing rule includes the identification information.

18. The method according to claim 17, characterized in that The notification edge application server discovery function network element update domain name system message processing rules include: The central session management network element sends the updated domain name system message processing rule to the edge application server discovery function.

19. The method according to claim 17, wherein The notification edge application server discovery function network element update domain name system message processing rules include: Send a second message to the first local session management network element, where the second message includes the identification information, where the identification information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

20. The method according to claim 19, characterized in that The second message also includes second indication information, where the second indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

21. The method according to any one of claims 12 to 20, characterized in that The first edge application server deployment information is edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The second edge application server deployment information includes the second part of edge application server deployment information and the first part of edge application server deployment information. The first part of edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the central session management network element. The second part of edge application server deployment information includes the data network access identifier corresponding to the local session management network element maintained by the central session management network element, the address range of the edge application server, and the association between the data network access identifier and the address range of the edge application server.

22. A communication method, characterized in that: include: receiving a domain name system context notification request from an edge application server discovery function network element, wherein the domain name system context notification request includes an address of a first edge application server; determining whether the address of the first edge application server falls within the range of first edge application server deployment information of the first local session management network element; If the address of the first edge application server does not fall within the range of the first edge application server deployment information of the first local session management network element, a first message is sent to the central session management network element, where the first message includes the address of the first edge application server. The address of the first edge application server is used to instruct the central session management network element to determine whether the second part of the edge application server deployment information of the second edge application server managed by the central session includes the address of the first edge application server. The first data network access identifier corresponding to the first edge application server is used to determine a second local session management network element, and the second local session management network element is used to determine a local protocol data unit session anchor point for accessing the first edge application server.

23. The method according to claim 22, characterized in that The first message further includes first indication information, where the first indication information is used to indicate whether the second part of the edge application server deployment information of the second edge application server deployment information managed by the central session includes the address of the first edge application server.

24. The method according to claim 22 or 23, characterized in that The method further comprises: receiving a first request message from a second local session management network element, where the first request message is used to request relevant information about edge computing, and the second local session management network element is used to maintain the first edge application server; Send the address of the first edge application server to the second local session management network element.

25. The method according to any one of claims 22 to 24, characterized in that The domain name system context notification request further includes identification information of a domain name system response message, the first message further includes the identification information, and the method further includes: receiving a second message from the central session management network element, wherein the second message includes identification information of a domain name system response message; Generate and send an updated domain name system message processing rule to the edge application server discovery function network element, the updated domain name system message processing rule is used to instruct the edge application server discovery function network element to send a cached domain name system response message to the user equipment, and the updated domain name system message processing rule includes the identification information.

26. The method according to claim 25, characterized in that The second message also includes second indication information, where the second indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

27. A communication method, characterized in that: include: Obtaining an address of a first edge application server, where the address of the first edge application server does not belong to the first edge application server deployment information of the first local session management network element; Determine a local protocol data unit session anchor for accessing the first edge application server.

28. The method according to claim 27, characterized in that The acquiring the address of the first edge application server includes: Sending a first request message to the central session management network element, where the first request message is used to request relevant information about edge computing; A first response message is received from the central session management network element, where the first response message includes an address of the first edge application server.

29. The method according to claim 28, characterized in that The acquiring the address of the first edge application server includes: Sending a first request message to the first local session management network element, where the first request message is used to request relevant information about edge computing; A first response message is received from the first local session management network element, where the first response message includes an address of a first edge application server.

30. The method according to any one of claims 27 to 29, characterized in that Before obtaining the address of the first edge application server, the method further includes: receiving information related to session management from a mobility management function access and a mobility management function network element; or, Receive session management related information from a central session management network element, where the session management related information includes an address of the central session management network element and / or an address of the first local session management.

31. A communication device, characterized in that: The method comprises a module or unit for executing the method of any one of claims 12 to 21, or a module or unit for executing the method of any one of claims 22 to 26, or a module or unit for executing the method of any one of claims 27 to 30.

32. A communication device, characterized in that: The communication device comprises a processor coupled to a memory, wherein the memory stores instructions, and when the instructions are executed by the processor, the communication device performs the method according to any one of claims 12 to 21, or the communication device performs the method according to any one of claims 22 to 26, or the communication device performs the method according to any one of claims 27 to 30.

33. A communication method, characterized in that: include: The first local session management network element configures the edge application server discovery function network element to configure the notification endpoint for the domain name system response message as the central session management network element; The central session management network element receives a domain name system context notification request from the edge application server discovery function network element, where the domain name system context notification request includes an address of a first edge application server; If the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server, the central session management network element sends a first data network access identifier to the network storage function network element; The network storage function network element determines a second local session management network element corresponding to the first data network access identifier; the second local session management network element is used to determine a local protocol data unit session anchor point for accessing the first edge application server.

34. The method according to claim 33, wherein If the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server, before the central session management network element sends the first data network access identifier to the network storage function network element, the method further includes: the central session management network element determining whether the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server.

35. The method according to claim 33 or 34, characterized in that The domain name system context notification request also includes first indication information, where the first indication information is used to instruct the central session management network element to determine whether the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server.

36. The method according to any one of claims 33 to 35, characterized in that The central session management network element sending the first data network access identifier to the network storage function network element includes: The central session management network element sends the first data network access identifier to the network storage function network element through the access and mobility management function network element.

37. The method according to claim 36, wherein The method further comprises: The network storage function network element sends the address of the second local session management network element to the access and mobility management function network element; The access and mobility management function network element sends session management related information to the second local session management network element, where the session management related information includes the address of the central session management network element.

38. The method according to any one of claims 33 to 35, characterized in that The method further comprises: The network storage function network element sends the address of the second local session management network element to the central session management network element; The central session management network element sends session management related information to the second local session management network element, where the session management related information includes the address of the central session management network element.

39. The method according to any one of claims 33 to 38, characterized in that The method further comprises: The second local session management network element obtains the address of the first edge application server; The second local session management network element determines the local protocol data unit session anchor point for accessing the first edge application server.

40. The method according to claim 39, wherein The domain name system context notification request further includes identification information of a domain name system response message, and the method further includes: The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rules, and the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to send a cached domain name system response message to the user equipment, and the updated domain name system message processing rules include the identification information.

41. The method according to claim 39, wherein The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: The central session management network element sends the updated domain name system message processing rule to the edge application server discovery function.

42. The method according to claim 39, wherein The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: The central session management network element sends a second message to the first local session management network element, where the second message includes the identification information; The first local session management network element generates and sends the updated domain name system message processing rule to the edge application server discovery function network element.

43. The method according to claim 42, characterized in that The second message further includes second indication information, where the second indication information is used to instruct the first local session management network element to send the updated domain name system message processing rule to the edge application server discovery function network element.

44. The method according to any one of claims 33 to 42, characterized in that The first edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The central session management network element includes the second edge application server deployment information, and the second edge application server deployment information includes: the edge application server deployment information corresponding to the edge computing service supported by the central session management network element, and the data network access identifier and edge application server address range corresponding to the local session management network element.

45. A communication method, characterized in that: include: receiving a domain name system context notification request from an edge application server discovery function network element, the domain name system context notification request including an address of a first edge application server, the central session management network element being a notification endpoint for a domain name system response message configured by the first local session management network element to the edge application server discovery function network element; If the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server, a first data network access identifier corresponding to the address of the first edge application server is sent to the network storage function network element, and the first data network access identifier is used to determine the second local session management network element, and the second local session management network element is used to determine a local protocol data unit session anchor point for accessing the first edge application server.

46. ​​The method according to claim 45, characterized in that If the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server, before sending the first data network access identifier corresponding to the address of the first edge application server to the network storage function network element, the method also includes: determining whether the second part of the edge application server deployment information includes the address of the first edge application server.

47. The method according to claim 45 or 46, characterized in that The domain name system context notification request also includes first indication information, where the first indication information is used to instruct the central session management network element to determine whether the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server.

48. The method according to any one of claims 45 to 47, characterized in that The sending of the first data network access identifier corresponding to the address of the first edge application server to the network storage function network element includes: The first data network access identifier is sent to the network storage function network element through the access and mobility management function network element.

49. The method according to any one of claims 45 to 47, characterized in that The method further comprises: Receiving the address of the second local session management from the network storage function network element; Sending session management related information to the second local session management network element, where the session management related information includes the address of the central session management network element.

50. The method according to claim 48 or 49, characterized in that The method further comprises: receiving a first request message from the second local session management network element, where the first request message is used to request relevant information about edge computing; Send the address of the first edge application server to the second local session management network element.

51. The method according to claim 50, characterized in that The domain name system context notification request further includes identification information of the domain name system response message, and the method further includes: Notify the edge application server discovery function network element to update the domain name system message processing rule, where the updated domain name system message processing rule is used to instruct the edge application server discovery function network element to send a cached domain name system response message to the user equipment, and the updated domain name system message processing rule includes the identification information.

52. The method according to claim 51, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rule includes: sending the updated domain name system message processing rule to the edge application server discovery function network element.

53. The method according to claim 51, characterized in that The notification of the edge application server discovery function network element to update the domain name system message processing rule includes: Send a second message to the first local session management network element, where the second message includes the identification information, where the identification information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

54. The method according to claim 53, wherein The second message also includes second indication information, where the second indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

55. The method according to any one of claims 45 to 54, characterized in that The first edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The central session management network element includes the second edge application server deployment information, and the second edge application server deployment information includes: the edge application server deployment information corresponding to the edge computing service supported by the central session management network element, and the data network access identifier and edge application server address range corresponding to the local session management network element.

56. A communication device, characterized in that The method comprises modules or units for performing the method according to any one of claims 45 to 55.

57. A communication device, characterized in that The device comprises a processor coupled to a memory, wherein the memory stores instructions, and when the instructions are executed by the processor, the communication device causes the communication device to perform the method according to any one of claims 45 to 55.

58. A communication method, characterized in that: include: The first local session management network element receives a domain name system context notification request from the edge application server discovery function network element, wherein the domain name system context notification request includes an address of the first edge application server, identification information of the domain name system response message, and a fully qualified domain name; When the address of the first edge application server does not fall within the range of the first edge application server deployment information of the first local session management network element, the first local session management network element sends a third message to the central session management network element, where the third message includes the identification information; The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rules, where the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to generate a domain name system query message with an empty domain name system extension mechanism client subnet option for the fully qualified domain name and delete the domain name system response message, where the updated domain name system message processing rules include the identification information.

59. The method according to claim 58, characterized in that The third message further includes third indication information, where the third indication information is used to instruct the central session management network element to notify the edge application server discovery function network element to update a domain name system message processing rule.

60. The method according to claim 58 or 59, characterized in that The third message also includes the address of the first edge application server and the fully qualified domain name, and the central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: Determine whether the second part of the edge application server deployment information of the second edge application server deployment information of the central session management network element includes the address of the first edge application server; If the second part of the edge application server deployment information does not include the address of the first edge application server, the central session management network element notifies the edge application server discovery function network element to update a domain name system message processing rule.

61. The method according to any one of claims 58 to 60, characterized in that The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: The central session management network element sends the updated domain name system message processing rule to the edge application server discovery function network element.

62. The method according to any one of claims 58 to 60, characterized in that The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: The central session management network element sends a fourth message to the first local session management network element, where the fourth message includes the identification information; The first local session management network element generates and sends the updated domain name system message processing rule to the edge application server discovery function network element.

63. The method according to claim 62, characterized in that The fourth message further includes fourth indication information, where the fourth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

64. The method according to any one of claims 58 to 63, characterized in that The first edge application server deployment information is edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The second edge application server deployment information includes the second part of edge application server deployment information and the first part of edge application server deployment information. The first part of edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the central session management network element. The second part of edge application server deployment information includes the data network access identifier corresponding to the local session management network element maintained by the central session management network element, the address range of the edge application server, and the association between the data network access identifier and the address range of the edge application server.

65. A communication method, characterized in that: include: receiving a third message from the first local session management network element, the third message including identification information and a fully qualified domain name; Notify the edge application server discovery function network element to update the domain name system message processing rules, where the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to generate a domain name system query message with an empty domain name system extension mechanism client subnet option for the fully qualified domain name and delete the domain name system response message, where the updated domain name system message processing rules include the identification information and the fully qualified domain name.

66. The method according to claim 65, characterized in that The third message further includes third indication information, where the third indication information is used to instruct the central session management network element to notify the edge application server discovery function network element to update a domain name system message processing rule.

67. The method according to claim 65 or 66, characterized in that The third message also includes the address of the first edge application server; The notification edge application server discovery function network element update domain name system message processing rules include: When the first part of the edge application server deployment information of the second edge application server deployment information of the central session management network element does not include the address of the first edge application server, and the first part of the edge application server deployment information does not include the fully qualified domain name, notify the edge application server discovery function network element to update the domain name system message processing rule.

68. The method according to any one of claims 65 to 67, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rule includes: sending the updated domain name system message processing rule to the edge application server discovery function network element.

69. The method according to any one of claims 65 to 68, characterized in that The notification edge application server discovery function network element update domain name system message processing rules include: Send a fourth message to the first local session management network element, where the fourth message includes the identification information, where the identification information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

70. The method according to claim 69, wherein The fourth message further includes fourth indication information, where the fourth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

71. A communication method, characterized in that: include: receiving a domain name system context notification request from an edge application server discovery function network element, the domain name system context notification request including an address of a first edge application server, identification information of a domain name system response message, and a fully qualified domain name; When the address of the first edge application server does not fall within the range of the first edge application server deployment information of the first local session management network element, a third message is sent to the central session management network element, where the third message includes the identification information and the fully qualified domain name, where the identification information is used to instruct the central session management network element to notify the edge application server discovery function network element to update a domain name system message processing rule, where the updated domain name system message processing rule is used to instruct the edge application server discovery function network element to generate a domain name system query message with an empty domain name system extension mechanism client subnet option for the fully qualified domain name and to delete the domain name system response message.

72. The method according to claim 71, characterized in that The third message further includes third indication information, where the third indication information is used to instruct the central session management network element to notify the edge application server discovery function network element to update a domain name system message processing rule.

73. The method according to claim 71 or 72, characterized in that The method further comprises: receiving a fourth message from the central session management network element, the fourth message including the identification information; Generate and send the updated domain name system message processing rule to the edge application server discovery function network element, where the updated domain name system message processing rule includes the identification information.

74. The method according to claim 73, characterized in that The fourth message further includes fourth indication information, where the fourth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

75. A communication device, characterized in that The method comprises a module or unit for performing the method of any one of claims 65 to 70, or comprises a module or unit for performing the method of any one of claims 71 to 74.

76. A communication device, characterized in that It includes a processor, which is coupled to a memory, and the memory stores instructions. When the instructions are executed by the processor, the communication device executes the method as described in any one of claims 65 to 70, or the communication device executes the method as described in any one of claims 71 to 74.

77. A communication method, characterized in that: include: The first local session management network element receives a domain name system context notification request from the edge application server discovery function network element, where the domain name system context notification request includes an address and a fully qualified domain name of the first edge application server; When the address of the first edge application server does not fall within the range of the first edge application server deployment information of the first local session management network element, the first local session management network element sends a third message to the central session management network element, where the third message includes the address of the first edge application server and the fully qualified domain name; When the first part of the edge application server deployment information of the second edge application server deployment information of the central session management network element does not include the address of the first edge application server, the central session management network element determines whether the first part of the edge application server deployment information includes the fully qualified domain name; The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule according to the determination result.

78. The method according to claim 77, characterized in that The third message also includes fifth indication information, where the fifth indication information is used to instruct the central session management network element to determine whether the first part of the edge application server deployment information includes the address of the first edge application server.

79. The method according to claim 77 or 78, characterized in that The third message also includes identification information of the domain name system response message.

80. A communication method, characterized in that: include: The first local session management network element configures the edge application server discovery function network element to configure the notification endpoint for the domain name system response message as the central session management network element; The central session management network element receives a domain name system context notification request from the edge application server discovery function network element, where the domain name system context notification request includes an address and a fully qualified domain name of a first edge application server; When the first part of the edge application server deployment information of the second edge application server deployment information of the central session management network element does not include the address of the first edge application server, determining whether the first part of the edge application server deployment information includes the fully qualified domain name; The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule according to the determination result.

81. The method according to claim 80, characterized in that The domain name system context notification request further includes fifth indication information, where the fifth indication information is used to instruct the central session management network element to determine whether the first part of edge application server deployment information includes the address of the first edge application server.

82. The method according to claim 79 or 81, characterized in that The domain name system context notification request also includes identification information of the domain name system response message, The central session management network element notifying the edge application server discovery function network element to update the domain name system message processing rule according to the determination result includes: If the first part of the edge application server deployment information includes the fully qualified domain name, the central session management network element generates information indicating the location of the user equipment according to the fully qualified domain name, the location information of the user equipment, and the second edge application server deployment information; The central session management network element notifies the edge application server discovery function network element to update a domain name system message processing rule, where the updated domain name system message processing rule is used to instruct the edge application server discovery function network element to generate a domain name system extension mechanism client subnet option, where the domain name system extension mechanism client subnet option includes information indicating the location of the user device, and adds the domain name system extension mechanism client subnet option to a domain name system query message and deletes the domain name system response message, where the domain name system query message is regenerated for the fully qualified domain name, and the updated domain name system message processing rule includes the first information and the identification information, where the first information is used to indicate information indicating the location of the user device.

83. The method according to claim 82, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rule includes: the central session management network element sending the updated domain name system message processing rule to the edge application server discovery function network element.

84. The method according to claim 82, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rule includes: the central session management network element sending a fifth message to the first local session management network element, the fifth message including the identification information and the first information, the first information being information for indicating the location of the user equipment; The first local session management network element generates and sends the updated domain name system message processing rule to the edge application server discovery function network element.

85. The method according to claim 84, characterized in that The fifth message also includes sixth indication information, where the sixth indication information is used to instruct the first local session management network element to generate and send an updated domain name system message processing rule to the edge application server discovery function network element.

86. The method according to claim 79 or 81, characterized in that The domain name system context notification request also includes identification information of the domain name system response message; The central session management network element notifies the edge application server discovery function network element to update a domain name system message processing rule based on the determination result, including: if the first part of the edge application server deployment information does not include the fully qualified domain name, the central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule, the updated domain name system message processing rule being used to instruct the edge application server discovery function network element to generate a domain name system query message with an empty domain name system extension mechanism client subnet option for the fully qualified domain name and to delete the domain name system response message, the updated domain name system message processing rule including the identification information.

87. The method according to claim 86, characterized in that The central session management network element notifying the edge application server discovery function network element to update the domain name system message processing rule includes: the central session management network element sending the updated domain name system message processing rule to the edge application server discovery function network element.

88. The method according to claim 86, characterized in that The central session management network element notifies the edge application server discovery function network element to update the domain name system message processing rule including: The central session management network element sends a fourth message to the first local session management network element, where the fourth message includes the identification information; The first local session management network element generates and sends the updated domain name system message processing rule to the edge application server discovery function network element.

89. The method according to claim 88, characterized in that The fourth message further includes fourth indication information, where the fourth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

90. The method according to any one of claims 77 to 89, wherein The first edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The second edge application server deployment information includes the second part of edge application server deployment information and the first part of edge application server deployment information. The first part of edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the central session management network element. The second part of edge application server deployment information includes the data network access identifier corresponding to the local session management network element maintained by the central session management network element, the address range of the edge application server, and the association between the data network access identifier and the address range of the edge application server.

91. A communication method, characterized in that: include: receiving a third message from the first local session management network element, the third message including the address and fully qualified domain name of the first edge application server; When the first part of the edge application server deployment information of the second edge application server deployment information of the central session management network element does not include the address of the first edge application server, determining whether the first part of the edge application server deployment information includes the fully qualified domain name; According to the determination result, the edge application server is notified to discover the function network element to update the domain name system message processing rule.

92. The method according to claim 91, wherein The third message further includes fifth indication information, where the fifth indication information is used to instruct the central session management network element to determine whether the first part of edge application server deployment information includes the address of the first edge application server.

93. The method according to claim 91 or 92, characterized in that The third message also includes identification information of the domain name system response message.

94. A communication method, characterized in that include: receiving a domain name system context notification request from an edge application server discovery function network element, the domain name system context notification request including an address and a fully qualified domain name of a first edge application server, the central session management network element being a notification endpoint for a domain name system response message configured by the first local session management network element to the edge application server discovery function network element; When the first part of the edge application server deployment information of the second edge application server deployment information of the central session management network element does not include the address of the first edge application server, determining whether the first part of the edge application server deployment information includes the fully qualified domain name; According to the determination result, the edge application server is notified to discover the function network element to update the domain name system message processing rule.

95. The method according to claim 94, characterized in that The domain name system context notification request further includes fifth indication information, where the fifth indication information is used to instruct the central session management network element to determine whether the first part of the edge application server deployment information includes the address of the first edge application server.

96. The method according to claim 93 or 95, characterized in that The domain name system context notification request also includes identification information of the domain name system response message, The notifying the edge application server discovery function network element to update the domain name system message processing rule according to the determination result includes: If the first part of the edge application server deployment information includes the fully qualified domain name, the central session management network element generates information indicating the location of the user equipment according to the fully qualified domain name, the location information of the user equipment, and the second edge application server deployment information; Notify the edge application server discovery function network element to update domain name system message processing rules, where the updated domain name system message processing rules include the identification information, and the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to generate a domain name system extension mechanism client subnet option, where the domain name system extension mechanism client subnet option includes the information used to indicate the location of the user device, and add the domain name system extension mechanism client subnet option to the domain name system query message and delete the domain name system response message. The domain name system query message is regenerated for the fully qualified domain name.

97. The method according to claim 96, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rule includes: sending the updated domain name system message processing rule to the edge application server discovery function network element.

98. The method according to claim 96, wherein The notification of the edge application server discovery function network element to update the domain name system message processing rule includes: Send a fifth message to the first local session management network element, where the fifth message includes the identification information and first information, where the first information is generated for indicating the location of the user equipment, and the first information is further used to instruct the first local session management network element to generate, according to the first information, information instructing the edge application server discovery function network element to generate a domain name system extension mechanism client subnet option in the updated domain name system message processing rule.

99. The method according to claim 98, wherein The fifth message further includes sixth indication information, where the sixth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

100. The method according to claim 93 or 95, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rules based on the determination result includes: if the first part of the edge application server deployment information does not include the fully qualified domain name, notifying the edge application server discovery function network element to update the domain name system message processing rules, the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to generate a domain name system query message with an empty domain name system extension mechanism client subnet option for the fully qualified domain name and delete the domain name system response message, and the updated domain name system message processing rules include identification information of the domain name system response message.

101. The method according to claim 100, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rule includes: sending the updated domain name system message processing rule to the edge application server discovery function network element.

102. The method according to claim 100, characterized in that The notifying the edge application server discovery function network element to update the domain name system message processing rules includes: the central session management network element sending a fourth message to the first local session management network element, the fourth message including the identification information, and the identification information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rules to the edge application server discovery function network element.

103. The method according to claim 102, characterized in that The fourth message further includes fourth indication information, where the fourth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

104. The method according to any one of claims 93 to 103, characterized in that The first edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the first local session management network element; The second edge application server deployment information includes the second part of edge application server deployment information and the first part of edge application server deployment information. The first part of edge application server deployment information is the edge application server deployment information corresponding to the edge computing service supported by the central session management network element. The second part of edge application server deployment information includes the data network access identifier corresponding to the local session management network element maintained by the central session management network element, the address range of the edge application server, and the association between the data network access identifier and the address range of the edge application server.

105. A communication method, characterized in that: include: receiving a domain name system context notification request from an edge application server discovery function network element, wherein the domain name system context notification request includes an address and a fully qualified domain name of a first edge application server; When the address of the first edge application server does not belong to the first edge application server deployment information of the first session management network element, a third message is sent to the central session management network element, where the third message includes the address of the first edge application server and the fully qualified domain name. The address of the first edge application server and the fully qualified domain name are used to instruct the central session management network element to notify the edge application server discovery function network element to update the domain name system message processing rule according to the address and the fully qualified domain name of the first edge application server.

106. The method according to claim 105, characterized in that The third message further includes fifth indication information, where the fifth indication information is used to instruct the central session management network element to determine whether the first part of the second edge application server deployment information includes the address of the first edge application server.

107. The method according to claim 105 or 106, characterized in that The DNS context notification request further includes identification information of a DNS response message, the third message further includes the identification information, and the method further includes: receiving a fifth message from the central session management network element, where the fifth message includes the identification information and first information, where the first information is used to indicate location information of the user equipment; Generate and send the updated domain name system message processing rule to the edge application server discovery function network element, the updated domain name system message processing rule including the first information and the identification information, the updated domain name system message processing rule is used to instruct the edge application server discovery function network element to generate a domain name system extension mechanism client subnet option, the domain name system extension mechanism client subnet option including the first information, add the domain name system extension mechanism client subnet option to the domain name system query message and delete the domain name system response message, the domain name system query message is regenerated for the fully qualified domain name.

108. The method according to claim 107, characterized in that The fifth message further includes sixth indication information, where the sixth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

109. The method according to claim 105 or 106, characterized in that The DNS context notification request further includes identification information of the DNS response message, the third message further includes the identification information, and the method further includes: receiving a fourth message from the central session management network element, the fourth message including the identification information; Generate and send the updated domain name system message processing rules to the edge application server discovery function network element, the updated domain name system message processing rules including the identification information, the updated domain name system message processing rules are used to instruct the edge application server discovery function network element to generate a domain name system query message with an empty domain name system extension mechanism client subnet option for the fully qualified domain name and delete the domain name system response message.

110. The method according to claim 109, characterized in that The fourth message further includes fourth indication information, where the fourth indication information is used to instruct the first local session management network element to generate and send the updated domain name system message processing rule to the edge application server discovery function network element.

111. A communication device, characterized in that Comprising modules or units for performing the method of any one of claims 91 to 104.

112. A communication device, characterized in that The device comprises a processor coupled to a memory, wherein the memory stores instructions, and when the instructions are executed by the processor, the communication device causes the communication device to perform the method according to any one of claims 105 to 110.

113. A communication system, characterized in that include: A central session management network element, a first local session management network element, and a second local session management network element, the central session management network element is used to perform the method according to any one of claims 12 to 21, the first local session management network element is used to perform the method according to any one of claims 22 to 26, and the first local session management network element is used to perform the method according to any one of claims 27 to 30.

114. A communication system, characterized in that include: A central session management network element, configured to execute the method according to any one of claims 45 to 55.

115. A communication system, characterized in that include: A central session management network element and a first local session management network element, the central session management network element is used to execute the method according to any one of claims 65 to 70, and the first local session management network element is used to execute the method according to any one of claims 71 to 74.

116. A communication system, characterized in that include: A central session management network element and a first local session management network element, wherein the central session management network element is used to perform the method according to any one of claims 91 to 93 and claims 96 to 104, and the first local session management network element is used to perform the method according to any one of claims 105 to 110.

117. A communication system, characterized in that It comprises: a central session management network element, wherein the central session management network element is used to execute the method as described in any one of claims 94 to 104.

118. A computer-readable storage medium, characterized in that The computer-readable storage medium is used to store a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 30, or causes the computer to execute the method according to any one of claims 33 to 55, or causes the computer to execute the method according to any one of claims 58 to 74, or causes the computer to execute the method according to any one of claims 77 to 110.

119. A computer program product, characterized in that When the computer program product runs on a computer, the computer executes the method according to any one of claims 1 to 30, or the computer executes the method according to any one of claims 33 to 55, or the computer executes the method according to any one of claims 58 to 74, or the computer executes the method according to any one of claims 77 to 110.

Images