WO2022222817A1 - 一种边缘应用服务器的选择方法及装置 - Google Patents

一种边缘应用服务器的选择方法及装置 Download PDF

Info

Publication number
WO2022222817A1
WO2022222817A1 PCT/CN2022/086550 CN2022086550W WO2022222817A1 WO 2022222817 A1 WO2022222817 A1 WO 2022222817A1 CN 2022086550 W CN2022086550 W CN 2022086550W WO 2022222817 A1 WO2022222817 A1 WO 2022222817A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
edge application
application servers
information
server
Prior art date
Application number
PCT/CN2022/086550
Other languages
English (en)
French (fr)
Inventor
周汉
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22790925.6A priority Critical patent/EP4319093A4/en
Publication of WO2022222817A1 publication Critical patent/WO2022222817A1/zh
Priority to US18/491,354 priority patent/US20240056496A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload

Definitions

  • the present application relates to the field of edge computing, and in particular, to a method and device for selecting an edge application server.
  • MEC Mobile edge computing
  • MEC can also be called multi-access edge computing (MEC).
  • MEC multi-access edge computing
  • IT information technology
  • MEC provides application developers and content providers with cloud computing capabilities, as well as an information technology (IT) service environment at the network edge.
  • Multiple edge application servers of a service are distributed and deployed on multiple MEC platforms, for example, in an edge network, and each edge application server of a service provides services for user equipment (UE) within a certain range.
  • UE user equipment
  • a domain name resolution server (local DNS Resolve, LDNSR) network element is used to process domain name system (domain name system, DNS) messages sent by the UE.
  • the LDNSR network element receives the UE's DNS message
  • the LDNSR requests the UE's location information from the session management function (SMF) network element
  • the LDNSR places the UE's location information in the edge network configuration server (edge network configuration server) in the DNS request message.
  • ECS data network configuration server
  • the DNS Server selects an application server that is closer to the specific UE location for the UE according to the ECS field. But this method only considers the delay factor.
  • the DNS server does not perceive information such as the load status of the application server, and cannot select a more suitable edge application server for the UE.
  • the present application provides a method for selecting an edge application server, so that a domain name resolution server network element determines an appropriate edge application server for a terminal device according to load status information and network addresses of multiple edge application servers.
  • a method for selecting an edge application server is provided.
  • the method is executed by a domain name resolution server network element, including: acquiring load status information of multiple edge application servers, and when receiving DNS request information from a domain name server from a terminal device , determining a first edge application server of the terminal device according to the load state information of the multiple edge application servers, where the multiple edge application servers include the first edge application server.
  • the domain name resolution server network element obtains the load status information of multiple edge application servers, and selects an appropriate edge application server for the terminal device according to the load status information of the multiple edge application servers.
  • the prior art only considers the delay factor, and only selects an edge application server that is relatively close to the terminal device, thus ignoring the possibility that the selected edge application server is already in an overloaded state.
  • the technical solution of the present application enables the domain name resolution server network element to consider the load status information when selecting the edge application server for the terminal, and can overcome the shortcomings of the prior art, thereby selecting a more suitable edge application server for the terminal.
  • acquiring load status information of multiple edge application servers includes: sending first request information to a network data analysis function network element, where the first request information is used to acquire Load status information of the multiple edge application servers. Load status information of the plurality of edge application servers from the network data analysis function network element is received.
  • acquiring load status information of multiple edge application servers includes: receiving load status information of multiple edge application servers from an edge service function network element.
  • the data network access identifier DNAI information of the plurality of edge application servers is obtained, and the first information of the terminal device is determined according to the load status information of the plurality of edge application servers.
  • the edge application server further includes: determining a first edge application server according to the load state information of the multiple edge application servers and the DNAI information of the multiple edge application servers.
  • acquiring the data network access identifier DNAI information of the multiple edge application servers includes: receiving data from the edge service DNAI information of the multiple edge application servers of the functional network element.
  • the subscription request information is used to subscribe to the multiple edge application server online events, wherein,
  • the subscription request information carries the identification information of the multiple edge application servers.
  • a method for selecting an edge application server is provided.
  • the method is executed by a network data analysis function network element, including: receiving first request information from a domain name resolution server network element, where the first request information is used to request the Load status information of multiple edge application servers.
  • the load state information of the multiple edge application servers is obtained, and the load state information of the multiple edge application servers is sent to the domain name resolution server network element.
  • a method for selecting an edge application server is provided.
  • the method is executed by an edge network configuration server network element, including: obtaining load status information of multiple edge application servers, and sending the load status information of the multiple edge application servers. .
  • the method further includes: receiving a subscription request message, where the subscription request message is used to obtain the data network access identifier DNAI information of the multiple edge application servers.
  • the method includes: sending DNAI information of the multiple edge application servers.
  • the above technical solution enables two factors, delay and load status, to be considered at the same time when selecting an edge application server for a terminal device, so as to select a more suitable edge application server.
  • the method further includes: receiving subscription request information, where the subscription request information is used to subscribe to the online events of the multiple edge application servers ; wherein, the subscription request information carries the identification information of the multiple edge application servers.
  • a method for selecting an edge application server is provided, the method is executed by an edge-enabled server network element, and includes: obtaining load status information of multiple edge application servers, and sending the load status information of the multiple edge application servers .
  • the above technical solution enables the factor of load status to be considered when selecting an edge application server for a terminal device, so as to select an appropriate edge application server.
  • some implementations of the fourth aspect include: receiving first request information, where the first request information is used to request load status information of the plurality of edge application servers.
  • a fifth aspect provides a domain name resolution server network element, including: an acquisition module for acquiring load status information of multiple edge application servers, and a determination module, when receiving the domain name server DNS request information from the terminal device, according to the The load status information of multiple edge application servers determines the first edge application server of the terminal device, the multiple edge application servers include the first edge application server, and a sending module is configured to send DNS response information to the terminal device, the DNS The response information includes identification information of the first edge application server.
  • the obtaining module is specifically configured to: send first request information to the network data analysis function network element, where the first request information is used to obtain the plurality of edge application servers The load status information of the multiple edge application servers is received from the network data analysis function network element.
  • the obtaining module is specifically configured to: receive loads from the multiple edge application servers of the edge service function network element status information.
  • the data network access identifier DNAI information of the multiple edge application servers is acquired, and the determining module is further configured to: The first edge application server is determined according to the load status information of the multiple edge application servers and the DNAI information of the multiple edge application servers.
  • the obtaining module is specifically configured to: receive information from the multiple edge application servers of the edge service function network element. DNAI information.
  • the sending module is further configured to: send subscription request information, where the subscription request information is used to subscribe the multiple edges An application server online event, wherein the subscription request information carries the identification information of the multiple edge application servers.
  • a sixth aspect provides a network element with a network data analysis function, comprising: a receiving module configured to receive first request information from a domain name resolution server network element, where the first request information is used to request the multiple edge application servers for Load status information.
  • An obtaining module is used to obtain the load status information of the multiple edge application servers.
  • the sending module is configured to send the load status information of the multiple edge application servers to the domain name resolution server network element.
  • an edge network configuration server network element comprising: an acquisition module for acquiring load status information of multiple edge application servers, and a sending module for sending the load status information of the multiple edge application servers.
  • a receiving module configured to receive a subscription request message, where the subscription request message is used to obtain the data network access identifier DNAI information of the multiple edge application servers .
  • the sending module is configured to: send the DNAI information of the multiple edge application servers.
  • the receiving module is further configured to: receive subscription request information, where the subscription request information is used to subscribe the multiple edges An application server online event, wherein the subscription request information carries the identification information of the multiple edge application servers.
  • an edge-enabled server network element including: an acquisition module for acquiring load status information of multiple edge application servers, and a sending module for sending the load status information of the multiple edge application servers.
  • some implementations of the eighth aspect include: a receiving module configured to receive first request information, where the first request information is used to request load status information of the plurality of edge application servers.
  • an edge application server selection device including a domain name resolution server network element, a network data analysis function network element, an edge network configuration server network element, and an edge enabling server network element.
  • the domain name resolution server network element is used to execute the method described in the first aspect.
  • the network element of the network data analysis function is used to execute the method described in the second aspect.
  • the edge network configuration server network element is configured to execute the method described in the third aspect.
  • the edge-enabled server network element is configured to perform the method described in the fourth aspect.
  • a computer-readable storage medium stores program instructions, when the instructions are executed, the domain name resolution server network element can execute the method described in the first aspect. Or, when the instruction is executed, the network data analysis function network element can execute the method described in the second aspect. Or, when the instruction is executed, the edge network configuration server can perform the method of the third aspect. Alternatively, when the instruction is executed, the edge-enabled server network element can perform the method described in the fourth aspect.
  • a chip system including: at least one processor, where the at least one processor is configured to execute stored instructions, so that a domain name resolution server network element can execute the method described in the first aspect.
  • the at least one processor is configured to execute stored instructions, so that the network data analysis function network element can execute the method described in the second aspect.
  • the at least one processor is configured to execute the stored instructions, so that the network element of the edge network configuration server can execute the method described in the third aspect.
  • the at least one processor is configured to execute stored instructions, so that the edge-enabled server network element can execute the method described in the fourth aspect.
  • a twelfth aspect provides a system, the system comprising: the domain name resolution server network element described in the fifth aspect, and/or the network data analysis function network element described in the sixth aspect, and/or, The edge network configuration server network element according to the seventh aspect, and/or the edge enabled server network element according to the eighth aspect.
  • FIG. 1 is a schematic diagram of a network system architecture according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a method for selecting an edge application server provided by the present application.
  • FIG. 4 is a schematic diagram of a method for selecting an edge application server provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a method for selecting an edge application server provided by another embodiment of the present application.
  • FIG. 6 is a schematic diagram of a method for selecting an edge application server provided by another embodiment of the present application.
  • FIG. 7 is a schematic block diagram of an apparatus provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another apparatus provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another apparatus provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an apparatus provided by an embodiment of the present application.
  • the technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a fifth generation (5th generation, 5G) system or a new radio (new radio, NR), and other future communication systems.
  • 5th generation 5G
  • NR new radio
  • the terminal device in this embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or user device.
  • the terminal device may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or future evolved public land mobile networks (PLMN)
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a terminal device, etc. is not limited in this embodiment of the present application.
  • FIG. 1 is a schematic block diagram of an example wireless communication system architecture applicable to the present application.
  • the system architecture includes a terminal device, a radio access network (RAN), a core network device, and a data network (DN). It adopts a service-based representation.
  • the terminal device in FIG. 1 can be used to connect to a radio access network device deployed by an operator through a wireless air interface, and then connect to a data network through a core network device.
  • Radio access network equipment is mainly used to implement functions such as wireless physical layer functions, resource scheduling, radio resource management, radio access control, and mobility management; core network equipment (also known as management equipment) is mainly used for terminal equipment. Registration, security authentication, mobility management and location management, etc. It should be noted that FIG.
  • FIG. 1 is only an exemplary architecture diagram.
  • the network architecture may further include other functional units or functional network elements, which are not limited in this embodiment of the present application.
  • FIG. 1 is based on a 5G system architecture, and may also be based on other system architectures, such as an LTE system, which is not limited in this embodiment of the present application.
  • the terminal device shown in FIG. 1 can be any of the above-mentioned possible terminal devices, for example, it can be a mobile phone, a computer, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, Smartphones, wireless local loop (WLL) stations, personal digital assistants (PDAs), computers, laptops, handheld communication devices, handheld computing devices, satellite wireless devices, wireless modems Cards, set top boxes (STBs), customer premise equipment (CPEs), and/or other devices used to communicate over wireless systems.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDAs personal digital assistants
  • computers laptops, handheld communication devices, handheld computing devices, satellite wireless devices, wireless modems Cards, set top boxes (STBs), customer premise equipment (CPEs), and/or other devices used to communicate over wireless systems.
  • STBs set top boxes
  • CPEs customer premise equipment
  • the above-mentioned wireless access network equipment can be an access network (access network, AN)/radio access network (radio access network, RAN) equipment, a network composed of multiple 5G-AN/5G-RAN nodes, the 5G-AN /5G-RAN nodes can be: access point (AP), next-generation base station (NR nodeB, gNB), central unit (central unit, CU) and distributed unit (distributed unit, DU) separate form gNB , a transmission receive point (TRP), a transmission point (TP), or some other access node.
  • access network access network
  • AN access network
  • RAN radio access network
  • the 5G-AN /5G-RAN nodes can be: access point (AP), next-generation base station (NR nodeB, gNB), central unit (central unit, CU) and distributed unit (distributed unit, DU) separate form gNB , a transmission receive point (TRP),
  • the above-mentioned core network equipment may include: unified data management network element (unified data management, UDM), access and mobility management function network element (access and mobility management function, AMF), session management function network element element (session management function, SMF), policy control function (policy control function, PCF), application function (application function, AF), user plane function (user plane function, UPF), network open function network Network exposure function (NEF), network repository function (NRF), network slice selection function (NSSF), authentication server function (AUSF) Wait.
  • These functional units can work independently, or can be combined together to achieve some control functions, such as: AMF, SMF and PCF can be combined as a management device to complete access authentication, security encryption, location registration, etc.
  • Access control and mobility management functions, as well as session management functions such as establishment, release and modification of user plane transmission paths, and functions for analyzing some slice-related data (such as congestion) and terminal equipment-related data.
  • each functional unit can establish a connection through a next generation network (NG) interface to realize communication.
  • NG next generation network
  • a terminal device establishes an air interface connection with a RAN device through an NR interface for transmission.
  • User plane data and control plane signaling terminal equipment can establish a control plane signaling connection with AMF through NG interface 1 (abbreviated as N1);
  • RAN equipment can establish user plane data connection with the offload point UPF through NG interface 3 (abbreviated as N3);
  • the RAN device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short).
  • Each core network element can communicate with other core network elements through a corresponding interface.
  • other core network network elements may communicate with the NSSF through the Nnssf interface, and other core network network elements may communicate with the NEF through the Nnef interface, and so on.
  • the part shown in FIG. 1 is only an exemplary architecture diagram.
  • the network architecture may also include other functional units or functional network elements, which are implemented in this application. This example is not limited.
  • the radio access network device in this embodiment of the present application may be a device for communicating with a terminal device and a core network device, and the radio access network device may be an evolved base station (evolutional nodeb, eNB) in the LTE system. or eNodeB), it can also be a wireless controller in a cloud radio access network (CRAN) scenario, or the access network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, and a 5G network
  • eNB evolved base station
  • CRAN cloud radio access network
  • the network equipment in the PLMN network or the access network equipment in the future evolved PLMN network, etc., are not limited in this embodiment of the present application.
  • FIG. 2 shows a schematic diagram of a system architecture or a scenario applied by an embodiment of the present application.
  • the system architecture includes a terminal device UE, core network elements (UPF, AMF, SMF, unified data management, UDM), PCF), Domain Name Resolution Server (local DNS Resolve, LDNDR), Network Data Analytics Function (NWDAF), Edge Enabler Server (EES) and Edge Application Server (EAS) ).
  • the edge enabling server EES and the edge application server EAS are included in the edge data network (EDN).
  • EDN corresponds to a data network, which is a special local data network (local DN), including edge-enabled functions, and can use the data network access identifier (DN access identifier, DNAI) and data network name ( datanetwork name, DNN) identification, is a network logic concept.
  • EDN is the peer-to-peer concept of the central cloud, which can be understood as a local data center (ie, the concept of geographic location), and can use the data network access identifier (DNAI) to ID, and can contain multiple local data networks (local DNs).
  • the edge application server EAS is an application deployed in the edge data network.
  • the edge application may also be referred to as an "application instance". Specifically, it refers to an instance (instance) of a server application (eg, social media software, augmented reality (AR), virtual reality (VR)) deployed and running on the EDN.
  • An application can deploy one or more EASs in one or more EDNs. EASs deployed and running in different EDNs can be considered as different EASs of an application.
  • Applications use different domain names, where the domain name can be a fully qualified domain name (FQDN), an arbitrary IP address, or a different IP address.
  • FQDN fully qualified domain name
  • EAS can also be referred to as an edge application (server), an application instance, an edge application instance, a multi-access edge computing (multi-access edge computing, MEC) application (server), an EAS function, and the like.
  • EES is deployed in the EDN, and can provide some enabling capabilities for the application instances deployed in the EDN, which can better support the deployment of applications in the MEC, and can also support the registration of edge applications, and the authentication and authentication of UEs.
  • Providing the UE with IP address information of the application instance, etc. may further support obtaining the identification and IP address information of the application instance, and further send the identification and IP address information of the application instance to the edge data network configuration server.
  • an EAS is registered on an EES, or the information of an EAS is configured on an EES through a management system, the EES is called the EES associated with the EAS, and the EES controls/manages the EAS registered/configured on the EES. .
  • the edge data network configuration server (ECS) is responsible for the configuration of the EDN, such as providing EES information to the UE.
  • the ECS can also directly provide the UE with application instance information, and interact with the application domain name server (domain name server, DNS) to obtain the application instance information.
  • the application instance and IP address information can be further obtained and saved from other functional entities.
  • the LDNSR network element is used to process the DNS message sent by the UE. After receiving the UE's DNS message, the LDNSR requests the UE's location information from the SMF network element, that is, the UE's location information is placed in the ECS field in the DNS request message. The field selects an application server closer to the UE location for the UE.
  • NWDAF network elements mainly collect performance data of various network functions, including user service experience and application instance status and other information collected from the application side.
  • the load status of the EAS can be a comprehensive representation of the operating status of various system resources of an EAS.
  • These resource operating statuses include the central processing unit (CPU) usage status, memory usage status, input/output (input/output, I/ O) Usage status, number of connected users, number of requested connections, bandwidth, etc.
  • CPU central processing unit
  • I/ O input/output
  • the operating state of these resources reaches a certain level, it may no longer be able to provide services to users, or may no longer accept access from new users. At this time, it can be considered that the EAS is overloaded.
  • the load states of different EASs of the same application may be different, and the load states of different EASs of different applications may also be different. That is to say, different applications can independently count the load of their corresponding EAS. For example, when the EAS for the first application is overloaded, the EAS for the second application may also be in a normal state.
  • FIG. 3 is a schematic flowchart of a method for selecting an edge application server provided by the present application, and the method includes:
  • the domain name resolution server network element obtains load status information of multiple edge application servers.
  • the LDNSR network element obtains load status information of multiple edge application server EASs, and the load status information may be real-time analysis data, including EAS load information, user service experience, etc., which is not limited in this embodiment of the present application.
  • the LDNSR network element sends first request information to the network data analysis function network element, where the first request information is used to obtain load status information of the multiple edge application servers, and correspondingly, the network data
  • the analysis function network element collects load status information of multiple edge application servers, and sends the load status information to the domain name resolution server network element.
  • the LDNSR network element receives load status information of multiple edge application servers sent by the edge service function network element.
  • the edge service function network element may be an edge enablement server EES function network element, or an edge network configuration server ECS function network element, which is not limited in this embodiment of the present application.
  • the domain name resolution server network element receives the domain name server DNS request message sent by the terminal device.
  • the terminal device sends a domain name server DNS request message to the LDNSR network element, where the DNS request message is used to request data network access identifier DNAI information of multiple edge application servers.
  • the terminal device can directly send the DNS request message to the LDNSR network element, or it can forward the DNS request message through other core network elements.
  • the core network element here may be an SMF network element, or a The UPF network element is not limited in this embodiment of the present application.
  • the domain name resolution server network element determines the first edge application server of the terminal device according to the load status information of the multiple edge application servers.
  • the LDNSR network element obtains load status information of multiple edge application servers, and determines the first edge application server from the multiple edge application servers according to the load status information. For example, the LDNSR network element is used for multiple edge application servers. The overloaded edge application server among the edge application servers is not selected, and the edge application server with less load is preferentially selected.
  • the LDNSR network element also acquires DNAI information (network address information) of multiple edge application servers, and determines the first edge application from the multiple edge application servers according to the load status information and the DNAI information server. For example, the LDNSR network element will select an edge application server with a smaller load among multiple edge application servers that are located close together. It should be noted that, through this technical solution, the LDNSR network element can simultaneously consider two factors of load state information and time delay, so as to select a more suitable edge application server for the terminal device. And in other embodiments of the present application, when selecting the edge application server considering the load status information, the DNAI information may also be considered simultaneously or further to select the edge application server for the terminal device.
  • DNAI information network address information
  • the domain name resolution server network element sends DNS response information to the terminal device.
  • the LDNSR generates the DNS response information, which can also be understood as that the LDNSR replaces the DNS server to generate the DNS response information, and sends the selected first EAS instance to the terminal device through the DNS response message.
  • the LDNSR network element can directly send the DNS response information to the terminal device, or it can forward the DNS response information through other core network elements.
  • the core network element here can be an SMF network element, or it can be The user port function is a UPF network element, which is not limited in this embodiment of the present application.
  • domain name resolution server network element in this application may also determine the first edge application server of the terminal device according to the load status information of an edge application server.
  • the application server can also be one, which is not limited in this application.
  • the LDNSR network element can simultaneously consider two factors of delay and load state information, so as to select a more suitable edge application server for the terminal.
  • FIG. 4 is a schematic flowchart of an embodiment provided by the present application, as shown in FIG. 4 .
  • the domain name resolution server network element sends a subscription request message to the edge service function network element.
  • the edge service function network element may be an edge enablement server EES function network element, or an edge network configuration server ECS function network element, which is not limited in this embodiment of the present application.
  • the LDNSR network element sends a subscription request message to the edge service function network element.
  • the edge service function network element receives a subscription request message from the LDNSR network element, and the subscription request message is used to subscribe to multiple edge application server online events.
  • An online event can be understood as the online status of a server, or a change in the online status of multiple servers.
  • the subscription request message carries information of multiple EAS instance identities (identities, IDs).
  • the domain name resolution server network element receives the subscription response information from the edge service function network element.
  • the subscription request message contains ID information of multiple EAS instances, each ID represents a type of EAS instance, and the edge service function network element responds to the LDNSR network element with the address of the EAS instance corresponding to the ID according to the EAS instance ID. information.
  • the address information includes information of an EAS instance identifier, DNAI information of the EAS instance, and an EES address where the EAS instance is located, etc., which are not limited in this embodiment of the present application.
  • the domain name resolution server network element sends the first request information to the network data analysis function network element.
  • the first request information is used to request load status information of multiple edge application servers, and the LDNSR network element requests the network data analysis function NWDAF network element for load status information of multiple EASs.
  • the load status information may include
  • the load information of the EAS instance may also include user service experience, etc., which is not limited in this embodiment of the present application.
  • the first request information carries the identifiers and/or EES addresses of multiple edge application servers, which is not limited in this embodiment of the present application.
  • the first request information may further include multiple requested EAS instance identifiers.
  • the instance identifiers of these multiple EASs can be included in the request message and sent to the NWDAF network element, or it can be sent to the NWDAF network element through other messages. It should be understood that this application The embodiment does not limit this.
  • the network element of the network data analysis function obtains load status information of multiple EAS edge application servers through the network element of the edge service function.
  • the NWDAF network element needs to collect the load status information of the EAS instances from the EESs on which the EASs are deployed.
  • the NWDAF network element collects the load status information of the application instance corresponding to the EAS application ID from the EES network element according to the EES addresses of the multiple EASs.
  • the EES network element sends the collected load status information of the EAS instance to the NWDAF network element.
  • the NWDAF network element collects the load status information of EAS instances with IDs 1 and 2 from EES1 according to the address of EES1.
  • the load status information of the EAS instances whose IDs are 3 and 4 are collected from EES2 according to the address of EES2.
  • the load state information may be the load information of the EAS instance or the user service experience, and it should be understood that this application does not limit this.
  • the NWDAF network element sends load status information of multiple edge application servers to the LDNSR network element.
  • the load status information may include load information of the EAS instance, user service experience, etc., which is not limited in this embodiment of the present application.
  • the terminal device sends a DNS request message to the LDNSR network element, and accordingly, the LDNSR network element receives the DNS request message from the terminal device.
  • the LDNSR network element determines the first edge application server according to the network addresses and load status information of the multiple edge application servers.
  • the LDNSR network element adds the location information of the UE to the ECS field in the DNS request message sent by the UE, and the DNS server selects multiple application servers that are close to the UE for the UE according to the location information of the UE.
  • the LDNSR network element determines, according to the obtained load state information of the EAS, the EAS with the smallest load among the EASs that are closer to the UE as the first edge application server accessed by the UE.
  • the LDNSR sends DNS response information to the terminal device.
  • the LDNSR generates DNS response information, and sends the determined first edge application server to the UE through the DNS response information. It should be noted that the generation of the response information by the LDNSR can be understood as the generation of the DNS response information by the LDNSR instead of the DNS server.
  • the LDNSR network element can simultaneously consider two factors of time delay and load state, so as to select a more suitable edge application server for the terminal.
  • FIG. 5 is a schematic flowchart of another embodiment provided by the present application, as shown in FIG. 5 .
  • the domain name resolution server network element sends subscription request information to the edge network configuration server network element.
  • the edge network configuration server network element sends subscription response information to the edge enabling server network element.
  • steps S510-S520 and the above-mentioned steps S410-S420 perform corresponding operations, which are not repeated here.
  • the domain name resolution server network element sends the first request information to the edge enabling server network element.
  • the first request information is used to request load status information of multiple edge application servers, and the LDNSR network element requests the EES network element for load status information of multiple EASs.
  • the load status information may include load information of EAS instances , user service experience, etc., which are not limited in this embodiment of the present application.
  • the first request information carries the identities and/or EES addresses of multiple edge application servers, which is not limited in this embodiment of the present application.
  • the first request information may further include multiple requested EAS instance identifiers.
  • the first request information may also carry information about reporting conditions, such as periodic reporting, reporting thresholds, etc.
  • reporting conditions such as periodic reporting, reporting thresholds, etc.
  • the periodic report can be understood as setting a specific time period.
  • the EES network element receives the periodic report, when the set time period is reached, the EES network element reports (sends) multiple requests to the LDNSR network element.
  • the reporting threshold can be understood as setting a threshold.
  • the EES network element receives the threshold report, when the set threshold is reached, the EES network element reports (sends) the load status information of the requested multiple EASs to the LDNSR network element. .
  • the edge enabling server network element sends load status information of multiple edge application servers to the domain name resolution server network element.
  • the load state information may include load information of the EAS instance, user service experience, etc., which is not limited in this embodiment of the present application.
  • the EES network element may also report load status information of multiple edge application servers to the LDNSR network element.
  • the EES network element receives the information of the reporting conditions in the foregoing step S530, and when the foregoing reporting conditions are satisfied, the EES reports the load status information of multiple edge application servers to the LDNSR network element.
  • the reporting condition received by the EES network element in the above step S530 is periodic reporting, it can be understood that, assuming that the period of periodic reporting is set to 100s, then the EES network element will report to the LDNSR after the period of 100s is set.
  • the network element reports the load status information of multiple edge application servers.
  • the reporting condition received by the EES network element in the above step S530 is threshold reporting, then the EES network element reports the load status information of multiple edge application servers to the LDNSR network element after reaching the set threshold.
  • satisfying the above reporting conditions can be understood as meeting at least one of periodic reporting and reporting thresholds, that is, the EES network element can also report load status information to the LDNSR network element when both the periodic reporting and reporting threshold conditions are met.
  • reporting conditions may also include other possible set reporting conditions, which are not limited in this embodiment of the present application.
  • the EES network element if the EES network element does not receive the information about the reporting conditions in the above step S530, in other words, the first request information does not carry the reporting conditions, then the EES network element directly reports the reporting conditions to the LDNSR network. The element sends the load status information of the edge application server.
  • the EES network element if the EES network element receives the reporting conditions in the above step S530, but does not meet the above reporting conditions, the EES network element will not report the load status of the edge application server to the LDNSR network element information.
  • the terminal device sends a DNS request message, and accordingly, the LDNSR network element receives the DNS request message from the terminal device.
  • the LDNSR network element determines the first edge application server according to the network address information and load state information of the multiple edge application servers.
  • the LDNSR sends DNS response information.
  • the LDNSR network element can simultaneously consider two factors of time delay and load state, so as to select an appropriate edge application server for the terminal.
  • FIG. 6 is a schematic flow chart of yet another embodiment provided by the present application.
  • EES1 mainly manages the load status information of EAS1 and EAS2
  • EES2 mainly manages the load status information of EAS3 and EAS4. Load status information.
  • EES1 and its managed EAS1 and EAS2 are deployed in EDN1, while EES2 and its managed EAS3 and EAS4 are deployed in EDN2.
  • the edge enabling server network element sends load status information and associated network address information of the edge application servers managed by the edge network configuration server network element to the edge network configuration server network element.
  • the EES network element obtains the load status information of each EAS edge application server in the EDN, and the load status information may be the load status of the CPU, graphics processing unit (GPU), and memory, etc., which is not described in this embodiment of the present application. limit.
  • EES1 acquires the load status information of EAS1 and EAS2 in EDN1
  • EES2 acquires the load status information of EAS1 and EAS3 in EDN2.
  • the EAS can also directly report the load status information of the EAS and the DNAI information associated with the EAS to the ECS network element. DNAI information.
  • the edge network configuration server network element acquires load status information of multiple edge application servers.
  • the edge network configuration server network element sends the load status information of multiple edge application servers and the DNAI information associated with the EAS to the core network network element, and accordingly, the core network network element stores the above information.
  • the ECS network element can send the above-mentioned information to the core network element by enhancing the existing AF influence traffic routing mechanism (that is, the application actively triggers the service flow routing rules), or can also use other methods. This is not limited.
  • the core network element may be an LDNSR network element, an SMF network element, a PCF network element, an NRF network element, or a UPF network element, which is not limited in this embodiment of the present application.
  • the terminal device sends EAS address request information to the core network element, for acquiring address information of multiple edge application servers.
  • the UE may send DNS request information to the core network element, or the UE may also send service provisioning request information, or the UE may also send EAS discovery request information, etc. It should be understood that this application does not limit the specific message names .
  • step S640 is an optional step, that is, the UE may not send the EAS address request information to the core network element.
  • the core network network element determines the first edge application server according to the network address information and load state information of the multiple edge application servers.
  • the core network element determines the list of EASs accessed by the UE according to the stored load state information of the multiple EASs, or determines the EESs corresponding to the multiple EASs accessed by the UE. If there are multiple edge application servers requested by the UE deployed in multiple EDNs, the 5GC network element determines multiple EASs that are closer to the UE according to the load status information of multiple EASs and the associated DNAI information, and selects the one with the smallest load among them. The EAS is determined as the EAS that the UE needs to access.
  • the core network element sends the address information of the EAS to the terminal device.
  • the network element of the core network sends the connection information of the EES corresponding to the determined EAS to the UE, or the network element of the core network sends the address information of the EAS to the UE.
  • the core network element sends the connection information of the multiple EESs and the load status information of the multiple EASs requested in the first request information to the UE, and the UE sends the connection information of the multiple EASs according to the load status information of the multiple EASs. and the associated DNAI information to determine the first edge application server.
  • the LDNSR network element can simultaneously consider two factors of time delay and load state, so as to select an appropriate edge application server for the terminal.
  • each device may also be implemented by a component (for example, a chip or a circuit) of a corresponding device.
  • each network element such as a transmitter device or a receiver device
  • each network element includes hardware structures and/or software modules corresponding to performing each function in order to implement the above functions.
  • Those skilled in the art should realize that the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware, or can be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. The following description will be given by using the division of each function module corresponding to each function as an example.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • FIG. 7 shows a schematic block diagram of an apparatus 700 of a domain name resolution server LDNSR according to an embodiment of the present application.
  • the apparatus 700 may correspond to the LDNSR in the embodiment shown in FIG. 3 , and may have any function of the LDNSR in the method.
  • the apparatus 700 includes an acquisition module 710 , a determination module 720 and a transmission module 730 .
  • the obtaining module 710 is configured to obtain load status information of multiple edge application servers
  • the determining module 720 when receiving the domain name server DNS request information from the terminal device, determines the first edge application server of the terminal device according to the load status information of the multiple edge application servers, and the multiple edge application servers include the first edge application server. edge application server;
  • the sending module 730 is configured to send DNS response information to the terminal device, where the DNS response information includes identification information of the first edge application server.
  • the obtaining module 710 is specifically used for:
  • Load status information of the plurality of edge application servers from the network data analysis function network element is received.
  • the obtaining module 710 is specifically used for:
  • Load status information of the plurality of edge application servers from the edge service function network element is received.
  • the determining module 720 is also used for:
  • the first edge application server is determined according to the load state information of the multiple edge application servers and the DNAI information of the multiple edge application servers.
  • the obtaining module 710 is specifically used for:
  • DNAI information of the plurality of edge application servers from the edge service function network element is received.
  • the sending module 730 is further configured to:
  • the subscription request information is used to subscribe to the online events of the multiple edge application servers, wherein the subscription request information carries the identification information of the multiple edge application servers.
  • FIG. 8 shows a schematic block diagram of an apparatus 800 of a network data analysis function network element NWDAF according to an embodiment of the present application.
  • the apparatus 800 may correspond to the NWDAF in the embodiment shown in FIG. 3 , and may have any function of the NWDAF in the method.
  • the apparatus 800 includes a receiving module 810 , an obtaining module 820 and a sending module 830 .
  • the receiving module 810 is configured to receive first request information from a domain name resolution server network element, where the first request information is used to request load status information of the plurality of edge application servers;
  • the obtaining module 820 configured to obtain load status information of the multiple edge application servers
  • the sending module 830 is configured to send the load status information of the multiple edge application servers to the domain name resolution server network element.
  • FIG. 9 shows a schematic block diagram of an apparatus 900 of an edge network configuration server ECS according to an embodiment of the present application.
  • the apparatus 900 may correspond to the ECS in the embodiments shown in FIG. 3 to FIG. 6 , and may have any function of the ECS in the method.
  • the apparatus 900 includes an obtaining module 910 , a sending module 920 and a receiving module 930 .
  • the obtaining module 910 is configured to obtain load status information of multiple edge application servers
  • the sending module 920 is configured to send load status information of the multiple edge application servers.
  • the apparatus 900 further includes:
  • the receiving module 930 is configured to receive a subscription request message, where the subscription request message is used to acquire the data network access identifier DNAI information of the multiple edge application servers.
  • the sending module 920 is configured to: send the DNAI information of the multiple edge application servers.
  • the receiving module 930 is further configured to:
  • FIG. 10 shows a schematic block diagram of an apparatus 1000 for an edge-enabled server EES according to an embodiment of the present application.
  • the apparatus 1000 may correspond to the EES in the embodiments shown in FIG. 3 to FIG. 6, and may have any function of the EES in the method.
  • the apparatus 1000 includes an obtaining module 1010 , a sending module 1020 and a receiving module 1030 .
  • the obtaining module 1010 is configured to obtain load status information of multiple edge application servers
  • the sending module 1020 is configured to send load status information of the multiple edge application servers.
  • the apparatus 1000 further includes:
  • the receiving module 1030 is configured to receive first request information, where the first request information is used to request load status information of the multiple edge application servers.
  • each module in the above communication apparatus can all be implemented in the form of software calling through the processing element; also can all be implemented in the form of hardware; some modules can also be implemented in the form of software calling through the processing element, and some modules can be implemented in the form of hardware.
  • each module can be a separately established processing element, or can be integrated in a certain chip of the communication device to realize, in addition, it can also be stored in the memory in the form of a program, which can be called and executed by a certain processing element of the communication device. function of the module.
  • each step of the above method or each of the above modules may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • a module in any of the above communication devices may be one or more integrated circuits configured to implement the above method, such as: one or more application specific integrated circuits (ASIC), or, an or multiple microprocessors (digital singnal processors, DSP), or, one or more field programmable gate arrays (FPGA), or a combination of at least two of these integrated circuit forms.
  • ASIC application specific integrated circuits
  • DSP digital singnal processors
  • FPGA field programmable gate arrays
  • a module in a communication device can be implemented in the form of a processing element scheduler
  • the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call programs.
  • these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the communication device includes: a processor 1110 and an interface 1130 , and the processor 1110 is coupled with the interface 1130 .
  • the interface 1130 is used to enable communication with other devices.
  • the interface 1130 may be a transceiver or an input-output interface.
  • the interface 1130 may be, for example, an interface circuit.
  • the communication device further includes a memory 1120 for storing instructions executed by the processor 1110 or input data required by the processor 1110 to execute the instructions or data generated after the processor 1110 executes the instructions.
  • the method performed by the LDNSR, NWDAF, ECS or EES in the above embodiment can be implemented by the processor 1110 calling the program stored in the memory (which can be the memory 1120 in the LDNSR, NWDAF, ECS or EES, or an external memory). That is, the LDNSR, NWDAF, ECS or EES may include a processor 1110 that executes the method performed by the LDNSR, NWDAF, ECS or EES in the above method embodiments by calling a program in the memory.
  • the processor here may be an integrated circuit with signal processing capability, such as a CPU.
  • the LDNSR, NWDAF, ECS or EES may be implemented by one or more integrated circuits configured to implement the above methods. For example: one or more ASICs, or, one or more microprocessor DSPs, or, one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms. Alternatively, the above implementations may be combined.
  • each module in FIG. 7 to FIG. 10 may be implemented by the processor 1110 in the communication apparatus 1100 shown in FIG. 11 calling the computer-executable instructions stored in the memory 1120 .
  • the function/implementation process of the determination module in FIGS. 7 to 10 may be implemented by the processor 1110 in the communication device 1000 shown in FIG. 11 calling the computer-executed instructions stored in the memory 1120, and the The function/implementation process of the receiving module or the transmitting module can be implemented through the interface 1130 in the communication device 1100 shown in FIG. 11 .
  • the processing unit in the above-mentioned apparatus includes a processor, and the processor is coupled to the memory, the memory is used for storing computer programs or instructions or/or data, and the processor is used for executing the computer programs or instructions and/or data stored in the memory, so that the above The methods in this method embodiment are performed.
  • each unit in the above apparatus can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware.
  • each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing. Function.
  • the processing element may also be called a processor, which may be an integrated circuit with signal processing capability.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.
  • An embodiment of the present application further provides a communication system, which includes: the above-mentioned domain name resolution server network element, a network data analysis function network element, an edge network configuration server network element, and an edge enabling server network element.
  • the embodiment of the present application also provides a computer-readable medium for storing computer program codes, where the computer program includes instructions for executing the communication method of the embodiment of the present application in the above method.
  • the readable medium may be a read-only memory (read-only memory, ROM) or a random access memory (random access memory, RAM), which is not limited in this embodiment of the present application.
  • the present application also provides a computer program product, the computer program product includes instructions that, when executed, enable a domain name resolution server network element, a network data analysis function network element, an edge network configuration server network element, and an edge enablement
  • the server network element performs the operations of the domain name resolution server network element, the network data analysis function network element, the edge network configuration server network element and the edge enablement server network element corresponding to the above method.
  • Embodiments of the present application further provide a system chip, which includes: a processing unit and a communication unit, where the processing unit may be, for example, a processor, and the communication unit may be, for example, an input/output interface, a pin, or a circuit.
  • the processing unit can execute computer instructions, so that the chip in the communication device executes any method for selecting an edge application server provided by the foregoing embodiments of the present application.
  • the computer instructions are stored in a storage unit.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc.
  • the storage unit can also be a storage unit in the terminal located outside the chip, such as ROM or other storage units that can store static information and instructions. Types of static storage devices, RAM, etc.
  • the processor mentioned in any one of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the program execution of the above-mentioned transmission method of feedback information.
  • the processing unit and the storage unit can be decoupled, respectively disposed on different physical devices, and connected in a wired or wireless manner to implement the respective functions of the processing unit and the storage unit, so as to support the system chip to implement the above embodiments various functions in .
  • the processing unit and the memory can also be coupled on the same device.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be ROM, programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM) , EEPROM) or flash memory.
  • Volatile memory can be RAM, which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate Synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous link dynamic random access memory direct memory bus random access memory Access memory
  • direct rambus RAM direct rambus RAM
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请提供了一种边缘应用服务器的选择方法和装置，该方法由域名解析服务器网元执行，包括：获取多个边缘应用服务器的负载状态信息，当接收到来自终端设备的域名服务器DNS请求信息，根据该多个边缘应用服务器的负载状态信息确定该终端设备的第一边缘应用服务器，该多个边缘应用服务器包括所述第一边缘应用服务器。向该终端设备发送DNS响应信息，该DNS响应信息包括该第一边缘应用服务器的标识信息。从而使得域名解析服务器网元根据多个边缘应用服务器的负载状态信息和网络地址为终端设备确定合适的边缘应用服务器。

Description

一种边缘应用服务器的选择方法及装置
本申请要求于2021年04月23日提交中国专利局、申请号为202110463173.7、发明名称为“一种边缘应用服务器的选择方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及边缘计算领域，尤其涉及一种边缘应用服务器的选择方法及装置。
背景技术
移动边缘计算(mobile edge computing，MEC)也可称为多接入边缘计算(multi-access edge computing，MEC)，是一种将数据处理和数据计算下沉到网络边缘侧，实现对网络边缘侧的快速计算，从而实现应用的快速服务响应的技术。MEC为应用开发人员和内容提供商提供了云计算功能，以及在网络边缘的信息技术(information technology，IT)服务环境。业务的多个边缘应用服务器会分别分布式部署在多个MEC平台上，如部署在边缘网络中，业务的每个边缘应用服务器为一定范围内的用户设备(userequipment，UE)提供服务。
域名解析服务器(local DNS Resolve，LDNSR)网元用于处理UE发送的域名***(domain name system，DNS)消息。LDNSR网元收到UE的DNS消息后，LDNSR向会话管理功能(session management function，SMF)网元请求UE的位置信息，LDNSR将UE的位置信息放置到DNS请求消息中的边缘网络配置服务器(edge data network configuration server，ECS)字段，DNS Server根据ECS字段为UE选择具体UE位置更近的一个应用服务器。但是这种方式只是考虑了时延因素。DNS服务器中并不感知应用服务器的负荷状态等信息，无法为UE选择一个更合适的边缘应用服务器。
发明内容
本申请提供一种边缘应用服务器的选择方法，使得域名解析服务器网元根据多个边缘应用服务器的负载状态信息和网络地址为终端设备确定合适的边缘应用服务器。
第一方面，提供了一种边缘应用服务器的选择方法，该方法由域名解析服务器网元执行，包括：获取多个边缘应用服务器的负载状态信息，当接收到来自终端设备的域名服务器DNS请求信息，根据该多个边缘应用服务器的负载状态信息确定该终端设备的第一边缘应用服务器，该多个边缘应用服务器包括该第一边缘应用服务器。向该终端设备发送DNS响应信息，该DNS响应信息包括该第一边缘应用服务器的标识信息。
基于上述技术方案，域名解析服务器网元获取多个边缘应用服务器的负载状态信息，并根据多个边缘应用服务器的负载状态信息为终端设备选择一个合适的边缘应用服务器。与现有技术相比，现有技术仅考虑时延因素，只会为终端设备选择位置较近的边缘应用服务器，因此忽略选择的边缘应用服务器已经处于超负荷状态这一可能性。本申请的技术方 案能够使得域名解析服务器网元在为终端选择边缘应用服务器时考虑到负荷状态信息这个因素，能够克服现有技术的缺点，从而为终端选择一个更合适的边缘应用服务器。
结合第一方面，在第一方面的某些实现方式中，获取多个边缘应用服务器的负载状态信息，包括：向网络数据分析功能网元发送第一请求信息，该第一请求信息用于获取该多个边缘应用服务器的负载状态信息。接收来自该网络数据分析功能网元的该多个边缘应用服务器的负载状态信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够考虑负荷状态这个因素，从而选择合适的边缘应用服务器。
结合第一方面，在第一方面的某些实现方式中，获取多个边缘应用服务器的负载状态信息，包括：接收来自边缘服务功能网元的多个边缘应用服务器的负载状态信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够考虑负荷状态这个因素，从而选择合适的边缘应用服务器。
结合第一方面，在第一方面的某些实现方式中，获取该多个边缘应用服务器的数据网络接入标识DNAI信息，根据该多个边缘应用服务器的负载状态信息确定该终端设备的第一边缘应用服务器，还包括：根据该多个边缘应用服务器的负载状态信息和该多个边缘应用服务器的DNAI信息，确定第一边缘应用服务器。上述技术方案使得在为终端设备选择边缘应用服务器时能够同时考虑时延和负荷状态两个因素，从而选择更合适的边缘应用服务器。
结合第一方面或第一方面的某些实现方式，在第一方面的另一些可能的实现方式中，获取该多个边缘应用服务器的数据网络接入标识DNAI信息，包括：接收来自该边缘服务功能网元的该多个边缘应用服务器的DNAI信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够同时考虑时延和负荷状态两个因素，从而选择更合适的边缘应用服务器。
结合第一方面或第一方面的某些实现方式，在第一方面的另一些可能的实现方式中，发送订阅请求信息，该订阅请求信息用于订阅该多个边缘应用服务器上线事件，其中，该订阅请求信息中携带该多个边缘应用服务器的标识信息。
第二方面，提供了一种边缘应用服务器的选择方法，该方法由网络数据分析功能网元执行，包括：接收来自域名解析服务器网元的第一请求信息，该第一请求信息用于请求该多个边缘应用服务器的负载状态信息。获得该多个边缘应用服务器的负载状态信息，向该域名解析服务器网元发送该多个边缘应用服务器的负载状态信息。
第三方面，提供了一种边缘应用服务器的选择方法，该方法由边缘网络配置服务器网元执行，包括：获得多个边缘应用服务器的负载状态信息，发送该多个边缘应用服务器的负载状态信息。
结合第三方面，在第三方面的某些实现方式中，还包括：接收订阅请求消息，该订阅请求消息用于获取该多个边缘应用服务器的数据网络接入标识DNAI信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够同时考虑时延和负荷状态两个因素，从而选择更合适的边缘应用服务器。
结合第三方面或第三方面的某些实现方式，在第三方面的另一些可能的实现方式中，包括：发送该多个边缘应用服务器的DNAI信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够同时考虑时延和负荷状态两个因素，从而选择更合适的边缘应用服务 器。
结合第三方面或第三方面的某些实现方式，在第三方面的另一些可能的实现方式中，还包括：接收订阅请求信息，该订阅请求信息用于订阅该多个边缘应用服务器上线事件；其中，该订阅请求信息中携带该多个边缘应用服务器的标识信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够同时考虑时延和负荷状态两个因素，从而选择更合适的边缘应用服务器。
第四方面，提供了一种边缘应用服务器的选择方法，该方法由边缘使能服务器网元执行，包括：获得多个边缘应用服务器的负载状态信息，发送该多个边缘应用服务器的负载状态信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够考虑负荷状态这个因素，从而选择合适的边缘应用服务器。
结合第四方面，在第四方面的某些实现方式中，包括：接收第一请求信息，该第一请求信息用于请求该多个边缘应用服务器的负载状态信息。上述技术方案使得在为终端设备选择边缘应用服务器时能够考虑负荷状态这个因素，从而选择合适的边缘应用服务器。
第五方面，提供了一种域名解析服务器网元，包括：获取模块，用于获取多个边缘应用服务器的负载状态信息，确定模块，当接收到来自终端设备的域名服务器DNS请求信息，根据该多个边缘应用服务器的负载状态信息确定该终端设备的第一边缘应用服务器，该多个边缘应用服务器包括该第一边缘应用服务器，发送模块，用于向该终端设备发送DNS响应信息，该DNS响应信息包括该第一边缘应用服务器的标识信息。
结合第五方面，在第五方面的某些实现方式中，该获取模块具体用于：向网络数据分析功能网元发送第一请求信息，该第一请求信息用于获取该多个边缘应用服务器的负载状态信息，接收来自该网络数据分析功能网元的该多个边缘应用服务器的负载状态信息。
结合第五方面或第五方面的某些实现方式，在第五方面的另一些可能的实现方式中，该获取模块具体用于：接收来自边缘服务功能网元的该多个边缘应用服务器的负载状态信息。
结合第五方面或第五方面的某些实现方式，在第五方面的另一些可能的实现方式中，获取该多个边缘应用服务器的数据网络接入标识DNAI信息，该确定模块还用于：根据该多个边缘应用服务器的负载状态信息和该多个边缘应用服务器的DNAI信息，确定该第一边缘应用服务器。
结合第五方面或第五方面的某些实现方式，在第五方面的另一些可能的实现方式中，该获取模块具体用于：接收来自该边缘服务功能网元的该多个边缘应用服务器的DNAI信息。
结合第五方面或第五方面的某些实现方式，在第五方面的另一些可能的实现方式中，该发送模块还用于：发送订阅请求信息，该订阅请求信息用于订阅该多个边缘应用服务器上线事件，其中，该订阅请求信息中携带该多个边缘应用服务器的标识信息。
第六方面，提供了一种网络数据分析功能网元，包括：接收模块，用于接收来自域名解析服务器网元的第一请求信息，该第一请求信息用于请求该多个边缘应用服务器的负载状态信息。获取模块，用于获得该多个边缘应用服务器的负载状态信息。发送模块，用于向该域名解析服务器网元发送该多个边缘应用服务器的负载状态信息。
第七方面，提供了一种边缘网络配置服务器网元，包括：获取模块，用于获得多个边 缘应用服务器的负载状态信息，发送模块，用于发送该多个边缘应用服务器的负载状态信息。
结合第七方面，在第七方面的某些实现方式中，还包括：接收模块，用于接收订阅请求消息，该订阅请求消息用于获取该多个边缘应用服务器的数据网络接入标识DNAI信息。
结合第七方面或第七方面的某些实现方式，在第七方面的另一些可能的实现方式中，该发送模块用于：发送该多个边缘应用服务器的DNAI信息。
结合第七方面或第七方面的某些实现方式，在第七方面的另一些可能的实现方式中，该接收模块还用于：接收订阅请求信息，该订阅请求信息用于订阅该多个边缘应用服务器上线事件，其中，该订阅请求信息中携带该多个边缘应用服务器的标识信息。
第八方面，提供了一种边缘使能服务器网元，包括：获取模块，用于获得多个边缘应用服务器的负载状态信息，发送模块，用于发送该多个边缘应用服务器的负载状态信息。
结合第八方面，在第八方面的某些实现方式中，包括：接收模块，用于接收第一请求信息，该第一请求信息用于请求该多个边缘应用服务器的负载状态信息。
第九方面，提供了一种边缘应用服务器选择装置，包括域名解析服务器网元、网络数据分析功能网元、边缘网络配置服务器网元以及边缘使能服务器网元。该域名解析服务器网元用于执行第一方面所述的方法。或者，该网络数据分析功能网元用于执行第二方面所述的方法。或者，该边缘网络配置服务器网元用于执行第三方面所述的方法。或者，该边缘使能服务器网元用于执行第四方面所述的方法。
第十方面，提供了一种计算机可读存储介质，该计算机存储介质存储有程序指令，当该指令被执行时，使得域名解析服务器网元可以执行第一方面所述的方法。或者，当该指令被执行时，使得网络数据分析功能网元可以执行第二方面所述的方法。或者，当该指令被执行时，使得边缘网络配置服务器可以执行第三方面所述的方法。或者，当该指令被执行时，使得边缘使能服务器网元可以执行第四方面所述的方法。
第十一方面，提供了一种芯片***，包括：至少一个处理器，该至少一个处理器用于执行存储的指令，使得域名解析服务器网元可以执行第一方面所述的方法。或者，该至少一个处理器用于执行存储的指令，使得网络数据分析功能网元可以执行第二方面所述的方法。或者，该至少一个处理器用于执行存储的指令，使得边缘网络配置服务器网元可以执行第三方面所述的方法。或者，该至少一个处理器用于执行存储的指令，使得边缘使能服务器网元可以执行第四方面所述的方法。
第十二方面，提供了一种***，该***包括：如第五方面所述的域名解析服务器网元，和/或，如第六方面所述的网络数据分析功能网元，和/或，如第七方面所述的边缘网络配置服务器网元，和/或，如第八方面所述的边缘使能服务器网元。
附图说明
图1是本申请实施例的网络***架构示意图。
图2本申请实施例提供的应用场景的示意图。
图3是本申请提供的边缘应用服务器的选择方法示意图。
图4是本申请一个实施例提供的边缘应用服务器的选择方法示意图。
图5是本申请又一个实施例提供的边缘应用服务器的选择方法示意图。
图6是本申请又一个实施例提供的边缘应用服务器的选择方法示意图。
图7是本申请实施例提供的一个装置示意框图。
图8是本申请实施例提供的又一个装置示意图。
图9是本申请实施例提供的又一个装置示意图。
图10是本申请实施例提供的又一个装置示意图。
图11是本申请实施例提供的装置示意结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***，例如：第五代(5th generation，5G)***或新无线(new radio，NR)，以及其他未来通信***等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
图1是适用于本申请的一例无线通信***架构的示意性框图。如图1所示，该***架构包括，终端设备，无线接入网设备(radio access network，RAN)、核心网设备以及数据网络(data network，DN)。采用的是基于业务接口(service-based)的表现形式。图1中的终端设备可以用于通过无线空口连接到运营商部署的无线接入网设备，继而通过核心网设备连接到数据网络。无线接入网设备主要用于实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理等功能；核心网设备(也可以称为管理设备)主要用于终端设备的设备注册、安全认证、移动性管理和位置管理等。需要说明的是，图1仅为示例性架构图，除图1中所示功能单元之外，该网络架构还可以包括其它功能单元或功能网元，本申请实施例对此不进行限定。图1以5G***架构为基础，还可以以其他***架构为基础，例如LTE***，本申请实施例对此不进行限定。
图1中所示的终端设备可以为上述的任意一种可能的终端设备，例如，可以为：手机、电脑，还可以为蜂窝电话、无绳电话、会话发起协议(session initiation protocol，SIP)电话、智能电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、电脑、膝上型计算机、手持式通信设备、手持式计算设备、卫星无线设备、无线调制解调器卡、电视机顶盒(set top box，STB)、用户驻地设备(customer premise equipment，CPE)和/或用于在无线***上进行通信的其它设备。上述无线接入网设备可以为接入网(access network，AN)/无线接入网(radio access network，RAN)设备，由多个5G-AN/5G-RAN节点组成的网络，该5G-AN/5G-RAN节点可以为：接入节点(access point，AP)、下一代基站(NR nodeB，gNB)、中心单元(central unit，CU)和分布式单元(distributed unit，DU)分离形态的gNB、收发点(transmission receive point，TRP)、 传输点(transmission point，TP)或某种其它接入节点。
如图1所示的，上述核心网设备可以包括：统一数据管理网元(unified data management，UDM)、接入和移动性管理功能网元(access and mobility management function，AMF)、会话管理功能网元(session management function，SMF)、策略控制功能网元(policy control function，PCF)、应用功能网元(application function，AF)、用户面功能网元(user plane function，UPF)、网络开放功能网元(network exposure function，NEF)、网络仓库功能网元(network repository function，NRF)、网络切片选择功能网元(network slice selection function，NSSF)、鉴权服务器功能网元(authentication server function，AUSF)等。这些功能单元可以独立工作，也可以组合在一起实现某些控制功能，如：AMF、SMF和PCF可以组合在一起作为管理设备，用于完成终端设备的接入鉴权、安全加密、位置注册等接入控制和移动性管理功能，以及用户面传输路径的建立、释放和更改等会话管理功能，以及分析一些切片(slice)相关的数据(如拥塞)、终端设备相关的数据的功能。
在图1的所示的5G网络中，各功能单元之间可以通过下一代网络(next generation，NG)接口建立连接实现通信，如：终端设备通过NR接口与RAN设备建立空口连接，用于传输用户面数据和控制面信令；终端设备可以通过NG接口1(简称N1)与AMF建立控制面信令连接；RAN设备可以通过NG接口3(简称N3)与分流点UPF建立用户面数据连接；RAN设备可以通过NG接口2(简称N2)与AMF建立控制面信令连接；UPF可以通过NG接口6(简称N6)与数据网络交互用户面数据。每个核心网网元可以通过相应的接口与其它核心网网元进行通信。例如，其它核心网网元可以通过Nnssf接口与NSSF进行通信，其它核心网网元可以通过Nnef接口与NEF进行通信等。
需要说明的是，图1所示的部分仅为示例性架构图，除图1所示的部分中所示功能单元之外，该网络架构还可以包括其它功能单元或功能网元，本申请实施例对此不进行限定。
应理解，本申请中的网元之间的接口名称仅是示例性的，网元之间的接口还可以是其它名称，本申请实施例对接口的名称不予限定。
还应理解，本申请实施例中的无线接入网设备可以是用于与终端装置和核心网设备通信的设备，该无线接入网设备可以是LTE***中的演进型基站(evolutional nodeb，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的网络设备或者未来演进的PLMN网络中的接入网设备等，本申请实施例对此并不限定。
图2示出了本申请实施例应用的***架构或场景示意图，如图2所示，该***架构包括终端设备UE、核心网网元(UPF、AMF、SMF、统一数据管理(unified data management，UDM)、PCF)、域名解析服务器(local DNS Resolve，LDNDR)、网络数据分析功能(network data analytics function，NWDAF)边缘使能服务器(edge enabler server，EES)和边缘应用服务器(edge application server，EAS)。其中，边缘使能服务器EES和边缘应用服务器EAS包含在边缘数据网络(edge data network，EDN)中。
边缘数据网络EDN：
一种通用理解为，EDN对应一个数据网络，是一个特别的本地数据网络(local DN)，包含边缘使能功能，可以使用数据网络接入标识符(DN access identifier，DNAI)和数据 网络名称(datanetwork name,DNN)标识，是网络逻辑概念。另一种对于EDN的理解，是EDN是中心云的对等概念，可以理解为是一个本地的数据中心(即地理位置概念)，可以使用数据网络接入标识(data network access identifier，DNAI)来标识，且可以包含多个本地数据网络(local DN)。
边缘应用服务器EAS：
边缘应用服务器EAS为部署在边缘数据网络中的应用。该边缘应用还可以称为“应用实例”。具体是指一个服务器应用程序(例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR))部署运行在EDN的实例(instance)。一个应用可在一个或多个EDN中部署一个或多个EAS，部署运行在不同的EDN中的EAS可以认为是一个应用的不同的EAS，它们可以共享一个域名，也可以与部署在云上的应用使用不同的域名，其中域名可以是全限定域名(fully qualified domain name，FQDN)，可以使用一个任意播放的IP地址，也可以使用不同的IP地址。
可以理解的是，EAS也可以称为边缘应用(服务器)、应用实例、边缘应用实例、多接入边缘计算(multi-access edge computing，MEC)应用(服务器)、EAS功能等。
边缘使能服务器EES：
EES部署在EDN中，并可以为部署在EDN中的应用实例提供一些使能能力，可以更好的支持应用在MEC的部署情况，也可以支持边缘应用的注册、对UE的认证和鉴权，为UE提供应用实例的IP地址信息等，还可以进一步支持获取应用实例的标识和IP地址信息，并进一步向应用实例的标识和IP地址信息发送给边缘数据网络配置服务器。一般情况下，EAS注册到一个EES上，或者，通过管理***将一个EAS的信息配置在一个EES上，该EES称为该EAS关联的EES，EES控制/管理注册/配置在该EES上的EAS。
边缘网络配置服务器(edge data network configuration server，ECS)负责EDN的配置，如向UE提供EES的信息。ECS还可以直接向UE提供应用实例的信息，以及和应用的域名服务器(domain name server，DNS)交互获取应用实例的信息。还可以进一步从其他功能实体获取并保存应用实例和IP地址的信息。
LDNSR：
LDNSR网元用于处理UE发送的DNS消息，LDNSR收到UE的DNS消息后，向SMF网元请求UE的位置信息，即将UE的位置信息放置到DNS请求消息中的ECS字段，DNS Server根据ECS字段为UE选择距离UE位置更近的一个应用服务器。
NWDAF：
NWDAF网元主要收集各个网络功能的性能数据，包括从应用侧收集用户业务体验和应用实例状态等信息。
下面对本申请涉及到的术语进行简单描述。
EAS的负载状态：
EAS的负载状态可以是一个EAS各项***资源运行状态的综合表征，这些资源运行状态包括中央处理器(central processing unit，CPU)使用状态、内存使用状态、输入/输出(input/output，I/O)使用状态、连接用户数、请求连接数、带宽等。当这些资源运行状态达到一定的程度时，可能无法再为用户提供服务，或者无法再接受新用户的接入。此时，可以认为该EAS发生过载(overload)。
可以理解的是，同一个应用的不同EAS的负载状态可以不同，不同应用的不同EAS也可以不同。也就是说，不同应用可以分别独立统计自己对应的EAS的负载情况。例如，针对第一应用的EAS过载时，针对第二应用的EAS也可能是正常状态。
图3是本申请提供的一种边缘应用服务器的选择方法的示意性流程图，该方法包括：
S310，域名解析服务器网元获得多个边缘应用服务器的负载状态信息。
具体的，LDNSR网元获得多个边缘应用服务器EAS的负载状态信息，该负载状态信息可以是实时分析数据，包括EAS的负荷信息、用户业务体验等，本申请实施例对此不作限制。
在一种可能的实现方式中，LDNSR网元向网络数据分析功能网元发送第一请求信息，该第一请求信息用于获取所述多个边缘应用服务器的负载状态信息，相应地，网络数据分析功能网元收集多个边缘应用服务器的负载状态信息，并向域名解析服务器网元发送上述负载状态信息。
在另一种可能的实现方式中，LDNSR网元接收边缘服务功能网元发送的多个边缘应用服务器的负载状态信息。应理解，边缘服务功能网元可以是边缘使能服务器EES功能网元，也可以是边缘网络配置服务器ECS功能网元，本申请实施例对此不作限制。
S320，域名解析服务器网元接收终端设备发送的域名服务器DNS请求消息。
终端设备向LDNSR网元发送域名服务器DNS请求消息，该DNS请求消息用于请求多个边缘应用服务器的数据网络接入标识DNAI信息。
需要说明的是，终端设备可以直接向LDNSR网元发送DNS请求消息，也可以通过其他核心网网元转发该DNS请求消息，应理解，这里的核心网网元可以是SMF网元，也可以是UPF网元，本申请实施例对此不作限制。
S330，域名解析服务器网元根据多个边缘应用服务器的负载状态信息确定终端设备的第一边缘应用服务器。
在一种可能的实现方式中，LDNSR网元获取到多个边缘应用服务器的负载状态信息，并根据负载状态信息从多个边缘应用服务器中确定第一边缘应用服务器，比如，LDNSR网元对于多个边缘应用服务器中的超负荷的边缘应用服务器不予选择，优先选择负荷较小的边缘应用服务器。
在另一种可能的实现方式中，LDNSR网元还获取了多个边缘应用服务器的DNAI信息(网络地址信息)，并根据负载状态信息和DNAI信息从多个边缘应用服务器中确定第一边缘应用服务器。比如，LDNSR网元将在位置较近的多个边缘应用服务器中选择其中负载较小的边缘应用服务器。需要说明的是，通过此技术方案可以使得LDNSR网元同时考虑负载状态信息和时延两个因素，从而为终端设备选择一个更合适的边缘应用服务器。以及本申请其它实施例在考虑负载状况信息选择边缘应用服务器时，也可同时或进一步考虑DNAI信息，来为终端设备选择边缘应用服务器。
S340，域名解析服务器网元向终端设备发送DNS响应信息。
具体的，LDNSR生成DNS响应信息，也可以理解为，LDNSR代替DNS服务器生成DNS响应信息，并将选择的第一EAS实例通过DNS响应消息发送给终端设备。
需要说明的是，LDNSR网元可以直接终端设备向发送DNS响应信息，也可以通过其他核心网网元转发该DNS响应信息，应理解，这里的核心网网元可以是SMF网元，也可 以是用户端口功能UPF网元，本申请实施例对此不作限制。
还需要说明的是，本申请中域名解析服务器网元也可以根据一个边缘应用服务器的负载状态信息确定终端设备的第一边缘应用服务器，换句话说，本申请实施例并不限于“多个边缘应用服务器”，也可以是一个，本申请对此不作限定。
通过上述技术方案，能够使得LDNSR网元能够同时考虑到时延和负载状态信息两个因素，从而为终端选择更合适的边缘应用服务器。
图4是本申请提供的一个实施例的示意性流程图，如图4所示。
可以理解的是，在不作特别说明的情况下，图4所示的实施例与图3所示的实施例中的相同术语表示的含义相同，为避免重复，在此不进行赘述。
S410，域名解析服务器网元向边缘服务功能网元发送订阅请求消息。
该边缘服务功能网元可以是边缘使能服务器EES功能网元，也可以是边缘网络配置服务器ECS功能网元，本申请实施例对此不作限定。
具体的，LDNSR网元向边缘服务功能网元发送订阅请求消息，相应地，边缘服务功能网元接收来自LDNSR网元的订阅请求消息，该订阅请求消息用于订阅多个边缘应用服务器上线事件，上线事件可以理解为服务器的上线情况，或者，多个服务器中上线状态变化。应理解，该订阅请求消息中携带多个EAS实例身份标识(identity，ID)的信息。
S420，域名解析服务器网元接收来自边缘服务功能网元的订阅响应信息。
具体的，订阅请求消息中包含多个EAS实例的ID信息，每个ID代表一种类型的EAS实例，边缘服务功能网元根据这个EAS实例ID向LDNSR网元响应该ID对应的EAS实例的地址信息。应理解，该地址信息包括EAS实例标识的信息，EAS实例的DNAI信息以及EAS实例所在的EES地址等，本申请实施例对此不作限制。
S430，域名解析服务器网元向网络数据分析功能网元发送第一请求信息。
具体的，该第一请求信息用于请求多个边缘应用服务器的负载状态信息，LDNSR网元向网络数据分析功能NWDAF网元请求多个EAS的负载状态信息，应理解，该负载状态信息可以包括EAS实例的负荷信息，也可以包括用户业务体验等，本申请实施例对此不作限制。
还应理解，该第一请求信息中携带多个边缘应用服务器的标识和/或EES地址，本申请实施例对此不作限制。
在一种可能的实现方式中，该第一请求信息中还可以包括请求的多个EAS实例标识。比如，若LDNSR需要获取多个EAS的负载状态信息，可以将这多个EAS的实例标识包含在请求消息中发送给NWDAF网元，也可以通过其他消息发送给NWDAF网元，应理解，本申请实施例对此不作限定。
S440，网络数据分析功能网元网元通过边缘服务功能网元获得多个EAS边缘应用服务器的负载状态信息。
具体的，多个EAS分布部署在多个EES上，那么NWDAF网元需要分别向部署了EAS的EES收集EAS实例的负载状态信息。NWDAF网元根据多个EAS的EES地址向EES网元收集EAS应用ID对应的应用实例的负载状态信息。相应地，EES网元将收集到的EAS实例的负载状态信息发送至NWDAF网元。
比如，ID为1和2的EAS部署在EES1上，ID为3和4的EAS部署在EES2上，那 么NWDAF网元根据EES1的地址向EES1收集ID为1和2的EAS实例的负载状态信息，相对应地，根据EES2的地址向EES2收集ID为3和4的EAS实例的负载状态信息。
应理解，负载状态信息可以是EAS实例的负荷信息，也可以是用户业务体验，应理解，本申请对此不作限制。
S450，NWDAF网元向LDNSR网元发送多个边缘应用服务器的负载状态信息。
应理解，该负载状态信息可以包括EAS实例的负荷信息、用户业务体验等，本申请实施例对此不作限制。
S460，终端设备向LDNSR网元发送DNS请求消息，相应地，LDNSR网元接收到来自终端设备的DNS请求消息。
S470，LDNSR网元根据多个边缘应用服务器网络地址和负载状态信息确定第一边缘应用服务器。
具体的，LDNSR网元将UE的位置信息添加到UE发送的DNS请求消息中的ECS字段中，DNS服务器根据UE位置信息为UE选择多个距离UE较近的应用服务器。LDNSR网元根据获得的EAS的负载状态信息确定距离UE较近的EAS中负载最小的EAS为UE访问的第一边缘应用服务器。
S480，LDNSR向终端设备发送DNS响应信息。
具体的，LDNSR生成DNS响应信息，将确定的第一边缘应用服务器通过DNS响应信息发送给UE。需要说明，LDNSR生成响应信息可以理解为LDNSR代替DNS服务器生成DNS响应信息。
通过上述技术方案，能够使得LDNSR网元能够同时考虑时延和负荷状态两个因素，从而为终端选择更合适的边缘应用服务器。
图5是本申请提供的又一个实施例的示意性流程图，如图5所示。
可以理解的是，在不作特别说明的情况下，图5所示的实施例与图3所示的实施例中的相同术语表示的含义相同，为避免重复，在此不进行赘述。
S510，域名解析服务器网元向边缘网络配置服务器网元发送订阅请求信息。
S520，边缘网络配置服务器网元向边缘使能服务器网元发送订阅响应信息。
需要说明的是，步骤S510-S520与上述步骤S410-S420执行相应的操作，在此不再赘述。
S530，域名解析服务器网元向边缘使能服务器网元发送第一请求信息。
具体的，第一请求信息用于请求多个边缘应用服务器的负载状态信息，LDNSR网元向EES网元请求多个EAS的负载状态信息，应理解，该负载状态信息可以包括EAS实例的负荷信息、用户业务体验等，本申请实施例对此不作限制。
还应理解，该第一请求信息中携带多个边缘应用服务器的身份标识和/或EES地址，本申请实施例对此不作限制。
在一种可能的实现方式中，该第一请求信息中还可以包括请求的多个EAS实例标识。
在另一种可能的实现方式中，该第一请求信息中还可以携带上报条件的信息，例如周期上报，上报阈值等，应理解，本申请实施例对于上报条件不作限制。其中，周期上报可以理解为设定一个具体的时间周期，当EES网元接收到周期上报，当达到这个设定的时间周期时，那么EES网元向LDNSR网元上报(发送)请求的多个EAS的负载状态信息。 上报阈值可以理解为设定一个阈值，当EES网元接收到阈值上报时，当达到这个设定的阈值时，那么EES网元向LDNSR网元上报(发送)请求的多个EAS的负载状态信息。
S540，边缘使能服务器网元向域名解析服务器网元发送多个边缘应用服务器的负载状态信息。
该负载状态信息可以包括EAS实例的负荷信息、用户业务体验等，本申请实施例对此不作限制。
在另一种可能的实现方式中，EES网元也可以向LDNSR网元上报多个边缘应用服务器的负载状态信息。
举例说明，若EES网元在上述步骤S530中接收到上报条件的信息，并且当满足上述上报条件时，EES向LDNSR网元上报多个边缘应用服务器的负载状态信息。
具体的，若EES网元在上述步骤S530中接收到的上报条件为周期上报，可以理解为，假设周期上报的时间设置为100s，那么EES网元则在达到100s的周期时间设定后向LDNSR网元上报多个边缘应用服务器的负载状态信息。
若EES网元在上述步骤S530中接收到的上报条件为阈值上报，那么EES网元则在达到设定阈值后向LDNSR网元上报多个边缘应用服务器的负载状态信息。
应理解，满足上述上报条件可以理解为满足周期上报、上报阈值中的至少一种，即EES网元也可以在同时满足周期上报和上报阈值的条件时，向LDNSR网元上报负载状态信息。
还应理解上述上报条件也可以包括其他可能的设定上报条件，本申请实施例对此不作限制。
在另一种可能的实现方式中，若EES网元在上述步骤S530中未接收到上报条件的信息，换句话说，上述第一请求信息中未携带上报条件，那么EES网元直接向LDNSR网元发送边缘应用服务器的负载状态信息。
在另一种可能的实现方式中，若EES网元在上述步骤S530中接收到上报条件，但是没有满足上述上报条件时，那么EES网元则不会向LDNSR网元上报边缘应用服务器的负载状态信息。
S550，终端设备发送DNS请求消息，相应地，LDNSR网元接收来自终端设备的DNS请求消息。
S560，LDNSR网元根据多个边缘应用服务器的网络地址信息和负载状态信息确定第一边缘应用服务器。
S570，LDNSR发送DNS响应信息。
需要说明的是，步骤S550-S570与上述步骤S460-S480执行相应的操作，本申请在此不再赘述。
通过上述技术方案，能够使得LDNSR网元能够同时考虑时延和负荷状态两个因素，从而为终端选择合适的边缘应用服务器。
图6是本申请提供的又一个实施例的示意性流程图。
可以理解的是，在不作特别说明的情况下，图6所示的实施例与图3所示的实施例中的相同术语表示的含义相同，为避免重复，在此不进行赘述。
如图6所示，为便于区分，对实施例中的多个EES、EAS、EDN进行编号，从图中可 以看出，EES1主要管理EAS1和EAS2的负载状态信息，EES2主要管理EAS3和EAS4的负载状态信息。并且，EES1及其管理的EAS1和EAS2均部署在EDN1中，而EES2及其管理的EAS3和EAS4均部署在EDN2中。
S610，边缘使能服务器网元向边缘网络配置服务器网元发送各自管理的边缘应用服务器的负载状态信息以及关联的网络地址信息。
具体的，EES网元获取EDN中各EAS边缘应用服务器的负载状态信息，负载状态信息可以是CPU、图形处理器(graphics processing unit，GPU)以及内存的负载状况等，本申请实施例在此不作限制。
例如，在S610a中，EES1获取EDN1中的EAS1、EAS2的负载状态信息，在S610b中，EES2获取EDN2中的EAS1、EAS3的负载状态信息。应理解，在EES上部署的EAS的数量仅是举例说明。相应的，EDN的数量也仅是举例说明，可以是1个或者多个，本申请实施例对此不作限制。
在另一种可能的实现方式中，EAS也可以直接向ECS网元上报EAS的负载状态信息以及EAS关联的DNAI信息，也就是说，无需通过EES网元向ECS网元发送负载状态信息以及关联的DNAI信息。
S620，边缘网络配置服务器网元获取多个边缘应用服务器的负载状态信息。
S630，边缘网络配置服务器网元向核心网网元发送多个边缘应用服务器的负载状态信息、以及EAS关联的DNAI信息，相应地，核心网网元保存上述信息。
具体的，ECS网元可以通过增强现有AF influence traffic routing机制(即，应用主动触发业务流路由规则)的方式将上述信息发送给核心网网元，也可以通过其他方式，本申请实施例对此不作限制。
应理解，核心网网元可以是LDNSR网元、SMF网元、PCF网元、NRF网元或者UPF网元等，本申请实施例对此不作限定。
S640，终端设备向核心网网元发送EAS地址请求信息，用于获取多个边缘应用服务器的地址信息。
具体的，UE可以向核心网网元发送DNS请求信息，或者，UE也可以发送service provisioning请求信息，亦或者，UE也可以发送EAS discovery请求信息等，应理解，本申请对具体消息名称不作限制。
应理解，步骤S640是一个可选的步骤，也就是说，UE可以不向核心网网元发送EAS地址请求信息。
S650，核心网网元根据多个边缘应用服务器的网络地址信息和负载状态信息确定第一边缘应用服务器。
具体的，核心网网元根据保存的多个EAS的负载状态信息确定UE接入的EAS列表，或者确定UE接入的多个EAS对应的EES。若有多个EDN里部署了UE请求的多个边缘应用服务器，5GC网元根据多个EAS的负载状态信息和关联的DNAI信息，确定距离UE较近的多个EAS，并将其中负载最小的EAS确定为UE需要访问的EAS。
S660，核心网网元向终端设备发送EAS的地址信息。
在一种可能的实现方式中，核心网网元将确定的EAS对应的EES的连接信息发送给UE，或者核心网网元将EAS的地址信息发送给UE。
在另一种可能的实现方式中，核心网网元将多个EES的连接信息以及第一请求信息中请求的多个EAS的负载状态信息发送给UE，由UE根据多个EAS的负载状态信息以及关联的DNAI信息确定第一边缘应用服务器。
通过上述技术方案，能够使得LDNSR网元能够同时考虑时延和负荷状态两个因素，从而为终端选择合适的边缘应用服务器。
本文中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
可以理解的是，上述各个方法实施例中，由各个设备实现的方法和操作，也可以由对应设备的部件(例如芯片或者电路)实现。
上述主要从各个交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发送端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以使用硬件的形式实现，也可以使用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以使用对应各个功能划分各个功能模块为例进行说明。
应理解，本申请实施例中的具体的例子只是为了帮助本领域技术人员更好地理解本申请实施例，而非限制本申请实施例的范围。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
以上，结合图3至图6详细说明了本申请实施例提供的方法。以下，结合图7至图10详细说明本申请实施例提供的装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
图7示出了本申请实施例的域名解析服务器LDNSR的装置700的示意性框图。
应理解，该装置700可以对应于图3所示的实施例中的LDNSR，可以具有方法中的LDNSR的任意功能。该装置700，包括获取模块710、确定模块720和发送模块730。
该获取模块710，用于获取多个边缘应用服务器的负载状态信息；
该确定模块720，当接收到来自终端设备的域名服务器DNS请求信息，根据该多个边缘应用服务器的负载状态信息确定该终端设备的第一边缘应用服务器，该多个边缘应用服务器包括该第一边缘应用服务器；
该发送模块730，用于向该终端设备发送DNS响应信息，该DNS响应信息包括该第一边缘应用服务器的标识信息。
在一种可能的实现方式中，该获取模块710具体用于：
向网络数据分析功能网元发送第一请求信息，该第一请求信息用于获取该多个边缘应用服务器的负载状态信息；
接收来自该网络数据分析功能网元的该多个边缘应用服务器的负载状态信息。
在另一种可能的实现方式中，该获取模块710具体用于：
接收来自边缘服务功能网元的该多个边缘应用服务器的负载状态信息。
在另一种可能的实现方式中，获取该多个边缘应用服务器的数据网络接入标识DNAI信息；
该确定模块720还用于：
根据该多个边缘应用服务器的负载状态信息和该多个边缘应用服务器的该DNAI信息，确定该第一边缘应用服务器。
在另一种可能的实现方式中，该获取模块710具体用于：
接收来自该边缘服务功能网元的该多个边缘应用服务器的DNAI信息。
在另一种可能的实现方式中，该发送模块730还用于：
发送订阅请求信息，该订阅请求信息用于订阅该多个边缘应用服务器上线事件，其中，该订阅请求信息中携带所述多个边缘应用服务器的标识信息。
图8示出了本申请实施例的网络数据分析功能网元NWDAF的装置800的示意性框图。
应理解，该装置800可以对应于图3所示的实施例中的NWDAF，可以具有方法中的NWDAF的任意功能。该装置800，包括接收模块810、获取模块820和发送模块830。
该接收模块810，用于接收来自域名解析服务器网元的第一请求信息，该第一请求信息用于请求该多个边缘应用服务器的负载状态信息；
该获取模块820，用于获得该多个边缘应用服务器的负载状态信息；
该发送模块830，用于向该域名解析服务器网元发送该多个边缘应用服务器的负载状态信息。
图9示出了本申请实施例的边缘网络配置服务器ECS的装置900的示意性框图。
应理解，该装置900可以对应于图3至图6所示的实施例中的ECS，可以具有方法中的ECS的任意功能。该装置900，包括获取模块910、发送模块920和接收模块930。
该获取模块910，用于获得多个边缘应用服务器的负载状态信息；
该发送模块920，用于发送该多个边缘应用服务器的负载状态信息。
在一种可能的实现方式中，装置900还包括：
该接收模块930，用于接收订阅请求消息，该订阅请求消息用于获取该多个边缘应用服务器的数据网络接入标识DNAI信息。
在另一种可能的实现方式中，该发送模块920用于：发送所述多个边缘应用服务器的DNAI信息。
在另一种可能的实现方式中，该接收模块930还用于：
接收订阅请求信息，该订阅请求信息用于订阅该多个边缘应用服务器上线事件，其中，该订阅请求信息中携带该多个边缘应用服务器的标识信息。
图10示出了本申请实施例的边缘使能服务器EES的装置1000的示意性框图。
应理解，该装置1000可以对应于图3至图6所示的实施例中的EES，可以具有方法 中的EES的任意功能。该装置1000，包括获取模块1010、发送模块1020和接收模块1030。
该获取模块1010，用于获得多个边缘应用服务器的负载状态信息；
该发送模块1020，用于发送该多个边缘应用服务器的负载状态信息。
在一种可能的实现方式中，该装置1000还包括：
该接收模块1030，用于接收第一请求信息，该第一请求信息用于请求该多个边缘应用服务器的负载状态信息。
应理解以上通信装置中模块的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且通信装置中的模块可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分模块以软件通过处理元件调用的形式实现，部分模块以硬件的形式实现。例如，各个模块可以为单独设立的处理元件，也可以集成在通信装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由通信装置的某一个处理元件调用并执行该模块的功能。此外这些模块全部或部分可以集成在一起，也可以独立实现。这里所述的处理元件又可以成为处理器，可以是一种具有信号的处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个模块可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
在一个例子中，以上任一通信装置中的模块可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(application specific integrated circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)，或这些集成电路形式中至少两种的组合。再如，当通信装置中的模块可以通过处理元件调度程序的形式实现时，该处理元件可以是通用处理器，例如中央处理器(central processing unit，CPU)或其它可以调用程序的处理器。再如，这些模块可以集成在一起，以片上***(system-on-a-chip，SOC)的形式实现。
参考图11，为本申请实施例提供的一种通信装置示意图，用于实现以上实施例中LDNSR、NWDAF、ECS或EES的操作。如图11所示，该通信装置包括：处理器1110和接口1130，处理器1110与接口1130耦合。接口1130用于实现与其他设备进行通信。接口1130可以为收发器或输入输出接口。接口1130例如可以是接口电路。可选地，该通信装置还包括存储器1120，用于存储处理器1110执行的指令或存储处理器1110运行指令所需要的输入数据或存储处理器1110运行指令后产生的数据。
以上实施例中LDNSR、NWDAF、ECS或EES执行的方法可以通过处理器1110调用存储器(可以是LDNSR、NWDAF、ECS或EES中的存储器1120，也可以是外部存储器)中存储的程序来实现。即，LDNSR、NWDAF、ECS或EES可以包括处理器1110，该处理器1110通过调用存储器中的程序，以执行以上方法实施例中LDNSR、NWDAF、ECS或EES执行的方法。这里的处理器可以是一种具有信号的处理能力的集成电路，例如CPU。LDNSR、NWDAF、ECS或EES可以通过配置成实施以上方法的一个或多个集成电路来实现。例如：一个或多个ASIC，或，一个或多个微处理器DSP，或，一个或者多个FPGA等，或这些集成电路形式中至少两种的组合。或者，可以结合以上实现方式。
具体的，图7至图10中各模块的功能/实现过程可以通过图11所示的通信装置1100 中的处理器1110调用存储器1120中存储的计算机可执行指令来实现。或者，图7至图10中的确定模块的功能/实现过程可以通过图11所示的通信装置1000中的处理器1110调用存储器1120中存储的计算机执行指令来实现，图7至图10中的接收模块或发送模块的功能/实现过程可以通过图11中所示的通信装置1100中的接口1130来实现。
应理解，上述装置中处理单元包括处理器，处理器与存储器耦合，存储器用于存储计算机程序或指令或者和/或数据，处理器用于执行存储器存储的计算机程序或指令和/或者数据，使得上文方法实施例中的方法被执行。
还应理解，以上装置中单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。且装置中的单元可以全部以软件通过处理元件调用的形式实现；也可以全部以硬件的形式实现；还可以部分单元以软件通过处理元件调用的形式实现，部分单元以硬件的形式实现。例如，各个单元可以为单独设立的处理元件，也可以集成在装置的某一个芯片中实现，此外，也可以以程序的形式存储于存储器中，由装置的某一个处理元件调用并执行该单元的功能。这里该处理元件又可以称为处理器，可以是一种具有信号处理能力的集成电路。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路实现或者以软件通过处理元件调用的形式实现。
本申请实施例还提供了一种通信***，该通信***包括：上述域名解析服务器网元、网络数据分析功能网元、边缘网络配置服务器网元和边缘使能服务器网元。
本申请实施例还提供了一种计算机可读介质，用于存储计算机程序代码，该计算机程序包括用于执行上述方法中本申请实施例的通信方法的指令。该可读介质可以是只读存储器(read-only memory，ROM)或随机存取存储器(random access memory，RAM)，本申请实施例对此不做限制。
本申请还提供了一种计算机程序产品，该计算机程序产品包括指令，当该指令被执行时，以使得域名解析服务器网元、网络数据分析功能网元、边缘网络配置服务器网元和边缘使能服务器网元执行对应于上述方法的域名解析服务器网元、网络数据分析功能网元、边缘网络配置服务器网元和边缘使能服务器网元的操作。
本申请实施例还提供了一种***芯片，该***芯片包括：处理单元和通信单元，该处理单元，例如可以是处理器，该通信单元例如可以是输入/输出接口、管脚或电路等。该处理单元可执行计算机指令，以使该通信装置内的芯片执行上述本申请实施例提供的任一种边缘应用服务器的选择方法。
可选地，该计算机指令被存储在存储单元中。
可选地，该存储单元为该芯片内的存储单元，如寄存器、缓存等，该存储单元还可以是该终端内的位于该芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。其中，上述任一处提到的处理器，可以是一个CPU，微处理器，ASIC，或一个或多个用于控制上述的反馈信息的传输方法的程序执行的集成电路。该处理单元和该存储单元可以解耦，分别设置在不同的物理设备上，通过有线或者无线的方式连接来实现该处理单元和该存储单元的各自的功能，以支持该***芯片实现上述实施例中的各种功能。或者，该处理单元和该存储器也可以耦合在同一个设备上。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包 括易失性和非易失性存储器两者。其中，非易失性存储器可以是ROM、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是RAM，其用作外部高速缓存。RAM有多种不同的类型，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种边缘应用服务器的选择方法，其特征在于，所述方法由域名解析服务器网元执行，包括：
    获取多个边缘应用服务器的负载状态信息；
    当接收到来自终端设备的域名服务器DNS请求信息，根据所述多个边缘应用服务器的负载状态信息确定所述终端设备的第一边缘应用服务器，所述多个边缘应用服务器包括所述第一边缘应用服务器；
    向所述终端设备发送DNS响应信息，所述DNS响应信息包括所述第一边缘应用服务器的标识信息。
  2. 根据权利要求1所述的方法，其特征在于，所述获取多个边缘应用服务器的负载状态信息，包括：
    向网络数据分析功能网元发送第一请求信息，所述第一请求信息用于获取所述多个边缘应用服务器的负载状态信息；
    接收来自所述网络数据分析功能网元的所述多个边缘应用服务器的负载状态信息。
  3. 根据权利要求1所述的方法，其特征在于，所述获取多个边缘应用服务器的负载状态信息，包括：
    接收来自边缘服务功能网元的所述多个边缘应用服务器的负载状态信息。
  4. 根据权利要求1所述的方法，其特征在于，
    获取所述多个边缘应用服务器的数据网络接入标识DNAI信息；
    所述根据所述多个边缘应用服务器的负载状态信息确定所述终端设备的第一边缘应用服务器，还包括：
    根据所述多个边缘应用服务器的负载状态信息和所述多个边缘应用服务器的所述DNAI信息，确定所述第一边缘应用服务器。
  5. 根据权利要求4所述的方法，其特征在于，所述获取所述多个边缘应用服务器的数据网络接入标识DNAI信息，包括：
    接收来自所述边缘服务功能网元的所述多个边缘应用服务器的DNAI信息。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    发送订阅请求信息，所述订阅请求信息用于订阅所述多个边缘应用服务器上线事件，其中，所述订阅请求信息中携带所述多个边缘应用服务器的标识信息。
  7. 一种边缘应用服务器的选择方法，其特征在于，所述方法由网络数据分析功能网元执行，包括：
    接收来自域名解析服务器网元的第一请求信息，所述第一请求信息用于请求所述多个边缘应用服务器的负载状态信息；
    获得所述多个边缘应用服务器的负载状态信息；
    向所述域名解析服务器网元发送所述多个边缘应用服务器的负载状态信息。
  8. 一种边缘应用服务器的选择方法，其特征在于，所述方法由边缘网络配置服务器网元执行，包括：
    获得多个边缘应用服务器的负载状态信息；
    发送所述多个边缘应用服务器的负载状态信息。
  9. 根据权利要求8所述的方法，其特征在于，还包括：
    接收订阅请求消息，所述订阅请求消息用于获取所述多个边缘应用服务器的数据网络接入标识DNAI信息。
  10. 根据权利要求8或9所述的方法，其特征在于，包括：
    发送所述多个边缘应用服务器的DNAI信息。
  11. 根据权利要求8至10中任一项所述的方法，其特征在于，还包括：
    接收订阅请求信息，所述订阅请求信息用于订阅所述多个边缘应用服务器上线事件；其中，所述订阅请求信息中携带所述多个边缘应用服务器的标识信息。
  12. 一种边缘应用服务器的选择方法，其特征在于，所述方法由边缘使能服务器网元执行，包括：
    获得多个边缘应用服务器的负载状态信息；
    发送所述多个边缘应用服务器的负载状态信息。
  13. 根据权利要求12所述的方法，其特征在于，包括：
    接收第一请求信息，所述第一请求信息用于请求所述多个边缘应用服务器的负载状态信息。
  14. 一种域名解析服务器网元，其特征在于，包括：
    获取模块，用于获取多个边缘应用服务器的负载状态信息；
    确定模块，当接收到来自终端设备的域名服务器DNS请求信息，根据所述多个边缘应用服务器的负载状态信息确定所述终端设备的第一边缘应用服务器，所述多个边缘应用服务器包括所述第一边缘应用服务器；
    发送模块，用于向所述终端设备发送DNS响应信息，所述DNS响应信息包括所述第一边缘应用服务器的标识信息。
  15. 根据权利要求14所述的域名解析服务器网元，其特征在于，所述获取模块具体用于：
    向网络数据分析功能网元发送第一请求信息，所述第一请求信息用于获取所述多个边缘应用服务器的负载状态信息；
    接收来自所述网络数据分析功能网元的所述多个边缘应用服务器的负载状态信息。
  16. 根据权利要求14所述的域名解析服务器网元，其特征在于，所述获取模块具体用于：
    接收来自边缘服务功能网元的所述多个边缘应用服务器的负载状态信息。
  17. 根据权利要求14所述的域名解析服务器网元，其特征在于，
    获取所述多个边缘应用服务器的数据网络接入标识DNAI信息；
    所述确定模块还用于：
    根据所述多个边缘应用服务器的负载状态信息和所述多个边缘应用服务器的所述DNAI信息，确定所述第一边缘应用服务器。
  18. 根据权利要求17所述的域名解析服务器网元，其特征在于，所述获取模块具体用于：
    接收来自所述边缘服务功能网元的所述多个边缘应用服务器的DNAI信息。
  19. 根据权利要求14至18中任一项所述的域名解析服务器网元，其特征在于，所述发送模块还用于：
    发送订阅请求信息，所述订阅请求信息用于订阅所述多个边缘应用服务器上线事件，其中，所述订阅请求信息中携带所述多个边缘应用服务器的标识信息。
  20. 一种网络数据分析功能网元，其特征在于，包括：
    接收模块，用于接收来自域名解析服务器网元的第一请求信息，所述第一请求信息用于请求所述多个边缘应用服务器的负载状态信息；
    获取模块，用于获得所述多个边缘应用服务器的负载状态信息；
    发送模块，用于向所述域名解析服务器网元发送所述多个边缘应用服务器的负载状态信息。
  21. 一种边缘网络配置服务器网元，其特征在于，包括：
    获取模块，用于获得多个边缘应用服务器的负载状态信息；
    发送模块，用于发送所述多个边缘应用服务器的负载状态信息。
  22. 根据权利要求21所述的边缘网络配置服务器网元，其特征在于，还包括：
    接收模块，用于接收订阅请求消息，所述订阅请求消息用于获取所述多个边缘应用服务器的数据网络接入标识DNAI信息。
  23. 根据权利要求21或22所述的边缘网络配置服务器网元，其特征在于，所述发送模块用于：
    发送所述多个边缘应用服务器的DNAI信息。
  24. 根据权利要求21至23中任一项所述的边缘网络配置服务器网元，其特征在于，所述接收模块还用于：
    接收订阅请求信息，所述订阅请求信息用于订阅所述多个边缘应用服务器上线事件，其中，所述订阅请求信息中携带所述多个边缘应用服务器的标识信息。
  25. 一种边缘使能服务器网元，其特征在于，包括：
    获取模块，用于获得多个边缘应用服务器的负载状态信息；
    发送模块，用于发送所述多个边缘应用服务器的负载状态信息。
  26. 根据权利要求25所述的边缘使能服务器网元，其特征在于，包括：
    接收模块，用于接收第一请求信息，所述第一请求信息用于请求所述多个边缘应用服务器的负载状态信息。
  27. 一种边缘应用服务器选择装置，其特征在于，包括域名解析服务器网元、网络数据分析功能网元、边缘网络配置服务器网元以及边缘使能服务器网元，
    所述域名解析服务器网元用于执行如权利要求1至6中任一项所述的方法；或者，
    所述网络数据分析功能网元用于执行如权利要求7所述的方法；或者，
    所述边缘网络配置服务器网元用于执行如权利要求8至11中任一项所述的方法；或者，
    所述边缘使能服务器网元用于执行如权利要求12或13所述的方法。
  28. 一种计算机可读存储介质，其特征在于，所述计算机存储介质存储有程序指令，当所述指令被执行时，使得域名解析服务器网元可以执行如权利要求1至6中任一项权利 要求所述的方法；或者，
    当所述指令被执行时，使得网络数据分析功能网元可以执行如权利要求7所述的方法；或者，
    当所述指令被执行时，使得边缘网络配置服务器可以执行如权利要求8至11中任一项所述的方法；或者，
    当所述指令被执行时，使得边缘使能服务器网元可以执行如权利要求12或13所述的方法。
  29. 一种芯片***，其特征在于，包括：至少一个处理器，所述至少一个处理器用于执行存储的指令，使得域名解析服务器网元可以执行如权利要求1至6中任一项权利要求所述的方法；或者，
    所述至少一个处理器用于执行存储的指令，使得网络数据分析功能网元可以执行如权利要求7所述的方法；或者，
    所述至少一个处理器用于执行存储的指令，使得边缘网络配置服务器网元可以执行如权利要求8至11中任一项所述的方法；或者，
    所述至少一个处理器用于执行存储的指令，使得边缘使能服务器网元可以执行如权利要求12或13所述的方法。
  30. 一种***，其特征在于，所述***包括：
    如权利要求14至19中任一项所述的域名解析服务器网元；和/或，
    如权利要求20所述的网络数据分析功能网元；和/或，
    如权利要求21至24中任一项所述的边缘网络配置服务器网元；和/或，
    如权利要求25或26所述的边缘使能服务器网元。
PCT/CN2022/086550 2021-04-23 2022-04-13 一种边缘应用服务器的选择方法及装置 WO2022222817A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22790925.6A EP4319093A4 (en) 2021-04-23 2022-04-13 METHOD AND APPARATUS FOR SELECTING AN EDGE APPLICATION SERVER
US18/491,354 US20240056496A1 (en) 2021-04-23 2023-10-20 Method and Apparatus for Selecting Edge Application Server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110463173.7 2021-04-23
CN202110463173.7A CN115334081A (zh) 2021-04-23 2021-04-23 一种边缘应用服务器的选择方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/491,354 Continuation US20240056496A1 (en) 2021-04-23 2023-10-20 Method and Apparatus for Selecting Edge Application Server

Publications (1)

Publication Number Publication Date
WO2022222817A1 true WO2022222817A1 (zh) 2022-10-27

Family

ID=83721943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/086550 WO2022222817A1 (zh) 2021-04-23 2022-04-13 一种边缘应用服务器的选择方法及装置

Country Status (4)

Country Link
US (1) US20240056496A1 (zh)
EP (1) EP4319093A4 (zh)
CN (1) CN115334081A (zh)
WO (1) WO2022222817A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117202311A (zh) * 2023-09-18 2023-12-08 成都汉度科技有限公司 边缘物联代理实体的配网方法、***及设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116112865B (zh) * 2023-01-17 2023-10-03 广州爱浦路网络技术有限公司 基于用户设备位置的边缘应用服务器选择方法、计算机装置和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103997526A (zh) * 2014-05-21 2014-08-20 中国科学院计算技术研究所 一种可扩展负载均衡***和方法
CN106933671A (zh) * 2015-12-29 2017-07-07 华为技术有限公司 一种进行伸缩处理的方法、装置和***
JP2017123116A (ja) * 2016-01-08 2017-07-13 日本電気株式会社 負荷分散システム、負荷分散装置、負荷分散方法、および、プログラム
CN112055052A (zh) * 2020-08-05 2020-12-08 中国建设银行股份有限公司 物联网***的服务探活及信息分发方法、***和介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112291381B (zh) * 2017-11-13 2022-01-21 华为技术有限公司 应用服务器切换方法、设备及***
US10778757B1 (en) * 2018-06-18 2020-09-15 Amazon Technologies, Inc. Load balancing traffic via dynamic DNS record TTLs
US10855596B2 (en) * 2018-11-20 2020-12-01 Microsoft Technology Licensing, Llc Load balancing among multiple endpoint computing systems of a domain
US11218438B2 (en) * 2019-04-12 2022-01-04 Huawei Technologies Co., Ltd. System, apparatus and method to support data server selection
KR20210119849A (ko) * 2020-03-25 2021-10-06 삼성전자주식회사 에지 컴퓨팅 시스템을 위한 통신 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103997526A (zh) * 2014-05-21 2014-08-20 中国科学院计算技术研究所 一种可扩展负载均衡***和方法
CN106933671A (zh) * 2015-12-29 2017-07-07 华为技术有限公司 一种进行伸缩处理的方法、装置和***
JP2017123116A (ja) * 2016-01-08 2017-07-13 日本電気株式会社 負荷分散システム、負荷分散装置、負荷分散方法、および、プログラム
CN112055052A (zh) * 2020-08-05 2020-12-08 中国建设银行股份有限公司 物联网***的服务探活及信息分发方法、***和介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC) (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.748, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.1.0, 30 October 2020 (2020-10-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 243, XP051961594 *
FUTUREWEI, ITRI: "Solution for KI#1 - Application Server Discovery with DNS and IP Anycast (FS_enh_EC)", 3GPP DRAFT; S2-2000258, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, Korea; 20200113, 6 January 2020 (2020-01-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051841784 *
See also references of EP4319093A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117202311A (zh) * 2023-09-18 2023-12-08 成都汉度科技有限公司 边缘物联代理实体的配网方法、***及设备
CN117202311B (zh) * 2023-09-18 2024-04-23 成都汉度科技有限公司 边缘物联代理实体的配网方法、***及设备

Also Published As

Publication number Publication date
EP4319093A4 (en) 2024-02-14
US20240056496A1 (en) 2024-02-15
CN115334081A (zh) 2022-11-11
EP4319093A1 (en) 2024-02-07

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
JP7041212B2 (ja) 仮想化されたモバイルコアネットワークへの接続
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
WO2021031562A1 (zh) 一种获取信息的方法及装置
WO2020108002A1 (zh) 一种传输策略确定方法、策略控制方法及装置
US20210385284A1 (en) Session establishment method and apparatus
US20230070712A1 (en) Communication method, apparatus, and system
WO2022222817A1 (zh) 一种边缘应用服务器的选择方法及装置
CN113115332B (zh) 一种upf确定方法及装置
WO2019024650A1 (zh) 一种资源配置方法和装置
US20230061152A1 (en) Communication method, apparatus, and system
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2022170518A1 (zh) 一种确定终端设备的地址的方法及装置、网络设备
US9560583B2 (en) Gateway selection based on geographical location
WO2023213177A1 (zh) 一种通信方法及装置
CN113709905A (zh) 一种通信方法、装置及计算机可读存储介质
WO2023035925A1 (zh) 一种业务处理方法、装置和***
US20220394595A1 (en) Communication method, apparatus, and system
WO2022067736A1 (zh) 一种通信方法及装置
CN113454959B (zh) 控制平面网络功能、用户平面网络功能和使用其的分组处理方法
WO2021244622A1 (zh) 一种通信方法、装置及计算机可读存储介质
WO2022001972A1 (zh) Dns请求的解析方法、通信装置及通信***
WO2024012230A1 (zh) 通信方法及装置
WO2023143212A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22790925

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022790925

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022790925

Country of ref document: EP

Effective date: 20231031

NENP Non-entry into the national phase

Ref country code: DE