WO2023109937A1 - 确定应用服务器的方法和装置 - Google Patents

确定应用服务器的方法和装置 Download PDF

Info

Publication number
WO2023109937A1
WO2023109937A1 PCT/CN2022/139487 CN2022139487W WO2023109937A1 WO 2023109937 A1 WO2023109937 A1 WO 2023109937A1 CN 2022139487 W CN2022139487 W CN 2022139487W WO 2023109937 A1 WO2023109937 A1 WO 2023109937A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
application server
network
terminal
candidate
Prior art date
Application number
PCT/CN2022/139487
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 EP22906682.4A priority Critical patent/EP4429201A1/en
Publication of WO2023109937A1 publication Critical patent/WO2023109937A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Definitions

  • the present application relates to the technical field of communications, and more specifically, to a method and device for determining an application server.
  • the selection strategy adopted is relatively simple, and the principle of proximity is usually adopted to select an application server for the terminal device.
  • the application server selected based on the principle of proximity may not be the most suitable application server. Therefore, how to select a suitable application server for the terminal device is an urgent problem to be solved.
  • the present application provides a method and device for determining an application server, which are used to select a suitable application server for a terminal device.
  • a method for determining an application server including:
  • the first network element obtains the characteristic parameters of the candidate application server, and the candidate application server can execute the target service of the terminal; the first network element obtains the network state of the service link, and the service link is a link from the terminal to the DN where the candidate application server is located; The first network element determines the target application server from the candidate application servers according to the characteristic parameters of the candidate application servers and the network state of the service link, and the target application server is used to execute the target service.
  • the first network element may be a session management network element, or a newly added network element.
  • the newly added network element may be called a computing service management function (compute service management function, CSMF) network element.
  • CSMF compute service management function
  • the first network element selects the application server for the terminal device
  • the characteristic parameters of the application server and the network status of the service link are taken into consideration, instead of selecting the application server only based on the principle of proximity. Therefore, compared with the existing methods, the method of the present application can make better use of resources in the network, and the selected target application server can better execute services of the terminal equipment, thereby improving user experience.
  • the characteristic parameters include the identifier of the application server, the identifier of the service that the application server can execute, and the data network access identifier DNAI of the DN where the application server is located.
  • the characteristic parameters further include one or more of the following:
  • the remaining capacity of the application server The remaining capacity of the application server, the task processing efficiency of the application server, the task storage efficiency of the application server, the data network name DNN of the DN where the application server is located, the identification of the application function network element associated with the application server, the location of the application server, the location of the application server.
  • the method further includes:
  • the first network element sends a first request message to the second network element, the first request message includes the identification of the target service, and the first request message is used to request the characteristic parameters of the application server capable of executing the target service; the first network element obtains the candidate
  • the characteristic parameter of the application server includes: the first network element receives a first response message from the second network element, and the first response message includes the characteristic parameter of the candidate application server.
  • the second network element is used for data storage.
  • the second network element may be an existing data storage network element in the core network system architecture, or the second network element may be a newly added network element.
  • the method further includes:
  • the first network element sends a second request message to the data management network element, the second request message is used to request terminal-related service information, and the second request message includes the identification of the terminal; the first network element receives the second response from the data management network element message, and the second response message includes the identifier of the target service.
  • the method further includes: the first network element receives a third request message from the session management network element, and the third request message is used to request the first network element to select an For the application server, the third request message includes the identifier of the terminal.
  • the method further includes:
  • the first network element acquires the identifier of the target service from the third network element, where the third network element is an edge application server discovery network element or a Domain Name System (DNS) server.
  • DNS Domain Name System
  • the network state of the service link includes:
  • the network element is associated with the DN where the candidate application server is located.
  • the first network element obtains the network status of the service link, including:
  • the first network element acquires the network status in the DN where the candidate application server is located from the local or the second network element; and/or, the first network element acquires the network status from the terminal to the access network device from the session management network element; and/or , the first network element obtains the network status from the access network device to the candidate user plane function network element from the session management network element.
  • the method further includes:
  • the first network element sends the identifier of the target application server, the identifier of the terminal and the identifier of the target service to the session management network element.
  • the first network element obtains the network status of the service link, including:
  • the first network element obtains the network status from the terminal to the access network device from the user plane function network element accessed by the terminal; and/or, the first network element obtains the access network device to the candidate user plane function from the candidate user plane function network element The network status of the NE.
  • the method further includes:
  • the first network element sends the identifier of the target application server, the identifier of the terminal, and the identifier of the target service to the edge application server discovery network element.
  • a first network element in a second aspect, includes a unit configured to execute the method in the first aspect and any possible implementation manner thereof.
  • a communication device including a communication interface and a processor.
  • the processor executes the computer program or instructions stored in the memory, so that the communication device executes the method in any possible implementation manner of the first aspect.
  • the memory may be located in the processor, or implemented by a chip independent of the processor, which is not specifically limited in the present application.
  • a computer-readable storage medium including a computer program.
  • the computer program When the computer program is run on a computer, the computer is made to execute the method in any possible implementation manner of the first aspect.
  • a chip is provided, and a processing circuit is disposed on the chip, and the processing circuit is configured to execute the method in any possible implementation manner of the first aspect.
  • a computer program product includes: a computer program (also referred to as code, or an instruction), when the computer program is executed, the computer executes any possible implementation manner in the first aspect method in .
  • a communication system in a seventh aspect, includes a first network element and other devices communicating with the first network element, and the first network element is used to implement the first aspect and any possible implementation thereof Methods.
  • Fig. 1 shows the system architecture applicable to the embodiment of the present application.
  • Fig. 2 is a schematic diagram of an example of the method proposed in this application.
  • FIG. 3 is a schematic diagram of an example of the method proposed in this application.
  • Fig. 4 is a schematic block diagram of a communication device provided in this application.
  • Fig. 5 is a schematic block diagram of a communication device provided in this application.
  • GSM global system for mobile communication
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • general packet radio service general packet radio service, GPRS
  • long term evolution long term evolution
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunications System
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G Fifth Generation
  • NR new radio
  • FIG. 1 shows a communication system 100 to which the present application applies.
  • the communication system 100 includes a terminal device, an access network device, a core network device, and a data network (data network, DN).
  • DN data network
  • the terminal equipment in the embodiment of the present application may refer to user equipment (user equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless Communication Device, 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 Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, terminal devices in future 6G networks or future evolution of public land mobile communication networks (public land mobile network (PLMN), etc., which are not limited in this embodiment of the present application.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the access network device in the embodiment of the present application may be a device for communicating with a terminal device, and the access network device may be a global system of mobile communication (GSM) system or a code division multiple access (code division multiple access, CDMA) in the base station (base transceiver station, BTS), also can be the base station (nodeB, NB) in the wideband code division multiple access (wideband code division multiple access, WCDMA) system, can also be the evolution in the LTE system eNB or eNodeB), it can also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario, or the access network device can be a relay station, an access point, or a vehicle-mounted device , wearable devices, access network devices in the 5G network, access network devices in the future 6G network, or access network devices in the future evolved PLMN network, etc., are not limited in this embodiment of the application.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • base station base trans
  • the core network may include, but is not limited to, session management network elements, application function network elements, network open network elements, data management network elements, data storage network elements, edge application server discovery network elements, and user plane function network element.
  • the session management network element is used to manage the creation and deletion of user sessions, and maintain the session context.
  • it may be a session management function (session management function, SMF) network element.
  • SMF session management function
  • the session management network element may still be an SMF network element, or have another name, which is not limited in this application.
  • Application function network elements are used to provide various business services.
  • it may be an application function (application function, AF) network element.
  • AF application function
  • the application function network element may still be an AF network element, or have another name, which is not limited in this application.
  • the network open network element is responsible for managing all external applications of open network data to ensure the security of external applications to the 3GPP network.
  • it may be a network exposure function (network exposure function, NEF) network element.
  • NEF network exposure function
  • the open network element may still be an NEF network element, or have another name, which is not limited in this application.
  • the data management network element is a network element used to manage data, for example, in a 5G network, it may be a unified data management function (Unified Data Management, UDM) network element. It should be understood that in future communication systems, the data management network element may still be a UDM network element, or have other names, which is not limited in this application.
  • UDM Unified Data Management
  • the data storage network element is used to store and retrieve contract data, policy data, public framework data, etc.
  • it may be a unified data repository (UDR) network element.
  • UDR unified data repository
  • the data storage network element may still be a UDR network element, or have another name, which is not limited in this application.
  • the edge application server discovery network element is used to discover the edge application server.
  • it may be an edge application server discovery function (edge application server discovery function, EASDF) network element.
  • EASDF edge application server discovery function
  • the network element discovered by the edge application server may still be an EASDF network element, or have another name, which is not limited in this application.
  • the user plane function network element is responsible for user plane functions, packet routing and forwarding, policy enforcement, traffic reporting, etc.
  • it may be a user plane function (user plane function, UPF) network element.
  • UPF user plane function
  • the user plane function network element may still be a UPF network element, or have other names, which is not limited in this application.
  • the selection strategy adopted is relatively simple, and the principle of proximity is usually adopted to select an application server for the terminal device.
  • the application server selected based on the principle of proximity may not be the most suitable application server.
  • the available computing capacity of the nearest application server is insufficient, or the available storage capacity of the nearest application server is insufficient, or the load of the nearest application server is relatively large, or the network status of the link between the terminal device and the nearest application server cannot Meet the needs.
  • using the nearest application server to execute services of the terminal device may not meet the requirements of the terminal device. For example, the delay requirement, capacity requirement, or network status requirement of the terminal device for the service cannot be met. Based on this, the present application proposes a method for solving the above problems.
  • the access network device is RAN
  • the session management network element is SMF
  • the application function network element is AF
  • the network opening network element is NEF
  • the data management network element is UDM
  • the data storage network element is UDR
  • the edge application network element is The server discovers that the network element is EASDF
  • the user plane function network element is UPF as an example for description.
  • FIG. 2 shows a method 200 provided by this application.
  • the method 200 includes:
  • AF#1 sends information #1 to the second network element, where the information #1 includes characteristic parameters of each application server in at least one application server associated with AF#1.
  • the second network element receives the information #1.
  • the second network element is used for data storage.
  • the second network element may be an existing UDR network element in the core network system architecture, or the second network element may be a newly added network element in the core network system architecture.
  • the newly added network element in the core network system architecture is called a compute service management function (CSMF) network element.
  • CSMF compute service management function
  • the newly added network element may have other names, which are not limited.
  • the newly added network element may be used to store information #1, and may also be used to perform related operations of the first network element in method 300 below.
  • AF#1 may send information #1 to the second network element through the NEF.
  • the NEF may send a response message #1 to AF#1, where the response message #1 indicates that information #1 is stored successfully.
  • AFs such as AF#2
  • AF#2 may send information #2 to the second network element, where the information #2 includes characteristic parameters of each application server in at least one application server associated with AF#2.
  • the second network element receives the information #2.
  • the second network element stores characteristic parameter information of at least one application server.
  • the characteristic parameters of the application server include the identification of the application server, the identification (service ID, SID) of the service that the application server can execute, and the data network access identifier (data network access identifier, DNAI) of the DN where the application server is located.
  • the identifier of the application server may be an Internet protocol (internet protocol, IP) address of the application server.
  • IP Internet protocol
  • the characteristic parameters of the application server also include one or more of the following:
  • the remaining capacity of the application server The remaining capacity of the application server, the task processing efficiency of the application server, the task storage efficiency of the application server, the data network name (data network name, DNN) of the DN where the application server is located, the identification of the AF associated with the application server, the location of the application server ( location), the domain to which the application server belongs, and the network slice selection assistance information (NSSAI) of the network slice to which the application server belongs.
  • data network name data network name, DNN
  • DNN data network name
  • NSSAI network slice selection assistance information
  • the remaining capacity of the application server can be indicated by the number of connections being processed by the application server and the total number of connections that the application server can handle.
  • the number of connections being processed by application server #1 is 100, and the total number of connections that the application server can handle is 500, so the remaining capacity of the application server is 400.
  • the task processing efficiency and task storage efficiency of the application server can be characterized by the duration of one call to the application server.
  • the duration of one call to the application server For example, the maximum duration, or the time range, or the average duration of one call to the application server.
  • characteristic parameter of the application server may also be other parameters, such as the number of UEs served by the application server, which is not limited in this application.
  • FIG. 3 shows a method 300 provided by this application. It should be understood that the method 300 can be performed on the basis of the method 200 .
  • the method 300 includes:
  • the first network element acquires characteristic parameters (referred to as first information) of candidate application servers.
  • Candidate application servers are capable of executing target services of the terminal. That is, the candidate application server has the ability to execute the target service.
  • the candidate application servers include one or more application servers.
  • the first network element may be an SMF, or a CSMF, or another network element, which is not limited.
  • SMF SMF
  • CSMF SMF
  • another network element which is not limited.
  • the description below takes the first network element as an SMF or CSMF as an example.
  • the following describes how the first network element obtains the first information:
  • Method 1 is applicable to the following two situations:
  • Case 1 The first network element is an SMF.
  • Case 2 the first network element is a CSMF, and the second network element in S210 is a UDR.
  • the first network element may obtain the first information through the following three steps.
  • Step 1 The first network element sends a first request message to the second network element in S210, the first request message includes the identifier of the target service, and the first request message is used to request the characteristic parameters of the application server capable of executing the target service.
  • the first request message also includes one or more of the following:
  • Step 2 The second network element determines a candidate application server from at least one application server according to the identifier of the target service and the characteristic parameter of at least one application server stored in S210.
  • the first request message requests an application server capable of executing service #1
  • the second network element queries the application server capable of executing service #1 from at least one application server.
  • the first request message requests an application server that can execute service #1 and is in DN#1
  • the second network element queries the application server that can execute service #1 and is in DN#1 from at least one application server server.
  • the first request message requests an application server that can perform service #1 and has a domain name of "aaa.com”
  • the second network element queries from at least one application server that can perform service #1 and has a domain name of "aaa.com”. com" application server.
  • Step 3 The second network element sends a first response message to the first network element, where the first response message includes the first information.
  • the second method is applicable to the case where the first network element is a CSMF, and the second network element is also a CSMF. That is, the first network element and the second network element are the same network element.
  • the first network element may obtain the characteristic parameters of the candidate application server from the characteristic parameters of at least one application server stored locally.
  • the first network element acquires the network state of the service link (denoted as the second information).
  • the service link is a link from the terminal to the DN where the candidate application server is located.
  • parameters characterizing the network state include but not limited to bandwidth, and/or delay, and/or packet loss rate, and the like.
  • the network status of the service link includes:
  • the above-mentioned RAN is the RAN accessed by the terminal
  • the above-mentioned candidate UPF is the UPF associated with the DN where the candidate application server is located.
  • the above-mentioned RAN and candidate UPF will not be described in detail below.
  • candidate application servers include application server #1 and application server #2, the DN where application server #1 resides is DN#1, the DN where application server #2 resides is DN#2, and the UPF associated with DN#1 is UPF# 1.
  • the UPF associated with DN#2 is UPF#2, and the candidate UPFs include UPF#1 and UPF#2.
  • the network status of service link #1 includes:
  • the network status of service link #2 includes:
  • the network state of the service link may include three parts.
  • the network state of service link #1 can be calculated by the formula in the following table. It should be understood that the calculation manner of the network state of the service link #1 and the network state of the service link #2 may be the same.
  • the first network element determines a target application server from the candidate application servers according to the characteristic parameters of the candidate application servers and the network state of the service link, and the target application server is used to execute the target service.
  • the first network element may determine the target application server from the candidate application servers according to the first information and the second information, and an application server selection policy applicable to the target service.
  • the reference computing power of each candidate application server can be calculated by the following formula #1:
  • the application server selection policy can be used to determine the above coefficient #1-coefficient #7, in other words, the values of coefficient #1-coefficient #7 are associated with the application server selection policy.
  • the application server selection policy may be pre-configured in the first network element.
  • the foregoing coefficients #1 to #7 may also be pre-configured in the first network element. That is, coefficients corresponding to different target services may be different.
  • the SID of the target service is SID#1
  • the candidate application servers are application server #1 (IP is IP#1)
  • application server #2 IP is IP#2)
  • application server #3 IP is IP#3
  • the application server selection strategy applicable to SID#1 is proximity and high efficiency.
  • the SID#1 is face detection (face detection).
  • the content included in the first information is shown in Table 2 below, and the content included in the second information is shown in Table 3 below. shown.
  • the service link #1 is the link between the terminal and DN#1
  • the service link #2 is the link between the terminal and multi-access edge computing (multi-access edge computing, MEC) #1.
  • Link #3 is a link between the terminal and MEC #2.
  • application server #1 is located in DN #1
  • application server #2 is located in MEC #1
  • application server #3 is located in MEC #2.
  • the location parameter may be represented by the distance from the terminal to the application server.
  • the distance is the distance between the geographical locations of the terminal and the application server, or it may be the distance of the communication path through which the terminal communicates with the application server.
  • the location parameter may be represented by the distance from the RAN to the application server.
  • the first network element determines the reference computing power of application server #1, the reference computing power of application server #2, and the reference computing power of application server #3, and determines that the target application server is the reference computing power of the three application servers.
  • the application server with the largest computing power It should be understood that the application server selection strategy of SID#1 is proximity and high efficiency, so the weights of location and task processing efficiency in formula #1 can be increased, for example, the values of coefficient #2 and coefficient #7 can be increased. Since the application server #2 (or MEC#1) is relatively close to the terminal, and the application server #2 has high task processing efficiency, the first network element calculates that the reference computing power of the application server #2 is the largest, and determines that the target application server is Application Server #2.
  • the SID of the target service is SID#2
  • the candidate application servers are application server #4 (IP is IP#4)
  • application server #5 IP is IP#5)
  • the application server selection policy applicable to SID#2 is resource Sufficiently, for example, the SID#2 is a translation service
  • the content included in the first information is shown in Table 4 below
  • the content included in the second information is shown in Table 5 below.
  • service link #4 is a link from the terminal to DN#4
  • service link #5 is a link from the terminal to DN#5.
  • the first network element determines the reference computing power of the application server #4 and the reference computing power of the application server #5, and determines that the target application server is the application server with the largest reference computing power among the two application servers. It should be understood that if the application server selection strategy of SID#2 is sufficient resources, then the weight of the remaining capacity parameter in formula #1 may be increased, for example, the value of coefficient #1 may be increased. Since the remaining capacity of the application server #4 is large, the first network element calculates that the reference computing power of the application server #4 is the largest, and determines that the target application server is the application server #4.
  • the first network element selects the application server for the terminal device
  • the characteristic parameters of the application server and the network status of the service link are taken into consideration, instead of selecting the application server only based on the principle of proximity. Therefore, compared with the existing methods, the method of the present application can make better use of resources in the network, and the selected target application server can better execute services of the terminal equipment, thereby improving user experience.
  • the first possible situation (the first network element is CSMF):
  • the method further includes:
  • the SMF sends a third request message to the first network element.
  • the first network element receives the third request message from the SMF.
  • the third request message is used to request the first network element to select an application server for the terminal, and the third request message includes the identifier of the terminal. In other words, the third request message is used to request the first network element to select computing power.
  • protocol data unit protocol data unit, PDU
  • the SMF may trigger sending a third request message to the first network element.
  • the first network element sends a second request message to the UDM.
  • the UDM receives the second request message.
  • the second request message is used to request service information related to the terminal, and the second request message includes an identifier of the terminal. Further, the second request message may be used to request service information related to the PDU session created for the terminal.
  • the UDM sends a second response message to the first network element.
  • the first network element receives a second response message from the UDM, where the second response message includes the identifier of the target service.
  • the second response message also includes one or more of the following:
  • the application identifier associated with the target service the identifier of the AF associated with the target service, the DNN of the DN associated with the target service, the NSSAI of the network slice associated with the target service, and the domain associated with the target service.
  • a possible implementation manner for the first network element to obtain the second information in S320 may be:
  • the first network element acquires the network status in the DN where the candidate application server is located from the local or the UDR.
  • the network status in multiple DNs may be pre-configured in the first network element, and the first network element may determine the network status in the DN where the candidate application server is located according to local configuration information.
  • the UDR may pre-configure the network statuses in multiple DNs, and the first network element obtains the network statuses in the DNs where the candidate application servers are located from the UDR.
  • the application provider can register the network status in the DN to CSMF or UDR through the NEF interface, the identifier can be SID, and/or, the application server IP, and/or, DNAI, the content can be delay, and/or , bandwidth, and/or, packet loss rate, etc.
  • the first network element acquires the network status from the terminal to the RAN from the SMF; and/or, the first network element acquires the network status from the RAN to the candidate UPF from the SMF.
  • the process may include the following steps:
  • Step A The first network element sends a request message #A to the SMF.
  • the SMF receives the request message #A.
  • the request message #A is used to request the network status from the terminal to the RAN, and/or, the network status from the RAN to the candidate UPF, and the request message #A includes the identifier of the terminal (for example, the IP of the terminal), and/or, the candidate UPF
  • the identifier of the DN where the application server resides for example, DNAI
  • Step B The SMF determines the UPF according to the identifier of the terminal in the request message #A. It should be understood that the UPF is the UPF accessed by the terminal.
  • Step C The SMF acquires the network status from the terminal to the RAN from the UPF.
  • Step D The SMF determines the candidate UPF according to the identifier of the DN where the candidate application server is located in the message #A.
  • Step E The SMF acquires the network status from the RAN to the candidate UPF from the candidate UPF.
  • the SMF may send the identifier of the RAN to the candidate UPF, and the candidate UPF determines the network status from the RAN to the candidate UPF according to the identifier of the RAN, and feeds back to the SMF.
  • the candidate UPF may periodically report the network status of the RAN to the candidate UPF.
  • the candidate UPFs are UPF#1, UPF#2 and UPF#3, then the SMF can obtain the network status from RAN to UPF#1, the network status from RAN to UPF#2 and the network status from RAN to UPF#3.
  • Step F The SMF sends a response message #A to the first network element, and the response message #A includes the network status from the terminal to the RAN, and/or the network status from the RAN to the candidate UPF.
  • the method further includes:
  • the first network element sends information #A to the SMF.
  • the SMF receives message #A.
  • the information #A includes the identifier of the terminal, the identifier of the target service and the identifier of the target application server.
  • the information #A may also include an identifier (for example, DNAI) of a DN associated with the target service and/or a domain name of a domain associated with the target service.
  • the SMF sends the information #A to the EASDF. Accordingly, EASDF receives this message #A.
  • SMF can send domain name system context (DNS context) to EASDF, and this information #A can be carried in DNS context.
  • DNS context domain name system context
  • the terminal sends a request message #B to the EASDF.
  • EASDF receives the request message #B.
  • This request message #B requests an application server for executing the target service.
  • the request message #B includes the identifier of the target service.
  • the request message #B may also include the domain name associated with the target service.
  • the identifier of the target service may be included in the domain name; or not included in the domain name, as a separate parameter.
  • the request message #B may be a DNS request message.
  • the EASDF sends a response message #B to the terminal. Accordingly, the terminal receives the response message #B.
  • the response message #B includes the identifier of the target application server.
  • EASDF determines the target application server according to the target service ID included in the information #A and the request message #B, and sends the target application server ID (for example, the IP of the target application server) to the terminal.
  • the EASDF may determine whether to trigger a notify operation, and when the notify operation needs to be performed, the EASDF sends a notify operation request message to the SMF.
  • the SMF judges whether to insert an uplink classifier (uplink classifier, ULCL)/branching point (branching point, BP) and a local PDU session anchor point (local PSA, L-PSA) according to the notify operation request message. If ULCL/BP and L-PSA need to be inserted, SMF inserts ULCL/BP and L-PSA.
  • the SMF sends a notify operation response message to the EASDF.
  • the second possible situation (the first network element is SMF):
  • the method further includes the above S302 and S303. I won't repeat them here.
  • the first network element selects the EASDF, it may be triggered to send the second request message to the UDM.
  • a possible implementation manner for the first network element to obtain the second information in S320 may be:
  • the first network element obtains the network status in the DN where the candidate application server is located from the UDR; and/or, the first network element can determine the UPF currently associated with the terminal according to the identifier of the terminal, and obtain the network status from the terminal to the RAN from the UPF and/or, the first network element may determine the candidate UPF according to the ID (DNAI) of the DN where the candidate application server is located, and acquire the network status from the RAN to the candidate UPF from the candidate UPF.
  • DNAI ID
  • the method further includes the above-mentioned S332-S334. I won't repeat them here.
  • the third possible situation (the first network element is CSMF):
  • the method also includes
  • the terminal sends a request message #B to the EASDF.
  • EASDF receives the request message #B.
  • This request message #B requests an application server for executing the target service.
  • the request message #B includes the identifier of the target service.
  • the request message #B may also include the domain name associated with the target service.
  • the identifier of the target service may be included in the domain name; or not included in the domain name, as a separate parameter.
  • the request message #B may be a DNS request message. That is, S310 is performed after the terminal initiates the DNS request.
  • the EASDF (an example of the third network element) sends the identifier of the target service to the first network element.
  • the first network element acquires the identifier of the target service from the EASDF.
  • the identifier of the target service may be carried in the above third request message. That is, at this time, the third request message includes the identifier of the terminal and the identifier of the target service. The third request message may also include the domain name associated with the target service.
  • the first network element acquires the network status in the DN where the candidate application server is located from the local or the UDR. And/or, the first network element acquires the network status from the terminal to the RAN from the SMF; and/or, the first network element acquires the network status from the RAN to the candidate UPF from the SMF. For details, reference may be made to the first possible situation, which will not be repeated here.
  • the SMF is the SMF associated with the terminal.
  • the first network element may send the identifier of the terminal to the UDM, and acquire the SMF associated with the terminal from the UDM.
  • the method further includes:
  • the first network element sends information #A to the SMF.
  • the SMF receives message #A.
  • the content included in the information #A is as above, and will not be repeated here.
  • the first network element may send information #A to the SMF through the EASDF. For example, through the notify interface of EASDF.
  • the SMF sends the information #A to the EASDF. Accordingly, EASDF receives this message #A.
  • SMF can send domain name system context (DNS context) to EASDF, and this information #A can be carried in DNS context.
  • DNS context domain name system context
  • the SMF may judge whether to insert the ULCL/BP and the L-PSA according to the information #A. If ULCL/BP and L-PSA need to be inserted, SMF inserts ULCL/BP and L-PSA.
  • the EASDF sends a response message #B to the terminal. Accordingly, the terminal receives the response message #B.
  • the response message #B includes the identifier of the target application server.
  • EASDF determines the target application server according to the target service ID included in the information #A and the request message #B, and sends the target application server ID (for example, the IP of the target application server) to the terminal.
  • the fourth possible situation (the first network element is SMF):
  • the method also includes the above S304 and S305, which will not be repeated here.
  • the method further includes the above S332 and S334, which will not be repeated here.
  • the SMF may judge whether to insert the ULCL/BP and the L-PSA according to the information #A. If ULCL/BP and L-PSA need to be inserted, SMF inserts ULCL/BP and L-PSA.
  • the fifth possible situation (the first network element is CSMF):
  • the terminal sends a request message #B to a local (local) domain name system (domain name system, DNS) server (server)/resolver (resolver).
  • DNS domain name system
  • server server/resolver/resolver
  • the local DNS server receives the request message #B.
  • the request message #B is used to request the application server to execute the target service.
  • the request message #B includes the identifier of the target service.
  • the request message #B may also include the domain name associated with the target service.
  • the identifier of the target service may be included in the domain name; or not included in the domain name, as a separate parameter.
  • the terminal can send request message #B to the local DNS server through ULCL/BP and L-PSA.
  • the request message #B may be a DNS request message.
  • the local DNS server (another example of the third network element) sends the identifier of the target service to the first network element.
  • the first network element receives the identifier of the target service from the local DNS server.
  • the identifier of the target service may be carried in the above third request message. That is, at this time, the third request message includes the identifier of the terminal and the identifier of the target service. The third request message also includes the domain name associated with the target service.
  • the method further includes:
  • the first network element sends information #A to the SMF.
  • the SMF receives message #A.
  • the content included in the information #A is as above, and will not be repeated here.
  • the SMF can judge whether to insert the ULCL/BP and the L-PSA according to the information #A. If ULCL/BP and L-PSA need to be inserted, SMF inserts ULCL/BP and L-PSA.
  • the first network element sends information #A to the local DNS server.
  • the local DNS server receives message #A.
  • the local DNS server sends a response message #B to the terminal. Accordingly, the terminal receives the response message #B.
  • the response message #B includes the identifier of the target application server.
  • the local DNS server determines the target application server according to the identification of the target service included in the information #A and the request message #B, and sends the identification of the target application server (for example, the IP of the target application server) to the terminal.
  • FIG. 4 is a communication device provided in an embodiment of the present application, and the communication device includes a transceiver unit 401 and a processing unit 402 .
  • the transceiver unit 401 may be used to implement a corresponding communication function.
  • the transceiver unit 401 may also be called a communication interface or a communication unit.
  • the processing unit 402 may be configured to perform processing operations.
  • the device further includes a storage unit, which can be used to store instructions and/or data, and the processing unit 402 can read the instructions and/or data in the storage unit, so that the device implements the above-mentioned method embodiments. action of the device.
  • a storage unit which can be used to store instructions and/or data
  • the processing unit 402 can read the instructions and/or data in the storage unit, so that the device implements the above-mentioned method embodiments. action of the device.
  • the communication device may be the first network element in the foregoing embodiments, or may be a component (such as a chip) of the first network element.
  • the transceiver unit is used to obtain the characteristic parameters of the candidate application server; the transceiver unit is also used to obtain the network status of the service link; The target application server is determined from the candidate application servers.
  • the transceiver unit is further configured to send the first request message to the second network element; the transceiver unit is also configured to receive the first response message from the second network element,
  • the transceiver unit is further configured to send a second request message to the data management network element; the transceiver unit is also configured to receive a second response message from the data management network element,
  • the transceiver unit is further configured to receive the third request message from the session management network element.
  • the transceiver unit is further configured to acquire the identifier of the target service from the third network element.
  • the transceiver unit is further configured to acquire the network status in the DN where the candidate application server is located from the local or the second network element; and/or the transceiver unit is also configured to acquire the The network state of the network access device; and/or, the transceiver unit is further configured to acquire the network state from the access network device to the candidate user plane function network element from the session management network element.
  • the transceiver unit is also used to obtain the network status from the terminal to the access network device from the user plane functional network element; and/or the transceiver unit is also used to obtain the access network status from the candidate user plane functional network element. The network status from the device to the candidate user plane function network element.
  • unit here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • the device may specifically be the first network element in the above-mentioned embodiments, and may be used to execute each process corresponding to the first network element in the above-mentioned method embodiments and/or steps, or, the device may specifically be the network management network element in the above embodiments, and may be used to execute the various processes and/or steps corresponding to the network management network elements in the above method embodiments. In order to avoid repetition, it is not repeated here repeat.
  • the above-mentioned communication device has the function of implementing the corresponding steps performed by the device in the above-mentioned method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver ), and other units, such as a processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 401 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.
  • the device in FIG. 4 may be the device in the foregoing method embodiment, or may be a chip or a chip system, for example: a system on chip (system on chip, SoC).
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. It is not limited here.
  • the embodiment of the present application also provides a communication device, as shown in FIG. 5 , including: a processor 501 and a communication interface 502 .
  • the processor 501 is configured to execute computer programs or instructions stored in the memory 503, or read data stored in the memory 503, so as to execute the methods in the above method embodiments.
  • the communication interface 502 is used for receiving and/or sending signals.
  • the processor 501 is configured to control the communication interface 502 to receive and/or send signals.
  • the communication device further includes a memory 503, and the memory 503 is used to store computer programs or instructions and/or data.
  • the memory 503 can be integrated with the processor 501, or can also be set separately.
  • the processor 501, the communication interface 502, and the memory 503 are connected to each other through a bus 504;
  • the bus 504 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA ) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the above-mentioned bus 504 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 5 , but it does not mean that there is only one bus or one type of bus.
  • the processor 501 is configured to execute the computer programs or instructions stored in the memory 503, so as to implement related operations of the first network element in each method embodiment above.
  • the processor (such as the processor 501) mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.
  • the processor may further include hardware chips.
  • the aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • the memory (such as the memory 503 ) mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or integrated. to another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separated, and a component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc 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)
  • Computer And Data Communications (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供了一种确定应用服务器的方法和装置。该方法包括：第一网元获取候选应用服务器的特征参数；第一网元获取服务链路的网络状态，服务链路为终端到候选应用服务器所在的DN的链路；第一网元根据候选应用服务器的特征参数和服务链路的网络状态，从候选应用服务器中确定目标应用服务器。因此，相比于现有的方法，采用本申请的方法可以更好地利用网络中的资源，选择的目标应用服务器可以更好地执行终端设备的业务，从而提升用户体验。

Description

确定应用服务器的方法和装置
本申请要求于2021年12月17日提交中国专利局、申请号为202111552660.7、申请名称为“确定应用服务器的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，并且更具体地，涉及一种确定应用服务器的方法和装置。
背景技术
当前，在为终端设备选择应用服务器时，采取的选择策略较为单一，通常采取就近原则为终端设备选择应用服务器。然而，采取就近原则选择的应用服务器可能并不是最合适的应用服务器。因此，如何才能为终端设备选择一个合适的应用服务器是一个亟待解决的问题。
发明内容
本申请提供了一种确定应用服务器的方法和装置，用于为终端设备选择一个合适的应用服务器。
第一方面，提供了一种确定应用服务器的方法，包括：
第一网元获取候选应用服务器的特征参数，候选应用服务器能够执行终端的目标业务；第一网元获取服务链路的网络状态，服务链路为终端到候选应用服务器所在的DN的链路；第一网元根据候选应用服务器的特征参数和服务链路的网络状态，从候选应用服务器中确定目标应用服务器，目标应用服务器用于执行目标业务。
应理解，第一网元可以为会话管理网元，或者为新增的网元。例如，该新增的网元可以称之为计算服务管理功能(compute service management function，CSMF)网元。
由以上可知，第一网元为终端设备选择应用服务器的时候考虑了应用服务器的特征参数以及服务链路的网络状态，而不是仅仅根据就近原则选取应用服务器。因此，相比于现有的方法，采用本申请的方法可以更好地利用网络中的资源，选择的目标应用服务器可以更好地执行终端设备的业务，从而提升用户体验。
结合第一方面，在第一方面的某些实现方式中，特征参数包括应用服务器的标识、应用服务器能够执行的业务的标识和应用服务器所在的DN的数据网络访问标识DNAI。
结合第一方面，在第一方面的某些实现方式中，特征参数还包括以下中的一项或多项：
应用服务器的剩余容量、应用服务器的任务处理效率、应用服务器的任务存储效率、应用服务器所在的DN的数据网络名称DNN、应用服务器关联的应用功能网元的标识、应用服务器的位置、应用服务器所属的域的域名、应用服务器所属的网络切片的网络切片选择辅助信息NSSAI。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
第一网元向第二网元发送第一请求消息，第一请求消息中包括目标业务的标识，第一请求消息用于请求能够执行目标业务的应用服务器的特征参数；第一网元获取候选应用服务器的特征参数，包括：第一网元从第二网元接收第一响应消息，第一响应消息包括候选应用服务器的特征参数。
应理解，该第二网元用于数据存储。例如，该第二网元可以为核心网系统架构中现有的数据存储网元，或者，该第二网元可以为新增的网元。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
第一网元向数据管理网元发送第二请求消息，第二请求消息用于请求终端相关的业务信息，第二请求消息包括终端的标识；第一网元从数据管理网元接收第二响应消息，第二响应消息包括目标业务的标识。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：第一网元从会话管理网元接收第三请求消息，第三请求消息用于请求第一网元为终端选择应用服务器，第三请求消息包括终端的标识。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
第一网元从第三网元获取目标业务的标识，其中，第三网元为边缘应用服务器发现网元或者域名系统DNS服务器。
结合第一方面，在第一方面的某些实现方式中，服务链路的网络状态包括：
候选应用服务器所在的DN内的网络状态，和/或，终端到接入网设备的网络状态，和/或，接入网设备到候选用户面功能网元的网络状态；其中，候选用户面功能网元与候选应用服务器所在的DN所关联。
结合第一方面，在第一方面的某些实现方式中，第一网元获取服务链路的网络状态，包括：
第一网元从本地或者第二网元获取候选应用服务器所在的DN内的网络状态；和/或，第一网元从会话管理网元获取终端到接入网设备的网络状态；和/或，第一网元从会话管理网元获取接入网设备到候选用户面功能网元的网络状态。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
第一网元向会话管理网元发送目标应用服务器的标识、终端的标识和目标业务的标识。
结合第一方面，在第一方面的某些实现方式中，第一网元获取服务链路的网络状态，包括：
第一网元从终端接入的用户面功能网元获取终端到接入网设备的网络状态；和/或，第一网元从候选用户面功能网元获取接入网设备到候选用户面功能网元的网络状态。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
第一网元向边缘应用服务器发现网元发送目标应用服务器的标识、终端的标识和目标业务的标识。
第二方面，提供一种第一网元，该第一网元包括用于执行该第一方面及其任一种可能实现方式中的方法的单元。
第三方面，提供一种通信设备，包括通信接口和处理器。当该通信设备运行时，处理 器执行存储器存储的计算机程序或指令，使得该通信设备执行第一方面中任一种可能实现方式中的方法。该存储器可以位于处理器中，也可以为与处理器通过相互独立的芯片来实现，本申请对此不具体限定。
第四方面，提供一种计算机可读存储介质，包括计算机程序，当计算机程序在计算机上运行时，使得计算机执行第一方面中任一种可能实现方式中的方法。
第五方面，提供一种芯片，芯片上设置有处理电路，处理电路用于执行该第一方面中任一种可能实现方式中的方法。
第六方面，提供了一种计算机程序产品，计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当计算机程序被运行时，使得计算机执行第一方面中任一种可能实现方式中的方法。
第七方面，提供一种通信系统，该通信系统包括第一网元和与该第一网元通信的其他设备，该第一网元用于执行第一方面及其任一种可能实现方式中的方法。
附图说明
图1示出了本申请实施例适用的系统架构。
图2为本申请所提出的方法的一例示意图。
图3为本申请所提出的方法的一例示意图。
图4为本申请提供的通信装置的一种示意性框图。
图5为本申请提供的通信设备的一种示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(global system for mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、第五代(5th Generation，5G)系统或新无线(new radio，NR)、未来第六代(6th Generation，6G)系统等。
图1示出了本申请适用的通信系统100。该通信系统100包括终端设备、接入网设备、核心网设备、数据网络(data network，DN)。
本申请实施例中的终端设备可以指用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端 设备，未来6G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例中的接入网设备可以是用于与终端设备通信的设备，该接入网设备可以是全球移动通讯(global system of mobile communication，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(nodeB，NB)，还可以是LTE系统中的演进型基站(evolutional nodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备、5G网络中的接入网设备以及未来6G网络中的接入网设备或者未来演进的PLMN网络中的接入网设备等，本申请实施例并不限定。
在本申请实施例中，核心网中可以包括但不限于会话管理网元、应用功能网元、网络开放网元、数据管理网元、数据存储网元、边缘应用服务器发现网元、用户面功能网元。
其中，会话管理网元用于管理用户会话创建、删除，维护会话上下文。例如，该在5G网络中，可以为会话管理功能(session management function，SMF)网元。应理解，在未来的通信系统中，会话管理网元可能仍然为SMF网元，或者具有其他名称，本申请对此不予限定。
应用功能网元用于提供各种业务服务。例如，在5G网络中，可以为应用功能(application function，AF)网元。应理解，在未来的通信系统中，应用功能网元可能仍然为AF网元，或者具有其他名称，本申请对此不予限定。
网络开放网元负责管理对外开放网络数据的所有的外部应用，保证外部应用到3GPP网络的安全。例如，在5G网络中，可以是网络开放功能(network exposure function，NEF)网元。应理解，在未来的通信系统中，网络开放网元可能仍然为NEF网元，或者具有其他名称，本申请对此不予限定。
数据管理网元是一种用于对数据进行管理的网元，例如，在5G网络中，可以是统一数据管理功能(Unified Data Management，UDM)网元。应理解，在未来的通信系统中，数据管理网元可能仍然为UDM网元，或者具有其他名称，本申请对此不予限定。
数据存储网元用于存储和检索签约数据、策略数据、公共架构数据等。例如，在5G网络中，可以是统一数据存储(unified data repository，UDR)网元。应理解，在未来的通信系统中，数据存储网元可能仍然为UDR网元，或者具有其他名称，本申请对此不予限定。
边缘应用服务器发现网元用于发现边缘应用服务器。例如，在5G网络中，可以是边缘应用服务器发现功能(edge application server discovery function，EASDF)网元。应理解，在未来的通信系统中，边缘应用服务器发现网元可能仍然为EASDF网元，或者具有其他名称，本申请对此不予限定。
用户面功能网元负责用户面功能，分组路由转发，策略实施，流量报告等。例如，在5G网络中，可以是用户面功能(user plane function，UPF)网元。应理解，在未来的通信系统中，用户面功能网元可能仍然为UPF网元，或者具有其他名称，本申请对此不予限定。
当前，在为终端设备选择应用服务器时，采取的选择策略较为单一，通常采取就近原则为终端设备选择应用服务器。然而，采取就近原则选择的应用服务器可能并不是最合适的应用服务器。例如，最近的应用服务器可用的计算能力不足，或者，最近的应用服务器可用的存储容量不足，或者最近的应用服务器负载已经比较大了，或者终端设备到最近的应用服务器的链路的网络状态不能满足需求。此时，使用该最近的应用服务器来执行终端设备的业务，可能不能满足终端设备的要求。例如，不能满足终端设备对于该业务的时延要求，或者容量要求，或者网络状态要求等。基于此，本申请提出了一种方法，用于解决上述问题。
为了描述方便，下文以接入网设备为RAN、会话管理网元为SMF、应用功能网元为AF、网络开放网元为NEF、数据管理网元为UDM、数据存储网元为UDR、边缘应用服务器发现网元为EASDF、用户面功能网元为UPF为例进行描述。
图2示出了本申请提供的方法200。该方法200包括：
S210，AF#1向第二网元发送信息#1，该信息#1包括AF#1关联的至少一个应用服务器中每个应用服务器的特征参数。相应地，第二网元接收该信息#1。
该第二网元用于数据存储。例如，该第二网元可以为核心网系统架构中现有的UDR网元，或者，该第二网元可以为核心网系统架构中新增的网元。本申请中将该核心网系统架构中新增的网元称为计算服务管理功能(compute service management function，CSMF)网元，当然该新增的网元还可以有其他的名称，不予限定。
该新增的网元可以用于存储信息#1，也可以用于执行下文方法300中第一网元的相关操作。
作为一种可能的方式，AF#1可以通过NEF向第二网元发送信息#1。可选地，NEF可以向AF#1发送响应消息#1，该响应消息#1指示信息#1存储成功。
类似地，其他的AF，例如AF#2可以向第二网元发送信息#2，该信息#2包括AF#2关联的至少一个应用服务器中每个应用服务器的特征参数。相应地，第二网元接收该信息#2。
即，第二网元存储了至少一个应用服务器的特征参数信息。
下面对应用服务器的特征参数进行说明。
可选地，应用服务器的特征参数包括应用服务器的标识、应用服务器能够执行的业务的标识(service ID，SID)和应用服务器所在的DN的数据网络访问标识(data network access identifier，DNAI)。
一示例，应用服务器的标识可以为应用服务器的互联网协议(internet protocol，IP)地址。
可选地，应用服务器的特征参数还包括以下中的一项或多项：
应用服务器的剩余容量、应用服务器的任务处理效率、应用服务器的任务存储效率、应用服务器所在的DN的数据网络名称(data network name，DNN)、应用服务器关联的AF的标识、应用服务器的位置(location)、应用服务器所属的域(domain)、应用服务器所属的网络切片的网络切片选择辅助信息(network slice selection assistance information，NSSAI)。
示例性地，应用服务器的剩余容量可以通过应用服务器正在处理的连接数以及应用服 务器能够处理的连接总数来指示。例如，应用服务器#1正在处理的连接数为100，应用服务器能够处理的连接总数为500，则应用服务器的剩余容量为400。
示例性地，应用服务器的任务处理效率和任务存储效率可以通过一次可以调用应用服务器的时长来表征。例如，一次可以调用应用服务器的最大时长，或者时间范围，或者平均时长。
应理解，应用服务器的特征参数还可以为其他参数，例如应用服务器服务的UE的个数等，本申请对此不予限制。
图3示出了本申请提供的方法300。应理解，方法300可以在方法200的基础之上进行。该方法300包括：
S310，第一网元获取候选应用服务器的特征参数(记为，第一信息)。
候选应用服务器能够执行终端的目标业务。即，候选应用服务器具有执行目标业务的能力。该候选应用服务器包括一个或多个应用服务器。
应理解，该第一网元可以为SMF、或者CSMF、或者其他的网元，不予限定。为了描述方便，下文中以第一网元为SMF或者CSMF为例进行说明。
下面介绍第一网元获取第一信息的方式：
方式一：
该方式一适用于下面两种情况：
情况1：第一网元为SMF。
情况2：第一网元为CSMF，S210中的第二网元为UDR。
第一网元可以通过下面的3个步骤获取第一信息。
步骤1：第一网元向S210中的第二网元发送第一请求消息，第一请求消息中包括目标业务的标识，第一请求消息用于请求能够执行目标业务的应用服务器的特征参数。
可选地，该第一请求消息中还包括以下中的一项或多项：
目标业务关联的AF的标识、目标业务关联的DN的DNN、目标业务关联的网络切片的NSSAI、目标业务关联的域。
步骤2：第二网元根据目标业务的标识以及S210中存储的至少一个应用服务器的特征参数，从至少一个应用服务器中确定候选应用服务器。
例如，第一请求消息请求能够执行业务#1的应用服务器，则第二网元从至少一个应用服务器中查询能够执行业务#1的应用服务器。
又例如，第一请求消息请求能够执行业务#1、并且在DN#1内的应用服务器，则第二网元从至少一个应用服务器中查询能够执行业务#1、并且在DN#1内的应用服务器。
又例如，第一请求消息请求能够执行业务#1、并且域名为“aaa.com”的应用服务器，则第二网元从至少一个应用服务器中查询能够执行业务#1、并且域名为“aaa.com”的应用服务器。
步骤3：第二网元向第一网元发送第一响应消息，该第一响应消息中包括该第一信息。
方式二：
该方式二适用于第一网元为CSMF，第二网元也为CSMF的情况。即，第一网元与第二网元为同一个网元。
此时，第一网元可以从本地存储的至少一个应用服务器的特征参数中，获取候选应用 服务器的特征参数。
S320，第一网元获取服务链路的网络状态(记为，第二信息)。
该服务链路为终端到候选应用服务器所在的DN的链路。
应理解，表征网络状态的参数包括但不限于带宽、和/或时延、和/或丢包率等。
服务链路的网络状态包括：
候选应用服务器所在的DN内的网络状态，和/或，终端到RAN的网络状态，和/或，RAN到候选UPF的网络状态。
其中，上述RAN为终端接入的RAN，上述候选UPF为候选应用服务器所在的DN所关联的UPF。关于上述RAN与候选UPF下文不再赘述。
例如，候选应用服务器包括应用服务器#1和应用服务器#2，应用服务器#1所在的DN为DN#1、应用服务器#2所在的DN为DN#2，DN#1所关联的UPF为UPF#1、DN#2所关联的UPF为UPF#2，则候选UPF包括UPF#1和UPF#2。
那么，服务链路#1的网络状态包括：
终端到RAN的网络状态，和/或，RAN到UPF#1的网络状态，和/或，DN#1内的网络状态。
服务链路#2的网络状态包括：
终端到RAN的网络状态，和/或，RAN到UPF#2的网络状态，和/或，DN#2内的网络状态。
由上可知，服务链路的网络状态可能包括三部分。作为一个示例，服务链路#1的网络状态可以通过下表中的公式计算。应理解，服务链路#1的网络状态与服务链路#2的网络状态的计算方式可以是相同的。
表1
  带宽 时延 丢包率
终端到RAN A D G
RAN到UPF#1 B E H
DN#1内 C F I
服务链路#1 min(A,B,C) D+E+F 1-(1-G)(1-H)(1-I)
S330，第一网元根据候选应用服务器的特征参数和服务链路的网络状态，从候选应用服务器中确定目标应用服务器，目标应用服务器用于执行目标业务。
作为一种方式，第一网元可以根据第一信息和第二信息，以及适用于目标业务的应用服务器选择策略，从候选应用服务器中确定目标应用服务器。
一示例，每个候选应用服务器的参考算力可以通过以下公式#1来计算：
公式#1：参考算力＝系数#1×剩余容量+系数#2×处理效率+系数#3×存储效率+系数#4×链路带宽+系数#5×链路时延+系数#6×链路丢包率+系数#7×location
其中，应用服务器选择策略可以用于确定上述系数#1-系数#7，换句话说，系数#1-系数#7的取值与应用服务器选择策略是相关联的。应用服务器选择策略可以是预先配置到第一网元中的。上述系数#1-系数#7也可以为预先配置到第一网元中的。即，不同的目标业务所对应的系数可能不同。
下面通过2个例子进行说明。
示例1：
该目标业务的SID为SID#1，候选应用服务器为应用服务器#1(IP为IP#1)、应用服务器#2(IP为IP#2)和应用服务器#3(IP为IP#3)，适用于SID#1的应用服务器选择策略为就近和高效率，例如该SID#1为人脸检测(face detection)，第一信息包括的内容如下表2所示，第二信息包括的内容如下表3所示。其中，服务链路#1为终端到DN#1之间的链路，服务链路#2为终端到多接入边缘计算(multi-access edge computing，MEC)#1之间的链路，服务链路#3为终端到MEC#2之间的链路。
应理解，应用服务器#1位于DN#1内，应用服务器#2位于MEC#1内，应用服务器#3位于MEC#2内。一示例，location参数可以通过终端到应用服务器的距离来表征。例如，该距离为终端与应用服务器的地理位置之间的距离，也可以为终端与应用服务器进行通信的通信路径的距离。又一示例，location参数可以通过RAN到应用服务器的距离来表征。
表2
Figure PCTCN2022139487-appb-000001
表3
  带宽 时延 丢包率
服务链路#1 500M 50ms 2％
服务链路#2 400M 10ms 1％
服务链路#3 500M 20ms 1％
通过上述公式#1，第一网元确定应用服务器#1的参考算力、应用服务器#2的参考算力和应用服务器#3的参考算力，并确定目标应用服务器为3个应用服务器中参考算力最大的应用服务器。应理解，SID#1的应用服务器选择策略为就近和高效率，那么可以提高公式#1中location和任务处理效率的权重，例如提高系数#2和系数#7的取值。由于应用服务器#2(或者，MEC#1)距离终端较近，并且应用服务器#2任务处理效率较高，则第一网元计算出应用服务器#2的参考算力最大，确定目标应用服务器为应用服务器#2。
示例2：
该目标业务的SID为SID#2，候选应用服务器为应用服务器#4(IP为IP#4)、应用服务器#5(IP为IP#5)，适用于SID#2的应用服务器选择策略为资源充足，例如该SID#2为翻译(translation)服务，第一信息包括的内容如下表4所示，第二信息包括的内容如下表5所示。其中，服务链路#4为终端到DN#4的链路，服务链路#5为终端到DN#5的链路。
表4
Figure PCTCN2022139487-appb-000002
Figure PCTCN2022139487-appb-000003
表5
  带宽 时延 丢包率
服务链路#4 500M 50ms 2％
服务链路#5 400M 10ms 1％
通过上述公式#1，第一网元确定应用服务器#4的参考算力和应用服务器#5的参考算力，并确定目标应用服务器为2个应用服务器中参考算力最大的应用服务器。应理解，SID#2的应用服务器选择策略为资源充足，那么可以提高公式#1中剩余容量参数的权重，例如提高系数#1的取值。由于应用服务器#4剩余容量较大，则第一网元计算出应用服务器#4的参考算力最大，确定目标应用服务器为应用服务器#4。
由以上可知，第一网元为终端设备选择应用服务器的时候考虑了应用服务器的特征参数以及服务链路的网络状态，而不是仅仅根据就近原则选取应用服务器。因此，相比于现有的方法，采用本申请的方法可以更好地利用网络中的资源，选择的目标应用服务器可以更好地执行终端设备的业务，从而提升用户体验。
下面结合不同的情形，对本申请的技术方案进行更进一步的描述。
第一种可能的情形(第一网元为CSMF)：
针对该情形，在S310之前，该方法还包括：
S301，SMF向第一网元发送第三请求消息。相应地，第一网元从SMF接收第三请求消息。
该第三请求消息用于请求第一网元为终端选择应用服务器，第三请求消息包括终端的标识。换句话说，该第三请求消息用于请求第一网元进行算力选择。
作为一种方式，在为终端创建协议数据单元(protocol data unit，PDU)会话的过程中，SMF进行EASDF选择之后，可以触发向第一网元发送第三请求消息。
S302，第一网元向UDM发送第二请求消息。相应地，UDM接收该第二请求消息。
第二请求消息用于请求终端相关的业务信息，第二请求消息包括终端的标识。进一步地，该第二请求消息可以用于请求与为终端创建的PDU会话相关的业务信息。
S303，UDM向第一网元发送第二响应消息。相应地，第一网元从UDM接收第二响应消息，第二响应消息包括目标业务的标识。
可选地，第二响应消息还包括以下中的一项或多项：
目标业务关联的应用标识、目标业务关联的AF的标识、目标业务关联的DN的DNN、目标业务关联的网络切片的NSSAI、目标业务关联的域。
此外，针对该情形，S320中第一网元获取第二信息的可能的实现方式可以为：
第一网元从本地或者UDR获取候选应用服务器所在的DN内的网络状态。
例如，可以预先在第一网元中配置多个DN内的网络状态，第一网元可以根据本地的配置信息，确定候选应用服务器所在的DN内的网络状态。
又例如，可以预先在UDR中配置多个DN内的网络状态，第一网元从UDR获取候选应用服务器所在的DN内的网络状态。
应理解，应用供应商可以通过NEF接口将DN内的网络状态注册到CSMF或者UDR， 标识可以是SID，和/或，应用服务器IP，和/或，DNAI，内容可以是时延，和/或，带宽，和/或，丢包率等。
和/或，第一网元从SMF获取终端到RAN的网络状态；和/或，第一网元从SMF获取RAN到候选UPF的网络状态。作为一种方式，该过程可以包括以下步骤：
步骤A：第一网元向SMF发送请求消息#A。相应地，SMF接收该请求消息#A。
该请求消息#A用于请求终端到RAN的网络状态，和/或，RAN到候选UPF的网络状态，该请求消息#A中包括终端的标识(例如，终端的IP)，和/或，候选应用服务器所在的DN的标识(例如，DNAI)。
步骤B：SMF根据请求消息#A中的终端的标识，确定UPF。应理解，该UPF为终端接入的UPF。
步骤C：SMF从该UPF获取终端到RAN的网络状态。
步骤D：SMF根据消息#A中候选应用服务器所在的DN的标识，确定候选UPF。
步骤E：SMF从候选UPF获取RAN到候选UPF的网络状态。
可选地，作为一种方式，SMF可以向候选UPF发送RAN的标识，候选UPF根据RAN的标识确定RAN到候选UPF的网络状态，并向SMF反馈。
可选地，作为另一种方式，候选UPF可以定期上报RAN到候选UPF的网络状态。
例如，候选UPF为UPF#1、UPF#2和UPF#3，则SMF可以获取RAN到UPF#1的网络状态、RAN到UPF#2的网络状态和RAN到UPF#3的网络状态。
步骤F：SMF向第一网元发送响应消息#A，该响应消息#A中包括终端到RAN的网络状态，和/或，RAN到候选UPF的网络状态。
针对该情形，在S330之后，该方法还包括：
S331，第一网元向SMF发送信息#A。相应地，SMF接收信息#A。
该信息#A包括终端的标识、目标业务的标识和目标应用服务器的标识。可选地，该信息#A还可以包括目标业务关联的DN的标识(例如，DNAI)和/或目标业务关联的域的域名。
S332，SMF向EASDF发送该信息#A。相应地，EASDF接收该信息#A。
作为一种方式，SMF可以向EASDF发送域名系统上下文(DNS context)，该信息#A可以承载于DNS context中。
S333，终端向EASDF发送请求消息#B。相应地，EASDF接收该请求消息#B。
该请求消息#B请求用于执行目标业务的应用服务器。该请求消息#B中包括目标业务的标识。该请求消息#B中还可以包括目标业务关联的域名。可选地，目标业务的标识可以包含于该域名中；或者不包含于该域名中，作为一个单独的参数。
作为一种方式，该请求消息#B可以为DNS请求消息。
S334，EASDF向终端发送响应消息#B。相应地，终端接收响应消息#B。该响应消息#B中包括目标应用服务器的标识。
作为一种方式，EASDF根据信息#A以及请求消息#B中包括的目标业务的标识，确定目标应用服务器，并向终端发送目标应用服务器的标识(例如，目标应用服务器的IP)。
可选地，在S334之前，EASDF可以判断是否触发通知(notify)操作，当需要进行notify操作时，EASDF向SMF发送notify操作请求消息。SMF根据notify操作请求消息， 判断是否插入上行分类器(uplink classifier，ULCL)/分支点(branching point，BP)和本地PDU会话锚点(local PSA，L-PSA)。如果需要插入ULCL/BP和L-PSA，SMF插入ULCL/BP和L-PSA。SMF向EASDF发送notify操作应答消息。
第二种可能的情形(第一网元为SMF)：
针对该情形，在S310之前，该方法还包括上述S302和S303。在此不再赘述。
可选地，在PDU会话创建过程中，第一网元进行EASDF选择之后，可以触发向UDM发送第二请求消息。
此外，针对该情形，S320中第一网元获取第二信息的可能的实现方式可以为：
第一网元从UDR获取候选应用服务器所在的DN内的网络状态；和/或，第一网元可以根据终端的标识，确定终端当前关联的UPF，并从该UPF获取终端到RAN的网络状态；和/或，第一网元可以根据候选应用服务器所在的DN的标识(DNAI)，确定候选UPF，并从候选UPF获取RAN到候选UPF的网络状态。
针对该情形，在S330之后，该方法还包括上述S332-S334。在此不再赘述。
第三种可能的情形(第一网元为CSMF)：
针对该情形，在S310之前，该方法还包括
S304，终端向EASDF发送请求消息#B。相应地，EASDF接收该请求消息#B。
该请求消息#B请求用于执行目标业务的应用服务器。该请求消息#B中包括目标业务的标识。该请求消息#B中还可以包括目标业务关联的域名。可选地，目标业务的标识可以包含于该域名中；或者不包含于该域名中，作为一个单独的参数。
作为一种方式，该请求消息#B可以为DNS请求消息。即，S310是在终端发起DNS请求之后进行的。
S305，EASDF(第三网元的一例)向第一网元发送目标业务的标识。相应地，第一网元从EASDF获取目标业务的标识。
应理解，目标业务的标识可以承载于上述第三请求消息中。即，此时，第三请求消息包括终端的标识和目标业务的标识。该第三请求消息中还可以包括目标业务关联的域名。
此外，针对该情形，S320中第一网元获取第二信息的可能的实现方式为：
第一网元从本地或者UDR获取候选应用服务器所在的DN内的网络状态。和/或，第一网元从SMF获取终端到RAN的网络状态；和/或，第一网元从SMF获取RAN到候选UPF的网络状态。具体可以参考第一种可能的情形，在此不再赘述。
该SMF为终端关联的SMF。具体地，第一网元可以向UDM发送终端的标识，并从UDM获取终端关联的SMF。
针对该情形，在S330之后，该方法还包括：
S331，第一网元向SMF发送信息#A。相应地，SMF接收信息#A。
信息#A所包括的内容如上，在此不再赘述。
作为一种方式，第一网元可以通过EASDF向SMF发送信息#A。例如，通过EASDF的notify接口实现。
S332，SMF向EASDF发送该信息#A。相应地，EASDF接收该信息#A。
作为一种方式，SMF可以向EASDF发送域名系统上下文(DNS context)，该信息#A可以承载于DNS context中。
可选地，在S332之前，SMF可以根据信息#A，判断是否插入ULCL/BP和L-PSA。如果需要插入ULCL/BP和L-PSA，则SMF插入ULCL/BP和L-PSA。
S334，EASDF向终端发送响应消息#B。相应地，终端接收响应消息#B。该响应消息#B中包括目标应用服务器的标识。
作为一种方式，EASDF根据信息#A以及请求消息#B中包括的目标业务的标识，确定目标应用服务器，并向终端发送目标应用服务器的标识(例如，目标应用服务器的IP)。
第四种可能的情形(第一网元为SMF)：
针对该情形，在S310之前，该方法还包括上述S304和S305，在此不再赘述。
此外，针对该情形，S320中第一网元获取第二信息的可能的实现方式与第二种可能的情形相同。
针对该情形，在S330之后，该方法还包括上述S332和S334，在此不再赘述。可选地，在S332之前，SMF可以根据信息#A，判断是否插入ULCL/BP和L-PSA。如果需要插入ULCL/BP和L-PSA，则SMF插入ULCL/BP和L-PSA。
第五种可能的情形(第一网元为CSMF)：
S306，终端向本地(local)域名系统(domain name system，DNS)服务器(server)/解析器(resolver)发送请求消息#B。相应地，local DNS服务器接收该请求消息#B。
该请求消息#B用于请求执行目标业务的应用服务器。该请求消息#B中包括目标业务的标识。该请求消息#B中还可以包括目标业务关联的域名。可选地，目标业务的标识可以包含于该域名中；或者不包含于该域名中，作为一个单独的参数。
作为一种方式，终端可以通过ULCL/BP和L-PSA向local DNS服务器发送请求消息#B。
作为一种方式，该请求消息#B可以为DNS请求消息。
S307，local DNS服务器(第三网元的另一例)向第一网元发送目标业务的标识。相应地，第一网元从local DNS服务器接收目标业务的标识。
应理解，目标业务的标识可以承载于上述第三请求消息中。即，此时，第三请求消息包括终端的标识和目标业务的标识。该第三请求消息中还包括目标业务关联的域名。
此外，针对该情形，S320中第一网元获取第二信息的可能的实现方式与第三种可能的情形相同，在此不再赘述。
针对该情形，在S330之后，该方法还包括：
S331，第一网元向SMF发送信息#A。相应地，SMF接收信息#A。
信息#A所包括的内容如上，在此不再赘述。
可选地，SMF可以根据信息#A，判断是否插入ULCL/BP和L-PSA。如果需要插入ULCL/BP和L-PSA，则SMF插入ULCL/BP和L-PSA。
S335，第一网元向local DNS服务器发送信息#A。相应地，local DNS服务器接收信息#A。
S336，local DNS服务器向终端发送响应消息#B。相应地，终端接收响应消息#B。该响应消息#B中包括目标应用服务器的标识。
作为一种方式，local DNS服务器根据信息#A以及请求消息#B中包括的目标业务的标识，确定目标应用服务器，并向终端发送目标应用服务器的标识(例如，目标应用服务 器的IP)。
根据前述方法，图4为本申请实施例提供的一种通信装置，该通信装置包括收发单元401和处理单元402。
其中，收发单元401可以用于实现相应的通信功能。收发单元401还可以称为通信接口或通信单元。处理单元402可以用于进行处理操作。
可选地，该装置还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元402可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中的装置的动作。
作为一种设计，该通信装置可以是前述实施例中的第一网元，也可以是第一网元的组成部件(如芯片)。
其中，收发单元，用于获取候选应用服务器的特征参数；收发单元，还用于获取服务链路的网络状态；处理单元，用于根据候选应用服务器的特征参数和服务链路的网络状态，从候选应用服务器中确定目标应用服务器。
在一种情况下，收发单元，还用于向第二网元发送第一请求消息；收发单元，还用于从第二网元接收第一响应消息，
在一种情况下，收发单元，还用于向数据管理网元发送第二请求消息；收发单元，还用于从数据管理网元接收第二响应消息，
在一种情况下，收发单元，还用于从会话管理网元接收第三请求消息。
在一种情况下，收发单元，还用于从第三网元获取目标业务的标识。
在一种情况下，收发单元，还用于从本地或者第二网元获取候选应用服务器所在的DN内的网络状态；和/或，收发单元，还用于从会话管理网元获取终端到接入网设备的网络状态；和/或，收发单元，还用于从会话管理网元获取接入网设备到候选用户面功能网元的网络状态。
在一种情况下，收发单元，还用于从用户面功能网元获取终端到接入网设备的网络状态；和/或，收发单元，还用于从候选用户面功能网元获取接入网设备到候选用户面功能网元的网络状态。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，这里的装置以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置可以具体为上述实施例中的第一网元，可以用于执行上述各方法实施例中与第一网元对应的各个流程和/或步骤，或者，装置可以具体为上述实施例中的网络管理网元，可以用于执行上述各方法实施例中与网络管理网元对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述通信装置具有实现上述方法中的装置所执行的相应步骤的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送 机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元401还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图4中的装置可以是前述方法实施例中的装置，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
本申请实施例还提供一种通信设备，如图5所示，包括：处理器501和通信接口502。处理器501用于执行存储器503存储的计算机程序或指令，或读取存储器503存储的数据，以执行上文各方法实施例中的方法。可选地，处理器501为一个或多个。通信接口502用于信号的接收和/或发送。例如，处理器501用于控制通信接口502进行信号的接收和/或发送。
可选地，如图5所示，该通信设备还包括存储器503，存储器503用于存储计算机程序或指令和/或数据。该存储器503可以与处理器501集成在一起，或者也可以分离设置。可选地，存储器503为一个或多个。
可选地，处理器501、通信接口502以及存储器503通过总线504相互连接；总线504可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。上述总线504可以分为地址总线、数据总线和控制总线等。为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
例如，处理器501用于执行存储器503存储的计算机程序或指令，以实现上文各个方法实施例中第一网元的相关操作。
应理解，本申请实施例中提及的处理器(如处理器501)可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device,CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
还应理解，本申请实施例中提及的存储器(如存储器503)可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本 申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (27)

  1. 一种确定应用服务器的方法，其特征在于，包括：
    第一网元获取候选应用服务器的特征参数，所述候选应用服务器能够执行终端的目标业务；
    第一网元获取服务链路的网络状态，所述服务链路为所述终端到所述候选应用服务器所在的数据网络DN的链路；
    第一网元根据所述候选应用服务器的特征参数和所述服务链路的网络状态，从所述候选应用服务器中确定目标应用服务器，所述目标应用服务器用于执行所述目标业务。
  2. 根据权利要求1所述的方法，其特征在于，
    所述特征参数包括应用服务器的标识、应用服务器能够执行的业务的标识以及应用服务器所在的DN的数据网络访问标识DNAI。
  3. 根据权利要求2所述的方法，其特征在于，所述特征参数还包括以下中的一项或多项：
    应用服务器的剩余容量、应用服务器的任务处理效率、应用服务器的任务存储效率、应用服务器所在的DN的数据网络名称DNN、应用服务器关联的应用功能网元的标识、应用服务器的位置、应用服务器所属的域的域名、应用服务器所属的网络切片的网络切片选择辅助信息NSSAI。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，
    所述方法还包括：
    所述第一网元向第二网元发送第一请求消息，所述第一请求消息中包括所述目标业务的标识，所述第一请求消息用于请求能够执行所述目标业务的应用服务器的特征参数；
    所述第一网元获取所述候选应用服务器的特征参数，包括：
    所述第一网元从所述第二网元接收第一响应消息，所述第一响应消息包括所述候选应用服务器的特征参数。
  5. 根据权利要求4所述的方法，其特征在于，
    所述方法还包括：
    所述第一网元向数据管理网元发送第二请求消息，所述第二请求消息用于请求所述终端相关的业务信息，所述第二请求消息包括所述终端的标识；
    所述第一网元从所述数据管理网元接收第二响应消息，所述第二响应消息包括所述目标业务的标识。
  6. 根据权利要求5所述的方法，其特征在于，
    所述方法还包括：
    所述第一网元从会话管理网元接收第三请求消息，所述第三请求消息用于请求所述第一网元为所述终端选择应用服务器，所述第三请求消息包括所述终端的标识。
  7. 根据权利要求4所述的方法，其特征在于，
    所述方法还包括：
    所述第一网元从第三网元获取所述目标业务的标识，其中，所述第三网元为边缘应用 服务器发现网元或者域名系统DNS服务器。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述服务链路的网络状态包括：
    所述候选应用服务器所在的DN内的网络状态，和/或，所述终端到接入网设备的网络状态，和/或，所述接入网设备到候选用户面功能网元的网络状态；
    其中，所述候选用户面功能网元与所述候选应用服务器所在的DN所关联。
  9. 根据权利要求8所述的方法，其特征在于，
    所述第一网元获取所述服务链路的网络状态，包括：
    所述第一网元从本地或者第二网元获取所述候选应用服务器所在的DN内的网络状态；和/或，所述第一网元从会话管理网元获取所述终端到所述接入网设备的网络状态；和/或，所述第一网元从所述会话管理网元获取所述接入网设备到所述候选用户面功能网元的网络状态。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述第一网元向所述会话管理网元发送所述目标应用服务器的标识、所述终端的标识和所述目标业务的标识。
  11. 根据权利要求8所述的方法，其特征在于，
    所述第一网元获取所述服务链路的网络状态，包括：
    所述第一网元从所述终端接入的用户面功能网元获取所述终端到所述接入网设备的网络状态；和/或，所述第一网元从所述候选用户面功能网元获取所述接入网设备到所述候选用户面功能网元的网络状态。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述第一网元向边缘应用服务器发现网元发送所述目标应用服务器的标识、所述终端的标识和所述目标业务的标识。
  13. 一种第一网元，其特征在于，包括：
    收发单元，以及与所述收发单元连接的处理单元；
    所述收发单元，用于获取候选应用服务器的特征参数，所述候选应用服务器能够执行终端的目标业务；
    所述收发单元，还用于获取服务链路的网络状态，所述服务链路为所述终端到所述候选应用服务器所在的数据网络DN的链路；
    所述处理单元，用于根据所述候选应用服务器的特征参数和所述服务链路的网络状态，从所述候选应用服务器中确定目标应用服务器，所述目标应用服务器用于执行所述目标业务。
  14. 根据权利要求13所述的网元，其特征在于，
    所述特征参数包括应用服务器的标识、应用服务器能够执行的业务的标识和应用服务器所在的DN的数据网络访问标识DNAI。
  15. 根据权利要求14所述的网元，其特征在于，
    所述特征参数还包括以下中的一项或多项：
    应用服务器的剩余容量、应用服务器的任务处理效率、应用服务器的任务存储效率、应用服务器所在的DN的数据网络名称DNN、应用服务器关联的应用功能网元的标识、 应用服务器的位置、应用服务器所属的域的域名、应用服务器所属的网络切片的网络切片选择辅助信息NSSAI。
  16. 根据权利要求13-15中任一项所述的网元，其特征在于，
    所述收发单元，还用于向第二网元发送第一请求消息，所述第一请求消息中包括所述目标业务的标识，所述第一请求消息用于请求能够执行所述目标业务的应用服务器的特征参数；
    所述收发单元，还用于从所述第二网元接收第一响应消息，所述第一响应消息包括所述候选应用服务器的特征参数。
  17. 根据权利要求16所述的网元，其特征在于，
    所述收发单元，还用于向数据管理网元发送第二请求消息，所述第二请求消息用于请求所述终端相关的业务信息，所述第二请求消息包括所述终端的标识；
    所述收发单元，还用于从所述数据管理网元接收第二响应消息，所述第二响应消息包括所述目标业务的标识。
  18. 根据权利要求17所述的网元，其特征在于，
    所述收发单元，还用于从会话管理网元接收第三请求消息，所述第三请求消息用于请求所述第一网元为所述终端选择应用服务器，所述第三请求消息包括所述终端的标识。
  19. 根据权利要求16所述的网元，其特征在于，
    所述收发单元，还用于从第三网元获取所述目标业务的标识，其中，所述第三网元为边缘应用服务器发现网元或者域名系统DNS服务器。
  20. 根据权利要求13-19中任一项所述的网元，其特征在于，所述服务链路的网络状态包括：
    所述候选应用服务器所在的DN内的网络状态，和/或，所述终端到接入网设备的网络状态，和/或，所述接入网设备到候选用户面功能网元的网络状态；
    其中，所述候选用户面功能网元与所述候选应用服务器所在的DN所关联。
  21. 根据权利要求20所述的网元，其特征在于，
    所述收发单元，还用于从本地或者第二网元获取所述候选应用服务器所在的DN内的网络状态；和/或，
    所述收发单元，还用于从会话管理网元获取所述终端到所述接入网设备的网络状态；和/或，
    所述收发单元，还用于从所述会话管理网元获取所述接入网设备到所述候选用户面功能网元的网络状态。
  22. 根据权利要求21所述的网元，其特征在于，
    所述收发单元，还用于向所述会话管理网元发送所述目标应用服务器的标识、所述终端的标识和所述目标业务的标识。
  23. 根据权利要求20所述的网元，其特征在于，
    所述收发单元，还用于从所述终端接入的用户面功能网元获取所述终端到所述接入网设备的网络状态；和/或，
    所述收发单元，还用于从所述候选用户面功能网元获取所述接入网设备到所述候选用户面功能网元的网络状态。
  24. 根据权利要求23所述的网元，其特征在于，
    所述收发单元，还用于向边缘应用服务器发现网元发送所述目标应用服务器的标识、所述终端的标识和所述目标业务的标识。
  25. 一种通信设备，其特征在于，包括：通信接口和处理器，所述处理器用于执行计算机程序或指令，使得所述通信设备执行如权利要求1-12中任一项所述的方法。
  26. 一种计算机可读存储介质，其特征在于，包括计算机程序或指令，当所述计算机程序或所述指令在计算机上运行时，使得所述计算机执行如权利要求1-12中任意一项所述的方法。
  27. 一种计算机程序产品，其特征在于，包含指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-12中任意一项所述的方法。
PCT/CN2022/139487 2021-12-17 2022-12-16 确定应用服务器的方法和装置 WO2023109937A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22906682.4A EP4429201A1 (en) 2021-12-17 2022-12-16 Method and apparatus for determining application server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111552660.7 2021-12-17
CN202111552660.7A CN116266904A (zh) 2021-12-17 2021-12-17 确定应用服务器的方法和装置

Publications (1)

Publication Number Publication Date
WO2023109937A1 true WO2023109937A1 (zh) 2023-06-22

Family

ID=86743778

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/139487 WO2023109937A1 (zh) 2021-12-17 2022-12-16 确定应用服务器的方法和装置

Country Status (3)

Country Link
EP (1) EP4429201A1 (zh)
CN (1) CN116266904A (zh)
WO (1) WO2023109937A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104010290A (zh) * 2014-06-16 2014-08-27 武汉博睿达信息技术有限公司 基于用户信息的ims应用服务器选择系统及选择方法
US20140341085A1 (en) * 2013-05-14 2014-11-20 Qualcomm Incorporated Selecting an application server at which to register one or more user equipments for an internet protocol multimedia subsystem (ims) session
CN105491631A (zh) * 2016-01-13 2016-04-13 广东欧珀移动通信有限公司 一种移动终端定位方法、装置及移动终端
CN106487840A (zh) * 2015-08-27 2017-03-08 中国移动通信集团公司 一种内容服务器的确定方法、平台及调度服务器
CN108132839A (zh) * 2016-11-30 2018-06-08 中国移动通信有限公司研究院 一种资源调度方法及装置
US20210136177A1 (en) * 2019-10-31 2021-05-06 Qualcomm Incorporated Edge computing platform capability discovery

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140341085A1 (en) * 2013-05-14 2014-11-20 Qualcomm Incorporated Selecting an application server at which to register one or more user equipments for an internet protocol multimedia subsystem (ims) session
CN104010290A (zh) * 2014-06-16 2014-08-27 武汉博睿达信息技术有限公司 基于用户信息的ims应用服务器选择系统及选择方法
CN106487840A (zh) * 2015-08-27 2017-03-08 中国移动通信集团公司 一种内容服务器的确定方法、平台及调度服务器
CN105491631A (zh) * 2016-01-13 2016-04-13 广东欧珀移动通信有限公司 一种移动终端定位方法、装置及移动终端
CN108132839A (zh) * 2016-11-30 2018-06-08 中国移动通信有限公司研究院 一种资源调度方法及装置
US20210136177A1 (en) * 2019-10-31 2021-05-06 Qualcomm Incorporated Edge computing platform capability discovery

Also Published As

Publication number Publication date
CN116266904A (zh) 2023-06-20
EP4429201A1 (en) 2024-09-11

Similar Documents

Publication Publication Date Title
US11564154B2 (en) Apparatus, method and computer program related to information about SCP(s) and SEPP(s) stored in NRF
EP3611960B1 (en) Network overload control method and device
WO2019091228A1 (zh) 通信方法和网络设备
US10674421B2 (en) Data packet processing method and device
WO2020068356A1 (en) User plane system selection based on latency
WO2021243837A1 (zh) 基于ursp规则的应用数据路由方法及用户设备
EP3849242A1 (en) Method and apparatus for dynamically adjusting pdu session
JP2021158664A (ja) 間接通信用のエラー処理のための方法、装置、およびコンピュータプログラム製品
CN109474954B (zh) 一种会话建立方法及装置
US20110228687A1 (en) Methods and apparatus for establishing reciprocal inter-radio access technology neighbor relations
US20230188974A1 (en) Network Capability Exposure Method, Apparatus, and System
WO2019057140A1 (zh) 应用上下文的处理方法和装置
WO2023091352A9 (en) Predictive user plane function (upf) load balancing based on network data analytics
CN104170513A (zh) 管理移动通信网络内的分组服务呼叫
WO2018141278A1 (zh) 无线通信方法、用户设备、接入网设备和网络系统
CN116866981A (zh) 通信方法和装置
EP3641399A1 (en) Method and device for determining service path
CN110677925B (zh) 一种无线承载处理的方法及终端设备
WO2023020297A1 (zh) 中继选择方法和装置
WO2023109937A1 (zh) 确定应用服务器的方法和装置
EP3972142B1 (en) Policy control function fallback
JP7493622B2 (ja) データ転送のサポート
US11903073B2 (en) Dynamic adjustment method and apparatus for PDU session
US11050796B2 (en) Interface session discovery within wireless communication networks
EP3869755A1 (en) Control plane network function, user plane network function, and packet processing method using same

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: 22906682

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022906682

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022906682

Country of ref document: EP

Effective date: 20240603

ENP Entry into the national phase

Ref document number: 2022906682

Country of ref document: EP

Effective date: 20240603

NENP Non-entry into the national phase

Ref country code: DE