Application addressing method, apparatus and system

Abstract

The present application relates to the technical field of communications. Disclosed are an application addressing method, apparatus and system, which aim to solve the problems of the discovery of an edge application and a user plane change in an edge network depending on and affecting a session management function (SMF) network element, realize the quick launch of the edge application, and simplify a change in the edge network. The method comprises: a first function network element acquiring edge application server (EAS) deployment information, and sending first information to an edge application server discovery function (EASDF) network element on the basis of the EAS deployment information; subsequently, the EASDF network element receiving a first request message from a terminal, and in response to the first request message, the EASDF network element determining an EAS address of a first application server on the basis of the first information; and furthermore, the EASDF network element sending the EAS address to the terminal, and correspondingly, the terminal receiving the EAS address. The solution of the present application can be widely applied in the technical fields of communications, and in fields such as artificial intelligence, the Internet of Vehicles and the Internet of Smart Home.

Description

An application addressing method, apparatus and system

[0001] This application claims priority to Chinese Patent Application No. 202311418695.0, filed on October 26, 2023, entitled “An Application Addressing Method, Apparatus and System”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to an application addressing method, apparatus, and system. Background Technology

[0003] In mobile edge computing scenarios, the terminal sends a Domain Name System (DNS) query request to the Edge Application Server Discovery Function (EASDF) network element. Based on the DNS query request sent by the terminal and the addressing policy provided by the Session Management Function (SMF) network element to the EASDF network element, the EASDF network element determines the Edge Application Server (EAS) address and sends the EAS address to the terminal. The addressing policy provided by the SMF network element includes application identification information related to the edge application and deployment information of the edge network user plane. Based on the received EAS address, the terminal determines the edge application server that provides the edge application to the terminal.

[0004] However, SMF network elements provide addressing strategies for EASDF network elements, requiring SMF network elements to be aware of the deployment information of edge applications and edge network user planes. This leads to problems in the discovery of edge application servers and changes to the edge network user plane, which depend on and affect SMF network elements.

[0005] Summary of the Invention

[0006] This application provides an application addressing method, apparatus, and system to address the issues of edge application server discovery and changes in the edge network user plane depending on and affecting SMF network elements.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] Firstly, this application provides an application addressing method, which can be executed by an edge application server discovery function (EASDF) network element and functional modules or chips within the EASDF network element. The following description uses an EASDF network element as the executing entity. The application addressing method includes: the EASDF network element obtaining first information from a first functional network element; the EASDF network element receiving a first request message from a terminal; in response to the first request message, the EASDF network element determining the edge application server (EAS) address of the first application service based on the first information; and the EASDF network element sending the EAS address to the terminal. Wherein, the first functional network element is used to select the application service and / or user plane network element; the first information is used to indicate the relevant information of the application service obtained by the first functional network element; and the first request message is used to discover the first application service.

[0009] Based on the method described in the first aspect, the EASDF network element can determine the EAS address based on the first information obtained from the first functional network element, so that the EASDF network element no longer needs to determine the EAS address according to the addressing strategy provided by the session management function (SMF) network element. This solves the problem that the EASDF network element depends on the deployment information of the SMF network element to determine the EAS address, that is, it solves the problem that the discovery of edge application servers and the changes in the edge network user plane depend on and affect the SMF network element.

[0010] In one possible design, the EASDF network element determines the EAS address based on first information, including: the EASDF network element determining second information based on the first information, including extended domain name system client subnet (ECS) information and / or DNS server address information; the EASDF network element sending a second request message to the DNS server based on the second information to request the DNS server to select an edge application server to provide the first application service; and the EASDF network element receiving the edge application service EAS address from the DNS server. Optionally, if the second information includes ECS information, the second request message may also include ECS information.

[0011] Based on this possible design, the EASDF network element can determine the ECS information and / or DNS server address information based on the first information obtained from the first functional network element, and then obtain the EAS address from the DNS server based on the ECS information and / or DNS server address information, no longer relying on the deployment information of the SMF network element to obtain the EAS address from the DNS server.

[0012] In one possible design, the EASDF network element determines the second information based on the first information by: the EASDF network element selecting a target first functional network element from the first functional network elements based on the first information; the EASDF network element sending a third request message to the target first functional network element, including the identification information of the first application service and / or the location information of the terminal; and the EASDF network element receiving the second information from the target first functional network element.

[0013] Based on this possible design, EASDF network elements can select a suitable target first functional network element and obtain second information from the selected target first functional network element, providing a feasible solution for EASDF network elements to determine second information; at the same time, it solves the problem that the acquisition of second information no longer depends on the deployment information of SMF network elements.

[0014] In one possible design, the first request message includes the identification information of the first application service; the EASDF network element selects a target first functional network element from the first functional network elements based on the first information, including: the EASDF network element selects the first functional network element that has obtained the relevant information of the first application service as the target first functional network element according to the identification information of the first application service and the first information, in other words, the target first functional network element is the first functional network element that has obtained the relevant information of the first application service.

[0015] Based on this possible design, the first functional network element that has (or can be understood as managing) relevant information of the first application service can be used as the target first functional network element. The first functional network element that manages the first application service can be directly located, which can improve the accuracy and efficiency of the second information obtained from the target first functional network element. This avoids signaling interaction with the first functional network element that has not obtained relevant information of the first application service to obtain the second information, which would lead to signaling interaction failure and waste of resources.

[0016] In one possible design, the first information includes the identification information of the application service obtained by the first functional network element and the address information of the DNS server. The application service managed by the first functional network element includes the first application service. The EASDF network element determines the second information based on the first information, including: the EASDF network element determines the address information of the DNS server according to the location information of the terminal; or, the EASDF network element selects the first functional network element that obtains relevant information of the first application service from the first functional network elements as the target first functional network element according to the identification information of the first application service, and uses the address information of the DNS server obtained by the target first functional network element as the address information of the DNS server.

[0017] Based on this possible design, EASDF network elements can determine the address information of the DNS server using either of the two methods, which improves the flexibility and diversity of determining the address information of the DNS server.

[0018] In one possible design, the first information also includes the address range of the user plane function network element corresponding to the application service obtained by the first function network element; the method further includes: the EASDF network element determines the target first function network element from the first function network elements according to the EAS address and the address range of the user plane function network element in the first information, and the EASDF network element sends first indication information to the SMF network element for determining the target first function network element.

[0019] Based on this possible design, the EASDF network element can identify the target first functional network element and indicate the target first functional network element to the SMF network element, so that the SMF network element can obtain the tunnel identifier of the user plane network element from the target first functional network element.

[0020] In one possible design, the EASDF network element determines the EAS address based on the first information, including: the EASDF network element determines the target first functional network element from the first functional network elements based on the first information; subsequently, the EASDF network element sends an EAS query request to the target first functional network element; further, the EASDF network element receives the EAS address from the target first functional network element.

[0021] Based on this possible design, the EAS address can be determined by the target first functional network element, and the EAS address can be obtained by the EAS DF network element from the target first functional network element, instead of the EAS DF network element obtaining the EAS address from the DNS server through signaling interaction, thereby reducing the processing complexity of the EAS DF network element and improving the efficiency of obtaining the EAS address.

[0022] In one possible design, the EASDF network element determines a target first functional network element from the first functional network elements based on first information, including: the first information includes the identification information of the application service obtained by the first functional network element; the EASDF network element determines the target first functional network element from the first functional network elements according to the identification information of the first application service and the correspondence between the identification information of the application service and the first functional network element; or; the first information includes the service area of ​​the first functional network element; the EASDF network element determines the target first functional network element from the first functional network elements according to the location information of the terminal and the correspondence between the service area of ​​the first functional network element and the first functional network element.

[0023] Based on this possible design, EASDF network elements can determine the target first functional network element through a variety of different methods, which improves the flexibility and diversity of EASDF network elements in determining the target first functional network element.

[0024] Secondly, this application provides an application addressing method, which can be executed by a first functional network element and functional modules or chips within the first functional network element. Understandably, the first functional network element can be an independent user plane network element, or it can be a function configured within an EASDF network element or an SMF network element, or it can be deployed together with EASDF / SMF. The following description uses the first functional network element as the executing entity. The application addressing method includes: the first functional network element obtaining EAS deployment information; then, the first functional network element sending first information to the EASDF network element based on the EAS deployment information. Wherein, the first functional network element is used to select an application service and / or a user plane network element; the EAS deployment information is used to determine the EAS of the application service; and the first information is used to indicate the relevant information of the application service obtained by the first functional network element.

[0025] Based on the method described in the second aspect, the first functional network element provides application service-related information to the EASDF network element, resolving the issue of the EASDF network element relying on the deployment information of the SMF network element to determine the EAS address. Simultaneously, when application or user plane deployment changes, the first functional network element updates the relevant application or user plane deployment information, providing the EASDF network element with accurate application or user plane deployment information. This resolves the issue of changes in application and / or user plane deployment information significantly impacting the SMF network element.

[0026] In one possible design, the first functional network element receives a third request message sent by the EASDF network element; based on the third request message, the first functional network element determines second information; and the first functional network element sends the second information to the EASDF network element. The third request message includes the identification information of the first application service and / or the location information of the terminal; the second information includes extended Domain Name System (DNS) client subnet (ECS) information or the address information of the DNS server; the DNS server is used to select the edge application server.

[0027] Based on this possible design, the first functional network element determines the second information and sends the determined second information to the EASDF network element. This facilitates the subsequent determination of the EAS address by the EASDF network element and also solves the problem that the acquisition of the second information no longer depends on the deployment information of the SMF network element.

[0028] In one possible design, the first functional network element determines the second information based on the third request information, including: the first functional network element selecting the address information of the DNS server managed by the first functional network element as the address information of the DNS server. The third request message includes the identification information of the first application service and / or the location information of the terminal, and the second information includes the address information of the DNS server.

[0029] Based on this possible design, the first functional network element determines the address information of the DNS server according to the address information of the DNS server it manages, which increases the flexibility and diversity of determining the address information of the DNS server.

[0030] In one possible design, the first functional network element determines the EAS address based on the EAS query request sent by the EASDF network element; subsequently, the first functional network element sends the EAS address to the EASDF network element. The EAS query request includes the identification information of the first application service, or a user's DNS query request message.

[0031] Based on this possible design, the first functional network element determines the EAS address and sends the EAS address to the EASDF network element. This eliminates the need for the EASDF network element to obtain the EAS address from the DNS server through signaling interaction, thus improving the efficiency of the EASDF network element in obtaining the EAS address.

[0032] In one possible design, the first functional network element determines the EAS address based on the EAS query request, including: the first functional network element determines the EAS address based on the application information recorded locally and the identification information of the first application service in the EAS query request; or: the first functional network element sends a DNS query request message in the EAS query request to the local DNS server according to the local addressing policy, and further obtains the EAS address from the local DNS server.

[0033] Based on this possible design, the first functional network element can determine the EAS address through a variety of different methods, which improves the flexibility and diversity of the first functional network element in determining the EAS address.

[0034] In one possible design, the first functional network element receives a session creation / modification request sent by the Session Management Function (SMF) network element; then, the first functional network element sends the tunnel identifier of the user plane network element determined by the first functional network element to the SMF network element.

[0035] Based on this possible design, the first functional network element determines the tunnel identifier of the user plane network element, avoiding the process of the SMF network element determining the L-PSA network element. Simultaneously, the first functional network element sends the determined tunnel identifier of the user plane network element to the SMF network element, facilitating the SMF network element to send the L-PSA network element's tunnel identifier to the radio access device or other user plane network elements when creating a user plane forwarding path for the terminal session.

[0036] In one possible design, the first functional network element receives the peer tunnel identifier of the user plane network element sent by the Session Management Function (SMF) network element; subsequently, the first functional network element sends the peer tunnel identifier to the user plane network element.

[0037] Based on this possible design, the SMF network element and the first functional network element create a user plane session path for the terminal device, which facilitates the subsequent forwarding of data packets from the terminal device by the user plane.

[0038] In one possible design, the first information includes at least one of the following: the FQDN of the application service obtained by the first functional network element, the identifier of the first functional network element, the address information of the DNS server obtained by the first functional network element, the address range of the user plane functional network element corresponding to the application service obtained by the first functional network element, the service area of ​​the application service obtained by the first functional network element, the data network access identifier (DNAI) obtained by the first functional network element, the DNAI prefix obtained by the first functional network element, and the service area of ​​the first functional network element.

[0039] Based on this possible design, the first functional network element determines the relevant information of the application service, which facilitates the subsequent determination of the second information by the first functional network element and / or the EASDF network element, and / or the first functional network element and / or the EASDF network element determines the EAS address.

[0040] Thirdly, this application provides an application addressing method, which can be executed by an SMF network element and functional modules or chips within the SMF network element. The following description uses an SMF network element as the executing entity. The application addressing method includes: the SMF network element receiving first indication information sent by an EASDF network element; subsequently, the SMF network element determining a target first functional network element based on the first indication information; further, the SMF network element sending a tunnel identifier request for an L-PSA network element to the target first functional network element; correspondingly, the SMF network element receiving the tunnel identifier of the L-PSA network element sent by the target first functional network element. The first indication information is used to determine the target first functional network element and includes at least one of the following: a DNAI or DNAI prefix obtained by the target first functional network element, a first functional network element identifier corresponding to the target first functional network element, and an Edge Application Service (EAS) address.

[0041] Based on the method described in the third aspect, the SMF network element determines the target first functional network element according to the first indication information sent by the EASDF network element. Based on the determined target first functional network element, the SMF network element and the target first functional network element establish a user plane session path for the terminal device. Furthermore, the SMF network element can determine the target first functional network element in different ways based on different information included in the first indication information, increasing the flexibility and versatility of the SMF network element in determining the target first functional network element.

[0042] In one possible design, the first indication information includes the DNAI or DNAI prefix obtained by the target first functional network element. The method includes: the SMF network element sending the first indication information to the network function NRF network element; subsequently, the SMF network element receiving the target first functional network element determined by the NRF network element.

[0043] Based on this possible design, the SMF network element determines the target first functional network element when the first indication information includes the DNAI or DNAI prefix obtained by the target first functional network element. This facilitates the subsequent creation of a user plane session path for the terminal device by the SMF network element and the target first functional network element.

[0044] In one possible design, the first indication information includes the identifier of the first functional network element corresponding to the target first functional network element, and the method includes: the SMF network element determines the target first functional network element based on the identifier of the first functional network element.

[0045] Based on this possible design, the SMF network element, when the first indication information includes the identifier of the first functional network element corresponding to the target first functional network element, achieves the purpose of determining the target first functional network element. This facilitates the subsequent creation of a user plane session path for the terminal device by the SMF network element and the target first functional network element.

[0046] In one possible design, the first indication information includes the EAS address, and the method includes: the SMF network element determining the target first functional network element based on the UPF IP Range obtained by the locally configured first functional network element.

[0047] Based on this possible design, the SMF network element, when the first indication information includes the EAS address, aims to determine the target first functional network element. This facilitates the subsequent creation of a user plane session path for the terminal device by the SMF network element and the target first functional network element.

[0048] In one possible design, the method also includes the SMF network element sending the terminal's location information to the EASDF network element.

[0049] Based on this possible design, the SMF network element sends the terminal's location information to the EASDF network element, and correspondingly, the EASDF network element receives the terminal's location information. This facilitates the subsequent use of the terminal's location information by the EASDF network element and / or the first functional network element to determine at least one of the following: the EAS address, the second information, and the target first functional network element.

[0050] Fourthly, this application provides a communication device, which can be an EASDF network element, a chip or system-on-a-chip within an EASDF network element, or a functional module within an EASDF network element for implementing the methods of the first aspect or any possible design of the first aspect. This communication device can implement the functions performed by the first communication device in the first aspect or any possible design of the first aspect, and these functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit, a processing unit, and a transmitting unit.

[0051] Processing unit, used to obtain first information from first functional network element;

[0052] The receiving unit is configured to receive first request information from the terminal; the first request information is used to request a first application service.

[0053] The processing unit is also used to respond to the first request message, and the EASDF network element determines the EAS address based on the first information;

[0054] The sending unit is used to send the EAS address to the terminal.

[0055] Specifically, the relevant descriptions of the first functional network element, the first information, the first request information, the first application service, and the EAS address can be referred to the first aspect or any possible design of the first aspect. At the same time, the execution actions of each unit of the communication device can be referred to the first aspect or any possible design of the first aspect, and will not be repeated here.

[0056] Fifthly, this application provides a communication device, which can be an EASDF network element or a chip or system-on-a-chip within an EASDF network element. This communication device can implement the functions performed by the EASDF network element in the first aspect or any possible design of the first aspect, and these functions can be implemented in hardware. In one possible design, the communication device includes a processor and a communication interface. The processor and communication interface are used to support the communication device in executing the application addressing method in the first aspect or any possible design of the first aspect. In yet another possible design, the communication device may further include a memory for storing necessary computer execution instructions and data. When the communication device is running, the processor executes the computer execution instructions stored in the memory to cause the communication device to execute the application addressing method as described in the first aspect or any possible design of the first aspect.

[0057] Sixthly, this application provides a communication device, which can be a first functional network element or a chip or system-on-a-chip within the first functional network element, or a functional module within the first functional network element for implementing the second aspect or any possible design of the second aspect. This communication device can implement the functions performed by the first functional network element in the aforementioned second aspect or possible design of the second aspect, and these functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a processing unit and a transmitting unit.

[0058] Processing unit, used to obtain first information from first functional network element;

[0059] The sending unit is used to send the EAS address to the terminal.

[0060] Specifically, the relevant descriptions of the first information and the EAS address can be referred to in the second aspect or any possible design of the second aspect. At the same time, the execution actions of each unit of the communication device can be referred to in the second aspect or any possible design of the second aspect, and will not be repeated here.

[0061] In a seventh aspect, this application provides a communication device, which can be a first functional network element or a chip or system-on-a-chip within the first functional network element. The communication device can implement the functions performed by the first functional network element in the second aspect or any possible design of the second aspect, and these functions can be implemented in hardware. In one possible design, the communication device includes a processor and a communication interface. The processor and communication interface are used to support the communication device in executing the application addressing method in the second aspect or any possible design of the second aspect. In yet another possible design, the communication device may further include a memory for storing necessary computer execution instructions and data. When the communication device is running, the processor executes the computer execution instructions stored in the memory to cause the communication device to execute the application addressing method as described in the first aspect or any possible design of the first aspect.

[0062] Eighthly, this application provides a communication device, which can be an SMF network element, a chip or system-on-a-chip within an SMF network element, or a functional module within an SMF network element for implementing the methods of the third aspect or any possible design of the third aspect. This communication device can implement the functions performed by the SMF network element in the aforementioned third aspect or possible design of the third aspect, and these functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include a receiving unit, a processing unit, and a transmitting unit.

[0063] The receiving unit is used to receive the first indication information sent by the EASDF network element, and to receive the tunnel identifier of the L-PSA network element sent by the target first functional network element;

[0064] The processing unit is used to determine the target first functional network element based on the first indication information;

[0065] The sending unit is used to send a tunnel identifier request of the L-PSA network element to the target first functional network element.

[0066] Specifically, the descriptions of the first instruction information and the target first functional network element can be referred to in the third aspect or any possible design of the third aspect. At the same time, the execution actions of each unit of the communication device can be referred to in the third aspect or any possible design of the third aspect, and will not be repeated here.

[0067] Ninthly, this application provides a communication device, which can be an SMF network element or a chip or system-on-a-chip within an SMF network element. The communication device can implement the functions performed by the SMF network element in the third aspect or any possible design of the third aspect, and these functions can be implemented in hardware. In one possible design, the communication device includes a processor and a communication interface. The processor and communication interface are used to support the communication device in executing the application addressing method in the third aspect or any possible design of the third aspect. In yet another possible design, the communication device may further include a memory for storing necessary computer execution instructions and data. When the communication device is running, the processor executes the computer execution instructions stored in the memory to cause the communication device to execute the application addressing method as described in the third aspect or any possible design of the third aspect.

[0068] In a tenth aspect, this application provides a communication system that includes the communication device provided in the fourth or fifth aspect, or the communication system includes the communication device provided in the sixth or seventh aspect, or the communication system includes the communication device provided in the eighth or ninth aspect.

[0069] In one aspect, this application provides a computer-readable storage medium that stores computer instructions that, when executed on a computer, cause the computer to perform the application addressing method of the first aspect or any possible design of the first aspect; or cause the computer to perform the application addressing method of the second aspect or any possible design of the second aspect; or cause the computer to perform the application addressing method of the third aspect or any possible design of the third aspect.

[0070] In a twelfth aspect, this application provides a computer program product comprising computer instructions that, when executed on a computer, cause the computer to perform the application addressing method of the first aspect or any possible design of the first aspect; or cause the computer to perform the application addressing method of the second aspect or any possible design of the second aspect; or cause the computer to perform the application addressing method of the third aspect or any possible design of the third aspect.

[0071] The technical effects of any design approach in aspects four and five are similar to those in aspect one or any possible design of aspect one, and will not be repeated here. The technical effects of any design approach in aspects six and seven are similar to those in aspect two, and will not be repeated here. The technical effects of any design approach in aspects eight and nine are similar to those in aspect three, and will not be repeated here.

[0072] The technical effects of any design method in aspects 10 to 12 can be referred to the technical effects of any possible design in aspect 1 or any possible design in aspect 1, or the technical effects of any design method in aspects 10 to 12 can be referred to the technical effects of any possible design in aspect 2 or any possible design in aspect 2, or the technical effects of any design method in aspects 10 to 12 can be referred to the technical effects of any possible design in aspect 3 or any possible design in aspect 3, and will not be repeated here. Attached Figure Description

[0073] Figure 1 is a schematic diagram of the process of accessing a website through a content delivery network;

[0074] Figure 2 is a schematic diagram of a 5G network architecture using CDN technology;

[0075] Figure 3 is a schematic diagram of the 5G network architecture;

[0076] Figure 4 is a schematic diagram of a communication system provided in an embodiment of this application;

[0077] Figure 5 is a schematic diagram of an application addressing process provided in an embodiment of this application;

[0078] Figure 6 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0079] Figure 7 is a schematic flowchart of an application addressing method provided in an embodiment of this application;

[0080] Figure 8 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0081] Figure 9 is a schematic flowchart of an application addressing method provided in an embodiment of this application;

[0082] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0083] Figure 11 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0084] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0085] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0086] Before introducing the embodiments of this application, some technical terms involved in the embodiments of this application will be explained. It should be noted that the following explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by the embodiments of this application.

[0087] A Content Delivery Network (CDN) is a computer network system that connects to each other over the Internet. It adds a new layer of network architecture to the existing network, distributing website content to the network "edge" closest to the user, allowing the user to obtain the content they need from nearby locations, thus alleviating Internet network congestion and improving the response speed of website access.

[0088] Specifically, a CDN caches website content at the network edge (the place closest to the user's network access). When a user accesses website content, the scheduling system routes or directs the user's request to the cache server that is closest to the user's network access or has the best access performance. The cache server then provides the content service to the user. Compared to directly accessing the origin server, this method shortens the network distance between the user and the content, thereby improving the response speed of the website.

[0089] For example, Figure 1 shows a schematic diagram of the process of accessing a website through a CDN. As shown in Figure 1, the process includes steps (1) to (8):

[0090] (1) When the terminal determines to initiate a Domain Name System (DNS) resolution request for a certain image resource (e.g., image1.jpg) under a certain domain name, the terminal initiates a DNS resolution request to the local DNS server.

[0091] The local DNS server can include DNS, a distributed database that maps domain names to internet protocol (IP) addresses, enabling users to access the internet more conveniently without having to remember the IP address strings that machines can directly read. Each IP address has a domain name, which consists of one or more strings separated by periods.

[0092] A DNS resolution request is used to obtain the IP address corresponding to a domain name. The DNS resolution request includes the domain name to be resolved. It should be understood that DNS resolution refers to the process of converting a domain name into an IP address.

[0093] (2) When the local DNS server receives a DNS resolution request, the local DNS server performs a recursive DNS query.

[0094] When a local DNS server receives a DNS resolution request from a client, it first checks its cache for the IP address mapped to the domain name. If the IP address is present in the cache, the local DNS server sends it directly to the client. If the IP address is not present in the cache, the local DNS server performs a recursive DNS lookup.

[0095] A DNS recursive lookup refers to a query request sent to other DNS servers when the local DNS server's cache does not contain the IP address mapped to a given domain name. The query request is used to determine the IP address corresponding to the domain name and also to obtain the address of the application DNS server managing that domain name.

[0096] (3) The application DNS server returns the IP address, including: when the local DNS server obtains the address of the application DNS server that manages the domain name through DNS recursive query, the local DNS server forwards the query request to the application DNS server, and the application DNS server returns the IP address mapped to the domain name to the local DNS server after receiving the query request.

[0097] (4) The local DNS server returns the IP address, including: the local DNS server receives the IP address mapped to the domain name sent by the application's DNS server, and returns the IP address mapped to the domain name to the terminal.

[0098] (5) The terminal initiates a request by receiving the IP address mapped to the domain name returned by the local DNS server and sending an access request to the application server indicated by that IP address. The access request is used to obtain the aforementioned image resource (e.g., image 1.jpg).

[0099] (6) The application server forwarding the request includes: the application server indicated by the IP address receiving the access request. If the application server indicated by the IP address does not cache the above image resources, then the application server forwards the access request to the business origin server. The business origin server refers to the server that manages the above image resources.

[0100] (7) The application server acquires and caches data, including: the business origin server receives the access request forwarded by the application server and sends the aforementioned image resources to the application server. The application server receives and caches the aforementioned image resources sent by the business origin server.

[0101] (8) The terminal acquires data by sending the aforementioned image resources to the terminal via the application server. Correspondingly, the terminal receives the aforementioned image resources.

[0102] Currently, CDN technology can be applied to the 5G network of the 3rd generation partnership project (3GPP). Figure 2 shows the 5G network architecture using CDN technology. As shown in Figure 2, the network architecture can include: terminals, radio access network (RAN) equipment, 5G core (5GC), edge application server discovery function (EASDF) network elements, protocol data unit session anchor user plane function (PSA-UPF) network elements, uplink classifier (ULCL) network elements, local protocol data unit session anchor (L-PSA) network elements, DNS server, and application server.

[0103] The terminal initiates a PDU session by sending a DNS query request. The DNS query request is used to obtain edge application services. The creation of a Protocol Data Unit (PDU) session establishes a data transmission channel between the terminal and the data network.

[0104] Among them, wireless access network equipment provides network access services for terminals.

[0105] Among them, the EASDF network element is a new network element defined by 3GPP for discovering edge application server (EAS), which is used to process DNS messages according to the instructions of the session management function (SMF) network element.

[0106] Specifically, EAS can also be called an edge application server, which refers to edge application services or edge application servers that provide services to applications.

[0107] The PSA-UPF network element serves as the PDU session anchor point for terminals accessing the central data network, and is also a user plane function network element that assigns user plane IP addresses to terminals. Terminals can use this network element to transmit data with the central data network.

[0108] The L-PSA network element serves as the PDU session anchor point when a terminal accesses the local network, and is determined by the SMF network element management. The terminal can use this network element to transmit data with the local network.

[0109] Among them, the ULCL network element is an uplink offloading function network element defined by 3GPP for data offloading of 5G user plane. It is used to offload uplink service data to the local or central data network, and aggregate downlink data packets from PSA UPF and L-PSA, and encapsulate them into the general packet radio service tunneling (GPRS) tunnel of the N3 interface and pass them to the RAN, and then to the terminal.

[0110] In Figure 2, 5GC can refer to the core network in the 5G architecture. For example, as shown in Figure 3, which is a schematic diagram of a 5G architecture, it can include UE, RAN, UPF, DN, and 5GC, where 5GC can be the following network elements:

[0111] Access and mobility management function (AMF): Primarily responsible for registration management, connection management, access management, mobility management, and various functions related to security, access management, and authorization.

[0112] Session management function (SMF): Used to create, update and delete PDU sessions, maintain PDU session context, and be responsible for tunnel maintenance, IP address allocation and management, user plane function selection and other functions.

[0113] Policy control function (PCF): Provides policy rules for control plane functions, used to generate and manage user, session, and QoS processing policies.

[0114] Application function (AF): A network element that provides various business services, can interact with the core network through network open functions, and can interact with the policy management framework for policy management.

[0115] Network exposure function (NEF): It can provide a framework, authentication and interface related to network capability exposure, and pass information between 5G system network functions and other network functions.

[0116] Authentication server function (AUSF): Used to implement access authentication for both 3GPP and non-3GPP systems.

[0117] The network slice selection function (NSSF) can determine the network slice instances that the UE is allowed to access based on the UE's slice selection assistance information, subscription information, etc.

[0118] Network Exposure Function Repository Function (NRF): This is a new function that provides registration and discovery capabilities, enabling network functions to discover each other and communicate through an application programming interface (API).

[0119] Unified data management (UDM): Responsible for the management of user identifiers, subscription data, authentication data, and the registration management of user service network elements.

[0120] Specifically, the communication interfaces between various functional network elements in the 5G network architecture are shown in Figure 3. User equipment (UAE) accesses the 5G network through the RAN equipment, communicating with the AMF through the N1 interface (N1); the RAN equipment communicates with the AMF through the N2 interface (N2); the RAN equipment communicates with the UPF through the N3 interface (N3); the SMF communicates with the UPF through the N4 interface (N4); and the UPF accesses the data network through the N6 interface (N6). Furthermore, the control plane functions shown in Figure 3, such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, or AF, interact using service-oriented interfaces. For example, the service interface provided externally by AUSF is Nausf; by AMF, Namf; by SMF, Nsmf; by NSSF, Nnssf; by NEF, Nnef; by NRF, Nnrf; by PCF, Npcf; by UDM, Nudm; and by AF, Naf. Related functional and interface descriptions can be found in the 5G system architecture diagram in the 23501 standard, and will not be elaborated upon here.

[0121] In the 5G network architecture shown in Figure 2, the terminal can discover the EAS that provides the application in the following way, the specific process of which is as follows:

[0122] (1) The terminal sends a DNS query request to the PSA-UPF network element through the wireless access network device; the PSA-UPF network element then forwards the DNS query request to the EASDF network element.

[0123] In this context, the EASDF network element is the EASDF network element selected by the SMF network element based on the PDU session initiated by the terminal. Furthermore, the SMF network element sends the selected EASDF network element address to the terminal, enabling the terminal to send DNS query requests to the EASDF network element, and allowing the SMF network element to send the DNS processing policy provided by the SMF network element to the EASDF network element through the PDU session.

[0124] (2) After receiving the DNS query request sent by PSA-UPF, the EASDF network element adds EDNS client subnet (ECS) information to the DNS query request to express the terminal location, based on the application identification information related to the application provided by the SMF network element and the DNS processing policy corresponding to the application identification information. After modifying the source address of the DNS query request (the source address is sent by the UE) to the address of EASDF, the DNS query request is sent to the DNS server.

[0125] (3) After receiving the DNS query request sent by the EASDF network element, the DNS server selects an EAS that is close to the terminal's location based on the ECS information in the received DNS query request, and sends a DNS response to the EASDF network element. The DNS response includes the EAS address selected by the DNS server.

[0126] (4) After receiving the DNS response sent by the DNS server, the EAS address in the DNS response is forwarded to the SMF network element.

[0127] (5) Based on the received EAS address, the SMF network element selects a user plane network element closer to the EAS as the ULCL network element and a user plane network element closer to the EAS as the L-PSA network element. The L-PSA network element and the ULCL network element can be the same network element. Furthermore, the SMF network element creates a tunnel between the RAN and the ULCL, and a tunnel between the ULCL and the PSA-UPF. At the same time, it creates a traffic offloading strategy for the ULCL.

[0128] (6) The EASDF network element sends the message with the destination address of the EAS address to the terminal through the ULCL network element selected by the SMF network element.

[0129] In the above process, the EASDF network element determines the EAS address based on the DNS query request sent by the terminal, the application identification information related to the application provided by the SMF network element to the EASDF network element, and the DNS processing policy, and then sends the EAS address to the terminal. The application identification information related to the application and the DNS processing policy can be collectively referred to as the addressing policy.

[0130] Therefore, the process of EASDF network elements determining EAS addresses relies on control plane network elements (SMF network elements). When deployment information for application and / or user planes changes, SMF network elements must also be aware of these changes so that EASDF network elements can determine accurate server addresses. However, currently, the user plane of the 5G core network can be deployed in provinces, cities, or down to the network edge to carry mobile edge computing (MEC) services, depending on traffic volume and demand. The control plane, on the other hand, is deployed in several major regions across the country, with each region carrying the control planes of several provinces, achieving centralized deployment. Based on this centralized deployment of the 5GC core network control plane, when deployment information for application and / or user planes changes, 5GC control plane network elements (e.g., SMF network elements) must make corresponding adjustments to the deployment information of all managed application and / or user planes, significantly impacting the 5GC control plane network elements.

[0131] Therefore, to address the issue that the process of determining the EAS address by the EASDF network element relies on the control plane network element (SMF network element), and that changes in application and / or user plane deployment information significantly impact the SMF network element, this application adds a first functional network element. This first functional network element can interact with the EASDF network element to perform the application addressing process, avoiding reliance on the SMF network element. Specifically, the application addressing method provided in this application includes: the first functional network element obtains EAS deployment information and, based on the EAS deployment information, sends first information to the EASDF network element. Subsequently, the EASDF network element receives a first request message from the terminal, responds to the first request message, and determines the EAS address of the first application service based on the first information. Further, the EASDF network element sends the EAS address to the terminal, and the terminal receives the EAS address accordingly.

[0132] Optionally, when the SMF network element needs to insert a ULCL for a terminal's session, or when the SMF network element needs to create or modify a session, the method further includes: the EASDF network element sending first indication information to the SMF network element. Accordingly, the SMF network element receives the first indication information and, based on the first indication information, determines the target first functional network element. Subsequently, the SMF network element sends an L-PSA tunnel identifier request to the target first functional network element. Accordingly, the target first functional network element determines the tunnel identifier of the L-PSA network element and sends the L-PSA network element's tunnel identifier to the SMF network element.

[0133] The application addressing method provided in the embodiments of this application will be described below with reference to the accompanying drawings. It should be understood that, for ease of description, in this application, the session management function is replaced by an SMF network element, the access and mobility management function is replaced by an AMF network element, the network function storage function is replaced by an NRF network element, the network open function is replaced by a NEF network element, the unified data management function is replaced by a UDM network element, and the edge application service discovery function is replaced by an EASDF network element.

[0134] The technical solutions of this application embodiment can be used in various communication systems, including satellite communication systems, 3GPP communication systems (e.g., Long Term Evolution, LTE), 5G mobile communication systems, New Radio (NR) systems, Beyond 5G (B5G) mobile communication systems, 6G mobile communication systems, and NR V2X systems. They can also be applied to LTE and 5G hybrid networking systems, device-to-device (D2D) communication systems, machine-to-machine (M2M) communication systems, Internet of Things (IoT) systems, and other next-generation communication systems. They can also be non-3GPP communication systems, without limitation. The following description uses the communication system shown in Figure 4 as an example to illustrate the application addressing method provided in this application embodiment.

[0135] Figure 4 is a schematic diagram of a communication system provided in this application. As shown in Figure 4, the communication system 40 includes a terminal, an EASDF network element, a first functional network element, an SMF network element, a UPF network element, and a wireless access network device. Optionally, it includes an NRF network element and an AMF network element. It is understood that the devices or network elements in the communication system 40 can communicate directly with each other or communicate through forwarding by other devices. This application does not specifically limit this aspect.

[0136] It is understood that Figure 4 above is merely a schematic diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application. Those skilled in the art should understand that in specific implementations, the communication system 40 may include fewer devices or network elements than those shown in Figure 4, or the communication system 40 may include other devices or other network elements. The number of devices or network elements in the communication system 40 can be determined according to specific needs and is not limited. The devices and network elements in the system shown in Figure 4 are described below.

[0137] Wireless access network equipment is mainly used to implement functions such as terminal resource scheduling, wireless resource management, and wireless access control. Specifically, the access network equipment can be any node among small base stations, wireless access points, transmission receive points (TRPs), transmission points (TPs), and some other access nodes. In the embodiments of this application, the apparatus for implementing the functions of the access network equipment can be the access network equipment itself, or it can be any apparatus that supports the access network equipment in implementing these functions, such as a chip system (e.g., a chip, or a processing system composed of multiple chips) or a modem. The following describes the method provided in the embodiments of this application, taking the access network equipment as an example.

[0138] The terminal can be terminal equipment, user equipment (UE), mobile station (MS), or mobile terminal (MT), etc. Specifically, the terminal can be a mobile phone, tablet computer, or computer with wireless transceiver capabilities. It can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a smart home, or an in-vehicle terminal, etc. In the embodiments of this application, the device used to implement the terminal's functions can be the terminal itself or a device capable of supporting the terminal in implementing those functions, such as a chip system (e.g., a chip, or a processing system composed of multiple chips) or a modem. The following describes the communication method provided in the embodiments of this application, taking the terminal as an example of the device used to implement the terminal's functions.

[0139] The first functional network element, also known as the service routing function (SRF) network element, is used to select application services and / or user plane network elements and data forwarding paths for the terminal. The first functional network element can obtain relevant information about the application service, or it can be understood as managing the application service, such as managing the mapping relationship between application services and user plane network elements. It can be understood that the first functional network element can be an independent user plane network element, or its corresponding function can be configured in an EASDF or SMF network element, or deployed together with EASDF / SMF. Optionally, one or more first functional network elements can be deployed in the system shown in Figure 4, and different first functional network elements obtain different information about the application services.

[0140] The descriptions of EASDF, SMF, UPF, and NRF network elements can be found in the 5G network architecture shown in Figure 2 above, and will not be repeated here.

[0141] Optionally, each network element or device in Figure 4 (e.g., session management network element, access network device, terminal, user plane network element, edge application service discovery function network element, network function storage function network element or first function network element, etc.) can also be referred to as a communication device. It can be a general-purpose device or a special-purpose device. This application embodiment does not specifically limit it in this way.

[0142] Optionally, the functions of each network element or device in Figure 4 of this application can be implemented by one device, multiple devices working together, or one or more functional modules within a single device. This application does not specifically limit these functions. It is understood that the aforementioned functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0143] The addressing method provided in this application embodiment is described below with reference to the communication system shown in Figure 4. The actions, terms, etc. involved in the following embodiments can be referred to each other. The message names or parameter names in the messages that are exchanged between devices in each embodiment are just examples, and other names can also be used in specific implementations. For example, "corresponding" in the following embodiments can be replaced by "associating" etc.

[0144] Figure 5 is a flowchart of the application addressing method provided in an embodiment of this application. As shown in Figure 5, it may include:

[0145] S501: The first functional network element obtains EAS deployment information and, based on the EAS deployment information, sends first information to the EASDF network element. Correspondingly, the EASDF network element obtains the first information from the first functional network element.

[0146] The first functional network element is used to select application services and / or user plane network elements. The first functional network element can be the first functional network element shown in Figure 4 (or referred to as the SRF network element / SRF). EAS deployment information is used to determine EAS address information. EAS deployment information includes the application address of the EAS, the address information of the DNS server used for EAS addressing, and other information. EAS deployment information can also be referred to as EAS information.

[0147] The application address of EAS, also known as the EAS address, is used to indicate the address information of EAS.

[0148] The address information of the DNS server used for EAS addressing is used to indicate the DNS server that supports EAS addressing.

[0149] For example, if the EAS deployment information includes the application address of the EAS, the first functional network element can directly determine the EAS address from the EAS deployment information. If the EAS deployment information includes the address information of the DNS server used for EAS addressing, the first functional network element can obtain the EAS address through the DNS server that supports EAS addressing.

[0150] For example, the first functional network element can obtain EAS deployment information from the L-PSA network element. Alternatively, the first functional network element can directly obtain the EAS deployment information. Specifically, this method can be referred to step S701 in Figure 7 below.

[0151] The first information is used to indicate relevant information about the application service obtained by the first functional network element. The first information may include, but is not limited to, the fully qualified domain name (FQDN) of the application service obtained by the first functional network element, the first functional network element ID, the address information of the DNS server obtained by the first functional network element, the UPF IP range of the user plane functional network element corresponding to the application service obtained by the first functional network element, the service area of ​​the application service obtained by the first functional network element, the data network access identifier (DNAI) obtained by the first functional network element, and the DNAI prefix obtained by the first functional network element. Specifically, the parameter descriptions in the first information can be found in the relevant descriptions in step S702 of Figure 7 below.

[0152] For example, the first functional network element sending first information to the EASDF network element based on EAS deployment information may include: the first functional network element sending first information consistent with the EAS deployment information to the EASDF network element after obtaining the EAS deployment information.

[0153] For example, when the first functional network element obtains the DNS server address information used for the current EAS addressing, it sends the DNS server address information obtained by the first functional network element to the EASDF network element via a data packet.

[0154] S502: The terminal sends a first request message to the EASDF network element. Correspondingly, the EASDF network element receives the first request message from the terminal.

[0155] The first request message is used to request a first application service. The first request message may include identification information of the first application service and identification information of the terminal. The identification information of the first application service is used to identify the first application service, and the identification information of the terminal is used to identify or indicate the terminal. The first application service may also be referred to as a first application, and may include, but is not limited to, services corresponding to various applications (apps) deployed on the terminal, and may also include computing resources, storage resources, memory resources, network resources, etc. In this application, the first request message requesting the first application service can also be understood as the first request message requesting an edge application server that provides the first application service.

[0156] In this application, the type of the first request message can be categorized based on the method by which the terminal discovers the edge application service (also referred to as the application service). The method of terminal discovery of the application service can include two types: application service discovery based on DNS (or DNS method), or application service discovery based on non-DNS (or non-DNS method). The application service discovered via CDN (or CDN method) is a typical example of an application service discovery based on DNS. Optionally, when the terminal discovers the application service via DNS, the first request message is of the first type, and may further include a DNS query request. The DNS query request can be used to request the edge application service address of the application, and may include, but is not limited to, the FQDN corresponding to the application. When the terminal discovers the edge application service via non-DNS, the first request message is of the second type, and may also include the anycast address of the application.

[0157] Understandably, this application does not limit the type of the first request message sent by the terminal.

[0158] For example, the terminal can send a first request message to the EASDF network element in the following manner: the terminal sends the first request message to the PSA-UPF network element through the RAN, and the PSA-UPF network element receives the first request message and forwards the first request message to the EASDF network element.

[0159] S503: The EASDF network element responds to the first request message sent by the terminal and determines the EAS address based on the first information.

[0160] The EAS address indicates the edge application service of the application, or can be understood as indicating the edge application server that provides services to the application. Specifically, the EAS address can be the address of the edge application server.

[0161] Specifically, the EAS address determined by the EASDF network element based on the first information can include the following two methods:

[0162] One possible scenario is that the EASDF network element determines the second information based on the first information; based on the second information, the EASDF network element sends a second request message to the DNS server, which requests the DNS server to select an edge application server to provide the first application service. Further, the DNS server responds to the second request message and sends the EAS address to the EASDF network element. Correspondingly, the EASDF network element receives the EAS address. Specifically, this implementation can be referred to in the embodiment corresponding to Figure 7 below.

[0163] Another possible scenario is that the target first functional network element determines the EAS address, and the EASDF network element, based on the first information, determines the target first functional network element from among the first functional network elements; then, the EASDF network element sends an EAS query request to the target first functional network element; further, the target functional network element responds to the EAS query request and sends its EAS address to the EASDF network element. Correspondingly, the EASDF network element receives the EAS address. Specifically, this implementation method can be referred to in the embodiment corresponding to Figure 9 below.

[0164] The EASDF network element can determine the target first functional network element in the following way: Based on the first request message and the first information, the EASDF network element selects the first functional network element that obtains the relevant information of the first application service as the target first functional network element. The specific implementation can be referred to step S707 in Figure 7 below, or step S907 in Figure 9 below.

[0165] S504: The EASDF network element sends the EAS address to the terminal. Correspondingly, the terminal receives the EAS address.

[0166] For example, the EASDF network element sends the EAS address to the terminal in the following manner: the EASDF network element sends the EAS address to the terminal through user plane function network elements and access network devices. Furthermore, after receiving the EAS address, the terminal can access edge application services based on the EAS address.

[0167] Optionally, when the SMF network element needs to insert ULCL for the terminal's session, or when the SMF network element needs to create or modify a session, the method shown in Figure 5 may further include the following steps S505 and S506:

[0168] S505: The EASDF network element sends a first indication message to the SMF network element. Correspondingly, the SMF network element receives the first indication message and, based on it, determines the target first functional network element.

[0169] The first indication information is used to identify the target first functional network element. The first indication information may include, but is not limited to, the EAS address, SRFID, and the DANI or DNAI prefix obtained by the SRF network element.

[0170] The target first functional network element is used to determine the tunnel identifier of the L-PSA network element. The target first functional network element is consistent with the target functional network element determined in S503. It should be understood that the target first functional network element determined by the EASDF network element is the same as the target first functional network element determined by the SMF network element.

[0171] For example, the SMF network element receives the first indication information and determines the target first functional network element based on the first indication information in the following ways: the SMF network element determines the first functional network element corresponding to the SRF network element ID as the first functional network element according to the SRFID sent by the EASDF network element.

[0172] Specifically, the SMF network element determines the target first functional network element in different ways based on the different contents included in the first indication information. The specific method by which the SMF network element determines the target first functional network element can be referred to step S712 in Figure 7 below.

[0173] S506: The SMF network element sends a tunnel identifier request for the L-PSA network element to the target first functional network element. Correspondingly, the target first functional network element determines the tunnel identifier of the L-PSA network element and sends the tunnel identifier of the L-PSA network element to the SMF network element.

[0174] Among them, the tunnel identifier request of the L-PSA network element is used to obtain the L-PSA network element tunnel identifier determined by the target first functional network element.

[0175] Among them, the tunnel identifier of the L-PSA network element is used by the SMF network element to create a user plane session path for the terminal session.

[0176] For example, an SMF network element can send a tunnel identifier request for an L-PSA network element to a target first functional network element via a GTP tunnel. Correspondingly, the target first functional network element can also send an L-PSA network element tunnel identifier to the SMF network element via a GTP tunnel.

[0177] Based on the method described in Figure 5, the newly added first functional network element provides application service-related information and user plane deployment information to the EASDF network element, resolving the issue of the EASDF network element relying on control plane network elements (SMF network elements) in determining the EAS address. Simultaneously, the first functional network element deploys application identification information related to the application service, as well as user plane deployment information. It should be understood that the user plane deployment information includes, but is not limited to, the deployment information of user plane network elements (e.g., L-PSA network elements) connected to the application service. Therefore, when the application and / or user plane deployment information changes, by modifying the relevant deployment information in the first functional network element, the EASDF network element can determine the accurate EAS address based on the updated application and / or user plane deployment information. Furthermore, this solves the problem of changes in application and / or user plane deployment information affecting control plane network elements (SMF network elements), enabling rapid deployment of edge applications and simplifying edge network modifications. Meanwhile, when the SMF network element needs to insert the ULCL network element for the terminal's session, or when the SMF network element needs to create or modify the session, the first functional network element determines the L-PSA network element, further avoiding the problem of significant impact on the SMF network element when the deployment of applications and / or user plane changes.

[0178] In this application, the network architectures underlying the two methods by which the EAS address is determined by the EASDF network element based on the first information in Figure 5 are different. Specifically, taking the SRF network element as the first functional network element as an example, the first method, which determines the EAS address through signaling interaction between the EASDF network element and the DNS server, can be applied to the network architecture shown in Figure 6. As shown in Figure 6, a schematic diagram of a network architecture provided in an embodiment of this application includes the following network elements and devices: UE, RAN, ULCL network element, L-PSA network element, PSA-UPF network element, SRF network element, EASDF network element, AMF network element, SMF network element, NRF network element, application server, and DNS server. The following is a description of each network element in Figure 6:

[0179] SRF network elements are used to provide application service information to EASDF network elements and manage L-PSA network elements. SRF network element management of L-PSA network elements can be understood as SRF network elements managing the deployment information of user plane network elements (e.g., L-PSA network elements).

[0180] It should be understood that the number of SRF network elements is unlimited and can be one or more. When there are multiple SRF network elements, the information provided by each SRF network element for application services to the EASDF network element can be the same or different.

[0181] It is important to note that SRF network elements include target SRF network elements. The target SRF network element is the SRF network element that obtains information related to the application service to be addressed.

[0182] One possible scenario is that an SRF network element represents multiple SRF network elements, and each SRF network element provides different information related to application services to the EASDF network element. In this case, the target SRF network element may include one.

[0183] Another possible scenario is that an SRF network element represents multiple SRF network elements, and if the information related to the application services provided by multiple SRF network elements to the EASDF network element is the same, then multiple target SRF network elements can exist.

[0184] The L-PSA network element is the PDU session anchor point when a terminal accesses the local network, and it is determined by the SRF network element management. The terminal can use this network element to transmit data with the local network.

[0185] SMF network elements are used to create, update, and delete PDU sessions, maintain PDU session context, be responsible for tunnel maintenance, IP address allocation, and manage and / or select other user plane function network elements (such as ULCL network elements and PSA-UPF network elements) other than L-PSA network elements.

[0186] A DNS server is used to determine the EAS address used in DNS query requests sent by a terminal.

[0187] The application server is used to provide the UE with the data for the application services requested by the UE.

[0188] In the architecture shown in Figure 6, the EASDF network element, AMF network element, PSA-UPF network element, ULCL network element, and NRF network element are consistent with those described in Figure 2. Based on the architecture shown in Figure 6, this application embodiment provides an application addressing method, the specific application addressing method of which is shown in Figure 7; the application addressing method includes the following steps:

[0189] The S700 and SRF network elements send registration information to the NRF network elements. Correspondingly, the NRF network elements receive the registration information.

[0190] Among them, the SRF network element, also known as the service routing function (SRF) network element, is used to provide application service-related information to the EASDF network element and to manage the L-PSA network element.

[0191] The description of NRF network elements can be found in the relevant description in the 5G network architecture shown in Figure 3.

[0192] The registration information can be understood as the information obtained by the SRF network element after registering with the network. The registration information is used to indicate the identification information of the SRF network element, and / or the correspondence between the UPF network element and the data network obtained by the SRF network element. The registration information may include, but is not limited to, at least one of the following: the SRF network element's identifier (e.g., SRFID), the DNAI obtained by the SRF network element, and the DNAI prefix.

[0193] Specifically, SRFID can be used to indicate SRFs. SRFID can include, but is not limited to, the name of the SRF network element, the address information of the SRF network element, etc., with different SRF network elements corresponding to different SRFID. The address information of the SRF network element is used to indicate the SRF network element, including but not limited to the IP address of the SRF network element. DNAI is used to identify the UPF (e.g., L-PSA or ULCL) obtained by the SRF network element and the data network connected to the SRF network element, or to identify the correspondence between the UPF and the application service access in the data network. The DNAI prefix can be information shared by multiple DNAIs; for example, multiple DNAIs may all begin with DNAI-Prefix.

[0194] It should be understood that in this application, S700 can be executed optionally. For example, if other functional network elements (e.g., EASDF network elements) can directly transmit data with the SRF network element, the other functional network elements can directly request the registration information of the SRF network element from the SRF network element, so the SRF network element does not need to execute S700. If other control plane network elements (e.g., SMF network elements) cannot directly transmit data with the SRF network element and need to indirectly obtain the registration information of the SRF network element through the NRF network element, then S700 needs to be executed.

[0195] Optionally, the NRF network element can store this registration information to facilitate subsequent requests from other network elements to the NRF network element for this registration information, and to perform subsequent operations based on this registration information. For example, the process of a subsequent SMF network element requesting the registration information of the SRF network element from the NRF network element, and determining the target SRF network element based on the registration information of the SRF network element.

[0196] S701 and L-PSA send EAS deployment information to the SRF network element. Correspondingly, the SRF network element obtains the EAS deployment information.

[0197] The EAS deployment information includes the application address of EAS, the address of the DNS server used for EAS addressing, and other information.

[0198] The application address of EAS, also known as the EAS address, is used to indicate the address information of EAS.

[0199] The address of the DNS server used for EAS addressing is used to indicate the DNS server that supports EAS addressing.

[0200] Understandably, this application does not limit the specific methods by which SRF network elements obtain EAS information.

[0201] Specifically, SRF network elements can also obtain EAS deployment information through other means, such as directly configuring the EAS deployment information in the SRF network element. It should be understood that in this application, S701 is optional; for example, it is not executed if the EAS deployment information is directly configured in the SRF network element. It is executed if the EAS deployment information is not configured in the SRF network element.

[0202] S702, the SRF network element sends the first information to the EASDF network element. Correspondingly, the EASDF network element obtains the first information from the SRF network element.

[0203] The first information is used to indicate the relevant information of the application service obtained by the SRF network element, including at least one of the following: the FQDN of the application service obtained by the SRF network element, the SRFID identifier of the SRF network element, the address information of the DNS server obtained by the SRF network element, the address range (UPF IP range) of the user plane function network element corresponding to the application service obtained by the SRF network element, the service area of ​​the application service obtained by the SRF network element, the DNAI obtained by the SRF network element, and the DNAI prefix obtained by the SRF network element.

[0204] Specifically, the FQDN of an application service indicates the domain name to which the application belongs, including the hostname of the application and the name of the domain name to which the application belongs. The DNS server resolves the FQDN of the application service to obtain the IP address mapped to the domain name to which the application service belongs.

[0205] Specifically, SRFID is used to identify SRF network elements. This includes the name of the SRF network element and its address information.

[0206] Specifically, the address information of the DNS server is used to indicate the DNS server.

[0207] Specifically, the DNAI and DNAI prefix obtained by the SRF network element can be the DNAI or DNAI prefix corresponding to one or more L-PSA obtained by the SRF network element, or it can be the DNAI or DNAI prefix used to identify the edge network obtained by the SRF network element.

[0208] Specifically, the application service area of ​​the application service obtained by the SRF network element is used to identify the terminal access area that the application service can serve.

[0209] Specifically, the UPF IP range can be the IP address segment or IPv6 prefix of one or more L-PSA network elements corresponding to the N6 side (or data network) obtained by the SRF network element, or it can be the IP address segment or IPv6 prefix used to identify the edge network obtained by the SRF network element.

[0210] It should be understood that the application service information obtained by the SRF network element can also be understood as the application service information stored in the SRF network element. The SRF network element can obtain application service information in various ways, such as the application sending it directly or indirectly to the SRF network element, for example, the application sending it directly to the SRF network element, or the NEF network element sending it to the SRF; it can also be obtained by other network elements and then sent to the SRF network element, for example, the UPF network element collecting application information and then sending it to the SRF; or it can be configured on the SRF, which is not limited in this invention.

[0211] S703, The terminal (UE) initiates the PDU session creation process.

[0212] The terminal initiates a PDU session creation process to establish a data transmission channel between the terminal and the data network. This process includes the UE sending a PDU session establishment request to the SMF network element through the RAN and AMF network elements. For detailed procedures on establishing a PDU session, please refer to TS23.502.

[0213] During the PDU session creation process, the S704 and SMF network elements select the EASDF network element for the terminal.

[0214] Specifically, the SMF network element selects the EASDF network element based on its stored EASDF network element identification information (including the location information of the EASDF network element) and the DNN identifier and / or slice identifier of the terminal's location information session; or, the SMF network element requests to obtain the identification information of the EASDF network element by sending a query request to the NRF, indicating the DNN identifier and / or slice identifier in the request.

[0215] After the SMF network element determines the EASDF network element for the terminal, the SMF network element subsequently sends the address of the EASDF network element to the terminal in the PDU session response message. The terminal then sends a DNS query request to the EASDF network element indicated by the EASDF network element address.

[0216] The S705 and SMF network elements obtain information such as the terminal's subscription data and send the DNS processing rules related to the terminal's PDU session to the selected EASDF network element.

[0217] When the SMF network element receives the PDU session establishment request sent by the UE, it obtains the UE's subscription data (also known as subscription data) from the UDM network element. The UE's subscription data is used to indicate the application information that needs to be addressed, which may include the application's FQDN. This allows the EASDF to process the DNS query request corresponding to the FQDN based on the corresponding addressing strategy.

[0218] The DNS processing rules related to the PDU session are created by the SMF network element and are used by the EASDF network element to process DNS query requests sent by the terminal according to the DNS processing rules sent by the SMF. The DNS processing rules may include an addressing policy ID, which the EASDF uses to process the terminal's DNS query requests based on the addressing policy corresponding to the addressing policy ID. Alternatively, the DNS processing rules may instruct the EASDF to perform DNS addressing based on the UE's location.

[0219] The addressing policy ID is an identifier used to indicate the policy for handling DNS query requests to EASDF network elements. It includes at least one of the following: DNS request message processing rule priority and DNS request message (also known as DNS query request) detection template. The DNS request message detection template includes at least one of the following: message type, source IP address, FQND range array, and IP address range array.

[0220] For example, the DNS processing rules sent by the SMF network element to the EASDF network element include instructions for the EASDF to perform DNS addressing based on the UE's location. After receiving the instruction from the SMF network element to perform DNS addressing based on the UE's location, the EASDF network element subsequently determines the ECS information or EAS address based on the UE's location information. For instance, in S707, the EASDF network element can determine the ECS information based on the terminal's (UE) location information; or, the EASDF network element can execute steps S707 to S710 to determine the EAS information based on the terminal's location information and the first information obtained by the target SRF.

[0221] For example, the DNS processing rules sent by the SMF network element to the EASDF network element include an addressing policy ID. The EASDF network element receives the addressing policy ID sent by the SMF network element. The addressing policy corresponding to the addressing policy ID instructs the EASDF network element to determine the ECS information based on the FQDN applied in the DNS request message detection template. Therefore, the EASDF network element can perform ECS information determination based on the applied FQDN in S707.

[0222] For example, the DNS processing rules sent by the SMF network element to the EASDF network element include an addressing policy ID. The EASDF network element receives the addressing policy ID from the SMF network element. The addressing policy corresponding to this addressing policy ID instructs the EASDF network element to determine the EAS address based on the FQDN applied in the DNS request message detection template. Therefore, the EASDF network element can execute steps S707 to S710 to determine the EAS information based on the applied FQDN and the first information obtained from the target SRF.

[0223] In one possible scenario, the SMF sends the terminal's location information to the EASDF network element. This location information is used to indicate the area information where the terminal accesses the wireless network.

[0224] It should be understood that in this application, the sending of terminal location information from the SMF network element to the selected EASDF network element is an optional operation. For example, this operation is not performed when the DNS server is determined through the FQDN of the application service in the DNS query request. This operation is performed when the target SRF network element, ECS information, and DNS server are determined through the terminal's location information.

[0225] S706. After the terminal completes the PDU session creation, it sends a DNS query request to the UPF-PSA network element. Correspondingly, the UPF-PSA network element receives the DNS query request and forwards it to the EASDF network element.

[0226] It should be understood that when a terminal completes the creation of a PDU session, it means that a data channel has been established between the terminal and the data network, enabling the terminal to interact with the data network.

[0227] The DNS query request is used to discover the application's EAS, including the application's identification information.

[0228] It should be understood that this application does not limit the way a terminal discovers an application's edge application services. A terminal can discover an application's edge application services via DNS or non-DNS methods.

[0229] For example, when a terminal discovers an application's edge application service via DNS, the terminal sends a DNS query request. The DNS request is used to discover the application's EAS, including the application's identifier (e.g., FQDN).

[0230] For example, when a terminal discovers an application's edge application service (EAS) using a non-DNS method, the terminal sends a query request to discover the application's EAS, including the application's anycast address.

[0231] It should be understood that when a terminal discovers an application's edge application service through a non-DNS method, the application can also refer to the same type of application. In this case, the query request sent by the terminal is used to discover the EAS of the same type of application, including the identifier of the same type of application (e.g., the application type of the same type of application).

[0232] One possible scenario is that the terminal sends a DNS-based query to the edge application service (e.g., EAS), in which case the DNS query request sent by the terminal includes the application identifier of the application service (e.g., the application service's FQDN).

[0233] Another possible scenario is that the terminal sends an edge application service query for computing power using a non-DNS method. In this case, the query request sent by the terminal includes the identifier of the computing power (e.g., the type of computing power).

[0234] In response to a DNS query request, the S707 and EASDF network elements determine the target SRF network element, or determine the ECS information, or determine the address information of the DNS server.

[0235] Optional execution: Step S707 is used by EASDF network elements to determine the target SRF network element. In this case, it includes the following steps:

[0236] One possible scenario is that the EASDF network element determines the target SRF network element based on the DNS query request forwarded by the UPF-PSA network element and the first information obtained by the EASDF network element from the SRF network element in S702.

[0237] Specifically, the process by which an EASDF network element determines the target SRF network element is as follows: The EASDF network element takes the FQDN used in the DNS query request as the target, and determines the SRF network element that includes the FQDN used in the DNS query request in the first information obtained by the SRF network element as the target SRF network element.

[0238] It should be understood that the protocol stipulates that when the EASDF network element determines the target SRF based on the FQDN applied in the DNS request, the SRF sends the applied FQDN from the first information to the EASDF network element. Alternatively, in S705, the DNS processing rules sent by the SMF network element to the EASDF network element include an addressing policy ID. The addressing policy corresponding to this addressing policy ID instructs the EASDF network element to determine the EAS address based on the FQDN applied in the DNS request message detection template. In this case, the EASDF network element requests the applied FQDN from the SRF network element in S702.

[0239] Another possible scenario is that the EASDF network element determines the target SRF network element based on the terminal location information sent by the SMF network element in S705 and the first information obtained by the EASDF network element from the SRF network element in S702.

[0240] Specifically, the process by which the EASDF network element determines the target SRF network element is as follows: The EASDF network element takes the terminal's location information as the target, compares the service area of ​​the SRF network element in the first information obtained from the SRF network element in S702 with the target one by one, and selects the SRF network element whose service area in the first information includes the terminal's location information as the target SRF network element.

[0241] It should be understood that the protocol stipulates that when the EASDF network element determines the target SRF based on the terminal's location information, the SRF sends the service area of ​​the SRF network element in the first information to the EASDF network element.

[0242] Optional execution: Step S707 is used by EASDF network elements to determine ECS information. This ECS information is used by the DNS server to select the EAS. It includes the following steps:

[0243] One possible scenario is that the EASDF network element determines the ECS information based on the terminal location information obtained from the S705.

[0244] Specifically, the process by which the EASDF network element determines the ECS information is as follows: Based on the location information of the terminal obtained from the S705, the EASDF network element selects a user plane network element that is close to the location and whose connected DN has the application requested by the terminal deployed, and uses the location information of the user plane network element (such as the address or address range information of the user plane network element) as the ECS information.

[0245] Another possible scenario is that the EASDF network element determines the ECS information based on the FQDN used in the DNS query request and the FQDN used in the first information obtained from S702.

[0246] Specifically, the process by which the EASDF network element determines the ECS information is as follows: The EASDF network element matches the FQDN used in the first information sent by the SRF network element to the EASDF network element based on the FQDN in the DNS query request, and selects the ECS information corresponding to the FQDN in the policy.

[0247] It should be understood that the protocol stipulates that when the EASDF network element determines the target ECS information based on the FQDN applied in the DNS query request, the SRF sends the FQDN applied in the first information to the EASDF network element. Alternatively, the DNS processing rules sent by the SMF network element to the EASDF network element in S705 include an addressing policy ID. The addressing policy corresponding to this addressing policy ID instructs the EASDF network element to determine the ECS information based on the FQDN applied in the DNS request message detection template. In this case, the EASDF network element requests the FQDN applied in the first information from the SRF network element in S702.

[0248] Optional execution: Step S707 is used by EASDF network elements to determine the address information of the DNS server, wherein the address information of the DNS server is used to indicate the DNS server.

[0249] One possible scenario is that the EASDF network element determines the DNS server address information based on the terminal location information obtained by the S705.

[0250] Specifically, the process by which the EASDF network element determines the address information of the DNS server is as follows: The EASDF network element, using the terminal's location information as the target, compares the service areas of each SRF network element in the first information obtained from the SRF network element in S702 with the target, selecting the SRF network element whose service area includes the terminal's location information as the target SRF network element. Further, the EASDF network element uses the DNS server address information obtained from the target SRF network element as the address information of that DNS server.

[0251] It should be understood that the protocol stipulates that when the EASDF network element determines the DNS server address information based on the terminal's location information, the SRF sends the service area of ​​the SRF network element in the first information to the EASDF network element.

[0252] Another possibility is that the EASDF network element determines the DNS server address information based on the FQDN used in the DNS query request.

[0253] Specifically, the process by which an EASDF network element determines the address information of a DNS server is as follows: Based on the FQDN in the DNS query request, the EASDF network element identifies the SRF network element whose first information obtained by the SRF network element includes the FQDN applied in the DNS query request as the target SRF network element. Further, the EASDF network element uses the DNS server address information obtained by the target SRF network element as the address information of that DNS server.

[0254] It should be understood that, according to the protocol, when the FQDN used in the DNS query request of the EASDF network element determines the DNS server address information, the SRF sends the FQDN used in the first information to the EASDF network element. Alternatively, the DNS processing rules sent by the SMF network element to the EASDF network element in S705 include an addressing policy ID. The addressing policy corresponding to this addressing policy ID instructs the EASDF network element to determine the EAS address based on the FQDN used in the DNS request message detection template. In this case, the EASDF network element requests the FQDN used in the first information from the SRF network element in S702.

[0255] The S708 and EASDF network elements send request messages to the target SRF network element. Correspondingly, the target SRF network element receives the request message.

[0256] The request message is used to obtain information about the application services acquired by the target SRF network element. The request message includes the FQDN of the application and / or the location information of the terminal in the DNS query request.

[0257] It should be understood that step S708 is optional. Step S708 is executed if step S707 involves using EASDF network elements to determine the target SRF network element. Step S708 is not executed if step S707 involves using EASDF network elements to determine ECS information, or if step S707 involves using EASDF network elements to determine the DNS server address information.

[0258] S709. The target SRF network element determines the address information of the ECS information or DNS server based on the request message sent by the EASDF network element, and sends the address information of the ECS information or DNS server to the EASDF network element.

[0259] Specifically, the method by which the target SRF network element determines the address information of the DNS server based on the request message sent by the EASDF network element includes: the target SRF network element sending the DNS server address information it has obtained as the address information of the DNS server to the EASDF network element.

[0260] Specifically, the methods by which the target SRF network element determines ECS information based on the request message sent by the EASDF network element include the following:

[0261] One possible scenario is that the request message sent by the EASDF network element includes the terminal's location information. In this case, the target SRF network element modifies the terminal's location information to ECS information. Then, it sends this ECS information to the EASDF network element.

[0262] Another possible scenario is that the request message sent by the EASDF network element includes the application's FQDN. In this case, the method by which the target SRF network element determines the ECS information includes: the target SRF network element takes the application indicated by the application's FQDN in the request message as the target application, and also takes the application indicated by the application's FQDN in its first acquired information as the target application; then, the target SRF network element determines the UPF network element corresponding to the target application based on the correspondence between the application indicated by its own DNAI and the UPF; further, the address information of the UPF network element corresponding to the target application is used as the ECS information. Finally, the ECS information is sent to the EASDF network element.

[0263] It should be understood that S709 is an optional execution step. If S708 is executed, then S709 is executed. If S708 is not executed, then S709 is not executed.

[0264] The S710 and EASDF network elements send DNS request messages to the DNS server. Correspondingly, the DNS server sends DNS response messages to the EASDF network elements. The DNS request message is used to obtain the application's EAS.

[0265] The DNS response message is used to respond to the DNS request message, including the EAS address of the application determined by the DNS server. The EAS address indicates the application's EAS.

[0266] Optional execution: The DNS request message includes the ECS information determined in S709 or S707.

[0267] For example, when the DNS server is a centralized DNS server, the DNS request message includes the ECS information determined above. In this case, the centralized DNS server needs to select an EAS that is closer to the terminal's location as the application's EAS, based on the ECS information in the DNS request message (the ECS information can indicate the terminal's location information).

[0268] Optional execution: The DNS request message does not include the ECS information determined in S709 or S707.

[0269] For example, when the DNS server is the DNS server indicated by the address information of the aforementioned DNS server, the DNS request message may not include the determined ECS information. In this case, the DNS server selects the application's EAS from the edge application servers it manages. Whether the DNS request message includes ECS information or not does not affect the DNS server's determination of the application's EAS.

[0270] Optionally, the EASDF network element sends a DNS request message to the DNS server indicated by the address information of the DNS server determined in S707 or S709. For example, if the EAS of the application is determined by both a local DNS server and a centralized DNS server, this is not performed. If the EAS of the application is determined by the aforementioned determined DNS server, this is performed.

[0271] It should be understood that this application does not restrict the specific method by which EASDF network elements obtain EAS addresses.

[0272] For example, this application provides a possible method for an EASDF network element to determine the EAS address based on a DNS server. An EASDF network element can also determine the EAS address in other ways; for instance, if the EASDF network element has the functionality of an SRF network element, the EAS address can be determined directly by the EASDF network element.

[0273] S711 and EASDF network elements determine the target SRF network element based on the FQDN used in the DNS query request or the EAS address in the DNS response message.

[0274] One possible scenario is that the EAS network element determines the target SRF network element based on the EAS address in the DNS response message and the UPF IP range in the first information obtained from the SRF in S702. The UPF IP range includes the EAS address.

[0275] Specifically, the method by which an EASDF network element determines a target SRF network element includes: based on the EAS address in the DNS response message, the EASDF network element identifies SRF network elements whose first information obtained by the SRF network element includes the EAS address in the DNS response message as target SRF network elements. The first information obtained by the SRF network element includes the UPF IP range containing the EAS address.

[0276] Another possible scenario is that the EASDF network element determines the target SRF network element based on the FQDN used in the DNS query request and the FQDN used in the first information of the SRF obtained in S702. The specific method is the same as the method in S707 for the EASDF network element to determine the target first functional network element based on the FQDN used in the DNS query request, and will not be elaborated here.

[0277] It should be understood that S711 is an optional execution step. For example, if the target first functional network element is not determined in step S707, step S711 is executed. If the target SRF network element has been determined in step S707, S711 is not executed.

[0278] S712, the EASDF network element sends the first indication information to the SMF network element. Accordingly, the SMF network element determines the target SRF network element based on the first indication information.

[0279] The first indication information is used to identify the target SRF network element, including at least one of the following: DNAI or DNAI prefix obtained by the target SRF network element, SRF network element identifier of the target SRF network element, and EAS address.

[0280] One possible scenario is that the first indication information includes the DNAI or DNAI prefix obtained by the target SRF network element. The SMF network element determines the target SRF network element based on the first indication information and the SRF registration information in the NRF.

[0281] Specifically, the process by which the SMF network element determines the target SRF network element based on the first indication information is as follows: The SMF network element sends a DNAI or DNAI prefix to the NRF network element. The NRF network element, based on the registration information of the SRF network elements in S700, selects the SRF network element whose DNAI and DNAI prefix match those in the first indication information as the target SRF network element. Subsequently, the NRF network element sends the target SRF network element to the SMF network element. The SRF registration information includes the DNAI or DNAI prefix obtained by the SRF network element.

[0282] Another possible scenario is that the first indication information includes the SRF network element identifier of the target SRF network element. The process by which the SMF network element determines the target SRF network element based on the first indication information is as follows: the SMF network element takes the SRF network element indicated by the SRF network element identifier as the target SRF network element.

[0283] Another possible scenario is that the first indication information includes the EAS address, and the SMF network element determines the target SRF network element based on the first indication information and the local configuration information of the SMF network element.

[0284] Specifically, the process by which the SMF network element determines the target SRF network element based on the first indication information is as follows: the SMF network element selects the SRF network element whose corresponding UPF IP range contains the EAS address as the target SRF network element.

[0285] It should be understood that S712 is an optional execution step. For example, S712 is executed when the SMF network element needs to insert a ULCL network element for the terminal's session, or when the SMF network element needs to create or modify a session; otherwise, S712 is not executed.

[0286] S713 and SMF network elements insert ULCL network elements into terminal sessions.

[0287] Specifically, the method by which the SMF network element inserts the ULCL network element into the terminal session includes: the SMF network element requests the tunnel identifier of the L-PSA network element from the target SRF network element and selects the ULCL network element; subsequently, the SMF network element provides the tunnel identifier of the L-SPA network element and the tunnel identifier of the RAN to the ULCL network element, and provides the downlink tunnel address of the ULCL network element to the L-PSA network element through the target SRF network element, and provides the uplink tunnel identifier of the ULCL network element to the RAN through the AMF network element.

[0288] The RAN tunnel identifier is sent by the SMF network element to the AMF network element in a session creation / modification request, and the AMF network element responds accordingly with a session creation / modification response. The RAN session creation / modification response includes the RAN tunnel identifier. The RAN tunnel identifier indicates the tunnel through which the RAN receives data.

[0289] The downlink tunnel address of the ULCL network element is allocated by the SMF network element or obtained from the ULCL network element, and is used to indicate the downlink tunnel through which the ULCL network element receives downlink data. The SMF network element provides the downlink tunnel address of the ULCL network element to the L-PSA network element through the target SRF. The L-PSA network element is determined by the target SRF network element.

[0290] The uplink tunnel address of the ULCL network element is assigned by the SMF network element or obtained from the ULCL network element, and is used to indicate the uplink tunnel for receiving uplink data in the ULCL. The SMF network element sends the uplink tunnel address of the ULCL to the AMF network element, and then the AMF network element forwards the uplink tunnel address of the ULCL network element to the RAN, so that the RAN can send data to the uplink tunnel of the ULCL network element.

[0291] The process by which an SMF network element selects a ULCL network element is as follows: Based on the terminal's location information, the SMF network element selects a UPF network element that is closest to the terminal from among the UPF network elements managed by the SMF itself as the ULCL network element. Alternatively, the SMF selects a ULCL network element based on information from the L-PSA network element, for example, selecting a user plane network element deployed between the RAN and L-PSA network elements as the ULCL network element.

[0292] The tunnel identifier of the L-PSA, used to indicate the tunnel through which the L-PSA network element receives data packets, is determined by the target SRF network element. This determination method includes: the target SRF network element determining the target L-PSA network element based on the session creation / modification request sent by the SMF network element.

[0293] Specifically, the process by which the target SRF network element determines the target L-PSA network element based on the session creation / modification request sent by the SMF network element is as follows: The SMF network element sends a session creation / modification request to the target SRF network element, and the session creation / modification request includes the terminal's location information. Correspondingly, the target SRF network element receives the session creation / modification request, uses the terminal's location information in the request as the target, and selects a target L-PSA network element from among the L-PSA network elements it manages, for example, selecting an L-PSA network element closer to the terminal's location. Subsequently, the target SRF sends the tunnel identifier of the target L-PSA network element to the SMF network element.

[0294] Based on the above steps, the SMF network element and the target SRF network element create a user plane session path for the terminal device.

[0295] It should be understood that S713 is an optional execution step. For example, S713 is executed when the SMF network element needs to insert a ULCL network element for the terminal's session, or when the SMF network element needs to create or modify a session; otherwise, S713 is not executed.

[0296] The S714 and SMF network elements send response messages to the EASDF network elements. Correspondingly, the EASDF network elements receive the response messages and forward them to the terminals.

[0297] The SMF network element sends a response message to the EASDF network element to indicate that the ULCL network element has been inserted. The insertion of the ULCL network element can be understood as the SMF network element having created a path for this session. After receiving the response message from the SMF network element, the EASDF network element forwards a DNS response message to the terminal.

[0298] One possible scenario is that after receiving the DNS response message, the EASDF network element in the S710 caches the DNS response message in the EASDF network element. If the SMF network element has already created a path for this session, the EASDF network element will send the received DNS response message to the terminal through the already created path.

[0299] Another possible scenario is that after receiving the DNS response message, the EASDF network element in the S710 caches the DNS response message in the EASDF network element. If the SMF network element has not created a path for this session, the EASDF network element needs to receive the response message sent by the SMF network element and then send the received DNS response message to the terminal.

[0300] After receiving the response message from the SMF network element, the EASDF network element forwards the DNS response message to the terminal. Specifically, the EASDF network element modifies the destination address in the DNS response message sent by the DNS server in the S710 to the terminal's address. This is because the destination address in the DNS response message sent by the DNS server in the S710 is the address of the EASDF network element.

[0301] In this application, the network architectures underlying the two methods for determining the EAS address of the EASDF network element based on the first information in Figure 5 are different. Specifically, the second method can be applied to the network architecture shown in Figure 8. As shown in Figure 8, a schematic diagram of a network architecture provided by an embodiment of this application includes the following network elements:

[0302] SRF network element: Used to provide application service related information to EASDF network elements and manage L-PSA network elements; also used to determine the EAS address used in the DNS query request sent by the terminal.

[0303] It should be understood that the number of SRF network elements is unlimited and can be one or more. When there are multiple SRF network elements, the information related to application services provided by each SRF network element to the EASDF network element can be the same or different.

[0304] It is important to note that SRF network elements include target SRF network elements. The target SRF network element is the SRF network element that obtains information related to the application to be addressed.

[0305] One possible scenario is that an SRF network element represents multiple SRF network elements, and each SRF network element provides different information for application services to the EASDF network element. In this case, there is only one target SRF network element.

[0306] Another possible scenario is that an SRF network element represents multiple SRF network elements, and if the information related to the application services provided by multiple SRF network elements to the EASDF network element is the same, then multiple target SRF network elements can exist.

[0307] The architecture shown in Figure 8, including EASDF, AMF, PSA-UPF, ULCL, and NRF network elements, is consistent with that described in Figure 2.

[0308] Based on the architecture shown in Figure 8, this application embodiment provides an application addressing method, the specific application addressing method of which is shown in Figure 9; the application addressing method includes the following steps:

[0309] The steps from S900 to S905 are the same as those from S700 to S705, and will not be repeated here.

[0310] S906. After completing session creation, the terminal (UE) sends a DNS query request to the EASDF network element through the terminal session. Correspondingly, the EASDF network element receives the DNS query request.

[0311] The DNS query request is used to discover the application's EAS, including the application's identification information (e.g., the application's FQDN).

[0312] It should be understood that this application does not limit the type and content of query requests sent by the terminal.

[0313] One possible scenario is that the terminal sends a query request based on a non-DNS addressing method, such as an Anycast addressing request. Anycast addressing is a method of querying a network address based on the application's Anycast address. Therefore, the query request sent by the terminal based on Anycast addressing includes the application's identification information and its Anycast address.

[0314] Another possibility is that the terminal sends a query request based on DNS addressing. DNS addressing is a method of querying the network address based on the application's address; therefore, the query request sent by the terminal based on DNS addressing includes the application's FQDN.

[0315] S907 and EASDF network elements determine the target SRF network element based on DNS query requests and / or terminal location information.

[0316] Specifically, the process of determining the target SRF network element in S907 and S707 is the same, and will not be repeated here.

[0317] The S908 and EASDF network elements send an EAS query request to the target SRF network element. The target SRF network element then receives the EAS query request.

[0318] The EAS query request is used to determine the application's EAS, including at least one of the application's FQND and DNS query request messages.

[0319] The FQDN of the above application is used to indicate the domain name of the application.

[0320] The aforementioned DNS query request message is used to indicate detailed information about the DNS query request, including the application's domain name, query type, and time-to-live (TTL). The application's domain name can be indicated by its FQDN; the query type indicates the type of resource record, for example, type 2 indicates a query for a domain name server, and type 1 indicates obtaining the IP address mapped to the domain name; the TTL, in seconds, indicates the lifespan of the resource record, which can be understood as the time after the address resolver retrieves the resource record to decide whether to store and use the cached data.

[0321] For example, an EAS query request sent by an EASDF network element to a target SRF network element includes the application's FQDN. The target SRF network element then performs subsequent steps based on the application's FQDN.

[0322] For example, an EAS query request sent by an EAS network element to a target SRF network element includes a DNS query request message. The target SRF network element then performs subsequent steps based on the DNS query request message.

[0323] S909, the target SRF network element determines the EAS address based on the EAS query request.

[0324] The EAS address is used to indicate the application's EAS;

[0325] The target SRF network element uses different methods to determine the EAS address based on the different information included in the EAS query request.

[0326] One possible scenario is that the EAS query request includes a DNS query request message or the application's FQDN. In this case, the target SRF network element determines the EAS address based on the application information in its local records and the EAS query request. Local records can be understood as information stored within the target SRF network element itself. Application information includes: the application's EAS, the application's FQDN, etc.

[0327] For example, the process by which a target SRF network element determines the EAS address is as follows: the target SRF network element determines the EAS address corresponding to the FQDN from its own stored (locally recorded) application information based on the FQDN used in the EAS query request. When determining the EAS address, the target SRF network element can also select an EAS based on load balancing strategies, etc.

[0328] Another possible scenario is that the EAS query request includes a DNS query request message. In this case, the target SRF network element determines the EAS address based on the local addressing policy and the EAS query request. The local addressing policy includes: the SRF determining a local DNS server and obtaining the EAS address from the local DNS server.

[0329] For example, the process by which a target SRF network element determines the EAS address is as follows: The target SRF determines the local DNS server based on the application address and / or the terminal's location information in the DNS query request message. Then, the target SRF network element sends a DNS query request message within the EAS query request to the local DNS server to further obtain the EAS address from the local DNS server. There are several possibilities regarding how the local DNS server obtains the DNS query request message.

[0330] It should be understood that this application does not restrict the way a local DNS server obtains DNS query request messages.

[0331] One possible scenario is that the EASDF network element forwards the user's DNS query request message to the target SRF network element. Subsequently, the target SRF network element modifies the destination address in the DNS query request message to the address of the local DNS server. Furthermore, the target SRF network element sends a DNS query request message to the local DNS server.

[0332] Another possible scenario is that the target SRF network element creates a DNS query request message based on the application's FQND sent by the EASDF network element, and then sends the DNS query request message to the local DNS server.

[0333] S910, the target SRF network element sends the EAS address to the EASDF network element. Correspondingly, the EASDF network element receives the EAS address.

[0334] In this process, the target SRF network element sends the EAS address to the EASDF network element, enabling the EASDF network element to determine the EAS of the application.

[0335] Optionally, in this application, the target SRF network element may also send the DNAI or DNAI prefix obtained by the target SRF network element to the EASDF network element. The DNAI or DNAI prefix is ​​used to indicate to the EASDF network element the correspondence between the UPF managed by the target SRF network element and the EAS, or information about the edge network managed by the target SRF network element.

[0336] For example, if the EASDF network element has already obtained the DNAI or DNAI prefix corresponding to EAS from the target SRF network element, it will not be executed. If the EASDF network element has not obtained the DNAI or DNAI prefix corresponding to EAS from the target SRF network element, it will be executed.

[0337] Steps S911 to S913 are the same as steps S712 to S714, and will not be repeated here.

[0338] Based on the method shown in Figure 9, deployment independent of a DNS server is achieved, with the EAS address determined by the target SRF network element. Furthermore, even when a local DNS is deployed in the local network, and there is no data connection between the EASDF network element and the local DNS server, application addressing can still be achieved using the method shown in Figure 9.

[0339] The above mainly describes the solutions provided in the embodiments of this application from the perspective of the interaction between various network elements and devices. It is understood that each network element and device, such as the first functional network element, EASDF network element, SMF network element, terminal device, etc., includes corresponding hardware structures and / or software modules to execute each function in order to achieve the above functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0340] This application embodiment can group terminals, network elements, network devices, etc., into functional modules according to the above method examples. For example, each functional group can correspond to a different functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the grouping of modules in this application embodiment is illustrative and only represents one logical functional grouping; other grouping methods may be used in actual implementation.

[0341] Figure 10 shows a structural diagram of a communication device 100, which can be used to perform the functions of the EASDF network elements involved in the above embodiments. As one possible implementation, the communication device 100 shown in Figure 10 includes: a receiving unit 1001, a processing unit 1002, and a transmitting unit 1003;

[0342] The receiving unit 1001 is used to receive first request information from the terminal. For example, the receiving unit may support the communication device 100 in executing S706 or S906.

[0343] The processing unit 1002 is used to obtain first information from the first functional network element. For example, the processing unit 1002 may be used to support the communication device 100 in executing S702 or S902.

[0344] The processing unit 1002 is also configured to respond to the first request message and determine the EAS address based on the first information. For example, the processing unit 1002 may be configured to support the communication device 100 in executing S707 to S710, or may be configured to support the communication device 100 in executing S907 to S909.

[0345] The sending unit 1003 is used to send the EAS address to the terminal. For example, the sending unit 1003 may support the communication device 100 to execute S714 or S913.

[0346] The descriptions of the first request message, the first information, and the EAS address can be found in the above method embodiments.

[0347] Specifically, all relevant content of each step involved in the method embodiments shown in Figures 7 and 9 above can be referenced from the functional descriptions of the corresponding functional modules, and will not be repeated here. The communication device 100 is used to execute the function of the EASDF network element in the application addressing method shown in Figure 7 or Figure 9, and therefore can achieve the same effect as the application addressing method described above.

[0348] As another possible implementation, the communication device 100 shown in FIG10 includes a processing module and a communication module. The processing module controls and manages the operation of the communication device 100. For example, the processing module may integrate the functions of the processing unit 1002, and may be used to support the communication device 100 in executing S702 and S707 to S710, or to support the communication device in executing S902 and S907 to S909, and other processes of the technology described herein. The communication module may integrate the functions of the receiving unit 1001 and the transmitting unit 1003, and may be used to support the communication device 100 in executing S706 or S714, or to support the communication device 100 in executing S906 or S913 and communication with other network entities, such as communication with the functional modules or network entities shown in FIG7 and FIG9. The communication device 100 may also include a storage module for storing the program code and data of the communication device 100.

[0349] Figure 11 shows a structural diagram of a communication device 110, which can be used to perform the functions of the first functional network element involved in the above embodiments. As one possible implementation, the communication device 110 shown in Figure 11 includes: a processing unit 1101 and a transmitting unit 1102;

[0350] Processing unit 1101 is used to obtain EAS deployment information. For example, processing unit 1101 may be used to support communication device 110 in executing S701, or it may be used to support communication device 110 in executing S901.

[0351] The transmitting unit 1102 is used to transmit first information to the EASDF network element. For example, the transmitting unit 1102 may support the communication device 110 to execute S702 or S902.

[0352] The descriptions of EAS deployment information and first information can be found in the above method embodiments.

[0353] Specifically, all relevant content of each step involved in the method embodiments shown in Figures 7 and 9 above can be referenced from the functional description of the corresponding functional module, and will not be repeated here. The communication device 110 is used to execute the first functional network element in the application addressing method shown in Figure 7 or Figure 9, and therefore can achieve the same effect as the application addressing method described above.

[0354] As another possible implementation, the communication device 110 shown in FIG11 includes a processing module and a communication module. The processing module controls and manages the operation of the communication device 110. For example, the processing module may integrate the functions of the processing unit 1101 and can be used to support the communication device 110 in executing S701 or S901, as well as other processes of the technology described herein. The communication module may integrate the functions of the transmitting unit 1102 and can be used to support the communication device 110 in executing S702 or S902 and communicating with other network entities, such as communication with the functional modules or network entities shown in FIG7 and FIG9. The communication device 110 may also include a storage module for storing the program code and data of the communication device 110.

[0355] Figure 12 shows a structural diagram of a communication device 120, which can be used to perform the functions of the SMF network elements involved in the above embodiments. As one possible implementation, the communication device 120 shown in Figure 12 includes: a receiving unit 1201, a processing unit 1202, and a transmitting unit 1203;

[0356] The receiving unit 1201 is used to receive the first indication information sent by the EASDF network element, and to receive the tunnel identifier of the L-PSA sent by the target first functional network element. For example, the receiving unit 1201 can support the communication device 120 to execute S712 and S713, or it can be used to support the communication device 120 to execute S911 and S912.

[0357] The processing unit 1202 is configured to determine a target first functional network element based on the first indication information. For example, the processing unit 1202 may be configured to support the communication device 120 in executing S712, or may be configured to support the communication device 120 in executing S911.

[0358] The sending unit 1203 is used to send a tunnel identification request for L-PSA to the target first functional network element. For example, the sending unit 1203 may support the communication device 120 to execute S713 or S912.

[0359] The descriptions of the target first functional network element, the first indication information, and the tunnel identification request of L-PSA can be referred to in the above method embodiments.

[0360] Specifically, all relevant content of each step involved in the method embodiments shown in Figures 7 and 9 above can be referenced from the functional description of the corresponding functional module, and will not be repeated here. The communication device 120 is used to perform the function of the SMF network element in the application addressing method shown in Figure 7 or Figure 9, and therefore can achieve the same effect as the application addressing method described above.

[0361] As another possible implementation, the communication device 120 shown in FIG12 includes a processing module and a communication module. The processing module controls and manages the operation of the communication device 120. For example, the processing module may integrate the functions of the processing unit 1202 and may be used to support the communication device 120 in executing S712 or S911, as well as other processes of the technology described herein. The communication module may integrate the functions of the receiving unit 1201 and the transmitting unit 1203 and may be used to support the communication device 120 in executing S712 and S713, or to support the communication device 120 in executing S911 and S912 and communicating with other network entities, such as communication with the functional modules or network entities shown in FIG7 and FIG9. The communication device 120 may also include a storage module for storing the program code and data of the communication device 120.

[0362] The aforementioned processing module can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication module can be a transceiver circuit or a communication interface, etc. The storage module can be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 100, communication device 110, and communication device 120 involved in the embodiments of this application can be the communication device 130 shown in FIG. 13. For example, the EASDF network element, the first functional network element, and the SMF network element mentioned above can adopt the composition structure shown in FIG. 13 or include the components shown in FIG. 13. FIG. 13 is a schematic diagram of the composition of a communication device 130 provided in an embodiment of this application. As shown in FIG. 13, the communication device 130 can include a processor 1301, a communication line 1302, and a communication interface 1303.

[0363] Furthermore, the communication device 130 may also include a memory 1304. The processor 1301, the memory 1304, and the communication interface 1303 can be connected via a communication line 1302.

[0364] The processor 1301 can be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor 1301 can also be other communication devices with processing capabilities, such as circuits, devices, or software modules.

[0365] Communication line 1302 is used to transmit information between the components included in communication device 130.

[0366] Communication interface 1303 is used for communication with other devices or other communication networks. These other communication networks can be Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. Communication interface 1303 can be a radio frequency module, transceiver, or any communication device capable of communication. This application embodiment uses a radio frequency module as an example to illustrate communication interface 1303. The radio frequency module can include an antenna, radio frequency circuitry, etc., and the radio frequency circuitry can include a radio frequency integrated chip, a power amplifier, etc.

[0367] Memory 1304 is used to store instructions. These instructions can be computer programs.

[0368] The memory 1304 can be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions; it can also be a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions; it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage, magnetic disk storage medium or other magnetic storage device. Optical disc storage includes compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.

[0369] It should be noted that the memory 1304 can exist independently of the processor 1301, or it can be integrated with the processor 1301. The memory 1304 can be used to store instructions, program code, or some data, etc. The memory 1304 can be located inside or outside the communication device 130, without limitation. The processor 1301 is used to execute the instructions stored in the memory 1304 to implement the communication method provided in the following embodiments of this application.

[0370] In one example, processor 1301 may include one or more CPUs, such as CPU0 and CPU1 in Figure 13.

[0371] As an optional implementation, the communication device 130 may include multiple processors, for example, in addition to the processor 1301 in FIG13, it may also include a processor 1307.

[0372] As an optional implementation, the communication device 130 also includes an output device 1305 and an input device 1306. The input device 1306 is a keyboard, mouse, microphone, or joystick, etc., and the output device 1305 is a display screen, speaker, etc.

[0373] It should be noted that the communication device 130 can be a desktop computer, a portable computer, a web server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device with a similar structure to that shown in Figure 13. Furthermore, the composition shown in Figure 13 does not constitute a limitation on the communication device. In addition to the components shown in Figure 13, the communication device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0374] In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.

[0375] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be implemented by a computer program instructing related hardware. This program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can be a terminal of any of the foregoing embodiments, such as an internal storage unit including a data transmission end and / or a data receiving end, like a hard disk or memory of the terminal. The computer-readable storage medium can also be an external storage device of the terminal, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal. Further, the computer-readable storage medium can include both the internal storage unit and the external storage device of the terminal. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0376] It should be understood that the collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution of this application all comply with relevant laws and regulations and do not violate public order and good morals. For example, in the technical solution of this application, the processing of user personal information is carried out with the user's authorization, and this will not be repeated hereafter.

[0377] It should be noted that the terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0378] It should be understood that in this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0379] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A. For example, B can be determined based on A. It should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information. Furthermore, the term "connection" in the embodiments of this application refers to various connection methods, such as direct connection or indirect connection, to achieve communication between devices, and the embodiments of this application do not impose any limitations on this.

[0380] Unless otherwise specified, the term "transmission" in the embodiments of this application refers to bidirectional transmission, encompassing the actions of sending and / or receiving. Specifically, "transmission" in the embodiments of this application includes sending data, receiving data, or both sending and receiving data. In other words, data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals; uplink data transmission refers to uplink channel and / or uplink signal transmission, and downlink data transmission refers to downlink channel and / or downlink signal transmission. The terms "network" and "system" in the embodiments of this application refer to the same concept; a communication system is a communication network.

[0381] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the grouping of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

[0383] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0384] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0385] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device, such as a microcontroller, chip, or processor, to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media for storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. An application addressing method, characterized in that, The method includes: The edge application service discovery function network element obtains first information from the first function network element; wherein, the first function network element is used to select application services and / or user plane network elements; the first information is used to indicate the relevant information of the application services obtained by the first function network element; The edge application service discovery function network element receives a first request message from the terminal; wherein, the first request message is used to discover a first application service; In response to the first request message, the edge application service discovery function network element determines the edge application service (EAS) address of the first application service based on the first information. The edge application service discovery function network element sends the EAS address to the terminal.

2. The method according to claim 1, characterized in that, The edge application service discovery function network element determines the edge application service (EAS) address based on the first information, including: The edge application service discovery function network element determines second information based on the first information; the second information includes extended Domain Name System Client Subnet (ECS) information and / or Domain Name System (DNS) server address information; the DNS server is used to select the edge application server; Based on the second information, a second request message is sent to the DNS server, the second request message being used to request the DNS server to select an edge application server to provide the first application service; if the second information includes the ECS information, the second request message includes the ECS information. Receive the Edge Application Service (EAS) address from the DNS server.

3. The method according to claim 2, characterized in that, The edge application service discovery function network element determines the second information based on the first information, including: The edge application service discovery function network element selects a target first function network element from the first function network elements based on the first information; Send a third request message to the target first functional network element, the third request message including the identification information of the first application service and / or the location information of the terminal; Receive the second information from the target first functional network element.

4. The method according to claim 3, characterized in that, The first request message includes the identification information of the first application service, and the first information includes the identification information of the application service managed by the first functional network element; The edge application service discovery function network element selects a target first function network element from the first function network elements based on the first information, including: The edge application service discovery function network element selects the first functional network element that obtains relevant information about the first application service from the first functional network elements as the target first functional network element, based on the identification information of the first application service and the first information.

5. The method according to claim 2, characterized in that, The first information includes the identification information of the application service managed by the first functional network element and the address information of the DNS server. The application service managed by the first functional network element includes the first application service. The edge application service discovery function network element determines the second information based on the first information, including: The edge application service discovery function network element determines the address information of the DNS server based on the location information of the terminal; or, The edge application service discovery function network element selects a first functional network element from the first functional network elements to obtain relevant information about the first application service, based on the identification information of the first application service, as the target first functional network element, and uses the address information of the DNS server obtained by the target first functional network element as the address information of the DNS server.

6. The method according to claim 5, characterized in that, The first information also includes the address range of the user plane function network element corresponding to the application service managed by the first functional network element; the method further includes: The edge application service discovery function network element determines the target first function network element from the first function network elements based on the edge application service (EAS) address and the address range of user plane function network elements in the first information. Send a first indication message to the session management function network element, the first indication message being used to identify the target first function network element.

7. The method according to claim 1, characterized in that, The edge application service discovery function network element determines the edge application service (EAS) address based on the first information, including: The edge application service discovery function network element determines the target first function network element from the first function network elements based on the first information; The edge application service discovery function network element sends an EAS query request to the target first function network element; The edge application service discovery function network element receives the EAS address from the target first function network element.

8. The method according to claim 7, characterized in that, The edge application service discovery function network element determines the target first function network element from the first function network elements based on the first information, including: The first information includes the identification information of the application service managed by the first functional network element. The edge application service discovery function network element determines the target first functional network element from the first functional network elements based on the identification information of the first application service and the correspondence between the identification information of the application service and the first functional network element; or; The first information includes the service area of ​​the first functional network element. The edge application service discovery function network element determines the target first functional network element from the first functional network elements based on the location information of the terminal and the correspondence between the service area of ​​the first functional network element and the first functional network element.

9. An application addressing method, characterized in that, The method includes: The first functional network element obtains Edge Application Service (EAS) deployment information; wherein, the first functional network element is used to select application service and / or user plane network elements; the EAS deployment information is used to determine the EAS of the application service; The first functional network element sends first information to the edge application service discovery function network element based on the EAS deployment information; wherein, the first information is used to indicate the relevant information of the application service obtained by the first functional network element.

10. The method according to claim 9, characterized in that, The method further includes: The first functional network element receives a third request message sent by the edge application service discovery function network element, wherein the third request message includes the identification information of the first application service and / or the location information of the terminal; The first functional network element determines the second information based on the third request information, wherein the second information includes extended Domain Name System Client Subnet (ECS) information or Domain Name System (DNS) server address information; the DNS server is used to select the edge application server; The first functional network element sends the second information to the edge application service discovery function network element.

11. The method according to claim 10, characterized in that, The third request message includes the identification information of the first application service and / or the location information of the terminal. The second information includes the address information of the DNS server. The first functional network element determines the second information based on the third request information, including: The first functional network element selects the address information of the DNS server managed by the first functional network element as the address information of the DNS server.

12. The method according to claim 9, characterized in that, The method further includes: Receive an EAS query request sent by the edge application service discovery function network element, wherein the EAS query request includes the identification information of the first application service, or the user's DNS query request message; The first functional network element determines the EAS address based on the EAS query request; The first functional network element sends the EAS address to the edge application service discovery function network element.

13. The method according to claim 12, characterized in that, The first functional network element determines the EAS address based on the EAS query request, including: The first functional network element determines the EAS address based on the application information recorded locally and the identifier information of the first application service in the EAS query request; or; The first functional network element sends a DNS query request message in the EAS query request to the local DNS server according to the local addressing policy, and further obtains the EAS address from the local DNS server.

14. The method according to claim 9, characterized in that, The method further includes: The first functional network element receives a session creation / modification request sent by the session management functional network element; Send the tunnel identifier of the user plane network element determined by the first functional network element to the session management function network element.

15. The method according to claim 9, characterized in that, The method further includes: The first functional network element receives the peer tunnel identifier of the user plane network element sent by the session management function network element; Send the peer tunnel identifier to the user plane network element.

16. The method according to any one of claims 1-15, characterized in that, The first information includes at least one of the following: the FQDN of the application service obtained by the first functional network element, the identifier of the first functional network element, the address information of the DNS server obtained by the first functional network element, the address range of the user plane functional network element corresponding to the application service obtained by the first functional network element, the service area of ​​the application service obtained by the first functional network element, the data network access identifier (DNAI) obtained by the first functional network element, the DNAI prefix obtained by the first functional network element, and the service area of ​​the first functional network element.

17. An application addressing method, characterized in that, The method includes: The session management function network element receives first indication information sent by the edge application service discovery function network element, wherein the first indication information is used to determine the target first function network element, and the first indication information includes at least one of the DNAI or DNAI prefix obtained by the target first function network element, the first function network element identifier corresponding to the target first function network element, and the edge application service EAS address. The session management function network element determines the target first function network element based on the first indication information; Send an L-PSA tunnel identifier request to the target first functional network element; Receive the tunnel identifier of L-PSA sent by the target first functional network element.

18. The method according to claim 17, characterized in that, The first indication information includes the DNAI or DNAI prefix obtained by the target first functional network element, and the method includes: The session management function network element sends the first indication information to the network function storage function (NRF) network element; The session management function network element receives the target first function network element determined by the NRF network element.

19. The method according to claim 17, characterized in that, The first indication information includes the identifier of the first functional network element corresponding to the target first functional network element, and the method includes: The session management function network element determines the target first function network element based on the first function network element identifier.

20. The method according to claim 17, characterized in that, The first indication information includes the EAS address, and the method includes: The session management function network element determines the target first function network element based on the UPF IP Range obtained from the locally configured first function network element.

21. The method according to claim 17, characterized in that, The method further includes: The session management function network element sends the terminal's location information to the edge application service discovery function network element.

22. A communication device, characterized in that, The communication device is applied to the edge application service discovery function network element, and the communication device includes: one or more functional units of the edge application service discovery function for supporting the communication device to perform the application addressing method as described in any one of claims 1-8.

23. A communication device, characterized in that, The communication device includes a processor and a communication interface, the processor and the communication interface being used to support the communication device in executing the application addressing method as described in any one of claims 1-8.

24. A communication device, characterized in that, The communication device is applied to a first functional network element, and the communication device includes: One or more functional units are configured to support the communication device in performing the application addressing method as described in any one of claims 9-16.

25. A communication device, characterized in that, The communication device includes a processor and a communication interface, the processor and the communication interface being used to support the communication device in executing the application addressing method as described in any one of claims 9-16.

26. A communication device, characterized in that, The communication device is applied to a session management function network element, and the communication device includes: One or more functional units are configured to support the communication device in performing the application addressing method as described in any one of claims 17-21.

27. A communication device, characterized in that, The communication device includes a processor and a communication interface, the processor and the communication interface being configured to support the communication device in executing the application addressing method as described in any one of claims 17-21.

28. A communication system, characterized in that, The communication system includes an edge application service discovery function network element for performing the method as described in any one of claims 1-8, and a first function network element for performing the method as described in any one of claims 9-16.

29. The communication system according to claim 28, characterized in that, The communication system also includes a terminal for sending a first request message and receiving an EAS address.

30. The communication system according to claim 28 or 29, characterized in that, The communication system further includes a session management function network element for performing the method as described in any one of claims 17-21.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-8, or cause the computer to perform the method as described in any one of claims 9-16, or cause the computer to perform the method as described in any one of claims 17-21.

32. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-8, or cause the computer to perform the method as described in any one of claims 9-16, or cause the computer to perform the method as described in any one of claims 17-21.

Images