Communication method and device

Abstract

The present application provides a communication method and apparatus. The method comprises: a session management function obtains at least one group of first associations, wherein the first association is a correspondence between identification information of Domain Name System (DNS) processing information and DNS processing information. The SMF transmits at least one group of first associations used in Protocol Data Unit (PDU) sessions of a plurality of terminal devices to an Edge Application Server Discovery Function (EASDF) and transmits a first message corresponding to the first PDU session to the EASDF, wherein the first information includes first identification information, and the first identification information is identification information of DNS processing information corresponding to the first PDU session. The EASDF receives the first association and the first message and determines DNS processing information corresponding to the first PDU session based on the first association and the first identification information. This improves the user's service experience and information processing efficiency.

Description

Technology Field

[0001] This application claims priority to Chinese patent application No. 202110810737.X, filed with the State Intellectual Property Administration of China on July 16, 2021, under the title "Communication Method and Apparatus," the entire contents of which are incorporated herein by reference.

[0002] This application relates to the field of communication, specifically to communication methods and devices. Background Technology

[0003] The 3rd generation partnership project (3GPP) standard TS 23.548 defines a new network element that supports discovery of edge application servers (EAS), namely the edge application server discovery function (EASDF). The primary function of EASDF is to process Domain Name System (DNS) messages based on instructions from the session management function (SMF).

[0004] In the procedure of discovering EAS using EASDF, SMF can transmit DNS information processing rules and EDNS client subnet options (which may simply be referred to as "ECS options") to EASDF at the protocol data unit (PDU) session level. However, the DNS information processing rules and ECS options transmitted across multiple PDU sessions are identical, and consequently, the information is transmitted repeatedly. Additionally, if DNS information processing rules need to be updated, SMF updates the DNS information processing rules for each PDU session, resulting in a large amount of signaling being transmitted.

[0005] The present application provides a communication method and apparatus. The SMF transmits the correspondence between the identification information of Domain Name System (DNS) processing information and the DNS processing information to the EASDF to improve information processing efficiency and the user's service experience.

[0006] According to a first embodiment, a communication method is provided. The method comprises: a session management function obtains at least one group of first associations, wherein the first association is a correspondence between identification information of Domain Name System (DNS) processing information and DNS processing information; the SMF transmits at least one group of first associations used in protocol data unit (PDU) sessions of a plurality of terminal devices to an edge application server discovery function (EASDF); and the SMF transmits a first message corresponding to the first PDU session to the EASDF, wherein the first information includes first identification information, the first identification information is identification information of DNS processing information corresponding to the first PDU session, and the first identification information is used by the EASDF to determine DNS processing information corresponding to the first PDU session based on the first association and the first identification information.

[0007] It should be noted that the first identifier in this application may be DNS processing information corresponding to the first UE or the first PDU session. In this application, the first identifier may be one of a UE group ID, a rule ID, DNAI, DNN, S-NSSAI, or something similar. For convenience of explanation, this embodiment is described using only an example where the first identifier is a rule ID. The rule ID mentioned in the following embodiments may be any one of the aforementioned first identifiers. This is not limited to.

[0008] This is because differentiation granularities differ across various deployment scenarios. For example, in some scenarios, different UEs correspond to different first associations (in this case, the UE group ID can be used as identification information). In other scenarios, different PDU sessions correspond to different first associations (in this case, the rule ID can be used as identification information).

[0009] According to the technical solution provided in this application, the SMF transmits to the EASDF the correspondence between the identification information of the Domain Name System (DNS) processing information and the DNS processing information. In this manner, since the SMF transmits DNS processing rules based on the identification information of the DNS processing information to the EASDF, the EASDF can use different DNS processing information for different PDU sessions or UEs. This enables differentiated processing of DNS messages and improves the user's service experience. Furthermore, repetitive requests and transmissions of information can be avoided, signaling interactions can be reduced, and information processing efficiency can be improved.

[0010] It should be noted that in this application, "multiple terminal devices" may refer to multiple or all terminal devices to which the first association may be applied, and "multiple PDU sessions" may be understood as multiple or all PDU sessions to which the first association may be applied. Further details are not described below.

[0011] Referring to the first embodiment, in some implementation of the first embodiment, DNS processing information includes DNS detection information or DNS processing parameters, and DNS detection information is used by the EASDF to determine a processing action for a DNS message by matching a DNS message, and DNS processing parameters are used by the EASDF to determine an EDNS client subnet option by matching a DNS message, so that the EASDF adds the EDNS client subnet option to the DNS message and transmits the DNS message to a DNS server, or DNS processing parameters are used by the EASDF to determine a local DNS server address by matching a DNS message, so that the EASDF transmits the local DNS server address to a local DNS server. A DNS message is received by the EASDF from a terminal device or a DNS server.

[0012] In the present application, "DNS detection information is used by the EASDF to determine a processing action for a DNS message by matching DNS messages" may alternatively mean that DNS detection information is used by the EASDF to determine a DNS message processing action corresponding to a DNS message.

[0013] It should be noted that in this application, DNS processing information may alternatively be DNS detection information and DNS processing parameters. Further details are not described below.

[0014] Based on the aforementioned technical solution, since the processing parameters of the present application may be DNS detection information or DNS processing parameters, the EASDF can determine processing actions for DNS messages based on the detection information. This prevents repetitive requests and transmissions of information. Additionally, the EASDF can determine ECS options or local DNS server addresses based on the DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0015] Referring to the first embodiment, in some implementation of the first embodiment, where the DNS processing information is DNS detection information, the DNS detection information includes a full-qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range.

[0016] Based on the aforementioned technical solution, in this application, since DNS detection information may include FQDN ranges and / or EAS IP address ranges, the EASDF can determine whether to report a DNS message by performing a match based on the FQDN ranges and / or EAS IP address ranges within the DNS message. In this manner, the SMF transmits DNS processing rules based on identification information of the DNS processing information to the EASDF, so that the EASDF can use different DNS processing information for different PDU sessions or UEs. This enables differentiated processing of DNS messages and improves the user's service experience.

[0017] Referring to the first embodiment, in a part of the first embodiment, the DNS detection information further comprises information regarding a DNS message processing operation performed by the EASDF, which is determined based on the first identification information, and the processing operation includes one or more of reporting a DNS message, reporting the contents of a DNS message, caching a DNS message, and forwarding a DNS message.

[0018] Based on the aforementioned technical solution, in this application, since the DNS detection information may further include information regarding DNS message processing operations performed by the EASDF, the EASDF can determine information regarding DNS message processing operations based on the detection information. This improves information processing efficiency.

[0019] In relation to the first embodiment, in some implementation of the first embodiment, where DNS processing information is a DNS processing parameter, the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and EDNS client subnet options, or the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and an EDNS client subnet option, or the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a local DNS server address, or the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and a local DNS server address, wherein the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0020] Based on the aforementioned technical solution, in this application, the EASDF can determine an ECS option or a local DNS server based on DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0021] Referring to the first embodiment, in a part of the first embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is an EDNS client subnet option, the first identification information is a first DNAI, and the first identification information is used by the EASDF to determine the EDNS client subnet option by matching the first association, so the EASDF adds the EDNS client subnet option to the DNS message and transmits the DNS message to the DNS server, the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0022] Referring to the first embodiment, in a part of the first embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a full-qualified domain name (FQDN) and an EDNS client subnet option, the first identification information is a first DNAI, and the first identification information and the DNS message are used by the EASDF to determine the EDNS by matching the first association, so the EASDF adds the EDNS client subnet option to the DNS message and transmits the DNS message to the DNS server, the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, the DNS message includes an FQDN, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0023] Based on the aforementioned technical solution, specifically in this application, when the identification information of the DNS processing information is a Data Network Access Identifier (DNAI), the DNS processing parameter may be an EDNS client subnet option, or the DNS processing parameter is There may be a correspondence between FQDN and EDNS client subnet options. Therefore, EASDF can determine ECS options based on DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0024] Referring to the first embodiment, in a part of the first embodiment, the identification information of the DNS processing information is a data network access identifier, the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a local DNS server address, the first identification information is a first DNAI, the first identification information is used by the EASDF to determine the local DNS server address by matching the first association, and the EASDF transmits a DNS message to the local DNS server, the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0025] Referring to the first embodiment, in a part of the first embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between an FQDN and a local DNS server address, the first identification information is a first DNAI, and the first identification information and the DNS message are used by the EASDF to determine the local DNS server address by matching the first association, and the EASDF transmits the DNS message to the local DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, the DNS message includes an FQDN, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0026] Based on the aforementioned technical solution, specifically in this application, when the identification information of the DNS processing information is a Data Network Access Identifier (DNAI), the DNS processing parameter may be a local DNS server address or a correspondence between an FQDN and a local DNS server address. Accordingly, the EASDF can determine the local DNS server address based on the DNS processing parameter. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0027] Referring to the first embodiment, in some implementation of the first embodiment, the deployment information of the edge application server includes one or more of information regarding an FQDN corresponding to a DNAI, information regarding an Internet Protocol address of the edge application server, and identification information of a DNS server, and the deployment information of the user plane function includes a correspondence between the user plane function (UPF) and the DNAI.

[0028] Referring to the first embodiment, in a part of the first embodiment, the first message further includes first indication information, the first indication information instructs the EASDF to determine DNS processing information corresponding to the first PDU session based on first identification information and a first association.

[0029] Based on the aforementioned technical solution, in the present application, the first message may further include first indication information, and the indication of this indication information may enable the EASDF to determine DNS processing information corresponding to the first PDU session based on the first identification information and the first association. This improves information processing efficiency.

[0030] According to a second embodiment, a communication method is provided. The method comprises: an edge application server discovery function (EASDF) receives from a session management function (SMF) at least one group of first associations used for protocol data unit (PDU) sessions of a plurality of terminal devices, wherein the first association is a correspondence between identification information of domain name system (DNS) processing information and DNS processing information, and the EASDF receives from the SMF a first message corresponding to the first PDU session, wherein the first message includes first identification information, and the first identification information is identification information of DNS processing information corresponding to the first PDU session, and the EASDF determines DNS processing information corresponding to the first PDU session based on the first identification information and the first association.

[0031] According to the technical solution provided in this application, the EASDF receives a first message and a correspondence between the identification information of the Domain Name System (DNS) processing information and the DNS processing information, and can determine the DNS processing information corresponding to the first PDU session based on the first identification information and the first association. In one embodiment, the SMF transmits a DNS processing rule based on the identification information of the DNS processing information to the EASDF. In this way, the EASDF can use different DNS processing information for different PDU sessions or UEs. This enables differentiated processing of DNS messages and improves the user's service experience. Additionally, the EASDF can determine ECS options and local server addresses based on DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0032] Referring to the second embodiment, in some implementation of the second embodiment, DNS processing information includes DNS detection information or DNS processing parameters, DNS detection information includes a full-qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range, and DNS processing parameters are correspondence between data network access identifier (DNAI) information and EDNS client subnet options, DNS processing parameters are correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and an EDNS client subnet option, DNS processing parameters are correspondence between data network access identifier (DNAI) information and a local DNS server address, or DNS processing parameters are correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and a local DNS server address.

[0033] Based on the aforementioned technical solution, since the processing parameters in this application may be DNS detection information or DNS processing parameters, the EASDF can determine the processing action for DNS messages based on the detection information. This prevents repetitive requests and transmissions of information. Additionally, the EASDF can determine ECS options or local DNS server addresses based on the DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0034] Referring to the second embodiment, in a part of the second embodiment, where the DNS processing information is DNS detection information, the method further comprises: the EASDF receives a DNS message, the EASDF matches the DNS message based on the first identification information and the first association, and the EASDF determines a processing action for the DNS message.

[0035] In the present application, the EASDF may further determine a processing action for a DNS message based on first identification information and a first association. Specifically, the EASDF matches a DNS message based on first identification information and a first association, and the EASDF determines a processing action for a DNS message.

[0036] In the present application, the EASDF may further determine a processing action for a DNS message based on first identification information and a first association. This prevents repetitive requests and transmissions of information.

[0037] Referring to a second embodiment, in a part of the second embodiment, the DNS detection information further comprises information regarding a DNS message processing operation performed by an EASDF, which is determined based on the first identification information, and the processing operation includes one or more of reporting a DNS message, reporting the contents of a DNS message, caching a DNS message, and forwarding a DNS message.

[0038] Based on the aforementioned technical solution, in this application, since the DNS detection information may further include information regarding DNS message processing operations performed by the EASDF, the EASDF can determine information regarding DNS message processing operations based on the detection information. This improves information processing efficiency.

[0039] Referring to the second embodiment, in a part of the second embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and an EDNS client subnet option, the method further comprises: EASDF receives a DNS message, EASDF matches the DNS message based on the first identification information and the first association, EASDF determines an EDNS client subnet option by matching the DNS message, EASDF adds the determined EDNS client subnet option to the DNS message and transmits the DNS message to a DNS server.

[0040] Referring to the second embodiment, in some implementation of the second embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a fully qualified domain name (FQDN) and an EDNS client subnet option, the method further comprises: an EASDF receives a DNS message, the EASDF matches the DNS message based on the first identification information and the first association, the EASDF determines an EDNS client subnet option by matching the DNS message, and the EASDF adds the determined EDNS client subnet option to the DNS message and transmits the DNS message to a DNS server.

[0041] Referring to a second embodiment, in a part of the second embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a local DNS server address, the method further comprises: the EASDF receives a DNS message, the EASDF matches the DNS message based on the first identification information and the first association, the EASDF determines the local DNS server address by matching the DNS message, and the EASDF transmits the DNS message to the local DNS server.

[0042] Referring to a second embodiment, in a part of the second embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information, a fully qualified domain name (FQDN), and a local DNS server address, the method further comprises: an EASDF receives a DNS message, the EASDF matches the DNS message based on the first identification information and the first association, the EASDF determines the local DNS server address by matching the DNS message, and the EASDF transmits the DNS message to the local DNS server.

[0043] Based on the aforementioned technical solution, in this application, the EASDF can determine an ECS option or a local DNS server based on DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0044] Referring to the second embodiment, in a part of the second embodiment, where the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, the DNS processing parameter is an EDNS client subnet option, and the first identification information is a first DNAI, the method further comprises: the EASDF receives a DNS message from a terminal device, the EASDF matches a first association based on the first identification information, the EASDF determines an EDNS client subnet option by matching the first association, the EASDF adds the determined EDNS client subnet option to the DNS message and transmits the DNS message to a DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0045] Referring to the second embodiment, in a part of the second embodiment, where the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and an EDNS client subnet option, and the first identification information is a first DNAI, the method further comprises: the EASDF receives a DNS message from a terminal device, the EASDF matches a first association based on the first identification information and the DNS message, the EASDF determines an EDNS client subnet option by matching the first association, the EASDF adds the determined EDNS client subnet option to the DNS message and transmits the DNS message to a DNS server.

[0046] Based on the aforementioned technical solution, specifically in this application, when the identification information of the DNS processing information is a Data Network Access Identifier (DNAI), the DNS processing parameter may be an EDNS client subnet option, or the DNS processing parameter may be a correspondence between an FQDN and an EDNS client subnet option. Accordingly, the EASDF can determine the ECS option based on the DNS processing parameter. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0047] Referring to the second embodiment, in a part of the second embodiment, where the identification information of the DNS processing information is a data network access identifier, the DNS processing information is a DNS processing parameter, the DNS processing parameter is a local DNS server address, and the first identification information is a first DNAI, the method further comprises: the EASDF receives a DNS message from a terminal device, the EASDF matches a first association based on the first identification information, the EASDF determines a local DNS server address by matching the first association, and the EASDF transmits the DNS message to a local DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0048] Referring to the second embodiment, in a part of the second embodiment, where the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and a DNS processing parameter, and the first identification information is a first DNAI, the method further comprises: the EASDF receives a DNS message from a terminal device, the EASDF matches a first association based on the first identification information and the DNS message, the EASDF determines a local DNS server address by matching the first association, and the EASDF transmits the DNS message to a local DNS server.

[0049] Based on the aforementioned technical solution, specifically in this application, when the identification information of the DNS processing information is a Data Network Access Identifier (DNAI), the DNS processing parameter may be a local DNS server address or a correspondence between an FQDN and a local DNS server address. Accordingly, the EASDF can determine the local DNS server address based on the DNS processing parameter. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0050] Referring to the second embodiment, in a part of the second embodiment, DNS processing parameters are determined by an SMF based on the deployment information of an edge application server and the deployment information of a user plane function, and the deployment information of the edge application server includes one or more of the following: information regarding an FQDN corresponding to a DNAI, information regarding an Internet Protocol address of an edge application server, and identification information of a DNS server, and the deployment information of the user plane function includes the correspondence between a user plane function (UPF) and a DNAI.

[0051] In this application, it should be noted that the placement information of user plane functions further includes the correspondence between DNAI and ECS options.

[0052] Referring to the second embodiment, in a part of the second embodiment, the first message further includes first indication information, the first indication information instructs the EASDF to determine DNS processing information corresponding to the first PDU session based on first identification information and a first association.

[0053] Based on the aforementioned technical solution, in the present application, the first message may further include first indication information, and the indication of this indication information may enable the EASDF to determine DNS processing information corresponding to the first PDU session based on the first identification information and the first association. This improves information processing efficiency.

[0054] According to a third embodiment, a communication method is provided. The method comprises: a first network element obtains at least one group of second associations, wherein the second association is a correspondence between device group identifier information and deployment information of an edge application server, and the first network element transmits at least one group of second associations to a session management function (SMF).

[0055] Referring to the third embodiment, in a part of the third method embodiment, the deployment information of the edge application server includes one or more of the following: information regarding a fully qualified domain name (FQDN) corresponding to a data network access identifier (DNAI), information regarding an Internet protocol address of the edge application server, and identification information of a Domain Name System (DNS) server.

[0056] Referring to the third embodiment, in some implementation of the third method embodiment, the first network element is a unified data store (UDR) or unified data management (UDM).

[0057] Based on the aforementioned technical solution, in this application, the UDR or UDM can transmit at least one group of second associations to the SMF, so that the SMF can determine the first association based on the second associations and UPF placement information. This improves the flexibility of information processing.

[0058] According to a fourth embodiment, a communication system is provided. The system includes a session management function (SMF) and an edge application server discovery function (EASDF). The SMF acquires at least one group of first associations—wherein the first association is a correspondence between identification information of Domain Name System (DNS) processing information and DNS processing information—and transmits at least one group of first associations used in protocol data unit (PDU) sessions of a plurality of terminal devices to the edge application server discovery function (EASDF), and is configured to transmit a first message corresponding to the first PDU session to the EASDF, wherein the first message includes first identification information, and the first identification information is identification information of DNS processing information corresponding to the first PDU session. The EASDF receives at least one group of first associations used in PDU sessions of a plurality of terminal devices and the first message corresponding to the first PDU session, and is configured to determine DNS processing information corresponding to the first PDU session based on the first identification information and the first association.

[0059] According to the technical solution provided in this application, the SMF transmits to the EASDF the identification information of the Domain Name System (DNS) processing information, the correspondence between the DNS processing information, and the first message, so that the EASDF can receive the identification information of the Domain Name System (DNS) processing information, the correspondence between the DNS processing information, and the first message, and the EASDF determines the DNS processing information corresponding to the first PDU session based on the first identification information and the first association. In one embodiment, the SMF transmits the DNS processing rule based on the identification information of the DNS processing information to the EASDF. In this way, the EASDF can use different DNS processing information for different PDU sessions or UEs. This enables differentiated processing of DNS messages and improves the user's service experience. Additionally, the EASDF can determine ECS options and local server addresses based on DNS processing parameters. This prevents repetitive requests and transmissions of information, reduces signaling interactions, and improves information processing efficiency.

[0060] Referring to the fourth embodiment, in some implementation of the fourth embodiment, DNS processing information includes DNS detection information or DNS processing parameters, DNS detection information includes a full-qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range, and DNS processing parameters are correspondence between data network access identifier (DNAI) information and EDNS client subnet options, DNS processing parameters are correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and an EDNS client subnet option, DNS processing parameters are correspondence between data network access identifier (DNAI) information and a local DNS server address, or DNS processing parameters are correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and a local DNS server address.

[0061] Referring to the fourth embodiment, in a part of the fourth embodiment, where the DNS processing information is DNS detection information, the EASDF is specifically configured to receive a DNS message, match the DNS message based on the first identification information and the first association, and determine a processing action for the DNS message.

[0062] Referring to the fourth embodiment, in some implementation of the fourth embodiment, the DNS detection information further comprises information regarding a DNS message processing operation performed by the EASDF, which is determined based on the first identification information, and the processing operation includes one or more of reporting a DNS message, reporting the contents of a DNS message, caching a DNS message, and forwarding a DNS message.

[0063] Referring to the fourth embodiment, in a part of the implementation of the fourth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and an EDNS client subnet option, the EASDF is specifically configured to receive a DNS message, match the DNS message based on the first identification information and the first association, determine the EDNS client subnet option by matching the DNS message, add the determined EDNS client subnet option to the DNS message, and transmit the DNS message to a DNS server.

[0064] Referring to the fourth embodiment, in a part of the implementation of the fourth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information, a fully qualified domain name (FQDN), and an EDNS client subnet option, the EASDF is specifically configured to receive a DNS message, match the DNS message based on the first identification information and the first association, determine the EDNS client subnet option by matching the DNS message, add the determined EDNS client subnet option to the DNS message, and transmit the DNS message to a DNS server.

[0065] Referring to the fourth embodiment, in a part of the fourth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a local DNS server address, the EASDF is specifically configured to receive a DNS message, match the DNS message based on the first identification information and the first association, determine the local DNS server address by matching the DNS message, and transmit the DNS message to the local DNS server.

[0066] Referring to the fourth embodiment, in a part of the fourth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information, a fully qualified domain name (FQDN), and a local DNS server address, the EASDF is specifically configured to receive a DNS message, match the DNS message based on the first identification information and the first association, determine the local DNS server address by matching the DNS message, and transmit the DNS message to the local DNS server.

[0067] Referring to the fourth embodiment, in some implementations of the fourth embodiment, the SMF is further configured to determine DNS processing parameters based on the deployment information of the edge application server and the deployment information of the user plane function.

[0068] Referring to the fourth embodiment, in some implementation of the fourth embodiment, the deployment information of the edge application server includes one or more of information regarding an FQDN corresponding to a DNAI, information regarding an Internet Protocol address of the edge application server, and identification information of a DNS server, and the deployment information of the user plane function includes a correspondence between the user plane function (UPF) and the DNAI.

[0069] Referring to the fourth embodiment, in a part of the fourth embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is an EDNS client subnet option, wherein the first identification information is a first DNAI, and the EASDF is specifically configured to receive a DNS message from a terminal device, match a first association based on the first identification information, determine an EDNS client subnet option by matching the first association, add the determined EDNS client subnet option to the DNS message, and transmit the DNS message to a DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0070] Referring to the fourth embodiment, in a part of the fourth embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and an EDNS client subnet option, the first identification information is a first DNAI, and the EASDF is specifically configured to receive a DNS message from a terminal device, match a first association based on the first identification information and the DNS message, determine an EDNS client subnet option by matching the first association, add the determined EDNS client subnet option to the DNS message, and transmit the DNS message to a DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0071] Referring to the fourth embodiment, in a part of the fourth embodiment, the identification information of the DNS processing information is a data network access identifier, the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a local DNS server address, wherein the first identification information is a first DNAI, and the EASDF is specifically configured to receive a DNS message from a terminal device, match a first association based on the first identification information, determine a local DNS server address by matching the first association, and transmit the DNS message to a local DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0072] Referring to the fourth embodiment, in a part of the fourth embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and a DNS processing parameter, the first identification information is a first DNAI, and the EASDF is specifically configured to receive a DNS message from a terminal device, match a first association based on the first identification information and the DNS message, determine a local DNS server address by matching the first association, and transmit the DNS message to the local DNS server.

[0073] Referring to the fourth embodiment, in some implementation of the fourth embodiment, the system further comprises a first network element, the first network element being a unified data store (UDR) or unified data management (UDM), and the first network element is configured to acquire at least one group of second associations—the second associations being correspondences between device group identification information and deployment information of an edge application server—and to transmit the second associations to an SMF. The SMF is configured to receive at least one group of second associations.

[0074] Referring to the fourth embodiment, in some implementation of the fourth embodiment, the first message further includes first indication information, the first indication information instructs the EASDF to determine DNS processing information corresponding to the first PDU session based on first identification information and a first association.

[0075] According to the fifth embodiment, a device is provided. The device may be an SMF. Alternatively, the device may be a chip. The device has the function of implementing an SMF in any possible implementation of the first embodiment. This function may be implemented by hardware, or by the hardware executing the corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned function.

[0076] This device includes a transceiver unit and a processing unit. The processing unit is configured to acquire at least one group of first associations, the first association being a correspondence between identification information of Domain Name System (DNS) processing information and DNS processing information. The transceiver unit is configured to transmit at least one group of first associations used in Protocol Data Unit (PDU) sessions of a plurality of terminal devices. The transceiver unit is configured to transmit a first message corresponding to the first PDU session, the first message including first identification information, the first identification information being identification information of DNS processing information corresponding to the first PDU session, and the first identification information being used by the EASDF to determine DNS processing information corresponding to the first PDU session based on the first identification information and the first association.

[0077] Referring to the fifth embodiment, in some implementation of the fifth embodiment, DNS processing information includes DNS detection information or DNS processing parameters, and DNS detection information is used by EASDF to determine a processing action for a DNS message by matching a DNS message, and DNS processing parameters are used by EASDF to determine an EDNS client subnet option by matching a DNS message so that EASDF adds an EDNS client subnet option to a DNS message and transmits the DNS message to a DNS server, or DNS processing parameters are used by EASDF to determine a local DNS server address by matching a DNS message so that EASDF transmits the DNS message to a local DNS server, and the DNS message is received by EASDF from a terminal device or a DNS server.

[0078] Referring to the fifth embodiment, in some implementation of the fifth embodiment, where DNS processing information is DNS detection information, the DNS detection information includes a full-qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range.

[0079] Referring to the fifth embodiment, in some implementation of the fifth embodiment, the DNS detection information further comprises information regarding a DNS message processing operation performed by the EASDF, which is determined based on the first identification information, and the processing operation includes one or more of reporting a DNS message, reporting the contents of a DNS message, caching a DNS message, and forwarding a DNS message.

[0080] Referring to the fifth embodiment, in some implementation of the fifth embodiment, where DNS processing information is a DNS processing parameter, the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and EDNS client subnet options, or the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and an EDNS client subnet option, or the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a local DNS server address, or the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and a local DNS server address, wherein the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0081] Referring to the fifth embodiment, in a part of the fifth embodiment, where the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is an EDNS client subnet option, the first identification information is a first DNAI, and the first identification information is used by the EASDF to determine the EDNS client subnet option by matching the first association, so the EASDF adds the EDNS client subnet option to the DNS message and transmits the DNS message to the DNS server, the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0082] Referring to the fifth embodiment, in a part of the fifth embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and an EDNS client subnet option, the first identification information is a first DNAI, and the first identification information and the DNS message are used by the EASDF to determine the EDNS client subnet option by matching the first association, so the EASDF adds the EDNS client subnet option to the DNS message and transmits the DNS message to the DNS server, the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0083] Referring to the fifth embodiment, in a part of the fifth embodiment, the identification information of the DNS processing information is a data network access identifier, the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a local DNS server address, the first identification information is a first DNAI, the first identification information is used by the EASDF to determine the local DNS server address by matching the first association, and the EASDF transmits a DNS message to the local DNS server, the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0084] Referring to the fifth embodiment, in a partial implementation of the fifth embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and a DNS processing parameter, the first identification information is a first DNAI, and the first identification information and the DNS message are used by the EASDF to determine the local DNS server by matching the first association, and the EASDF transmits the DNS message to the local DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device, the DNS message is received by the EASDF from the terminal device, and the DNS processing parameter is determined by the SMF based on the deployment information of the edge application server and the deployment information of the user plane function.

[0085] Referring to the fifth embodiment, in some implementation of the fifth embodiment, the deployment information of the edge application server includes one or more of information regarding an FQDN corresponding to a DNAI, information regarding an Internet Protocol address of the edge application server, and identification information of a DNS server, and the deployment information of the user plane function includes a correspondence between the user plane function (UPF) and the DNAI.

[0086] Referring to the fifth embodiment, in some implementation of the fifth embodiment, the first message further includes first indication information, the first indication information instructs the EASDF to determine DNS processing information corresponding to the first PDU session based on first identification information and a first association.

[0087] According to the sixth embodiment, a communication device is provided, and the device may be an EASDF. Alternatively, the device may be a chip. The device has the function of implementing the EASDF in a possible implementation of the second embodiment. This function may be implemented in hardware, or the hardware may be implemented by executing the corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned function.

[0088] The device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive at least one group of first associations used in Protocol Data Unit (PDU) sessions of a plurality of terminal devices, wherein the first association is a correspondence between identification information of Domain Name System (DNS) processing information and DNS processing information. The transceiver unit is configured to receive a first message, wherein the first message includes first identification information, and the first identification information is identification information of DNS processing information corresponding to the first PDU session. The processing unit is configured to determine DNS processing information corresponding to the first PDU session based on the first identification information and the first association.

[0089] Referring to the sixth embodiment, in some implementation of the sixth embodiment, DNS processing information includes DNS detection information or DNS processing parameters. DNS detection information includes a full-qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range, and DNS processing parameters are correspondence between data network access identifier (DNAI) information and EDNS client subnet options, or DNS processing parameters are correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and an EDNS client subnet option, or DNS processing parameters are correspondence between data network access identifier (DNAI) information and a local DNS server address, or DNS processing parameters are correspondence between data network access identifier (DNAI) information and a full-qualified domain name (FQDN) and a local DNS server address.

[0090] Referring to the sixth embodiment, in a part of the sixth embodiment, where DNS processing information is DNS detection information, a transceiver unit is configured to receive a DNS message, a processing unit is configured to match a DNS message based on first identification information and a first association, and a processing unit is configured to determine a processing action for a DNS message.

[0091] Referring to the sixth embodiment, in some implementation of the sixth embodiment, the DNS detection information further comprises information regarding a DNS message processing operation performed by the EASDF, which is determined based on the first identification information, and the processing operation includes one or more of reporting a DNS message, reporting the contents of a DNS message, caching a DNS message, and forwarding a DNS message.

[0092] Referring to the sixth embodiment, in a part of the sixth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and an EDNS client subnet option, a transceiver unit is configured to receive a DNS message, a processing unit is configured to match a DNS message based on the first identification information and the first association, a processing unit is configured to determine an EDNS client subnet option by matching the DNS message, a processing unit is configured to add the determined EDNS client subnet option to a DNS message, and a transceiver unit is configured to transmit a DNS message with the added EDNS client subnet option to a DNS server.

[0093] Referring to the sixth embodiment, in a part of the implementation of the sixth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information, a fully qualified domain name (FQDN), and an EDNS client subnet option, a transceiver unit is configured to receive a DNS message, a processing unit is configured to match a DNS message based on the first identification information and the first association, the processing unit is configured to determine an EDNS client subnet option by matching the DNS message, the processing unit is configured to add the determined EDNS client subnet option to the DNS message, and the transceiver unit is configured to transmit the DNS message with the added EDNS client subnet option to a DNS server.

[0094] Referring to the sixth embodiment, in a part of the sixth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information and a local DNS server address, a transceiver unit is configured to receive a DNS message, a processing unit is configured to match a DNS message based on the first identification information and the first association, a processing unit is configured to determine a local DNS server address by matching the DNS message, and a transceiver unit is configured to transmit a DNS message to a local DNS server.

[0095] Referring to the sixth embodiment, in a part of the sixth embodiment, where DNS processing information is a DNS processing parameter and the DNS processing parameter is a correspondence between data network access identifier (DNAI) information, a fully qualified domain name (FQDN), and a local DNS server address, a transceiver unit is configured to receive a DNS message, a processing unit is configured to match a DNS message based on the first identification information and the first association, the processing unit is configured to determine a local DNS server address by matching the DNS message, and the processing unit is configured to transmit a DNS message to a local DNS server.

[0096] Referring to the sixth embodiment, in a part of the sixth embodiment, where the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is an EDNS client subnet option, the first identification information is a first DNAI, the transceiver unit is configured to receive a DNS message from a terminal device, the processing unit is configured to match a first association based on the first identification information, the processing unit is configured to determine an EDNS client subnet option by matching the first association, the processing unit is configured to add the determined EDNS client subnet option to a DNS message, and the transceiver unit is configured to transmit a DNS message with the added EDNS client subnet option to a DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0097] Referring to the sixth embodiment, in a part of the sixth embodiment, the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and an EDNS client subnet option, the first identification information is a first DNAI, the transceiver unit is configured to receive a DNS message from a terminal device, the processing unit is configured to match a first association based on the first identification information and the DNS message, the processing unit is configured to determine an EDNS client subnet option by matching the first association, the processing unit is configured to add the determined EDNS client subnet option to the DNS message, and the transceiver unit is configured to transmit the DNS message with the added EDNS client subnet option to a DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0098] Referring to the sixth embodiment, in a part of the sixth embodiment, where the identification information of the DNS processing information is a data network access identifier, the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a local DNS server address, the first identification information is a first DNAI, the transceiver unit is configured to receive a DNS message from a terminal device, the processing unit is configured to match a first association based on the first identification information, the processing unit is configured to determine a local DNS server address by matching the first association, and the transceiver unit is configured to transmit a DNS message to a local DNS server, wherein the first DNAI is a DNAI associated with the location of the terminal device.

[0099] Referring to the sixth embodiment, in a part of the sixth embodiment, where the identification information of the DNS processing information is a data network access identifier (DNAI), the DNS processing information is a DNS processing parameter, and the DNS processing parameter is a correspondence between a fully qualified domain name (FQDN) and a DNS processing parameter, the first identification information is a first DNAI, the transceiver unit is configured to receive a DNS message from a terminal device, the processing unit is configured to match a first association based on the first identification information and the DNS message, the processing unit is configured to determine a local DNS server address by matching the first association, and the transceiver unit is configured to transmit the DNS message to a local DNS server.

[0100] Referring to the sixth embodiment, in some implementation of the sixth embodiment, DNS processing parameters are determined by an SMF based on the deployment information of an edge application server and the deployment information of a user plane function, and the deployment information of the edge application server includes one or more of the following: information regarding an FQDN corresponding to a DNAI, information regarding an Internet Protocol address of an edge application server, and identification information of a DNS server, and the deployment information of the user plane function includes the correspondence between a user plane function (UPF) and a DNAI.

[0101] Referring to the sixth embodiment, in some implementation of the sixth embodiment, the first message further includes first indication information, the first indication information instructs the EASDF to determine DNS processing information corresponding to the first PDU session based on first identification information and first association.

[0102] According to the seventh embodiment, a communication device is provided. This device may be a first network element, e.g., a UDR or a UDM. This device may alternatively be a chip. This device has the function of implementing the first network element in any possible implementation of the third embodiment. This function may be implemented in hardware, or the hardware may be implemented by running the corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned function.

[0103] This device includes a transceiver unit and a processing unit. The processing unit is configured to acquire at least one group of second associations, the second association being a correspondence between device group identification information and placement information of an edge application server. The transceiver unit is configured to transmit the second association.

[0104] Referring to the seventh embodiment, in some implementation of the seventh embodiment, the deployment information of an edge application server includes one or more of information regarding a fully qualified domain name (FQDN) corresponding to a data network access identifier (DNAI), information regarding an Internet protocol address of the edge application server, and identification information of a Domain Name System (DNS) server.

[0105] According to the eighth embodiment, a communication device is provided, which includes a processor. The processor is coupled to memory and may be configured to execute instructions in memory to implement the function of an SMF in any possible implementation of the first embodiment. Optionally, the device further includes memory. Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0106] In the implementation, this device is an SMF. If this device is an SMF, the communication interface may be a transceiver or an input / output interface.

[0107] In another implementation, this device is a chip configured in an SMF. If this device is a chip configured in an SMF, the communication interface may be an input / output interface.

[0108] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0109] According to the ninth embodiment, a communication device is provided, which includes a processor. The processor is coupled to memory and may be configured to execute instructions in memory to implement the function of an EASDF in any possible implementation of the second embodiment. Optionally, the device further includes memory. Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0110] In the implementation, this device is an EASDF. If this device is an EASDF, the communication interface may be a transceiver or an I / O interface.

[0111] In another implementation, the device is a chip configured in the EASDF. If this device is a chip configured in the EASDF, the communication interface may be an I / O interface.

[0112] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0113] According to the tenth embodiment, a communication device is provided, which includes a processor. The processor is coupled to memory and may be configured to execute instructions in memory to implement the function of a first network element in any possible implementation of the third embodiment. For example, the device may be a UDR or a UDM. Optionally, the device further includes memory. Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface.

[0114] In the implementation, this device is a first network element. If this device is a first network element, the communication interface may be a transceiver or an input / output interface.

[0115] In another implementation, this device is a chip configured in a first network element. If this device is a chip configured in a first network element, the communication interface may be an input / output interface.

[0116] Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0117] According to the eleventh embodiment, a processor is provided, comprising an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, thereby enabling the processor to perform a method in any one of the first to third embodiments or a possible implementation of the first to third embodiments.

[0118] In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, etc. An input signal received by the input circuit may be received and input by, for example, a receiver (but not limited thereto), and a signal output by the output circuit may be output to, for example, a transmitter (but not limited thereto) and transmitted by it, and the input circuit and the output circuit may be the same circuit, wherein the circuit is used as the input circuit and the output circuit at different moments. Specific implementations of the processor and various circuits are not limited to the embodiments of this application.

[0119] According to the 12th embodiment, a device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory, receive a signal using a receiver, and transmit a signal using a transmitter to perform a method in any one of the first to third embodiments or possible implementations of the first to third embodiments.

[0120] Optionally, there is one or more processors and one or more memories.

[0121] Optionally, the memory may be integrated with the processor, or the memory and processor may be placed separately.

[0122] In a specific implementation process, the memory may be a non-transitory memory, such as read-only memory (ROM). The memory and processor may be integrated on a single chip or placed separately on different chips. The type of memory and the manner in which the memory and processor are placed are not limited to the embodiments of this application.

[0123] It should be understood that related data exchange processes, such as the transmission of display information, may be processes that output display information from a processor, and the reception of capability information may be processes that receive input capability information from a processor. Specifically, data output by a processor may be output to a transmitter, and input data received by a processor may originate from a receiver. Transmitters and receivers may be collectively referred to as transceivers.

[0124] The device of the 12th embodiment may be a chip. The processor may be implemented using hardware or software. If the processor is implemented using hardware, the processor may be a logic circuit, an integrated circuit, etc. Alternatively, if the processor is implemented using software, the processor may be a general-purpose processor and may be implemented by reading software code stored in memory. The memory may be integrated into the processor or may exist independently outside the processor.

[0125] According to the 13th embodiment, a computer program product is provided. The computer program product includes a computer program (which may also be referred to as code or instructions), and when the computer program is executed, the computer is able to perform a method in any one of the first through third embodiments or a possible implementation of the first through third embodiments.

[0126] According to the 14th embodiment, a computer-readable medium is provided. The computer-readable medium stores a computer program (which may also be referred to as code or instructions), and when the computer program is executed on a computer, the computer is able to perform a method in any one of the first to third embodiments or a possible implementation of the first to third embodiments.

[0127] According to the 15th embodiment, a chip system comprising a processor is provided, wherein the processor is configured to call a computer program from memory and execute the computer program so as to enable a device on which the chip system is installed to perform a method in any one of the first to third embodiments or a possible implementation of the first to third embodiments.

[0128] According to the 16th embodiment, a system is provided. The system includes a device of the 5th embodiment, a device of the 6th embodiment, and a device of the 7th embodiment. Brief explanation of the drawing

[0129] FIG. 1 is a drawing of a system architecture to which an embodiment of the present application can be applied. FIG. 2 is a schematic flowchart of a communication method (200) according to the present application. FIG. 3 is a schematic flowchart of a communication method (300) according to the present application. FIG. 4 is a schematic flowchart of a communication method (400) according to the present application. FIG. 5 is a schematic flowchart of a communication method (500) according to the present application. FIG. 6 is a schematic block diagram of a communication device (100) according to the present application. FIG. 7 is a schematic block diagram of a communication device (200) according to the present application. Specific details for implementing the invention

[0130] The following describes the technical solution of the present application with reference to the attached drawings.

[0131] The wireless communication system mentioned in the embodiments of the present application includes, but is not limited to, a global system for mobile communications (GSM) system, a long term evolution (LTE) frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, an LTE system, an LTE-Advanced (LTE-A) system, a next-generation communication system (e.g., a 6G communication system), a system integrating multiple access systems, or an evolved system.

[0132] The technical solution provided in this application may also be applied to machine-type communication (MTC), machine-to-machine communication Long Term Evolution-machine (LTE-M) technology, device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of Things (IoT) networks, or other networks. IoT networks may include, for example, the Internet of Vehicles. Communication methods in a vehicle internet system are collectively referred to as vehicle to X (V2X, where X may represent anything). For example, V2X may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0133] The following describes in detail the network system architecture related to an embodiment of the present application with reference to FIG. 1.

[0134] FIG. 1 is a diagram of a system architecture to which an embodiment of the present application may be applied. As illustrated in the diagram, the network architecture may specifically include the following network elements.

[0135] 1. Radio Access Network (RAN): An access network that implements network access functions based on wireless communication technology may be referred to as a radio access network. A radio access network can manage wireless resources, provide access services to terminals, and further complete the transmission of control signals and user data between terminals and a core network.

[0136] The wireless access network device related to the present application may be a device equipped with a wireless transceiver function. The wireless access network device may be a device that provides wireless communication function services and is generally located on the network side, and includes, but is not limited to, a next-generation NodeB (gNodeB, gNB) of a 5th generation (5G) communication system, a next-generation NodeB of a 6th generation (6G) mobile communication system, a base station of a future mobile communication system, an access node of a Wi-Fi system, an evolved NodeB (eNB) of an LTE system, a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a home NodeB (e.g., an evolved home NodeB or home NodeB, HNB), a base band unit (BBU), a transmission receive point (TRP), a transmitting point (TP), and a base transceiver station (BTS). In a network structure, an access network device may include a central unit (CU) node, a distributed unit (DU) node, a RAN device including a CU node and a DU node, or a RAN device including a CU control plane node, a CU user plane node, and a DU node. The access network device may service a cell, and user equipment communicates with a base station using transmission resources (e.g., frequency domain resources or frequency spectrum resources) used by the cell. A cell may be a cell corresponding to a base station (e.g., a base station). A cell may belong to a macro base station or to a base station corresponding to a small cell.Here, small cells may include metro cells, micro cells, pico cells, femto cells, etc. These small cells are characterized by small coverage and low transmission power, making them applicable to data transmission services that provide high speed. The wireless access network device may be a macro base station, a micro base station or an indoor base station, a relay node or a donor node, a device that provides wireless communication services to a user terminal in a V2X communication system, a wireless controller in a cloud radio access network (CRAN) scenario, a relay station, a vehicle-mounted device, a wearable device, a network device in a future evolved network, etc. The specific technology and specific device type used by the wireless access network device are not limited to the embodiments of this application.

[0137] 2. User equipment (UE): In the embodiments of the present application, the UE may be a network terminal device such as a mobile phone or an Internet of Things terminal device. Specifically, for example, the terminal device may be user equipment (UE), for example, a mobile phone, a tablet computer (pad), a computer having a wireless transceiver function, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal device. Alternatively, the terminal device may be a wireless terminal in industrial control, a machine type communication (MTC) terminal, customer premises equipment (CPE), a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a smart home, a mobile phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device, or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future advanced Public Land Mobile Network (PLMN).

[0138] 3. Access and Mobility Management Function (AMF): The access and mobility management function is primarily used for mobility management, access management, etc., and can be used to implement functions such as legitimate blocking functions or access authorization (or authentication) functions, other than the session management functions of a mobility management entity (MME). In the embodiments of the present application, the AMF can be used to implement the functions of the access and mobility management function.

[0139] 4. Session management function (SMF): The session management function is primarily used for session management, allocation and management of Internet Protocol (IP) addresses of terminal devices, user plane functions, selection and management of interfaces for policy control functions or billing functions, downlink data notifications, etc. In the embodiments of the present application, the SMF may be used to implement the functions of the session management function.

[0140] 5. Policy Control Function (PCF): The policy control function is an integrated policy framework for guiding network behavior and provides policy rule information, etc., to control plane functions (e.g., AMF or SMF).

[0141] 6. Application function (AF): Application functions are used to perform data routing that affects the application, access network exposure functions, or interact with the policy framework to perform policy control.

[0142] 7. Unified Data Management (UDM): Unified data management is used to perform unified data management, 5G user data management, user identifier processing, access authentication, registration, mobility management, etc.

[0143] 8. Unified Data Repository (UDR): The unified data repository is used by the UDM to store or read subscription data, or by the PCF to store or read policy data.

[0144] 9. User plane function (UPF): A user plane function may be used for performing packet routing and forwarding, performing quality of service (QoS) processing for user plane data, etc. User data may access a data network (DN) through a user plane function. In an embodiment of the present application, a user plane function may be configured to implement the functions of a user plane function.

[0145] 10. Data network (DN): A data network is a network that provides data transmission, for example, a carrier service network, the Internet, and a third-party service network.

[0146] 11. Network repository function (NRF): The network repository function stores descriptive information about network function entities and services provided by network function entities, and is used to support functions such as service discovery and network element entity discovery.

[0147] 12. Network Exposure Function (NEF): The network exposure function is used to securely expose to the outside services, capabilities, etc. provided by the 3rd Generation Partnership Project (3GPP) network functions.

[0148] 13. Edge Application Server (EAS): In an edge computing (EC) deployment scenario, some services may be provided by multiple EASs deployed at the network edge. These EASs provide the same services and content but have different Internet Protocol (IP) addresses (anycast addresses are not included or considered in this application). When a UE needs to access a service, in an EC scenario, the UE must access the available EAS closest to the UE.

[0149] 14. Edge Application Server Discovery Function (EASDF): The Edge Application Server Discovery Function is the EASDF, a new network element that assists in EAS discovery. The primary function of the EASDF is to process Domain Name System (DNS) messages based on instructions from the SMF. For example, the EASDF reports DNS messages to the SMF, adds extended mechanisms for DNS (EDNS) client subnet options (EDNS client subnet options are also referred to as "ECS options" for short) to DNS queries, forwards DNS queries to DNS servers, and forwards DNS responses to UEs.

[0150] In the network architecture, the N2 interface is configured to transmit non-access stratum (NAS) messages, etc., as an interface between the RAN and the AMF; the N3 interface is configured to transmit user plane data, etc., as an interface between the RAN and the UPF; the N4 interface is configured to transmit information such as identification information, data buffer indication information, and downlink data notification messages of the tunnel connected to the N3 interface, as an interface between the SMF and the UPF; the N6 interface is configured to transmit user plane data between the UPF and the DN; and the N9 interface is an interface between the UPFs, for example, the N9 interface may be an interface between the visited-policy control function (V-PCF) and the home-policy control function (H-PCF), or an interface between a UPF connected to the DN and a UPF connected to the RAN, and the N9 interface is configured to transmit user plane data between the UPFs.

[0151] It should be understood that the aforementioned network architecture applied to the embodiments of this application is merely an example of a network architecture described in terms of conventional point-to-point architecture and service-based architecture, and that the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of implementing the functions of the aforementioned network elements is applicable to the embodiments of this application.

[0152] It should be noted that the names of network elements in this application are merely examples. This application does not exclude cases where network elements may be given different names in the future or where the functions of network elements are combined. As technology advances, any device or network element capable of implementing the functions of the aforementioned network elements falls within the scope of protection of this application.

[0153] It should be understood that the names of the interfaces between the network elements of FIG. 1 are merely examples. In certain implementations, the interfaces may have different names. This is not specifically limited in this application. Also, the names of the messages (or signaling) transmitted between the aforementioned network components are merely examples and do not constitute any limitation on the function of the messages.

[0154] To facilitate understanding of the technical solution of the present application, the protocol data unit (PDU) session is briefly described below with reference to the content related to the technical solution of the present application.

[0155] A PDU session is the process by which a User End User (UE) communicates with a Data Network (DN). Once a PDU session is established, a data transmission channel is established between the UE and the DN. Each PDU session supports one PDU session type (e.g., IPv4, IPv6, IPv4v6, Ethernet, and unstructured). A single PDU session can have multiple PDU session anchors. To support the ability to select routing to the DN and to support Service and Session Continuity (SSC) mode 3, the SMF can control the data routing of the PDU session to enable the PDU session to have multiple N6 interfaces simultaneously. The UPF of each N6 interface can be referred to as a PDU session anchor. Multiple PDU session anchors for a single PDU session can be implemented in the following two ways.

[0156] Method 1: Uses an uplink classifier (UL CL) in a single PDU session.

[0157] The SMF can insert the uplink classifier "UL CL" into the data transmission path of a PDU session. The function of "UL CL" can be provided within the UPF. "UL CL" is used to forward data packets that satisfy service filtering rules, similar to the function of a routing table, to a specified path. The SMF controls the insertion and deletion of "UL CL". The SMF can perform actions on the UPF through the N4 interface. The SMF determines whether to perform actions on the UPF based on the UPF's capability, namely whether the UPF supports 'UL CL'. The UE is unaware of the data transmission function of "UL CL" in the core network. Therefore, the UE does not participate in the insertion and deletion of "UL CL". When "UL CL" is inserted into the data path of a PDU session, the PDU session has multiple PDU session anchors, and these anchors provide multiple different paths to the same DN. The function of "UL CL" is to transmit uplink service data to different PDU session anchors based on filter requirements and to combine downlink data from multiple anchors of the UE.

[0158] Figure 1 can be considered a scenario in which one PDU session has two PDU session anchors. An uplink classifier (UL CL) is installed at the UPF at the end of the N3 interface, and an anchor (C-PSA) and an anchor (L-PAS) are terminated at the N6 interface, and transmission between the uplink classifier UPF and the anchor UPF is performed through the N9 interface.

[0159] Method 2: Uses IPv6 multi-homing in a single PDU session.

[0160] A single PDU session can be associated with multiple IPv6 prefixes, and the PDU session is referred to as a multihomed PDU session. A multihomed PDU session can access a single data network (DN) through multiple PDU session anchors. Data paths corresponding to all PDU session anchors eventually converge on a common UPF, which has a branching point (BP) function, and is referred to as a branching point UPF. Branching points forward uplink service packets to different PDU anchors and combine downlink data from the anchors. Branching point UPFs can be used for billing statistics and rate control. The SMF controls the insertion or removal of branching points in the UPF through the N4 interface. The SMF performs the aforementioned operations depending on the capabilities of the UPF, namely whether the UPF supports the branching point function.

[0161] Figure 1 can be considered a scenario where a single PDU session has two PDU session anchors. If the network needs to switch the anchor of the access network, a new anchor accessing the same data network is established first (e.g., the L-PDU session anchor (L-PSA) in Figure 1), and then the old anchor (e.g., the C-PSA in Figure 1) is released. During the anchor switching process, the UE can acquire continuous service, and the service is unaffected.

[0162] The foregoing briefly describes the PDU session. To better understand the technical solutions of the embodiments of this application, nouns or terms in this application are briefly explained before describing the embodiments of this application.

[0163] (1) Data Network Name (DNN): The Data Network Name (DNN) can be used to select the SMF and UPF for establishing a Protocol Data Unit (PDU) session, or to determine the policy applied to the PDU session. The DNN consists of two parts: (1) a network identification (ID) that represents an external network and is mandatory, and (2) an operator ID that represents the operator to which the DNN belongs and is optional.

[0164] (2) Single Network Slice Selection Assistance Information (S-NSSAI): Single Network Slice Selection Assistance Information can uniquely identify network slices and may include one or more Data Network Names (DNNs) for the AMFs to be selected. The SMFs selected for a PDU session are specified in the DNNs. An NSSAI is a set of S-NSSAIs and can identify network slice groups. When a UE is performing a service, the UE can select a corresponding slice group (including AMFs / SMFs / UPFs) based on the S-NSSAIs. When a UE performs an attach operation, the UE provides S-NSSAI information, and the gNB selects a 5G core network (5GC) based on the S-NSSAI information. If the UE does not provide relevant S-NSSAI information, the gNB routes the UE's NAS information to the default 5GC.

[0165] (3) Data network access identifier (DNAI): A data network access identifier is an identifier for user plane access of one or more DNs where application processes are deployed.

[0166] In 4G and earlier existing mobile network architectures and deployments, user plane devices are deployed in a tree topology. Uplink user packets pass through base stations and backhaul networks, eventually accessing the data network via a centrally located anchor gateway. These anchor gateways are typically placed at high locations within the network (e.g., a central equipment room in a wide area). This topological structure is simple and facilitates centralized service management, control, and packet processing by operators at the anchor. However, as mobile service traffic has increased explosively, this type of deployment mode is becoming increasingly difficult to support rapidly growing mobile service traffic models. In one aspect, in networks where anchor gateways are centrally deployed, increased traffic eventually concentrates at the gateways and core equipment rooms. This leads to increasingly higher requirements for backhaul network bandwidth, equipment room throughput, and gateway specifications. In another aspect, backhaul networks with long distances from access points to anchor gateways and complex transport environments also cause significant latency and jitter in user packet transmission.

[0167] Based on the aforementioned background, the concept of edge computing (EC) is being proposed in the industry. EC enables the local processing of distributed service traffic by moving UPF and service processing capabilities to the downstream network edge. This prevents excessive traffic concentration and significantly reduces specification requirements for core equipment rooms and centralized gateways. Furthermore, the distance of the backhaul network is shortened, and end-to-end (E2E) latency and jitter of user packets are reduced. This enables the deployment of services with very low latency.

[0168] As previously mentioned, in an EC deployment scenario, some services may be provided by multiple EASs deployed at the network edge. These EASs provide the same services and content but have different IP addresses (anycast addresses are not included or considered in this application). When a UE needs to access a service, in an EC scenario, the UE must access the available EAS closest to the UE. Therefore, the UE must obtain the IP address of the appropriate EAS. The 3rd Generation Partnership Project (3GPP) standard TS 23.548 defines the EASDF, a new network element that supports EAS discovery. The primary function of the EASDF is to process Domain Name System (DNS) messages based on instructions from the SMF.

[0169] The procedure for discovering an EAS using EASDF is as follows: After the SMF selects the EASDF during the session establishment process, the SMF transmits DNS processing rules to the EASDF via a PDU session (i.e., DNS processing rules are transmitted on a session basis). The DNS processing rules include one or more of the following: information regarding the fully qualified domain name (FQDN), information regarding the EAS's IP address, and information regarding the DNS server identifier. The FQDN range and the EAS IP address range indicate the deployment status of the edge service. If the service's FQDN or EAS IP address falls within the above ranges, it indicates that the service is deployed at the local edge. When the EASDF receives a DNS query from a UE, the EASDF matches the FQDN included in the DNS query with the aforementioned FQDN ranges. If the FQDN falls within the FQDN range, the EASDF transmits a DNS message report to the SMF and obtains ECS options from the SMF. ECS options are extension items within the DNS message that indicate the UE's location information. EASDF adds the ECS option to the DNS query and forwards the DNS query to the DNS server. After receiving the DNS response from the DNS server, EASDF matches the EAS IP address included in the DNS response with the aforementioned EAS IP address range. If the EAS IP address falls within the EAS IP address range, EASDF sends a DNS message report to the SMF, and the SMF inserts "UL CL" or "BP" and instructs EASDF to forward the DNS response to the UE, thereby completing the local service discovery.

[0170] From the aforementioned procedure, it can be seen that when the SMF transmits EAS deployment information to the EASDF on a session basis, the EAS deployment information transmitted across multiple PDU sessions is identical. Consequently, the information is transmitted repeatedly. Therefore, at the 3GPP SA WG2#145E meeting, a technique for transmitting EAS node-level deployment information was adopted. "Node level" refers to transmitting information at the device granularity level. That is, the SMF obtains EAS deployment information from the UDR at the device level and transmits node-level DNS processing rules to the EASDF at the device level.

[0171] However, in the current procedure where the SMF obtains EAS deployment information from the UDR, node-level transport technology is used, yet all PDU sessions and all UEs using the same EASDF share the same DNS processing rules. In practice, different UEs or different PDU sessions have different permissions for the services that can be accessed via EC. For example, only UE #1 and UE #3 can access Service #A, while other UEs do not have permission to access Service #A. If the current technical solution is used, all UEs using the same EASDF (e.g., UE #1 through UE #10) can access Service #A. Furthermore, from the previously described procedure, it can be seen that ECS options are transmitted and stored on a session-by-session basis. Since the EASDF requests ECS options from the SMF after receiving a DNS query for each PDU session, a large amount of ECS options are repeated. Therefore, a communication method is required to address the problem where different UEs or PDU sessions have different permissions to access EC services, and such a communication method can be used to resolve the issue of ECS options being repeatedly requested and transmitted across different PDU sessions.

[0172] In this regard, the present application provides a communication method. The SMF transmits to the EASDF the correspondence between the identification information of the Domain Name System (DNS) processing information and the DNS processing information. The SMF transmits to the EASDF DNS processing rules based on the identification information of the DNS processing information so that the EASDF can use different DNS processing information for different PDU sessions or UEs. This further implements differentiated processing of DNS messages, resolves the problem of different UEs having different permissions to access EC services, and improves the user's service experience. Additionally, repetitive transmission of information can be avoided, signaling interactions can be reduced, and information processing efficiency can be improved.

[0173] It should be noted that in the following embodiments of this application, the operation of the UDR may be performed by the UDM. In the following embodiments of this application, the UDR is merely an example for illustrative purposes. It is not limited thereto.

[0174] It should be noted that in the following embodiments of the present application, a terminal device is described using, for example, a user device (UE).

[0175] FIG. 2 is a schematic flowchart of a communication method (200) according to the present application. The method of FIG. 2 includes the following steps.

[0176] Step 201: The session management function (SMF) acquires at least one group of the first associations.

[0177] The first association is the correspondence between the identification information of Domain Name System (DNS) processing information and the DNS processing information.

[0178] In the present application, the identification information of the DNS processing information identifies the DNS processing information and may be one of a UE group ID, a rule ID, DNAI, DNN, S-NSSAI, or a similar one. The rule ID represents the corresponding rule.

[0179] In a possible implementation, the SMF can determine a first association based on the acquired second association (i.e., the association between the UE group ID and the deployment information of the EAS) and the UE group ID.

[0180] In a possible implementation, the SMF can determine the first association based on the acquired second association, UE group ID, and rule ID.

[0181] In a possible implementation, the first association can be configured in the EASDF.

[0182] In the present application, DNS processing information may include DNS detection information or DNS processing parameters. Alternatively, DNS processing information may include DNS detection information and DNS processing parameters.

[0183] In the present application, the deployment information of the EAS includes one or more of the following: information regarding an FQDN corresponding to a DNAI, information regarding an Internet Protocol address of an edge application server, and identification information of a DNS server.

[0184] In the present application, where DNS processing information is DNS detection information, the DNS detection information may be used by the EASDF to determine a DNS message processing action corresponding to a DNS message. Specifically, the DNS detection information may be used by the EASDF to determine a processing action for a DNS message by matching a DNS message. For example, the DNS detection information may include a Fully Qualified Domain Name (FQDN) range and / or an Edge Application Server Internet Protocol address range. As another example, the DNS detection information may include a Fully Qualified Domain Name (FQDN) range and / or an Edge Application Server Internet Protocol address range and information regarding a DNS message processing action. A DNS message processing action may include one or more of reporting a DNS message, reporting the contents within a DNS message, caching a DNS message, and forwarding a DNS message.

[0185] In the present application, where DNS processing information is a DNS processing parameter, the DNS processing parameter may be a correspondence between DNAI and an ECS option and is used by the EASDF to determine the ECS option, or the DNS processing parameter may be a correspondence between DNAI, an FQDN, and an ECS option and is used by the EASDF to determine the ECS option, or the DNS processing parameter may be a correspondence between DNAI and a local DNS server address and is used by the EASDF to determine the local DNS server address, or the DNS processing parameter may be a correspondence between DNAI, an FQDN, and a local DNS server address and is used by the EASDF to determine the local DNS server address.

[0186] In the present application, where the identification information of the DNS processing information is DNAI and the DNS processing information is a DNS processing parameter, the DNS processing parameter may be an EDNS client subnet option, or where the identification information of the DNS processing information is DNAI and the DNS processing information is a DNS processing parameter, the DNS processing parameter may be a correspondence between an FQDN and an EDNS client subnet option, or where the identification information of the DNS processing information is DNAI and the DNS processing information is a DNS processing parameter, the DNS processing parameter may be a local DNS server address, or where the identification information of the DNS processing information is DNAI and the DNS processing information is a DNS processing parameter, the DNS processing parameter may be a correspondence between an FQDN and a local DNS server address.

[0187] Step 202: The SMF transmits at least one group of first associations used in the Protocol Data Unit (PDU) session of multiple terminal devices to the EASDF. In response, the EASDF receives at least one group of first associations used in the Protocol Data Unit (PDU) session of multiple terminal devices.

[0188] In the present application, the EASDF may acquire at least one group of a first association used in a PDU session of a plurality of UEs, where "a plurality of UEs" may be understood as a plurality or all UEs to which the first association can be applied. A plurality of PDU sessions may be understood as a plurality or all PDU sessions to which the first association is applied.

[0189] In a possible implementation, the SMF may send a request to the EASDF to create a "node-level DNS context," wherein the request includes a first association. In another possible implementation, this step may alternatively be triggered when the SMF receives a request to establish a PDU session or in other ways. This is not limited to the provisions of this specification.

[0190] Step 203: SMF transmits a first message to EASDF corresponding to the first UE or first PDU session, the first message including first identification information. In response, EASDF receives the first message.

[0191] In the present application, the first identification information is identification information of DNS processing information corresponding to the first UE or the first PDU session, and the first identification information is used by the EASDF to determine DNS processing information corresponding to the first PDU session based on the first identification information and the first association.

[0192] For example, the first identification information may be a UE group ID, rule ID, DNAI, DNN, S-NSSAI, etc.

[0193] Step 204: The EASDF determines DNS processing information corresponding to the first UE or first PDU session based on the first identification information and the first association.

[0194] In a possible implementation, the EASDF can determine a processing action for a DNS message based on first identification information and a first association. Specifically, the EASDF matches DNS messages based on first identification information and a first association and determines a processing action for the DNS message.

[0195] In a possible implementation, the EASDF can determine an ECS option or a local DNS server address based on the first identification information and the first association.

[0196] For example, the EASDF matches DNS messages based on first identification information and first associations, and determines EDNS client subnet options by matching DNS messages. The EASDF adds the determined EDNS client subnet options to the DNS message and sends the DNS message to the DNS server. As another example, the EASDF matches DNS messages based on first identification information and first associations, and determines the local DNS server address by matching DNS messages. The EASDF sends the DNS message to the local DNS server.

[0197] In a possible implementation, the EASDF may determine an EDNS client subnet option by matching a first association based on first identification information and matching the first association, or the EASDF may determine a local DNS server address by matching a first association based on first identification information and matching the first association.

[0198] According to the method provided in this application, the SMF transmits to the EASDF the correspondence between the identification information of the Domain Name System (DNS) processing information and the DNS processing information. In this way, the SMF can transmit differentiated EAS deployment information to the EASDF for different PDU sessions or UEs using different session or UE subscription information, and the EASDF can use different DNS processing information. This enables differentiated processing of DNS messages and improves the user's service experience. Furthermore, repetitive transmission of information can be avoided, signaling interactions can be reduced, and information processing efficiency can be improved.

[0199] FIG. 3 is a schematic flowchart of a communication method (300) according to the present application. The method of FIG. 3 includes the following steps.

[0200] Step 301: The UDR obtains at least one group of a second association, the second association being a correspondence between user equipment group (UE group) identifier (ID) information (the UE group ID may be an internal group ID or an external group ID) and deployment information of an edge application server.

[0201] In the present application, the deployment information of the EAS may include one or more of the following: information regarding an FQDN corresponding to a DNAI, information regarding the IP address of the EAS, and identification information of a DNS server.

[0202] In one example, the UDR can obtain an association between UE group ID #1 and the deployment information of the EAS, that is, a correspondence (which may also be understood as a “mapping relationship”) between “UE group ID #1 and the deployment information of the EAS”. For example, the deployment information of the EAS may be an FQDN range, an EAS IP address range, and a DNS server identifier corresponding to each DNAI of UE group ID #1. That is, the second association may be a correspondence between “UE group ID #1 and the FQDN range, the EAS IP address range, and the DNS server identifier”.

[0203] In a possible implementation, AF may initiate an AF request to the UDR to send one or more groups of associations between UE group ID #1 and the deployment information of the EAS to the UDR.

[0204] For example, the association between a UE group ID and EAS deployment information refers to the EAS deployment information corresponding to the service that can be accessed via EC by the UE corresponding to the UE group ID. For example, Service #A allows only UEs belonging to employees of Company #A to access it via EC. Assume that UE group ID #3 corresponds to a UE belonging to an employee of Company #A, and in the EAS deployment information corresponding to UE group ID #3, the FQDN range must include the FQDN corresponding to Service #A, and the EAS IP range must include the IP address of the EAS providing Service #A. If the UE group ID of the employee's UE is not UE group ID #3, the EAS deployment information corresponding to the employee's UE does not include the FQDN or EAS IP; that is, the employee's UE cannot access Service #A.

[0205] In other possible implementations, the correspondence between the UE group ID and the EAS deployment information may be pre-configured in the UDR, or some of the aforementioned correspondences may be pre-configured and some of the aforementioned correspondences provided by the AF. If all correspondences between the UE group ID and the EAS deployment information are pre-configured in the UDR, this step is omitted.

[0206] Step 302: SMF obtains at least one group of first associations, the first associations being correspondences between identification information of Domain Name System (DNS) processing information and DNS processing information.

[0207] In the present application, DNS processing information may include DNS detection information or DNS processing parameters.

[0208] In this embodiment, DNS processing information is used as an example of DNS detection information. That is, in this embodiment, the first association is explained using the correspondence between the identification information of Domain Name System (DNS) processing information and the DNS detection information as an example.

[0209] In this embodiment, the identification information of the DNS processing information may be one of a UE group ID, a rule ID, DNAI, DNN, S-NSSAI, or something similar. For convenience of explanation, this embodiment is described using only an example where the identification information of the DNS processing information is a rule ID. The rule ID mentioned in the following embodiments may be any of the aforementioned identification information of the DNS processing information. This is not limited to. The rule ID represents the corresponding rule.

[0210] This embodiment is described using an example in which the identification information of the DNS processing information is a rule ID, and the DNS detection information is a Fully Qualified Domain Name (FQDN) range and / or an Edge Application Server Internet Protocol address range, or the DNS detection information is an FQDN range and / or an EAS IP address range and information regarding processing actions for DNS messages. In this application, processing actions for DNS messages may include reporting the contents within the DNS message to the SMF, caching the DNS message, forwarding the DNS message (e.g., forwarding the DNS message to a UE or DNS server), etc. In this embodiment, the DNS message may be received by the EASDF from the UE or DNS server.

[0211] In this embodiment, the function of the first association is that the EASDF can subsequently determine a processing action for a DNS message based on the DNS message and the first association. Specifically, the EASDF can subsequently determine a rule ID based on the IP address corresponding to the UE to further determine the UE's FQDN range and / or EAS IP address range, and a processing action for the DNS message.

[0212] In the example, where the DNS detection information is a full-qualified domain name (FQDN) range and / or an EAS IP address range, the first association may be, for example, a correspondence between "Rule ID #1 and the FQDN range," a correspondence between "Rule ID #1 and the EAS IP address range," a correspondence between "Rule ID #1 and the FQDN range and the EAS IP address range," etc. Rule ID #2, Rule ID #3, ..., Rule ID #N (where N is an integer greater than 0) are similar to Rule ID #1. Further details are not described again.

[0213] In a possible implementation, the SMF may request the EAS deployment information from the UDR, and the UDR then transmits a second association, namely the association between the UE group ID and the EAS deployment information, to the SMF.

[0214] In another possible implementation, the SMF may subscribe to notifications regarding the deployment information of the EAS, and if the notification conditions are met, the UDR may send a notification message to the SMF and send to the SMF the association between the UE group ID and the EAS deployment information and / or the processing action for the DNS message.

[0215] Alternatively, when an event such as the expiration of the SMF's internal timer is triggered, the UDR can transmit the association between the UE group ID and the EAS deployment information to the SMF.

[0216] In another possible implementation of this stage, the UDR may additionally transmit the association between the UE identification information and the EAS placement information, and the association between the UE identification information and the UE group ID, to the SMF separately via two messages. In this implementation, the SMF must determine the association between the UE group ID and the EAS placement information based on the contents of the two messages.

[0217] In a possible implementation, the SMF configures the UE group ID locally or obtains the UE group ID from the join data.

[0218] In possible implementations, the SMF configures the rule ID locally or obtains the rule ID from the PCF, where the rule ID corresponds to the UE group ID.

[0219] In a possible implementation, the SMF determines the first association based on the acquired second association and the UE group ID.

[0220] In a possible implementation, the SMF determines the first association based on the acquired second association, UE group ID, and rule ID.

[0221] In the example, where the DNS detection information further includes information regarding DNS message processing operations (which can also be understood as "information regarding DNS message processing operations performed by the EASDF based on the rule ID"), the first association may be, for example, a correspondence between "reporting the contents of the FQDN range and DNS message to the SMF", a correspondence between "forwarding the FQDN range and DNS message", a correspondence between "forwarding the DNS message and the EAS IP address range", a correspondence between "caching the DNS message and the EAS IP address range", etc. Rule ID #2, Rule ID #3, ..., Rule ID #N (where N is an integer greater than 0) are similar to Rule ID #1. Further details are not described again.

[0222] Step 303: EASDF obtains at least one group of first associations used in the PDU sessions of multiple UEs.

[0223] In the present application, the EASDF may acquire at least one group of a first association used in a PDU session of a plurality of UEs, where "a plurality of UEs" may be understood as a plurality or all UEs to which the first association can be applied. A plurality of PDU sessions may be understood as a plurality or all PDU sessions to which the first association can be applied.

[0224] In a possible implementation, at least one group of first associations used in the PDU sessions of multiple UEs can be pre-configured in the EASDF.

[0225] In another possible implementation, the SMF may transmit at least one group of first associations used in the PDU sessions of multiple UEs to the EASDF.

[0226] In an example, the implementation of this step may be that the SMF sends a request to the EASDF to create a "node-level DNS context," the request including a first association. In other possible implementations, this step may alternatively be triggered when the SMF receives a request to establish a PDU session or in other ways. This is not limited to the present specification.

[0227] Specifically, the "node-level DNS context" may include "node-level DNS processing rules," and the "node-level DNS processing rules" may include at least one group of the first associations. Alternatively, the "node-level DNS context" may include at least one group of associations between a rule ID and a "node-level DNS processing rule," each "node-level DNS processing rule" including a group of DNS detection information. For example, the "node-level DNS context" includes an association between "rule ID #1 and node-level DNS processing rule #1," an association between "rule ID #2 and node-level DNS processing rule #2," an association between "rule ID #3 and node-level DNS processing rule #3," and an association between "rule ID #4 and node-level DNS processing rule #4." In the example, node-level DNS processing rule #1 includes a group of DNS detection information. For example, node-level DNS processing rule #1 includes a group of {FQDN ranges} or a group of {FQDN ranges, EAS IP ranges}. In other examples, Node-level DNS processing rule #1 further includes DNS message processing actions. For example, Node-level DNS processing rule #1 includes a group of {FQDN ranges, EAS IP ranges, and reporting the contents of the DNS message to the SMF}, or Node-level DNS processing rule #1 includes a group of {FQDN ranges, EAS IP ranges, and forwarding the DNS message}. Node-level DNS processing rules #2, Node-level DNS processing rule #3, etc., are similar to Node-level DNS processing rule #1. Further details are not described again.

[0228] In this application, information at this step may be transmitted using Neasdf_NodeLevelDNSHandlingRules_Create / Update or other messages. This is not limited to this application.

[0229] In this application, it should be noted that steps 301 through 303 are performed on a node basis. The following steps 304 through 314 are performed on a session basis.

[0230] Step 304: SMF transmits a first message to EASDF, the first message containing a first identifier.

[0231] For example, the first PDU session corresponds to message #1 (an example of the first message), and the first message includes a rule ID (an example of the first identifier).

[0232] In this embodiment, it should be noted that the first identifier may be DNS processing information corresponding to the first UE or the first PDU session.

[0233] In this embodiment, the first identifier may be a UE group ID, a rule ID, DNAI, DNN, S-NSSAI, or a similar one. For convenience of explanation, this embodiment is described using only an example where the first identifier is a rule ID. The rule ID mentioned in the following embodiments may be any of the aforementioned first identifiers. This is not limited to.

[0234] For example, SMF can send a request to EASDF to create a "session-based DNS context."

[0235] In a possible implementation, the request includes the IP address of UE #1, the DNN of the PDU session, and a "session-based DNS processing rule." The "session-based DNS processing rule" includes a rule ID. Here, the rule ID refers to an ID corresponding to the PDU session or the UE associated with the PDU session. For example, the rule ID associated with the first PDU session is rule ID #1.

[0236] In another possible implementation, the request includes UE #1's IP address, the DNN of the PDU session, "session-based DNS processing rules," and a rule ID. In this case, the rule ID is not included in the "session-based DNS processing rules" but is used as an information element in parallel with UE #1's IP address, the DNN of the PDU session, and the "session-based DNS processing rules." At this stage, the rule ID is transmitted to the EASDF by the SMF.

[0237] In this application, information of this step may be transmitted using a Neasdf_DNSContext_Create / Update Request or other messages. This is not limited to the above.

[0238] Optionally, indication information #1 (an example of the first indication information) may be additionally transmitted at this stage. The function of indication information #1 is to instruct the EASDF to process DNS messages based on "node-level DNS processing rules" after the EASDF receives a DNS query transmitted by UE #1 or a DNS response transmitted by a DNS server. Of course, the aforementioned logic may be configured in the EASDF when it is shipped from the factory or when the network is deployed. In this case, indication information #1 does not need to be transmitted.

[0239] Step 305: UE #1 (an example of the first UE) sends a DNS query (an example of a DNS message) to the EASDF, the DNS query including an FQDN. In response, the EASDF receives the DNS query.

[0240] Step 306: EASDF determines the processing action for DNS messages based on DNS queries, session-level DNS contexts, and node-level DNS contexts.

[0241] In a possible implementation, the EASDF can determine the processing action for a DNS message based on the UE group ID and the first association.

[0242] In other possible implementations, EASDF can match DNS messages based on UE group IDs and first associations and determine processing actions for DNS messages.

[0243] In the example, after receiving a DNS query transmitted by UE #1, the EASDF may perform the following steps: (1) The EASDF may determine a rule ID corresponding to a PDU session based on the IP address of UE #1 and / or the DNN of the PDU session and the session-level DNS context. For example, the EASDF may determine the source IP address of the DNS query transmitted by UE #1 as the IP address of UE #1. Since the session-level DNS context already includes the IP address of UE #1, the DNN of the PDU session, and the rule ID (assuming the rule ID corresponding to UE #1 is rule ID #1), the EASDF may determine that the rule ID of UE #1 is rule ID #1 based on the IP address of UE #1 and / or the DNN of the PDU session. (2) The EASDF may determine a processing action for an FQDN range and / or DNS message based on the rule ID (and, if, in step 304, the indication information #1) and the node-level DNS context. A node-level DNS context includes a first association, that is, one or more groups of associations between a rule ID and DNS detection information. Thus, the processing action for the FQDN range and the DNS message can be determined based on the rule ID. It may be understood that the EASDF matches the DNS message. (3) The EASDF can determine whether to perform a processing action for the DNS message based on the FQDN range, for example, whether to report the DNS message to the SMF. The scenario considered in this application is a scenario in which the EASDF successfully determines the FQDN range, that is, a scenario in which the EASDF successfully matches the FQDN of the DNS message transmitted by UE #1 with the FQDN range included in the first association transmitted by the SMF. In this case, the EASDF can transmit the DNS report message to the SMF.

[0244] If the EASDF fails to determine the FQDN range when performing step (2), the EASDF does not report to the SMF. Subsequent steps are separate from the EC scenario and are not discussed in this application.

[0245] Step 307: EASDF sends a DNS report message to SMF.

[0246] The EASDF performs a match between the FQDN included in the DNS query and the FQDN range included in the first association transmitted by the SMF. If the FQDN belongs to the FQDN range, the EASDF transmits a DNS report message to the SMF, which includes the FQDN corresponding to the DNS query.

[0247] Step 308: EASDF obtains the ECS option or local DNS server address from SMF.

[0248] As mentioned above, the ECS option is an extension item within the DNS message that indicates the location information of the UE.

[0249] When the EASDF sends a DNS report message to the SMF in step 307, the SMF may send the UE's ECS option or the address of the local DNS server to the EASDF.

[0250] Step 309: EASDF forwards the DNS message to the DNS server. The DNS server can receive the DNS message.

[0251] In a possible implementation, EASDF can add ECS options to a DNS query and forward the DNS message with the added ECS options to the DNS server.

[0252] In another possible implementation, the EASDF forwards the DNS message to the local DNS server obtained in step 308.

[0253] Step 310: The EASDF receives a DNS response from a DNS server, which includes the server's FQDN or IP address.

[0254] In possible implementations, the DNS response may include the EAS IP address.

[0255] Step 311: EASDF determines the processing action (i.e., DNS response) for a DNS message based on the DNS response, session-level DNS context, and node-level DNS context.

[0256] In a possible implementation, EASDF can determine the processing action for a DNS message based on a rule ID and a first association.

[0257] In other possible implementations, EASDF can match DNS messages based on rule IDs and first associations and determine processing actions for DNS messages.

[0258] In the example, after receiving a DNS response, the EASDF may sequentially perform the following steps: (1) The EASDF may determine a rule ID corresponding to UE #1 based on the IP address of UE #1 and / or the DNN of the PDU session and the session-level DNS context. For example, the EASDF may determine the destination IP address of the DNS response as the IP address of UE #1. Since the session-level DNS context includes the IP address of UE #1, the DNN of the PDU session, and a rule ID (assuming the rule ID corresponding to UE #1 is rule ID #1), the EASDF may determine that the rule ID of UE #1 is rule ID #1 based on the IP address of UE #1 and / or the DNN of the PDU session. (2) The EASDF may determine a processing action for the EAS IP range and / or DNS message based on the UE rule ID (and, if the indication information #1 is included in step 304, indication information #1) and the node-level DNS context. Since the node-level DNS context includes one or more groups of associations between a rule ID and an EAS IP range and / or a processing action for a DNS message, the EAS IP range and the processing action for a DNS message can be determined based on the rule ID. The EASDF may also be understood as matching a DNS message. (3) The EASDF determines whether to perform a processing action for a DNS message based on the EAS IP address range, for example, whether to cache the DNS message and report the DNS message to the SMF. The scenario considered in this application is a scenario in which the EASDF successfully determines the EAS IP range, that is, a scenario in which the EASDF successfully matches the server IP address of the DNS response with the EAS IP address included in the first association transmitted by the SMF.In this case, the EASDF can cache the DNS message and then send a DNS report message to the SMF, which includes the EAS IP address corresponding to the DNS response.

[0259] If the EASDF fails to determine the EAS IP scope when performing step (2), the EASDF does not report to the SMF. Subsequent steps are separate from the EC scenario and are not discussed in this application.

[0260] Step 312: The EASDF sends a DNS report message to the SMF, which includes the FQDN or EAS IP address corresponding to the DNS response.

[0261] After receiving a DNS response from a DNS server, the EASDF matches the FQDN or server IP address range included in the DNS response. If the FQDN or server IP address range included in the DNS response belongs to the FQDN range or EAS IP address range included in the first association, the EASDF transmits a DNS report message to the SMF, which includes the FQDN or EAS IP address corresponding to the DNS response.

[0262] Step 313: SMF inserts UL CL or BP.

[0263] Specifically, SMF can insert UL CL and local UPF based on the FQDN or EAS IP address included in the DNS report message.

[0264] Step 314: SMF instructs EASDF to forward the DNS response to UE #1.

[0265] In a possible implementation, the SMF can instruct the EASDF to forward the DNS response to UE #1.

[0266] Step 315: EASDF forwards the DNS response to UE #1 to complete local service discovery.

[0267] According to the method provided in this embodiment, since the SMF transmits DNS processing rules based on identification information of DNS processing information to the EASDF, the EASDF can use different DNS processing information for different PDU sessions or UEs. This enables differentiated processing of DNS messages and improves the user's service experience.

[0268] FIG. 4 is a schematic flowchart of a communication method (400) according to an embodiment of the present application. The method (400) includes the following steps.

[0269] For Step 401, refer to Step 301 of Method 300. Further details are not described again.

[0270] Step 402: SMF obtains at least one group of first associations, the first associations being correspondences between identification information of Domain Name System (DNS) processing information and DNS processing information.

[0271] Method 1:

[0272] In the present application, DNS processing information may include DNS detection information and DNS processing parameters.

[0273] The first association in this embodiment may be a correspondence between the identification information of the Domain Name System (DNS) processing information and the DNS detection information, i.e., "a correspondence between the identification information of the DNS processing information and the DNS detection information" (this is described as the first association a for convenience of distinction, and the first association a is specifically described in the method (300) and details are not described again here). Alternatively, the first association in this embodiment may be a correspondence between the identification information of the Domain Name System (DNS) processing information and the DNS processing parameter, i.e., a correspondence between the identification information of the DNS processing information and the "DNS processing parameter" (this is described as the first association b for convenience of distinction). It may also be understood that in this embodiment, the SMF can simultaneously acquire at least one group of the first association a and at least one group of the first association b. The following describes the first association b.

[0274] In this embodiment, the identification information of the DNS processing information may be one of a UE group ID, a rule ID, DNAI, DNN, S-NSSAI, or something similar. For convenience of explanation, this embodiment is described using only an example where the identification information of the DNS processing information is a rule ID. The rule ID mentioned in the following embodiments may be any of the identification information of the DNS processing information described above. This is not limited to this.

[0275] This embodiment is described using an example in which the identification information of the DNS processing information is a rule ID, and the DNS processing parameter is a correspondence between DNAI and an ECS option, or the DNS processing parameter is a correspondence between DNAI and an FQDN and an ECS option, or the DNS processing parameter is a correspondence between DNAI and a local DNS server address, or the DNS processing parameter is a correspondence between DNAI and an FQDN and a local DNS server address. In this embodiment, the first association b can be used by the EASDF to determine the ECS option and the local DNS server address using the identification information of the DNS processing information corresponding to the UE (e.g., a rule ID), and the EASDF does not need to send a DNS message for reporting to the SMF to request the ECS option or the local DNS server address. In the example, the first association b can be represented as shown in Table 1 and Table 2.

[0276] Identification information of DNS processing information DNS processing parameters Rule ID #1 DNAI #1 - (FQDN #1) - ECS Option #1 DNAI #2 - (FQDN #2) - ECS Option #2 ... Rule ID #2 DNAI #3 - (FQDN #3) - ECS Option #3 DNAI #4 - (FQDN #4) - ECS Option #4 ... ...

[0277] Identification information of DNS processing information DNS processing parameters Rule ID #1 DNAI #1 - (FQDN #1) - Local DNS server address #1 DNAI #2 - (FQDN #2) - Local DNS server address #2 ... Rule ID #2 DNAI #3 - (FQDN #3) - Local DNS server address #3 DNAI #4 - (FQDN #4) - Local DNS server address #4 ... ...

[0278] It should be noted that the DNAI and FQDN in the {relationship between DNAI, (FQDN), and ECS option} cannot be exactly the same as the DNAI and FQDN in another {relationship between DNAI, (FQDN), and ECS option}, and the DNAI and FQDN in the {relationship between DNAI, (FQDN), and local DNS server address} cannot be exactly the same as the DNAI and FQDN in another {relationship between DNAI, (FQDN), and local DNS server address}. For example, the DNAI and FQDN in the {relationship between DNAI #1, (FQDN) #1, and ECS option #1} cannot be exactly the same as the DNAI and FQDN in the {relationship between DNAI #2, (FQDN) #2, and ECS option #2}. That is, there is no correspondence such as {the association between DNAI #1, (FQDN) #1, and ECS Option #1} and {the association between DNAI #1, (FQDN) #1, and ECS Option #2}. In other words, DNAI+FQDN uniquely identifies the ECS Option. In this application, "(FQDN)" means that the FQDN is optional. It should be understood that Tables 1 and 2 are merely examples and are not limited thereto.

[0279] In a possible implementation, the SMF may request the EAS deployment information from the UDR, and the UDR then transmits a second association, namely the association between the UE group ID and the EAS deployment information, to the SMF.

[0280] In another possible implementation, the SMF may subscribe to notifications regarding the deployment information of the EAS, and when the notification condition is met, the UDR may send a notification message to the SMF and send to the SMF the association between the UE group ID and the processing action for the deployment information of the EAS and / or DNS messages.

[0281] Alternatively, when an event such as the expiration of the SMF's internal timer is triggered, the UDR can transmit the association between the UE group ID and the EAS deployment information to the SMF.

[0282] In another possible implementation of this stage, the UDR may additionally transmit the association between the UE identification information and the EAS placement information, and the association between the UE identification information and the UE group ID, to the SMF separately via two messages. In this implementation, the SMF must determine the association between the UE group ID and the EAS placement information based on the contents of the two messages.

[0283] In a possible implementation, the SMF configures the UE group ID locally or obtains the UE group ID from the join data.

[0284] In possible implementations, the SMF configures the rule ID locally or obtains the rule ID from the PCF, where the rule ID corresponds to the UE group ID.

[0285] In a possible implementation, the SMF determines the first association based on the acquired second association and the UE group ID.

[0286] In a possible implementation, the SMF determines the first association based on the acquired second association, UE group ID, and rule ID.

[0287] In a possible implementation, the SMF determines the first association based on the acquired second association, UE group ID, and UPF placement information. The UPF placement information is the correspondence between the UPF and the DNAI or the correspondence between the DNAI and the ECS option. The UPF placement information can be configured locally in the SMF.

[0288] In a possible implementation, the SMF determines the first association based on the acquired second association, UE group ID, rule ID, and UPF placement information.

[0289] Specifically, in a possible implementation, the SMF may determine an association between a rule ID and a list of {associations between DNAI and (FQDN) and ECS options}, or determine an association between a rule ID and a list of {associations between DNAI and (FQDN) and local DNS server addresses}. UPF placement information may be a correspondence between the UPF and DNAI, or UPF placement information may be a correspondence between the DNAI and ECS options. UPF placement information may be configured locally in the SMF or obtained by the UPF from a network repository function (NRF). In this case, the first association b is used by the EASDF to determine the ECS options based on the rule ID, or the first association b is used by the EASDF to determine the local DNS server address based on the rule ID.

[0290] Method 2:

[0291] Alternatively, the first association obtained by the SMF may be a correspondence between the "identification information of DNS processing information, DNS detection information, and DNS processing parameters." It should be noted that the relationship between the "identification information of DNS processing information, DNS detection information, and DNS processing parameters" is such that the rule ID can be mapped to the DNS detection information and DNS processing parameters.

[0292] In this case, the first association may be a correspondence between the identification information of the Domain Name System (DNS) processing information, the DNS detection information, and the DNS processing parameters. For example, in this case, the first association may be a correspondence between "rule ID, FQDN range and / or EAS IP range, and {a relationship between DNAI and (FQDN) and ECS options}", or a correspondence between "rule ID, FQDN range and / or EAS IP range, DNS message processing action, and {a relationship between DNAI, (FQDN) and ECS options}", or a correspondence between "rule ID, FQDN range and / or EAS IP range, and {a relationship between DNAI, (FQDN) and local DNS server address}", or a correspondence between "rule ID, FQDN range and / or EAS IP range, DNS message processing action, and {a relationship between DNAI, (FQDN) and local DNS server address}".

[0293] Step 403: EASDF obtains at least one group of first associations used in the PDU sessions of multiple UEs.

[0294] In the present application, the EASDF may acquire at least one group of a first association used in a PDU session of a plurality of UEs, where "a plurality of UEs" may be understood as a plurality of or all UEs to which the first association can be applied. A plurality of PDU sessions may be understood as a plurality of or all PDU sessions to which the first association can be applied.

[0295] In this embodiment, as described above, in a possible implementation, the EASDF can simultaneously obtain the first association a and the first association b.

[0296] In a possible implementation, at least one group of first associations used in the PDU sessions of multiple UEs can be pre-configured in the EASDF.

[0297] In another possible implementation, the SMF may transmit at least one group of first associations used in the PDU sessions of multiple UEs to the EASDF.

[0298] In an example, the implementation of this step may be that the SMF sends a request to the EASDF to create a "node-level DNS context," the request including a first association. In other possible implementations, this step may alternatively be triggered when the SMF receives a request to establish a PDU session or in other ways. This is not limited to the present specification.

[0299] Specifically, in a possible implementation, the "node-level DNS context" may include a "node-level DNS processing rule," and the "node-level DNS processing rule" may include at least one group of a first association, for example, at least one group of a first association a and at least one group of a first association b.

[0300] Alternatively, in a possible implementation, the "node-level DNS context" may include at least one group of associations between a rule ID and a "node-level DNS processing rule" and a list of {associations between DNAI, (FQDN), and ECS options} (i.e., DNS processing parameters). Additionally, in this case, it may be understood that the "node-level DNS context" may include a first association b, at least one group of associations between a rule ID and a "node-level DNS processing rule". Each node-level DNS processing rule includes a group of DNS detection information. In the example, "node-level DNS context" includes an association between "rule ID #1 and node-level DNS processing rule #1", and an association between "rule ID #2 and {DNAI 2, (FQDN #2) and ECS option #2}" (i.e., the first association b). For example, node-level DNS processing rule #1 includes a group of DNS detection information. For example, node-level DNS processing rule #1 includes a group of {FQDN ranges}, a group of {FQDN ranges, EAS IP ranges}, a group of {FQDN ranges, EAS IP ranges, processing actions for DNS messages}, etc.

[0301] Alternatively, in another possible implementation, the "node-level DNS context" may include at least one group of associations between a rule ID and a "node-level DNS processing rule." Each node-level DNS processing rule includes a group of DNS detection information and a group of DNS processing parameters. In the example, the "node-level DNS context" includes an association between "rule ID #1 and node-level DNS processing rule #1," where node-level DNS processing rule #1 includes a group of DNS detection information and a group of DNS processing parameters. For example, node-level DNS processing rule #1 includes a group of {FQDN ranges} and a list of {associations between DNAI, (FQDN), and ECS options}, a group of {FQDN ranges, EAS IP ranges} and a list of {associations between DNAI, (FQDN), and ECS options}, a group of {FQDN ranges, EAS IP ranges, actions to handle DNS messages} and a list of {associations between DNAI, (FQDN), and local DNS server addresses}, etc.

[0302] In this embodiment, the information of this step may be transmitted using Neasdf_NodeLevelDNSHandlingRules_Create / Update or other messages. This is not limited to the present specification.

[0303] It should be noted that in this application, steps 401 through 403 are performed on a node basis. The following steps 404 through 412 are performed on a session basis.

[0304] Step 404: SMF transmits a first message to EASDF, the first message containing a first identifier.

[0305] If the identification information of the DNS processing information is not a DNAI, the first message may further include a DNAI corresponding to the location of the UE associated with the PDU session.

[0306] For example, the first PDU session corresponds to message #1 (an example of the first message), and the first message includes a rule ID (an example of the first identifier).

[0307] It should be noted that the first identifier of the present application may be DNS processing information corresponding to the first UE or the first PDU session.

[0308] In this embodiment, the first identifier may be a UE group ID, a rule ID, DNAI, DNN, S-NSSAI, or a similar one. For convenience of explanation, this embodiment is described using only an example where the first identifier is a rule ID. The rule ID mentioned in the following embodiments may be any of the aforementioned first identifiers. This is not limited to.

[0309] For example, SMF can send a request to EASDF to create a "session-based DNS context."

[0310] In a possible implementation, the request may include the IP address of UE #1, the identifier of the DNN of the PDU session, and a "session-based DNS processing rule." The "session-based DNS processing rule" includes a rule ID and a DNAI. The rule ID is an ID corresponding to the PDU session or the UE associated with the PDU session. For example, the rule ID of the UE associated with the first session is rule ID #1. The DNAI is a DNAI corresponding to the location of the UE associated with the PDU session.

[0311] In another possible implementation, the request includes UE #1's IP address, the identifier of the PDU session's DNN, "session-based DNS processing rules," and a rule ID. In this case, the rule ID is not included in the "session-based DNS processing rules" but is used as an information element alongside UE #1's IP address, the PDU session's DNN, and the "session-based DNS processing rules." At this stage, the rule ID is transmitted to the EASDF by the SMF.

[0312] In this application, information of this step may be transmitted using a Neasdf_DNSContext_Create / Update Request or other messages. This is not limited to the above.

[0313] Optionally, at this stage, indication information #1 (an example of the first indication information) may be additionally transmitted. The function of indication information #1 is to instruct the EASDF to process DNS messages based on "node-level DNS processing rules" after the EASDF receives a DNS query transmitted by UE #1 or a DNS response transmitted by a DNS server. Of course, the aforementioned logic may be configured in the EASDF when it is shipped from the factory or when the network is deployed. In this case, indication information #1 does not need to be transmitted.

[0314] Step 405: UE #1 (an example of the first UE) sends a DNS query (an example of a DNS message) to the EASDF, the DNS query including an FQDN. In response, the EASDF receives the DNS query.

[0315] Step 406: Based on the DNS query, session-level DNS context, and node-level DNS context, EASDF determines the ECS option or local DNS server address of UE #1.

[0316] In a possible implementation, EASDF can determine UE #1's ECS option or local DNS server address based on the rule ID and the first association b.

[0317] In other possible implementations, EASDF can match DNS messages based on the rule ID and the first association b, and determine UE #1's ECS option or local DNS server address.

[0318] For example, after receiving a DNS query sent by UE #1, the EASDF determines an ECS option or a local DNS server address based on the DNS query, the session-level DNS context, and the node-level DNS context.

[0319] In the example, after receiving a DNS query sent by UE #1, the EASDF may perform the following steps: (1) The EASDF may determine a rule ID corresponding to a PDU session based on the IP address of UE #1 and / or the DNN of the PDU session and the session-level DNS context. For example, the EASDF may determine the source IP address of the DNS query sent by UE #1 as the IP address of UE #1. Since the session-level DNS context already includes the IP address of UE #1, the DNN of the PDU session, and the rule ID (assuming the rule ID corresponding to UE #1 is rule ID #1), the EASDF may determine that the rule ID of UE #1 is rule ID #1 based on the IP address of UE #1. (2) The EASDF may determine DNS processing parameters based on the rule ID (and, if the 304 step includes, the indication #1) and the node-level DNS context. For example, the EASDF may determine a list of {associations between DNAI, (FQDN), and ECS options} based on a rule ID, or a list of {associations between DNAI, (FQDN), and local DNS server addresses} based on a rule ID. Since the node-level DNS context includes one or more groups of first association b, i.e., associations between a rule ID and DNS processing parameters, the DNS processing parameters may be determined based on the rule ID. (3) The EASDF may determine an ECS option or a local DNS server address based on the DNS processing parameters and DNAI, or based on the DNS processing parameters, DNAI, and DNS query.For example, the ECS option or local DNS server address is determined based on the DNAI, the FQDN included in the DNS query, and a list of {relationships between the DNAI, (FQDN), and ECS option} or {relationships between the DNAI, (FQDN), and local DNS server address}.

[0320] The aforementioned steps (1), (2), and (3) may be understood as the EASDF performing a match on a DNS message. The scenario considered in this application is one in which the EASDF can successfully determine an ECS option or a local DNS server address, that is, a scenario in which the EASDF successfully matches the association between the DNS message transmitted by UE #1 and the "rule ID and DNS processing parameter" included in the first association transmitted by the SMF. This may also be understood as a scenario in which the EASDF can successfully determine the ECS option of UE #1 or the local DNS server address of UE #1.

[0321] When performing step (2), if the EASDF is unable to determine the DNS processing parameters, the EASDF may not report to the SMF. Subsequent steps are separate from the EC scenario and are not discussed in this application. Alternatively, the EASDF may report to the SMF based on existing technology and request an ECS option or a local DNS server address. Subsequent steps are performed entirely based on existing technology and are therefore not discussed in this application.

[0322] When performing step (3), if the EASDF fails to determine the ECS option or the local DNS server address, the EASDF may not report to the SMF. Subsequent steps are separate from the EC scenario and are not discussed in this application. Alternatively, the EASDF may report to the SMF based on existing technology and obtain the ECS option or the local DNS server address from the SMF. Since all subsequent steps are performed based on existing technology, they are not discussed in this application.

[0323] Step 407: EASDF sends a DNS message to a DNS server. The DNS server can receive the DNS message.

[0324] Specifically, after the EASDF determines an ECS option or a local DNS server address, in the case of an ECS option, the EASDF adds the determined ECS option to a DNS message (e.g., a DNS query) and forwards the DNS message with the added ECS option to the DNS server. If the EASDF determines a local DNS server address, the EASDF can send a DNS message to the local DNS server.

[0325] Step 408: EASDF receives a DNS response from a DNS server, which includes the server's FQDN or IP address.

[0326] In possible implementations, the DNS response may include the EAS IP address.

[0327] Step 409: EASDF determines the processing action (i.e., DNS response) for a DNS message based on the DNS response, session-level DNS context, and node-level DNS context.

[0328] In a possible implementation, EASDF can determine the processing action for a DNS message based on a rule ID and a first association a.

[0329] In other possible implementations, EASDF can match DNS messages based on a rule ID and a first association a, and determine a processing action for the DNS message.

[0330] For details, refer to step 311 of method (300). Details are not described again here.

[0331] Step 410: The EASDF sends a report message to the SMF, which includes an FQDN or EAS IP address corresponding to the DNS response.

[0332] After receiving a DNS response from a DNS server, the EASDF matches the FQDN or EAS IP address range included in the DNS response. If the FQDN or EAS IP address range included in the DNS response belongs to the FQDN range or EAS IP address range included in the first association, the EASDF transmits a DNS report message to the SMF, the DNS report message containing the FQDN or EAS IP address corresponding to the DNS response.

[0333] Step 411: SMF inserts UL CL or BP.

[0334] Specifically, SMF can insert UL CL and local UPF based on the FQDN or EAS IP address included in the DNS report message.

[0335] Step 412: SMF instructs EASDF to forward the DNS response to UE #1.

[0336] In a possible implementation, the SMF can instruct the EASDF to forward the DNS response to UE #1.

[0337] Step 413: EASDF forwards the DNS response to UE #1 to complete local service discovery.

[0338] According to the method provided in this embodiment, the SMF transmits DNS processing information identifying the message granularity of DNS processing information to the EASDF, so that the EASDF can use different DNS processing information for different PDU sessions or UEs. This enables differentiated processing of DNS messages and improves the user's service experience. Additionally, by determining ECS ​​options or local DNS server addresses based on node-level DNS context, the EASDF can prevent the repetitive transmission of ECS options, reduce signaling interactions, and improve information processing efficiency.

[0339] FIG. 5 is a schematic flowchart of a communication method (500) according to the present application. The method of FIG. 5 includes the following steps.

[0340] For step 501, refer to step 301 of method (300). Further details are not explained again.

[0341] Step 502: SMF obtains at least one group of first associations, the first associations being correspondences between identification information of Domain Name System (DNS) processing information and DNS processing information.

[0342] In the present application, DNS processing information may include DNS detection information or DNS processing parameters.

[0343] The first association of this embodiment may be an association between the identification information of the Domain Name System (DNS) processing information and the DNS processing information parameters.

[0344] This embodiment is described using an example where the identifying information of the DNS processing information is a Data Network Access Identifier (DNAI) and the DNS processing information parameter is an ECS option, or an example where the identifying information of the DNS processing information is a Data Network Access Identifier (DNAI) and the DNS processing information parameter is a correspondence between an FQDN and an ECS option, or an example where the identifying information of the DNS processing information is a Data Network Access Identifier (DNAI) and the DNS processing information parameter is a local DNS server, or an example where the identifying information of the DNS processing information is a Data Network Access Identifier (DNAI) and the DNS processing information parameter is a correspondence between an FQDN and a local DNS server.

[0345] In this embodiment, the function of the first association is that the EASDF can subsequently determine an ECS option or a local DNS server address based on a DNS message and the first association. Specifically, the EASDF can determine an ECS option or a local DNS server address using the DNAI (and the requested FQDN) corresponding to the UE, and there is no need to send a DNS message to the SMF to request an ECS option.

[0346] In a possible implementation, the SMF may request the EAS deployment information from the UDR, and the UDR then transmits a second association, namely the association between the UE group ID and the EAS deployment information, to the SMF.

[0347] In another possible implementation, the SMF may subscribe to notifications regarding the deployment information of the EAS, and when the notification conditions are met, the UDR may send a notification message to the SMF and send to the SMF the association between the UE group ID, the deployment information of the EAS, and / or the processing action for the DNS message.

[0348] Alternatively, when an event such as the expiration of the SMF's internal timer is triggered, the UDR can transmit the association between the UE group ID and the EAS deployment information to the SMF.

[0349] In another possible implementation of this stage, the UDR may additionally transmit the association between the UE identification information and the EAS placement information, and the association between the UE identification information and the UE group ID, to the SMF separately via two messages. In this implementation, the SMF must determine the association between the UE group ID and the EAS placement information based on the two messages.

[0350] Specifically, in a possible implementation, the SMF can determine the relationship between DNAI and the ECS option, or the relationship between DNAI and {FQDN and ECS option}, or the relationship between DNAI and the local DNS server address, or the relationship between DNAI and {FQDN and local DNS server address}, based on the second relationship (i.e., the relationship between the UE group ID and the EAS placement information) and the UPF placement information.

[0351] Step 503: EASDF obtains at least one group of first associations used in the PDU sessions of multiple UEs.

[0352] In the present application, the EASDF may acquire at least one group of a first association used in a PDU session of a plurality of UEs, where "a plurality of UEs" may be understood as a plurality or all UEs to which the first association can be applied. A plurality of PDU sessions may be understood as a plurality or all PDU sessions to which the first association can be applied.

[0353] In a possible implementation, at least one group of first associations used in the PDU sessions of multiple UEs can be pre-configured in the EASDF.

[0354] In another possible implementation, the SMF may transmit at least one group of first associations used in the PDU sessions of multiple UEs to the EASDF.

[0355] In an example, the implementation of this step may be that the SMF sends a request to the EASDF to create a "node-level DNS context," the request including a first association. In other possible implementations, this step may alternatively be triggered when the SMF receives a request to establish a PDU session or in other ways. This is not limited to the present specification.

[0356] Specifically, in a possible implementation, a "node-level DNS context" may include a "node-level DNS processing rule," and the "node-level DNS processing rule" may include at least one group of the first associations. For example, the "node-level DNS processing rule" may include a correspondence between a "DNAI and an ECS option," or the "node-level DNS processing rule" may include a correspondence between a "DNAI and {FQDN and an ECS option}," or the "node-level DNS processing rule" may include a correspondence between a "DNAI and a local DNS server address," or the "node-level DNS processing rule" may include a correspondence between a "DNAI and {FQDN and a local DNS server address}."

[0357] In another possible implementation, the "node-level DNS context" may include identification information of DNS processing information and associations between "node-level DNS processing rules," and the "node-level DNS processing rules" may include DNS processing parameters. For example, the "node-level DNS processing rules" may include ECS options, and the "node-level DNS context" may include one or more groups of correspondences between DNAI and ECS options. Alternatively, the "node-level DNS processing rules" may include correspondences between "FQDN and ECS options," and the "node-level DNS context" may include one or more groups of correspondences between DNAI, FQDN, and ECS options. Alternatively, the "node-level DNS processing rules" may include correspondences between local DNS server addresses, and the "node-level DNS context" may include one or more groups of correspondences between DNAI and local DNS server addresses. Alternatively, "node-level DNS processing rules" include correspondences between "FQDNs and local DNS server addresses," and "node-level DNS contexts" include one or more groups of correspondences between DNAIs, FQDNs, and local DNS server addresses.

[0358] In this embodiment, the information of this step may be transmitted using Neasdf_NodeLevelDNSHandlingRules_Create / Update or other messages. This is not limited to the present specification.

[0359] In this application, it should be noted that steps 501 through 503 are performed on a node basis. The following steps 504 through 508 are performed on a session basis.

[0360] Step 504: SMF transmits a first message to EASDF, the first message containing a first identifier.

[0361] In this embodiment, it should be noted that the first identifier may be DNS processing information corresponding to the first UE or the first PDU session.

[0362] For example, the first PDU session corresponds to message #1 (an example of the first message), and the first message includes DNAI (an example of the first identifier).

[0363] For example, SMF can send a request to EASDF to create a "session-based DNS context."

[0364] In a possible implementation, the request may include the IP address of UE #1, the DNN of the PDU session, and "session-based DNS processing rules." The "session-based DNS processing rules" include DNAIs. The DNAI is a DNAI corresponding to the location of the UE associated with the PDU session.

[0365] In another possible implementation, the request includes UE #1's IP address, the DNN of the PDU session, "session-based DNS processing rules," and DNAI. In this case, DNAI is not included in the "session-based DNS processing rules" but is used as an information element in parallel with UE #1's IP address, the DNN of the PDU session, and the "session-based DNS processing rules." At this stage, DNAI is transmitted to the EASDF by the SMF.

[0366] In this application, information of this step may be transmitted using a Neasdf_DNSContext_Create / Update Request or other messages. This is not limited to the above.

[0367] Optionally, at this stage, indication information #1 (an example of the first indication information) may be additionally transmitted. The function of indication information #1 is to instruct the EASDF to process DNS messages based on "node-level DNS processing rules" after the EASDF receives a DNS query transmitted by UE #1 or a DNS response transmitted by a DNS server. Of course, the aforementioned logic may be configured in the EASDF when the EASDF is shipped from the factory or when the network is deployed. In this case, indication information #1 does not need to be transmitted.

[0368] Step 505: UE #1 (an example of the first UE) sends a DNS query (an example of a DNS message) to the EASDF, the DNS query including an FQDN. In response, the EASDF receives the DNS query.

[0369] Step 506: Based on the DNS query, session-level DNS context, and node-level DNS context, EASDF determines the ECS option or local DNS server address of UE #1.

[0370] In a possible implementation, the EASDF can determine the ECS option or local DNS server address of UE #1 based on the DNAI and the first association.

[0371] In other possible implementations, the EASDF can match DNS messages based on DNAI and the first association and determine UE #1's ECS option or local DNS server address.

[0372] For example, after receiving a DNS query sent by UE #1, the EASDF determines an ECS option or a local DNS server address based on the DNS query, the session-level DNS context, and the node-level DNS context.

[0373] In the example, after receiving a DNS query transmitted by UE #1, the EASDF may perform the following steps: (1) The EASDF may determine the DNAI corresponding to UE #1 based on the IP address of UE #1 and / or the DNN of the PDU session and the session-level DNS context. For example, the EASDF may determine the source IP address of the DNS query transmitted by UE #1 as the IP address of UE #1. Since the session-level DNS context already contains the IP address of UE #1 and / or the DNN of the PDU session and the DNAI (assuming the UE DNAI corresponding to UE #1 is DNAI #1), the EASDF may determine that the DNAI of UE #1 is DNAI #1 based on the IP address of UE #1. (2) The EASDF may determine the ECS option or local DNS server address based on the DNAI (and if the identification information #1 is included in step 304, the identification information #1, or if the association includes an FQDN, the FQDN) and the node-level DNS context. Since the node-level DNS context includes one or more groups of first associations, namely the association between "DNAI, (FQDN), and ECS option" or the association between "DNAI, (FQDN), and local DNS server address", the ECS option or local DNS server address can be determined based on the DNAI (and the FQDN included in the DNS query if the association includes an FQDN).

[0374] The aforementioned steps (1) and (2) may be understood as the EASDF performing a matching on the first association to determine the ECS option or the local DNS server address. The scenario considered in this application is one in which the EASDF can successfully determine the ECS option or the local DNS server address, that is, a scenario in which the EASDF successfully matches the "association between DNAI, (FQDN), and ECS option" or the "association between DNAI, (FQDN), and the local DNS server address" included in the first association transmitted by the SMF with the DNS message transmitted by UE #1. This may also be understood as a scenario in which the EASDF can successfully determine the ECS option of UE #1 or the local DNS server address of UE #1. In this embodiment, "(FQDN)" means that the FQDN is optional.

[0375] When performing step (2), if the EASDF cannot determine the ECS option or the local DNS server address, the EASDF may not report to the SMF. Subsequent steps are separate from the EC scenario and are not discussed in this application. Alternatively, the EASDF may report to the SMF and request the ECS option based on existing technology. Since subsequent steps are performed entirely based on existing technology, they are not discussed in this application.

[0376] Step 507: EASDF sends a DNS message to a DNS server. The DNS server can receive the DNS message.

[0377] Specifically, after the EASDF determines an ECS option or a local DNS server address, in the case of an ECS option, the EASDF adds the determined ECS option to a DNS message (e.g., a DNS query) and forwards the DNS message with the added ECS option to the DNS server. If the EASDF determines a local DNS server address, the EASDF can send a DNS message to the local DNS server.

[0378] Step 508: EASDF receives a DNS response from a DNS server, which includes the server's FQDN or IP address.

[0379] In possible implementations, the DNS response may include the EAS IP address.

[0380] Subsequently, the EASDF may match the contents of the DNS response, determine whether to send a report message to the SMF, and cache the DNS message. If the EASDF sends the report message to the SMF, the SMF may insert a UL CL or BP. Subsequently, the SMF may instruct the EASDF to deliver the DNS response to UE #1, and the EASDF completes the local service discovery by delivering the DNS response to UE #1. Further details are not described in this application.

[0381] According to the method provided in this embodiment, the SMF transmits the association between the DNAI and the ECS option, or the association between the DNAI and the local DNS server address, to the EASDF at the node level, so that the EASDF can determine the ECS option or the local DNS server address based on the node-level DNS context. This prevents the repeated transmission of the ECS option, reduces signaling interactions, and improves information processing efficiency.

[0382] To clearly explain the technical solution in the embodiments of this application, it should be noted that terms such as "first" and "second" are used to distinguish identical or similar items having essentially the same function and purpose in the embodiments of this application. For example, the first information and the second information are used merely to distinguish different information and do not limit the order of the first information and the second information. Those skilled in the art will understand that terms such as "first" and "second" do not limit quantity or order of execution, and that terms such as "first" and "second" do not indicate a clear difference.

[0383] In the embodiments of the present application, “one or more of” or similar expressions refer to any combination of these terms, including any combination of a single term or any combination of plural terms. For example, one or more of a, b, or c may represent a; b; c; a and b; a and c; b and c; or a, b, and c, where a, b, and c may each be singular or plural.

[0384] It should be understood that in this application, “when” and “if” mean that the device performs the corresponding processing under objective circumstances and are not intended to limit time. These terms do not mean that the device must have a decision action during implementation, nor do they imply any other limitations.

[0385] Above, the communication method provided in the embodiment of the present application has been described in detail with reference to FIGS. 2 through 5. Next, the apparatus provided in the embodiment of the present application will be described with reference to FIGS. 6 and 7. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Accordingly, for details not specifically described, refer to the method embodiment described above. For brevity, details are not described again herein.

[0386] The above description has primarily focused on the interaction between nodes in relation to the solutions provided in the embodiments of this application. To implement the aforementioned functions, each node, e.g., SMF, EASDF, or UDR, may be understood to include a corresponding hardware structure and / or a corresponding software module for performing each function. Those skilled in the art should be able to recognize, in combination with the examples described in the embodiments disclosed herein, that the units and algorithm steps in this application may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementations should not be considered outside the scope of this application.

[0387] In the embodiments of the present application, a functional module of a terminal device or the terminal device itself may be obtained through partitioning based on the method example described above. For example, each functional module may be obtained through partitioning based on each function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiments of the present application, the partitioning into modules is merely an example and is only a logical functional partitioning. Other partitioning methods may be used in actual implementation. Below, an example in which each functional module is obtained through partitioning based on each corresponding function is used for illustrative purposes.

[0388] FIG. 6 is a schematic block diagram of a device (100) according to an embodiment of the present application. As shown in the drawing, the device (100) may include a transceiver unit (110) and a processing unit (120).

[0389] In a possible design, the device (100) may be an SMF in the above-described method embodiment or a chip configured to implement the function of the SMF in the above-described method embodiment. It should be understood that the device (100) may correspond to the SMF in the method (200), method (300), method (400), and method (500) according to the embodiment of the present application, and that the device (100) may perform steps corresponding to the SMF in the method (200), method (300), method (400), and method (500) in the embodiment of the present application. It should be understood that the specific process by which the units perform the above-described corresponding steps is described in detail in the above-described method embodiment. For brevity, details are not described again herein.

[0390] In a possible design, the device (100) may be an EASDF in the above-described method embodiment or a chip configured to implement the function of the EASDF in the above-described method embodiment. It should be understood that the device (100) may correspond to the EASDF in the method (200), method (300), method (400), and method (500) according to the embodiment of the present application, and that the device (100) may perform steps corresponding to the EASDF in the method (200), method (300), method (400), and method (500) in the embodiment of the present application. It should be understood that the specific process by which the units perform the above-described corresponding steps is described in detail in the above-described method embodiment. For brevity, details are not described again herein.

[0391] In a possible design, the device (100) may be a first network element in the above-described method embodiment, e.g., a UDR or a UDM, or a chip configured to implement the function of the first network element in the above-described method embodiment. It should be understood that the device (100) may correspond to the UDR in the method (300), method (400), and method (500) according to the embodiment of the present application, and that the device (100) may perform steps corresponding to the UDR in the method (200), method (300), method (400), and method (500) in the embodiment of the present application. It should be understood that the specific process by which the units perform the above-described corresponding steps is described in detail in the above-described method embodiment. For brevity, details are not described again herein.

[0392] FIG. 7 is a schematic block diagram of a device (200) according to an embodiment of the present application. As illustrated in the drawing, the device (200) includes at least one processor (220). The processor (220) is coupled to a memory and is configured to transmit and / or receive a signal by executing instructions stored in the memory. Optionally, the device (200) further includes a memory (230) configured to store instructions. Optionally, the device (200) further includes a transceiver (210), and the processor (220) controls the transceiver (210) to transmit and / or receive a signal.

[0393] It should be understood that the processor (220) and memory (230) can be integrated into a single processing unit. The processor (220) is configured to execute program code stored in memory (230) to implement the aforementioned functions. During a specific implementation, memory (230) may alternatively be integrated into the processor (220) or be independent of the processor (220).

[0394] Additionally, it should be understood that the transceiver (210) may include a receiver (or referred to as a receiver machine) and a transmitter (or referred to as a transmitter machine). The transceiver may further include an antenna. There may be one or more antennas. The transceiver (210) may be a communication interface or an interface circuit.

[0395] Specifically, the transceiver (210) of the device (200) can correspond to the transceiver unit (110) of the device (100), and the processor (220) of the device (200) can correspond to the processing unit (120) of the device (100).

[0396] It should be understood that the specific process by which the transceiver and the processor perform the corresponding steps described above is described in detail in the aforementioned method examples. For the sake of brevity, details are not described again herein.

[0397] In a possible design, the device (200) may be an SMF in the above-described method embodiment. In a possible design, the device (200) may be an EASDF in the above-described method embodiment. In a possible design, the device (200) may be a first network element in the above-described method embodiment, e.g., a UDR or a UDM.

[0398] In the implementation process, the steps of the method described above may be implemented using the hardware integrated logic circuits of a processor or using instructions in the form of software. The steps of the method disclosed with reference to the embodiments of this application may be executed and achieved directly by a hardware processor, or may be executed and achieved using a combination of hardware and software modules within the processor. The software modules may be located on a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory, and the processor reads information from the memory and completes the steps of the method described above in combination with the processor's hardware. To avoid repetition, details are not described again herein.

[0399] It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip and has signal processing capabilities. In the implementation process, the steps in the aforementioned method embodiments may be implemented using the hardware integrated logic circuit of the processor or using instructions in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. This may implement or perform the method, steps, and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any existing processor, etc. The steps of the method disclosed with reference to the embodiments of the present application may be executed and achieved directly by a hardware decoding processor, or may be executed and achieved using a combination of hardware and software modules of the decoding processor. The software module may be located on a mature storage medium in the relevant field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is located in memory, and the processor reads the information from the memory and combines it with the processor's hardware to complete the steps of the method described above.

[0400] It may be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of exemplary rather than limiting description, various forms of RAM, e.g., static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous SDRAM (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synch-link DRAM (SLDRAM), and direct ram-bus RAM (DR RAM) may be used. It should be noted that the memory of the system and method described herein includes, but is not limited to, these and other suitable types of memory.

[0401] According to the method provided in the embodiment of the present application, the present application further provides a computer program product. The computer program product stores computer program code. When the computer program code is executed on a computer, the computer is able to perform the method in any one of the embodiments of method (200), method (300), method (400), and method (500).

[0402] According to the method provided in the embodiment of the present application, the present application further provides a computer-readable medium. The computer-readable medium stores program code. When the program code is executed on a computer, the computer is able to perform the method in any one of the embodiments of method (200), method (300), method (400), and method (500).

[0403] According to the method provided in the embodiments of the present application, the present application further provides a system. The system includes the aforementioned device or apparatus.

[0404] All or part of the foregoing embodiments may be implemented using software, hardware, firmware, or any combination thereof. Where software is used to implement the foregoing embodiments, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product comprises one or more computer instructions. When computer instructions are loaded into and executed on a computer, a procedure or function according to an embodiment of the present application is created in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. Computer instructions may be stored on a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, fiber optic, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave). A computer-readable storage medium may be any available medium accessible by a computer, or a data storage device incorporating one or more available media, such as a server or data center. Available media may be magnetic media (e.g., floppy disks, hard disk drives, or magnetic tapes), optical media (e.g., digital video discs (DVDs)), semiconductor media (e.g., solid state discs (SSDs)), etc.

[0405] The network-side device and terminal device in the aforementioned device embodiment correspond to the network-side device or terminal device in the method embodiment. The corresponding module or unit performs the corresponding step. For example, a communication unit (transceiver) performs the receiving step or the transmitting step in the method embodiment, and steps other than the transmitting step and the receiving step may be performed by a processing unit (processor). Refer to the corresponding method embodiment for the function of a specific unit. There may be one or more processors.

[0406] Terms such as “component,” “module,” and “system” as used herein refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or running software. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated in the drawings, computing devices and applications running on computing devices may all be components. One or more components may reside within a process and / or execution thread, and components may be located on a single computer or distributed across two or more computers. Additionally, these components may be executed using various computer-readable media that store various data structures. For example, components may communicate using local and / or remote processes based on signals having, for example, one or more data packets (e.g., data from two components interacting with other components on a network such as the Internet, which interacts with other systems using signals from a local system, a distributed system, and / or the Internet).

[0407] Those skilled in the art will recognize that, in combination with the examples described in the embodiments disclosed herein, the unit and algorithm steps may be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether a function is performed by hardware or by software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementations should not be construed as being outside the scope of this application.

[0408] For the sake of convenience and brevity, it will be clearly understood by those skilled in the art that the detailed operation processes of the aforementioned systems, devices, and units refer to the corresponding processes of the aforementioned method embodiments. Details are not described again herein.

[0409] It should be understood that in the various embodiments provided in this application, the disclosed systems, devices, and methods may be implemented in different ways. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical functional division and may be different during actual implementation. For example, multiple units or components may be combined or integrated into different systems, or some features may be ignored or not performed. Additionally, the mutual coupling, direct coupling, or communication connections shown or discussed may be implemented using some interfaces. Indirect coupling or communication connections between devices or units may be implemented electronically, mechanically, or in other forms.

[0410] The units described as separate parts may or may not be physically separated, and the parts indicated as units may or may not be physical units, and may be located in one location or distributed across multiple network units. Some or all of the units may be selected based on actual requirements to achieve the purpose of the solution of the embodiment.

[0411] In addition, the functional units in the embodiments of the present application may be integrated into a single processing unit, and each unit may exist physically alone or two or more units may be integrated into a single unit.

[0412] Where a function is implemented in the form of a software function unit and sold or used as an independent product, said function may be stored on a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or parts or portions of the technical solution that contribute to the prior art, may be implemented in the form of a software product. The software product is stored on a storage medium and includes various instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0413] The foregoing description is merely a specific embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modification or substitution readily discernible by those skilled in the art within the technical scope disclosed in the present application falls within the scope of protection of the present application. Accordingly, the scope of protection of the present application is subject to the scope of protection of the claims.

Claims

Claim 1 A communication method comprising: a step of obtaining at least one group of a first association by means of a session management function, wherein the first association is a correspondence between identification information of domain name system (DNS) processing information and said DNS processing information; a step of transmitting the at least one group of the first association used in a protocol data unit (PDU) session of a plurality of terminal devices to an edge application server search function by means of the session management function; and a step of transmitting a first message corresponding to the first PDU session to the edge application server search function by means of the session management function, wherein the first message includes first identification information, the first identification information is identification information of DNS processing information corresponding to the first PDU session, and the first identification information is used to determine said DNS processing information corresponding to the first PDU session based on the first identification information and the first association. Claim 2 A communication method according to claim 1, wherein the identification information of the DNS processing information identifies the DNS processing information, the DNS processing information includes DNS detection information and / or DNS processing parameters, the DNS detection information includes a fully qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range, and the DNS processing parameters include an EDNS client subnet option or a local DNS server address. Claim 3 In paragraph 2, the above DNS detection information is a communication method used to determine a processing operation for the DNS message by matching the DNS message. Claim 4 A communication method in which, in paragraph 2, the identification information of the DNS processing information is a data network access identifier (DNAI). Claim 5 A communication method according to paragraph 4, wherein the DNS processing information is the DNS processing parameter, the DNS processing parameter is the EDNS client subnet option, the first identification information is the first DNAI, the first identification information is used to determine the EDNS client subnet option by matching the first association, and the first DNAI is the DNAI associated with the location of the terminal device. Claim 6 A communication method according to claim 4, wherein the DNS processing information is the DNS processing parameter, the DNS processing parameter is the local DNS server address, the first identification information is the first DNAI, the first identification information is used to determine the local DNS server address by matching the first association, and the first DNAI is the DNAI associated with the location of the terminal device. Claim 7 A communication method comprising: receiving at least one group of a first association used in a protocol data unit (PDU) session of a plurality of terminal devices from a session management function by an edge application server discovery function, wherein the first association is a correspondence between identification information of Domain Name System (DNS) processing information and the DNS processing information; receiving a first message corresponding to the first PDU session from the session management function by the edge application server discovery function, wherein the first message includes first identification information, and the first identification information is identification information of DNS processing information corresponding to the first PDU session; and determining the DNS processing information corresponding to the first PDU session based on the first identification information and the first association by the edge application server discovery function. Claim 8 A communication method according to claim 7, wherein the identification information of the DNS processing information identifies the DNS processing information, the DNS processing information includes DNS detection information and / or DNS processing parameters, the DNS detection information includes a fully qualified domain name (FQDN) range and / or an edge application server Internet Protocol address range, and the DNS processing parameters include an EDNS client subnet option or a local DNS server address. Claim 9 In claim 8, the above DNS detection information is a communication method used to determine a processing action for the DNS message by matching the DNS message. Claim 10 In claim 8, the DNS processing information is the DNS detection information, and the method further comprises the steps of: receiving a DNS message by the edge application server search function; matching the DNS message based on the first identification information and the first association relationship by the edge application server search function; and determining a processing operation for the DNS message by the edge application server search function. Claim 11 A communication method according to paragraph 8, wherein the identification information of the DNS processing information is a data network access identifier (DNAI). Claim 12 A communication method according to claim 11, wherein the DNS processing information is the DNS processing parameter, the DNS processing parameter is the EDNS client subnet option, the first identification information is the first DNAI, the first identification information is used to determine the EDNS client subnet option by matching the first association, and the first DNAI is the DNAI associated with the location of the terminal device. Claim 13 A communication method according to claim 11, wherein the DNS processing information is the DNS processing parameter, the DNS processing parameter is the local DNS server address, the first identification information is the first DNAI, the first identification information is used to determine the local DNS server address by matching the first association, and the first DNAI is the DNAI associated with the location of the terminal device. Claim 14 A communication method according to claim 11, wherein the DNS processing information is the DNS processing parameter, the DNS processing parameter is the EDNS client subnet option, the first identification information is the first DNAI, and the method further comprises the steps of receiving a DNS message from a terminal device by the edge application server search function, matching the first association based on the first identification information by the edge application server search function, determining the EDNS client subnet option by matching the first association by the edge application server search function, and adding the determined EDNS client subnet option to the DNS message and transmitting the DNS message to a DNS server by the edge application server search function, wherein the first DNAI is a DNAI associated with the location of the terminal device. Claim 15 A communication method according to claim 11, wherein the DNS processing information is the DNS processing parameter, the DNS processing parameter is the local DNS server address, the first identification information is the first DNAI, and the method further comprises the steps of receiving a DNS message from a terminal device by the edge application server search function, matching the first association based on the first identification information by the edge application server search function, determining the local DNS server address by matching the first association by the edge application server search function, and transmitting the DNS message to a local DNS server by the edge application server search function, wherein the first DNAI is a DNAI associated with the location of the terminal device. Claim 16 A computer-readable storage medium for storing instructions, wherein when the instructions are executed by a communication device, the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 15 is implemented. Claim 17 A communication method comprising: a step of obtaining at least one group of a first association by means of a session management function, wherein the first association is a correspondence between identification information of Domain Name System (DNS) processing information and said DNS processing information; a step of transmitting the at least one group of the first association used in a Protocol Data Unit (PDU) session of a plurality of terminal devices to an edge application server search function by means of the session management function; a step of receiving the at least one group of the first association used in a Protocol Data Unit (PDU) session of the plurality of terminal devices from the session management function by means of the edge application server search function; a step of transmitting a first message corresponding to the first PDU session to the edge application server search function by means of the session management function, wherein the first message includes first identification information, and the first identification information is identification information of said DNS processing information corresponding to the first PDU; a step of receiving the first message corresponding to the first PDU session from the session management function by means of the edge application server search function; and the first identification information by means of the edge application server search function A communication method comprising the step of determining the DNS processing information corresponding to the first PDU session based on the first association. Claim 18 A communication device comprising one or more functional units, wherein the one or more functional units are configured to enable the communication device to perform a communication method according to any one of claims 1 to 6. Claim 19 A communication device comprising one or more functional units, wherein the one or more functional units are configured to enable the communication device to perform a communication method according to any one of claims 7 to 15. Claim 20 A communication system comprising: a communication device including one or more functional units - wherein the one or more functional units are configured to enable the communication device to perform a communication method according to any one of claims 1 through 6 - and a communication device including one or more functional units - wherein the one or more functional units are configured to enable the communication device to perform a communication method according to any one of claims 7 through 15 -. Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete Claim 33 delete Claim 34 delete Claim 35 delete Claim 36 delete Claim 37 delete Claim 38 delete Claim 39 delete Claim 40 delete Claim 41 delete Claim 42 delete Claim 43 delete Claim 44 delete

Images