Edge service acquisition method and device

Abstract

The present application provides an edge service acquisition method and apparatus. The method includes: a server discovery function network element receives a plurality of DNS response messages sent by a DNS server, the plurality of DNS response messages including address information of an EAS queried by a terminal device, and determines to send a DNS information report to a first core network element once for the plurality of DNS response messages according to first indication information. A signaling overhead generated when the server discovery function network element sends the DNS information report to the first core network element is reduced, so as to reduce the signaling overhead in the process of acquiring an edge service.

Description

[Technical Field]

[0001] The present application relates to the field of communications, and more particularly to edge service acquisition methods and apparatuses. [Background technology]

[0002] To use an edge service, a terminal device first needs to obtain the address information of an edge application server (EAS) by using a service discovery mechanism based on DNS. Currently, the terminal device performs the following steps to obtain the address information of the EAS: The terminal device sends a DNS query request including the identification information of the EAS to an edge application server discovery function (EASDF) network element to obtain the address information of the EAS. The EASDF sends the DNS query request to a DNS server to obtain a DNS response corresponding to the service, and sends a DNS information report to the SMF based on the response. The SMF then completes the establishment of a data plane path for the terminal device. Finally, the EASDF sends a DNS response including the address information of the EAS to the terminal device.

[0003] In current network elements, the same edge service may have more than one EAS identity. Therefore, when accessing a service, the terminal device sends multiple DNS query requests, and the EASDF sends multiple DNS query requests to a DNS server and receives multiple DNS responses. The multiple DNS responses trigger the EASDF to send multiple DNS information reports to the SMF, and the SMF completes the establishment of a data plane path for the terminal device accordingly. Because the EASs in the returned DNS responses usually belong to the same data network (DN), the SMF only needs to complete the establishment of a data plane path for the terminal device once. Therefore, the existing edge service acquisition method may result in a waste of signaling resources. Summary of the Invention

[0004] The present application provides an edge service acquisition method and apparatus, so as to reduce signaling overhead in the process of acquiring edge services.

[0005] According to a first aspect, there is provided an edge service acquisition method, the method including: receiving, by a server discovery function network element, a plurality of DNS response messages sent by a DNS server, the plurality of DNS response messages including address information of an EAS queried by a terminal device; and determining, by the server discovery function network element based on first indication information, to send a DNS information report to a first core network element once for the plurality of DNS response messages.

[0006] According to the method provided in this embodiment of the present application, a server discovery function network element may receive multiple DNS response messages including address information of multiple EASs corresponding to the same data network, and the server discovery function network element may determine, based on the first indication information, to send a DNS information report to the first core network element only once for the multiple DNS response messages, thereby reducing signaling overhead generated when address information of multiple EASs is queried.

[0007] Referring to the first aspect, in some implementations of the first aspect, the first core network element is a session management function network element, and the server discovery function network element is an edge application server discovery function network element.

[0008]

[0013] Referring to the first aspect, in some implementations of the first aspect, the first indication information includes correspondence information between a network address and an identification information of a data network. The server discovery function network element determines that the queried EAS corresponds to the same data network identification information based on the first indication information and the address information of the EAS in the plurality of DNS response messages, and the server discovery function network element reports a DNS information report corresponding to one of the plurality of DNS response messages to the first core network element once.

[0009] With reference to the first aspect, in some implementations of the first aspect, a server discovery function network element buffers multiple DNS response messages, the server discovery function network element receives second instruction information sent by a first core network element, the second instruction information including handling rules for the multiple DNS response messages, and the server discovery function network element determines to send the multiple DNS response messages to a terminal device based on the second instruction information.

[0010] With reference to the first aspect, in some implementations of the first aspect, before the server discovery function network element receives the plurality of DNS response messages sent by the DNS server, the method further includes receiving, by the server discovery function network element, first indication information sent by the first core network element.

[0011] With reference to the first aspect, in some implementations of the first aspect, the data network identification information is one of the following: the data network access identifier DNAI of the data network, and Data Network Name DNN It includes at least one of the following information.

[0012] According to a second aspect, an edge service acquisition method is provided, the method including: sending first instruction information by a first core network element to a server discovery function network element, the first instruction information instructing the server discovery function network element to send a DNS information report to the first core network element once for a plurality of DNS response messages, the plurality of DNS response messages including address information of an EAS queried by a terminal device; and receiving the DNS information report by the first core network element.

[0013] According to the method provided in this embodiment of the present application, a server discovery function network element can response Messages can be received from multiple DNS servers. response Messages can be sent to multiple EASs that support the same data network. address The server discovery function network element may include the first 1 Based on the instruction information, multiple DNS response It may be decided to send the DNS information report to the first core network element only once for the message, which may reduce the signaling overhead generated when address information of multiple EASs is queried.

[0014] Referring to the second aspect, in some implementations of the second aspect, the first indication information includes correspondence information between a network address and identification information of a data network.

[0015] With reference to the second aspect, in some implementations of the second aspect, the first core network element sends second instruction information to the server discovery function network element, and the second instruction information includes handling rules for multiple DNS response messages, whereby the server discovery function network element determines to send multiple DNS response messages to the terminal device based on the second instruction information.

[0016] Referring to the second aspect, in some implementations of the second aspect, the identification information of the data network is one of the following: the data network access identifier DNAI of the data network, and Data Network Name DNN It includes at least one of the following information.

[0017] According to a third aspect, there is provided an edge service acquisition method, the method including: receiving, by a server discovery function network element, a plurality of DNS query messages from a terminal device, the plurality of DNS query messages being for querying address information of an EAS; and determining, by the server discovery function network element based on third instruction information, to send a DNS information report to a first core network element once for the plurality of DNS query messages.

[0018] Referring to the third aspect, in some implementations of the third aspect, the third instruction information includes correspondence information between the identification information of the EAS and the identification information of the data network. 3Based on the indication information, it is determined that the multiple DNS query messages correspond to the same data network identification information, and the server discovery function network element reports a DNS information report corresponding to one of the multiple DNS query messages to the first core network element once.

[0019] With reference to the third aspect, in some implementations of the third aspect, the server discovery function network element buffers multiple DNS query messages, the server discovery function network element receives fourth instruction information from the first core network element, the fourth instruction information includes handling rules for the multiple DNS query messages, and the server discovery function network element determines to send the multiple DNS query messages to the DNS server based on the fourth instruction information.

[0020] Referring to the third aspect, in some implementations of the third aspect, the server discovery function network element receives third indication information sent by the first core network element.

[0021] Referring to the third aspect, in some implementations of the third aspect, the EAS identification information is: EAS Uniform Resource Identifier URI, EAS instance identifier, or EAS absolute domain name FQDN It includes at least one of the following information.

[0022] With reference to the third aspect, in some implementations of the third aspect, the identification information of the data network is one of the following: Data Network Access Identifier DNAI, and Data Network Name DNN It includes at least one of the following information.

[0023] According to a fourth aspect, an edge service acquisition method is provided, the method including: sending third instruction information by a first core network element to a server discovery function network element, the third instruction information instructing the server discovery function network element to send a DNS information report to the first core network element once for multiple DNS query messages, the multiple DNS query messages being for querying address information of an EAS; and receiving the DNS information report by the first core network element.

[0024] Referring to the fourth aspect, in some implementations of the fourth aspect, the third instruction information includes correspondence information between identification information of the EAS and identification information of the data network.

[0025] With reference to the fourth aspect, in some implementations of the fourth aspect, the first core network element sends fourth instruction information to the server discovery function network element, the fourth instruction information includes handling rules for the multiple DNS query messages, and the handling rules include constructing a client subnet option for the multiple DNS query messages.

[0026] Referring to the fourth aspect, in some implementations of the fourth aspect, the EAS identification information is one of the following: EAS Uniform Resource Identifier URI, EAS instance identifier, or EAS absolute domain name FQDN It includes at least one of the following information.

[0027] With reference to the fourth aspect, in some implementations of the fourth aspect, the identification information of the data network is one of the following: Data Network Access Identifier DNAI, and Data Network Name DNN It includes at least one of the following information.

[0028] According to a fifth aspect, an edge service acquisition apparatus is provided, the apparatus including: a transceiver unit configured to receive a plurality of DNS response messages sent by a DNS server, the plurality of DNS response messages including address information of an EAS queried by a terminal device; and a processing unit that determines, based on first indication information, to send a DNS information report to a first core network element once for the plurality of DNS response messages.

[0029] With reference to the fifth aspect, in some implementations of the fifth aspect, the first core network element is a session management function network element.

[0030]

[0013] With reference to the fifth aspect, in some implementations of the fifth aspect, the first indication information includes correspondence information between a network address and an identification information of a data network. The processing unit is specifically configured to determine, based on the first indication information and the plurality of DNS response messages, that the queried EASs correspond to the same data network identification information. The transceiver unit is specifically configured to report, once to the first core network element, a DNS information report corresponding to one of the plurality of DNS response messages.

[0031] With reference to the fifth aspect, in some implementations of the fifth aspect, the apparatus further includes a storage unit configured to buffer the plurality of DNS response messages. The transceiver unit is specifically configured to receive second instruction information sent by the first core network element, the second instruction information including handling rules for the plurality of DNS response messages. The processing unit is specifically configured to determine, based on the second instruction information, to send the plurality of DNS response messages to the terminal device.

[0032] With reference to the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to receive first indication information sent by the first core network element.

[0033] With reference to the fifth aspect, in some implementations of the fifth aspect, the data network identification information is one of the following: the data network access identifier DNAI of the data network, and Data Network Name DNN It includes at least one of the following information.

[0034] According to a sixth aspect, an edge service acquisition apparatus is provided, the apparatus including: a transceiver unit configured to send first instruction information to a server discovery function network element, the first instruction information instructing the server discovery function network element to send a DNS information report to a first core network element once for a plurality of DNS response messages, the plurality of DNS response messages including address information of an EAS queried by a terminal device; and the transceiver unit is further configured to receive the DNS information report.

[0035] Referring to the sixth aspect, in some implementations of the sixth aspect, the first indication information includes correspondence information between a network address and identification information of a data network.

[0036] With reference to the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to send second instruction information to the server discovery function network element, where the second instruction information includes handling rules for the multiple DNS response messages, whereby the server discovery function network element determines to send the multiple DNS response messages to the terminal device based on the second instruction information.

[0037] With reference to the sixth aspect, in some implementations of the sixth aspect, the identification information of the data network is one of the following: the data network access identifier DNAI of the data network, and Data Network Name DNN It includes at least one of the following information.

[0038] According to a seventh aspect, an edge service acquisition apparatus is provided, the apparatus including: a transceiver unit configured to receive a plurality of DNS query messages from a terminal device, the plurality of DNS query messages being for querying address information of an EAS; and a processing unit configured to determine, based on third indication information, to send a DNS information report to a first core network element once for the plurality of DNS query messages.

[0039] Referring to the seventh aspect, in some implementations of the seventh aspect, the third instruction information includes correspondence information between the identification information of the EAS and the identification information of the data network. 3 The transceiver unit is particularly configured to determine, based on the indication information, that the multiple DNS query messages correspond to the same data network identification information. The transceiver unit is further configured to report, once to the first core network element, a DNS information report corresponding to one of the multiple DNS query messages.

[0040] With reference to the seventh aspect, in some implementations of the seventh aspect, the apparatus further includes a storage unit configured to buffer the plurality of DNS query messages. The transceiver unit is further configured to receive fourth instruction information sent by the first core network element, the fourth instruction information including handling rules for the plurality of DNS query messages. The processing unit is specifically configured to determine, based on the fourth instruction information, to send the plurality of DNS query messages to the DNS server.

[0041] With reference to the seventh aspect, in some implementations of the seventh aspect, the transceiver unit is specifically configured to receive third indication information sent by the first core network element.

[0042] Referring to the seventh aspect, in some implementations of the seventh aspect, the identification information of the EAS is one of the following: EAS Uniform Resource Identifier URI, EAS instance identifier, or EAS absolute domain name FQDN It includes at least one of the following information.

[0043] With reference to the seventh aspect, in some implementations of the seventh aspect, the identification information of the data network is one of the following: Data Network Access Identifier DNAI, and Data Network Name DNN It includes at least one of the following information.

[0044] According to an eighth aspect, an edge service acquisition apparatus is provided, the apparatus including: a transceiver unit configured to send third instruction information to a server discovery function network element, the third instruction information instructing the server discovery function network element to send a DNS information report to a first core network element once for a plurality of DNS query messages, the plurality of DNS query messages being for querying address information of an EAS; and the transceiver unit is further configured to receive the DNS information report.

[0045] Referring to the eighth aspect, in some implementations of the eighth aspect, the third instruction information includes correspondence information between identification information of the EAS and identification information of the data network.

[0046] With reference to the eighth aspect, in some implementations of the eighth aspect, the transceiver unit is further configured to send fourth instruction information to the server discovery function network element, the fourth instruction information including handling rules for the multiple DNS query messages, and the handling rules including constructing a client subnet option for the multiple DNS query messages.

[0047] Referring to the eighth aspect, in some implementations of the eighth aspect, the identification information of the EAS is one of the following: EAS Uniform Resource Identifier URI, EAS instance identifier, or EAS absolute domain name FQDN It includes at least one of the following information.

[0048] With reference to the eighth aspect, in some implementations of the eighth aspect, the identification information of the data network is one of the following: Data Network Access Identifier DNAI, and Data Network Name DNN It includes at least one of the following information.

[0049] According to a ninth aspect, there is provided an edge service acquisition device. The device may be a server discovery function network element, or the device may be a chip. The device has a function of implementing the server discovery function network element in the first aspect, the third aspect, or any one of possible implementations of the first aspect or the third aspect. The function may be implemented by hardware, or may be implemented by the hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0050] According to a tenth aspect, there is provided an edge service acquisition device. The device may be a first core network element, for example, a session management function network element, or the device may be a chip. The device has a function of implementing the first core network element in the second aspect, the fourth aspect, or any one of possible implementations of the second aspect or the fourth aspect. The function may be implemented by hardware, or may be implemented by the hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0051] According to an eleventh aspect, an edge service acquisition device is provided, the edge service acquisition device including a processor. The processor may be coupled to a memory and configured to execute instructions in the memory to implement the server discovery function network element of the first aspect, the third aspect, or any one of possible implementations of the first aspect or the third aspect. Optionally, the device further includes the memory. Optionally, the device further includes a communication interface, the processor being coupled to the communication interface.

[0052] According to a twelfth aspect, there is provided an edge service acquisition apparatus, the edge service acquisition apparatus including a processor. The processor may be coupled to a memory and configured to execute instructions in the memory to implement the first core network element of the second aspect, the fourth aspect, or any one of possible implementations of the second aspect or the fourth aspect. Optionally, the apparatus further includes the memory. Optionally, the apparatus further includes a communication interface, the processor being coupled to the communication interface.

[0053] In implementation, the device is a first core network element, such as an SMF. When the device is an SMF, the communication interface may be a transceiver or an input / output interface.

[0054] In another implementation, the device is a chip located in an SMF network element. When the device is a chip located in an SMF network element, the communication interface may be an input / output interface.

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

[0056] According to a thirteenth aspect, there is provided a processor, comprising an input circuit, an output circuit, and a processing circuit, the processing circuit configured to receive a signal via the input circuit and to transmit a signal via the output circuit, such that the processor can perform a method according to any one of the first to fourth aspects or possible implementations of the first to fourth aspects.

[0057] In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, etc. The input signal received by the input circuit may be received and input by a receiver, the signal output by the output circuit may be output by a transmitter and transmitted by the transmitter, the input circuit and the output circuit may be the same circuit, and the circuit may be used as an input circuit and an output circuit at different times. The specific implementation of the processor and various circuits is not limited to the embodiments of the present application.

[0058] According to a fourteenth aspect, there is provided an apparatus, comprising a processor and a memory, wherein the processor is configured to read instructions stored in the memory and may receive signals by using the receiver and transmit signals by using the transmitter, to perform a method according to any one of the first to fourth aspects or possible implementations of the first to fourth aspects.

[0059] Optionally, there are one or more processors and one or more memories.

[0060] Optionally, the memory may be integral with the processor, or the memory and processor may be located separately.

[0061] In a specific implementation process, the memory may be a non-transitory memory such as a read-only memory (ROM). The memory and the processor may be integrated into one chip, or may be separately arranged on different chips. The type of memory and the way in which the memory and the processor are arranged are not limited in this embodiment of the present application.

[0062] It should be understood that a related data exchange process, such as transmitting instruction information, may be a process of outputting instruction information from a processor, and receiving capability information may be a process of receiving input capability information by a processor. Specifically, data output by a processor may be output to a transmitter, and input data received by a processor may be from a receiver. The transmitter and receiver may be collectively referred to as a transceiver.

[0063] The device of the fourteenth aspect may be a chip. The processor may be implemented using hardware or software. If the processor is implemented using hardware, the processor may be a logic circuit, an integrated circuit, etc. If the processor is implemented using software, the processor may be a general-purpose processor and is implemented by reading software code stored in a memory. The memory may be integrated into the processor or may exist separately from the processor.

[0064] According to a fifteenth aspect, there is provided a computer program product, which includes a computer program (which may also be referred to as code or instructions), which, when executed, causes a computer to carry out a method according to any one of the first to fourth aspects or possible implementations of the first to fourth aspects.

[0065] According to a sixteenth aspect, there is provided a computer-readable medium having stored thereon a computer program (also referred to as code or instructions), which, when executed on a computer, enables the computer to carry out a method according to any one of the first to fourth aspects or possible implementations of the first to fourth aspects.

[0066] According to a seventeenth aspect, a chip system is provided, comprising a processor configured to call a computer program from a memory and execute the computer program, whereby a device in which the chip system is installed executes a method according to any one of the first to fourth aspects or possible implementations of the first to fourth aspects. [Brief explanation of the drawings]

[0067] [Figure 1] FIG. 1 is a diagram of a system architecture to which embodiments of the present application are applied. [Figure 2] FIG. 1 is a schematic diagram of an edge service architecture according to an embodiment of the present application. [Figure 3] 3 is a schematic flow chart of an existing edge service acquisition method 300. [Figure 4] 4 is a schematic flow chart of an edge service acquisition method 400 according to the present application. [Figure 5] 5 is a schematic flow chart of an edge service acquisition method 500 according to the present application. [Figure 6] 6 is a schematic flow chart of a method 600 for obtaining edge services in accordance with the present disclosure. [Figure 7] 7 is a schematic flow chart of a method 700 for obtaining edge services in accordance with the present disclosure. [Figure 8] 1 is a schematic block diagram of an edge service acquisition device 100 according to the present application. [Figure 9] 1 is a schematic block diagram of an edge service acquisition device 200 according to the present application. DETAILED DESCRIPTION OF THE INVENTION

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

[0069] The wireless communication systems described in the embodiments of this application include, but are not limited to, a Global System for Mobile Communications (GSM) system, a Long Term Evolution (LTE) frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, a LTE system, a Long Term Evolution-Advanced (LTE-Advanced, LTE-A) system, a next generation communication system (e.g., a 6G communication system), a system that integrates multiple access systems, or an evolved system.

[0070] The technical solutions provided in this application may further be applied to machine type communication (MTC), Long Term Evolution (LTE) for M2M (LTE-M) communication, device to device (D2D) networks, machine to machine (M2M) networks, Internet of Things (IoT) networks, or other networks. IoT networks may include, for example, Internet of Vehicles. Communication modes in Internet of Vehicle systems are collectively referred to as Vehicle to X (V2X, where X can represent anything). For example, V2X may include vehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I) communications, vehicle-to-pedestrian (V2P) communications, or vehicle-to-network (V2N) communications.

[0071] The terminal device in the present embodiment may include various access terminals, mobile devices, user terminals, or user equipments having wireless communication capabilities. For example, the terminal device may be user equipment (UE) such as a mobile phone, a tablet computer (Pad), a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal device. The terminal device may alternatively be a wireless terminal in industrial control, a machine type communication (MTC) terminal, customer premises equipment (CPE), a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a mobile or computing device with wireless communication capabilities, other processing device connected to a wireless modem, an in-vehicle device, or a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN).

[0072] With reference to FIG. 1 and FIG. 2, the following describes in detail the network system architecture and the edge service architecture within the architecture in the embodiment of the present application.

[0073] 1 is a schematic block diagram of an example of a wireless communication system architecture to which the present application is applied. As shown in the figure, the system architecture may specifically include the following network elements:

[0074] 1. (Radio) Access Network (RAN): RAN is an access network that implements network access functions based on wireless communication technology. The radio access network manages radio resources, provides access services to terminals, and can complete the transfer of control signals and user data between terminals and the core network.

[0075] The radio access network device involved in this application may be a device with a radio transceiver function. The radio access network device may be a device that provides wireless communication function services and is typically located on a network side. Radio access network devices include, but are not limited to, a next-generation Node B (gNodeB, gNB) in a fifth-generation (5G) communication system, a next-generation Node B in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, an access node in a Wi-Fi system, an evolved Node B (eNB) in an LTE system, a radio network controller (RNC), a Node B (NodeB, NB), a base station controller (BSC), a home Node B (e.g., home evolved NodeB or home NodeB, HNB), a base band unit (BBU), a transmission reception point (TRP), a transmitting point (TP), and a base transceiver station (BTS). In a network structure, an access network device may include a central unit (CU) node, a distributed unit (DU) node, a RAN device including a CU node and a DU node, or a RAN device including a CU control plane node, a CU user plane node, and a DU node. An access network device may serve a cell. User equipment communicates with a base station over transmission resources (e.g., referred to as frequency domain resources or frequency spectrum resources) used for the cell. A cell may be a cell corresponding to a base station. A cell may belong to a macro base station or a base station corresponding to a small cell.The small cells herein may include metro cells, micro cells, pico cells, femto cells, etc. These small cells are characterized by small coverage and low transmission power and are applied to providing high-speed data transmission services. The radio access network devices may be macro base stations, micro base stations, or indoor base stations, or may be relay nodes or donor nodes, devices that provide wireless communication services to user equipment in a V2X communication system, radio controllers in cloud radio access network (CRAN) scenarios, relay stations, in-vehicle devices, wearable devices, network devices in future evolved networks, etc. The specific technologies and specific device configurations used by the radio access network devices are not limited by the embodiments of the present application.

[0076] 2. User plane function (UPF) network element: configured to perform packet routing and forwarding, quality of service (QoS) processing for user plane data, etc. User data can be transmitted to a data network (DN) through this network element.

[0077] 3. Data network (DN) 140: A network that carries out data transmission.

[0078] 4. Access and mobility management function network element (AMF): Mainly used for mobility management, access management, etc. The AMF is configured to implement functions such as lawful interception or access authentication / authorization other than session management within the functionality of the mobility management entity (MME).

[0079] 5. Session management function network element (SMF) 160: Mainly used for session management, terminal device internet protocol (IP) address allocation and management, selection of manageable user plane functions, termination of interface towards policy control and modification functions, downlink data notification, etc.

[0080] 6. Network Exposure Function (NEF) 180: Primarily configured to securely expose services, capabilities, etc. provided by 3rd Generation Partnership Project (3GPP) network functions.

[0081] 7. Policy control function network element (PCF): A unified policy framework that governs network behavior and provides policy rule information, etc. to control plane function network elements (e.g., AMF or SMF network elements).

[0082] 8. Application Function Network Element (AF) 1110: Configured to support application influence on traffic routing, access network publishing function network elements, or interact with a policy framework for policy control, etc.

[0083] Furthermore, the above network architecture further includes a network slice selection function (NSSF) configured to manage information about network slices, and a network repository function (NRF) configured to store network function profiles of NF entities and their supported services and support functions such as service discovery and network element entity discovery.

[0084] In this network architecture, the N2 interface is an interface between the RAN and the AMF network element and is used for transmitting non-access stratum (NAS) messages, etc.; the N3 interface is an interface between the RAN and the UPF network element and is used for transmitting user plane data, etc.; and the N4 interface is an interface between the SMF network element and the UPF network element and is used for transmitting information such as tunnel identification information, data buffer indication information, and downlink data notification messages for the N3 connection.

[0085] It may be understood that the above network elements or functions may be network elements within a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0086] For ease of explanation, the following is described by using an example in which the access management function network element in this application is an AMF network element, the session management network element is an SMF network element, and the policy control network element is a PCF network element.

[0087] Furthermore, an AMF network element is abbreviated as AMF, an SMF network element is abbreviated as SMF, and a PCF network element is abbreviated as PCF. Specifically, in the following description of this application, all AMFs may be replaced by access management function network elements, all SMFs may be replaced by session management network elements, and all PCFs may be replaced by policy control network elements.

[0088] For ease of explanation, in this application, the edge service acquisition method is described by using an example in which the device is an AMF entity, an SMF entity, or a PCF entity. For an implementation method in which the device is a chip in an AMF entity, a chip in an SMF entity, or a chip in a PCF entity, please refer to the specific description of the method in which the device is an AMF entity, an SMF entity, or a PCF entity. Details will not be repeated.

[0089] In the network architecture shown in Figure 1, the UE is connected to the AMF via the N1 interface, the RAN is connected to the AMF via the N2 interface, and the RAN is connected to the UPF via the N3 interface.

[0090] The UPFs are connected to each other through the N9 interface, and the UPFs are interconnected to the data network (DN) through the N6 interface.

[0091] The SMF controls the UPF through the N4 interface.

[0092] In Figure 1, N1, N2, N3, N4, etc. are interface sequence numbers. For the meaning of these interface sequence numbers, please refer to the meaning defined in the current standard protocol, which is not limited here.

[0093] It should be understood that the above-described network architectures applied to the embodiments of the present application are merely examples of network architectures described from the perspective of conventional point-to-point architectures and service architectures, and the network architectures applied to the embodiments of the present application are not limited thereto. Any network architecture capable of implementing the functions of the above-described network elements is applicable to the embodiments of the present application.

[0094] 2 is a schematic diagram of a system architecture or scenario in which the embodiments of the present application are applied. The system can also be seen as a support for edge computing in the above network architecture.

[0095] As shown in FIG. 2, the system architecture includes an edge application server (EAS). The EAS is an edge application server deployed in an edge data network (EDN) and may also be referred to as an edge application (server), application instance, edge application instance, multi-access edge computing (MEC) application (server), EAS function, etc. An edge application is also referred to as an "application instance" and is specifically an instance of a server application program (e.g., social media software, augmented reality (AR), or virtual reality (VR)) deployed and executed in an EDN. One or more EASs may be deployed for one application in one or more EDNs. EASs deployed and executed in different EDNs may be considered different EASs for one application. The EAS may share one or more domain names or may use a different domain name from that of the application deployed on the cloud, which may be a fully qualified domain name (FQDN) or a single anycast internet protocol (IP) address or may use different IP addresses.

[0096] The edge data network may be a local data network. The local DN can be identified by a data network access identifier (DNAI) and a data network name (DNN), and is a logical network concept.

[0097] The system architecture further includes an edge application server discovery function (EASDF) network element. The EASDF has the following functions: Registering with the NRF for EASDF discovery and selection, receiving DNS message handling rules from the SMF, exchanging DNS messages with the UE, and processing domain name system (DNS) messages based on the instructions of the SMF, including forwarding DNS messages to a central DNS (C-DNS) resolver / server or a local DNS (L-DNS) resolver / server for DNS queries. Furthermore, the EASDF may further establish a user plane connection to the UPF via the N6 interface to carry DNS signaling exchanged with the UE. The EASDF may be directly connected to one or more local DNs. A DNS server (resolver / server) may be deployed locally by the 5GC operator or a third party that contains the local DNs, and is configured to resolve the UE's DNS queries to the appropriate EAS IP addresses within the local DNs. The DNS server may be deployed at different locations in the network as a central DNS (C-DNS) server or a local DNS (L-DNS) server. The L-DNS may or may not be connected to the C-DNS, depending on the deployment.

[0098] When a terminal device needs to perform service transmission, the SMF entity can establish multiple protocol data unit (PDU) sessions to the same or different DNs. If multiple PDU sessions to the same DN are established, different UFPs must be used. The SMF can control PDU data routing so that a PDU session can have multiple N6 interfaces. The UPF connected to each N6 interface is called a PDU session anchor (PSA) UPF. Each PSA provides a different path to the same DN.

[0099] For different PDU sessions, the SMF may insert an uplink classifier (UL CL) into the data transmission path of each PDU session. The UL CL functionality is provided by the UFP to forward data packets that satisfy service filtering rules to a specified path. If a UL CL is inserted into the data channel of a PDU session, the PDU session may have multiple PDU session anchors, providing multiple different paths to the same DN. In other words, the function of the UL CL may be to transmit uplink data to different PSAs and to combine downlink data to the UE. Alternatively, data corresponding to all PSAs may be aggregated into a common UPF, which has the function of a branching point (BP). The branching point forwards uplink data to different PSAs in the uplink direction and combines downlink data from the PSAs in the downlink direction.

[0100] In the system architecture shown in Figure 2, UPF (UL CL / BP) may correspond to a UPF that provides UL CL functionality or a common UPF. Specifically, the UPF may transmit uplink data to different PSAs, such as UPF (PSA2) and UPF (PSA1), and combine downlink data to the UE.

[0101] To use an edge application, the terminal device needs to obtain the IP address of the EAS by using a DNS-based service discovery mechanism. As shown in Figure 3, the terminal device can obtain the IP address of the EAS in the following steps:

[0102] S301: Execute a process to establish a PDU session.

[0103] The process of establishing a PDU session includes establishing a session of a user plane path between the UE and the UPF. The specific procedure is included in the prior art and will not be described in detail here.

[0104] During the process of establishing the S302.PDU session, the SMF selects the EASDF.

[0105] S303.SMF sends a DNS context creation request (Neasdf_DNSContext_Create Request) to the selected EASDF. The DNS context creation request may include the IP address of the terminal device, a callback URI, and a DNS message handling rule. The EASDF may create a DNS context for the PDU session based on the request message and store the UE's IP address, callback URI, and DNS message handling rule in the context.

[0106] Accordingly, at S304, the EASDF sends a DNS context creation response to the SMF.

[0107] S305.SMF sends a DNS context update request (Neasdf_DNSContext_Update Request) to EASDF.

[0108] The update request message may be triggered by the mobility of the terminal device, or the update request message may be triggered by the insertion or removal of a PSA. The update request message may include an EASDF context ID and a DNS message handling rule.

[0109] Accordingly, at S306, the EASDF sends a DNS context update response to the SMF.

[0110] S310. The terminal device sends a DNS query message to the EASDF.

[0111] S320. If the DNS query message matches the DNS message handling rules for reporting, the EASDF sends a DNS message report to the SMF by invoking the DNS context notify request (Neasdf_DNSContext_Notify Request).

[0112] S330.SMF sends a DNS context notify response (Neasdf_DNSContext_Notify Response) to EASDF.

[0113] Optionally, if the DNS message handling rules for the FQDN received in the report need to be updated, for example, if update information is provided to construct EDNS Client Subnet option (ECS) information, the SMF sends a DNS context update request (Neasdf_DNSContext_Update Request) to the EASDF in S340. The update request may include the DNS message handling rules.

[0114] ECS (EDNS-Client-Subnet) is a new protocol supported by DNS services. According to this protocol, the user's IP address is added to the DNS request packet. In this way, the DNS server can return the IP address of a closer server to the user based on the user's IP address instead of the recursive server's IP address, allowing the user to access the closer server.

[0115] Correspondingly, at S350, the EASDF sends a DNS context update response (Neasdf_DNSContext_Update Response) to the SMF.

[0116] S350.EASDF processes received DNS query messages.

[0117] The EASDF may add an ECS option to the DNS query message and send the DNS query message to the C-DNS server. Alternatively, the EASDF may send the DNS query message to a local DNS server.

[0118] S360.EASDF sends a DNS query request to the DNS server.

[0119] S370.EASDF receives the DNS response sent by the DNS server.

[0120] S380.EASDF sends the DNS message report to SMF by triggering a DNS context notify request (Neasdf_DNSContext_Notify Request).

[0121] S390.SMF sends a DNS context notify response (Neasdf_DNSContext_Notify Response) to EASDF.

[0122] Optionally, at S3100, the SMF may further insert a UL CL / BP.

[0123] Based on the EAS information (e.g., EAS IP address) received from the EASDF, the SMF may determine the DNAI and the DNAI's associated N6 traffic routing information. The SMF entity may perform selection and insertion of the UL CL / BP and local PSA to complete the establishment of the data plane path for the UE.

[0124] After the data plane path for the UE is established, at S3110, the SMF may send a DNS context update request (Neasdf_DNSContext_Update Request) including DNS message handling rules to the EASDF.

[0125] Accordingly, at S3120, the EASDF sends a DNS context update response (Neasdf_DNSContext_Update Response) to the SMF.

[0126] S3130.EASDF sends a DNS response message to the terminal device.

[0127] In current network services, the same edge service may call more than one FQDN. Therefore, when accessing an edge service, a terminal device simultaneously sends multiple DNS query requests, and the EASDF sends multiple DNS query requests to the DNS server and receives multiple DNS responses. The multiple DNS responses trigger the EASDF to send multiple DNS message reports to the SMF, which then selects a DNAI and inserts a UL CL / BP. However, because the EASs in the returned DNS responses usually belong to the same DN, there is a possibility of wasting signaling resources when the EASDF sends multiple DNS messages to the SMF.

[0128] In view of this, the present application provides an edge service acquisition method, in which a server discovery function network element can determine a specific message transmission policy based on indication information, so as to reduce signaling overhead in acquiring an edge service.

[0129] The following describes in detail the method according to the embodiments of the present application with reference to the accompanying drawings. It should be noted that in the following process of describing the embodiments with reference to the accompanying drawings, the drawings are only for ease of understanding and should not constitute any limitation on the present application. The names of the network elements are defined only to distinguish different functions and should not constitute any limitation on the present application. The present application excludes the possibility of defining other network elements that implement the same or similar functions.

[0130] 4 is a schematic block diagram of an edge service acquisition method 400 according to the present application. The method includes at least the following steps:

[0131] S410. The server discovery function network element receives multiple DNS responses sent by the DNS server.

[0132] The server discovery function network element may include an EASDF network element. The plurality of DNS response messages are responses to the plurality of DNS queries (DNS Query) sent by the terminal device. The plurality of DNS response messages include address information of the EAS queried by the terminal device.

[0133] The address information of the EAS may include address information of multiple EASs for the same edge service, or the address information of the EAS may be address information of multiple EASs corresponding to different edge services.

[0134] S420. The server discovery function network element determines, based on the first indication information, to send a DNS information report to the first core network element once for the multiple DNS response messages.

[0135] The server discovery function network element determining, based on the first indication information, to send a DNS information report to the first core network element once for the plurality of DNS response messages may include the server discovery function network element reporting, based on the first indication information, a DNS information report corresponding to one of the plurality of DNS response messages to the first core network element, where the DNS response message may include, for example, a first DNS response message received by the server discovery function network element. The first core network element may be a session management function network element, and the DNS information report is for triggering the session management function network element to send handling rules for the plurality of DNS response messages.

[0136] The first indication information may include a correspondence between the network address information and the data network, for example, the first indication information may include a correspondence table between the network address information and the identification information of the data network.

[0137] The network address information may be an IP address, and the identification information of the data network may include a data network access identifier DNAI and / or a data network name DNN. It should be understood that the same edge service may correspond to the identification information of different EASs, and the identification information of different EASs may correspond to the identification information of the same data network. The data network may be a local DN.

[0138] It should be noted that the above are only examples of identification information and should not constitute any limitation to the present application, and the present application does not exclude that the identification information may be any other information that can be used to obtain edge server address information.

[0139] In a possible implementation, the server discovery function network element receives multiple DNS response messages, and the multiple DNS response messages include address information of EASs. The server discovery function network element can determine a data network corresponding to the address information of the EAS based on the correspondence between the address information of the EASs and the network address information and the data network. If the address information of the EASs corresponds to the same data network, the server discovery function network element determines to report a DNS information report once for the multiple DNS response messages.

[0140] For example, the first indication information may be configured in the server discovery function network element, or the server discovery function network element may receive the first indication information sent by the first core network element. For example, the server discovery function network element may receive the first indication information in a PDU session establishment process. The server discovery function network element may receive a DNS context creation request (Neasdf_DNSContext_Create Request) sent by the SMF, where the request message includes the first indication information. Alternatively, the server discovery function network element may receive the first indication information in a DNS context update procedure. For example, the EASDF may receive a DNS context update request (Neasdf_DNSContext_Update Request) sent by the SMF, where the update request includes the first indication information. Alternatively, the EASDF may receive the first indication information at any time before the terminal device sends a DNS query request.

[0141] Optionally, the method may further include S430: The server discovery function network element buffers the plurality of DNS response messages.

[0142] The server discovery function network element may buffer the plurality of DNS response messages, and then, based on the DNS handling rule sent by the first core network element, the server discovery function network element may decide to send all or some of the plurality of DNS response messages to the terminal device.

[0143] Optionally, the method may further include S440, in which the server discovery function network element receives second instruction information sent by the first core network element, and the second instruction information includes DNS handling rules for the plurality of DNS response messages.

[0144] For example, the DNS handling rule may instruct the server discovery network element to send multiple buffered DNS response messages to the terminal device, or may instruct the server discovery network element to send a DNS response message for a specified EAS address range to the terminal device. Alternatively, the DNS handling rule may instruct the server discovery network element not to buffer the first DNS response message following multiple DNS response messages, where the first DNS response message is also a response to multiple DNS query request messages sent by the terminal device. Alternatively, the DNS handling rule may instruct the server discovery network element to discard the first DNS response message following multiple DNS response messages.

[0145] S450. The server discovery function network element sends a plurality of DNS response messages to the terminal device.

[0146] According to the method provided in this embodiment of the present application, a server discovery function network element may receive multiple DNS response messages including address information of multiple EASs corresponding to the same data network, and the server discovery function network element may determine, based on the first indication information, to send a DNS information report to the first core network element only once for the multiple DNS response messages, thereby reducing signaling overhead generated when address information of multiple EASs is queried.

[0147] 5 is a schematic block diagram of an edge service acquisition method 500 according to the present application. The method includes at least the following steps:

[0148] S510. A server discovery function network element receives a plurality of DNS Query messages sent by terminal devices.

[0149] The multiple DNS query messages are used by the terminal device to obtain address information of EASs for the edge service, and the address information of the EASs may include address information of multiple EASs for the same edge service, or the address information of the EASs may be address information of multiple EASs corresponding to different edge services.

[0150] S520. The server discovery function network element determines, according to the third indication information, to send a DNS information report to the first core network element once for the multiple DNS query messages.

[0151] The server discovery function network element determining, based on the third indication information, to send a DNS information report to the first core network element once for the plurality of DNS query messages may include the server discovery function network element reporting, based on the third indication information, a DNS information report corresponding to one of the plurality of DNS query messages to the first core network element, where the DNS query message may include, for example, a first DNS query message received by the server discovery function network element. The first core network element may be a session management function network element, and the DNS information report is for triggering the session management function network element to send a DNS handling rule for the plurality of DNS query messages.

[0152] The third instruction information may include a correspondence between the identification information of the EAS and the data network, for example, the third instruction information may include a correspondence table between the identification information of the EAS and the identification information of the data network.

[0153] The EAS identification information is as follows: EAS uniform resource identifiers (URIs), EAS instance ID, and EAS FQDN It should be understood that the address information of the EAS can be obtained based on the identification information of the EAS. The identification information of the data network is similar to that in S420. The details will not be described again here.

[0154] It should be noted that the above are only examples of identification information and should not constitute any limitation to the present application, and the present application does not exclude that the identification information may be any other information that can be used to obtain edge server address information.

[0155] In a possible implementation, the multiple DNS query messages include identification information of queried EASs. The server discovery function network element may determine the data network corresponding to the identification information of the queried EASs based on the identification information of the queried EASs and the correspondence between the identification information of the EASs and the data network. If the identification information of the queried EASs corresponds to the same data network, the server discovery function network element determines to report the DNS information report once for the multiple DNS query messages.

[0156] For example, the third indication information may be configured in the server discovery function network element, or the server discovery function network element may receive the third indication information sent by the first core network element. For example, the server discovery function network element may receive the third indication information in a PDU session establishment process. The server discovery function network element may receive a DNS context creation request (Neasdf_DNSContext_Create Request) sent by the SMF, where the request message includes the third indication information. Alternatively, the server discovery function network element may receive the third indication information in a DNS context update procedure. For example, the EASDF may receive a DNS context update request (Neasdf_DNSContext_Update Request) sent by the SMF, where the update request includes the third indication information. Alternatively, the EASDF may receive the third indication information at any time before the terminal device sends a DNS query message. In another possible implementation, the third indication information and the above-mentioned first indication information may be included in the same information, for example, the first information. The first core network element may send both the first indication information and the third indication information to the server discovery function network element by sending the first information.

[0157] Optionally, the method may further include S530, in which the server discovery function network element buffers the plurality of DNS query messages.

[0158] The server discovery function network element may buffer the DNS query messages, and then process the DNS query messages based on the DNS handling rules sent by the first core network element, such as by constructing EDNS client subnet option information.

[0159] Optionally, the method may further include S540, receiving fourth indication information sent by the first core network element, where the fourth indication information includes a DNS handling rule.

[0160] S550. The server discovery function network element sends multiple DNS query messages to a DNS server to obtain DNS response messages corresponding to the multiple DNS query messages, and the DNS response messages include address information of the EAS queried by the terminal device.

[0161] S560. The server discovery function network element sends a plurality of DNS response messages to the terminal device.

[0162] According to the method provided in this embodiment of the present application, the server discovery function network element can receive multiple DNS query messages, and the multiple DNS query messages may correspond to the same data network. The server discovery function network element can determine, based on the third indication information, to send a DNS information report to the first core network element only once for the multiple DNS query messages, thereby reducing signaling overhead generated when address information of multiple EASs is queried.

[0163] The edge service acquisition method in the embodiment of the present application will be described in detail below with reference to FIG. 6 and FIG.

[0164] Figure 6 is a schematic flowchart of another edge service acquisition method 600 according to the present application. The method 600 shown in Figure 6 may be performed by network elements such as the SMF, EASDF, UDM (UL CL / BP), and UDM (PDA) in the system shown in Figure 1. As shown in Figure 6, the method includes steps S610 to S6110.

[0165] Optionally, in S610, the SMF sends first indication information to the EASDF. In response, the EASDF receives the first indication information. The first indication information is similar to that in S420. Details will not be described again here.

[0166] S620.EASDF receives multiple DNS query messages sent by the terminal device.

[0167] The multiple DNS query messages may be for obtaining address information of the EAS corresponding to the same data network identification information, and the data network identification information is similar to that in S420.

[0168] S630.EASDF sends multiple DNS query messages to a DNS server.

[0169] S640.EASDF receives DNS response messages sent by a DNS server in response to multiple DNS query messages.

[0170] S650. The EASDF buffers the plurality of DNS response messages, and determines, based on the first indication information, to send a DNS information report to the first core network element once for the plurality of DNS response messages.

[0171] S660.EASDF sends a DNS information report (DNS context notification request) to SMF.

[0172] S670.EASDF receives a response message (DNS context notification response) for the DNS information report.

[0173] S680.SMF establishes a data plane path for the terminal device based on the DNS information report.

[0174] The S690.SMF sends second instruction information to the EASDF, and the second instruction information may include DNS handling rules.

[0175] For example, the SMF entity may send the second indication information in a DNS context update request (Neasdf_DNSContext_Update Request) message.

[0176] The DNS handling rule may be a policy for instructing the server discovery network element to send a DNS response message to the terminal device, for example, to send multiple DNS response messages buffered by the EASDF or to send a DNS response message for a specified EAS address range, where the second instruction information may include EAS IP address range information, a specified DANI, or a specified FQDN. Alternatively, the DNS handling rule may instruct the server discovery network element not to buffer a first DNS response message following multiple DNS response messages, where the first DNS response message is also a response to multiple DNS query messages sent by the terminal device. Alternatively, the DNS handling rule may instruct the server discovery network element to discard a first DNS response message following multiple DNS response messages.

[0177] S6100.SMF receives the response message sent by the EASDF, which may be a DNS context update response (Neasdf_DNSContext_Update Response).

[0178] S6110.EASDF sends a DNS response message to the terminal device.

[0179] Figure 7 is a schematic flowchart of another edge service acquisition method 700 according to the present application. The method 700 shown in Figure 7 may be performed by network elements such as the SMF, EASDF, UDM (UL CL / BP), and UDM (PSA) in the system shown in Figure 1. As shown in Figure 7, the method includes steps S710 to S7120.

[0180] Optionally, at S710, the SMF sends third instruction information to the EASDF. Correspondingly, the EASDF receives third instruction information. The third instruction information is similar to that at S520. Details will not be described again here.

[0181] S720.EASDF receives multiple DNS query messages sent by the terminal device.

[0182] The multiple DNS query messages may be for obtaining address information of the EAS corresponding to the same data network identification information, and the data network identification information is similar to that in S420.

[0183] S730.EASDF buffers multiple DNS query messages.

[0184] S740. The EASDF determines, based on the third indication information, to send a DNS information report (DNS context notification request) to the first core network element for the multiple DNS query messages.

[0185] S750.EASDF receives a response message (DNS context notification response) for the DNS information report.

[0186] The S760.SMF sends fourth instruction information to the EASDF, where the fourth instruction information may include a DNS handling rule. For example, the DNS handling rule may include constructing EDNS client subnet option information.

[0187] For example, the SMF entity may send the fourth indication information in a DNS context update request (Neasdf_DNSContext_Update Request) message.

[0188] S770. The EASDF receives a DNS context update response (Neasdf_DNSContext_Update Response) message.

[0189] Optionally, at S780, the EASDF constructs EDNS client subnet option information for the buffered DNS query message.

[0190] S790.EASDF sends multiple DNS query messages to a DNS server.

[0191] S7100.EASDF receives a DNS response message that responds to multiple DNS query messages sent by a DNS server.

[0192] S7110. The process of processing the DNS response message is similar to that in S680.

[0193] S7120.EASDF sends a DNS response message to the terminal device.

[0194] It should be noted that, in order to clearly describe the technical solutions in the embodiments of the present application, terms such as "first" and "second" are used in the embodiments of the present application to distinguish between the same or similar items having essentially the same functions and purposes. For example, the terms "first information" and "second information" are only used to distinguish between different pieces of information, and do not limit the order of the first information and the second information. Those skilled in the art can understand that the terms "first" and "second" do not limit the quantity or execution order, and do not indicate a clear distinction.

[0195] The above describes in detail the edge service acquisition method in the embodiment of the present application with reference to Figures 4 to 7. The device provided in the embodiment of the present application will be described below with reference to Figures 8 and 9. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for the contents not described in detail, please refer to the above method embodiment. For the sake of brevity, the details will not be described again here.

[0196] The above mainly describes the solutions provided in the embodiments of the present application from the perspective of interactions between nodes. It can be understood that, to implement the above functions, each node, such as a terminal device or a network device, includes a corresponding hardware structure and / or software module for performing each function. In combination with the examples described in the embodiments disclosed herein, those skilled in the art can recognize that the units and algorithm steps in the present application may be implemented by hardware or a combination of hardware and computer software. Whether the functions are implemented by hardware or hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but it should not be considered that such implementation goes beyond the scope of the present application.

[0197] In the embodiments of the present application, the functional modules of the terminal device or the network device may be obtained by division based on the above-mentioned method examples. For example, each functional module may be obtained by division based on its respective function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiments of the present application, the module division is an example and is merely a logical functional division. In actual implementation, other division methods may be used. An example in which each functional module is obtained by division based on its corresponding function will be used for the following explanation.

[0198] 8 is a schematic block diagram of an apparatus 100 according to an embodiment of the present application. As shown, the apparatus 100 may include a transceiver unit 110 and a processing unit 120.

[0199] In a possible design, the apparatus 100 may be a server discovery function network element in the above method embodiments, or may be a chip configured to implement the functions of the server discovery function network element in the above method embodiments. It should be understood that the apparatus 100 may correspond to the server discovery function network element in the methods 400, 500, 600, and 700 of the present application. The apparatus 100 may perform steps corresponding to the server discovery function network element in the methods 400, 500, 600, and 700 of the present application. It should be understood that the specific processes by which the units perform the above corresponding steps have been described in detail in the above method embodiments, and will not be described in detail here for the sake of brevity.

[0200] Specifically, the transceiver unit is configured to receive a plurality of DNS response messages sent by a DNS server, the plurality of DNS response messages being responses to a plurality of DNS queries sent by a terminal device, and the plurality of DNS response messages including address information of an EAS queried by the terminal device.

[0201] The address information of the EAS may include address information of multiple EASs for the same edge service, or the address information of the EAS may be address information of multiple EASs corresponding to different edge services.

[0202] The processing unit is configured to determine, based on first indication information, to send a DNS information report to the first core network element once for the plurality of DNS response messages, The first indication information may include a correspondence between network address information and a data network.

[0203] Optionally, the apparatus 100 may further include a storage unit 130 configured to buffer a plurality of DNS response messages.

[0204] Optionally, the transceiver unit is further configured to receive second instruction information sent by the first core network element, where the second instruction information includes DNS handling rules for the plurality of DNS response messages.

[0205] The DNS handling rule may instruct the server discovery network element to send multiple buffered DNS response messages to the terminal device, or may instruct the server discovery network element to send a DNS response message for a specified EAS address range to the terminal device. Alternatively, the DNS handling rule may instruct the server discovery network element not to buffer the first DNS response message following multiple DNS response messages, where the first DNS response message is also a response to multiple DNS query request messages sent by the terminal device. Alternatively, the DNS handling rule may instruct the server discovery network element to discard the first DNS response message following multiple DNS response messages.

[0206] In a possible design, the apparatus 100 may be a first core network element, such as an SMF, in the above method embodiments, or may be a chip configured to implement the functions of the first core network element in the above method embodiments. It should be understood that the apparatus 100 may perform steps corresponding to the first core network element in the methods 400, 500, 600, and 700 of the present application. It should be understood that the specific processes by which the units perform the above corresponding steps have been described in detail in the above method embodiments, and will not be described in detail here for the sake of brevity.

[0207] 9 is a schematic block diagram of an apparatus 200 according to an embodiment of the present application. As shown, the apparatus 200 includes at least one processor 220. The processor 220 is coupled to a memory and configured to execute instructions stored in the memory to transmit signals and / or receive signals. Optionally, the apparatus 200 further includes a memory 230 configured to store instructions. Optionally, the apparatus 200 further includes a transceiver 210, wherein the processor 220 controls the transceiver 210 to transmit signals and / or receive signals.

[0208] It should be understood that the processor 220 and the memory 230 may be integrated into one processing device. The processor 220 is configured to execute program code stored in the memory to implement the above-described functions. In a specific implementation, the memory 230 may alternatively be integrated into the processor 220 or may be separate from the processor 220.

[0209] It should be further understood that the transceiver 210 may include a receiver (also referred to as a receiving machine) and a transmitter (also referred to as a transmitting machine). The transmitter may further include an antenna. There may be one or more antennas. The transceiver 210 may be a communications interface or interface circuit.

[0210] In particular, the transceiver 210 of the apparatus 200 may correspond to the transceiver unit 110 of the apparatus 100 , and the processor 220 of the apparatus 200 may correspond to the processing unit 120 of the apparatus 200 .

[0211] It should be understood that the specific processes by which the transceiver and the processor perform the above corresponding steps have been described in detail in the above method embodiments, and for the sake of brevity, the details will not be described here.

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

[0213] It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip and have a single processing capability. In the implementation process, the steps in the above-described method embodiments may be implemented by using hardware integrated logic circuitry in the processor or by using instructions in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. It may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present application may be directly executed by a hardware decoding processor, or may be executed by using a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with the processor's hardware.

[0214] It may be understood that the memory in this embodiment of the present application may be volatile memory or nonvolatile memory, or may include volatile memory and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of example and not limitation, many types of RAM may be used, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM), and direct rambus dynamic random access memory (direct rambus RAM, DR RAM). It should be noted that memory in the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0215] According to the method provided in the embodiment of the present application, the present application further provides a computer program product, which stores computer program code, and when the computer program code is executed on a computer, the computer can perform any one of the embodiments of Method 300, Method 400, and Method 500.

[0216] According to the method provided in the embodiment of the present application, the present application further provides a computer-readable medium, which stores program code, and when the program code is executed by a computer, the computer can perform any one of the embodiments of Method 300, Method 400, and Method 500.

[0217] According to the method provided in the embodiment of the present application, the present application further provides a system, which includes the apparatus or device described above.

[0218] All or part of the above embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., synchronous cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio wave, or microwave) transmission. The computer-readable storage medium may be any available medium accessible by a computer or a data storage device incorporating one or more available media, such as a server or data center. The media that can be used may be magnetic media (e.g., floppy disks, hard disk drives, or magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), semiconductor media (e.g., solid-state drives (SSDs)), etc.

[0219] The network side device and the terminal device in the above apparatus embodiments correspond to the network side device or the terminal device in the method embodiments. Corresponding modules or units perform corresponding steps. For example, a communication unit (transceiver) performs the receiving step or the transmitting step in the method embodiments, and steps other than the transmitting step and the receiving step may be performed by a processing unit (processor). For specific unit functions, please refer to the corresponding method embodiments. There may be one or more processors.

[0220] As used herein, terms such as “component,” “module,” and “system” are used to denote a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software running on it. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. As depicted using the figures, both computing devices and applications running on computing devices may be components. One or more components may reside within a process and / or thread of execution, and a component may be located on one computer and / or distributed between two or more computers. Moreover, these components may execute from various computer-readable media that store various data structures. For example, components may communicate by using local and / or remote processes, based on signals, for example, comprising one or more data packets (e.g., data from two components interacting with other components within a local or distributed system and / or across a network such as the Internet that interacts with other systems using signals).

[0221] Those skilled in the art may realize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is implemented by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but it should not be considered that the implementation goes beyond the scope of the present application.

[0222] For convenience and concise description, it can be clearly understood by those skilled in the art that for the detailed operation processes of the above systems, devices, and units, please refer to the corresponding processes in the above method embodiments, and the details will not be described again here.

[0223] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into other systems, or some functions may be omitted or not performed. Furthermore, the mutual couplings or direct couplings or communication connections shown or discussed may be implemented using some kind of interface. Indirect couplings or communication connections between devices or units may be implemented in electronic, mechanical, or other forms.

[0224] Units described as separate parts may or may not be physically separated, and parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units, some or all of which may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0225] Furthermore, the functional units in the embodiments of the present application may be integrated into one processing unit, each unit may exist physically alone, or two or more units may be integrated into one unit.

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

[0227] The above description is merely a specific implementation of the present application, and is not intended to limit the scope of protection of the present application. Any modifications or replacements that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should fall within the scope of protection of the present application. Therefore, the scope of protection of the present application should be subject to the scope of protection of the claims.

Claims

1. 1. A method for acquiring an edge service, comprising: receiving, by a server discovery function network element, a plurality of domain name system (DNS) response messages from a DNS server, the plurality of DNS response messages including address information of edge application servers (EASs) queried by a terminal device, the address information of the EASs in the plurality of DNS response messages corresponding to the same data network; determining, by the server discovery function network element based on first indication information, to send a DNS information report to a first core network element once for the plurality of DNS response messages; sending the DNS information report to the first core network element by the server discovery function network element, including any one of the plurality of DNS response messages in the DNS information report, and buffering the remaining DNS response messages of the plurality of DNS response messages; receiving, by the server discovery function network element, a handling rule sent from the first core network element in response to the DNS information report, and processing the remaining buffered DNS response messages according to the handling rule; A method having the following.

2. the first indication information includes correspondence information between a network address and an identification information of a data network; The determining, by the server discovery function network element, based on first indication information, to send a DNS information report to a first core network element once for the plurality of DNS response messages, includes: determining, by the server discovery function network element, based on the first indication information and the address information of the EASs in the plurality of DNS response messages, that the queried EASs correspond to the same data network identification information. The method of claim 1.

3. Prior to receiving a plurality of DNS response messages from the DNS server by the server discovery function network element, the method further comprises: receiving, by the server discovery function network element, the first indication information from the first core network element. The method of claim 1.

4. the first core network element is a session management function network element; The method of claim 1.

5. The identification information of the data network is: a Data Network Access Identifier (DNAI) for said data network; and The Data Network Name (DNN) of said data network The information includes at least one of The method of claim 2.

6. 1. A method for acquiring an edge service, comprising: sending first indication information by a first core network element to a server discovery function network element, the first indication information instructing the server discovery function network element to send a Domain Name System (DNS) information report to the first core network element once for a plurality of DNS response messages, the plurality of DNS response messages including address information of Edge Application Servers (EAS) queried by terminal devices, the address information of the EASs in the plurality of DNS response messages corresponding to the same data network; receiving, by the first core network element, the DNS information report including any one DNS response message of the plurality of DNS response messages; transmitting, by the first core network element, in response to the DNS information report, to the server discovery function network element, handling rules for processing remaining DNS response messages of the plurality of DNS response messages buffered at the server discovery function network element; A method having the following.

7. the first core network element is a session management function network element; The method of claim 6.

8. the first indication information includes correspondence information between a network address and an identification information of a data network; The method of claim 6.

9. The identification information of the data network is: a Data Network Access Identifier (DNAI) for said data network; and The Data Network Name (DNN) of said data network The information includes at least one of The method of claim 8.

10. An edge service acquisition device, a processor coupled to a memory, the memory configured to store a program or instruction; When the program or the instructions are executed by the processor, the edge service acquisition device can perform the method according to any one of claims 1 to 5. Edge service acquisition device.

11. An edge service acquisition device, a processor coupled to a memory, the memory configured to store a program or instruction; When the program or the instructions are executed by the processor, the edge service acquisition device can perform the method according to any one of claims 6 to 9. Edge service acquisition device.

12. having a computer program, The computer program, when executed on a computer, enables the computer to carry out the method according to any one of claims 1 to 5. A computer-readable storage medium.

13. having a computer program, The computer program, when executed on a computer, enables the computer to carry out the method according to any one of claims 6 to 9. A computer-readable storage medium.

14. a server discovery function network element and a first core network element; The server discovery function network element is configured to perform the method of any one of claims 1 to 5, The first core network element is configured to perform the method according to any one of claims 6 to 9. Communication system.

15. 1. A method for acquiring an edge service, comprising: receiving, by a server discovery function network element, a plurality of domain name system (DNS) response messages from a DNS server, the plurality of DNS response messages including address information of edge application servers (EASs) queried by a terminal device, the address information of the EASs in the plurality of DNS response messages corresponding to the same data network; determining, by the server discovery function network element based on first indication information, to send a DNS information report to a first core network element once for the plurality of DNS response messages; sending the DNS information report to the first core network element by the server discovery function network element, including any one of the plurality of DNS response messages in the DNS information report, and buffering the remaining DNS response messages of the plurality of DNS response messages; receiving the DNS information report by the first core network element; sending, by the first core network element, in response to the DNS information report, handling rules for processing the remaining buffered DNS response messages to the server discovery function network element; receiving, by the server discovery function network element, the handling rules and processing the remaining buffered DNS response messages in accordance with the handling rules; A method having the following.

16. The method comprises: sending the first indication information by the first core network element to the server discovery function network element, the first indication information instructing the server discovery function network element to send the DNS information report to the first core network element once for the plurality of DNS response messages; receiving the first indication information from the first core network element by the server discovery function network element; Further comprising:

16. The method of claim 15.

Images