WO2021189869A1 - 一种获取信息的方法及装置 - Google Patents

一种获取信息的方法及装置 Download PDF

Info

Publication number
WO2021189869A1
WO2021189869A1 PCT/CN2020/127921 CN2020127921W WO2021189869A1 WO 2021189869 A1 WO2021189869 A1 WO 2021189869A1 CN 2020127921 W CN2020127921 W CN 2020127921W WO 2021189869 A1 WO2021189869 A1 WO 2021189869A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
information
instance
application
edge
Prior art date
Application number
PCT/CN2020/127921
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 CN202080054615.6A priority Critical patent/CN114175600B/zh
Publication of WO2021189869A1 publication Critical patent/WO2021189869A1/zh

Links

Images

Classifications

    • 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/4541—Directories for service discovery
    • 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/1021—Server selection for load balancing based on client or server locations
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a method and device for obtaining information.
  • the multi-access edge computing technology can provide information technology (IT) capabilities and cloud computing capabilities for the radio access network by deploying a general server on the radio access side.
  • one application can correspond to one instance or multiple instances.
  • each of the multiple instances is managed by an edge-enabled server.
  • other devices need to obtain the information of multiple instances of the application, they need to separately query multiple edge-enabled servers that manage the multiple instances. As a result, a large amount of signaling overhead and service delay will be brought, thereby affecting the user experience.
  • the embodiment of the present application provides a method for obtaining information, which is used to obtain and save the information of the application instance, so that the user can directly obtain the information of the application instance from the first server without querying the second server.
  • Obtaining the information of the application instance with the third server can save signaling overhead and reduce service delay.
  • an embodiment of the present application provides a method for obtaining information
  • the implementation body of the method includes a first server, a second server, and a third server.
  • the first server is a server serving the second server and the third server.
  • the first server may receive the information of the first instance of the application from the second server, and the first server may receive the information of the second instance of the application from the third server.
  • the information of the first instance includes identification information of the application and first information, and the first information is used to indicate the location of the first instance;
  • the information of the second instance includes identification information and second information of the application,
  • the second information is used to indicate the location of the second instance.
  • the first server will save the information of the first instance and the information of the second instance. Therefore, the storage problem of the information of the first instance of the application and the information of the second instance of the application is solved.
  • the first server that manages the information of the application instance can receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server, respectively, and transfer the application
  • the information of the first instance of and the information of the second instance of the application are stored in the first server. Therefore, the problem of storing the information of the application instance in the edge network is solved, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device).
  • the other device can directly obtain the information of the instance of the application from the first server without querying the second server and the third server to obtain the information of the instance of the application.
  • Information can save signaling overhead and slow down service delay.
  • the first server receives the area information of the second server from the second server or the first network element; the first server obtains the location of the user equipment Information; the first server determines the target server according to the area information of the second server and the location information of the user equipment.
  • the first network element is a NEF network element, a UDM network element, a UDR network element, a PCF network element, or an NRF network element.
  • the first server receives the application identifier from the EEC, and the target server serves the application instance corresponding to the application identifier.
  • the method further includes: the first server sends the area information of the target server to the user equipment.
  • the method further includes: the first server sending to the user equipment the cell identifier or the tracking area identifier corresponding to the target server area information.
  • the method further includes: the first server sending the area information of the location of the user equipment to the user equipment.
  • the method further includes: the first server sends a first message to the second network element, and the first message is used to influence the user equipment to the The routing information of the target server, the first message includes the user identifier and the application identifier of the user equipment, and the first message further includes user traffic description information of the target server and/or area information of the target server.
  • the method further includes: the first server sends a second message to the second network element, and the second message is used to influence the user equipment to the The routing information of the application instance corresponding to the target server, the second message includes the user identification and the application identification of the user equipment, and the first message further includes the user traffic description information of the application instance and/or the area information of the application instance.
  • the second network element includes any of a session management function SMF network element, an access management function AMF network element, and a network capability opening function NEF network element One item.
  • the first information includes the Internet Protocol IP address of the first instance and one or more of the following: the access identifier of the first edge network Information, the IP address of the first edge network, or the IP address of the first edge-enabled server, the second server is located in the first edge network; the second information includes the IP address of the second instance and the following Or multiple items: the access identification information of the second edge network, the IP address of the second edge network, or the IP address of the second edge enabling server, where the third server is located in the second edge network.
  • the first information in the information of the first instance and the second information in the information of the second instance are further limited.
  • the first information in addition to the Internet Protocol IP address of the first instance, the first information also includes: the access identification information of the first edge network, the IP address of the first edge network, or the first edge network.
  • the specific location of the first instance of the application can be determined by various identification information or IP address information, so that the first server can accurately determine the application while acquiring the information of the first instance of the application. The specific location of the first instance.
  • the first server can also accurately determine the specific location of the second instance of the application.
  • the method further includes: the first server sends the first application program interface to the second server API discovery request, the first API discovery request includes discovery type information, the discovery type information is used to indicate that the first API discovery request is used to request an instance of the application, or the discovery type information is used to indicate that the first API discovery
  • the request is used to request an instance and API of the application, and the instance of the application includes the first instance and the second instance; the first server sends the first API discovery request to the third server.
  • the signaling interaction between the first server and the second server can reuse the discovery mechanism in the API general architecture CAPIF.
  • the first server may send a first API discovery request to the second server and the third server to trigger the second server to send the information of the first instance of the application to the first server, and to trigger the first instance of the application.
  • the three servers send the information of the second instance of the application to the first server. Therefore, the first server does not need to separately configure the request to obtain the information of the application instance, which can save the signaling overhead between the first server, the second server, and the third server, thereby reducing the access caused by increased signaling. Latency of application.
  • the first server receiving information of the first instance of the application from the second server includes: the first server Receive a first API discovery response from the second server, the first API discovery response includes information about the first instance; the first server receives information about a second instance of the application from the third server, including: the first server A second API discovery response is received from the third server, and the second API discovery response includes the information of the second instance.
  • the discovery mechanism in the API common architecture CAPIF for signaling interaction multiplexing between the first server and the second server is proposed, but also the first instance of sending the second server to the first server is proposed.
  • the information is carried in the first API discovery response.
  • the information of the second instance sent by the third server to the first server is carried in the second API discovery response. Therefore, the first server can use the existing signaling to receive the information of the application instance from the second server and the third server.
  • the second server or the third server does not need to be configured to send the application instance information separately.
  • the information message of the instance Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the first server receiving information of the first instance of the application from the second server includes: the first server receiving the first instance of the application from the second server API publishing request, the first API publishing request includes the information of the first instance of the application, the first API publishing request is used to publish the API and/or the first instance; the first server receives the application information from the third server
  • the information of the second instance includes: the first server receives a second API publishing request from the third server, the second API publishing request includes information about the second instance of the application, and the second API publishing request is used to publish the API And/or this second instance.
  • the signaling interaction between the first server and the second server can reuse the publishing mechanism in the API general architecture CAPIF, and it is also proposed to send the second server to the first server of the first server.
  • the information of the instance is carried in the first API release request.
  • the information of the second instance sent by the third server to the first server is carried in the second API release request. Therefore, the first server can use the existing signaling to receive the information of the application instance from the second server and the third server.
  • the second server or the third server does not need to be configured to send the application instance information separately.
  • the information message of the instance Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the first API publishing request further includes publishing type information, and the publishing type information is used to indicate an instance of publishing the application And/or publish the API, the instance of the application includes the first instance;
  • the second API publication request also includes publication type information, the publication type information is used to indicate the instance of the application and/or the publication of the API, the instance of the application Including this second example.
  • the first API publishing request and the second publishing request further include publishing type information, and the publishing type information is used to indicate the type of content to be published. Therefore, the first server can determine whether the information carried in the first API publishing request or the second API publishing request includes information about the instance of the application according to the publishing type information.
  • the method before the first server receives the information of the first instance of the application from the second server, or, Before the first server receives the information of the first instance of the application from the second server, the method further includes: the first server sends a subscription request to the second server and the third server, and the subscription request is used to request subscription to the application Information about the instance.
  • the signaling interaction between the first server and the second server may be based on a subscription-notification mechanism, that is, the first server subscribes to the information of the application instance from the second server or the third server .
  • the second server or the third server will send the information of the application instance to the first server. Therefore, the first server only needs to send a message to the second server or the third server once to receive the information of the application instance from the second server or the third server. Therefore, the signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the subscription request includes a subscription condition
  • the subscription condition is used to indicate an instance of the application
  • the instance of the application includes the The first example and the second example.
  • the subscription condition may be carried in the subscription request to indicate that the content requested to be subscribed by the first server is the information of the instance of the application, or to indicate the type of the instance of the application that the first server requests to subscribe.
  • the application further includes one or more of the following: the identification information of the first edge-enabled server, or the service scope information of the first instance; the information of the second instance of the application further includes one or more of the following Item: identification information of the second edge-enabled server, or service scope information of the second instance.
  • the information of the instance of the application proposed may also include the identification information of the edge-enabled server, or the service range information of the instance of the application.
  • the identification information of the edge-enabled server is used to identify the identity of the edge-enabled server, so that other servers or the first device can accurately find the edge-enabled server.
  • the service scope information of the instance of the application is used to indicate the scope of the users who use the instance of the application, and may also refer to the locations where the users served by the instance of the application may be located. Therefore, this embodiment expands the specific implementation manner of the information of the application instance, so that the information of the application instance can be adapted to the requirements of specific scenarios.
  • the first The server configures the server for the edge network.
  • the specific implementation manner of the first server in the edge network is clarified, and the first server may configure the server for the edge network in the edge network.
  • the second The server or the third server is any one of the following: an edge-enabled server; or a network management server in an edge network; or an application instance server; or an OSS network element of an operation support system.
  • the specific implementation manners of the second server and the third server are clarified, where the second server and the third server may be the same server among the foregoing multiple servers, or may be different among the foregoing multiple servers. Server. Since the second server and the third server can have multiple implementation manners, the diversity of solutions is increased.
  • the method It also includes: the first server receives the identification information of the application and the location information of the first device from the first device; the first server sends the IP address of the third instance to the first device, and the third instance is used by the application
  • the identification information of the first device, the location information of the first device, the information of the first instance of the application, and the information of the second instance of the application are determined, and the third instance is the first instance or the second instance.
  • the first server can determine the third instance from the foregoing first and second instances according to the identification information of the application sent by the first device and the location information of the first device, and the third instance is determined by The identification information of the application, the location information of the first device, the information of the first instance of the application, and the information of the second instance of the application are determined.
  • the first device when the first device needs to obtain an instance of the application, the first device does not need to search for the information of the instance of the application in the second server and the third server in turn, but can directly The information of the instance of the application is obtained from the first server.
  • the signaling procedure for the first device to obtain the information of the instance of the application can be reduced, thereby reducing the network delay caused by increased signaling.
  • the first server may also select an application instance that meets the requirements of the first device for the first device according to the requirements of the first device. Therefore, the process of obtaining the information of the application instance by the first device is optimized.
  • the method further includes: when the IP address of the third instance is the IP address of the first instance , The first server sends one or more of the following to the first device: the access identification information of the first edge network, the IP address of the first edge network, or the IP address of the first edge-enabled server;
  • the IP address of the third instance is the IP address of the second instance
  • the first server sends one or more of the following to the first device: the access identification information of the second edge network, the second edge The IP address of the network or the IP address of the second edge-enabled server.
  • the first server in addition to sending the IP address of the application instance to the first device, the first server also sends the edge network access identification information and the edge network's access identification information to the first device.
  • the edge network access identification information One or more of the IP address or the IP address of the edge-enabled server. Therefore, the diversity of information provided by the first server to the first device is increased, so that the information of the application instance sent by the first server to the first device can better meet the requirements of the first device.
  • the first device is a terminal device or an edge-enabled server.
  • the first device may be a terminal device, and the first device may also be an edge-enabled server. Therefore, the diversity of the first device is increased, so that the first device can perform the foregoing method as a different device or server in different application scenarios.
  • the The second server or the third server is any one of the following: an application instance management network element, which is a network element used to deploy the application instance; or an edge-enabled server manages a network element, and the edge enables The energy server management network element is used to manage the edge-enabled server.
  • the second server and the third server may also be other network elements besides the edge network, for example, an application instance management network element or an edge-enabled server management network element. Therefore, the foregoing implementation manner may also be applicable to the signaling interaction process between the first server and a network other than the edge network.
  • an embodiment of the present application provides a method for obtaining information, and the implementation body of the method includes a first server and a second server.
  • the second server obtains information of the first instance of the application, the information of the first instance includes identification information of the application and first information, and the first information is used to indicate the location of the first instance; the second server Sending the information of the first instance to the first server, where the first server is a server serving the second server.
  • the other device can directly obtain the information of the instance of the application from the first server without querying the second server and the third server to obtain the information of the instance of the application. Information can save signaling overhead and slow down service delay.
  • the second server can send the acquired information of the first instance of the application to the first server, so that the first server can save the information of the first instance sent by the second server in time. Therefore, it is advantageous for the first server to save the information of the application instance in the edge network, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device).
  • other devices such as the first device do not need to obtain the information of the instance of the application from the second server, but can directly obtain the information of the instance of the application from the first server. Therefore, you can save The process for the first server to obtain the information of the instance of the application.
  • the second server sends the area information of the second server to the first server.
  • the first information includes the Internet Protocol IP address of the first instance and one or more of the following: the access identifier of the first edge network Information, the IP address of the first edge network, or the IP address of the first edge-enabled server, and the second server is located in the first edge network.
  • the first information in the information of the first instance is further limited.
  • the first information in addition to the Internet Protocol IP address of the first instance, the first information also includes: the access identification information of the first edge network, the IP address of the first edge network, or the first edge network.
  • the access identification information of the first edge network in addition to the Internet Protocol IP address of the first instance, the first information also includes: the access identification information of the first edge network, the IP address of the first edge network, or the first edge network.
  • One or more of the IP addresses of an edge-enabled server One or more of the IP addresses of an edge-enabled server. Therefore, the specific location of the first instance of the application can be determined through various identification information or IP address information, so that the first server can accurately determine the application while acquiring the information of the first instance of the application. The specific location of the first instance.
  • the second server acquiring information of the first instance of the application includes: the second server obtains information from The first instance server of the application receives the identification information of the first instance and the IP address of the first instance; the second server obtains the first information from the second server.
  • the manner in which the second server obtains the information of the first instance of the application is clarified.
  • the identification information of the first instance and the IP address of the first instance can be assigned by the second instance.
  • the server directly obtains the first instance server of the application, and then the second server determines the first information.
  • the information of the first instance is obtained by the second server from a different server. Therefore, the second server can ensure the integrity of the information of the first instance.
  • the second server acquiring information of the first instance of the application includes: the second server obtains information from The first instance server of the application receives the information of the first instance.
  • the second server can directly obtain the information of the first instance from the first instance server of the application, that is, the second server can directly obtain the identification information of the first instance from the first instance server , The IP address of the first instance and the first information. Therefore, the process for the second server to obtain the information of the first instance can be simplified.
  • the method also Including: the second server receives a first application program interface API discovery request from the first server, the first API discovery request includes discovery type information, and the discovery type information is used to indicate that the first API discovery request is used to request the application Or, the discovery type information is used to indicate that the first API discovery request is used to request the instance and API of the application, and the instance of the application includes the first instance.
  • the signaling interaction between the first server and the second server can reuse the discovery mechanism in the API general architecture CAPIF.
  • the first server may send the first API discovery request to the second server to trigger the second server to send the information of the first instance of the application to the first server. Therefore, the first server does not need to separately configure the request for obtaining the information of the application instance, which can save the signaling overhead between the first server and the second server, thereby reducing the delay in accessing the application caused by increased signaling.
  • the second server sending the information of the first instance to the first server includes: A server sends a first API discovery response, and the first API discovery response includes the information of the first instance.
  • the first server can receive the information of the instance of the application from the second server by using existing signaling, and the second server does not need to separately configure a message for sending the information of the instance of the application. Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the second The server sending the information of the first instance to the first server includes: the second server sends a first API publishing request to the first server, the first API publishing request includes the information of the first instance of the application, the first The API publishing request is used to publish the API and/or the first instance.
  • the signaling interaction between the first server and the second server can reuse the publishing mechanism in the API general architecture CAPIF, and it is also proposed to send the second server to the first server of the first server.
  • the information of the instance is carried in the first API release request. Therefore, the first server can use existing signaling to respectively receive the information of the application instance from the second server, and the second server does not need to separately configure a message for sending the information of the application instance. Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the first API publishing request further includes publishing type information, and the publishing type information is used to indicate an instance of publishing the application And/or publish the API, and the instance of the application includes the first instance.
  • the first API publishing request and the second publishing request further include publishing type information, and the publishing type information is used to indicate the type of content to be published. Therefore, the first server can determine whether the information carried in the first API publishing request includes information about the instance of the application according to the publishing type information.
  • the second server obtains the information of the first instance of the application, including :
  • the second server receives a third API publishing request from the first instance server of the application, the third API publishing request includes the identification information of the first instance and the IP address of the first instance, and the third API publishing request is used for Publish the API and/or the first instance.
  • the signaling interaction between the first server and the second server may be based on a subscription-notification mechanism, that is, the first server subscribes to the information of the application instance from the second server, then the first server should be When the information of the application instance in the second server is updated, the second server will send the information of the application instance to the first server. Therefore, the first server only needs to send a message to the second server once to receive information from the second server or the instance of the application. Therefore, the signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the method further includes: the second server receives a subscription request from the first server, and the subscription request is used to request to subscribe to the information of the instance of the application.
  • the subscription request includes a subscription condition
  • the subscription condition is used to indicate an instance of the application
  • the instance of the application includes the The first instance
  • the subscription condition may be carried in the subscription request to indicate that the content requested to be subscribed by the first server is the information of the instance of the application, or to indicate the type of the instance of the application that the first server requests to subscribe.
  • the application The information of the first instance further includes one or more of the following: identification information of the first edge-enabled server, or service scope information of the first instance.
  • the information of the instance of the application proposed may also include the identification information of the edge-enabled server, or the service range information of the instance of the application.
  • the identification information of the edge-enabled server is used to identify the identity of the edge-enabled server, so that other servers or the first device can accurately find the edge-enabled server.
  • the service scope information of the instance of the application is used to indicate the scope of the users who use the instance of the application, and can also refer to the locations where the users served by the instance of the application may be located. Therefore, this embodiment expands the specific implementation manner of the information of the application instance, so that the information of the application instance can be adapted to the requirements of specific scenarios.
  • the The first server configures the server for the edge network.
  • the specific implementation manner of the first server in the edge network is clarified, and the first server may configure the server for the edge network in the edge network.
  • the The second server is any one of the following: an edge-enabled server; or, a network management server in the edge network.
  • the specific implementation of the second server is clarified, where the second server may be the same server among the aforementioned multiple types of servers, or may be a different server among the aforementioned multiple types of servers. Since the second server can be implemented in multiple ways, the diversity of solutions is increased.
  • the second server is any one of the following: or, the application instance server, which includes the first instance server of the application or the second instance server of the application; or, the operation support system OSS network element.
  • the The second server is any one of the following: an application instance management network element, which is a network element used to deploy the application instance; or an edge-enabled server management network element, which is an edge-enabled server management network element Meta is used to manage the edge-enabled server.
  • the second server may also be a network element other than the edge network, for example, an application instance management network element or an edge-enabled server management network element. Therefore, the foregoing implementation manner may also be applicable to the signaling interaction process between the first server and a network other than the edge network.
  • the present application provides a method for obtaining information, including: a user equipment receives area information of a fourth server from a first server, where the first server is a server serving the fourth server; and the user equipment obtains the first server. Area information, where the first area information is used to indicate the area where the user equipment is located; the user equipment triggers the switching of the fourth server according to the area information of the fourth server and the first area information.
  • the first server may send the area information of the fourth server to the user equipment, and then the user equipment may use the obtained first area information and the area of the aforementioned fourth server
  • the information determines whether to update the fourth server, which can be understood as whether to switch the fourth server to the fifth server.
  • the user equipment may trigger the update of the fourth server according to the comparison of the foregoing two area information.
  • the enabling layer or the application layer can obtain the DNAI information corresponding to the fourth server, without requiring the operator to provide the topology information (cell identification list or tracking list) in the network format corresponding to the fourth server, and can also be combined to obtain from the network layer And the DNAI information of the fourth server acquired by the enabling layer to determine whether the fourth server needs to be changed. In this way, the topology information of the operator's network can also be protected.
  • the area information of the fourth server does not match the first area information.
  • the user equipment acquiring the first area information includes: the user equipment receives the first area information from a second network element; or, the user equipment The corresponding relationship between the first information and the first area information is received from the second network element, where the first information is a cell identifier or a tracking area identifier corresponding to the area indicated by the first area information; the user equipment and The second information of the user equipment determines the first area information, and the second information is used to indicate the cell identifier or tracking area identifier of the location of the user equipment.
  • the method before the user equipment receives the area information of the fourth server from the first server, the method further includes: the user equipment sends the application to the first server Identification, the application identification is used for determining the fourth server.
  • the fourth server when the first server is an edge configuration server, the fourth server is an edge-enabled server, and the fourth server serves the application identifier corresponding to Or, when the first server is an edge-enabled server, the fourth server is an application instance corresponding to the application identifier.
  • the second network element includes a session management function SMF network element or an access management function AMF network element, a network capability opening function NEF, and an edge configuration server ECS , Edge-enabled server EES.
  • the present application provides a method for obtaining information, including: a first server receives an application identifier from a user equipment; the first server determines a fourth server according to the application identifier, and the first server serves the fourth server The server; the first server sends the area information of the fourth server to the user equipment, the area information of the fourth server and the first area information are used for the confirmation of the fifth server, and the first area information is used to indicate where the user equipment is located area.
  • the fourth server when the first server is an edge configuration server, the fourth server is an edge-enabled server, and the fourth server serves the application identifier corresponding to Or, when the first server is an edge-enabled server, the fourth server is an application instance corresponding to the application identifier.
  • the method further includes: the first server sends a first message to the second network element, the The first message is used to influence routing information from the user equipment to the fourth server, the first message includes the user identification and application identification of the user equipment, and the first message also includes the user traffic description information of the target server and/or The area information of the target server.
  • the method further includes: the first server sends a second message to the second network element, the The second message is used to influence routing information from the user equipment to the application instance corresponding to the fourth server, the second message includes the user identification and application identification of the user equipment, and the first message also includes the user traffic description of the application instance Information and/or area information of the application instance.
  • the present application provides a method for obtaining information, including: a second network element determines first area information of a user equipment, the first area information is used to indicate the area where the user equipment is located; The user equipment sends the first area information.
  • the second network element stores a correspondence relationship between the first information and the first area information, and the first information is corresponding to the first area
  • the cell identification or tracking area identification of the second network element; determining the first area information of the user equipment by the second network element includes: the second network element acquiring second information of the user equipment, the second information being the cell where the user equipment is located Identification or tracking area identification; the second network element determines the first area information of the user equipment according to the second information of the user equipment and the corresponding relationship.
  • the method further includes: the second network element receives a first message from the first server, and the first message is used to influence the user equipment to the target
  • the routing information of the server includes the user identification and application identification of the user equipment, the first message also includes the traffic description information of the target server and/or the area information of the target server, and the target server serves the application Identifies the corresponding application instance.
  • the method further includes:
  • the second network element receives a second message from the first server, the second message is used to influence routing information from the user equipment to an application instance corresponding to the target server, and the second message includes the user identification and application identification of the user equipment
  • the first message also includes the general description information of the application instance and/or the area information of the application instance.
  • the second network element includes a session management function SMF network element, an access management function AMF network element, a network capability opening function NEF network element, an ECS or Any one of EES.
  • the present application provides a method for obtaining information, including: a second network element sends a corresponding relationship between first area information and first information to a user equipment, and the first area information is used to indicate where the user equipment is located.
  • Area the first information is a cell identifier or a tracking area identifier corresponding to the first area.
  • the second network element includes a session management function SMF network element, an access management function AMF network element, a network capability opening function NEF network element, ECS Any one of EES.
  • an embodiment of the present application provides a device for acquiring information, and the device for acquiring information can implement the function of the first server in the foregoing method.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the apparatus for acquiring information includes a processor and a transceiver, and the processor is configured to process the apparatus for acquiring information to perform corresponding functions in the foregoing method.
  • the transceiver is used to implement the communication between the above-mentioned information acquisition device and the second server or the third server.
  • the apparatus for acquiring information may further include a memory, which is configured to be coupled with the processor and stores program instructions and data necessary for the apparatus for acquiring information.
  • an embodiment of the present application provides a device for acquiring information, which can implement the function of the second server in the foregoing method.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the apparatus for acquiring information includes a processor and a transceiver, and the processor is configured to process the apparatus for acquiring information to perform corresponding functions in the foregoing method.
  • the transceiver is used to implement the communication between the above-mentioned information acquisition device and the first server and the application instance server.
  • the apparatus for acquiring information may further include a memory, which is configured to be coupled with the processor and stores program instructions and data necessary for the apparatus for acquiring information.
  • an embodiment of the present application provides a device for acquiring information.
  • the device for acquiring information may be a first server or a chip in the first server.
  • the device for acquiring information may include a processing module and a transceiver module.
  • the processing module may be a processor, and the transceiver module may be a transceiver;
  • the first server may also include a storage module, and the storage module may be a memory; the storage module is used for An instruction is stored, and the processing module executes the instruction stored in the storage module, so that the first server executes the method introduced in the first aspect or any one of the implementation manners of the first aspect.
  • the processing module may be a processor, the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module, So that the first server executes the method introduced in the first aspect or any one of the implementation manners of the first aspect.
  • the storage module may be a storage module (for example, a register, a cache, etc.) in the chip, or a storage module (for example, a read-only memory, a random access memory, etc.) located outside the chip in the first server. ).
  • an embodiment of the present application provides a device for acquiring information.
  • the device for acquiring information may be a second server or a chip in the second server.
  • the device for acquiring information may include a processing module and a transceiver module.
  • the processing module may be a processor, and the transceiver module may be a transceiver;
  • the device for acquiring information through the Internet of Vehicles may also include a storage module, and the storage module may be a memory; the storage The module is used to store instructions, and the processing module executes the instructions stored in the storage module, so that the second server executes the method introduced in the second aspect or any one of the implementation manners of the second aspect.
  • the processing module may be a processor, the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module, So that the second server executes the method introduced in the second aspect or any one of the implementation manners of the second aspect.
  • the storage module may be a storage module (for example, register, cache, etc.) in the chip, or a storage module (for example, read-only memory, random access memory, etc.) located outside the chip in the second server.
  • an embodiment of the present application provides a device for acquiring information.
  • the device for acquiring information may be a user equipment or a chip in the user equipment.
  • the device for acquiring information may include a processing module and a transceiver module.
  • the processing module may be a processor, and the transceiver module may be a transceiver;
  • the device for acquiring information through the Internet of Vehicles may also include a storage module, which may be a memory; the storage module Used to store instructions, the processing module executes the instructions stored in the storage module, so that the user equipment executes the method introduced in the third aspect or any one of the implementation manners of the third aspect.
  • the processing module may be a processor, the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module to The user equipment is caused to execute the method introduced in the third aspect or any one of the implementation manners of the third aspect.
  • the storage module may be a storage module in the chip (for example, a register, a cache, etc.), or a storage module (for example, a read-only memory, a random access memory, etc.) located outside the chip in a user equipment.
  • an embodiment of the present application provides a communication system, which includes: a first server, a second server, and a third server; the second server is used to obtain information about the first instance of the application; The third server is used to obtain the information of the second instance of the application; the first server is used to receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server , And save the information of the first instance of the application and the information of the second instance of the application.
  • the embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to execute the implementation described in any one of the foregoing first to sixth aspects method.
  • the embodiments of the present application provide a computer-readable storage medium, including instructions, when the instructions are run on a computer, so that the computer executes any one of the foregoing first to sixth aspects.
  • the first server that manages the information of the application instance can receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server, respectively, and transfer the application
  • the information of the first instance of and the information of the second instance of the application are stored in the first server. Therefore, the problem of saving the information of the application instance in the edge network is solved, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device).
  • the other device can directly obtain the information of the instance of the application from the first server without querying the second server and the third server to obtain the information of the instance of the application.
  • Information can save signaling overhead and slow down service delay.
  • FIG. 1A is a system architecture diagram provided in an embodiment of this application.
  • FIG. 1B is a flowchart of a method for obtaining information in an embodiment of this application
  • FIG. 1C is another system architecture diagram of the method for obtaining information in an embodiment of this application.
  • FIG. 1D is another system architecture diagram of the method for obtaining information in an embodiment of this application.
  • FIG. 2 is another flowchart of the method for obtaining information in an embodiment of the application
  • FIG. 3A is a diagram of another system architecture adapted to the method for obtaining information in an embodiment of this application;
  • FIG. 3B is a diagram of another system architecture adapted to the method for obtaining information in an embodiment of the application
  • FIG. 4 is another flowchart of the method for obtaining information in an embodiment of the application
  • FIG. 5 is another flowchart of the method for obtaining information in an embodiment of this application.
  • FIG. 6A is a diagram of another system architecture adapted to the method for obtaining information in an embodiment of this application.
  • FIG. 6B is a diagram of another system architecture adapted to the method for obtaining information in an embodiment of this application.
  • FIG. 6C is a diagram of another system architecture adapted to the method for obtaining information in an embodiment of this application.
  • FIG. 7 is another flowchart of the method for obtaining information in an embodiment of the application.
  • FIG. 8 is another flowchart of the method for obtaining information in an embodiment of the application.
  • FIG. 9 is a schematic diagram of an embodiment of an apparatus for acquiring information in an embodiment of the application.
  • FIG. 10 is a schematic diagram of another embodiment of an apparatus for acquiring information in an embodiment of the application.
  • FIG. 11 is a schematic diagram of another embodiment of an apparatus for acquiring information in an embodiment of the application.
  • FIG. 12 is a schematic diagram of another embodiment of an apparatus for obtaining information in an embodiment of the application.
  • FIG. 13 is another flowchart of the method for obtaining information in an embodiment of this application.
  • FIG. 14 is another flowchart of the method for obtaining information in an embodiment of this application.
  • FIG. 15 is another flowchart of the method for obtaining information in an embodiment of this application.
  • FIG. 16 is another flowchart of the method for obtaining information in an embodiment of the application.
  • FIG. 17 is another flowchart of the method for obtaining information in an embodiment of the application.
  • the embodiment of the present application provides a method for obtaining information, which is used to obtain and save the information of the application instance, so that the user can directly obtain the information of the application instance from the first server without querying the second server.
  • Obtaining the information of the application instance with the third server can save signaling overhead and reduce service delay.
  • Application refers to a program running on a terminal device or a server, so that users can obtain the services provided by the application.
  • the program running on the terminal device is called the application client program
  • the program running on the server is called the application server program.
  • the application in the embodiment of this application refers to an application server program.
  • Instance An application instance, which refers to the running instance of an application server program in one server. Different instances of the same application can run on servers in different edge networks. It can be understood that an application instance is a program running in an application instance server. For ease of understanding, the aforementioned applications and application examples are introduced by taking Huawei Video as an example.
  • Application programming interface It can also be called an application programming interface, which is an agreement for the connection of different components of a software system.
  • the API specifies that software running on one end system (for example, a terminal device or server) requests the Internet infrastructure to deliver software to a specific destination running on another end system (for example, another terminal device or another server) The way of data.
  • the solution proposed in the embodiment of the present application is mainly based on the fifth generation mobile communication (the 5th generation, 5G) technology or new wireless technology, and may also be based on the subsequent evolution access standard, which is not specifically limited here.
  • 5G fifth generation mobile communication
  • 5G the 5th generation
  • FIG. 1A it is a system architecture diagram suitable for a method for obtaining information.
  • the system mainly includes: a first server 101, a second server 102, and a first device 103.
  • the second server 102 is used to determine the information of the instance of the application, and the information of the instance of the application may be generated by the second server 102, or may be obtained by the second server 102 from other servers.
  • the first server 101 is configured to obtain and save the information of the application instance from the second server 102 for use by the first device 103.
  • the first server 101 is connected to the second server 102 through the first interface 111. Therefore, the first server 101 can obtain the application instance information stored in the second server 102 from the second server 102.
  • the first server 101 is connected to the first device 103 through the second interface 112. Therefore, the first server 101 can send the information stored in the first server 101 to the first device 103, where the first server 101
  • the information of the instance of the application stored in may include the information of the instance of the application obtained from the second server 102.
  • the first device 103 may be a terminal device, a server, or another device that needs to obtain application instance information from the first server 101 through the second interface 112, and the specific name is not limited here.
  • the first device 103 when the first device 103 is a terminal device, the first device may be a terminal device that can use an application provided by an application instance server.
  • the terminal device includes a device that provides voice and/or data connectivity to the user.
  • it may include a handheld device with a wireless connection function or a processing device connected to a wireless modem.
  • the terminal device can communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • RAN radio access network
  • the terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), mobile station (mobile), remote Station (remote station), access point (access point, AP), remote terminal equipment (remote terminal), access terminal equipment (access terminal), user terminal equipment (user terminal), user agent (user agent), or user Equipment (user device), etc.
  • PCS personal communication service
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistants
  • the terminal device may be a vehicle-mounted terminal, a roadside terminal, or a wearable device.
  • the terminal device may be a restricted device, for example, a low-power terminal device, or a terminal device with limited storage capability, or a terminal device with limited computing capability, which is not specifically limited here.
  • the first device 103 when the first device 103 is a server, the first device 103 may be an edge-enabled server, and the edge-enabled server is used to provide an enabler capability or enable the application instances deployed in the edge network. Enabler service to better support the deployment of applications in MEC.
  • the aforementioned enabling capability or enabling service may come from the 3rd generation partnership project (3GPP) network, or may come from an edge enabling server.
  • 3GPP 3rd generation partnership project
  • the first device 103 in the embodiment of the present application may be a device or a chip in the device, a server, or a chip in the server in any of the foregoing scenarios, and the details are not limited herein. Whether as a device or as a chip, the first device 103 can be manufactured, sold, or used as an independent product.
  • the main process of the method for obtaining information proposed in the embodiment of the present application includes the following steps:
  • the first server receives information about the first instance of the application from the second server.
  • the second server is used to determine the information of the instance of the application, and the information of the instance of the application may be generated by the second server, or may be obtained by the second server from other servers.
  • the first server is connected to the second server through the aforementioned first interface 111.
  • the information of the application instance determined by the second server is referred to as the information of the first instance.
  • the first server can receive the information of the first instance of the application from the second server.
  • the information of the first instance includes identification information of the application and first information, and the identification information of the application is used to identify the application.
  • the first information is used to indicate the location of the first instance. Specifically, it will be described in detail in step 201a below, and the details will not be repeated here.
  • the first server receives information about the second instance of the application from the third server.
  • the server connected to the first server may also have a third server, and the third server is similar to the second server.
  • the third server is used to determine information about the instance of the application, and the information about the instance of the application may be generated by the third server, or may be obtained by the third server from other servers.
  • the information of the application instance determined by the third server is referred to as the information of the second instance.
  • the information of the second instance includes identification information of the application and second information, and the second information is used to indicate the location of the second instance.
  • the first server is a server serving the aforementioned second server and the aforementioned third server.
  • step 001 can be executed before step 002, or step 001 can be executed after step 002, or step 001 and step 002 can be executed at the same time, and the details are not limited here.
  • the first server saves the information of the first instance and the information of the second instance.
  • the first server may save the information of the first instance in the first server; when the first server obtains the information of the second instance, The second server may save the information of the second instance in the first service. Since the foregoing step 001 and the foregoing step 002 do not have a clear time sequence limitation, there is no difference between the step of storing the information of the first instance by the first server and the step of storing the information of the second instance by the first server. Clear chronological order.
  • the first server may first save the information of the first instance and then save the information of the second instance, the first server may also save the information of the second instance first and then save the information of the first instance, the The first server may also save the information of the first instance and the information of the second instance at the same time, which is not specifically limited here.
  • the aforementioned first server may be an edge network configuration server, or other servers, which is not specifically limited here.
  • the aforementioned second server or the third server is an edge-enabled server, a network management server in an edge network, an application instance server, an operation support system (OSS) network element, an application instance management network element, or an edge enablement server
  • the server manages any type of server or network element in the network elements, which is not specifically limited here. Specifically, a detailed introduction will be given later, and for details, please refer to the embodiment corresponding to FIG. 2 later.
  • the second server and the third server may be the same type of server.
  • both the second server and the third server may be edge-enabled servers; the second server and the third server may also be different Types of servers, for example, the second server is an edge-enabled server, and the third server is a network management server in the edge network, which is not specifically limited here.
  • the first server can receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server, respectively, and combine the information of the first instance of the application with The information of the second instance of the application is stored in the first server. Therefore, the problem of saving the information of the application instance in the edge network is solved, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device 103).
  • the other device can directly obtain the information of the instance of the application from the first server without querying the second server and the third server to obtain the information of the instance of the application. Information can save signaling overhead and slow down service delay.
  • the second server 102 may be used to generate information about an application instance, and may be used to obtain information about the application instance from other servers.
  • the second server 102 is an application instance server.
  • the system architecture diagram to which the method for obtaining information is adapted may be further shown in FIG. 1C.
  • an application instance server 104 is also included.
  • the application instance server 104 is used to generate information about an application instance.
  • the application instance server 104 is connected to the second server 102 through the fourth interface 114, and the application instance server 104 can transmit the information of the instance to the second server 102, or the second server 102 can obtain it through the fourth interface 114 Information about the instance in the application instance server 104.
  • the application instance server 104 is also connected to the first server 101 through the third interface 113, and the application instance server 104 can transmit the information of the instance to the first server 101, or the first server 101 can pass through the first server 101.
  • the third interface 113 obtains the information of the instance in the application instance server 104.
  • the second server 102 and the application instance server 104 in FIG. 1C are located in the first edge network (edge network).
  • the edge network may also be called an edge computing network (edge computing network), which is used to indicate application deployment problems, such as a local data center.
  • the edge network may also be an edge data network (EDN).
  • EDN edge data network
  • only an edge network is taken as an example for introduction.
  • the edge network may include some or all of the capabilities of the aforementioned edge computing network or edge data network, which is not specifically limited here.
  • each application instance server 104 can only be managed by one corresponding second server 102. It can also be understood that the pair of application instance servers 104 can only be served by one corresponding second server 102, or it can be understood that the application instance server 104 can only be served by one corresponding second server 102.
  • the service can be obtained from a corresponding second server 102.
  • the second server 102 provides services for the application instance server 104 of one or more applications.
  • the second server 102 may be an edge enabler server (EES) or other servers with one or more
  • the application instance server 104 of the application provides a functional entity of the edge-enabled service, and the specific implementation form of the second server is not limited here.
  • the first server 101 may be an edge network configuration server (edge network configuration server).
  • the edge network may also be an edge data network configuration server (edge data network configuration server), or other first servers may be provided
  • the functional entity of the function does not limit the specific implementation form of the first server here.
  • the first server 101 may also be connected to another edge network, that is, the first server may serve multiple edge networks, as specifically shown in FIG. 1D.
  • the first server 101 and the first server 101 An edge network is connected to a second edge network.
  • the application instance server connected to the second server 102 through the fourth interface 114 in the aforementioned first edge network is referred to as the first instance server 1041 of the application;
  • the application instance server to which the three servers 105 are connected is the second instance server 1042 of the application.
  • the third server 105 in the second edge network is connected to the first server 101 through the fifth interface 115, and the third server 105 is connected to the second instance server 1042 of the application through the seventh interface 117.
  • the second instance server 1042 is connected to the first server 101 through the sixth interface 116.
  • the second instance server 1042 of the application is similar to the aforementioned application instance server 104, and the third server 105 is similar to the second server 102, and details are not repeated here.
  • first server, the second server, or the third server in the embodiment of the present application may be a server or a chip in the server, which is not specifically limited here. Whether as a server or as a chip, the first server, second server, or third server can be manufactured, sold, or used as an independent product.
  • FIG. 1D only shows that the first server is connected to the second server in the first edge network, and the first server is connected to the third server in the second edge network.
  • multiple second servers may also exist in the first edge network
  • multiple third servers may also exist in the second edge network
  • the first server may also be connected to other edge networks or data networks.
  • the connection for example, the third edge network
  • the other edge network or the data network may also have other servers (for example, the fourth server), etc., which are not specifically limited here.
  • the method for obtaining information includes the following steps:
  • the second server obtains information about the first instance of the application.
  • the second server is a server serving an application instance.
  • the multiple application instances may be different instances of the same application, and the multiple application instances may also be different instances belonging to different applications.
  • the second server can obtain information about one or more instances of the application.
  • the application refers to a program running in a terminal device or a server, so that the user can interact with the terminal device through operation to obtain the service provided by the application.
  • the program running on the terminal device is called the application client program, and the program running on the server is called the application server program.
  • the application in the embodiment of this application refers to an application server program.
  • An instance of the application refers to an instance of an application server program running on one server, and different instances of an application can run on servers in different edge networks. It can be understood that an application instance is a program running in an application instance server.
  • the aforementioned applications and application examples are introduced by taking Huawei Video as an example.
  • the Huawei video server is deployed in Shenzhen (that is, the server program of Huawei Video runs on the server deployed in Shenzhen, we can call it the cloud of Huawei video application), and when the operator sets up a Beijing In the data center, the server that can provide the operating environment of Huawei Video Application Server, then Huawei Video Application can run its Huawei Video application server program on the server deployed in the Beijing data center. At this time, then this operation is deployed in
  • the application server program of Huawei Video on the Huawei Application Server in the Beijing Data Center can be referred to as an application instance of Huawei Video (referred to as "Huawei Video-Beijing Instance"), and this server is a Huawei Video Application Instance Server. Therefore, the client of Huawei Video, which is close to the data center, can connect to the Huawei Video-Beijing instance to access the content provided by Huawei Video.
  • the second server obtains the information of the first instance of the application, and the information of the first instance includes identification information of the application and first information, where the first information is used to indicate the location of the first instance of the application.
  • the identification information of the application is used to identify the application.
  • the identification information of the application may be the name of the application, or a serial number that uniquely identifies the application, or other character strings that can uniquely identify the application, which is not specifically limited here.
  • the identification information of the application can be one or more of the following: application identifier (application ID), uniform resource locator (uniform resource locator, URL), fully qualified domain name (FQDN), application name (application name).
  • the first information includes the Internet Protocol IP address of the first instance, and the IP address of the first instance may be a virtual IP address or a first edge network intranet IP address, which is not specifically limited here.
  • the first information may further include one or more of the following: access identification information of the first edge network or an IP address of the first edge network.
  • the access identification information of the first edge network is also referred to as the access identifier (data network access identifier, DNAI) of the first data network, which indicates access to one or more data networks (data networks, DN) User plane access point.
  • the IP address of the first edge network is the IP address of the edge network where the second server is located, and may be an IP address segment.
  • the first information may also include the IP address of the first edge-enabled server, and the first edge-enabled server provides edge-enabled servers for the first instance of the application. The server of the service.
  • the information of the first instance also includes identification information of the first edge-enabled server or service scope information of the first instance.
  • the first edge-enabled server is the aforementioned server that provides edge-enabled services for the first instance of the application, and the identification information of the first edge-enabled server is used to identify the first edge-enabled server, so that The other server or the first device can accurately find the first edge-enabled server.
  • the service range information of the first instance is used to indicate the range in which the first instance using the application can provide application services, and the range may be a subset of the coverage area of the first edge network.
  • the service range information of the first example may be a set of tracking area identity (TAI), or cell identification information, such as cell ID (cell ID) or cell ID list (cell ID list), It can also be latitude and longitude or administrative area information, etc., which is not specifically limited here.
  • TAI tracking area identity
  • cell ID cell ID
  • cell ID list cell ID list
  • latitude and longitude administrative area information
  • the second server may adopt different implementation manners. details as follows:
  • the second server receives the identification information of the first instance and the IP address of the first instance from the first instance server of the application, and the second server obtains the local information of the second server Other information in the first information, for example, the second server is also in the same first edge network, the local information of the second server stores the access identification information of the first edge network, the IP address of the first edge network, or One or more of the IP addresses of the second server. At this time, the second server can obtain the information of the first instance of the application.
  • the second server may directly receive the information of the first instance from the first instance server of the application.
  • the second server may use any of the foregoing implementation manners to obtain the information of the first instance, which is not specifically limited here.
  • the third server obtains information about the second instance of the application.
  • the third server is similar to the aforementioned second server, and the third server is also a server serving an application instance.
  • the third server is a server serving multiple application instances
  • the multiple application instances may be different instances of the same application, and the multiple application instances may also be different instances belonging to different applications.
  • the third server may obtain information about one or more instances of the application.
  • the instance of the application of the third server service is different from the instance of the application of the second server service (serving) described above.
  • the instance of the application of the third server service is referred to as the second instance. It should be understood that the foregoing second instance and third instance are only names for distinguishing different instances, and do not limit the name of the second server service and the name of the third server service.
  • the third server obtains the information of the second instance of the application, and the information of the second instance includes the identification information of the application and the second information.
  • the second information includes the Internet Protocol IP address of the second instance.
  • the second information may also include one or more of the following: access identification information of the second edge network or an IP address of the second edge network.
  • the second server is an edge-enabled server
  • the second information may also include the IP address of the second edge-enabled server.
  • the third server may adopt the following different implementation modes:
  • the third server receives the identification information of the second instance and the IP address of the second instance from the second instance server of the application, and the third server obtains the local information of the third server Other information in the second information, for example, the third server is also in the same first edge network, the local information of the third server stores the access identification information of the second edge network, the IP address of the second edge network, or One or more of the IP addresses of the third server. At this time, the third server can obtain the information of the second instance of the application.
  • the second instance server corresponding to the second instance stores the second information, so the third server can directly receive the information of the second instance from the second instance server of the application.
  • the information of the second instance of the application also includes one or more of the following:
  • the identification information of the second edge enabling server, or the service scope information of the second instance is not limited.
  • step 201b is similar to step 201a, and the details are not repeated here.
  • step 201a can be performed before step 201b, or step 201a can be performed after step 201b, or step 201a and step 201b can be performed at the same time, and the details are not limited here.
  • the second server sends the information of the first instance to the first server.
  • the second server may send the information of the first instance to the first server.
  • the first server may obtain the information of the first instance from the second server. Receive the information of the first instance.
  • the first server is a server serving the aforementioned second server and third server, and it can be understood that the first server can provide corresponding edge network configuration information for the second server and the third server; also It can be understood that the third server and the second server are configured with the address of the first server and can be connected to the first server.
  • the first server may obtain information about different instances of the application from the second server and the third server. In practical applications, the first server not only serves the aforementioned second server and the aforementioned third server, but the first server may also serve other servers.
  • the information of the first instance received by the first server from the second server can be carried in a message based on a request-response mechanism.
  • the first server sends a message to the second server. Sending a request message, the second server replies a response message to the first server, and the response message carries the information of the first instance.
  • the information of the first instance received by the first server from the second server may be carried in a message based on a subscription-notification mechanism.
  • the first server sends a subscription message to the second server, The subscription message is used to subscribe to the information of the application instance in the second server.
  • the second server replies to the first server one or more notification messages based on the aforementioned subscription message, and each notification message carries information about the first instance of the application. For example, every time the information of the application instance in the second server is updated, the second server will send a notification message to the first server.
  • the update involved in this embodiment may mean that the information of the instance of the application appears in the second server for the first time, for example, the second server obtains the information of the first instance of the application for the first time; It can mean that the information of the application instance in the second server has not increased or decreased but has changed.
  • the IP address of the first instance in the information of the first instance in the second server is changed from IP address A to IP address B; It can also mean that the information of the application instance is completely or partially deleted or invalidated from the second server.
  • the service range information of the first instance in the information of the first instance is identified by the tracking area TAI and the identity of the cell The information is changed to only this tracking area is identified as TAI. The details are not limited here.
  • the third server sends the information of the second instance to the first server.
  • the third server may send the information of the second instance to the first server, so the first server may receive the information from the third server Information about this second instance.
  • the information of the second instance received by the first server from the third server may be carried in a message based on a request-response mechanism, or may be carried in a message based on a subscription-notification mechanism. News. Specifically, it is similar to the foregoing step 202a, and the details are not repeated here.
  • step 202a can be performed before step 202b, or step 202a can be performed after step 202b, or step 202a and step 202b can be performed at the same time, which is not specifically limited here.
  • the first server saves the information of the first instance and the information of the second instance.
  • the first server may save the information of the first instance in the first server; when the first server obtains the information of the second instance, The second server may save the information of the second instance in the first service. Since the foregoing step 202a and the foregoing step 202b do not have a clear time sequence limitation, there is no difference between the step of storing the information of the first instance by the first server and the step of storing the information of the second instance by the first server. Clear chronological order.
  • the first server may first save the information of the first instance and then save the information of the second instance, the first server may also save the information of the second instance first and then save the information of the first instance, the The first server may also save the information of the first instance and the information of the second instance at the same time, which is not specifically limited here.
  • the first server can receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server, respectively, and combine the information of the first instance of the application with The information of the second instance of the application is stored in the first server. Therefore, the problem of saving the information of the application instance in the edge network is solved, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device).
  • the first device needs to query and obtain the information of the instance of the application, the first device can directly obtain it from the first server. Therefore, the first device does not need to traverse the second server and the third server before obtaining the information from the second server. Or from the third server. Therefore, the signaling overhead can be saved, and the service delay can be reduced.
  • the first server sends a save response to the second server.
  • step 204a is an optional step.
  • the first server may send a save response to the second server.
  • the save response is used to notify the second server that the first server has saved the information of the first instance. information.
  • the first server sends a save response to the third server.
  • step 204b is an optional step.
  • the first server may send a save response to the third server.
  • the save response is used to notify the third server that the first server has saved the information of the second instance. information.
  • step 202a can be performed before step 202b, or step 202a can be performed after step 202b, or step 202a and step 202b can be performed at the same time, which is not specifically limited here.
  • the first server sends a save response to the second server or the third server, which is beneficial for the second server and the third server to determine the storage of the information of the first instance and the information of the second instance Condition.
  • the first device sends identification information of the application and location information of the first device to the first server.
  • step 205 is an optional step.
  • the first device When the first device needs to obtain information about the instance of the application in the first server, the first device will send the identification information of the application and the first server to the first server.
  • the location information of the device so the first server receives the identification information of the application and the location information of the first device from the first device.
  • the location information of the first device may be one or more of TAI, cell ID, DNAI, administrative location information, geographic location information, or latitude and longitude information of the location where the first device is located.
  • the first server sends the IP address of the third instance to the first device.
  • step 206 is an optional step.
  • the first server may return the IP address of the instance that the first device wants to obtain to the first device.
  • the instance to be acquired by the first device is referred to as the third instance, and the third instance is referred to as the first instance or the second instance.
  • the third instance is determined by the identification information of the application, the location information of the first device, the information of the first instance of the application, and the information of the second instance of the application.
  • the first server determines that the application corresponding to the identification information of the application is the application corresponding to the first instance and the second instance.
  • the first server determines that the location information of the first device is the same as the location information of the first instance, the first server It is determined that the third instance is the first instance; or, if the first server determines that the distance between the location indicated by the location information of the first device and the location indicated by the information of the first instance is greater than the distance indicated by the location information of the first device and the location If the distance of the position indicated by the information of the second instance is small, the first server determines that the third instance is the first instance. In actual applications, the first server may also determine the third instance in other ways, and the details are not repeated here.
  • the first server will also send other information about the third instance to the first device.
  • the first server when the IP address of the third instance is the IP address of the first instance, the first server will also send the access identification information of the first edge network and the first device to the first device.
  • the first server in addition to sending the IP address of the first instance to the first device, the first server sends the access identification information of the first edge network or the first device to the first device.
  • the IP address of an edge network can enable the first device to determine the location of the first instance server corresponding to the information of the first instance.
  • the first server sending the IP address of the first edge-enabled server to the first device can enable the first device to determine the location of the first edge-enabled server in the edge network. Therefore, it is beneficial for the first device to perform other operations according to the location of the aforementioned first instance server or the location of the first edge-enabled server.
  • the first server when the IP address of the third instance is the IP address of the second instance, the first server will also send to the first device the access identification information of the second edge network, the One or more of the IP address of the second edge network or the IP address of the second edge-enabled server.
  • the first server in addition to sending the IP address of the second instance to the first device, the first server sends the access identification information of the second edge network or the first device to the first device.
  • the IP address of the second edge network can enable the first device to determine the location of the second instance server corresponding to the information of the second instance.
  • the first server sending the IP address of the second edge-enabled server to the first device can enable the first device to determine the location of the second edge-enabled server in the edge network. Therefore, it is beneficial for the first device to perform other operations according to the location of the aforementioned second instance server or the location of the second edge-enabled server.
  • the server that performs information exchange with the first server is not limited to the aforementioned second server and the aforementioned third server, and there may also be servers similar to the aforementioned second server and third server.
  • the information exchange process between the first server and the fourth server can refer to the aforementioned method flow between the first server and the second server or the third server, which is not specifically limited here.
  • this embodiment only takes the information interaction between the first server and the second server and the third server as an example for introduction, and the number of servers that exchange information with the first server is not limited. Make a limit.
  • the first server can determine the third instance from the foregoing first and second instances according to the identification information of the application sent by the first device and the location information of the first device. Therefore, when the first device needs to obtain an instance of the application, the first device does not need to look up the information of the instance of the application in the second server and the third server in turn, but can directly obtain the information from the first server. Obtaining the information of the instance of the application, therefore, the signaling procedure for the first device to obtain the information of the instance of the application can be reduced, thereby reducing the network delay caused by increased signaling.
  • the first server may also select an application instance that meets the requirements of the first device for the first device according to the requirements of the first device. Therefore, the process of obtaining the information of the application instance by the first device is optimized.
  • the aforementioned first server may be an edge network configuration server, or other servers, which is not specifically limited here.
  • the aforementioned second server or the third server is an edge-enabled server, a network management server in an edge network, an application instance server, an operation support system OSS network element, an application instance management network element, or an edge-enabled server management network element Any type of server or network element, which is not specifically limited here.
  • the application instance management network element refers to the network element or functional entity used to manage the application instance, for example, the package resource (package) of the application instance is packaged and distributed to the network element or functional entity in the operating environment of the edge network.
  • the edge-enabled server management network element refers to the management of edge-enabled servers, for example, configure storage and computing resources for edge-enabled servers, configure edge network information in edge-enabled servers, and provide edge-enabled server configuration needs An example of an application of edge-enabled services.
  • the second server and the third server may be the same type of server.
  • both the second server and the third server may be edge-enabled servers; the second server and the third server may also be different Types of servers, for example, the second server is an edge-enabled server, and the third server is a network management server in the edge network, which is not specifically limited here.
  • step 201a is executed, and step 202a and subsequent steps can be executed directly.
  • the third server is the second instance server of the application, the third server (ie, the second instance server of the application) will not execute the foregoing step 201b, and may directly execute step 202b and subsequent steps.
  • the second server or the third server is a network management server or an operation support system network element in the edge network
  • the network management server or the operation support system network element since the network management server or the operation support system network element has been configured with information about the instance of the application, Therefore, the second server will not execute the aforementioned step 201a, and can directly execute step 202a and subsequent steps.
  • the third server will not execute the aforementioned step 201b, and may directly execute step 202b and subsequent steps.
  • the multi-access edge computing network architecture mainly includes: an edge network configuration server 301, an edge enable server 302, an application instance server 303, and a user equipment 304.
  • the edge enabling server 302 can provide some enabling capabilities for application instances, and can better support the deployment of the application in the MEC.
  • the edge-enabled server 302 is connected to the application instance server 303 through the reference point 3 (edge-3), so the edge-enabled server 302 can obtain the information of the application instance in the application instance server 303 through the reference point 3.
  • the reference point 3 may be the fourth interface 114 in FIG. 1C or FIG. 1D, or the seventh interface 117 in FIG. 1D.
  • the edge network configuration server 301 is used to obtain information about an application instance for the user equipment 304 to use.
  • the edge network configuration server 301 is connected to the edge enable server 302 through reference point 5 (edge-5), so the edge network configuration server 301 can obtain the information of the application instance in the edge enable server 302.
  • the reference point 5 may be the first interface 111 in the foregoing FIG. 1A, FIG. 1C or FIG. 1D, or may be the fifth interface 115 in the foregoing FIG. 1D.
  • the edge network configuration server 301 is connected to the application instance server 303 through the reference point 6 (edge-6). Therefore, the edge network configuration server 301 can obtain the information of the application instance in the application instance server 303.
  • the reference Point 6 may be the third interface 113 in FIG. 1C or FIG. 1D, or the sixth interface 116 in FIG. 1D.
  • the edge network configuration server 301 is connected to the user equipment 304 through reference point 4 (edge-4), so the edge network configuration server 301 can send the information of the application instance to the user equipment 304.
  • the reference Point 4 may be the second interface 112 in the aforementioned FIG. 1A, FIG. 1C or FIG. 1D.
  • the edge network EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center, which can be identified by the edge network access identifier DNAI.
  • Multiple local edge networks can be deployed in the edge network.
  • the application instance server 303 is used to serve a certain instance or several instances of the application.
  • the application server corresponding to the application instance server 303 may also be called an edge application server, a mobile edge computing application (MEC application) or a multi-access edge computing application (MEC) application) server.
  • MEC application mobile edge computing application
  • MEC multi-access edge computing application
  • the user equipment 304 may be a mobile device such as a mobile phone or a computer, and an application client (application client) and an edge enabler client (EEC) may be installed on the user equipment 304.
  • the application client is the peer entity of the edge application on the user side.
  • the edge-enabled client EEC is the peer entity of the edge-enabled server EES on the user side.
  • the application client in the user equipment UE 304 and the application instance server 303 in the edge network can perform application data traffic, and the edge-enabled client EEC and the edge-enabled server 302 can pass through a reference point 1 (edge-1) establishes a connection, and the edge-enabled server 302 is also connected to the 3GPP network through reference point 2 (edge-2).
  • edge-1 establishes a connection
  • edge-enabled server 302 is also connected to the 3GPP network through reference point 2 (edge-2).
  • FIG. 3B exemplarily shows a schematic diagram of a 5G network architecture applicable to embodiments of the present application.
  • the terminal device 311 can communicate with the core network via the access network (AN) 312, and the terminal device can refer to 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.
  • UE user equipment
  • the access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in the future 5G network, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • FIG. 3B only illustrates one terminal device. In an actual network, there may be multiple terminal devices coexisting, which will not be repeated here.
  • AN may also be referred to as a radio access network (radio access network, RAN), which is collectively referred to as AN below, and is mainly responsible for providing a wireless connection for the terminal device 311, ensuring reliable transmission of uplink and downlink data of the terminal device 311, and so on.
  • the access network entity AN 312 may be a gNB (generation Node B) in a 5G system, or an evolved base station (evolutional node B, eNB or eNodeB) in a long term evolution (LTE) system, etc.
  • the session management function (SMF) 313 is mainly responsible for establishing and managing sessions for the terminal device 311.
  • the appropriate UPF 314 for the terminal device 311 can be selected according to the location information of the terminal device 311.
  • the user plane function (UPF) 314 is a functional network element of the user plane of the terminal device 311.
  • the main functions include packet routing and forwarding, and quality of service (QoS) processing of user plane data.
  • the 5G system can support the insertion of multiple session anchors UPF on the user plane path of a protocol data unit (PDU) session to support the connection to the local data network (DN), thereby enabling terminal equipment Can visit the application in the local DN nearby.
  • PDU protocol data unit
  • DN local data network
  • multiple UPFs may be included between the terminal device and the DN, some of which may be used as uplink classifiers (ULCL) or branching points (BP); some UPFs may be used as PDU session anchors (PDU session). anchor, PSA).
  • Access and mobility management (AMF)315, the main functions include the termination point of the control plane of the wireless access network, the termination point of non-access signaling, mobility management, lawful monitoring, access authorization or Authentication, etc.
  • the policy control function (policy cntrol funtion, PCF) 316 is mainly responsible for the establishment, release, and modification of user plane transmission paths.
  • Authentication server function authentication server function, AUSF 317, whose main functions include user authentication and so on.
  • UDM User data management
  • the data network (DN) 319 may refer to a network that provides services for the terminal device 311.
  • the application server (AS) 320 can provide data services for applications (applications) in the terminal device.
  • Figure 3B also shows possible implementations of the interfaces in each entity, such as the N2 interface between AN312 and AMF315, the N3 interface between AN312 and UPF314, etc., which will not be repeated here.
  • the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge enabling server.
  • the application instance server can manage one or more instances of the application. Therefore, the application instance server stores information about the instance of the application. For example, the identification information of the instance of the application and the IP address of the instance of the application. Wherein, the identification information of the instance of the application is used to identify the instance of the application.
  • the IP address of the instance of the application is used to indicate the deployment location of the instance in the network, and can be used by the application client to connect to the instance to obtain its application services. Then, the instance server of the application can send the identification information of the application instance and the IP address of the application instance to the edge-enabled server, that is, the edge-enabled server can receive the identification information of the application instance and the application instance server from the application instance server.
  • the IP address of the application instance is used to identify the instance of the application.
  • the identification information of the application instance and the IP address of the application instance received by the edge-enabled server from the application instance server may be carried in a message based on a request-response mechanism.
  • the edge enabler The server sends a request message to the application instance server, the application instance server replies a response message to the edge enable server, and the response message carries the identification information of the application instance and the IP address of the application instance .
  • it can be carried in a message based on a subscription-notification mechanism.
  • the edge-enabled server sends a subscription message to the application instance server, and the application instance server replies one or more messages to the edge-enabled server.
  • a notification message based on the aforementioned subscription message, and each notification message carries the identification information of the application instance and the IP address of the application instance.
  • the application instance server may also send information indicating the location of the application instance to the edge-enabled server.
  • information indicating the location of the application instance For example, the Internet Protocol IP address of the application instance, the access identification information of the edge network, the IP address of the edge network where the edge-enabled server is located, or the IP address of the edge-enabled server, etc., are not specifically limited here.
  • step 401 there may be one or more application instance servers in step 401, and there may also be one or more edge-enabled servers.
  • the application instance server corresponds to the edge-enabled server one-to-one, or each edge-enabled server corresponds to multiple application instance servers. There is no limit.
  • the edge network configuration server sends a first request to the edge enabling server.
  • the edge network configuration server may send a first request to the edge-enabled server.
  • the first request is used to request information about the instance of the application.
  • the edge network configuration server is generally a server serving an edge-enabled server in the edge network, and the edge-enabled server may be one or more, which is not specifically limited here.
  • the edge enabling server sends the information of the application instance to the edge network configuration server.
  • the edge-enabled server after the edge-enabled server receives the first request sent by the edge network configuration server, the edge-enabled server will send the application instance information to the edge network configuration server.
  • the information of the application instance includes the identification information of the application instance in step 401 and the IP address of the application instance.
  • the information of the application instance may also include the access identification information of the edge network and the IP address of the edge network. Address or IP address of the edge-enabled server.
  • the information of the instance of the application further includes identification information of the edge-enabled server, or information about the service scope of the instance of the application. Specifically, reference may be made to the related description in the foregoing step 201a, and the details are not repeated here.
  • the aforementioned information such as the access identification information of the edge network, the IP address of the edge network, and the IP address of the edge-enabled server can be obtained by the edge-enabled server from the application instance server, or can be obtained by the edge-enabled server.
  • the server obtains it from the local database of the edge-enabled server, which is not specifically limited here.
  • the information of the instance of the application may refer to the information of different instances of the same application, for example, the information of the first instance and the information of the second instance in the aforementioned embodiment corresponding to FIG. 2. In actual applications, it may also include information about other instances of the application, which is not specifically limited here.
  • the edge network configuration server saves information about the instance of the application.
  • the edge network configuration server when the edge network configuration server receives the information of the application instance sent by the edge enabling server, the edge network configuration server will save the information of the application instance. Specifically, each time the edge network configuration server receives information about the instance of the application, the edge network configuration server will save the information about the instance of the application once. The information about the instance of the application saved each time may be different. There is no limitation here.
  • the edge network configuration server when the information about the application instance sent by the edge enabling server does not include the tracking area identifier TAI of the UE, or the information about the application instance does not include the cell ID or cell ID list, the edge network configuration server also The DNAI/EDN IP can be further analyzed to obtain the UE's tracking area identification TAI, cell ID, or cell ID list, etc., and save the UE's tracking area identification TAI, cell ID, or cell ID. Specifically, the edge network configuration server may send DNAI to the 3GPP network element to obtain information such as the tracking area identifier TAI, cell ID, or cell ID list corresponding to the DNAI.
  • the 3GPP network element may be a unified data repository (UDR) network element or a session management function (session management function, SMF) network element, which is not specifically limited here.
  • the edge network configuration server After the edge network configuration server can send DNAI to the 3GPP network element, the edge network configuration server will retrieve the tracking area identification TAI, cell ID or cell ID list and other information corresponding to the DNAI in the UDR or SMF, and configure the server to the edge network Send tracking area identification TAI, cell ID or cell ID list and other information.
  • the service area information of the first instance may be the tracking area identity (TAI) of the first device, or the identification information of the cell where the first device is located, such as cell ID (cell ID) or cell list (cell ID). list), which can also be other information used to identify the location of the service user of the first instance, which is not specifically limited here.
  • TAI tracking area identity
  • cell ID cell ID
  • cell list cell ID
  • list can also be other information used to identify the location of the service user of the first instance, which is not specifically limited here.
  • the edge network configuration server sends a save response to the edge enabling server.
  • step 405 is an optional step.
  • the edge network configuration server may send a save response to the edge-enabled server to notify the edge-enabled server of the edge network configuration server The information of the instance of this application has been saved successfully.
  • the edge network configuration server may send a save response to the edge-enabled server every time the information of the application instance is saved.
  • the user equipment UE sends the identification information of the application and the location information of the UE to the edge network configuration server.
  • step 406 is an optional step.
  • the UE When the user equipment UE needs to obtain the information of the application instance in the edge network configuration server, the UE will send the identification information of the application and the location information of the UE to the edge network configuration server, so the edge network configuration server receives from the UE The identification information of the application and the location information of the UE.
  • the identification information of the application and the location information of the UE For the introduction of the identification information of the application and the location information of the UE, refer to the foregoing step 201a, and the details are not repeated here.
  • the edge network configuration server sends the IP address of the third instance to the user equipment UE.
  • step 407 is an optional step.
  • the edge network configuration server may return the IP address of the instance that the UE wants to obtain to the UE.
  • the instance that the UE wants to obtain is called the third instance, which is one of multiple instances of the application.
  • the third instance may be the first instance in the embodiment corresponding to FIG. 2.
  • the third instance is determined by the identification information of the application, the location information of the UE, the information of the first instance of the application, and the information of the second instance of the application.
  • the edge network configuration server will also send other information about the third instance to the UE. Specifically, it is similar to the foregoing step 206, and details are not repeated here.
  • the method shown in FIG. 4 also includes the following steps: an edge configuration server (edge configuration server, ECS) obtains the area information of the EES and obtains the location information of the user equipment, and then the ECS obtains the area information of the EES and the user equipment The location information determines the target EES.
  • EES edge configuration server
  • the location information determines the target EES.
  • the EES is one or more EES managed by ECS.
  • the target EES is the EES that matches the location of the user equipment among the above-mentioned EES.
  • the ECS can select the target EES for the user equipment that matches its location or is closest to the user equipment by acquiring the area information of the EES and the location information of the user equipment, that is, select the EDN where the target EES is located.
  • the user equipment discovers an application instance from the EES, it can be ensured that the application instance accessed by the user equipment is the application instance that matches the location of the user equipment or is the closest to the user equipment. Thereby improving user experience and reducing transmission delay.
  • this step refer to the description of FIG. 13 and FIG. 14.
  • the edge network configuration server that manages the information of the application instance can receive the information of the application instance from the edge enabling server, and save the obtained information of the application instance in the edge network configuration server. Therefore, the storage problem of the information of the application instance in the edge network is solved.
  • the edge network configuration server since the signaling interaction between the edge network configuration server and the edge-enabled server is based on a request-response mechanism, the edge network configuration server sends a first request to the edge-enabled server when it needs to obtain information about the application instance
  • the edge-enabled server may also send the information of the application instance to the edge network configuration server based on the first request.
  • the requirement of the edge network configuration server to obtain the instance of the application can be satisfied, so as to further realize the function of the edge network configuration server to save the information of the instance of the application.
  • the method also enables the UE to obtain the information of the application instance from the edge network configuration server without obtaining the information of the application instance from multiple edge-enabled servers or other servers, thereby saving the The UE obtains the signaling overhead of the information of the instance of the application, thereby reducing the delay of accessing the application.
  • the edge network configuration server sends a subscription request to the edge enabling server.
  • the edge network configuration server may first send a subscription request to the edge enabling server, and the subscription request is used to request to subscribe to the The information of the instance of the application in the edge-enabled server, so that when the information of the instance of the application in the edge-enabled server is updated, the edge-enabled server can actively notify the edge network configuration server of the information of the instance of the application.
  • the update in this embodiment can mean that the information of the instance of the application first appears in the edge-enabled server; it can also mean that the information of the instance of the application in the edge-enabled server has not increased or decreased but has occurred.
  • Change it can also mean that all or part of the information of the application instance is deleted or invalidated from the edge-enabled server. Specifically, it is similar to the situation where the information of the application instance in the second server is updated in the foregoing, and the details are not repeated here.
  • the subscription request includes a subscription condition
  • the subscription condition is used to indicate an instance of the application.
  • the instance of the application may be a certain instance of the application or several instances of the application.
  • the application examples may be the first example and the second example in the embodiment corresponding to FIG. 2.
  • the application example may also include other examples besides the first example and the second example, and the specific examples are not limited here.
  • the edge network configuration server can subscribe information of multiple different instances to multiple edge-enabled servers.
  • the edge enabling server sends a subscription response in response to the subscription request to the edge network configuration server.
  • step 502 is an optional step, and the subscription response is used to notify the edge network configuration server whether the subscription is successful.
  • the edge network configuration server successfully subscribes the information of the application instance in the edge enable server
  • the edge enable server will notify the edge network configuration server by sending a notification message to the edge network configuration server. It should be understood that since there may be multiple edge-enabled servers, step 502 may be performed multiple times, that is, different edge-enabled servers send subscription responses to the edge network configuration server.
  • the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge enabling server.
  • the application instance server is multiple and the edge-enabled server is multiple, the application instance server corresponds to the edge-enabled server one-to-one, or each edge-enabled server corresponds to multiple application instance servers. There is no limit.
  • step 503 can be performed before step 501 and step 502; or, step 503 can be performed before step 501 and after step 502; or step 503 can be performed after step 501 and step 502; or, step 503 and step 501 Execute at the same time; or, step 503 and step 502 are executed at the same time.
  • the details are not limited here.
  • step 503 is similar to the aforementioned step 401, and the details will not be repeated here.
  • the edge enabling server sends the information of the application instance to the edge network configuration server.
  • the edge-enabled server after the edge-enabled server receives the identification information of the application instance and the IP address of the application instance sent by the application instance server, the edge-enabled server will send the instance of the application to the edge network configuration server.
  • the information of the instance of the application includes the identification information of the instance of the application in step 503 and the IP address of the instance of the application, and the information of the instance of the application also includes the access identification information of the edge network or the IP of the edge network. Address or IP address of the edge-enabled server.
  • the information of the instance of the application further includes identification information of the edge-enabled server, or information about the service scope of the instance of the application. Specifically, reference may be made to the related description in the foregoing step 201a, and the details are not repeated here.
  • the aforementioned information such as the access identification information of the edge network, the IP address of the edge network, and the IP address of the edge-enabled server can be obtained by the edge-enabled server from the application instance server, or can be obtained by the edge-enabled server.
  • the server obtains it from the local database of the edge-enabled server, which is not specifically limited here.
  • the information of the instance of the application may refer to the information of different instances of the same application, for example, the information of the first instance and the information of the second instance in the aforementioned embodiment corresponding to FIG. 2. In actual applications, it may also include information about other instances of the application, which is not specifically limited here.
  • the edge network configuration server saves information about the instance of the application.
  • the edge network configuration server sends a save response to the edge enabling server.
  • the user equipment UE sends the identification information of the application and the location information of the user equipment UE to the edge network configuration server.
  • the edge network configuration server sends the IP address of the third instance to the user equipment UE.
  • step 505 to step 508 are similar to the aforementioned step 404 to step 407, and the details will not be repeated here.
  • the edge network configuration server that manages the information of the application instance can receive the information of the application instance from the edge enabling server, and save the obtained information of the application instance in the edge network configuration server. Therefore, the storage problem of the information of the application instance in the edge network is solved.
  • the signaling interaction between the edge network configuration server and the edge-enabled server is based on the subscription-notification mechanism, when the edge network configuration server subscribes to the edge-enabled server for a certain instance of the application or a certain number of the application In the case of an instance, the edge enabling server can send the information of the instance of the application to the edge network configuration server when the information of the instance of the application is updated.
  • the requirement of the edge network configuration server to obtain the instance of the application can be satisfied, so as to further realize the function of the edge network configuration server to save the information of the instance of the application.
  • the method also enables the UE to obtain the information of the application instance from the edge network configuration server without obtaining the information of the application instance from multiple edge-enabled servers or other servers, thereby saving the UE from obtaining information.
  • the signaling overhead of the information of the application instance thereby reducing the delay of accessing the application.
  • the method for obtaining information proposed in the embodiments of the present application can not only be applied to the system shown in FIG. 3A, but also can be combined with the common API framework (common application programming interface framework, common API framework, CAPIF), by reusing the API common framework Part of the signaling process in the, in order to save the signaling construction between the edge network configuration server and the edge enable server.
  • common API framework common application programming interface framework, common API framework, CAPIF
  • the general architecture of the API includes:
  • API common architecture core function (CAPIF core function, CCF) 601, API management function (application programming interface management function, API management function, AMF) 602, API publishing function (application programming interface publishing function, API publishing function, APF) 603, API open function (application programming interface exposing function, API exposing function, AEF) 604 and API calling entity (application programming interface invoker, API invoker) 6051/6052.
  • API management function application programming interface management function, API management function, AMF
  • API publishing function application programming interface publishing function, API publishing function, APF
  • API open function application programming interface exposing function, API exposing function, AEF
  • API calling entity application programming interface invoker, API invoker
  • API common architecture core function CCF 601, API management function AMF 602, API publishing function APF 603, API open function AEF 604, and API calling entity 6051 are located in the public land mobile network trust domain (PLMN trust domain) )middle.
  • the API calling entity 6052 is located outside the trust domain of the public land mobile network.
  • API common architecture core function CCF 601 is connected to API open function AEF 604 through connection point 3 (CAPIF-3), API common architecture core function CCF 601 is connected to API publishing function APF 603 through connection point 4 (CAPIF-4), API common architecture core function CCF 601 is connected to API management function AMF 602 through connection point 5 (CAPIF-5).
  • the aforementioned API opening function AEF 604, API publishing function APF 603, and API opening function AMF 602 all belong to the same API provider domain.
  • the core function CCF 601 of the API common architecture is connected to the API calling entity 6051 through the connection point 1 (CAPIF-1), and the API calling entity 6051 is connected to the service APIs in the API service domain through the connection point 2 (CAPIF-2).
  • the core function of the API common architecture CCF 601 is connected to the API calling entity 6052 through the connection point 1e (CAPIF-1e), and the API calling entity 6052 is connected through the connection point 2e( CAPIF-2e) Call service APIs in the API service domain.
  • each module in FIG. 6A is as follows:
  • API call entity 6051/6052 also known as API caller, it refers to a third-party application that has signed a service agreement with a public land mobile network (PLMN) operator.
  • PLMN public land mobile network
  • end-to-end (machine to machine, M2M) applications, internet of things (IoT) applications, vehicle to everything (V2X) applications, etc. which are not specifically limited here. It should be understood that the aforementioned application can be run in a terminal device or a network device.
  • the API calling entity 6051/6052 can also be equipment in the PLMN network, for example, mobility management entity (MME), radio access network (RAN) equipment, policies and Charging rules function (policy and charging rules function, PCRF) network element, etc.; it can also be the access and mobility management function (AMF) network element and session management function (session management function) in the 5G communication system function, SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, application function (AF) network element, etc.
  • MME mobility management entity
  • RAN radio access network
  • PCRF Policy and Charging rules function
  • PCRF policy and charging rules function
  • AMF access and mobility management function
  • SMF user plane function
  • PCF policy control function
  • AF application function
  • the API call entity 6051/6052 can support the authentication of the API call entity; it can support mutual authentication with the core function CCF 601 of the API common architecture; it can access the authorization obtained by the API; it can discover the APIs; it can call the API
  • API calling entity can be authenticated based on the identity of the API calling entity and other information; it can publish, store and support API discovery; it can be responsible for API access control based on the PLMN operator's strategy; it can store API calls And provide the authorized entity for review; it can support API Invoker registration; it can also store configuration policies.
  • API management function AMF 602 used to provide API management. Specifically, it can audit the API call log provided by the API common architecture core function CCF 601; it can monitor the events reported by the API common architecture core function CCF 601; it can configure the API provider's policy to the API; it can detect the status of the API; You can register API call entities.
  • API publishing function APF 603 used to provide API publishing functions so that API calling entities can discover the API.
  • API open function AEF 604 It is used to provide APIs and the entrance of API calling entity 6051/6052 to call API. Specifically, the API calling entity 6051/6052 can be authenticated based on the identity of the API calling entity 6051/6052 and other information provided by the API common architecture core function CCF 601; the authorization provided by the API common architecture core function CCF 601 can be confirmed; the API log can be Synchronize to CCF 601, the core function of API common architecture.
  • FIG. 6A can be further extended to enable the intercommunication between different API common architecture core functions CCF.
  • the aforementioned system architecture of FIG. 6A can be extended to FIG. 6B.
  • the core functions of the two API common architecture CCFs are located in different trust domains, the aforementioned system architecture of FIG. 6A can be extended to FIG. 6C.
  • FIG. 6B and FIG. 6C refer to the introduction corresponding to FIG. 6A above, and details are not repeated here.
  • API common architecture core function CCF1 and API common architecture core function CCF2 in Figure 6B can interact through connection point 6 (CAPIF-6), and the API common architecture core function CCF1 in Figure 6C It can also interact with CCF2, the core function of the API common architecture, through the connection point 6e (CAPIF-6e).
  • the connection point 6 or connection point 6e can support one API common architecture core function CCF to publish a service API or discovery service API to another API common architecture core function CCF.
  • the edge network In the following, in conjunction with the general API architecture shown in FIG. 6A and the extended architecture shown in FIG. 6B or FIG. 6C, when part of the process in the information acquisition method reuses the CAPIF discovery mechanism, as shown in FIG. 7, the edge network
  • the configuration server and edge-enabled server will perform the following steps:
  • the edge network configuration server can implement the functions of the API common architecture core function 1 in Figure 6B or Figure 6C, and the edge enable server can implement the functions in Figure 6B or Figure 6C.
  • API common architecture core function 2 the application instance server can realize the function of one or more functional modules in the API service domain (that is, the API provider domain) in FIG. 6B or FIG. 6C, for example, the application instance server implements API publishing function.
  • the interface between the edge-enabled server and the edge network configuration server includes part or all of the interface functions of the connection point 6 or the connection point 6e.
  • the reference point 5 in FIG. 3A may include the connection point 6 or the connection point 6e.
  • the first interface 111 in FIG. 1A or FIG. 1C or FIG. 1D may include part or all of the interface functions of the connection point 6 or the connection point 6e.
  • the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge enabling server.
  • the application instance server can implement the function of one or more functional modules in the API service domain 2 in FIG. 6B or FIG. 6C
  • the application instance server can enable the server to the edge through different interfaces.
  • the identification information of the instance of the application and the IP address of the instance of the application are sent.
  • the application instance server implements the API publishing function
  • the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge-enabled server through the connection point 4.
  • the interface between the edge-enabled server and the application instance server includes part or all of the interface functions of the connection point 4.
  • the third interface 3A may include part or all of the interface functions of the connection point 4; for example, The fourth interface 114 in FIG. 1C or FIG. 1D may include part or all of the interface functions of the connection point 4; for example, the seventh interface 117 in FIG. 1D may include part or all of the interface functions of the connection point 4.
  • the application instance server when the application instance server implements the API opening function, the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge-enabled server through the connection point 3; when the application instance server implements API management When functioning, the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge-enabled server through the connection point 5, which is not specifically limited here.
  • the edge network configuration server sends a first API discovery request to the edge enabling server.
  • the edge network configuration server sends a first API discovery request (service API discovery request) to the edge enabling server through the connection point 6 or the connection point 6e, and the first API discovery request is used to request the discovery of an application instance or API .
  • the first API discovery request includes discovery type information, and the discovery type information is used to indicate that the first API discovery request is used to request an instance of the application, or the discovery type information is used to indicate that the first API discovery
  • the request is used to request the instance and API of the application.
  • the instance of the application may be an instance of the application or multiple instances of the application. For example, the instance of the application may be the first in the embodiment corresponding to FIG. 2. Examples and second examples.
  • the edge-enabled server can determine the type that the edge network configuration server needs to discover through the discovery type information carried in the edge-enabled server .
  • the discovery type information may be represented by Arabic numerals or character strings. For example, when the discovery type information is "0", it means that the first API discovery request is used to request discovery of an API; when the discovery type information is "1”, it means that the first API discovery request is used to request discovery of an application instance ; When the discovery type information is "2", it means that the first API discovery request is used to request discovery of application instances and APIs. The details are not limited here.
  • the edge enabling server sends a first API discovery response to the edge network configuration server, where the first API discovery response carries information about the instance of the application.
  • the edge network configuration server after the edge network configuration server receives the first API discovery request sent by the edge-enabled server, the edge network configuration server will send the first API discovery request to the edge-enabled server through connection point 6 or connection point 6e.
  • API discovery response service API discovery response
  • the edge network The configuration server will send a first API discovery response to the edge-enabled server, and the first API discovery response carries information about the instance of the application.
  • the information of the instance of the application may include the identification information of the instance of the application in step 701 and the IP address of the instance of the application, and the information of the instance of the application may also include the access identification information of the edge network and the IP address of the edge network. Address or IP address of the edge-enabled server.
  • the information of the instance of the application further includes identification information of the edge-enabled server, or information about the service scope of the instance of the application. Specifically, reference may be made to the related description in the foregoing step 201a, and the details are not repeated here.
  • the edge network configuration server saves the information of the instance of the application.
  • the edge network configuration server may save the application instance information carried in the first API discovery response sent by the edge enabling server. Since, at this time, the edge network configuration server can realize the function of the API common architecture core function CCF1 in FIG. 6B or FIG. 6A, therefore, the API common architecture core function CCF1 can save the information of the application instance.
  • the core function CCF1 of the API general architecture is connected with the API calling entity through the connection point 1 or the connection point 1e, and the UE can realize the function of the API calling entity. Therefore, the edge network configuration server can provide the information of the application instance to the UE for use, that is, the API common architecture core function CCF1 can provide the information of the application instance to the API calling entity for use.
  • the UE can directly configure the server from the edge network, that is, the UE can directly obtain the information of the application instance from the API common architecture core function CCF1 without traversing the edge enable server (that is, the API common architecture core function 2) Then you can get the information of the application instance. In turn, the signaling overhead for the UE to obtain the information of the application instance can be saved, thereby reducing the delay of accessing the application.
  • the edge network configuration server sends a save response to the edge enabled server.
  • step 705 is an optional step. After the edge network configuration server saves the information of the instance of the application, the edge network configuration server sends a save response to the edge-enabled server to notify the edge-enabled server that the information of the instance of the application is successfully saved.
  • the UE sends identification information of the application and location information of the UE to the edge network configuration server.
  • step 706 is an optional step.
  • the UE sends the identification information of the application and the location information of the UE to the edge network configuration server.
  • the UE may send the identification information of the application and the location information of the UE to the edge network configuration server through the connection point 1e.
  • the edge network configuration server sends the IP address of the third instance to the UE.
  • step 707 is an optional step.
  • the edge network configuration server may determine the third instance according to the identification information of the application sent by the UE, the location information of the UE, and other information of the UE, and send the IP address of the third instance to the UE.
  • the edge network configuration server will also send other information about the third instance to the UE.
  • the access identification information of the first edge network, the IP address of the edge network, or the IP address of the edge-enabled server is not specifically limited here.
  • both the edge network configuration server and the edge enable server can implement the core functions of the API common architecture, and pass the connection point 6.
  • the information of the application instance in the edge-enabled server is sent to the edge network configuration server, and the obtained information of the application instance is stored in the edge network configuration server. Therefore, it is convenient for the edge network configuration server to send the information of the application instance to the UE. Therefore, it not only solves the problem of storing the information of the application instance in the edge network, but also reuses the signaling in the CAPIF, thus saving signaling overhead .
  • the edge In the following, in conjunction with the general API architecture shown in Figure 6A or the extended architecture shown in Figure 6B or Figure 6C, when part of the process in the method for obtaining information reuses the CAPIF publish mechanism, as shown in Figure 8, the edge
  • the network configuration server and edge-enabled server will perform the following steps:
  • the edge network configuration server can implement the functions of the API common architecture core function 1 in Figure 6B or Figure 6C, and the edge enable server can implement the functions in Figure 6B or Figure 6C.
  • API general architecture core function 2 the application instance server can realize the function of one or more functional modules in the API service domain 2 in FIG. 6B or FIG. 6C, for example, the application instance server realizes the API publishing function.
  • the interface between the edge-enabled server and the edge network configuration server includes part or all of the interface functions of the connection point 6 or the connection point 6e.
  • the reference point 5 in FIG. 3A may include the connection point 6 or the connection point 6e.
  • the first interface 111 in FIG. 1A or FIG. 1C or FIG. 1D may include part or all of the interface functions of the connection point 6 or the connection point 6e.
  • the edge network configuration server sends a subscription request to the edge enabling server.
  • step 801 is an optional step.
  • the edge network configuration server may send a subscription request to the edge-enabled server, and the subscription request is used to request to subscribe to the information of the instance of the application, so that when the information of the instance of the application in the edge-enabled server is updated, the edge
  • the network configuration server may notify the edge-enabled server of the information of the instance of the application.
  • the update in this embodiment can mean that the information of the instance of the application first appears in the edge-enabled server; it can also mean that the information of the instance of the application in the edge-enabled server has not increased or decreased but has occurred. Change; it can also mean that all or part of the information of the application instance is deleted or invalidated from the edge-enabled server. Specifically, it is similar to the situation where the information of the application instance in the second server is updated in the foregoing, and the details are not repeated here.
  • the subscription request includes a subscription condition
  • the subscription condition is used to indicate an instance of the application.
  • the instance of the application may be a certain instance of the application or several instances of the application, for example, the The examples may be the first example and the second example in the aforementioned embodiment corresponding to FIG. 2.
  • the edge enabling server sends a subscription response in response to the subscription request to the edge network configuration server.
  • step 802 is an optional step. After the edge enabling server receives the subscription request sent by the edge network configuration server, the edge enabling server will send a subscription response to the edge network configuration server, and the subscription response can be used to notify the edge network configuration server of this subscription whether succeed. In another implementation manner, the edge enabling server sends a subscription response to the edge network configuration server after the subscription is successful. At this time, the subscription response is used to indicate that the edge network configuration server is notified that the subscription is successful.
  • the application instance server sends a third API publishing request to the edge enabling server, where the third API publishing request carries the identification information of the application instance and the IP address of the application instance.
  • the application instance server can implement the functions of one or more functional modules in the API service domain 2 in FIG. 6B or FIG. 6C. Therefore, the application instance server can send data to the edge-enabled server through different interfaces.
  • the identification information of the application instance and the IP address of the application instance For example, when the application instance server implements the API publishing function, the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge-enabled server through the connection point 4.
  • the interface between the edge-enabled server and the application instance server includes part or all of the interface functions of the connection point 4.
  • the reference point 3 in FIG. 3A may include part or all of the interface functions of the connection point 4; for example, The fourth interface 114 in FIG.
  • FIG. 1C or FIG. 1D may include part or all of the interface functions of the connection point 4; for example, the seventh interface 117 in FIG. 1D may include part or all of the interface functions of the connection point 4.
  • the application instance server when the application instance server implements the API opening function, the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge-enabled server through the connection point 3; when the application instance server implements API management When functioning, the application instance server sends the identification information of the application instance and the IP address of the application instance to the edge-enabled server through the connection point 5, which is not specifically limited here.
  • the application instance server implements the API publishing function as an example for introduction.
  • the application instance server sends a third API publish request (service API publish request) to the edge-enabled server through the connection point 4.
  • the third API publish request carries the identification information of the application instance and the IP address of the application instance .
  • the identification information of the application instance and the IP address of the application instance are similar to the foregoing step 701, and the details are not repeated here.
  • the third API publishing request may also carry API information, for example, the name of the API, the type of the API, the version number of the API, and the API. Communication type, API interface information (IP address and port number) and protocol information, etc.
  • the edge-enabled server sends a third API release response to the application instance server.
  • step 804 is an optional step.
  • the edge-enabled server may send a third API publication response (service API publish response) to the application instance server.
  • the third API publishing response may indicate whether the API publishing is successful.
  • the edge enabling server sends a first API publishing request to the edge network configuration server, where the first API publishing request carries information about the instance of the application.
  • the edge network configuration server can implement the functions of the API common architecture core function 1 in FIG. 6B or 6C
  • the edge enable server can implement the API common architecture core function 2 in FIG. 6B or FIG. 6C.
  • the edge-enabled server may send a first API publication request (interconnection service API publish request) to the edge network configuration server through the connection point 6, and the first API publication request is used to publish the API and/or the instance of the application.
  • the first API publishing request is used to publish the instance of the application, or the first API publishing request is used to publish the API and the instance of the application.
  • the first API publishing request When the first API publishing request is used to publish an instance of the application, the first API publishing request carries information of the application instance.
  • the first API publishing request further includes publishing type information, and the publishing type information is used to indicate an instance of the application to be published.
  • the first API publishing request When the first API publishing request is used to publish the instance of the application and the API, the first API publishing request carries the information of the instance of the application and the information of the API.
  • the first API publishing request further includes publishing type information, and the publishing type information is used to indicate the instance and API of the application to be published.
  • the information of the instance of the application may include the identification information of the instance of the application in step 803 and the IP address of the instance of the application, and the information of the instance of the application may also include the access identification information of the edge network or the edge network. IP address or IP address of the edge-enabled server.
  • the information of the instance of the application further includes identification information of the edge-enabled server, or information about the service scope of the instance of the application. Specifically, reference may be made to the related description in the foregoing step 201a, and the details are not repeated here.
  • the edge network configuration server saves the information of the instance of the application.
  • step 806 is an optional step.
  • the edge network configuration server may save the application instance information carried in the first API publishing request sent by the edge enabling server. Because, at this time, the edge network configuration server core function CCF1 and the API calling entity are connected through the connection point 1 or the connection point 1e, and the UE can realize the function of the API calling entity. Therefore, the edge network configuration server can provide the information of the application instance to the UE for use, that is, the API common architecture core function CCF1 can provide the information of the application instance to the API calling entity for use.
  • the edge network configuration server sends the first API release response to the edge enabling server.
  • step 807 is an optional step.
  • the edge network configuration server may send a first API publishing response (interconnection service API publish response) to the edge enabling server.
  • the first API release response may be used as a save response to notify the edge-enabled server that the information of the application instance is successfully saved.
  • the UE sends identification information of the application and location information of the UE to the edge network configuration server.
  • the edge network configuration server sends the IP address of the third instance to the UE.
  • step 808 to step 809 are similar to the aforementioned step 706 to step 707, and the details are not repeated here.
  • the edge network configuration server, the edge enable server, and the application instance server in the embodiment corresponding to FIG. 7 or FIG. 8 may use the following methods to reuse the functional modules in the CAPIF architecture.
  • the edge network configuration server can implement the functions of the core functions of the API general architecture in FIG. 6A, and the edge enable server can implement the functions of one or more functional modules in the API service domain in FIG. 6A.
  • the The interface between the edge-enabled server and the edge network configuration server may be connection point 3, connection point 4, or connection point 5.
  • the edge-enabled server implements the API publishing function.
  • the interface between the edge-enabled server and the edge network configuration server includes some or all of the interface functions of the connection point 4; for example, the reference point 5 in FIG. 3A may be It includes part or all of the interface functions of the connection point 4; for example, the first interface 111 in the aforementioned FIG. 1A or FIG. 1C or FIG.
  • the application instance server can implement the function of an API calling entity, and the application instance server is connected to the edge network configuration server through the connection point 1e, and the application instance server is connected to the edge enable server through the connection point 2e.
  • the application instance server can realize the function of API calling entity.
  • the application instance server can be connected to the edge network configuration server through the connection point 1e.
  • the edge network configuration server can directly obtain the information of the application instance from the application instance server.
  • the functional modules in the CAPIF architecture can be reused in the following manner.
  • the edge network configuration server can implement the functions of the core functions of the API general architecture in Figure 6A, and the application instance server can implement the functions of one or more functional modules in the API service domain in Figure 6A.
  • the application The interface between the instance server and the edge network configuration server can be connection point 3, connection point 4, or connection point 5.
  • the application instance server implements the API publishing function.
  • the interface between the application instance server and the edge network configuration server includes some or all of the interface functions of the connection point 4; for example, the reference point 5 in FIG. 3A may include the connection Part or all of the interface functions of the point 4; for example, the first interface 111 in the aforementioned FIG. 1A or FIG. 1C or FIG. 1D may include part or all of the interface functions of the connection point 4.
  • the solutions of the methods provided in the embodiments of the present application are introduced from the perspective of each server or network element itself and the interaction between each server or network element.
  • the foregoing servers or devices such as the foregoing first server, second server, third server, first device, etc., in order to implement the foregoing functions, include hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • this embodiment provides a device 90 for acquiring information, and the device 90 for acquiring information can implement corresponding functions through a software module.
  • the information acquiring device 90 may be a chip or a system on a chip in the first server.
  • the apparatus 90 for acquiring information may include a receiving module 901 and a processing module 902, wherein:
  • the receiving module 901 is configured to receive information of a first instance of an application from a second server, the information of the first instance includes identification information of the application and first information, and the first information is used to indicate the location of the first instance
  • the receiving module 901 is further configured to receive information about a second instance of the application from a third server, the information of the second instance includes identification information of the application and second information, and the second information is used to indicate the second
  • the location of the instance the first server is a server serving the second server and the third server.
  • processing module 902 is used to save the information of the first instance and the information of the second instance.
  • the apparatus 90 for obtaining information in this embodiment can receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server, respectively, and combine the information of the first instance of the application.
  • the information and the information of the second instance of the application are saved. Therefore, the problem of storing the information of the application instance in the edge network is solved, and it is convenient for the information acquiring apparatus 90 to send the information of the application instance to other devices (for example, the first device).
  • the other device can directly obtain the information of the instance of the application from the information-obtaining device 90 without querying the second server and the third server to obtain the information of the application.
  • the information of the instance can save signaling overhead and slow down service delay.
  • the receiving module 901 is also used to receive the area information of the second server from the second server or the first network element; the processing module 902 is also used to obtain the location information of the user equipment; The processing module 902 is further configured to determine the target server according to the area information of the second server and the location information of the user equipment.
  • the first network element is a NEF network element, a UDM network element, a UDR network element, a PCF network element, or an NRF network element.
  • the receiving module 901 is further configured to receive an application identifier from the EEC, and the target server serves the application instance corresponding to the application identifier.
  • the apparatus 90 for obtaining information further includes: a sending module 903, configured to send a first application program interface API discovery request to the second server and the third server, and the first API
  • the discovery request includes discovery type information, the discovery type information is used to indicate that the first API discovery request is used to request an instance of the application, or the discovery type information is used to indicate that the first API discovery request is used to request an instance of the application
  • examples of the application include the first instance and the second instance.
  • the information obtaining device 90 does not need to separately configure the request for obtaining the information of the application instance, which can save the signaling overhead between the information obtaining device 90 and other information obtaining devices (for example, the second server, the third server), and thereby It can alleviate the delay of access application caused by increased signaling.
  • the receiving module 901 is specifically configured to: receive a first API discovery response from the second server, where the first API discovery response includes the information of the first instance;
  • the server receives a second API discovery response, and the second API discovery response includes the information of the second instance.
  • the information acquisition device 90 can reuse the discovery mechanism in the API general framework CAPIF, but also proposes to carry the information of the first instance in the first API discovery response or the second API discovery response. middle.
  • the information acquiring device 90 can use existing signaling to respectively receive the information of the application instance from other information acquiring devices (for example, the second server, the third server), and the other information acquiring devices (for example, , The second server, the third server) do not need to separately configure the message that sends the information of the instance of the application. Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the receiving module 901 is specifically configured to: receive a first API publishing request from the second server, where the first API publishing request includes information about the first instance of the application, and the first API publishing request includes information about the first instance of the application.
  • An API publishing request is used to publish the API and/or the first instance;
  • a second API publishing request is received from the third server, the second API publishing request includes information of the second instance of the application, and the second API publishing The request is used to publish the API and/or the second instance.
  • the device 90 for obtaining information can reuse the publishing mechanism in the API general framework CAPIF, and it is also proposed to carry the information of the first instance in the first API publishing request, or to include the second instance The information of is carried in the second API release request. Therefore, the information acquiring device 90 can use existing signaling to respectively receive the information of the application instance from other information acquiring devices (for example, the second server, the third server), and other information acquiring devices (for example, The second server, the third server) do not need to separately configure the message that sends the information of the instance of the application. Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the receiving module 901 is further configured to receive the identification information of the application and the location information of the first device from the first device; the sending module 903 is also configured to send the first device to the first device.
  • the device sends the IP address of the third instance, which is determined by the identification information of the application, the location information of the first device, the information of the first instance of the application, and the information of the second instance of the application.
  • the example is the first example or the second example.
  • the apparatus 90 for acquiring information may determine the third instance from the foregoing first and second instances according to the identification information of the application sent by the first device and the location information of the first device.
  • the first device when the first device needs to obtain an instance of the application, the first device does not need to search for the application in other information-obtaining devices (for example, the second server, the third server) in turn
  • the information of the instance of the application can be directly obtained from the information-obtaining device 90. Therefore, the signaling process for the first device to obtain the information of the instance of the application can be reduced, and the increase in information can be slowed down.
  • the information acquiring apparatus 90 can also select an application instance for the first device that meets the requirements of the first device according to the requirements of the first device. Therefore, the process of obtaining the information of the application instance by the first device is optimized.
  • the sending module 903 is further configured to send one or more of the following to the first device: the access identification information of the first edge network, and the IP address of the first edge network. Address, or the IP address of the first edge enabling server; sending one or more of the following to the first device: the access identification information of the second edge network, the IP address of the second edge network, or the first device The IP address of the second edge enable server.
  • the information acquiring device 90 in addition to sending the IP address of the application instance to the first device, the information acquiring device 90 also sends the edge network access identifier to the first device.
  • the sending module 903 is further configured to send a subscription request to the second server and the third server, and the subscription request is used to request to subscribe to the information of the instance of the application.
  • the information acquiring device 90 may be based on a subscription-notification mechanism, that is, the information acquiring device 90 subscribes to the information of the instance of the application from the second server or the third server, then it should be the first When the information of the application instance in the second server or the third server is updated, the second server or the third server will send the information of the application instance to the information acquiring device 90.
  • the information acquiring device 90 only needs to send a message to the second server or the third server once to receive the information of the application instance from the second server or the third server. Therefore, the signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the subscription request includes a subscription condition
  • the subscription condition is used to indicate an instance of the application
  • the instance of the application includes the first instance and the second instance.
  • this embodiment provides another information acquiring apparatus 100, and the information acquiring apparatus 100 can implement corresponding functions through software modules.
  • the information acquiring apparatus 100 may be a chip or a system on a chip in the second server.
  • the apparatus 100 for acquiring information may include a sending module 1001 and a processing module 1002, where:
  • the processing module 1002 is configured to obtain information of a first instance of an application, where the information of the first instance includes identification information of the application and first information, and the first information is used to indicate the location of the first instance.
  • the sending module 1001 is configured to send information of the first instance to a first server, where the first server is a server serving the second server.
  • the apparatus 100 for acquiring information in this embodiment can send the acquired information of the first instance of the application to the first server, so that the first server can save the first instance sent by the apparatus 100 for acquiring information in time.
  • Information about the instance Therefore, it is advantageous for the first server to save the information of the application instance in the edge network, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device).
  • other devices such as the first device
  • the other device can directly obtain the information of the instance of the application from the first server without obtaining the information of the instance of the application by querying multiple information-obtaining apparatuses 100. It can save signaling overhead and slow down service delay.
  • the sending module 1001 is further configured to send the area information of the second server to the first server.
  • the apparatus 100 for acquiring information further includes:
  • the receiving module 1003 is configured to receive the identification information of the first instance and the IP address of the first instance from the server of the first instance of the application.
  • the processing module 1002 is also used to determine the first information.
  • the information acquiring device 100 directly acquires the first instance server of the application, and then the information acquiring device 100 determines the first information.
  • the information of the first instance is obtained by the apparatus 100 for obtaining information from a different server. Therefore, the information acquiring apparatus 100 can ensure the integrity of the information of the first example.
  • the apparatus 100 for acquiring information further includes: the receiving module, configured to receive the information of the first instance from the server of the first instance of the application.
  • the apparatus 100 for obtaining information may directly obtain the information of the first instance from the first instance server of the application, that is, the apparatus 100 for obtaining information may directly obtain the information from the first instance server.
  • the identification information of the first instance, the IP address of the first instance, and the first information can be simplified.
  • the receiving module is further configured to receive a first application program interface API discovery request from the first server, where the first API discovery request includes discovery type information, and the discovery type information is used for Indicate that the first API discovery request is used to request an instance of the application, or the discovery type information is used to indicate that the first API discovery request is used to request an instance and API of the application, and the instance of the application includes the first instance.
  • the device 100 for acquiring information can reuse the discovery mechanism in the API general framework CAPIF.
  • the first server may send a first API discovery request to the information acquiring device 100 to trigger the information acquiring device 100 to send the information of the first instance of the application to the first server. Therefore, the first server does not need to separately configure the request for obtaining the information of the application instance, which can save signaling overhead, thereby reducing the delay in accessing the application caused by increased signaling.
  • the sending module 1001 is specifically configured to send a first API discovery response to the first server, where the first API discovery response includes the information of the first instance.
  • the apparatus 100 for acquiring information can reuse the discovery mechanism in the API general framework CAPIF, but it is also proposed that the information of the first instance is carried in the first API discovery response. Therefore, the first server can use the existing signaling to receive the information of the application instance from the information acquiring apparatus 100, and the information acquiring apparatus 100 does not need to separately configure a message for sending the information of the application instance. Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the sending module 1001 is specifically configured to send a first API publishing request to the first server, where the first API publishing request includes information about the first instance of the application, and the first API publishing request includes information about the first instance of the application.
  • the API publishing request is used to publish the API and/or the first instance.
  • the apparatus 100 for acquiring information can reuse the publishing mechanism in the API general framework CAPIF, and it is also proposed to carry the information of the first instance in the first API publishing request. Therefore, the first server can use the existing signaling to respectively receive the information of the application instance from the information acquiring apparatus 100, and the information acquiring apparatus 100 does not need to separately configure a message for sending the information of the application instance. Therefore, signaling overhead can be saved, and the delay of access application caused by increased signaling can be slowed down.
  • the processing module 1002 is specifically configured to receive a third API publishing request from the first instance server of the application.
  • the third API publishing request includes the identification information of the first instance and the IP of the first instance. Address, the third API publishing request is used to publish the API and/or the first instance.
  • the first API publishing request and the second publishing request further include publishing type information, and the publishing type information is used to indicate the type of content to be published. Therefore, the first server can determine whether the information carried in the first API publishing request includes information about the instance of the application according to the publishing type information.
  • the receiving module 1003 is further configured to receive a subscription request from the first server, and the subscription request is used to request information about subscribing to the instance of the application.
  • the apparatus 100 for acquiring information may be based on a subscription-notification mechanism, that is, the apparatus 100 for acquiring information receives a subscription request from the first server, then when the application of the apparatus 100 for acquiring information is an example When the information of is updated, the information acquiring apparatus 100 will send the information of the instance of the application to the first server. Therefore, the first server only needs to send a message to the information acquiring device 100 once to receive information from the application instance of the information acquiring device 100.
  • the subscription request includes a subscription condition
  • the subscription condition is used to indicate an instance of the application
  • the instance of the application includes the first instance and the second instance.
  • this embodiment provides a schematic structural diagram of an apparatus 110 for obtaining information.
  • the apparatus 110 for obtaining information may be the first server in the embodiment corresponding to FIG. 2 or FIG. 13 to FIG. 15, or it may be FIG. 4 to FIG. 5 or FIG. 7 to FIG. 8 or corresponding to FIG. 13 to FIG.
  • the edge network configuration server in the embodiment may also be the chip or system on chip on the first server or edge network configuration server.
  • the information acquiring device 110 includes a processor 1101 and a memory 1102.
  • the memory 1102 is used to store programs, and the processor 1101 is used to execute the programs in the memory 1102 to implement the functions of the first server in each method embodiment of the present application.
  • the processor 1101 may be used to store information of the first instance And information about this second instance.
  • the processor 1101 may include one or more processors, and the memory 1102 may include one or more storage media (for example, one or one storage device with a large amount of storage).
  • the processor 1101 can be used to process server protocols and data, control the entire server, execute software programs, and process data of the software programs.
  • the processor 1101 can be used to support the information acquisition device 110 to execute the information described in the foregoing embodiments. action.
  • the information acquiring device 110 may include a baseband processor and a central processing unit, or integrate the functions of a baseband processor and a central processing unit.
  • the baseband processor and the central processing unit may also be independent processors, which are interconnected by technologies such as a bus.
  • the information acquiring device 110 may include multiple baseband processors to adapt to different network standards, and the information acquiring device 110 may include multiple central processors to enhance its processing capabilities.
  • the various components can be connected via various buses.
  • the aforementioned baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
  • the aforementioned central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the server protocol and data can be built in the processor, or can be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the memory 1102 is mainly used to store software programs and data.
  • the memory 1102 may exist independently and is connected to the processor 1101.
  • the memory 1102 may be integrated with the processor 1101, for example, integrated in one or more chips.
  • the memory 1102 can store program codes for executing the technical solutions of the embodiments of the present application, and is controlled by the processor 1101 to execute, and various types of computer program codes that are executed can also be regarded as drivers of the processor 1101.
  • FIG. 11 in this embodiment only shows one memory and one processor.
  • the communication device 110 may have multiple processors or multiple memories, which are not specifically described here. limited.
  • the memory 1102 may also be referred to as a storage medium or a storage device.
  • the memory 1102 may be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element, which is not limited in the embodiment of the present application.
  • the apparatus 110 for acquiring information further includes an input/output device 1103, and the input/output device 1103 can be used for the apparatus 110 for acquiring information to communicate with other devices. For example, receiving the information of the first instance of the application from the second server, where the information of the first instance includes identification information of the application and first information, and the first information is used to indicate the location of the first instance.
  • the input/output device 1103 is further configured to receive information of a second instance of the application from a third server, the information of the second instance includes identification information of the application and second information, and the second information is used to indicate the second instance of the application.
  • the location of the second instance, the first server is a server serving the second server and the third server.
  • the input/output device 1103 may include an interface for communicating with other devices.
  • the information acquiring device 110 may also include one or more power supplies 1104, and/or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • operating systems such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • the steps performed by the first server or the edge network configuration server may be Based on the structure of the information acquisition device 110 shown in FIG. 11.
  • the apparatus 110 for obtaining information in this embodiment can receive the information of the first instance of the application and the information of the second instance of the application from the second server and the third server, respectively, and combine the information of the first instance of the application The information and the information of the second instance of the application are saved. Therefore, the problem of storing the information of the application instance in the edge network is solved, and it is convenient for the information acquiring apparatus 90 to send the information of the application instance to other devices (for example, the first device).
  • this embodiment provides a schematic structural diagram of another apparatus 120 for obtaining information.
  • the apparatus 120 for obtaining information may be the second server in the embodiment corresponding to FIG. 2 above, or may be the edge enablement in the embodiment corresponding to FIG. 4 to FIG. 5 or FIG. 7 to FIG. 8 and FIG. 13 to FIG.
  • the server may also be a chip or a system on a chip on the second server or edge-enabled server.
  • the apparatus 120 for acquiring information includes a processor 1201 and a memory 1202.
  • the memory 1202 is used to store programs, and the processor 1201 is used to execute the programs in the memory 1202 to implement the function of the second server in the method embodiments of the present application.
  • the processor 1201 may be used to obtain the first instance of the application. information.
  • the processor 1201 may include one or more processors, and the memory 1202 may include one or more storage media (for example, one or more storage devices with a large amount of storage).
  • the processor 1201 and the memory 1202 are similar to the processor 1101 and the memory 1102 introduced in the embodiment corresponding to FIG. 11, and the details are not repeated here.
  • the information acquiring apparatus 120 further includes an input/output device 1203, and the input/output device 1203 can be used for the information acquiring apparatus 120 to communicate with other devices.
  • the first server sends the information of the first instance, and the first server is a server serving the second server.
  • the input/output device 1203 may include an interface for communicating with other devices.
  • the information acquiring device 120 may further include one or more power supplies 1204, and/or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • operating systems such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • the steps performed by the second server or the edge-enabled server may be Based on the structure of the apparatus 120 for acquiring information shown in FIG. 12.
  • the information acquiring apparatus 120 in this embodiment can send the acquired information of the first instance of the application to the first server, so that the first server can save the first information sent by the information acquiring apparatus 120 in time.
  • Information about the instance Therefore, it is advantageous for the first server to save the information of the application instance in the edge network, and it is convenient for the first server to send the information of the application instance to other devices (for example, the first device).
  • other devices such as the first device
  • the third server in the method embodiments corresponding to FIGS. 2, 4 to 5, 7 to 8 and FIGS. 13 to 17 has similar functions to those of the foregoing second server.
  • the steps performed by the third server may also be based on the structure of the information obtaining apparatus 120 shown in FIG. 12.
  • Figure 13 it is a flowchart of the method for obtaining information provided by this application.
  • Figure 13 can be applied to a scenario where the EES and the area information corresponding to the EES have been pre-configured in the EES.
  • the method includes the following steps:
  • the third edge enable server sends the identification information and area information of the third EES to an edge network configuration server (edge configuration server, ECS).
  • ECS edge configuration server
  • the edge network configuration server receives the identification information and area information of the third EES from the third edge enabling server.
  • the third EES may be one EES or multiple EESs.
  • the area information of the third EES indicates that each EES corresponds to the respective area information of each EES, and the respective area information of the multiple EES may be the same or different.
  • the identification information of the third EES is used to identify the third EES.
  • the identification information of the third EES may be one or more of the following: the ID of the third EES, the IP address of the third EES, the URL of the third EES, or the FQDN of the third EES.
  • the identification information of the third EES is an EES identification list, and each EES corresponds to one EES identification in the list.
  • the area information of the third EES is used to indicate the network topology area or physical area information or network topology access address that can be connected to the third EES.
  • the area information of the third EES may also be referred to as the network topology area information of the third EES.
  • the area information of the third EES may include one or more of the following: identification or IP address information of one or more UPF network elements, one or more DNAIs, and parts of a local area data network (LADN) Or all service area information, or LADN identification.
  • the third EES sends the identification information and area information of the third EES to the ECS through a request message.
  • the area information of the third EES may be sent to the ECS as the attribute information of the third EES.
  • the request message also includes the access address information of the third EES, such as the IP address or URL of the third EES.
  • the request message may be a registration request message, a registration update request message, or other EES sending signaling messages to the ECS.
  • the third EES sends the area information corresponding to the third EES to the ECS only once. That is to say, if the third EES sends multiple registration request messages, registered update request messages, or other EES signaling messages to ECS, the third EES sends the area of the third EES to ECS through one of the messages. information. For example, the third EES sends the area information of the third EES to the ECS through the first registration request message.
  • the ECS saves the identification information and area information of the third EES.
  • Step 1302 is optional.
  • the ECS when the area information of the third EES is the service area information of the LADN, the ECS requests the service area information of the LADN from the network management server, OSS network element or network element (network function, NF).
  • the ECS saves the identification information of the third EES and the service area information of the LADN.
  • the area information of the third EES is one or more DNAIs
  • the format of the identification information and area information of the third EES stored in the ECS is as shown in Table 1.
  • the third EES includes two, and their identification information is EES ID#1 and EES ID#2 respectively.
  • the area information of the third EES corresponding to EES ID#1 is DNAI#1 and DNAI#2; the area information of the third EES corresponding to EES ID#2 is DNAI#3.
  • the area information of the third EES is stored as the third EES attribute information.
  • the third EES attribute information also includes the access address of the third EES. For example, the access address of the third EES corresponding to EES ID#1 is IP#1; the access address of the third EES corresponding to EES ID#1 is IP#2.
  • the ECS sends a response message to the third EES.
  • the third EES receives the response message from the ECS.
  • Step 1303 is optional.
  • the response message may be an EES registration response message, an EES registration update response message, or a response message of other signaling sent by the EES to the ECS.
  • the third EES sends a registration/update request to the ECS.
  • the ECS receives the registration/update request from the third EES.
  • Step 1304 is optional.
  • the registration/update request also includes the application identification FQDN and the identification information of the third EES.
  • the request message is used to indicate that the application identified by the FQDN is registered on the third EES.
  • the ECS saves the relationship between the identification information, area information, and FQDN of the third EES.
  • Step 1305 is optional.
  • the third EES identifier and the area information of the third EES may be stored separately with the application identifier and the third EES identifier received in step 1304, and are associated with the third EES identifier.
  • the storage form of the third EES identification and the area information of the third EES is shown in Table 1, and the storage form of the application identification and the third EES identification is shown in Table 2.
  • the identifier of the third EES registered by the application corresponding to the application identifier FQDN#1 is EES ID#1 and EES ID#2
  • the identifier of the third EES registered by the application corresponding to the application identifier FQDN#2 is EES ID#1.
  • the third EES identifier and the area information of the third EES may also be saved together with the application identifier received in step 1304, as shown in Table 3 or Table 4, for example.
  • the third EES includes two, and their identification information is EES ID#1 and EES ID#2 respectively.
  • the area information of the third EES corresponding to EES ID#1 is DNAI#1 and DNAI#2
  • the application identifiers registered on the corresponding third EES are FQDN#1 and FQDN#2
  • the third EES corresponding to EES ID#2 The area information of the EES is DNAI#3, and the corresponding application identifier registered on the third EES is FQDN#1.
  • the area information of the third EES and the registered application identifier are stored as the third EES attribute information.
  • the third EES attribute information also includes the access address of the third EES.
  • the access address of the third EES corresponding to EES ID#1 is IP#1
  • the access address of the third EES corresponding to EES ID#2 is IP#2.
  • Table 4 there are two third EESs with application identification FQDN#1, and their identification information is EES ID#1 and EES ID#2 respectively.
  • the area information of the third EES corresponding to EES ID#1 is DNAI#1 and DNAI#2
  • the area information of the third EES corresponding to EES ID#2 is DNAI#3
  • the area information of the third EES corresponding to EES ID#2 The region information is DNAI#3.
  • the area information of the third EES corresponding to EES ID#1 is DNAI#1 and DNAI#2.
  • Table 4 also includes the access address of the third EES.
  • the access address of the third EES corresponding to EES ID#1 is IP#1
  • the access address of the third EES corresponding to EES ID#2 is IP#2.
  • the ECS sends a registration/update response message to the third EES.
  • the third EES receives the registration/update response message from the ECS.
  • Step 1306 is optional.
  • the registration response message can be used to indicate the success or failure of registration.
  • the update response message may be used to indicate the success or failure of the update.
  • the EEC sends a service configuration request to the ECS.
  • ECS receives service configuration requests from EEC.
  • Step 1307 is optional.
  • the service configuration request includes any one or more of the following: user equipment identification, EEC identification information, or application identification FQDN.
  • the user equipment identifier is the user equipment identifier where the EEC is located, and the EEC identifier is used to identify the EEC.
  • the service configuration request also includes location information of the user equipment where the EEC is located.
  • the ECS obtains the location information of the user equipment and determines the target EES.
  • the target EES is one or more EES in the third EES.
  • the location information of the user equipment may include one or more of the following: cell ID, TAI, DNAI(s), the identifier or IP address of the UPF network element of the anchor point of the user equipment, or other information that can indicate that the UE is Information about the topological location or geographic location of the network in the network.
  • the ECS may obtain the location information of the user equipment from the service configuration request in step 1307.
  • the ECS can obtain the location information of the user equipment from the network side.
  • the ECS determines the target EES according to the area information of the third EES and the location information of the user equipment.
  • the area information of the target EES matches the location information of the user equipment.
  • the ECS can determine the target EES according to the area information of the third EES and the location information of the user equipment in any of the following ways: Method 1: The ECS determines the location information of the user equipment TAI/Cell ID/DNAI(s) is A subset of the area information of the target EES; mode two, ECS determines that the location of the user equipment is located in the area of the target EES; mode three, ECS determines that the location of the user equipment is closest to the physical location of the edge or center of the EES area.
  • the ECS determines the target EES according to the area information of the third EES, the location information of the user equipment, and the application identifier.
  • the target EES can provide the application identified by the FQDN requested by the EEC. If there are multiple satisfying EESs, the ECS may determine the only one EES according to the distance between the user equipment and the EES (for example, the network topology distance or the physical distance from the user equipment location to the boundary of the network topology area corresponding to the EES) or other parameters. Alternatively, the ECS determines multiple target EESs and marks the priority of each EES.
  • the ECS sends the target EES information to the user equipment.
  • the user equipment receives the target EES information from the ECS.
  • the information of the target EES is the access information of the target EES.
  • the access information of the target EES is an IP address or URL.
  • the target EES information also includes the DNAI of the target EES.
  • the ECS sends the information of the target EES to the third EES through the service configuration response.
  • the service configuration response also includes the FQDN corresponding to the target EES.
  • ECS can determine the target EES based on the area information of the EES and the location information of the user equipment. Therefore, the ECS can select the location of the user equipment by obtaining the area information of the EES and the location information of the user equipment. Match or match the target EES closest to the user equipment, that is, select the EDN where the target EES is located.
  • the user equipment discovers an application instance from the EES, it can be ensured that the application instance accessed by the user equipment is the application instance that matches the location of the user equipment or is closest to the user equipment.
  • the ECS obtains the area information of the third EES during the interaction with one or more third EESs, without introducing additional signaling, which simplifies the system implementation. Thereby improving user experience and reducing transmission delay.
  • Figure 14 it is a flowchart of the method for obtaining information provided by this application.
  • Figure 14 can be applied to a scenario where the first network element has obtained the fourth EES and the area information corresponding to the fourth EES, and the fourth EES has been registered in the ECS.
  • the first network element may acquire the area information corresponding to the fourth EES and the fourth EES in a pre-configured manner or a manner of receiving from the fourth EES.
  • the method in FIG. 14 can refer to the description in FIG. 13. The method includes the following steps:
  • the ECS sends the identification information of the fourth EES to the first network element.
  • the first network element receives the identification information of the fourth EES from the ECS.
  • the fourth EES may be one EES or multiple EESs.
  • the description of the identification information of the fourth EES can refer to the description of the identification information of the third EES in step 1301 of FIG. 13, which will not be repeated this time.
  • the first network element may be a network exposure function (NEF) network element, a unified data management (UDM) network element, a UDR network element, a PCF network element, or a network storage function (network repository). function, NRF) network element.
  • NEF network exposure function
  • UDM unified data management
  • UDR User Data Management
  • PCF PCF
  • NRF network storage function
  • the ECS sends the identification information of the fourth EES to the first network element in the form of the identification list of the fourth EES.
  • the ECS sends the identification information of the fourth EES to the first network element through an EES information request message, and the EES information request message is used to request the area information of the fourth EES.
  • the first network element sends the area information of the fourth EES to the ECS.
  • the ECS receives the area information of the fourth EES from the first network element.
  • the ECS stores the identification information and area information of the fourth EES.
  • Step 1402 is optional.
  • step 1402 reference may be made to the description of the ECS storing the identification information and area information of the third EES in step 1302 in FIG. 13, which will not be repeated this time.
  • the first network element sends a registration/update request to the ECS.
  • the ECS receives the registration/update request from the first network element.
  • Step 1404 is optional.
  • the registration/update request also includes the application identification FQDN and identification information of the fourth EES.
  • the request message is used to indicate that the application identified by the FQDN is registered on the fourth EES.
  • the ECS saves the relationship between the identification information, area information, and FQDN of the fourth EES.
  • Step 1405 is optional.
  • step 1405 may refer to the description of the relationship between the identification information, area information, and FQDN of the fourth EES stored by the ECS in step 1305 of FIG. 13, which will not be repeated this time.
  • the ECS sends a registration/update response message to the first network element.
  • the first network element receives the registration/update response message from the ECS.
  • Step 1406 is optional.
  • the registration response message can be used to indicate the success or failure of registration.
  • the update response message may be used to indicate the success or failure of the update.
  • step 1407 is optional.
  • steps 1407-1409 reference may be made to the description of steps 1307-1309 in FIG. 13, which will not be repeated this time.
  • ECS can determine the target EES according to the area information of the EES and the location information of the user equipment, so ECS can select the matching location for the user equipment by obtaining the area information of the EES and the location information of the user equipment Or the target EES closest to the user equipment, that is, select the EDN where the target EES is located.
  • the user equipment discovers an application instance from the EES, it can be ensured that the application instance accessed by the user equipment is the application instance that matches the location of the user equipment or is closest to the user equipment.
  • the location information of multiple or even all fourth EESs can be acquired at one time, which improves the performance efficiency of the system. Thereby improving user experience and reducing transmission delay.
  • the method involves a user equipment, a first server, and a fourth server. Specifically, the method includes the following steps:
  • the first server sends the area information of the fourth server to the user equipment.
  • the user equipment receives the area information of the fourth server from the first server.
  • the first server is a server serving the fourth server.
  • the fourth server is a server related to applications required by the user equipment. For example, if the user equipment needs to obtain the service of a certain application, the fourth service is a server that can provide the application service for the user equipment, or the fourth server can select a server that provides the aforementioned application service for the user equipment. .
  • the first server is a server serving the fourth server. It can be understood that the fourth server is registered with the first server.
  • the fourth server can use the service-oriented interface provided by the first server, such as registration service, registration update service, and subscription service. Wait.
  • the aforementioned first server is an edge configuration server (edge configuration server, ECS), and the aforementioned fourth server is an edge enabler server (EES).
  • ECS edge configuration server
  • the fourth server can select a server that provides the aforementioned application service for the user equipment.
  • the aforementioned ECS can use information about applications provided by the user equipment (for example, application identification, location information of the user equipment, etc.) as a discovery filter condition, so that EES can be selected for the user equipment.
  • the EES selects a server that can provide the aforementioned application service (ie, an application instance, also called an edge application server (EAS)) based on filtering conditions such as application information provided by the user equipment.
  • an application instance also called an edge application server (EAS)
  • the area information of the aforementioned fourth server is the data network access identifier (DNAI) of the data network associated with the EES.
  • the aforementioned fourth server may be one server or multiple servers.
  • the area information of the aforementioned fourth server is a DNAI associated with an EES.
  • the area information of the foregoing fourth server includes multiple EES DNAIs.
  • the aforementioned multiple EES DNAIs may be multiple EES-related DNAI lists, that is, the region information is a list containing multiple EES DNAIs, and each DNAI is associated with a different EES.
  • the DNAI associated with the EES can be understood as the DNAI that can indicate the area served by the EES; or, the DNAI carried by the EES when the EES interacts with other servers.
  • the aforementioned first server is an edge-enabled server EES
  • the aforementioned fourth server is an application instance registered to the EES (also referred to as an edge application server EAS).
  • the fourth service is a server capable of providing the application service for the user equipment.
  • the aforementioned EES can select a server (ie, application instance) that can provide the aforementioned application service for the user equipment based on the information about the application provided by the user equipment (for example, application identification, edge-enabled client EEC identification, etc.).
  • the DNAI associated with the EAS can be understood as the DNAI that can indicate the area served by the EAS; or, the DNAI carried by the EAS when the EES interacts with other servers.
  • the area information of the aforementioned fourth server is DNAI associated with EAS. It should also be noted that the aforementioned fourth server may be one server or multiple servers.
  • the area information of the foregoing fourth server is a DNAI associated with EAS.
  • the area information of the foregoing fourth server includes multiple EAS DNAIs, for example, a list including multiple EAS DNAIs, that is, the area information is a list that includes multiple EAS DNAIs, each DNAI is associated with different EAS.
  • the first server may determine the aforementioned fourth server based on user information and/or application information.
  • the user's information may be the user's location, for example, tracking area identity (TAI), cell ID (cell ID) or cell list (cell ID list), latitude and longitude or administrative area information, etc., specifically here Not limited.
  • the information of the application may be the identification of the application, the configuration file of the application client, etc., and may also be the application requirements for EAS (such as bandwidth, storage), etc.
  • the first server may also refer to the identification information of the user in the process of determining the fourth server.
  • the identification information of the user may be a user ID, the identification of the edge-enabled client EEC in the user equipment, and the user equipment Logo, etc.
  • the user equipment obtains first area information.
  • step 1502 and the aforementioned step 1501 may not have a clear time sequence limitation. That is to say, generally, the user equipment may first receive the area information of the fourth server from the first server, and then obtain the foregoing first area information; but the user equipment may also first obtain the foregoing first area information, and then obtain the foregoing first area information from the first server.
  • a server receives the area information of the fourth server, which is not specifically limited here.
  • the first area information is used to indicate the area where the user equipment is located.
  • the first area information may be DNAI currently associated with the user equipment.
  • the DNAI currently associated with the user equipment can be understood as the DNAI corresponding to the current location of the user equipment, or the user equipment is used to indicate the DNAI of the current location when the user equipment interacts with a server (for example, EES or ECS).
  • the first area information is the DNAI associated with the session in which the user equipment accesses the fourth server, and the DNAI may be the same as or different from the DNAI corresponding to the session in which the user equipment accesses the first server.
  • the user equipment may obtain the foregoing first area information in the following manner:
  • the user equipment receives the first area information from the second network element. That is, the second network element first determines the first area information, and then the second network element sends the aforementioned first area information to the user equipment.
  • the second network element stores the corresponding relationship between the first information and the area information, or the second network element may also obtain the corresponding relationship from other systems or network elements.
  • the first information includes a cell identifier or a tracking area identifier corresponding to the first area.
  • the first information may be tracking area identity (TAI); it may also be cell identification information, such as cell ID (cell ID) or cell ID list (cell ID list); it may also be latitude and longitude or administrative area Information, etc., are not specifically limited here.
  • the first information may also include cell identifiers or tracking area identifiers of other areas (for example, the second area).
  • the aforementioned area information includes first area information, and the first area information corresponds to a certain cell identifier (for example, cell identifier A) in the first information, or the first area information corresponds to a certain tracking area identifier in the first information (For example, tracking area identifier B) corresponding, which means that when the aforementioned user equipment is located in the cell corresponding to the aforementioned cell identifier A or the aforementioned user equipment is located in the area indicated by the aforementioned tracking area identifier B, then the user equipment should be in the first area information In the first area indicated.
  • a certain cell identifier for example, cell identifier A
  • tracking area identifier B tracking area identifier B
  • the aforementioned correspondence between the first information and the area information includes the cell identity of the current location of the user equipment and/or the correspondence between the tracking area identity and the first area information, and may also include other cell identities and other information.
  • the corresponding relationship of the area information is not specifically limited here.
  • the second network element may obtain second information of the user equipment, and the second information is the cell identifier or tracking area identifier in which the user equipment is located at the current moment. Based on the aforementioned second information of the user equipment (that is, the current location of the user equipment), the second network element can find the first area information corresponding to the aforementioned second information of the user equipment from the aforementioned correspondence, and then send the information to the aforementioned user equipment Send the aforementioned first area letter. That is, the former first information includes the aforementioned second information, and the aforementioned second information may be one of a plurality of cell identities in the first information, or one of a plurality of tracking area identities in the first information. In addition, the aforementioned correspondence between the first information and the area information includes the correspondence between the second information and the first area information.
  • the correspondence between the aforementioned first information and the area information may be stored in the aforementioned second network element in the form of a correspondence table, that is, the second network element stores a correspondence table that records the aforementioned correspondence.
  • the second network element may look up the area information in the correspondence table according to the current location of the user equipment, and determine that the area information corresponding to the current location of the user equipment is the first area information. Subsequently, the second network element sends the aforementioned first area information to the aforementioned user equipment.
  • the cell identifier of the current location of the user equipment is cell_002, that is, the second information of the user equipment is the cell identifier cell_002, then it can be determined that the area information corresponding to the second information is the DNAI of area 1 according to the foregoing correspondence relationship. , It can be determined that the first area information is the DNAI of area 1.
  • the tracking area identifier of the current location of the user equipment is TAI_003, that is, the second information of the user equipment is the tracking area identifier TAI_003
  • the aforementioned second network element may be a session management function (SMF) network element or an access management function (AMF) network element.
  • SMS session management function
  • AMF access management function
  • the user equipment receives a correspondence between the first information and the area information from the second network element, and the area information in the correspondence includes the first area information. Then, the user equipment determines the first area information according to the correspondence and the second information of the user equipment. That is, the second network element does not directly determine the first area information, but sends the corresponding relationship between the first area information and the first information to the user equipment, and the user equipment determines the corresponding relationship according to the second information of the user equipment and the corresponding relationship. The first area information.
  • the user equipment may search and match the corresponding first information according to the second information of the user equipment, and then find the first area information corresponding to the first information.
  • the second network element stores the corresponding relationship between the first information and the first area information, where the first information is a cell identifier or a tracking area identifier corresponding to the first area.
  • the second network element may obtain second information of the user equipment, and the second information is the cell identifier or the tracking area identifier in which the user equipment is located.
  • the second network element may associate the first information corresponding to the user equipment with the first information.
  • the area information and its corresponding first information are sent to the terminal device.
  • the foregoing second network element may be any one of a session management function SMF network element, an access management function AMF network element, and a network capability opening function (network exposure function, NEF).
  • the second network element may also be an edge configuration server ECS or an edge enabling server EES, which is not specifically limited here.
  • the user equipment triggers the switching of the fourth server according to the area information of the fourth server and the first area information.
  • triggering the switching of the four servers can be understood as triggering the user equipment to switch the aforementioned fourth server to another server; it can also be understood as triggering the user equipment to send a request to another server (for example, ECS) server to request The server allocates or selects a new server for the user equipment.
  • ECS electronic commerce
  • the user equipment After the user equipment receives the area information of the fourth server and the first area information, the user equipment will determine whether the area information of the fourth server matches the first area information.
  • the aforementioned matching can be understood as meaning that the area indicated by the area information of the fourth server is exactly the same as the area indicated by the first area information or the first area information is a subset of the area information of the fourth server.
  • the area indicated by the first area information and the area indicated by the area information of the fourth server are the same area, for example, the area information of the fourth server is DNAI1 and the first area information is DNAI1, then the aforementioned two areas can be determined Regional matching.
  • the area indicated by the first area information is within the area indicated by the area information of the fourth server, for example, the area information of the fourth server is ⁇ DNAI1, DNAI2, DNAI3 ⁇ , and the first area information is DNAI1, then the foregoing is determined The two areas match.
  • the user equipment when the area information of the fourth server does not match the first area information, the user equipment will trigger the update of the fourth server, which can also be understood as triggering the "replacement” or “switching” of the fourth server Or “replace” or “change”, that is, replace the fourth server of the device serving the user with another server with equivalent functions, or other servers corresponding to the fourth server function will provide services for the user device.
  • the mismatch can be understood as when the first area information is different from the area information of the fourth server or when the first area information is not a subset of the area information of the fourth server.
  • the user equipment replaces the fourth server with a fifth server, and the area information of the fifth server matches the first area information.
  • the aforementioned fourth server and fifth server are servers of the same type.
  • the aforementioned fourth server is EES
  • the fifth server should also be EES.
  • the fifth server should also be EAS.
  • the foregoing fourth server is an EES server
  • the area information of the fourth server is the DNAI associated with EES
  • the foregoing first area information is the target DNAI
  • the target DNAI is used to indicate the current location of the user equipment.
  • the user equipment compares the aforementioned target DNAI with the DNAI associated with the EES. If the target DNAI does not match the DNAI associated with the EES, the user equipment will update the aforementioned EES. Specifically, the user equipment will retrieve the target EES matching the target DNAI locally, that is, the DNAI associated with the target EES matches the aforementioned target DNAI.
  • the user equipment will also send an application context migration request to the EES or the target EES to perform application context migration.
  • the aforementioned fourth server is an EAS server
  • the area information of the fourth server is the DNAI associated with EAS
  • the aforementioned first area information is the target DNAI
  • the target DNAI is used to indicate that the user equipment is currently
  • the user equipment compares the aforementioned target DNAI with the DNAI associated with EAS. If the target DNAI does not match the DNAI associated with the EAS, the user equipment will update the aforementioned EAS. Specifically, the user equipment will retrieve the target EAS matching the target DNAI locally, that is, the DNAI associated with the target EAS matches the aforementioned target DNAI.
  • the user equipment may also send a context migration request to the EAS or the target EAS to perform application data migration.
  • the user equipment will also send an application context migration request to the EES or the target EES to perform application context migration.
  • the user equipment may also request the first server (for example, the aforementioned ECS) to configure a new EES for the user equipment.
  • the user equipment sends a request message to the first server.
  • the request message is used to request the first server to update the aforementioned fourth server, or use Then, the first server is requested to allocate a new server (for example, the fifth server) to the user equipment.
  • the fifth server may be EES or EAS, which is not specifically limited here.
  • the first server may send the area information of the aforementioned fourth server to the user equipment, and then the user equipment may use the obtained first area information and the aforementioned fourth server The area information determines whether to update the fourth server.
  • the user equipment may trigger the update of the fourth server according to the comparison of the foregoing two area information.
  • the enabling layer or the application layer can obtain the DNAI information corresponding to the fourth server, without requiring the operator to provide the topology information (cell identification list or tracking list) in the network format corresponding to the fourth server, and can also be combined to obtain from the network layer And the DNAI information of the fourth server acquired by the enabling layer to determine whether the fourth server needs to be changed. In this way, the topology information of the operator's network can also be protected.
  • the UE is an implementation of the user equipment in the embodiment corresponding to FIG. 15, and the ECS is the first server in the embodiment corresponding to FIG.
  • EES is an implementation manner of the fourth server in the embodiment corresponding to FIG. 15. It can also be understood that EES is an implementation manner of the first server in the embodiment corresponding to FIG. 15, and EAS is an implementation manner of the fourth server in the embodiment corresponding to FIG. 15.
  • the UE, ECS, and EES will perform the following steps:
  • the UE sends message 1 to the ECS.
  • the ECS receives message 1 from the UE.
  • the UE may request the ECS to allocate a server for the UE. Specifically, the UE may send the UE information and application information to the ECS, so that the ECS allocates a server for the UE according to the UE information and application information.
  • the UE may send message 1 to the ECS, and the message 1 is used to request EES information from the ECS.
  • the message 1 carries user identification information.
  • the user identification can be the identification of the edge-enabled client EEC and the identification of the UE.
  • the message can also carry application information, such as the identification of the application and the configuration file of the application client. Other requirements for the application server, such as delay, bandwidth, etc.
  • the message 1 may also carry the location of the UE.
  • the location of the UE may be tracking area identity (TAI), cell ID (cell ID) or cell ID list, latitude and longitude or administrative area information, etc., which are not specifically limited here.
  • the aforementioned message 1 may also carry application information such as the identification of the application and the configuration information (application client profile) of the application client, which is not specifically limited here.
  • the above-mentioned UE location information and application information can be used when the ECS searches for the EES to match the UE's location and the EAS EES that can provide the aforementioned application services.
  • the aforementioned message 1 is a service provision request (service provision request).
  • the aforementioned information such as the location of the UE, the identity of the UE, the identity of the application, and the identity of the EEC can all be carried in the service configuration request, so that the UE can send the aforementioned information to the ECS.
  • the aforementioned message 1 is a subscription message, and the subscription message is used to subscribe to the ECS to allocate the EES service to the UE.
  • EES sends message 2 to ECS.
  • ECS receives message 2 from EES.
  • Step 1601b is an optional step.
  • Step 1061a and step 1061b are independent of each other, and there is no time sequence limitation between step 1061a and step 1061b. That is, the UE may first perform step 1061a, and then the EES may perform step 1061b; or the EES may perform step 1061b, and then the UE may perform step 1061a; there may also be cases where the UE and EES send messages to the ECS at the same time.
  • 1601 occurs in the application context relocation process caused by the user's movement.
  • the UE can send message 1 to ECS based on the need to obtain application services (that is, perform the aforementioned step 1061a).
  • EES can also send message 2 to ECS after learning that the UE needs to obtain application services, so that the ECS is Determine the target EES, and the target EES can provide information about the edge application server serving the aforementioned application on the UE.
  • message 2 may carry the identity of the UE and the location of the UE, and the message 2 is used to request EES information from the ECS.
  • the message 2 may also carry application information, for example, the identification of the application, the configuration information of the application client, and the application-related information used to filter EES can also refer to the corresponding application in the message 1 sent by EEC to ECS Information.
  • the message 2 can also carry EES area information (for example, DNAI of EES) or EAS area information (for example, DNAI of EAS), which is used by ECS to select EES that can provide services in EES DNAI or EAS DNAI .
  • the aforementioned message 2 is an EES discovery request (EES discovery request). That is to say, the aforementioned information such as the location of the UE, the identity of the UE, and the identity of the application can all be carried in the EES discovery request, so that the EES can send the aforementioned information to the ECS, which can then prompt the ECS to discover the EES required by the UE.
  • EES discovery request EES discovery request
  • the aforementioned message 1 is a subscription message, which is used for subscribing to EES, which can also be understood as subscribing to EES that can provide application services for the UE.
  • the ECS determines the first EES according to message 1 or message 2.
  • the ECS after the ECS receives any one of the foregoing message 1 and message 2, the ECS will select an appropriate EES for the UE according to the application information and the UE information carried in the foregoing message.
  • the EES selected by the ECS as the UE is called the first EES.
  • the ECS will obtain local configuration information, and determine the aforementioned target EES based on user information, application information, and local configuration information.
  • the local configuration information may include the corresponding relationship between the UE and the application. Therefore, the ECS can search for the application corresponding to the UE according to the information and the corresponding relationship of the UE, and determine whether the application is the application carried in the aforementioned message 1 or message 2. The application indicated by the message.
  • the ECS will obtain local policy information, and the local policy information is used to indicate whether the ECS is allowed to provide part or all of the EES information when the application information is not obtained by the ECS.
  • the ECS determines the partial EES or the default EES matched according to the location of the UE as the first EES.
  • the ECS can select one or more EES as the first EES for the UE according to the location or application information of the UE, and determine the information of the first EES.
  • the information of the first EES includes the DNAI associated with the first EES. .
  • the ECS After the ECS selects the first EES for the UE, the ECS needs to send the information of the first EES to the EEC or the source EES (that is, the EES in step 1601b). Generally, if the ECS is the first EES determined based on the information in message 1, the ECS will execute step 1603a; if the ECS is the first EES determined based on the information in message 2, the ECS will execute step 1603b. It can also be understood that if the ECS receives message 1 from the UE, the ECS also needs to reply to the UE with the information of the first EES after determining the first EES. For details, please refer to step 1603a. Similarly, if the ECS receives message 2 from the EES, the ECS also needs to reply to the EES the information of the first EES after determining the first EES, please refer to step 1603b for details.
  • the ECS sends the DNAI associated with the first EES to the UE.
  • the UE receives the DNAI associated with the first EES from the ECS.
  • the DNAI associated with the first EES may be carried in the response message of the aforementioned message 1.
  • the DNAI associated with the first EES is carried in the foregoing service provision response (service provision response) message.
  • service provision response service provision response
  • the request-response mechanism is adopted between the aforementioned step 1061a and step 1063a.
  • the DNAI associated with the first EES is carried in the aforementioned subscription-based notification message.
  • the message of the subscribe-notification mechanism is adopted between the aforementioned step 1061a and step 1063a.
  • the ECS may send multiple notification messages when the trigger condition of the notification message is met, and each notification message may carry the first EES.
  • the first EES carried in different notification messages may not be completely the same.
  • the DNAI associated with the first EES is the DNAI of one EES; if the first EES is multiple EES, the DNAI of the first EES is the DNAI that contains multiple EES associations List of DNAI.
  • the ECS may also carry other information about the first EES in the message for sending the DNAI associated with the first EES, which is not specifically limited here.
  • step 1608 the UE will perform step 1608.
  • the ECS sends the DNAI associated with the first EES to the EES.
  • the EES receives the DNAI associated with the first EES from the ECS.
  • Step 1603b is an optional step. After the EES has performed step 1601b and the ECS has performed step 1602, the ECS will perform step 1603b.
  • the DNAI of the first EES is carried in the aforementioned EES discovery response (EES discovery response) message.
  • EES discovery response EES discovery response
  • the request-response mechanism is adopted between the aforementioned step 1061b and step 1063b.
  • the DNAI associated with the first EES is carried in the aforementioned subscription-based notification message.
  • the message of the subscribe-notification mechanism is adopted between the aforementioned step 1061b and step 1063b.
  • the ECS may send multiple notification messages to the EES when the trigger condition of the notification message is met, and each notification message may carry the first EES.
  • the first EES carried in different notification messages may not be completely the same.
  • the ECS may also carry other information about the first EES in the message for sending the DNAI associated with the first EES, which is not specifically limited here.
  • the EES may also send the first EES information (including the DNAI associated with the first EES) obtained from the ECS to
  • the UE can also be understood as the EEC sent to the UE.
  • the UE matches the DNAI information acquired in 1607 with the information of the first EES, and further, the UE can initiate an edge application server EAS discovery process to one or more EESs in the first EES, so that the EES executes the subsequent step 1604.
  • EEC After the EEC obtains the information of the first EES, after obtaining the current DNAI from 1607, it is judged that the current DNAI matches the DNAI of the first EES, and the EEC is connected to the first EES. EEC sends a request message to EES to obtain EAS information.
  • the EEC can carry UE information in the message, and the UE information can include the user's identity, the user's location, and can also carry application information. For specific explanations of user identification and application information, please refer to the previous description.
  • the EES determines the first EAS according to the information of the UE and the information of the application.
  • the EES locally has registered EAS information, and the EES matches the EAS that satisfies the UE information and application information carried in the EEC request.
  • the EES After the EES selects the first EAS for the UE, the EES will execute step 1605.
  • the EES sends the DNAI associated with the first EAS to the UE.
  • the EES may also send other information besides the DNAI associated with EAS to the UE.
  • step 1605 may be triggered by step 1604, that is, after the EES selects the first EAS for the UE, the EES sends the DNAI associated with the first EAS to the EES. It may also be implemented by the EEC in the UE during application context migration. Specifically, the EEC in the UE may receive the first EAS information (including the DNAI associated with the first EAS) from the EES during the application context migration process.
  • the AMF determines the target DNAI according to the location of the UE.
  • the target DNAI is used to indicate the area where the UE is currently located.
  • the AMF stores the corresponding relationship between the current location of the UE and the DNAI.
  • the AMF can be based on the location of the UE (for example, the group tracking area identification TAI, cell ID (cell ID), cell ID list), The latitude and longitude or administrative area information, etc.) and the foregoing corresponding relationship determine the area where the UE is currently located, that is, the target DNAI.
  • the target DNAI determined by the AMF is the DNAI of the area where the UE is currently located.
  • the AMF sends the target DNAI to the UE.
  • the UE receives the target DNAI from the AMF.
  • step 1607 when the UE sends a message such as registration, periodic registration, mobility registration, or handover message to the AMF, the AMF sends the target DNAI to the UE in the response message of the foregoing message.
  • a message such as registration, periodic registration, mobility registration, or handover message
  • the UE may carry an indication parameter in a message such as registration, periodic registration, mobility registration, or handover message, which is used to indicate a request to obtain the target DNAI. That is, the target DNAI sent by the AMF to the UE in step 1607 is a response message based on the aforementioned registration message or handover message.
  • the request-response mechanism is adopted between the UE and the AMF.
  • the UE may also subscribe to the AMF for the target DNAI through a subscription message.
  • the AMF will determine a new DNAI (ie target DNAI) for the UE based on the changed TAI/cell ID, and Send the target DNAI to the UE.
  • step 1606 and step 1607 can also be implemented by SMF or NEF.
  • step 1606 can also be replaced by SMF or NEF determining the target DNAI according to the location of the UE.
  • Step 1607 can also be replaced by SMF or NEF sending the target DNAI to the UE.
  • the SMF can subscribe to the UE's location change from the AMF, so as to obtain the current latest location of the UE.
  • the target DNAI can be judged using the same logic as the AMF to judge the target DNAI of the UE.
  • step 1606 and step 1607 and the aforementioned step 1601a (or step 1601b) to step 1605 are independent of each other. That is, when the UE receives the target DNAI from the AMF, the UE may not necessarily receive the aforementioned DNAI from the first EES of the ECS or the DNAI from the first EAS of the EES.
  • the UE determines whether to update the first EES or the first EAS according to the DNAI associated with the target DNAI and the first EES (or the DNAI associated with the first EAS).
  • the UE will determine the DNAI associated with the first EES (or the DNAI associated with the first EAS) ) Whether it matches the target DNAI.
  • the UE compares the DNAI associated with the first EES with the target DNAI. If the target DNAI does not match the DNAI associated with the first EES, the UE will retrieve the target EES locally that matches the target DNAI, that is, the DNAI associated with the target EES matches the aforementioned target DNAI. Further, the EEC may also send an application discovery request message to the target EES for obtaining information of the target EAS.
  • the UE compares the DNAI associated with the first EAS with the target DNAI. If the target DNAI does not match the DNAI associated with the first EAS, the UE will retrieve the target EAS that matches the target DNAI locally, that is, the DNAI associated with the target EAS matches the aforementioned target DNAI. Further, the EEC may also send an application context migration request to the first EES (ie, the EES registered by the first EAS), and may also carry information of the target EAS in the request to request the first EES to perform application context migration.
  • an application context migration request ie, the EES registered by the first EAS
  • the UE will also trigger a service provisioning update process to the ECS, so that the ECS will re-allocate EES to the UE.
  • the EEC may send a request message to the first EES.
  • the request is used to migrate the application context.
  • ECS sends message 3 to SMF.
  • Step 1609 is optional.
  • the ECS after the ECS determines the first EES for the UE, the ECS will also send a message 3 to the SMF, and the message 3 is used to influence the route from the UE to the EDN.
  • the message 3 is used to instruct the SMF to determine the route from the UE to the EDN; it can also be understood that the message 3 is used to configure the SMF to determine the route from the UE to the EDN; it can also be understood that the message 3 is used for adjustment SMF determines the route from the UE to the EDN.
  • the message 3 is an AF influence message.
  • the aforementioned message 3 carries user traffic description information of the first EES and DNAI associated with the first EES. At this time, the message 3 is used to influence the route from the UE to the first EES.
  • the traffic description information of the first EES includes the data network DNN, single network slice selection assistance information (S-NSSAI), the application identifier of the first EES, and the connection between the UE and the first EES.
  • S-NSSAI single network slice selection assistance information
  • the SMF will configure a route from the UE to the aforementioned first EES for the UE, so that the UE can access the aforementioned first EES according to the aforementioned route.
  • the ECS may also select one or more EAS for the UE, which is referred to as the second EAS for ease of introduction.
  • the ECS will also send the user traffic description information of the second EAS to the SMF.
  • the message 3 is used to influence the route from the UE to the second EAS.
  • the traffic description information of the aforementioned second EAS includes the data network DNN, single network slice selection assistance information (S-NSSAI), the application identifier of the second EAS, and the connection between the UE and the second EAS.
  • S-NSSAI single network slice selection assistance information
  • the SMF will configure a route from the UE to the aforementioned second EAS for the UE, so that the UE can access the aforementioned second EAS according to the aforementioned route.
  • DNAI associated with the first EES and the DNAI associated with the second EAS may be the same DNAI or different DNAIs, which are not specifically limited here.
  • the above-mentioned ECS traffic affecting EES and traffic affecting EAS can be implemented in the same message or in different messages.
  • the ECS determines the first ESS or the first EAS for the UE, it can send the DNAI associated with the first ESS or the DNAI associated with the first EAS to the UE. Then, the UE can send the DNAI associated with the first ESS or the DNAI associated with the first EAS to the UE.
  • the DNAI associated with the first EES or the DNAI associated with the first EAS determines whether to update the first ESS or the first EAS. It is beneficial to trigger the UE to update the first EES or the first EAS in time, and reduce the probability that the UE will obtain application services due to DNAI mismatch.
  • step 1607 can also be replaced with the following steps:
  • ECS receives target DNAI from SMF
  • the ECS sends the target DNAI to the UE.
  • step 1607 can also be replaced with the following steps:
  • EES receives target DNAI from SMF
  • the EES sends the target DNAI to the UE.
  • the SMF in the foregoing steps a1, a2, b1, and b2 can be replaced with AMF or NEF.
  • the ECS or EES can also obtain the target DNAI from the AMF or NEF, and then send the target DNAI to the UE.
  • the ECS or EES can receive the target DNAI from AMF, SMF, or NEF, and then the ECS or EES sends the target DNAI to the UE.
  • the ECS or EES sends the target DNAI to the UE.
  • FIG. 17 it is a flowchart of another method for obtaining information provided by this application. As shown in Figure 17, the method includes the following steps:
  • the user equipment UE sends message 1 to the edge configuration server ECS.
  • the edge enable server EES sends message 2 to the ECS.
  • the ECS determines the first EES according to message 1 or message 2.
  • the ECS sends the DNAI of the first EES to the UE.
  • the ECS sends the DNAI of the first EES to the first EES.
  • the EES determines the first EAS according to the information of the UE and the information of the application.
  • the EES sends the DNAI of the first EAS to the UE.
  • step 1701a to step 1705 are similar to the foregoing step 1601a to step 1605.
  • step 1061a to step 1065 please refer to the foregoing step 1061a to step 1065, which will not be repeated here.
  • the SMF sends the corresponding relationship between the location of the UE and the DNAI to the UE.
  • the SMF can obtain the location of the user equipment, such as the cell identification or tracking area identification where the user equipment is located.
  • the SMF may correspond to the cell identification or tracking area of the user equipment.
  • the information of the first area associated with the tracking area identifier and the corresponding first information are sent to the UE. Specifically, please refer to the related introduction in step 1502, and the details are not described here.
  • the UE determines the target DNAI according to the location of the UE and the corresponding relationship.
  • the UE after the UE receives the corresponding relationship from the SMF, the UE will find the DNAI corresponding to the current location of the UE from the foregoing corresponding relationship based on the location of the UE, and determine the DNAI as the target DNAI.
  • the UE determines whether to update the first EES or the first EAS according to the target DNAI and the DNAI of the first EES (or the DNAI of the first EAS).
  • ECS sends message 3 to SMF.
  • step 1708 to step 1709 are similar to the foregoing step 1608 to step 1609.
  • step 1068 to step 1069 please refer to the foregoing step 1068 to step 1069, which will not be repeated here.
  • the ECS may send the DNAI of the aforementioned first ESS or the DNAI of the first EAS to the UE. Then, the UE can obtain the corresponding relationship from the SMF, and determine the target DNAI based on the corresponding relationship and the location of the UE. Then, the UE will determine whether to update the first ESS or the first EAS according to the target DNAI and the DNAI of the first EES or the DNAI of the first EAS. It is beneficial to trigger the UE to update the first EES or the first EAS in time, and reduce the probability that the UE will obtain application services due to DNAI mismatch.
  • AMF/SMF/NEF sends the corresponding relationship between DNAI and its corresponding cell/TA list to ECS.
  • the ECS will determine the DNAI corresponding to the location of the UE according to the location of the UE, that is, the target DNAI.
  • the ECS can obtain the location information of the UE, such as a report from the UE or obtain the location information of the UE from the core network. After the ECS receives the foregoing correspondence, the ECS may determine the target DNAI based on the location of the UE in the ECS and the correspondence.
  • the ECS sends the target DNAI to the UE.
  • AMF/SMF/NEF sends the correspondence between DNAI and its corresponding cell/TA list to EES.
  • the cell/TA includes the TA/cell corresponding to the location of the UE.
  • EES will determine the DNAI corresponding to the location of the UE according to the location of the UE, that is, the target DNAI.
  • the EES can obtain the location information of the UE, such as a report from the UE or obtain the location information of the UE from the core network. After the EES receives the foregoing correspondence, the EES can determine the target DNAI based on the location of the UE in the EES and the correspondence.
  • the EES sends the target DNAI to the UE.
  • EEC subscribes to the ECS the DNAI corresponding to the location of the UE.
  • ECS can subscribe to the AMF/SMF/NEF for the DNAI corresponding to the UE, and the DNAI can be related to the user plane data of EES or EAS , It can also only be related to any user plane data of the UE.
  • ECS obtains the DNAI corresponding to the location of the UE from AMF/SMF/NEF.
  • ECS can determine the DNAI corresponding to the current location of the UE according to the correspondence between the local DNAI and its corresponding cell/TA list.
  • the ECS can obtain the location of the UE, namely the cell and TA, from the EEC or core network equipment, and determine it according to the location of the UE.
  • the DNAI corresponding to the location of the UE is the target DNAI.
  • ECS obtains the DNAI corresponding to the location of the UE from AMF/SMF/NEF.
  • the ECS sends the target DNAI to the UE.
  • the EEC subscribes to the EES the DNAI corresponding to the location of the UE.
  • EES can subscribe to the AMF/SMF/NEF for the DNAI corresponding to the UE, and the DNAI can be related to the user plane data of EES or EAS , It can also only be related to any user plane data of the UE.
  • the EES obtains the DNAI corresponding to the location of the UE from AMF/SMF/NEF.
  • EES can determine the DNAI corresponding to the current location of the UE according to the correspondence between the local DNAI and its corresponding cell/TA list. EES can obtain the location of the UE, namely the cell and TA, from the EEC or core network equipment, and determine it according to the location of the UE. The DNAI corresponding to the location of the UE is the target DNAI. Or EES obtains the DNAI corresponding to the UE location from AMF/SMF/NEF.
  • the EES sends the target DNAI to the UE.
  • the ECS or EES can receive the corresponding relationship from AMF, SMF, or NEF, and then the ECS or EES determines the target DNAI based on the internally stored UE location and the received corresponding relationship, and combines the target DNAI is sent to the UE. It is beneficial for the ECS to send the aforementioned target DNAI to the UE when sending the DNAI of the first EES to the UE, and shorten the time delay for the UE to wait for the target DNAI. Similarly, it is beneficial for the EES to send the aforementioned target DNAI to the UE when sending the DNAI of the first EAS to the UE, and shorten the time delay for the UE to wait for the target DNAI. The UE can compare the DNAI of the first EES (or the DNAI of the first EAS) with the target DNAI as soon as possible, thereby shortening the time delay.
  • One or more of the above modules or units can be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor may include but is not limited to at least one of the following: a central processing unit, a microprocessor, a digital signal processing (digital signal processing, DSP), a microcontroller (microcontroller unit, MCU), or an artificial intelligence processor, etc.
  • Various types of computing devices that run software Each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the processor may be built in a system on chip (SoC) or an application specific integrated circuit (ASIC), or it may be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the processor's internal processing is used to execute software instructions for calculation or processing, and may further include necessary hardware accelerators, such as field programmable gate array (FPGA) and programmable logic circuit (programmable logic circuit). device, PLD) or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • programmable logic circuit programmable logic circuit
  • the hardware can be CPU, microcontroller, DSP, MCU, artificial intelligence processor, ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator or non-integrated discrete device
  • the hardware can run necessary software or does not rely on software to perform the above method flow.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)) )Wait.

Abstract

本申请实施例公开了一种获取信息的方法，可以应用于多接入边缘计算MCE领域，例如，MCE的车联网场景或MCE的物联网场景。本申请实施例中的方法包括：第一服务器分别从第二服务器和第三服务器接收应用的第一实例的信息和应用的第二实例的信息，然后，该第一服务器保存该第一实例的信息和该第二实例的信息，以使得该第一服务器可以集中维护该应用的不同实例的信息，进而可以使其他设备可以直接从该第一服务器获取到该应用的实例的信息。

Description

一种获取信息的方法及装置
本申请要求于2020年03月24日提交中国专利局、申请号为PCT/CN2020/080966、发明名称为“一种获取信息的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，尤其涉及一种获取信息的方法及装置。
背景技术
随着移动互联网和物联网的快速发展，为了解决终端设备计算能力有限和存储能力有限以及能耗等问题，需要将高复杂度、高能耗计算任务迁移至云计算数据中心的服务器，从而降低终端设备的能耗，延长该终端设备的待机时长。然而，将计算任务迁移至云计算数据中心的服务器的方式不仅会造成大量的数据传输而增加网络负荷，还会带来数据传输时延而影响时延敏感的业务。因此，为了有效解决移动互联网和物联网快速发展带来的高网络负荷、高带宽以及低时延等要求，提出了多接入边缘计算(multi-access edge computing，MEC)的概念。该多接入边缘计算技术可以通过在无线接入侧部署通用服务器，从而为无线接入网提供信息技术(information technology，IT)的能力和云计算的能力。
在多接入边缘计算技术的系统架构中，一个应用可以对应一个实例或多个实例。当一个应用对应多个实例时，该多个实例中的每个实例分别由一个边缘使能服务器管理。当其他设备需要获取该应用的多个实例的信息时，需要通过分别查询管理上述多个实例的多个边缘使能服务器来获取。由此，会带来大量的信令开销以及业务的时延，从而影响用户的体验。
发明内容
本申请实施例提供了一种获取信息的方法，用于获取并保存应用的实例的信息，以使得用户可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
第一方面，本申请实施例提供了一种获取信息的方法，该方法的实施主体包括第一服务器、第二服务器和第三服务器。其中，该第一服务器为服务第二服务器和第三服务器的服务器。该第一服务器可以从第二服务器接收应用的第一实例的信息，并且，第一服务器可以从第三服务器接收该应用的第二实例的信息。其中，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置；该第二实例的信息包括该应用的标识信息和第二信息，该第二信息用于指示该第二实例的位置。然后，该第一服务器将保存该第一实例的信息和该第二实例的信息。因此，解决了该应用的第一实例的信息和该应用的第二实例的信息的保存问题。
本申请实施例中，由于，管理应用的实例的信息的第一服务器可以分别从第二服务器 和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存于该第一服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该第一服务器向其他设备(例如第一设备)发送该应用的实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
根据第一方面，本申请实施例第一方面的一种实施方式中，该第一服务器从第二服务器或第一网元接收该第二服务器的区域信息；该第一服务器获取用户设备的位置信息；该第一服务器根据该第二服务器的区域信息和该用户设备的位置信息确定目标服务器。
根据第一方面，本申请实施例第一方面的又一种实施方式中，第一网元为NEF网元、UDM网元、UDR网元、PCF网元、或NRF网元。
根据第一方面，本申请实施例第一方面的又一种实施方式中，第一服务器从EEC接收应用标识，该目标服务器服务于该应用标识对应的应用实例。
根据第一方面，本申请实施例第一方面的一种实施方式中，该方法还包括：该第一服务器向该用户设备发送该目标服务器的区域信息。
根据第一方面，本申请实施例第一方面的一种实施方式中，该方法还包括：该第一服务器向该用户设备发送该目标服务器区域信息对应的小区标识或追踪区标识。
根据第一方面，本申请实施例第一方面的一种实施方式中，该方法还包括：该第一服务器向该用户设备发送该用户设备所在位置的区域信息。
根据第一方面，本申请实施例第一方面的一种实施方式中，该方法还包括：该第一服务器向第二网元发送第一消息，该第一消息用于影响该用户设备到该目标服务器的路由信息，该第一消息包括该用户设备的用户标识和应用标识，该第一消息还包括该目标服务器的用户流量描述信息和/或该目标服务器的区域信息。
根据第一方面，本申请实施例第一方面的一种实施方式中，该方法还包括：该第一服务器向第二网元发送第二消息，该第二消息用于影响该用户设备到该目标服务器对应的应用实例的路由信息，该第二消息包括该用户设备的用户标识和应用标识，该第一消息还包括该应用实例的用户流量描述信息和/或该应用实例的区域信息。
根据第一方面，本申请实施例第一方面的一种实施方式中，该第二网元包括会话管理功能SMF网元、接入管理功能AMF网元、网络能力开放功能NEF网元中的任意一项。
根据第一方面，本申请实施例第一方面的第一种实施方式中，该第一信息包括该第一实例的互联网协议IP地址和如下一项或多项：第一边缘网络的接入标识信息、该第一边缘网络的IP地址、或第一边缘使能服务器的IP地址，该第二服务器位于该第一边缘网络中；该第二信息包括该第二实例的IP地址和如下一项或多项：第二边缘网络的接入标识信息、该第二边缘网络的IP地址、或第二边缘使能服务器的IP地址，该第三服务器位于该第二边缘网络中。
本实施方式中，对第一实例的信息中的第一信息以及第二实例的信息中的第二信息进行了进一步限定。以第一信息为例，该第一信息除了包括第一实例的互联网协议IP地址以外，该第一信息还包括：第一边缘网络的接入标识信息、第一边缘网络的IP地址、或第一 边缘使能服务器的IP地址中的一项或多项。因此，可以该通过多种标识信息或IP地址等信息确定该应用的第一实例的具体位置，以使得该第一服务器在获取该应用的第一实例的信息的同时，还可以准确确定该应用的第一实例的具体位置。类似的，该第一服务器在获取应用的第二实例的信息的同时，也可以准确确定该应用的第二实例的具体位置。
根据第一方面或第一方面的第一种实施方式，本申请实施例第一方面的第二种实施方式中，该方法还包括：该第一服务器向该第二服务器发送第一应用程序接口API发现请求，该第一API发现请求包括发现类型信息，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例，或，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例和API，该应用的实例包括该第一实例和该第二实例；该第一服务器向该第三服务器发送该第一API发现请求。
本实施方式中，提出该第一服务器与该第二服务器(或第三服务器)之间的信令交互可以复用API通用架构CAPIF中的发现机制。具体地，该第一服务器可以通过向第二服务器和第三服务器发送第一API发现请求，以触发该第二服务器向该第一服务器发送应用的第一实例的信息，以及，以触发该第三服务器向该第一服务器发送应用的第二实例的信息。因此，该第一服务器不需要单独配置获取应用的实例的信息的请求，可以节省第一服务器与第二服务器以及第三服务器之间的信令开销，进而可以减缓因增加信令造成的接入应用的延迟。
根据第一方面的第二种实施方式，本申请实施例第一方面的第三种实施方式中，该第一服务器从该第二服务器接收应用的第一实例的信息，包括：该第一服务器从该第二服务器接收第一API发现响应，该第一API发现响应包括该第一实例的信息；该第一服务器从该第三服务器接收应用的第二实例的信息，包括：该第一服务器从该第三服务器接收第二API发现响应，该第二API发现响应包括该第二实例的信息。
本实施方式中，不仅提出该第一服务器与该第二服务器之间的信令交互复用API通用架构CAPIF中的发现机制，还提出将第二服务器发送给该第一服务器的第一实例的信息携带于该第一API发现响应中，类似的，将第三服务器发送给该第一服务器的第二实例的信息携带于该第二API发现响应中。因此，该第一服务器可以利用现有的信令分别从该第二服务器和该第三服务器中接收该应用的实例的信息，该第二服务器或该第三服务器不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
根据第一方面，本申请实施例第一方面的第四种实施方式中，该第一服务器从第二服务器接收应用的第一实例的信息，包括：该第一服务器从第二服务器接收第一API发布请求，该第一API发布请求包括该应用的第一实例的信息，该第一API发布请求用于发布该API和/或该第一实例；该第一服务器从第三服务器接收应用的第二实例的信息，包括：该第一服务器从第三服务器接收第二API发布请求，该第二API发布请求包括该应用的第二实例的信息，该第二API发布请求用于发布该API和/或该第二实例。
本实施方式中，提出该第一服务器与该第二服务器之间的信令交互可以复用API通用架构CAPIF中的发布机制，并且，还提出将第二服务器发送给该第一服务器的第一实例的信息携带于该第一API发布请求中，类似的，将第三服务器发送给该第一服务器的第二实 例的信息携带于该第二API发布请求中。因此，该第一服务器可以利用现有的信令分别从该第二服务器和该第三服务器中接收该应用的实例的信息，该第二服务器或该第三服务器不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
根据第一方面的第四种实施方式，本申请实施例第一方面的第五种实施方式中，该第一API发布请求还包括发布类型信息，该发布类型信息用于指示发布该应用的实例和/或发布API，该应用的实例包括该第一实例；该第二API发布请求还包括发布类型信息，该发布类型信息用于指示发布该应用的实例和/或发布API，该应用的实例包括该第二实例。
本实施方式中，提出该第一API发布请求和该第二发布请求还包括发布类型信息，该发布类型信息用于指示发布的内容的类型。因此，该第一服务器可以根据该发布类型信息确定该第一API发布请求或该第二API发布请求所携带的信息中是否包括该应用的实例的信息。
根据第一方面或第一方面的第一种实施方式，本申请实施例第一方面的第六种实施方式中，该第一服务器从第二服务器接收应用的第一实例的信息之前，或者，该第一服务器从第二服务器接收应用的第一实例的信息之前，该方法还包括：该第一服务器向该第二服务器和该第三服务器发送订阅请求，该订阅请求用于请求订阅该应用的实例的信息。
本实施方式中，提出该第一服务器与该第二服务器之间的信令交互可以基于订阅-通知机制，即该第一服务器从该第二服务器或该第三服务器订阅该应用的实例的信息，则该当该第二服务器或该第三服务器中的应用的实例的信息更新时，该第二服务器或该第三服务器将向该第一服务器发送该应用的实例的信息。因此，该第一服务器仅需向该第二服务器或该第三服务器发送一次消息，即可接收来自该第二服务器或该第三服务器的应用的实例的信息。因此，可以节省该信令开销，进而可以减缓增加信令造成的接入应用的延迟。
根据第一方面的第六种实施方式，本申请实施例第一方面的第七种实施方式中，该订阅请求包括订阅条件，该订阅条件用于指示该应用的实例，该应用的实例包括该第一实例和该第二实例。
本实施方式中，可以在该订阅请求中携带订阅条件，以指示该第一服务器请求订阅的内容为应用的实例的信息，或者，以指示该第一服务器请求订阅的应用的实例的类型。
根据第一方面、第一方面的第一种实施方式至第一方面的第七种实施方式中的任意一种实施方式，本申请实施例第一方面的第八种实施方式中，该应用的第一实例的信息还包括如下一项或多项：第一边缘使能服务器的标识信息，或者，该第一实例的服务范围信息；该应用的第二实例的信息还包括如下一项或多项：第二边缘使能服务器的标识信息，或者，该第二实例的服务范围信息。
本实施方式中，提出该应用的实例的信息还可以包括边缘使能服务器的标识信息，或者，该应用的实例的服务范围信息。其中，该边缘使能服务器的标识信息用于标识该边缘使能服务器的身份，以使得其他服务器或第一设备可以准确查找该边缘使能服务器。该应用的实例的服务范围信息用于指示使用该应用的实例的用户所在的范围，也可以指该应用的实例服务的用户可能处于的位置。因此，本实施方式扩展了应用的实例的信息的具体实现方式，以使得该应用的实例的信息可以适用于具体场景的需求。
根据第一方面、第一方面的第一种实施方式至第一方面的第八种实施方式中的任意一种实施方式，本申请实施例第一方面的第九种实施方式中，该第一服务器为边缘网络配置服务器。
本实施方式中，明确了第一服务器在边缘网络中的具体实现方式，该第一服务器可以为边缘网络中的边缘网络配置服务器。
根据第一方面、第一方面的第一种实施方式至第一方面的第九种实施方式中的任意一种实施方式，本申请实施例第一方面的第十种实施方式中，该第二服务器或该第三服务器为如下任意一项：边缘使能服务器；或者，边缘网络中的网络管理服务器；或者，应用实例服务器；或者，运营支持系统OSS网元。
本实施方式中，明确了第二服务器和第三服务器的具体实现方式，其中，该第二服务器和该第三服务器可以为前述多种服务器中相同的服务器，也可以为前述多种服务器中不同的服务器。由于该第二服务器和该第三服务器可以有多种实现方式，因此，增加了方案的多样性。
根据第一方面、第一方面的第一种实施方式至第一方面的第十种实施方式中的任意一种实施方式，本申请实施例第一方面的第十一种实施方式中，该方法还包括：该第一服务器从第一设备接收该应用的标识信息和该第一设备的位置信息；该第一服务器向该第一设备发送第三实例的IP地址，该第三实例由该应用的标识信息、该第一设备的位置信息、该应用的第一实例的信息和该应用的第二实例的信息确定，所述第三实例为该第一实例或该第二实例。
本实施方式中，提出该第一服务器可以根据第一设备发送的应用的标识信息和该第一设备的位置信息确定从前述第一实例和第二实例中确定第三实例，该第三实例由该应用的标识信息、该第一设备的位置信息、该应用的第一实例的信息和该应用的第二实例的信息确定。在这样的实施方式中，当该第一设备需要获取该应用中的某一个实例时，该第一设备无需依次在第二服务器和第三服务器中查找该应用的实例的信息，而是可以直接从该第一服务器获取该应用的实例的信息，因此，可以减少该第一设备获取该应用的实例的信息的信令流程，进而可以减缓因增加信令而造成的网络时延。此外，该第一服务器还可以根据第一设备的需求为该第一设备选择出满足该第一设备的需求的应用的实例。因此，优化了该第一设备获取该应用的实例的信息的流程。
根据第一方面的第十一种实施方式，本申请实施例第一方面的第十二种实施方式中，该方法还包括：当该第三实例的IP地址为该第一实例的IP地址时，该第一服务器向该第一设备发送如下一项或多项：该第一边缘网络的接入标识信息、该第一边缘网络的IP地址、或该第一边缘使能服务器的IP地址；当该第三实例的IP地址为该第二实例的IP地址时，该第一服务器向该第一设备发送如下一项或多项：该第二边缘网络的接入标识信息、该第二边缘网络的IP地址、或该第二边缘使能服务器的IP地址。
本实施方式中，提出该第一服务器除了向该第一设备发送该应用的实例的IP地址之外，该第一服务器还向该第一设备发送边缘网络的接入标识信息、该边缘网络的IP地址、或该边缘使能服务器的IP地址中的一项或多项。因此，增加了该第一服务器提供给该第一设备的信息的多样性，以使得该第一服务器发送给该第一设备的应用的实例的信息可以更 好地满足该第一设备的需求。
根据第一方面的第十一种实施方式或第一方面的第十二种实施方式，本申请实施例第一方面的第十三种实施方式中，该第一设备为终端设备或边缘使能服务器。
本实施方式中，提出该第一设备可以为终端设备，该第一设备也可以为边缘使能服务器。因此，增加的该第一设备的多样性，以使得该第一设备可以在不同的应用场景下作为不同的设备或服务器执行前述方法。
根据第一方面、第一方面的第一种实施方式至第一方面的第九种实施方式中的任意一种实施方式，本申请实施例第一方面的第十四种实施方式中，该第二服务器或该第三服务器为如下任意一项：应用实例管理网元，该应用实例管理网元为用于部署所述应用实例的网元；或者，边缘使能服务器管理网元，该边缘使能服务器管理网元用于管理该边缘使能服务器。
本实施方式中，提出该第二服务器和该第三服务器还可以是除了边缘网络之外的其他网元，例如，应用实例管理网元或边缘使能服务器管理网元。因此，该前述实施方式还可以适用于该第一服务器与边缘网络之外的网络的信令交互流程。
第二方面，本申请实施例提供了一种获取信息的方法，该方法的实施主体包括第一服务器和第二服务器。其中，该第二服务器获取应用的第一实例的信息，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置；该第二服务器向第一服务器发送该第一实例的信息，该第一服务器为服务该第二服务器的服务器。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
本申请实施例中，由于，第二服务器可以将获取的应用的第一实例的信息发送给该第一服务器，以使得该第一服务器可以及时保存该第二服务器发送的第一实例的信息。因此，有利于该第一服务器保存该边缘网络中应用的实例的信息，便于该第一服务器向其他设备(例如第一设备)发送该应用的实例的信息。此外，还可以使其他设备(例如第一设备)无需从该第二服务器中获取该应用的实例的信息，而是可以直接从该第一服务器中获取该应用的实例的信息，因此，可以节省该第一服务器获取该应用的实例的信息的流程。
根据第一方面，本申请实施例第一方面的一种实施方式中，该第二服务器向该第一服务器发送第二服务器的区域信息。
根据第二方面，本申请实施例第二方面的第一种实施方式中，该第一信息包括该第一实例的互联网协议IP地址和如下一项或多项：第一边缘网络的接入标识信息、该第一边缘网络的IP地址、或第一边缘使能服务器的IP地址，该第二服务器位于该第一边缘网络中。
本实施方式中，对第一实例的信息中的第一信息进行了进一步限定。以第一信息为例，该第一信息除了包括第一实例的互联网协议IP地址以外，该第一信息还包括：第一边缘网络的接入标识信息、第一边缘网络的IP地址、或第一边缘使能服务器的IP地址中的一项或多项。因此，可以该通过多种标识信息或IP地址等信息确定该应用的第一实例的具体位置，以使得该第一服务器在获取该应用的第一实例的信息的同时，还可以准确确定该应用的第一实例的具体位置。
根据第二方面或第二方面的第一种实施方式，本申请实施例第二方面的第二种实施方式中，该第二服务器获取应用的第一实例的信息，包括：该第二服务器从该应用的第一实例服务器接收该第一实例的标识信息和该第一实例的IP地址；该第二服务器从该第二服务器获取该第一信息。
本实施方式中，明确了该第二服务器获取该应用的第一实例的信息的方式，该第一实例的信息中的第一实例的标识信息和该第一实例的IP地址可以由该第二服务器直接从该应用的第一实例服务器中获取，然后，该第二服务器再确定该第一信息。在这样的实施方式中，该第一实例的信息是该第二服务器从不同的服务器获取的。因此，该第二服务器可以保证该第一实例的信息的完整性。
根据第二方面或第二方面的第一种实施方式，本申请实施例第二方面的第三种实施方式中，该第二服务器获取应用的第一实例的信息，包括：该第二服务器从该应用的第一实例服务器接收该第一实例的信息。
本实施方式中，提出该第二服务器可以直接从该应用的第一实例服务器获取该第一实例的信息，即该第二服务器可以直接从该第一实例服务器中获取该第一实例的标识信息、该第一实例的IP地址和该第一信息。因此，可以简化该第二服务器获取该第一实例的信息的流程。
根据第二方面、第二方面的第一种实施方式至第二方面的第三种实施方式中的任意一种实施方式，本申请实施例第二方面的第四种实施方式中，该方法还包括：该第二服务器从该第一服务器接收第一应用程序接口API发现请求，该第一API发现请求包括发现类型信息，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例，或，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例和API，该应用的实例包括该第一实例。
本实施方式中，提出该第一服务器与该第二服务器之间的信令交互可以复用API通用架构CAPIF中的发现机制。具体地，该第一服务器可以通过向第二服务器发送第一API发现请求，以触发该第二服务器向该第一服务器发送应用的第一实例的信息。因此，该第一服务器不需要单独配置获取应用的实例的信息的请求，可以节省第一服务器与第二服务器之间的信令开销，进而可以减缓因增加信令造成的接入应用的延迟。
根据第二方面的第四种实施方式，本申请实施例第二方面的第五种实施方式中，该第二服务器向第一服务器发送该第一实例的信息，包括：该第二服务器向第一服务器发送第一API发现响应，该第一API发现响应包括该第一实例的信息。
本实施方式中，不仅提出该第一服务器与该第二服务器之间的信令交互复用API通用架构CAPIF中的发现机制，还提出将第二服务器发送给该第一服务器的第一实例的信息携带于该第一API发现响应中。因此，该第一服务器可以利用现有的信令从该第二服务器中接收该应用的实例的信息，该第二服务器不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
根据第二方面、第二方面的第一种实施方式至第二方面的第三种实施方式中的任意一种实施方式，本申请实施例第二方面的第六种实施方式中，该第二服务器向第一服务器发送该第一实例的信息，包括：该第二服务器向该第一服务器发送第一API发布请求，该第 一API发布请求包括该应用的第一实例的信息，该第一API发布请求用于发布该API和/或该第一实例。
本实施方式中，提出该第一服务器与该第二服务器之间的信令交互可以复用API通用架构CAPIF中的发布机制，并且，还提出将第二服务器发送给该第一服务器的第一实例的信息携带于该第一API发布请求中。因此，该第一服务器可以利用现有的信令分别从该第二服务器中接收该应用的实例的信息，该第二服务器不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
根据第二方面的第六种实施方式，本申请实施例第二方面的第七种实施方式中，该第一API发布请求还包括发布类型信息，该发布类型信息用于指示发布该应用的实例和/或发布API，该应用的实例包括该第一实例。
本实施方式中，提出该第一API发布请求和该第二发布请求还包括发布类型信息，该发布类型信息用于指示发布的内容的类型。因此，该第一服务器可以根据该发布类型信息确定该第一API发布请求所携带的信息中是否包括该应用的实例的信息。
根据第二方面的第六种实施方式或第二方面的第七种实施方式，本申请实施例第二方面的第八种实施方式中，该第二服务器获取应用的第一实例的信息，包括：该第二服务器从应用的第一实例服务器接收第三API发布请求，该第三API发布请求包括该第一实例的标识信息和该第一实例的IP地址，该第三API发布请求用于发布API和/或该第一实例。
本实施方式中，提出该第一服务器与该第二服务器之间的信令交互可以基于订阅-通知机制，即该第一服务器从该第二服务器订阅该应用的实例的信息，则该当该第二服务器中的应用的实例的信息更新时，该第二服务器将向该第一服务器发送该应用的实例的信息。因此，该第一服务器仅需向该第二服务器发送一次消息，即可接收来自该第二服务器或的应用的实例的信息。因此，可以节省该信令开销，进而可以减缓增加信令造成的接入应用的延迟。
根据第二方面、第二方面的第一种实施方式至第二方面的第三种实施方式中的任意一种实施方式，本申请实施例第二方面的第九种实施方式中，该第二服务器向第一服务器发送该第一实例的信息之前，该方法还包括：该第二服务器从该第一服务器接收订阅请求，该订阅请求用于请求订阅该应用的实例的信息。
根据第二方面的第九种实施方式，本申请实施例第二方面的第十种实施方式中，该订阅请求包括订阅条件，该订阅条件用于指示该应用的实例，该应用的实例包括该第一实例。
本实施方式中，可以在该订阅请求中携带订阅条件，以指示该第一服务器请求订阅的内容为应用的实例的信息，或者，以指示该第一服务器请求订阅的应用的实例的类型。
根据第二方面、第二方面的第一种实施方式至第二方面的第十种实施方式中的任意一种实施方式，本申请实施例第二方面的第十一种实施方式中，该应用的第一实例的信息还包括如下一项或多项：第一边缘使能服务器的标识信息，或者，该第一实例的服务范围信息。
本实施方式中，提出该应用的实例的信息还可以包括边缘使能服务器的标识信息，或者，该应用的实例的服务范围信息。其中，该边缘使能服务器的标识信息用于标识该边缘使能服务器的身份，以使得其他服务器或第一设备可以准确查找该边缘使能服务器。该应 用的实例的服务范围信息用于指示使用该应用的实例的用户所在的范围，也可以指该应用的实例服务的用户可能处于的位置。因此，本实施方式扩展了应用的实例的信息的具体实现方式，以使得该应用的实例的信息可以适用于具体场景的需求。
根据第二方面、第二方面的第一种实施方式至第二方面的第十一种实施方式中的任意一种实施方式，本申请实施例第二方面的第十二种实施方式中，该第一服务器为边缘网络配置服务器。
本实施方式中，明确了第一服务器在边缘网络中的具体实现方式，该第一服务器可以为边缘网络中的边缘网络配置服务器。
根据第二方面、第二方面的第一种实施方式至第二方面的第十二种实施方式中的任意一种实施方式，本申请实施例第二方面的第十三种实施方式中，该第二服务器为如下任意一项：边缘使能服务器；或者，边缘网络中的网络管理服务器。
本实施方式中，明确了第二服务器的具体实现方式，其中，该第二服务器可以为前述多种服务器中相同的服务器，也可以为前述多种服务器中不同的服务器。由于该第二服务器可以有多种实现方式，因此，增加了方案的多样性。
根据第二方面、第二方面的第一种实施方式、第二方面的第四种实施方式至第二方面的第十二种实施方式中的任意一种实施方式，本申请实施例第二方面的第十四种实施方式中，该第二服务器为如下任意一项：或者，该应用实例服务器，该应用实例服务器包括应用的第一实例服务器或应用的第二实例服务器；或者，运营支持系统OSS网元。
根据第二方面、第二方面的第一种实施方式至第二方面的第十二种实施方式中的任意一种实施方式，本申请实施例第一方面的第十五种实施方式中，该第二服务器为如下任意一项：应用实例管理网元，该应用实例管理网元为用于部署所述应用实例的网元；或者，边缘使能服务器管理网元，该边缘使能服务器管理网元用于管理该边缘使能服务器。
本实施方式中，提出该第二服务器还可以是除了边缘网络之外的其他网元，例如，应用实例管理网元或边缘使能服务器管理网元。因此，该前述实施方式还可以适用于该第一服务器与边缘网络之外的网络的信令交互流程。
第三方面，本申请提供了一种获取信息的方法，包括：用户设备从第一服务器接收第四服务器的区域信息，该第一服务器为服务于该第四服务器的服务器；该用户设备获取第一区域信息，该第一区域信息用于指示该用户设备所在的区域；该用户设备根据该第四服务器的区域信息和该第一区域信息，触发第四服务器的切换。
本实施例中，第一服务器在为用户设备确定了第四服务器之后，可以向用户设备发送第四服务器的区域信息，然后，用户设备可以根据获得的第一区域信息和前述第四服务器的区域信息确定是否要更新第四服务器，可以理解为，是否要将第四服务器切换为第五服务器。在这样的实施方式中，用户设备可以根据前述两个区域信息的比对情况触发更新第四服务器。这样使能层或应用层可以获取到第四服务器对应的DNAI信息，不必要求运营商提供第四服务器对应的网络格式的拓扑信息(小区标识列表或者追踪去列表)，也能够结合从网络层获取的DNAI和使能层获取的第四服务器的DNAI的信息，判断是否需要变更第四服务器。由此还可以保护运营商网络的拓扑信息。
根据第三方面，本申请实施例第三方面的一种实施方式中，该第四服务器的区域信息 和该第一区域信息不匹配。
根据第三方面，本申请实施例第三方面的一种实施方式中，该用户设备获取第一区域信息，包括：该用户设备从第二网元接收该第一区域信息；或者，该用户设备从第二网元接收第一信息与该第一区域信息的对应关系，该第一信息为对应于该第一区域信息指示的区域的小区标识或追踪区标识；该用户设备根据该对应关系和该用户设备的第二信息，确定该第一区域信息，该第二信息用于指示该用户设备所在位置的小区标识或追踪区标识。
根据第三方面，本申请实施例第三方面的一种实施方式中，该用户设备从第一服务器接收第四服务器的区域信息之前，该方法还包括：该用户设备向该第一服务器发送应用标识，该应用标识用于该第四服务器的确定。
根据第三方面，本申请实施例第三方面的一种实施方式中，当该第一服务器为边缘配置服务器时，该第四服务器为边缘使能服务器，该第四服务器服务于该应用标识对应的应用实例；或者，当该第一服务器为边缘使能服务器时，该第四服务器为该应用标识对应的应用实例。
根据第三方面，本申请实施例第三方面的一种实施方式中，该第二网元包括会话管理功能SMF网元或接入管理功能AMF网元、网络能力开放功能NEF、边缘配置服务器ECS、边缘使能服务器EES。
第四方面，本申请提供了一种获取信息的方法，包括：第一服务器从用户设备接收应用标识；该第一服务器根据该应用标识确定第四服务器，该第一服务器为服务该第四服务器的服务器；第一服务器向用户设备发送第四服务器的区域信息，该第四服务器的区域信息和第一区域信息用于第五服务器的确认，该第一区域信息用于指示该用户设备所在的区域。
根据第四方面，本申请实施例第四方面的一种实施方式中，当该第一服务器为边缘配置服务器时，该第四服务器为边缘使能服务器，该第四服务器服务于该应用标识对应的应用实例；或者，当该第一服务器为边缘使能服务器时，该第四服务器为该应用标识对应的应用实例。
根据第四方面，本申请实施例第四方面的一种实施方式中，当该第一服务器为边缘配置服务器时，该方法还包括：该第一服务器向第二网元发送第一消息，该第一消息用于影响该用户设备到该第四服务器的路由信息，该第一消息包括该用户设备的用户标识和应用标识，该第一消息还包括该目标服务器的用户流量描述信息和/或该目标服务器的区域信息。
根据第四方面，本申请实施例第四方面的一种实施方式中，当该第一服务器为边缘配置服务器时，该方法还包括：该第一服务器向第二网元发送第二消息，该第二消息用于影响该用户设备到该第四服务器对应的应用实例的路由信息，该第二消息包括该用户设备的用户标识和应用标识，该第一消息还包括该应用实例的用户流量描述信息和/或该应用实例的区域信息。
第五方面，本申请提供了一种获取信息的方法，包括：第二网元确定用户设备的第一区域信息，该第一区域信息用于指示该用户设备所在的区域；该第二网络向该用户设备发送该第一区域信息。
根据第五方面，本申请实施例第五方面的一种实施方式中，该第二网元存储有第一信息与该第一区域信息的对应关系，该第一信息为对应于该第一区域的小区标识或追踪区标识；该第二网元确定用户设备的第一区域信息，包括：该第二网元获取该用户设备的第二信息，该第二信息为该用户设备所在位置的小区标识或追踪区标识；该第二网元根据该用户设备的第二信息与该对应关系，确定该用户设备的第一区域信息。
根据第五方面，本申请实施例第五方面的一种实施方式中，该方法还包括：该第二网元从第一服务器接收第一消息，该第一消息用于影响该用户设备到目标服务器的路由信息，该第一消息包括该用户设备的用户标识和应用标识，该第一消息还包括该目标服务器的通行描述信息和/或该目标服务器的区域信息，该目标服务器服务于该应用标识对应的应用实例。
根据第五方面，本申请实施例第五方面的一种实施方式中，该方法还包括：
该第二网元从第一服务器接收第二消息，该第二消息用于影响该用户设备到目标服务器对应的一个应用实例的路由信息，该第二消息包括该用户设备的用户标识和应用标识，该第一消息还包括该应用实例的通行描述信息和/或该应用实例的区域信息。
根据第五方面，本申请实施例第五方面的一种实施方式中，该第二网元包括会话管理功能SMF网元、接入管理功能AMF网元、网络能力开放功能NEF网元、ECS或EES中的任意一项。
第六方面，本申请提供了一种获取信息的方法，包括：第二网元向用户设备发送第一区域信息和第一信息的对应关系，该第一区域信息用于指示该用户设备所在的区域，该第一信息为对应于该第一区域的小区标识或追踪区标识。
根据第六方面，本申请实施例第六方面的一种实施方式中，该第二网元包括会话管理功能SMF网元、接入管理功能AMF网元、网络能力开放功能NEF网元中、ECS、EES的任意一项。
第七方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以实现上述方法中第一服务器的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，上述获取信息的装置的结构中包括处理器和收发器，该处理器被配置为处理该获取信息的装置执行上述方法中相应的功能。该收发器用于实现上述获取信息的装置与第二服务器或第三服务器之间的通信。该获取信息的装置还可以包括存储器，该存储器用于与处理器耦合，其保存该获取信息的装置必要的程序指令和数据。
第八方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以实现上述方法中第二服务器的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，上述获取信息的装置的结构中包括处理器和收发器，该处理器被配置为处理该获取信息的装置执行上述方法中相应的功能。该收发器用于实现上述获取信息的装置与第一服务器和应用实例服务器之间的通信。该获取信息的装置还可以包括存储器，该存储器用于与处理器耦合，其保存该获取信息的装置必要的程序指令和数据。
第九方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以是第一 服务器，也可以是第一服务器内的芯片。该获取信息的装置可以包括处理模块和收发模块。当该获取信息的装置是第一服务器时，该处理模块可以是处理器，该收发模块可以是收发器；该第一服务器还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理模块执行该存储模块所存储的指令，以使该第一服务器执行第一方面或第一方面的任一种实施方式所介绍的方法。当该获取信息的装置是第一服务器内的芯片时，该处理模块可以是处理器，该收发模块可以是输入/输出接口、管脚或电路等；该处理模块执行存储模块所存储的指令，以使该第一服务器执行第一方面或第一方面的任一种实施方式所介绍的方法。此外，该存储模块可以是该芯片内的存储模块(例如，寄存器、缓存等)，也可以是该第一服务器内的位于该芯片外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以是第二服务器，也可以是第二服务器内的芯片。该获取信息的装置可以包括处理模块和收发模块。当该获取信息的装置是第二服务器时，该处理模块可以是处理器，该收发模块可以是收发器；该车联网获取信息的装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理模块执行该存储模块所存储的指令，以使该第二服务器执行第二方面或第二方面的任一种实施方式所介绍的方法。当该获取信息的装置是第二服务器内的芯片时，该处理模块可以是处理器，该收发模块可以是输入/输出接口、管脚或电路等；该处理模块执行存储模块所存储的指令，以使该第二服务器执行第二方面或第二方面的任一种实施方式中所介绍的方法。该存储模块可以是该芯片内的存储模块(例如，寄存器、缓存等)，也可以是第二服务器内的位于该芯片外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十一方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以是用户设备，也可以是用户设备内的芯片。该获取信息的装置可以包括处理模块和收发模块。当该获取信息的装置是用户设备时，该处理模块可以是处理器，该收发模块可以是收发器；该车联网获取信息的装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理模块执行该存储模块所存储的指令，以使该用户设备执行第三方面或第三方面的任一种实施方式所介绍的方法。当该获取信息的装置是用户设备内的芯片时，该处理模块可以是处理器，该收发模块可以是输入/输出接口、管脚或电路等；该处理模块执行存储模块所存储的指令，以使该用户设备执行第三方面或第三方面的任一种实施方式中所介绍的方法。该存储模块可以是该芯片内的存储模块(例如，寄存器、缓存等)，也可以是用户设备内的位于该芯片外部的存储模块(例如，只读存储器、随机存取存储器等)。
第十二方面，本申请实施例提供了一种通信系统，该通信系统包括：第一服务器、第二服务器和第三服务器；该第二服务器，用于获取应用的第一实例的信息；该第三服务器，用于获取应用的第二实例的信息；该第一服务器，用于从该第二服务器和该第三服务器接收该应用的第一实例的信息和该应用的第二实例的信息，并保存该应用的第一实例的信息和该应用的第二实例的信息。
第十三方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行如前述第一方面至第六方面中任意一种实施方式所介绍的方法。
第十四方面，本申请实施例提供了一种计算机可读存储介质，包括指令，当该指令在计算机上运行时，以使得计算机执行如前述第一方面至第六方面中任意一种实施方式所介绍的方法。
从以上技术方案可以看出，本申请实施例具有以下优点：
本申请实施例中，由于，管理应用的实例的信息的第一服务器可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存于该第一服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该第一服务器向其他设备(例如第一设备)发送该应用实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例。
图1A为本申请实施例中提供的一个系统架构图；
图1B为本申请实施例中获取信息的方法的一个流程图；
图1C为本申请实施例中获取信息的方法的另一个系统架构图；
图1D为本申请实施例中获取信息的方法的另一个系统架构图；
图2为本申请实施例中获取信息的方法的另一个流程图；
图3A为本申请实施例中获取信息的方法适应的另一个系统架构图；
图3B为本申请实施例中获取信息的方法适应的另一个系统架构图；
图4为本申请实施例中获取信息的方法的另一个流程图；
图5为本申请实施例中获取信息的方法的另一个流程图；
图6A为本申请实施例中获取信息的方法适应的另一个系统架构图；
图6B为本申请实施例中获取信息的方法适应的另一个系统架构图；
图6C为本申请实施例中获取信息的方法适应的另一个系统架构图；
图7为本申请实施例中获取信息的方法的另一个流程图；
图8为本申请实施例中获取信息的方法的另一个流程图；
图9为本申请实施例中获取信息的装置的一个实施例示意图；
图10为本申请实施例中获取信息的装置的另一个实施例示意图；
图11为本申请实施例中获取信息的装置的另一个实施例示意图；
图12为本申请实施例中获取信息的装置的另一个实施例示意图；
图13为本申请实施例中获取信息的方法的另一个流程图；
图14为本申请实施例中获取信息的方法的另一个流程图；
图15为本申请实施例中获取信息的方法的另一个流程图；
图16为本申请实施例中获取信息的方法的另一个流程图；
图17为本申请实施例中获取信息的方法的另一个流程图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例提供了一种获取信息的方法，用于获取并保存应用的实例的信息，以使得用户可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
为便于理解，下面先对本申请实施例所涉及的部分技术术语进行解释：
应用(application)：指运行于终端设备或服务器中的程序，以使得用户可以获取该应用提供的业务。其中，运行于终端设备的程序称为应用客户端程序，运行于服务器中的程序称为应用服务器程序。本申请实施例中的应用指的是应用服务器程序。
实例(instance)：即应用的实例，指应用服务器程序在一个服务器中的运行实例，同一个应用的不同实例可以运行于不同的边缘网络中的服务器上。可以理解为，应用的实例为运行于应用实例服务器中的程序。为便于理解，以应用是华为视频为例对前述应用和应用的实例进行介绍。
应用程序接口(application programming interface，API)：也可以被称为应用程序编程接口，是软件系统不同组成部分衔接的约定。该API规定了运行在一个端系统(例如，终端设备或服务器)上的软件请求因特网基础设施向运行在另一个端系统(例如，另一个终端设备或另一服务器)上的特定目的地软件交付数据的方式。
为便于理解，下面先对本申请实施例所提出的获取信息的方法的系统架构和应用场景进行介绍：
本申请实施例提出的方案主要基于第五代移动通信(the 5th generation，5G)技术或新无线技术，也可以基于后续演进接入制式，具体此处不做限定。在本实施例以及后续实施例中，仅以基于5G的通信系统为例进行介绍。
如图1A所示，为一种适用于获取信息的方法的系统架构图，该系统主要包括：第一服务器101、第二服务器102和第一设备103。
其中，该第二服务器102用于确定应用的实例的信息，该应用的实例的信息可以由该第二服务器102生成，也可以由该第二服务器102从其他的服务器中获得。
该第一服务器101用于从该第二服务器102中获取并保存应用的实例的信息，以供该第一设备103使用。具体地，该第一服务器101通过第一接口111与第二服务器102连接，因此，该第一服务器101可以从该第二服务器102获取该第二服务器102中存储的应用的实例的信息。该第一服务器101通过第二接口112与第一设备103连接，因此，该第一服 务器101可以将该第一服务器101中存储的信息发送给该第一设备103，其中，该第一服务器101中存储的应用的实例的信息可以包括从该第二服务器102中获取的应用的实例的信息。
该第一设备103可以是终端设备，也可以是服务器，还可以是其他需要通过第二接口112从该第一服务器101获取应用的实例的信息的设备，具体名称此处不做限定。
具体地，当该第一设备103为终端设备时，该第一设备可以为能够使用应用实例服务器提供的应用的终端设备。该终端设备包括向用户提供语音和/或数据连通性的设备，例如，可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以包括用户设备(user equipment，UE)、无线终端设备、移动终端设备、用户单元(subscriber unit)、用户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point，AP)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、或用户装备(user device)等。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、等设备。此外，在车联网场景下，该终端设备可以是车载终端、路侧终端或者可穿戴设备。此外，在物联网场景下，该终端设备可以为受限设备，例如，低功耗终端设备，或存储能力有限的终端设备，或计算能力有限的终端设备，具体此处不做限定。
此外，当该第一设备103为服务器时，该第一设备103可以为边缘使能服务器，该边缘使能服务器用于为部署在边缘网络中的应用实例提供使能能力(enabler capability)或使能服务(enabler service)，以更好的支持应用在MEC的部署。其中，前述使能能力或使能服务可以来自于第三代伙伴计划(the 3rd generation partnership project，3GPP)网络，也可以来自于边缘使能服务器。
还应理解的是，本申请实施例中的第一设备103可以是上述任意一种场景下的设备或该设备中的芯片、服务器或该服务器中的芯片，具体此处不做限定。无论作为设备还是作为芯片，该第一设备103都可以作为独立的产品进行制造、销售或者使用。
基于前述图1A所示的系统架构，如图1B所示，本申请实施例所提出的获取信息的方法的主要流程包括如下步骤：
001、第一服务器从第二服务器接收应用的第一实例的信息。
由前述系统架构可知，该第二服务器用于确定应用的实例的信息，该应用的实例的信息可以由该第二服务器生成，也可以由该第二服务器从其他的服务器中获得。并且，该第一服务器通过前述第一接口111与第二服务器连接。为便于介绍，将该第二服务器确定的应用的实例的信息称为第一实例的信息。于是，该第一服务器可以从该第二服务器接收应用的第一实例的信息。
其中，该第一实例的信息包括该应用的标识信息和第一信息，该应用的标识信息用于 标识该应用。该第一信息用于指示该第一实例的位置。具体地，后文步骤201a中将详细介绍，具体此处不再赘述。
002、该第一服务器从第三服务器接收该应用的第二实例的信息。
本实施例中，与该第一服务器连接的服务器除了前述第二服务器之外，还可能存在第三服务器，该第三服务器与该第二服务器类似。该第三服务器用于确定应用的实例的信息，该应用的实例的信息可以由该第三服务器生成，也可以由该第三服务器从其他的服务器中获得。为便于介绍，将该第三服务器确定的应用的实例的信息称为第二实例的信息。该第二实例的信息包括该应用的标识信息和第二信息，该第二信息用于指示该第二实例的位置。
此外，该第一服务器为服务前述第二服务器和前述第三服务器的服务器。
应当注意的是，步骤001与步骤002之间无明确的时间先后顺序的限定。也就是说，步骤001可以在步骤002之前执行，或者，步骤001可以在步骤002之后执行，或者步骤001与步骤002可以同时执行，具体此处不做限定。
003、该第一服务器保存该第一实例的信息和该第二实例的信息。
当该第一服务器获取到该第一实例的信息时，该第一服务器可以将该第一实例的信息保存于该第一服务器中；当该第一服务器获取到该第二实例的信息时，该第二服务器可以将该第二实例的信息保存于该第一服务中。由于，前述步骤001与前述步骤002无明确的时间先后顺序的限定，因此，该第一服务器保存该第一实例的信息的步骤与该第一服务器保存该第二实例的信息的步骤之间无明确的时间先后顺序的限定。也就是说，该第一服务器可以先保存该第一实例的信息再保存该第二实例的信息，该第一服务器也可以先保存该第二实例的信息再保存该第一实例的信息，该第一服务器还可以同时保存该第一实例的信息和该第二实例的信息，具体此处不做限定。
本实施例中，前述第一服务器可以为边缘网络配置服务器，或其他服务器，具体此处不做限定。前述第二服务器或该第三服务器为边缘使能服务器、边缘网络中的网络管理服务器、应用实例服务器、运营支持系统(operation support systems，OSS)网元、应用实例管理网元、或边缘使能服务器管理网元中的任意一种服务器或网元，具体此处不做限定。具体地，后文将做详细介绍，具体请参见后文图2对应的实施例。
此外，该第二服务器和该第三服务器可以为相同种类的服务器，例如，该第二服务器和该第三服务器均可以为边缘使能服务器；该第二服务器和该第三服务器也可以为不同种类的服务器，例如，该第二服务器为边缘使能服务器，该第三服务器为边缘网络中的网络管理服务器，具体此处不做限定。
本实施例中，由于，该第一服务器可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存于该第一服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该第一服务器向其他设备(例如第一设备103)发送该应用实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
在图1A所示的系统中，该第二服务器102可以用于生成应用的实例的信息，可以用于从其他的服务器中获取该应用实例的信息。当该第二服务器102用于生成应用的实例的信息时，该第二服务器102为应用实例服务器。该第二服务器102用于从其他的服务器中获取该应用实例的信息时，该获取信息的方法适应的系统架构图可以进一步如图1C所示。
在如图1C所示的系统中，除了前述第一服务器101、前述第二服务器102和前述第一设备103之外，还包括应用实例服务器104。其中，该应用实例服务器104用于生成应用的实例的信息。该应用实例服务器104通过第四接口114与第二服务器102连接，该应用实例服务器104可以将该实例的信息传输至该第二服务器102，或者，该第二服务器102通过该第四接口114获取该应用实例服务器104中的实例的信息。
此外，该应用实例服务器104还通过第三接口113与该第一服务器101连接，该应用实例服务器104可以将该实例的信息传输至该第一服务器101，或者，该第一服务器101通过该第三接口113获取该应用实例服务器104中的实例的信息。
应当理解的是，在如图1C中的第二服务器102和应用实例服务器104位于第一边缘网络(edge network)中。其中，该边缘网络也可以被称为边缘计算网络(edge computing network)，用于表示应用部署的问题，如本地数据中心。在一些实施方式中，该边缘网络也可以是边缘数据网络(edge data network，EDN)。在本实施例以及后续实施例中，仅以边缘网络为例进行介绍。并且，应当理解的是，该边缘网络可以包含前述边缘计算网络或边缘数据网络的部分或全部能力，具体此处不做限定。
该边缘网络中可以存在多个第二服务器102和多个应用实例服务器104。并且，每个应用实例服务器104仅可以被一个对应的第二服务器102管理，也可以理解为应用实例服务器104对仅可以被一个对应的第二服务器102服务，也可以理解为应用实例服务器104仅可以从一个对应的第二服务器102获得服务。在实际应用中，该第二服务器102为一个或多个应用的应用实例服务器104提供服务，该第二服务器102可以为边缘使能服务器(edge enabler server，EES)或者其他具备为一个或多个应用的应用实例服务器104提供边缘使能服务的功能实体，此处不对该第二服务器的具体实现形式做限定。该第一服务器101可以为边缘网络配置服务器(edge network configuration server)，在一些实施方式中，该边缘网络也可以是边缘数据网络配置服务器(edge data network configuration server)，或者其他可以具备第一服务器功能的功能实体，此处不对该第一服务器的具体实现形式做限定。
还应理解的是，该第一服务器101还可以与另一个边缘网络连接，即该第一服务器可以服务于多个边缘网络，具体如图1D所示，此时，该第一服务器101与第一边缘网络和第二边缘网络连接。为便于介绍，称前述第一边缘网络中通过第四接口114与该第二服务器102连接的应用实例服务器为应用的第一实例服务器1041；称第二边缘网络中通过第七接口117与该第三服务器105连接的应用实例服务器为应用的第二实例服务器1042。
具体地，该第二边缘网络中的第三服务器105通过第五接口115与第一服务器101连接，该第三服务器105通过第七接口117于应用的第二实例服务器1042连接，该应用的第二实例服务器1042通过第六接口116与第一服务器101连接。具体地，该应用的第二实例服务器1042与前述应用实例服务器104类似，第三服务器105与第二服务器102类似，具 体此处不再赘述。
此外，本申请实施例中的第一服务器、第二服务器或第三服务器可以为服务器或该服务器中的芯片，具体此处不做限定。无论作为服务器还是作为芯片，该第一服务器、第二服务器或第三服务器都可以作为独立的产品进行制造、销售或者使用。
上面对本申请实施例所涉及的系统架构进行了介绍，下面结合前述系统架构对本申请实施例所提出的方法进行介绍：
应当理解的是，前述系统架构图1D仅示出了第一服务器与第一边缘网络中的第二服务器连接，第一服务器与第二边缘网络中的第三服务器连接。但是，应当理解的是，该第一边缘网络中还可能存在多个第二服务器，该第二边缘网络中还可能存在多个第三服务器，该第一服务器还可能与其他边缘网络或数据网络连接(例如，第三边缘网络)，该其他边缘网络或数据网络中还可能存在其他的服务器(例如，第四服务器)等，具体此处不做限定。在本实施例以及后续实施例中，仅以该第一服务器与第二服务器之间的信息交互和第一服务器与第三服务器之间的信息交互为例进行介绍。具体地，如图2所示，该获取信息的方法的包括如下步骤：
201a、第二服务器获取应用的第一实例的信息。
本实施例中，该第二服务器为服务于应用的实例(application instance)的服务器。当该第二服务器为服务于多个应用的实例的服务器时，该多个应用的实例可以为同一应用的不同的实例，该多个应用的实例也可以为属于不同应用的不同实例，具体此处不做限定。在本实施例以及后续实施例中，仅以该多个应用的实例为同一应用的不同的实例为例进行介绍。因此，对于在第二服务器所在的边缘网络部署的应用，该第二服务器可以获取该应用的一个或者多个实例的信息。其中，该应用(application)指运行于终端设备或服务器中的程序，以使得该用户可以通过操作与该终端设备交互获取该应用提供的业务。运行在终端设备的程序称为应用客户端程序，运行在服务器中的程序称为应用服务器程序。本申请实施例中的应用指的是应用服务器程序。该应用的实例指应用服务器程序在一个服务器中运行的实例(instance)，不同的一个应用的不同实例可以运行在不同的边缘网络中的服务器。可以理解为，应用的实例为运行于应用实例服务器中的程序。为便于理解，以应用是华为视频为例对前述应用和应用的实例进行介绍。此时，若华为视频服务器集中部署在深圳(即华为视频的服务器程序运行在部署在深圳的服务器上，我们可以称之为华为视频应用的云端)，并且，当运营商在北京设置了一个北京数据中心，可以提供华为视频应用服务器的运行环境的服务器，则华为视频应用可以将其华为视频的应用服务器程序运行在服务器部署在该北京数据中心的服务器上，此时，那么这个运行在部署在北京数据中心的华为应用服务器上的华为视频的应用服务器程序就可以称为华为视频的一个应用实例(简称“华为视频-北京实例”)，这个服务器为华为视频应用实例服务器。于是，距离该数据中心的近的华为视频的客户端可以连接到华为视频-北京实例访问华为视频提供的内容。以上对于应用和应用的实例的解释也适用于本发明的其他实施例。
具体地，该第二服务器获取应用的第一实例的信息，该第一实例的信息包括该应用的标识信息和第一信息，其中，第一信息用于指示该应用的第一实例的位置。
其中，该应用的标识信息用于标识该应用。例如，该应用的标识信息可以为该应用的名称，或唯一标识该应用的序列号，或其他可以唯一标识该应用的字符串，具体此处不做限定。例如，该应用的标识信息可以为如下一种或多种：应用的标识符(application ID)、统一资源定位符(uniform resource locator，URL)、全量域名(fully qualified domain name，FQDN)、应用名称(application name)。例如，该第一信息包括该第一实例的互联网协议IP地址，该第一实例的IP地址可以为虚拟IP地址或者第一边缘网络内网IP地址，具体此处不做限定。此外，第一信息还可以包括如下一项或多项：第一边缘网络的接入标识信息或第一边缘网络的IP地址。其中，该第一边缘网络的接入标识信息也被称为第一数据网络的接入标识符(data network access identifier，DNAI)，表示访问部署应用程序的一个或多个数据网络(data network，DN)用户平面接入点。该第一边缘网络的IP地址，为该第二服务器所在的边缘网络的IP地址，可以是一个IP地址段。此外，当该第二服务器为边缘使能服务器时，该第一信息还可以包括第一边缘使能服务器的IP地址，该第一边缘使能服务器为该应用的第一实例的提供边缘使能服务的服务器。
可选的，该第一实例的信息除了该应用的标识信息和第一信息，还包括第一边缘使能服务器的标识信息，或该第一实例的服务范围信息。其中，该第一边缘使能服务器为前述为该应用的第一实例的提供边缘使能服务的服务器，该第一边缘使能服务器的标识信息用于标识该第一边缘使能服务器，以使得其他服务器或第一设备可以准确查找该第一边缘使能服务器。该第一实例的服务范围信息用于指示使用该应用的第一实例可以提供应用业务的范围，该范围可以是第一边缘网络覆盖区域的一个子集。具体地，该第一实例的服务范围信息可以为一组追踪区标识(tracking area identity，TAI)，也可以为小区的标识信息，例如小区ID(cell ID)或小区列表(cell ID list)，还可以为经纬度或行政区域信息等，具体此处不做限定。
当该第二服务器获取该应用的第一实例的信息时，该第二服务器可以采用不同的实现方式。具体如下：
在一种实现方式中，该第二服务器从该应用的第一实例服务器接收该第一实例的标识信息和该第一实例的IP地址，该第二服务器从该第二服务器的本地信息中获取该第一信息中的其他信息，例如第二服务器也处于同一个第一边缘网络，则第二服务器的本地信息中保存有第一边缘网络的接入标识信息、第一边缘网络的IP地址或第二服务器的IP地址中的一项或多项。此时，该第二服务器便可获得该应用的第一实例的信息。
在另一实现方式中，该第二服务器可以直接从该应用的第一实例服务器接收该第一实例的信息。
在实际应用中，该第二服务器可以采用前述任意一种实现方式获取该第一实例的信息，具体此处不做限定。
201b、第三服务器获取应用的第二实例的信息。
本实施例中，该第三服务器与前述第二服务器类似，该第三服务器也为服务于应用的实例(application instance)的服务器。当该第三服务器为服务于多个应用的实例的服务器时，该多个应用的实例可以为同一应用的不同的实例，该多个应用的实例也可以为属于不同应用的不同实例，具体此处不做限定。在本实施例以及后续实施例中，仅以该多个 应用的实例为同一应用的不同的实例为例进行介绍。因此，对于在第三服务器所在的边缘网络部署的应用，该第三服务器可以获取该应用的一个或者多个实例的信息。但是，该第三服务器服务(serving)的应用的实例与前述第二服务器服务(serving)的应用的实例不同，为便于介绍，称该第三服务器服务的应用的实例为第二实例。应当理解的是，前述第二实例、第三实例仅是为了区分不同的实例而取的称谓，并不对该第二服务器服务的名称和第三服务器服务的名称进行限定。
具体地，该第三服务器获取应用的第二实例的信息，该第二实例的信息包括该应用的标识信息和第二信息。该第二信息包括该第二实例的互联网协议IP地址。此外，第二信息还可以包括如下一项或多项：第二边缘网络的接入标识信息或第二边缘网络的IP地址。当该第二服务器为边缘使能服务器时，该第二信息还可以包括第二边缘使能服务器的IP地址。当该第三服务器获取该应用的第二实例的信息时，该第三服务器可以采用如下不同的实现方式：
在一种实现方式中，该第三服务器从该应用的第二实例服务器接收该第二实例的标识信息和该第二实例的IP地址，该第三服务器从该第三服务器的本地信息中获取该第二信息中的其他信息，例如第三服务器也处于同一个第一边缘网络，则第三服务器的本地信息中保存有第二边缘网络的接入标识信息、第二边缘网络的IP地址或第三服务器的IP地址中的一项或多项。此时，该第三服务器便可获得该应用的第二实例的信息。
在另一实现方式中，该第二实例对应的第二实例服务器中存有该第二信息，于是，该第三服务器可以直接从该应用的第二实例服务器接收该第二实例的信息。
该应用的第二实例的信息还包括如下一项或多项：
第二边缘使能服务器的标识信息，或者，该第二实例的服务范围信息。
具体地，步骤201b与步骤201a类似，具体此处不再赘述。
应当注意的是，步骤201a与步骤201b之间无明确的时间先后顺序的限定。也就是说，步骤201a可以在步骤201b之前执行，或者，步骤201a可以在步骤201b之后执行，或者步骤201a与步骤201b可以同时执行，具体此处不做限定。
202a、第二服务器向第一服务器发送第一实例的信息。
本实施例中，当该第二服务器获取该应用的第一实例的信息之后，该第二服务器可以向该第一服务器发送第一实例的信息，相应地，该第一服务器可以从第二服务器接收该第一实例的信息。其中，该第一服务器为服务(serving)前述第二服务器和第三服务器的服务器，可以理解为该第一服务器可以为该第二服务器和该第三服务器提供对应的边缘网络的配置信息；也可以理解为，该第三服务器和该第二服务器被配置有第一服务器的地址，可以连接到第一服务器。具体地，该第一服务器可以从该第二服务器和该第三服务器中获取该应用的不同实例的信息。在实际应用中，该第一服务器不仅仅只服务于前述第二服务器和前述第三服务器，该第一服务器还可能服务其他的服务器。
此外，需要注意的是，该第一服务器从第二服务器接收的第一实例的信息可以携带于基于请求-响应(request-response)机制的消息中，例如，该第一服务器向该第二服务器发送一个请求消息，该第二服务器向该第一服务器回复一个响应消息，并且，在该响应消息中携带该第一实例的信息。或者，该第一服务器从第二服务器接收的第一实例的信息可 以携带于基于订阅-通知(subscribe-notification)机制的消息中，例如，该第一服务器向该第二服务器发送一个订阅消息，该订阅消息用于订阅该第二服务器中的应用的实例的信息。该第二服务器向该第一服务器回复一个或多个基于前述订阅消息的通知消息，并且，每个通知消息中均携带该应用的第一实例的信息。例如，当该第二服务器中的应用的实例的信息每次更新时，该第二服务器都会向该第一服务器发送一次通知消息。应当理解的是，本实施例中所涉及的更新，可以指该应用的实例的信息初次出现在该第二服务器中，例如，该第二服务器第一次获取应用的第一实例的信息；也可以指该第二服务器中应用的实例的信息没有增减但发生了变更，例如，该第二服务器中的第一实例的信息中的第一实例的IP地址，由IP地址A变更为IP地址B；还可以指该应用的实例的信息全部或部分从该第二服务器中删除或失效，例如，该第一实例的信息中的第一实例的服务范围信息由追踪区标识TAI和小区的标识信息变更为仅有该追踪区标识TAI。具体此处不做限定。
202b、第三服务器向第一服务器发送第二实例的信息。
本实施例中，当该第三服务器获取该应用的第二实例的信息之后，该第三服务器可以向该第一服务器发送第二实例的信息，于是，该第一服务器可以从第三服务器接收该第二实例的信息。具体地，该第一服务器从第三服务器接收的第二实例的信息可以携带于基于请求-响应(request-response)机制的消息中，也可以携带于基于订阅-通知(subscribe-notification)机制的消息中。具体地，与前述步骤202a类似，具体此处不再赘述。
应当注意的是，步骤202a与步骤202b之间无明确的时间先后顺序的限定。也就是说，步骤202a可以在步骤202b之前执行，或者，步骤202a可以在步骤202b之后执行，或者步骤202a与步骤202b可以同时执行，具体此处不做限定。
203、该第一服务器保存该第一实例的信息和该第二实例的信息。
当该第一服务器获取到该第一实例的信息时，该第一服务器可以将该第一实例的信息保存于该第一服务器中；当该第一服务器获取到该第二实例的信息时，该第二服务器可以将该第二实例的信息保存于该第一服务中。由于，前述步骤202a与前述步骤202b无明确的时间先后顺序的限定，因此，该第一服务器保存该第一实例的信息的步骤与该第一服务器保存该第二实例的信息的步骤之间无明确的时间先后顺序的限定。也就是说，该第一服务器可以先保存该第一实例的信息再保存该第二实例的信息，该第一服务器也可以先保存该第二实例的信息再保存该第一实例的信息，该第一服务器还可以同时保存该第一实例的信息和该第二实例的信息，具体此处不做限定。
本实施例中，由于，该第一服务器可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存于该第一服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该第一服务器向其他设备(例如第一设备)发送该应用实例的信息。当第一设备需要查询获取该应用的实例的信息时，该第一设备可以直接从该第一服务器处获取，于是，该第一设备无需遍历第二服务器和第三服务器后才能从第二服务器或第三服务器中获取。因此，可以节省信令开销，减缓业务时延。
204a、该第一服务器向该第二服务器发送保存响应。
本实施例中，步骤204a为可选的步骤。当该第一服务器保存了该第一实例的信息之后，该第一服务器可以向该第二服务器发送保存响应，该保存响应用于通知该第二服务器该第一服务器已经保存该第一实例的信息。
204b、该第一服务器向该第三服务器发送保存响应。
本实施例中，步骤204b为可选的步骤。当该第一服务器保存了该第二实例的信息之后，该第一服务器可以向该第三服务器发送保存响应，该保存响应用于通知该第三服务器该第一服务器已经保存该第二实例的信息。
应当注意的是，步骤204a与步骤204b之间无明确的时间先后顺序的限定。也就是说，步骤202a可以在步骤202b之前执行，或者，步骤202a可以在步骤202b之后执行，或者步骤202a与步骤202b可以同时执行，具体此处不做限定。
本实施例中，该第一服务器向该第二服务器或该第三服务器发送保存响应，有利于该第二服务器和该第三服务器确定该第一实例的信息和该第二实例的信息的保存情况。
205、第一设备向该第一服务器发送应用的标识信息和第一设备的位置信息。
本实施例中，步骤205为可选的步骤，当第一设备需要获取该第一服务器中的应用的实例的信息时，该第一设备将向该第一服务器发送应用的标识信息和第一设备的位置信息，于是，该第一服务器从第一设备接收该应用的标识信息和该第一设备的位置信息。其中，该应用的标识信息的介绍可以参见前述步骤201a，具体此处不再赘述。其中，该第一设备的位置信息可以是第一设备所在位置的TAI、cell ID、DNAI、行政位置信息、地理位置信息或经纬度信息中的一项或多项。
206、第一服务器向该第一设备发送第三实例的IP地址。
本实施例中，步骤206为可选的步骤，该第一服务器可以向第一设备返回该第一设备欲获取的实例的IP地址。为便于介绍，称该第一设备欲获取的实例为第三实例，该第三实例为第一实例或第二实例。该第三实例由该应用的标识信息、该第一设备的位置信息、该应用的第一实例的信息和该应用的第二实例的信息确定。第一服务器确定该应用的标识信息对应的应用为第一实例和第二实例对应的应用，若第一服务器确定该第一设备的位置信息与该第一实例的位置信息相同，则第一服务器确定第三实例为第一实例；或者，若第一服务器确定第一设备的位置信息所指示位置与该第一实例的信息所指示的位置的距离比第一设备的位置信息所指示位置与该第二实例的信息所指示的位置的距离小，则第一服务器确定第三实例为第一实例。在实际应用中，该第一服务器还可以采用其他方式确定该第三实例，具体此处不再赘述。
可选的，该第一服务器还将向该第一设备发送其他的关于该第三实例的信息。
在一种实施方式中，当该第三实例的IP地址为该第一实例的IP地址时，该第一服务器还将向该第一设备发送该第一边缘网络的接入标识信息、该第一边缘网络的IP地址、或该第一边缘使能服务器的IP地址中的一项或者多项。在这种实施方式中，该第一服务器除了向该第一设备发送该第一实例的IP地址之外，该第一服务器向该第一设备发送第一边缘网络的接入标识信息或该第一边缘网络的IP地址，可以使该第一设备确定该第一实例的信息对应的第一实例服务器所在的位置。此外，该第一服务器向该第一设备发送第一边缘使能服务器的IP地址可以使该第一设备确定该第一边缘使能服务器在边缘网络中的位置。因 此，有利于该第一设备根据前述第一实例服务器的位置或第一边缘使能服务器的位置执行其他的操作。
在另一种实施方式中，当该第三实例的IP地址为该第二实例的IP地址时，该第一服务器还将向该第一设备发送该第二边缘网络的接入标识信息、该第二边缘网络的IP地址、或该第二边缘使能服务器的IP地址中的一项或者多项。在这种实施方式中，该第一服务器除了向该第一设备发送该第二实例的IP地址之外，该第一服务器向该第一设备发送第二边缘网络的接入标识信息或该第二边缘网络的IP地址可以使该第一设备确定该第二实例的信息对应的第二实例服务器所在的位置。此外，该第一服务器向该第一设备发送第二边缘使能服务器的IP地址可以使该第一设备确定该第二边缘使能服务器在边缘网络中的位置。因此，有利于该第一设备根据前述第二实例服务器的位置或第二边缘使能服务器的位置执行其他的操作。
还应理解的是，本实施例中，与该第一服务器进行信息交互的服务器不仅仅限于前述第二服务器和前述第三服务器，还可能存在与前述第二服务器和第三服务器类似的服务器，例如，可能存在第四服务器，用于获取应用的第三实例的信息。此时，该第一服务器与该第四服务器的信息交互过程可以参见前述第一服务器与第二服务器或第三服务器的方法流程，具体此处不做限定。并且，还应理解的是，本实施例仅以第一服务器与第二服务器和第三服务器之间的信息交互为例进行介绍，对与该第一服务器进行信息交互的服务器的个数并不做限定。
本实施例中，提出该第一服务器可以根据第一设备发送的应用的标识信息和该第一设备的位置信息确定从前述第一实例和第二实例中确定第三实例。因此，当该第一设备需要获取该应用中的某一个实例时，该第一设备无需依次在第二服务器和第三服务器中查找该应用的实例的信息，而是可以直接从该第一服务器获取该应用的实例的信息，因此，可以减少该第一设备获取该应用的实例的信息的信令流程，进而可以减缓因增加信令而造成的网络时延。此外，该第一服务器还可以根据第一设备的需求为该第一设备选择出满足该第一设备的需求的应用的实例。因此，优化了该第一设备获取该应用的实例的信息的流程。
本实施例中，前述第一服务器可以为边缘网络配置服务器，或其他服务器，具体此处不做限定。前述第二服务器或该第三服务器为边缘使能服务器、边缘网络中的网络管理服务器、应用实例服务器、运营支持系统OSS网元、应用实例管理网元、或边缘使能服务器管理网元中的任意一种服务器或网元，具体此处不做限定。其中，应用实例管理网元指用于管理应用实例的网元或功能实体，例如，将应用实例的软件包资源(package)打包并分发至边缘网络的运行环境中的网元或功能实体。该边缘使能服务器管理网元指用于管理边缘使能服务器，例如，为边缘使能服务器配置存储和计算资源，向边缘使能服务器中配置边缘网络的信息，向边缘使能服务器配置需要提供边缘使能服务的应用的实例。
此外，该第二服务器和该第三服务器可以为相同种类的服务器，例如，该第二服务器和该第三服务器均可以为边缘使能服务器；该第二服务器和该第三服务器也可以为不同种类的服务器，例如，该第二服务器为边缘使能服务器，该第三服务器为边缘网络中的网络管理服务器，具体此处不做限定。
但是，当该第二服务器为应用的第一实例服务器时，由于该应用的第一实例服务器内 部存储有该第一实例的信息，因此，第二服务器(即应用的第一实例服务器)将不执行前述步骤201a，并且，可以直接执行步骤202a以及后续步骤。类似的，当该第三服务器为应用的第二实例服务器时，第三服务器(即应用的第二实例服务器)将不执行前述步骤201b，并且，可以直接执行步骤202b以及后续步骤。
此外，当该第二服务器或第三服务器为边缘网络中的网络管理服务器或运营支持系统网元时，由于该网络管理服务器或该运营支持系统网元中已配置有该应用的实例的信息，因此，该第二服务器将不执行前述步骤201a，并且，可以直接执行步骤202a以及后续步骤。类似的，该第三服务器将不执行前述步骤201b，并且，可以直接执行步骤202b以及后续步骤。
为便于进一步理解，下面将以该第一服务器为边缘网络配置服务器、第二服务器为边缘使能服务器和该第一设备为用户设备的实现方式进行进一步介绍。具体地，如图3A所示，该多接入边缘计算网络架构主要包括：边缘网络配置服务器301、边缘使能服务器302、应用实例服务器303和用户设备304。
其中，该边缘使能服务器302可以为应用的实例提供一些使能能力，可以更好的支持应用在MEC的部署情况。该边缘使能服务器302通过参考点3(edge-3)与应用实例服务器303连接，于是，该边缘使能服务器302可以通过该参考点3获取该应用实例服务器303中的应用的实例的信息，此时，该参考点3可以为前述图1C或图1D中的第四接口114，也可以为前述图1D中的第七接口117。
该边缘网络配置服务器301用于获取应用的实例的信息，以供该用户设备304使用。其中，该边缘网络配置服务器301通过参考点5(edge-5)与边缘使能服务器302连接，于是，该边缘网络配置服务器301可以获取该边缘使能服务器302中的应用的实例的信息，此时，该参考点5可以为前述图1A、图1C或图1D中的第一接口111，也可以为前述图1D中的第五接口115。该边缘网络配置服务器301通过参考点6(edge-6)与应用实例服务器303连接，于是，该边缘网络配置服务器301可以获取该应用实例服务器303中的应用的实例的信息，此时，该参考点6可以为前述图1C或图1D中的第三接口113，也可以为前述图1D中的第六接口116。此外，该边缘网络配置服务器301通过参考点4(edge-4)与用户设备304连接，于是，该边缘网络配置服务器301可以向该用户设备304发送该应用的实例的信息，此时，该参考点4可以为前述图1A、图1C或图1D中的第二接口112。
此外，前述边缘使能服务器302与应用实例服务器303均位于边缘网络中。该边缘网络EDN是中心云的对等概念，可以理解为是一个本地的数据中心，可以使用边缘网络接入标识DNAI来标识。边缘网络中可以部署多个本地边缘网络(local data network，local DN)。该边缘网络中可以存在多个边缘使能服务器302以及多个应用实例服务器303，具体此处不做限定。
该应用实例服务器303用于服务该应用的某一种实例或某几种实例。该应用实例服务器303对应的应用服务器也可以称为边缘应用(edge application)服务器、移动边缘计算应用(mobile edge computing application，MEC application)或多接入边缘计算应用(multi-access edge computing application，MEC application)服务器。
用户设备304可以是手机、电脑等移动设备，该用户设备304上可以安装有应用客户端(application client)和边缘使能客户端(edge enabler client，EEC)。应用客户端是边缘应用在用户侧的对等实体。边缘使能客户端EEC是边缘使能服务器EES在用户侧的对等实体。
此外，用户设备UE 304中的应用客户端和边缘网络中的应用实例服务器303可以进行应用数据传输(application data traffic),边缘使能客户端EEC和该边缘使能服务器302之间可以通过参考点1(edge-1)建立连接，该边缘使能服务器302还通过参考点2(edge-2)与3GPP网络连接。
图3A所示的架构可以应用于5G网络中。具体的，图3B示例性示出了适用于本申请实施例的一种5G网络架构示意图。如图3B所示，在5G网络架构中，终端设备311可以经接入网(access network，AN)312与核心网进行通信，终端设备可以指用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端等。图3B中为方便描述，只示例出1个终端设备，实际网络中，可能存在多个终端设备共存，在此不再赘述。
AN也可以称之为无线接入网(radio accessnetwork，RAN)，以下统称为AN，主要负责为终端设备311提供无线连接，保证终端设备311的上下行数据的可靠传输等。接入网实体AN 312可为5G系统中的gNB(generation Node B)，还可以是长期演进(long term evolution，LTE)系统中的演进型基站(evolutional node B，eNB或eNodeB)等。
会话管理功能(session management function，SMF)313，主要负责为终端设备311建立会话、管理会话等。可以根据终端设备311的位置信息为终端设备311选择合适的UPF 314。
用户面功能(user plane function，UPF)314，是终端设备311用户面的功能网元，主要功能包括分组路由和转发，用户面数据的服务质量(quality of service，QoS)处理等。5G系统中可以支持在一个协议数据单元(protocol data unit，PDU)会话的用户面路径上插入多个会话锚点UPF，以支持到本地数据网络(data network，DN)的连接，从而使得终端设备可以就近访问本地DN中的应用。具体的，终端设备与DN之间可以包括多个UPF，其中部分UPF可以作为上行分流器(uplink classifier，ULCL)或分支点(branching point，BP)；部分UPF可以作为PDU会话锚点(PDU session anchor，PSA)。
接入和移动性管理(access and mobility management function,AMF)315，主要功能包括无线接入网络控制平面的终结点，非接入信令的终结点，移动性管理，合法监听，接入授权或鉴权等。
策略控制功能(policy cntrol funtion，PCF)316，主要负责用户面传输路径的建立、释放和更改等功能。
鉴权服务器功能(authentication server function，AUSF)317，其主要功能包括用户鉴权等。
用户数据管理(user data management，UDM)318，主要负责管理用户的签约数据等。
数据网络(data network，DN)319可以是指为终端设备311提供服务的网络。
应用服务器(application server，AS)320，可以为终端设备中的应用(application)提供数据服务。
图3B中还示出了各个实体中的接口的可能实现方式，比如AN312和AMF315之间的N2接口，AN 312与UPF 314之间的N3接口等，在此不再一一赘述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例中部分场景以无线通信网络中NR网络的场景为例进行说明，应当指出的是，本申请实施例中的方案还可以应用于其他无线通信网络中，相应的名称也可以用其他无线通信网络中的对应功能的名称进行替代。
下面将以前述图3A所示的系统架构为基础，介绍当边缘网络配置服务器和边缘使能服务器之间的消息基于请求-响应机制时的流程，具体如图4所示，包括如下步骤：
401、应用实例服务器向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。
本实施例中，该应用实例服务器可以管理应用的一种或多种实例，因此，该应用实例服务器存储有该应用的实例的信息。例如，该应用的实例的标识信息和该应用的实例的IP地址。其中，该应用的实例的标识信息用于标识该应用的实例。该应用的实例的IP地址用于指示该实例在网络中的部署位置，可以用于应用客户端连接到该实例获取其应用业务。于是，该应用的实例服务器可以向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址，即该边缘使能服务器可以从该应用实例服务器接收应用的实例的标识信息和该应用的实例的IP地址。
具体地，边缘使能服务器从该应用实例服务器接收的应用的实例的标识信息和该应用的实例的IP地址可以携带于基于请求-响应(request-response)机制的消息中，例如，该边缘使能服务器向该应用实例服务器发送一个请求消息，该应用实例服务器向该边缘使能服务器回复一个响应消息，并且，在该响应消息中携带该应用的实例的标识信息和该应用的实例的IP地址。或者，可以携带于基于订阅-通知(subscribe-notification)机制的消息中，例如，该边缘使能服务器向该应用实例服务器发送一个订阅消息，该应用实例服务器向该边缘使能服务器回复一个或多个基于前述订阅消息的通知消息，并且，每个通知消息中均携带应用的实例的标识信息和该应用的实例的IP地址。
可选的，该应用实例服务器还可以向该边缘使能服务器发送指示该应用的实例的位置的信息。例如，该应用的实例的互联网协议IP地址、边缘网络的接入标识信息、该边缘使能服务器所在的边缘网络的IP地址或边缘使能服务器的IP地址等，具体此处不做限定。
还应理解的是，步骤401中的应用实例服务器可以为一个或多个，该边缘使能服务器也可以为一个或多个。当该应用实例服务器为多个且该边缘使能服务器为多个时，该应用实例服务器与该边缘使能服务器一一对应，或者，每个边缘使能服务器对应多个应用实例服务器，具体此处不做限定。
402、边缘网络配置服务器向边缘使能服务器发送第一请求。
本实施例中，当该边缘网络配置服务器存在获取应用的实例的信息的需求时，该边缘网络配置服务器可以向边缘使能服务器发送第一请求。其中，该第一请求用于请求应用的实例的信息。
应当理解的是，在步骤402中，该边缘网络配置服务器一般为边缘网络中的一个服务边缘使能服务器的服务器，该边缘使能服务器可以为一个或者多个，具体此处不做限定。
403、该边缘使能服务器向边缘网络配置服务器发送应用的实例的信息。
本实施例中，当该边缘使能服务器接收该边缘网络配置服务器发送的第一请求之后，该边缘使能服务器将向边缘网络配置服务器发送应用的实例的信息。其中，该应用的实例的信息包括前述步骤401中的应用的实例的标识信息和该应用的实例的IP地址，该应用的实例的信息还可以包括边缘网络的接入标识信息、边缘网络的IP地址或边缘使能服务器的IP地址。在一些实施方式中，该应用的实例的信息还包括边缘使能服务器的标识信息，或该应用的实例的服务范围信息。具体地，可以参阅前述步骤201a中的相关描述，具体此处不再赘述。
应当理解的是，前述边缘网络的接入标识信息、边缘网络的IP地址和边缘使能服务器的IP地址等信息可以由该边缘使能服务器从该应用实例服务器获取，也可以由该边缘使能服务器从该边缘使能服务器的本地数据库中获取，具体此处不做限定。
应当理解的是，在步骤403中，该应用的实例的信息可以指同一应用的不同的实例的信息，例如，前述图2对应的实施例中的第一实例的信息和第二实例的信息。在实际应用中，还可能包括该应用的其他的实例的信息，具体此处不做限定。
404、该边缘网络配置服务器保存该应用的实例的信息。
本实施例中，当该边缘网络配置服务器收到该边缘使能服务器发送的应用的实例的信息时，该边缘网络配置服务器将保存该应用的实例的信息。具体地，该边缘网络配置服务器每收到一次该应用的实例的信息，该边缘网络配置服务器将保存一次该应用的实例的信息，其中，每次保存的应用的实例的信息可能存在差异，具体此处不做限定。
可选的，当边缘使能服务器发送的应用的实例的信息中不包括UE的追踪区标识TAI,或者，该应用的实例的信息不包括小区ID或小区ID列表时，该边缘网络配置服务器还可以进一步解析DNAI/EDN IP以获取UE的追踪区标识TAI、小区ID或小区ID列表等，并保存该UE的追踪区标识TAI、小区ID或小区ID。具体地，该边缘网络配置服务器可以向3GPP网元发送DNAI，以获取该DNAI对应的追踪区标识TAI、小区ID或小区ID列表等信息。其中，该3GPP网元可以为统一数据存储库(unified data repository，UDR)网元或会话管理功能(session management function，SMF)网元，具体此处不做限定。当该边缘网络配置服务器可以向3GPP网元发送DNAI之后，该边缘网络配置服务器将在UDR或SMF检索该DNAI对应的追踪区标识TAI、小区ID或小区ID列表等信息，并向边缘网络配置服务器 发送追踪区标识TAI、小区ID或小区ID列表等信息。
该第一实例的服务范围信息可以为第一设备的追踪区标识(tracking area identity，TAI)，也可以为第一设备所在小区的标识信息，例如小区ID(cell ID)或小区列表(cell ID list)，还可以为其他用于标识该第一实例的服务用户的位置的信息，具体此处不做限定。
405、该边缘网络配置服务器向边缘使能服务器发送保存响应。
本实施例中，步骤405为可选的步骤。当该边缘网络配置服务器保存了该边缘使能服务器发送的应用的实例的信息之后，该边缘网络配置服务器可以向该边缘使能服务器发送保存响应，以通知该边缘使能服务器该边缘网络配置服务器已将该应用的实例的信息保存成功。可选的，该边缘网络配置服务器可以每保存一次该应用的实例的信息就向该边缘使能服务器发送一次保存响应。
406、用户设备UE向该边缘网络配置服务器发送应用的标识信息和UE的位置信息。
本实施例中，步骤406为可选的步骤。当用户设备UE需要获取该边缘网络配置服务器中的应用的实例的信息时，该UE将向该边缘网络配置服务器发送应用的标识信息和UE的位置信息，于是，该边缘网络配置服务器从UE接收该应用的标识信息和该UE的位置信息。其中，该应用的标识信息和该UE的位置信息的介绍可以参见前述步骤201a，具体此处不再赘述。
407、边缘网络配置服务器向用户设备UE发送第三实例的IP地址。
本实施例中，步骤407为可选的步骤，该边缘网络配置服务器可以向UE返回该UE欲获取的实例的IP地址。为便于介绍，称该UE欲获取的实例为第三实例，该第三实例为该应用的多个实例的中的一个，例如，该第三实例可以为前述图2对应的实施例中的第一实例或第二实例。此时，该第三实例由该应用的标识信息、该UE的位置信息、该应用的第一实例的信息和该应用的第二实例的信息确定。
可选的，该边缘网络配置服务器还将向该UE发送其他的关于该第三实例的信息。具体地，与前述步骤206类似，具体此处不再赘述。可选的，图4所示的方法还包括以下步骤：边缘网络配置服务器(edge configuration server，ECS)获取EES的区域信息，并获取用户设备的位置信息，然后ECS根据EES的区域信息和用户设备的位置信息确定目标EES。例如，该EES为ECS所管理的一个或多个EES。目标EES为上述EES中和用户设备的位置匹配的EES。由此，ECS通过获取到EES的区域信息以及用户设备的位置信息，可以为用户设备选择与其位置匹配或者距离用户设备最近的目标EES，也即选择该目标EES所在的EDN。当用户设备向EES发现应用实例时，可以确保用户设备访问的应用实例为与用户设备位置匹配或者距离距离用户设备最近的应用实例。从而提高了用户体验，降低传输时延。该步骤的实施方式可参考图13和图14的描述。
本实施例中，由于，管理应用的实例的信息的边缘网络配置服务器可以从边缘使能服务器接收应用的实例的信息，并将获取的应用实例的信息保存于该边缘网络配置服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题。此外，由于该边缘网络配置服务器与该边缘使能服务器之间的信令交互基于请求-响应机制，该边缘网络配置服务器在需要获取应用的实例的信息时向该边缘使能服务器发送第一请求，该边缘使能服务器也可以基 于该第一请求向该边缘网络配置服务器发送应用的实例的信息。因此，可以满足该边缘网络配置服务器获取应用的实例的需求，以进一步实现该边缘网络配置服务器保存该应用的实例的信息的功能。此外，该方法还使得该UE可以从该边缘网络配置服务器中获取到该应用的实例的信息，而无需从多个边缘使能服务器或其他服务器处获取该应用的实例的信息，进而可以节省该UE获取该应用的实例的信息的信令开销，进而减少接入应用的延迟。
下面将以前述图3A所示的系统架构为基础，介绍当边缘网络配置服务器和边缘使能服务器之间的消息基于订阅-通知机制时的流程，具体如图5所示，包括如下步骤：
501、边缘网络配置服务器向边缘使能服务器发送订阅请求。
本实施例中，当边缘网络配置服务器需要获取某一个或某几个应用的实例的信息之前，该边缘网络配置服务器可以先向该边缘使能服务器发送订阅请求，该订阅请求用于请求订阅该边缘使能服务器中的应用的实例的信息，以使得该边缘使能服务器中的应用的实例的信息更新时，该边缘使能服务器能主动通知该边缘网络配置服务器该应用的实例的信息。应当理解的是，本实施例中的更新，可以指该应用的实例的信息初次出现在该边缘使能服务器中；也可以指该边缘使能服务器中应用的实例的信息没有增减但发生了变更；还可以指该应用的实例的信息全部或部分从该边缘使能服务器中删除或失效。具体地，与前文中第二服务器中的应用的实例的信息发生更新的情况类似，具体此处不再赘述。
可选的，该订阅请求包括订阅条件，该订阅条件用于指示该应用的实例。具体地，该应用的实例可以为该应用的某一个实例或该应用的某几个实例。例如，该应用的实例可以为图2所对应的实施例中的第一实例和第二实例。可选的，该应用的实例还可以包括除了该第一实例和该第二实例之外的其他实例，具体此处不做限定。
应当理解的是，步骤501中的边缘使能服务器可以为一个，也可以为多个。因此，该边缘网络配置服务器可以向多个边缘使能服务器订阅多个不同的实例的信息。
502、边缘使能服务器向边缘网络配置服务器发送响应于该订阅请求的订阅响应。
本实施例中，步骤502为可选的步骤，订阅响应用于通知边缘网络配置服务器是否订阅成功。当该边缘网络配置服务器成功订阅该边缘使能服务器中的应用的实例的信息时，该边缘使能服务器将通过向该边缘网络配置服务器发送通知消息以通知该边缘网络配置服务器。应当理解的是，由于该边缘使能服务器可以为多个，因此，步骤502可以执行多次，即由不同的边缘使能服务器向该边缘网络配置服务器发送订阅响应。
503、应用实例服务器向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。
本实施例中，步骤503中的应用实例服务器可以为一个或多个，该边缘使能服务器也可以为一个或多个。当该应用实例服务器为多个且该边缘使能服务器为多个时，该应用实例服务器与该边缘使能服务器一一对应，或者，每个边缘使能服务器对应多个应用实例服务器，具体此处不做限定。
还应理解的是，步骤503与前述步骤501和步骤502无明确的时间先后顺序的限定。也就是说，步骤503可以在步骤501和步骤502之前执行；或者，步骤503可以在步骤501之前且步骤502之后执行；或者步骤503在步骤501和步骤502之后执行；或者，步骤503 与步骤501同时执行；或者，步骤503与步骤502同时执行。具体此处不做限定。
具体地，步骤503与前述步骤401类似，具体此处不再赘述。
504、该边缘使能服务器向边缘网络配置服务器发送应用的实例的信息。
本实施例中，当该边缘使能服务器接收到应用实例服务器发送的应用的实例的标识信息和该应用的实例的IP地址之后，该边缘使能服务器将向边缘网络配置服务器发送应用的实例的信息。其中，该应用的实例的信息包括前述步骤503中的应用的实例的标识信息和该应用的实例的IP地址，该应用的实例的信息还包括边缘网络的接入标识信息、或边缘网络的IP地址或边缘使能服务器的IP地址。在一些实施方式中，该应用的实例的信息还包括边缘使能服务器的标识信息，或该应用的实例的服务范围信息。具体地，可以参阅前述步骤201a中的相关描述，具体此处不再赘述。
应当理解的是，前述边缘网络的接入标识信息、边缘网络的IP地址和边缘使能服务器的IP地址等信息可以由该边缘使能服务器从该应用实例服务器获取，也可以由该边缘使能服务器从该边缘使能服务器的本地数据库中获取，具体此处不做限定。
应当理解的是，在步骤504中，该应用的实例的信息可以指同一应用的不同的实例的信息，例如，前述图2对应的实施例中的第一实例的信息和第二实例的信息。在实际应用中，还可能包括该应用的其他的实例的信息，具体此处不做限定。
505、该边缘网络配置服务器保存该应用的实例的信息。
506、该边缘网络配置服务器向边缘使能服务器发送保存响应。
507、用户设备UE向该边缘网络配置服务器发送应用的标识信息和用户设备UE的位置信息。
508、边缘网络配置服务器向用户设备UE发送第三实例的IP地址。
本实施例中，步骤505至步骤508与前述步骤404至步骤407类似，具体此处不再赘述。
本实施例中，由于，管理应用的实例的信息的边缘网络配置服务器可以从边缘使能服务器接收应用实例的信息，并将获取的应用实例的信息保存于该边缘网络配置服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题。此外，由于该边缘网络配置服务器与该边缘使能服务器之间的信令交互基于订阅-通知机制，当该边缘网络配置服务器向边缘使能服务器订阅了应用的某一个实例或该应用的某几个实例时，该边缘使能服务器便可在该应用的实例的信息更新时向该边缘网络配置服务器发送该应用的实例的信息。因此，可以满足该边缘网络配置服务器获取应用的实例的需求，以进一步实现该边缘网络配置服务器保存该应用的实例的信息的功能。此外，该方法还使得该UE可以从该边缘网络配置服务器中获取到该应用实例的信息，而无需从多个边缘使能服务器或其他服务器处获取该应用实例的信息，进而可以节省该UE获取该应用实例的信息的信令开销，进而减少接入应用的延迟。
本申请实施例所提出的获取信息的方法除了可以适用于前述图3A所示的系统，还可以与API通用架构(common application programming interface framework，common API framework，CAPIF)结合，通过复用API通用架构中的部分信令流程，以节省该边缘网络 配置服务器和该边缘使能服务器之间的信令构建。
下面先对该API通用架构进行介绍，具体如图6A所示，该API通用架构包括：
API通用架构核心功能(CAPIF core function，CCF)601、API管理功能(application programming interface management function，API management function，AMF)602、API发布功能(application programming interface publishing function，API publishing function，APF)603、API开放功能(application programming interface exposing function，API exposing function，AEF)604和API调用实体(application programming interface invoker，API invoker)6051/6052。
其中，API通用架构核心功能CCF 601、API管理功能AMF 602、API发布功能APF 603、API开放功能AEF 604和API调用实体6051位于公共陆地移动网络信任域(public land mobile network trust domain，PLMN trust domain)中。API调用实体6052位于公共陆地移动网络信任域之外。
其中，API通用架构核心功能CCF 601通过连接点3(CAPIF-3)与API开放功能AEF 604连接，API通用架构核心功能CCF 601通过连接点4(CAPIF-4)与API发布功能APF 603连接，API通用架构核心功能CCF 601通过连接点5(CAPIF-5)与API管理功能AMF 602连接。前述API开放功能AEF 604、API发布功能APF 603以及API开放功能AMF 602均属于同一API提供商域中。
此外，该API通用架构核心功能CCF 601通过连接点1(CAPIF-1)与API调用实体6051连接，该API调用实体6051通过连接点2(CAPIF-2)与API服务域中的服务APIs连接。对于位于公共陆地移动网络信任域之外的API调用实体6052，该API通用架构核心功能CCF 601通过连接点1e(CAPIF-1e)与API调用实体6052连接，该API调用实体6052通过连接点2e(CAPIF-2e)调用API服务域中的服务APIs。
具体地，图6A中的各个模块的功能如下：
API调用实体6051/6052：也被称为API调用者，指与公共陆地移动网络(public land mobile network，PLMN)运营商签定了服务协议的第三方应用。例如，端到端(machine to machine，M2M)应用、物联网(internet of things，IoT)应用、车联网(vehicle to everything，V2X)应用等，具体此处不做限定。应当理解的是，前述应用可以运行在终端设备中，也可以运行在网络设备中。此外，API调用实体6051/6052也可以是PLMN网络中的设备，例如，4G通信系统中的移动管理实体(mobility management entity，MME)，无线接入网络(radio access network，RAN)设备，策略与计费规则功能(policy and charging rules function，PCRF)网元等；也可以是5G通信系统中的接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、策略控制功能(policy control function，PCF)网元、应用功能(application function，AF)网元等。API调用实体6051/6052可以支持API调用实体的认证；可以支持和API通用架构核心功能CCF 601的相互鉴权；可以访问API已获取的授权；可以发现APIs；可以调用APIs。
API通用架构核心功能CCF 601：可以基于API调用实体的标识和其他信息认证API调用实体；可以发布、存储和支持API的发现；可以基于PLMN运营商的策略负责API的访问 控制；可以存储API调用的日志，并提供给授权实体查阅；可以支持API invoker的注册；还可以存储配置策略。
API管理功能AMF 602：用于提供对API的管理。具体地，可以审计从API通用架构核心功能CCF 601提供的API调用日志的审计；可以监控API通用架构核心功能CCF 601报告的事件；可以向API配置API提供者的策略；可以检测API的状态；可以注册API调用实体。
API发布功能APF 603：用于提供API发布的功能，以便API调用实体可以发现API。
API开放功能AEF 604：用于提供APIs以及API调用实体6051/6052调用API的入口。具体地，可以基于API调用实体6051/6052的标识和API通用架构核心功能CCF 601提供的其他信息认证API调用实体6051/6052；可以确认API通用架构核心功能CCF 601提供的授权；可以将API日志同步到API通用架构核心功能CCF 601上。
应当理解的是，前述图6A所示的系统架构还可以进一步扩展，以使得不同的API通用架构核心功能CCF之间可以互通。例如，当两个API通用架构核心功能CCF位于同一信任域时，前述图6A的系统架构可以扩展为图6B。当两个API通用架构核心功能CCF位于不同信任域时，前述图6A的系统架构可以扩展为图6C。其中，图6B和图6C中的单元或模块可以参见前文图6A对应的介绍，具体此处不再赘述。还应理解的是，在图6B中的API通用架构核心功能CCF1和API通用架构核心功能CCF2之间可以通过连接点6(CAPIF-6)进行交互，在图6C中的API通用架构核心功能CCF1和API通用架构核心功能CCF2之间还可以通过连接点6e(CAPIF-6e)进行交互。该连接点6或连接点6e可以支持一个API通用架构核心功能CCF向另一个API通用架构核心功能CCF发布服务API或发现服务API。还应理解的是，在实际应用中，可以将前述图6A进行进一步扩展，以适应不同场景的需求，具体此处不再赘述。
下面结合图6A所示的API通用架构图6B或图6C所示的扩展架构，当该获取信息的方法中的部分流程复用CAPIF发现(discover)机制时，如图7所示，该边缘网络配置服务器和边缘使能服务器将执行如下步骤：
本实施例中，当复用CAPIF发现机制时，该边缘网络配置服务器可以实现图6B或图6C中的API通用架构核心功能1的功能，该边缘使能服务器可以实现图6B或图6C中的API通用架构核心功能2的功能，该应用实例服务器可以实现图6B或图6C中的API服务域(即API提供商域)中的一个或多个功能模块的功能，例如，该应用实例服务器实现API发布功能。此时，边缘使能服务器和边缘网络配置服务器之间的接口包含连接点6或连接点6e的部分或全部接口功能，例如，前述图3A中的参考点5可以包含连接点6或连接点6e的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点6或连接点6e的部分或全部接口功能。
701、应用实例服务器向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。
本实施例中，由于，应用实例服务器可以实现图6B或图6C中的API服务域2中的一个或多个功能模块的功能，因此，该应用实例服务器可以通过不同的接口向边缘使能服务 器发送应用的实例的标识信息和该应用的实例的IP地址。例如，当该应用实例服务器实现API发布功能时，应用实例服务器通过连接点4向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。此时，边缘使能服务器和应用实例服务器之间的接口包含连接点4的部分或全部接口功能，例如，前述图3A中的参考点3可以包含连接点4的部分或全部接口功能；例如，前述图1C或图1D中的第四接口114可以包含连接点4的部分或全部接口功能；例如，前述图1D中的第七接口117可以包含连接点4的部分或全部接口功能。此外，当该应用实例服务器实现API开放功能时，应用实例服务器通过连接点3向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址；当该应用实例服务器实现API管理功能时，应用实例服务器通过连接点5向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址，具体此处不做限定。
702、边缘网络配置服务器向边缘使能服务器发送第一API发现请求。
本实施例中，边缘网络配置服务器通过连接点6或连接点6e向边缘使能服务器发送第一API发现请求(service API discover request)，该第一API发现请求用于请求发现应用的实例或者API。可选的，该第一API发现请求包括发现类型信息，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例，或，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例和API，该应用的实例可以为该应用的一种实例或该应用的多种实例，例如，该应用的实例可以为前述图2对应的实施例中的第一实例和第二实例。应当理解的是，当该边缘使能服务器接收该第一API发现请求之后，该边缘使能服务器可以通过该边缘使能服务器中所携带的发现类型信息，确定该边缘网络配置服务器需要发现的类型。可选的，该发现类型信息可以由阿拉伯数字或者字符串表示。例如，当该发现类型信息为“0”时，表示该第一API发现请求用于请求发现API；当该发现类型信息为“1”时，表示该第一API发现请求用于请求发现应用实例；当该发现类型信息为“2”时，表示该第一API发现请求用于请求发现应用实例和API。具体此处不做限定。
703、边缘使能服务器向边缘网络配置服务器发送第一API发现响应，该第一API发现响应中携带该应用的实例的信息。
本实施例中，当该边缘网络配置服务器收到该边缘使能服务器发送的第一API发现请求之后，该边缘网络配置服务器将通过连接点6或连接点6e向该边缘使能服务器发送第一API发现响应(service API discover response)。具体地，当该第一API发现请求用于请求发现应用的实例或该第一API发现请求中的发现类型信息用于指示该第一API发现请求用于请求该应用的实例时，该边缘网络配置服务器将向该边缘使能服务器发送第一API发现响应，该第一API发现响应中携带该应用的实例的信息。
其中，该应用的实例的信息可以包括前述步骤701中的应用的实例的标识信息和该应用的实例的IP地址，该应用的实例的信息还包括边缘网络的接入标识信息、边缘网络的IP地址或边缘使能服务器的IP地址。在一些实施方式中，该应用的实例的信息还包括边缘使能服务器的标识信息，或该应用的实例的服务范围信息。具体地，可以参阅前述步骤201a中的相关描述，具体此处不再赘述。
704、边缘网络配置服务器保存该应用的实例的信息。
本实施例中，该边缘网络配置服务器可以保存该边缘使能服务器发送的第一API发现 响应所携带的应用的实例的信息。由于，此时该边缘网络配置服务器可以实现图6B或图6A中的API通用架构核心功能CCF1的功能，因此，该API通用架构核心功能CCF1可以保存该应用的实例的信息。并且，该API通用架构核心功能CCF1与API调用实体通过连接点1或连接点1e连接，并且，UE可以实现API调用实体的功能。因此，该边缘网络配置服务器可以将该应用的实例的信息提供给该UE使用，即该API通用架构核心功能CCF1可以将该应用的实例的信息提供给该API调用实体使用。因此，该UE可以直接从该边缘网络配置服务器，即该UE可以直接从该API通用架构核心功能CCF1中获取应用的实例的信息，而无需通过遍历该边缘使能服务器(即API通用架构核心功能2)就可以获取该应用的实例的信息。进而可以节省该UE获取该应用的实例的信息的信令开销，进而减少接入应用的延迟。
705、边缘网络配置服务器向该边缘使能服务器发送保存响应。
本实施例中，步骤705为可选的步骤。该边缘网络配置服务器保存该应用的实例的信息之后，该边缘网络配置服务器向该边缘使能服务器发送保存响应，以通知该边缘使能服务器该应用的实例的信息保存成功。
706、UE向边缘网络配置服务器发送应用的标识信息和UE的位置信息。
本实施例中，步骤706为可选的步骤。当UE需要应用的实例的信息时，该UE向边缘网络配置服务器发送应用的标识信息和UE的位置信息，例如，当该UE实现图6B或图6C中的API调用实体1的功能时，该UE可以通过连接点1e向边缘网络配置服务器发送应用的标识信息和UE的位置信息。
707、边缘网络配置服务器向UE发送第三实例的IP地址。
本实施例中，步骤707为可选的步骤。该边缘网络配置服务器可以根据UE发送的应用的标识信息和UE的位置信息以及该UE的其他信息确定第三实例，并向该UE发送该第三实例的IP地址。
可选的，该边缘网络配置服务器还将向该UE发送其他的关于该第三实例的信息。例如，第一边缘网络的接入标识信息、边缘网络的IP地址、或边缘使能服务器的IP地址中的一项或者多项，具体此处不做限定。
具体地，可以参加前述步骤205中的相关描述，具体此处不再赘述。
本实施例中，由于，边缘网络配置服务器和边缘使能服务器之间可以复用CAPIF发现机制，因此，边缘网络配置服务器和边缘使能服务器均可以实现API通用架构核心功能，并通过连接点6实现从边缘使能服务器中的应用实例的信息发送至边缘网络配置服务器，并将获取的应用实例的信息保存于该边缘网络配置服务器中。因此，便于该边缘网络配置服务器向UE发送该应用实例的信息，因此，不仅解决了边缘网络中应用的实例的信息的保存问题，还复用了CAPIF中的信令，因此节省了信令开销。
下面结合图6A所示的API通用架构或图6B或图6C所示的扩展架构，当该获取信息的方法中的部分流程复用CAPIF发布(publish)机制时，如图8所示，该边缘网络配置服务器和边缘使能服务器将执行如下步骤：
本实施例中，当复用CAPIF发布机制时，该边缘网络配置服务器可以实现图6B或图 6C中的API通用架构核心功能1的功能，该边缘使能服务器可以实现图6B或图6C中的API通用架构核心功能2的功能，该应用实例服务器可以实现图6B或图6C中的API服务域2中的一个或多个功能模块的功能，例如，该应用实例服务器实现API发布功能。此时，边缘使能服务器和边缘网络配置服务器之间的接口包含连接点6或连接点6e的部分或全部接口功能，例如，前述图3A中的参考点5可以包含连接点6或连接点6e的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点6或连接点6e的部分或全部接口功能。
801、边缘网络配置服务器向边缘使能服务器发送订阅请求。
本实施例中，步骤801为可选的步骤。该边缘网络配置服务器可以向该边缘使能服务器发送订阅请求，该订阅请求用于请求订阅该应用的实例的信息，以使得当该边缘使能服务器中的应用的实例的信息更新时，该边缘网络配置服务器可以将该应用的实例的信息通知到该边缘使能服务器。应当理解的是，本实施例中的更新，可以指该应用的实例的信息初次出现在该边缘使能服务器中；也可以指该边缘使能服务器中应用的实例的信息没有增减但发生了变更；还可以指该应用的实例的信息全部或部分从该边缘使能服务器中删除或失效。具体地，与前文中第二服务器中的应用的实例的信息发生更新的情况类似，具体此处不再赘述。
可选的，该订阅请求包括订阅条件，该订阅条件用于指示该应用的实例，该应用的实例可以为该应用中的某一个实例或该应用中的某几个实例，例如，该应用的实例可以为前述图2对应的实施例中的第一实例和第二实例。
802、边缘使能服务器向边缘网络配置服务器发送响应于该订阅请求的订阅响应。
本实施例中，步骤802为可选的步骤。当该边缘使能服务器接收到该边缘网络配置服务器发送的订阅请求之后，该边缘使能服务器将向该边缘网络配置服务器发送订阅响应，该订阅响应可以用于通知该边缘网络配置服务器本次订阅是否成功。在另一种实施方式中，该边缘使能服务器在订阅成功之后才向该边缘网络配置服务器发送订阅响应，此时，该订阅响应用于指示通知该边缘网络配置服务器本次订阅成功。
803、应用实例服务器向边缘使能服务器发送第三API发布请求，该第三API发布请求携带应用的实例的标识信息和该应用的实例的IP地址。
本实施例中，该应用实例服务器可以实现图6B或图6C中的API服务域2中的一个或多个功能模块的功能，因此，该应用实例服务器可以通过不同的接口向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。例如，当该应用实例服务器实现API发布功能时，应用实例服务器通过连接点4向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。此时，边缘使能服务器和应用实例服务器之间的接口包含连接点4的部分或全部接口功能，例如，前述图3A中的参考点3可以包含连接点4的部分或全部接口功能；例如，前述图1C或图1D中的第四接口114可以包含连接点4的部分或全部接口功能；例如，前述图1D中的第七接口117可以包含连接点4的部分或全部接口功能。此外，当该应用实例服务器实现API开放功能时，应用实例服务器通过连接点3向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址；当该应用实例服务器实现API管理功能时，应用实例服务器通过连接点5向该边缘使能服务器发送应用的实例的 标识信息和该应用的实例的IP地址，具体此处不做限定。
本实施例中，以该应用实例服务器实现API发布功能为例进行介绍。此时，该应用实例服务器通过连接点4向边缘使能服务器发送第三API发布请求(service API publish request)，该第三API发布请求携带应用的实例的标识信息和该应用的实例的IP地址。具体地，应用的实例的标识信息和该应用的实例的IP地址与前文步骤701类似，具体此处不再赘述。
可选的，当该第三API发布请求用于发布API和应用的实例时，该第三API发布请求还可以携带API的信息，例如，API的名称、API的类型、API的版本号、API的通信类型、API的接口信息(IP地址和端口号)以及协议信息等。
804、边缘使能服务器向该应用实例服务器发送第三API发布响应。
本实施例中，步骤804为可选的步骤。
当该边缘使能服务器接收到该应用实例服务器发送的第三API发布请求之后，该边缘使能服务器可以向该应用实例服务器发送第三API发布响应(service API publish response)。可选的，该第三API发布响应可以指示该API发布是否成功。
805、边缘使能服务器向边缘网络配置服务器发送第一API发布请求，该第一API发布请求携带应用的实例的信息。
本实施例中，由于该边缘网络配置服务器可以实现图6B或图6C中的API通用架构核心功能1的功能，该边缘使能服务器可以实现图6B或图6C中的API通用架构核心功能2的功能，当前述API发布功能(应用实例服务器)向API通用架构核心功能2(边缘使能服务器)发布了API之后，该API通用架构核心功能2(边缘使能服务器)可以将该发布的API共享至API通用架构核心功能1(边缘网络配置服务器)。因此，该边缘使能服务器可以通过连接点6向边缘网络配置服务器发送第一API发布请求(interconnection service API publish request)，该第一API发布请求用于发布该API和/或该应用的实例。具体地，该第一API发布请求用于发布该应用的实例，或者，该第一API发布请求用于发布该API和该应用的实例。
当该第一API发布请求用于发布该应用的实例时，该第一API发布请求携带应用的实例的信息。可选的，该第一API发布请求还包括发布类型信息，该发布类型信息用于指示发布该应用的实例。
当该第一API发布请求用于发布该应用的实例和该API时，该第一API发布请求携带应用的实例的信息和API的信息。可选的，该第一API发布请求还包括发布类型信息，该发布类型信息用于指示发布该应用的实例和API。
其中，该应用的实例的信息可以包括前述步骤803中的应用的实例的标识信息和该应用的实例的IP地址，该应用的实例的信息还包括边缘网络的接入标识信息、或边缘网络的IP地址或边缘使能服务器的IP地址。在一些实施方式中，该应用的实例的信息还包括边缘使能服务器的标识信息，或该应用的实例的服务范围信息。具体地，可以参阅前述步骤201a中的相关描述，具体此处不再赘述。
806、边缘网络配置服务器保存该应用的实例的信息。
本实施例中，步骤806为可选的步骤。本实施例中，该边缘网络配置服务器可以保存 该边缘使能服务器发送的第一API发布请求所携带的应用的实例的信息。由于，此时该边缘网络配置服务器核心功能CCF1与API调用实体通过连接点1或连接点1e连接，并且，UE可以实现API调用实体的功能。因此，该边缘网络配置服务器可以将该应用的实例的信息提供给该UE使用，即该API通用架构核心功能CCF1可以将该应用的实例的信息提供给该API调用实体使用。
807、边缘网络配置服务器向边缘使能服务器发送第一API发布响应。
本实施例中，步骤807为可选的步骤。当该边缘网络配置服务器收到边缘使能服务器发送的第一API发布请求之后，该边缘网络配置服务器可以向边缘使能服务器发送第一API发布响应(interconnection service API publish response)。可选的，该第一API发布响应可以用作保存响应，以通知该边缘使能服务器该应用的实例的信息保存成功。
808、UE向边缘网络配置服务器发送应用的标识信息和UE的位置信息。
809、边缘网络配置服务器向UE发送第三实例的IP地址。
本实施例中，步骤808至步骤809与前述步骤706至步骤707类似，具体此处不再赘述。
此外，在另一些实施例中，前述图7或图8对应的实施例中的边缘网络配置服务器、边缘使能服务器和应用实例服务器可以采用如下方式复用CAPIF架构中的功能模块。
具体地，边缘网络配置服务器可以实现图6A中的API通用架构核心功能的功能，该边缘使能服务器可以实现图6A中的API服务域中的一个或多个功能模块的功能，此时，该边缘使能服务器和边缘网络配置服务器之间的接口可以为连接点3、连接点4或连接点5。例如，该边缘使能服务器实现API发布功能，此时，边缘使能服务器和边缘网络配置服务器之间的接口包含连接点4的部分或全部接口功能；例如，前述图3A中的参考点5可以包含连接点4的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点4的部分或全部接口功能。可选的，该应用实例服务器可以实现API调用实体的功能，并且，该应用实例服务器通过连接点1e与边缘网络配置服务器连接，该应用实例服务器通过连接点2e与边缘使能服务器连接。该应用实例服务器可以实现API调用实体的功能，此时，该应用实例服务器可以通过连接点1e与边缘网络配置服务器连接。
此外，还存在一些实施方式，该边缘网络配置服务器可以直接从该应用实例服务器获取该应用的实例的信息。此时，可以采用如下方式复用CAPIF架构中的功能模块。
具体地，边缘网络配置服务器可以实现图6A中的API通用架构核心功能的功能，该应用实例服务器可以实现图6A中的API服务域中的一个或多个功能模块的功能，此时，该应用实例服务器和边缘网络配置服务器之间的接口可以为连接点3、连接点4或连接点5。例如，该应用实例服务器实现API发布功能，此时，应用实例服务器和边缘网络配置服务器之间的接口包含连接点4的部分或全部接口功能；例如，前述图3A中的参考点5可以包含连接点4的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点4的部分或全部接口功能。
上述实施例中，分别从各个服务器或网元本身、以及从各个服务器或网元之间交互的角度对本申请实施例提供的方法的各方案进行了介绍。可以理解的是，前述服务器或设备，例如前述第一服务器、第二服务器、第三服务器、第一设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
如图9所示，本实施例提供了一种获取信息的装置90，该获取信息的装置90可以通过软件模块来实现相应的功能。此时，该获取信息的装置90可以为第一服务器中的芯片或片上系统。该获取信息的装置90可包括接收模块901和处理模块902，其中：
该接收模块901，用于从第二服务器接收应用的第一实例的信息，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置；该接收模块901，还用于从第三服务器接收该应用的第二实例的信息，该第二实例的信息包括该应用的标识信息和第二信息，该第二信息用于指示该第二实例的位置，该第一服务器为服务该第二服务器和该第三服务器的服务器。
此外，该处理模块902，用于保存该第一实例的信息和该第二实例的信息。
由此，本实施例中的获取信息的装置90可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该获取信息的装置90向其他设备(例如第一设备)发送该应用的实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该获取信息的装置90中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
在一种可选的实施方式中，该接收模块901还用于从第二服务器或第一网元接收该第二服务器的区域信息；该处理模块902还用于获取用户设备的位置信息；该处理模块902还用于根据该第二服务器的区域信息和该用户设备的位置信息确定目标服务器。
在另一种可选的实施方式中，第一网元为NEF网元、UDM网元、UDR网元、PCF网元、或NRF网元。
在另一种可选的实施方式中，该接收模块901还用于从EEC接收应用标识，该目标服务器服务于该应用标识对应的应用实例。
在另一种可选的实施方式中，该获取信息的装置90还包括：发送模块903，用于向该第二服务器和该第三服务器发送第一应用程序接口API发现请求，该第一API发现请求包括发现类型信息，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例，或，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例和API，该应用的实例包括该第一实例和该第二实例。在这样的实施方式中，提出该获取信息的装置90可以复用API通用架构CAPIF中的发现机制。获取信息的装置90不需要单独配置获取应用的实例的信息的请求，可以节省获取信息的装置90与其他获取信息的装置(例如，第二服务 器、第三服务器)之间的信令开销，进而可以减缓因增加信令造成的接入应用的延迟。
在另一种可选的实施方式中，该接收模块901，具体用于：从该第二服务器接收第一API发现响应，该第一API发现响应包括该第一实例的信息；从该第三服务器接收第二API发现响应，该第二API发现响应包括该第二实例的信息。在这样的实施方式中，不仅提出该获取信息的装置90可以复用API通用架构CAPIF中的发现机制，还提出将第一实例的信息携带于该第一API发现响应或该第二API发现响应中。因此，该获取信息的装置90可以利用现有的信令分别从其他获取信息的装置(例如，第二服务器、第三服务器)中接收该应用的实例的信息，该其他获取信息的装置(例如，第二服务器、第三服务器)不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
在另一种可选的实施方式中，该接收模块901，具体用于：从该第二服务器接收第一API发布请求，该第一API发布请求包括该应用的第一实例的信息，该第一API发布请求用于发布该API和/或该第一实例；从该第三服务器接收第二API发布请求，该第二API发布请求包括该应用的第二实例的信息，该第二API发布请求用于发布该API和/或该第二实例。在这样的实施方式中，提出获取信息的装置90可以复用API通用架构CAPIF中的发布机制，并且，还提出将第一实例的信息携带于该第一API发布请求中，或将第二实例的信息携带于该第二API发布请求中。因此，该获取信息的装置90可以利用现有的信令分别从其他获取信息的装置(例如，第二服务器、第三服务器)中接收该应用的实例的信息，其他获取信息的装置(例如，第二服务器、第三服务器)不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
在另一种可选的实施方式中，该接收模块901，还用于从第一设备接收该应用的标识信息和该第一设备的位置信息；该发送模块903，还用于向该第一设备发送第三实例的IP地址，该第三实例由该应用的标识信息、该第一设备的位置信息、该应用的第一实例的信息和该应用的第二实例的信息确定，该第三实例为该第一实例或该第二实例。在这样的实施方式中，提出该获取信息的装置90可以根据第一设备发送的应用的标识信息和该第一设备的位置信息确定从前述第一实例和第二实例中确定第三实例。在这样的实施方式中，当该第一设备需要获取该应用中的某一个实例时，该第一设备无需依次在其他获取信息的装置(例如，第二服务器、第三服务器)中查找该应用的实例的信息，而是可以直接从该获取信息的装置90获取该应用的实例的信息，因此，可以减少该第一设备获取该应用的实例的信息的信令流程，进而可以减缓因增加信令而造成的网络时延。此外，该获取信息的装置90还可以根据第一设备的需求为该第一设备选择出满足该第一设备的需求的应用的实例。因此，优化了该第一设备获取该应用的实例的信息的流程。
还存在一种可选的实施方式，该发送模块903，还用于：向该第一设备发送如下一项或多项：该第一边缘网络的接入标识信息、该第一边缘网络的IP地址、或该第一边缘使能服务器的IP地址；向该第一设备发送如下一项或多项：该第二边缘网络的接入标识信息、该第二边缘网络的IP地址、或该第二边缘使能服务器的IP地址。在这样的实施方式中，提出该获取信息的装置90除了向该第一设备发送该应用的实例的IP地址之外，该获取信息的装置90还向该第一设备发送边缘网络的接入标识信息、该边缘网络的IP地址、或该 边缘使能服务器的IP地址中的一项或多项。因此，增加了该获取信息的装置90提供给该第一设备的信息的多样性，以使得该获取信息的装置90发送给该第一设备的应用的实例的信息可以更好地满足该第一设备的需求。
还存在一种实施方式，该发送模块903，还用于向该第二服务器和该第三服务器发送订阅请求，该订阅请求用于请求订阅该应用的实例的信息。在这样的实施方式中，提出该获取信息的装置90可以基于订阅-通知机制，即该获取信息的装置90从该第二服务器或该第三服务器订阅该应用的实例的信息，则该当该第二服务器或该第三服务器中的应用的实例的信息更新时，该第二服务器或该第三服务器将向该获取信息的装置90发送该应用的实例的信息。因此，该获取信息的装置90仅需向该第二服务器或该第三服务器发送一次消息，即可接收来自该第二服务器或该第三服务器的应用的实例的信息。因此，可以节省该信令开销，进而可以减缓增加信令造成的接入应用的延迟。可选的，该订阅请求包括订阅条件，该订阅条件用于指示该应用的实例，该应用的实例包括该第一实例和该第二实例。
如图10所示，本实施例提供了另一种获取信息的装置100，该获取信息的装置100可以通过软件模块来实现相应的功能。此时，该获取信息的装置100可以为第二服务器中的芯片或片上系统。该获取信息的装置100可包括发送模块1001和处理模块1002，其中：
处理模块1002，用于获取应用的第一实例的信息，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置。
发送模块1001，用于向第一服务器发送该第一实例的信息，该第一服务器为服务该第二服务器的服务器。
由此，本实施例中的获取信息的装置100可以将获取的应用的第一实例的信息发送给该第一服务器，以使得该第一服务器可以及时保存该获取信息的装置100发送的第一实例的信息。因此，有利于该第一服务器保存该边缘网络中应用的实例的信息，便于该第一服务器向其他设备(例如第一设备)发送该应用的实例的信息。此外，还可以使其他设备(例如第一设备)无需从该获取信息的装置100中获取该应用的实例的信息，而是可以直接从该第一服务器中获取该应用的实例的信息，因此，可以节省该第一服务器获取该应用的实例的信息的流程。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询多个获取信息的装置100获取应用的实例的信息，可以节省信令开销，减缓业务时延。
在一种可选的实施方式中，该发送模块1001还用于向该第一服务器发送第二服务器的区域信息。
在一种可选的实施方式中，该获取信息的装置100还包括：
接收模块1003，用于从该应用的第一实例服务器接收该第一实例的标识信息和该第一实例的IP地址。该处理模块1002，还用于确定该第一信息。在这样的实施方式中，明确了该获取信息的装置100获取该应用的第一实例的信息的方式，该第一实例的信息中的第一实例的标识信息和该第一实例的IP地址可以由该获取信息的装置100直接从该应用的第一实例服务器中获取，然后，该获取信息的装置100再确定该第一信息。在这样的实施方式中，该第一实例的信息是该获取信息的装置100从不同的服务器获取的。因此，获取信 息的装置100可以保证该第一实例的信息的完整性。
在另一种可选的实施方式中，该获取信息的装置100还包括：该接收模块，用于从该应用的第一实例服务器接收该第一实例的信息。在这样的实施方式中，提出该获取信息的装置100可以直接从该应用的第一实例服务器获取该第一实例的信息，即该获取信息的装置100可以直接从该第一实例服务器中获取该第一实例的标识信息、该第一实例的IP地址和该第一信息。因此，可以简化该获取信息的装置100获取该第一实例的信息的流程。
在另一种可选的实施方式中，该接收模块，还用于从该第一服务器接收第一应用程序接口API发现请求，该第一API发现请求包括发现类型信息，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例，或，该发现类型信息用于指示该第一API发现请求用于请求该应用的实例和API，该应用的实例包括该第一实例。在这样的实施方式中，提出获取信息的装置100可以复用API通用架构CAPIF中的发现机制。具体地，该第一服务器可以通过向获取信息的装置100发送第一API发现请求，以触发该获取信息的装置100向该第一服务器发送应用的第一实例的信息。因此，该第一服务器不需要单独配置获取应用的实例的信息的请求，可以节省信令开销，进而可以减缓因增加信令造成的接入应用的延迟。
在另一种可选的实施方式中，该发送模块1001，具体用于向第一服务器发送第一API发现响应，该第一API发现响应包括该第一实例的信息。在这样的实施方式中，不仅提出该获取信息的装置100可以复用API通用架构CAPIF中的发现机制，还提出将第一实例的信息携带于该第一API发现响应中。因此，该第一服务器可以利用现有的信令从该获取信息的装置100中接收该应用的实例的信息，该获取信息的装置100不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
在另一种可选的实施方式中，该发送模块1001，具体用于向该第一服务器发送第一API发布请求，该第一API发布请求包括该应用的第一实例的信息，该第一API发布请求用于发布该API和/或该第一实例。在这样的实施方式中，提出该获取信息的装置100可以复用API通用架构CAPIF中的发布机制，并且，还提出将第一实例的信息携带于该第一API发布请求中。因此，该第一服务器可以利用现有的信令分别从该获取信息的装置100中接收该应用的实例的信息，该获取信息的装置100不需要单独配置发送该应用的实例的信息的消息。因此，可以节省信令开销，进而可以减缓增加信令造成的接入应用的延迟。
还存在一种实施方式，该处理模块1002，具体用于从应用的第一实例服务器接收第三API发布请求，该第三API发布请求包括该第一实例的标识信息和该第一实例的IP地址，该第三API发布请求用于发布API和/或该第一实例。在这样的实施方式中，提出该第一API发布请求和该第二发布请求还包括发布类型信息，该发布类型信息用于指示发布的内容的类型。因此，该第一服务器可以根据该发布类型信息确定该第一API发布请求所携带的信息中是否包括该应用的实例的信息。
还存在一种实施方式，该接收模块1003，还用于从该第一服务器接收订阅请求，该订阅请求用于请求订阅该应用的实例的信息。在这样的实施方式中，提出该获取信息的装置100可以基于订阅-通知机制，即该获取信息的装置100从该第一服务器接收订阅请求，则 当该获取信息的装置100中的应用的实例的信息更新时，该获取信息的装置100将向该第一服务器发送该应用的实例的信息。因此，该第一服务器仅需向该获取信息的装置100发送一次消息，即可接收来自该获取信息的装置100的应用的实例的信息。因此，可以节省该信令开销，进而可以减缓增加信令造成的接入应用的延迟。可选的，该订阅请求包括订阅条件，该订阅条件用于指示该应用的实例，该应用的实例包括该第一实例和该第二实例。
如图11所示，本实施例提供了一种获取信息的装置110的结构示意图。该获取信息的装置110可以为前述图2或图13至图15对应的实施例中的第一服务器，也可以为图4至图5或图7至图8或后文图13至图17对应的实施例中的边缘网络配置服务器，也可以为该第一服务器或边缘网络配置服务器上的芯片或片上系统。
该获取信息的装置110包括处理器1101和存储器1102。存储器1102用于存储程序，处理器1101用于执行存储器1102中的程序，以实现本申请各方法实施例中第一服务器的功能，例如，该处理器1101可以用于保存该第一实例的信息和该第二实例的信息。
具体地，处理器1101可以包括一个或一个以上的处理器，存储器1102可以包括一个或一个以上的存储介质(例如一个或一个以上海量存储设备)。该处理器1101可以用于对服务器协议以及数据进行处理，以及对整个服务器进行控制，执行软件程序，处理软件程序的数据，例如用于支持该获取信息的装置110执行前述实施例中所描述的动作。可选的，该获取信息的装置110可以包括基带处理器和中央处理器，或者，集成基带处理器和中央处理器的功能。本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，获取信息的装置110可以包括多个基带处理器以适应不同的网络制式，获取信息的装置110可以包括多个中央处理器以增强其处理能力，获取信息的装置110的各个部件可以通过各种总线连接。前述基带处理器也可以表述为基带处理电路或者基带处理芯片。前述中央处理器也可以表述为中央处理电路或者中央处理芯片。对服务器协议以及数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储器中，由处理器执行软件程序以实现基带处理功能。
本实施例中，该存储器1102主要用于存储软件程序和数据。存储器1102可以是独立存在，与处理器1101相连。可选的，该存储器1102可以和该处理器1101集成于一体，例如集成于一个或多个芯片之内。其中，该存储器1102能够存储执行本申请实施例的技术方案的程序代码，并由处理器1101来控制执行，被执行的各类计算机程序代码也可被视为是处理器1101的驱动程序。应当理解的是，本实施例中的图11仅示出了一个存储器和一个处理器，但是，在实际应用中，该通信设备110可以存在多个处理器或多个存储器，具体此处不做限定。此外，该存储器1102也可以称为存储介质或者存储设备等。该存储器1102可以为与处理器处于同一芯片上的存储元件，即片内存储元件，或者为独立的存储元件，本申请实施例对此不做限定。
此外，该获取信息的装置110还包括输入/输出设备1103，该输入输出设备1103可以用于获取信息的装置110与其它设备进行通信。例如，从第二服务器接收应用的第一实例的信息，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置。该输入/输出设备1103，还用于从第三服务器接收该应用的第二实例的信 息，该第二实例的信息包括该应用的标识信息和第二信息，该第二信息用于指示该第二实例的位置，该第一服务器为服务该第二服务器和该第三服务器的服务器。
可选的，该输入/输出设备1103可以包含用于与其他设备进行通信的接口。例如，前述图1A或图1C或图1D中的第一接口111、第二接口112等；前述图3A中的参考点5或参考点4等。
可选的，该获取信息的装置110还可以包括一个或一个以上电源1104，和/或，一个或一个以上操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM等。
还应理解的是，上述图2、图4至图5、图7至图8以及图13至图17所对应的方法实施例中，该第一服务器或边缘网络配置服务器所执行的步骤均可以基于该图11所示的获取信息的装置110结构。
由此，本实施例中的获取信息的装置110可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该获取信息的装置90向其他设备(例如第一设备)发送该应用的实例的信息。
如图12所示，本实施例提供了另一种获取信息的装置120的结构示意图。该获取信息的装置120可以为前述图2对应的实施例中的第二服务器，也可以为图4至图5或图7至图8以及图13至图17对应的实施例中的边缘使能服务器，也可以为该第二服务器或边缘使能服务器上的芯片或片上系统。
该获取信息的装置120包括处理器1201和存储器1202。存储器1202用于存储程序，处理器1201用于执行存储器1202中的程序，以实现本申请各方法实施例中第二服务器的功能，例如，该处理器1201可以用于获取应用的第一实例的信息。
具体地，处理器1201可以包括一个或一个以上的处理器，存储器1202可以包括一个或一个以上的存储介质(例如一个或一个以上海量存储设备)。该处理器1201和该存储器1202与前述图11对应的实施例中所介绍的处理器1101和该存储器1102类似，具体此处不再赘述。
此外，该获取信息的装置120还包括输入/输出设备1203，该输入输出设备1203可以用于获取信息的装置120与其它设备进行通信。例如，第一服务器发送所述第一实例的信息，所述第一服务器为服务所述第二服务器的服务器。
可选的，该输入/输出设备1203可以包含用于与其他设备进行通信的接口。例如，前述图1A或图1C或图1D中的第一接口111；前述图1C或图1D中的第四接口114；前述图1D中的第七接口117；前述图3A中的参考点1、参考点2、参考点3或参考点5等。
可选的，该获取信息的装置120还可以包括一个或一个以上电源1204，和/或，一个或一个以上操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM等。
还应理解的是，上述图2、图4至图5、图7至图8以及图13至图17所对应的方法实施例中，该第二服务器或边缘使能服务器所执行的步骤均可以基于该图12所示的获取信 息的装置120结构。
由此，本实施例中的获取信息的装置120可以将获取的应用的第一实例的信息发送给该第一服务器，以使得该第一服务器可以及时保存该获取信息的装置120发送的第一实例的信息。因此，有利于该第一服务器保存该边缘网络中应用的实例的信息，便于该第一服务器向其他设备(例如第一设备)发送该应用的实例的信息。此外，还可以使其他设备(例如第一设备)无需从该获取信息的装置120中获取该应用的实例的信息，而是可以直接从该第一服务器中获取该应用的实例的信息，因此，可以节省该第一服务器获取该应用的实例的信息的流程。
还应理解的是，上述图2、图4至图5、图7至图8以及图13至图17所对应的方法实施例中的第三服务器与前述第二服务器所实现的功能类似，该第三服务器所执行的步骤也可以基于该图12所示的获取信息的装置120结构。
如图13所示，为本申请提供的获取信息的方法的流程图。图13可以应用于EES中已经预配置了EES和EES对应的区域信息的场景。该方法包括以下步骤：
1301、第三边缘使能服务器(EES)向边缘网络配置服务器(edge configuration server，ECS)发送第三EES的标识信息和区域信息。相应的，边缘网络配置服务器从第三边缘使能服务器接收第三EES的标识信息和区域信息。
其中，该第三EES可以为一个EES或者多个EES。当第三EES为多个EES时，第三EES的区域信息表示每个EES对应该每个EES各自的区域信息，多个EES各自的区域信息可以相同或者不同。
其中，第三EES的标识信息用于标识第三EES。例如，该第三EES的标识信息可以为如下一种或多种：第三EES的ID、第三EES的IP地址、第三EES的URL或第三EES的FQDN。当第三EES为多个EES时，第三EES的标识信息为一个EES标识列表，每个EES对应列表中的一个EES标识。
其中，第三EES的区域信息用于表示可以连接到第三EES的网络拓扑区域或物理区域信息或网络拓扑接入地址。例如，第三EES的区域信息又可以称为第三EES的网络拓扑区域信息。该第三EES的区域信息可以包括如下一种或多种：一个或多个UPF网元的标识或者IP地址信息、一个或多个DNAI、局域数据网(local area data network，LADN)的部分或全部服务区域信息、或LADN的标识。
例如，第三EES通过请求消息向ECS发送第三EES的标识信息和区域信息。其中，该第三EES的区域信息可以作为第三EES的属性信息发送给ECS。可选的，该请求消息中还包括第三EES的接入地址信息，如第三EES的IP地址或URL。例如，该请求消息可以为注册请求消息、注册更新请求消息、或者其他EES向ECS发送信令的消息。
可选的，第三EES仅向ECS发送一次该第三EES对应的区域信息。也就是说，如果第三EES向ECS发送多次注册请求消息、注册的更新请求消息、或者其他EES向ECS发送信令的消息，第三EES通过其中的一条消息向ECS发送第三EES的区域信息。例如，第三EES通过第一条注册请求消息向ECS发送第三EES的区域信息。
1302、ECS保存第三EES的标识信息和区域信息。
步骤1302为可选步骤。
其中，当第三EES的区域信息为LADN的服务区域信息时，ECS向网络管理服务器、OSS网元或网元(network function，NF)请求该LADN的服务区域信息。ECS保存该第三EES的标识信息和该LADN的服务区域信息。例如，当第三EES的区域信息为一个或多个DNAI时，ECS中保存第三EES的标识信息和区域信息的形式如表1所示。在表1中，第三EES包括2个，其标识信息分别为EES ID#1和EES ID#2。其中，EES ID#1对应的第三EES的区域信息为DNAI#1和DNAI#2；EES ID#2对应的第三EES的区域信息为DNAI#3。可选的，第三EES的区域信息作为第三EES属性信息保存。第三EES属性信息还包括第三EES的接入地址。例如，EES ID#1对应的第三EES的接入地址为IP#1；EES ID#1对应的第三EES的接入地址为IP#2。
表1
Figure PCTCN2020127921-appb-000001
1303、ECS向第三EES发送响应消息。相应的，第三EES从ECS接收响应消息。
步骤1303为可选步骤。
例如，该响应消息可以是EES注册响应消息、EES注册更新响应消息、或者其他EES向ECS发送的信令的响应消息。
1304、第三EES向ECS发送注册/更新请求。相应的，ECS从第三EES接收注册/更新请求。
步骤1304为可选步骤。
例如，该注册/更新请求中还包括应用标识FQDN和第三EES的标识信息。该请求消息用于指示第三EES上注册了该FQDN所标识的应用。
1305、ECS保存第三EES的标识信息、区域信息和FQDN的关系。
步骤1305为可选步骤。
例如，可以将第三EES标识和第三EES的区域信息，与步骤1304中的收到的应用标识和第三EES标识分别保存，通过第三EES标识关联。例如，第三EES标识和第三EES的区域信息的保存形式如表1所示，应用标识和第三EES标识的保存形式如表2所示。在表2中，应用标识FQDN#1对应的应用所注册的第三EES的标识为EES ID#1和EES ID#2；应用标识FQDN#2对应的应用所注册的第三EES的标识为EES ID#1。
表2
应用标识 所注册的第三EES的标识
FQDN#1 EES ID#1，EES ID#2
FQDN#2 EES ID#1
或者，也可以将第三EES标识、第三EES的区域信息与步骤1304中的收到的应用标识一起保存，例如表3或表4所示。
在表3中，第三EES包括2个，其标识信息分别为EES ID#1和EES ID#2。其中，EES ID#1对应的第三EES的区域信息为DNAI#1和DNAI#2，对应的第三EES上注册的应用标识为FQDN#1和FQDN#2；EES ID#2对应的第三EES的区域信息为DNAI#3，对应的第三EES上注册的应用标识为FQDN#1。可选的，第三EES的区域信息以及注册的应用标识作为第三EES属性信息保存。第三EES属性信息还包括第三EES的接入地址。例如，EES ID#1对应的第三EES的接入地址为IP#1；EES ID#2对应的第三EES的接入地址为IP#2。
表3
Figure PCTCN2020127921-appb-000002
在表4中，应用标识为FQDN#1的第三EES有两个，其标识信息分别为EES ID#1和EES ID#2。其中，EES ID#1对应的第三EES的区域信息为DNAI#1和DNAI#2，EES ID#2对应的第三EES的区域信息为DNAI#3；EES ID#2对应的第三EES的区域信息为DNAI#3。应用标识为FQDN#2的第三EES有一个，其标识信息为EES ID#1，EES ID#1对应的第三EES的区域信息为DNAI#1和DNAI#2。可选的，表4中还包括第三EES的接入地址。例如，EES ID#1对应的第三EES的接入地址为IP#1；EES ID#2对应的第三EES的接入地址为IP#2。
表4
Figure PCTCN2020127921-appb-000003
1306、ECS向第三EES发送注册/更新响应消息。相应的，第三EES从ECS接收注册/更新响应消息。
步骤1306为可选步骤。
例如，注册响应消息可以用于指示注册成功或者失败。或者，更新响应消息可以用于指示更新成功或者失败。
1307、EEC向ECS发送服务配置请求。相应的，ECS从EEC接收服务配置请求。
步骤1307为可选步骤。
例如，服务配置请求中包括以下任意一项或多项：用户设备标识、EEC标识信息、或应用标识FQDN。其中，用户设备标识为EEC所在的用户设备标识，EEC标识用于标识EEC。可选地，服务配置请求中还包括EEC所在用户设备的位置信息。
1308、ECS获取用户设备的位置信息，确定目标EES。
其中，目标EES为第三EES中的一个或多个EES。
例如，用户设备的位置信息可以包括以下一项或多项：小区标识(cell ID)、TAI、DNAI(s)、用户设备的锚点UPF网元的标识或IP地址、或其他可以表示UE在网络中的网络拓扑位置或地理位置的信息。
例如，ECS可以从步骤1307的服务配置请求中获取用户设备的位置信息。或者，ECS可以从网络侧获取用户设备的位置信息。
例如，ECS根据第三EES的区域信息和用户设备的位置信息确定目标EES。该目标EES的区域信息与用户设备的位置信息匹配。例如，ECS可以通过以下方式中的任一种方式根据第三EES的区域信息和用户设备的位置信息确定目标EES：方式一、ECS确定用户设备的位置信息TAI/Cell ID/DNAI(s)是目标EES的区域信息的一个子集；方式二、ECS确定用户设备的位置位于目标EES的区域中；方式三、ECS确定用户设备的位置与该EES的区域的边缘或者中心的物理位置最近。
可选的，若在步骤1304中包括应用标识FQDN，则ECS根据第三EES的区域信息、用户设备的位置信息以及应用标识确定目标EES。该目标EES可以提供EEC所请求的FQDN标识的应用。如果存在多个满足的EES，则ECS可以根据用户设备与EES的距离(例如用户设备位置到EES对应的网络拓扑区域边界的网络拓扑距离或物理距离)的远近或其他参数确定唯一一个EES。或者，ECS确定多个目标EES，并对每个EES标记优先级。
1309、ECS向用户设备发送目标EES的信息。相应的，用户设备从ECS接收目标EES的信息。
例如，目标EES的信息为目标EES的接入信息。例如，目标EES的接入信息为IP地址或URL。可选的，该目标EES的信息还包括目标EES的DNAI。
例如，ECS通过服务配置响应向第三EES发送目标EES的信息。服务配置响应中还包括目标EES对应的FQDN。
通过图13所示的方法，ECS可以根据EES的区域信息和用户设备的位置信息确定目标EES，由此，ECS通过获取到EES的区域信息以及用户设备的位置信息，可以为用户设备选择与其位置匹配或者距离用户设备最近的目标EES，也即选择该目标EES所在的EDN。当用户设备向EES发现应用实例时，可以确保用户设备访问的应用实例为与用户设备位置匹配 或者距离用户设备最近的应用实例。此外，ECS在和一个或多个第三EES的交互中获取到该第三EES的区域信息，无需引入额外的信令，简化了系统实现。从而提高了用户体验，降低传输时延。
如图14所示，为本申请提供的获取信息的方法的流程图。图14可以应用于第一网元已经获取了第四EES和第四EES对应的区域信息，且第四EES已经在ECS中注册过的场景。其中，第一网元可以通过预配置的方式或者从第四EES接收的方式获取第四EES和第四EES对应的区域信息。图14的方法可参考图13的描述，该方法包括以下步骤：
1401、ECS向第一网元发送第四EES的标识信息。相应的，第一网元从ECS接收第四EES的标识信息。
其中，该第四EES可以为一个EES或者多个EES。
例如，第四EES的标识信息的描述可参考图13的步骤1301中第三EES的标识信息的描述，此次不再赘述。
其中，第一网元可以为网络能力开放功能(network exposure function，NEF)网元、统一数据管理(unified data management，UDM)网元、UDR网元、PCF网元、或网络存储功能(network repository function，NRF)网元。
例如，当第四EES的数量为多个时，ECS通过第四EES的标识列表的形式向第一网元发送第四EES的标识信息。
例如，ECS通过EES信息请求消息向第一网元发送第四EES的标识信息，该EES信息请求消息用于请求第四EES的区域信息。
1402、第一网元向ECS发送第四EES的区域信息。相应的，ECS从第一网元接收第四EES的区域信息。
例如，第四EES的区域信息的描述可参考图13的步骤1301中第三EES的区域信息的描述，此次不再赘述。
1402、ECS保存第四EES的标识信息和区域信息。
步骤1402为可选步骤。
例如，步骤1402可参考图13的步骤1302中ECS保存第三EES的标识信息和区域信息的描述，此次不再赘述。
1404、第一网元向ECS发送注册/更新请求。相应的，ECS从第一网元接收注册/更新请求。
步骤1404为可选步骤。
例如，该注册/更新请求中还包括应用标识FQDN和第四EES的标识信息。该请求消息用于指示第四EES上注册了该FQDN所标识的应用。
1405、ECS保存第四EES的标识信息、区域信息和FQDN的关系。
步骤1405为可选步骤。
例如，步骤1405可参考图13的步骤1305中ECS保存第四EES的标识信息、区域信息和FQDN的关系的描述，此次不再赘述。
1406、ECS向第一网元发送注册/更新响应消息。相应的，第一网元从ECS接收注册/ 更新响应消息。
步骤1406为可选步骤。
例如，注册响应消息可以用于指示注册成功或者失败。或者，更新响应消息可以用于指示更新成功或者失败。
图14所示的方法还包括步骤1407-1409。其中，步骤1407为可选步骤。例如，步骤1407-1409可参考图13的步骤1307-1309的描述，此次不再赘述。
通过图14所示的方法，ECS可以根据EES的区域信息和用户设备的位置信息确定目标EES，由此ECS通过获取到EES的区域信息以及用户设备的位置信息，可以为用户设备选择与其位置匹配或者距离用户设备最近的目标EES，也即选择该目标EES所在的EDN。当用户设备向EES发现应用实例时，可以确保用户设备访问的应用实例为与用户设备位置匹配或者距离用户设备最近的应用实例。进一步，通过从第一网元获取多个第四EES的位置信息，可以一次获取到多个甚至所有的第四EES的位置信息，提高了系统的性能的效率。从而提高了用户体验，降低传输时延。
如图15所示，为本申请提供的另一种获取信息的方法，该方法涉及用户设备、第一服务器和第四服务器。具体地，该方法包括以下步骤：
1501、第一服务器向用户设备发送第四服务器的区域信息。相应的，用户设备从第一服务器接收第四服务器的区域信息。
其中，该第一服务器为服务该第四服务器的服务器。该第四服务器是与用户设备所需的应用相关的服务器。例如，用户设备需要获得某个应用的服务，那么，该第四服务为能够为该用户设备提供该应用服务的服务器，或者，该第四服务器能够为该用户设备选择一个提供前述应用服务的服务器。其中，第一服务器为服务该第四服务器的服务器，可以理解为第四服务器注册到第一服务器，第四服务器可以使用第一服务器提供的服务化接口，如注册服务、注册更新服务以及订阅服务等。
在一种可选的实施方式中，前述第一服务器为边缘配置服务器(edge configuration server，ECS)，前述该第四服务器为边缘使能服务器(edge enabler server，EES)。此时，该第四服务器能够为该用户设备选择一个提供前述应用服务的服务器。也就是说，前述ECS能够将用户设备提供的关于应用的信息(例如，应用标识、用户设备的位置信息等信息)作为发现过滤条件，以使得能够为用户设备选择EES。然后，再由该EES基于用户设备提供的应用的信息等过滤条件选择能够提供前述应用服务的服务器(即应用实例，也被称为边缘应用服务器(edge application server，EAS))。
在这种实现方式中，前述第四服务器的区域信息为EES所关联的数据网络的接入标识符(data network access identifier，DNAI)。还应当注意的是，前述第四服务器可以是一个服务器，也可以是多个服务器。当前述第四服务器为一个服务器时，前述第四服务器的区域信息为一个EES关联的DNAI。当前述第四服务器为多个服务器时，前述第四服务器的区域信息为包含多个EES DNAI。例如，前述多个EES DNAI可以是多个EES关联的DNAI列表，即该区域信息为包含多个EES DNAI的列表，每个DNAI与不同的EES关联。
其中，EES关联的DNAI，可以理解为，能够指示该EES提供服务的区域的DNAI；或者， 该EES与其他服务器进行数据交互时，该EES所携带的DNAI。
在另一种可选的实施方式中，前述第一服务器为边缘使能服务器EES，前述第四服务器为注册到该EES的应用实例(也被称为边缘应用服务器EAS)。此时，该第四服务为能够为该用户设备提供该应用服务的服务器。也就是说，前述EES能够基于用户设备提供的关于应用的信息(例如，应用标识，边缘使能客户端EEC标识等)为用户设备选择能够提供前述应用服务的服务器(即应用实例)。
其中，EAS关联的DNAI，可以理解为，能够指示该EAS提供服务的区域的DNAI；或者，该EES与其他服务器进行数据交互时，该EAS所携带的DNAI。
在这种实现方式中，前述第四服务器的区域信息为EAS关联的DNAI。还应当注意的是，前述第四服务器可以是一个服务器，也可以是多个服务器。当前述第四服务器为一个服务器时，前述第四服务器的区域信息为一个EAS关联的DNAI。当前述第四服务器为多个服务器时，前述第四服务器的区域信息包含多个EAS DNAI，例如，为包括多个EAS DNAI的列表，即该区域信息为包含多个EAS DNAI的列表，每个DNAI与不同的EAS关联。
可选的，在步骤1501之前，该第一服务器可以基于用户的信息和/或应用的信息确定前述第四服务器。其中，该用户的信息可以是用户的位置，例如，追踪区标识(tracking area identity，TAI)、小区ID(cell ID)或小区列表(cell ID list)、经纬度或行政区域信息等，具体此处不做限定。其中，应用的信息可以应用的标识、应用客户端的配置文件等，还可以为对于EAS的应用需求(如带宽、存储)等。可选的，该第一服务器在确定第四服务器的过程中还可能参考了用户的标识信息，该用户的标识信息可以是用户ID，用户设备中的边缘使能客户端EEC的标识以及用户设备的标识等。
1502、用户设备获取第一区域信息。
应当注意的是，步骤1502与前述步骤1501也可以没有明确的时间先后顺序的限定。也就是说，一般地，该用户设备可以先从第一服务器接收到第四服务器的区域信息，再获取前述第一区域信息；但该用户设备也可以先获取前述第一区域信息，再从第一服务器接收到第四服务器的区域信息，具体此处不做限定。
其中，该第一区域信息用于指示该用户设备所在的区域。可选的，该第一区域信息可以是用户设备当前所关联的DNAI。其中，用户设备当前所关联的DNAI可以理解为用户设备当前所在位置对应的DNAI，或者，用户设备与服务器(例如，EES或ECS)进行数据交互时，该用户设备用于表明当前位置的DNAI。
例如，第一区域信息为该用户设备访问第四服务器的会话所关联的DNAI，该DNAI可以与该用户设备访问第一服务器的会话对应的DNAI相同，也可以不同。
具体地，用户设备可以采用如下方式获取前述第一区域信息：
在一种可选的实施方式中，该用户设备从第二网元接收该第一区域信息。也就是说，先由第二网元确定第一区域信息，然后，该第二网元向用户设备发送前述第一区域信息。
例如，该第二网元存储有第一信息与区域信息的对应关系，或者，第二网元也可以从其他系统或网元获取到该对应关系。其中，该第一信息包括对应于第一区域的小区标识或追踪区标识。例如，该第一信息可以是追踪区标识(tracking area identity，TAI)；也可以为小区的标识信息，如小区ID(cell ID)或小区列表(cell ID list)；还可以为经 纬度或行政区域信息等，具体此处不做限定。可选的，该第一信息还可能包含其他区域(例如，第二区域)的小区标识或追踪区标识。而前述区域信息包括第一区域信息，该第一区域信息与第一信息中某个小区标识(例如，小区标识A)对应，或者，第一区域信息与第一信息中的某个追踪区标识(例如，追踪区标识B)对应，表示当前述用户设备位于前述小区标识A对应的小区中或者前述用户设备位于前述追踪区标识B指示的区域中，那么，该用户设备应当在第一区域信息指示的第一区域中。还应当理解的是，前述第一信息与区域信息的对应关系包括用户设备当前所在位置的小区标识和/或追踪区域标识与第一区域信息的对应关系，可能还包括其他的小区标识与其他的区域信息的对应关系，具体此处不做限定。
当用户设备在前述第二网元注册之后，第二网元可以获取该用户设备的第二信息，第二信息为当前时刻用户设备所位于的小区标识或追踪区标识。基于前述用户设备的第二信息(即用户设备当前的位置)该第二网元可以从前述对应关系中查找到与前述用户设备的第二信息对应的第一区域信息，然后，向前述用户设备发送前述第一区域信。也就是说，前第一信息包括前述第二信息，前述第二信息可以是第一信息中的多个小区标识中的一个，或者，是第一信息中的多个追踪区标识中的一个。此外，前述第一信息与区域信息的对应关系包括第二信息与第一区域信息的对应关系。
示例性的，前述第一信息与区域信息的对应关可以以对应关系表的形式存储于前述第二网元中，也就是说，该第二网元存储有记录前述对应关系的对应关系表。第二网元可以根据用户设备的当前位置查找对应关系表中的区域信息，确定与该用户设备当前的位置对应的区域信息为第一区域信息。随后，该第二网元向前述用户设备发送前述第一区域信息。
为便于理解，以表5为例，前述第一信息与区域信息的对应关系可以如下表5所示：
表5
Figure PCTCN2020127921-appb-000004
例如，若用户设备当前所在位置的小区标识为cell_002，即用户设备的第二信息为小区标识cell_002，那么，根据前述对应关系可以确定与该第二信息对应的区域信息为区域1的DNAI，因此，可以确定该第一区域信息为区域1的DNAI。又例如，若用户设备当前所在位置的追踪区标识为TAI_003，即用户设备的第二信息为追踪区标识TAI_003，那么，根据前述对应关系可以确定与该第二信息对应的区域信息为区域2的DNAI，因此，可以确定该第一区域信息为区域2的DNAI。
此外，前述第二网元可以是会话管理功能(session management function，SMF)网元或接入管理功能(access management function，AMF)网元。
在另一种可选的实施方式中，该用户设备从第二网元接收第一信息与区域信息的对应关系，该对应关系中的区域信息包括第一区域信息。然后，该用户设备根据该对应关系和 该用户设备的第二信息，确定该第一区域信息。也就是说，该第二网元不直接确定第一区域信息，而是向用户设备发送包含第一区域信息和第一信息的对应关系，由用户设备根据用户设备的第二信息和对应关系确定第一区域信息。可选的，用户设备可以根据用户设备的第二信息去查找和匹配对应的第一信息，进而找到该第一信息对应的第一区域信息。
类似的，该第二网元存储有第一信息与第一区域信息的对应关系，其中，该第一信息为对应于所述第一区域的小区标识或追踪区标识。当用户设备在前述第二网元注册之后，第二网元可以获取该用户设备的第二信息，第二信息为所述用户设备所位于的小区标识或追踪区标识。当接收到用户设备的初始第二信息或当用户设备的第二信息发生变化时(即终端设备的位置发生变化时)，第二网元可以将对应于用户设备的第二信息关联的第一区域的信息及其对应的第一信息发送给终端设备。关于该对应关系的介绍可以参阅前文中的描述，此处不再赘述。
本实施方式中，前述第二网元可以是会话管理功能SMF网元或接入管理功能AMF网元、网络能力开放功能(network exposure function，NEF)中的任意一种。可选的，该第二网元还可以是边缘配置服务器ECS或边缘使能服务器EES，具体此处不做限定。
1503、用户设备根据该第四服务器的区域信息和该第一区域信息，触发该第四服务器的切换。
其中，触发该四服务器的切换，可以理解为，触发用户设备将前述第四服务器切换为另一个服务器；也可以理解为，触发用户设备向另一个服务器(例如，ECS)服务器发送请求，以请求该服务器为用户设备分配或选择一个新的服务器。
具体地，当前述用户设备收到前述第四服务器的区域信息和第一区域信息之后，该用户设备将判断前述第四服务器的区域信息与第一区域信息是否匹配。其中，前述匹配可以理解为是该第四服务器的区域信息指示的区域与该第一区域信息指示的区域完全相同或该第一区域信息为第四服务器的区域信息的一个子集。示例性的，若第一区域信息指示的区域与第四服务器的区域信息指示的区域为同一区域，例如，第四服务器的区域信息为DNAI1，第一区域信息为DNAI1，则可以确定前述两个区域匹配。示例性的，若第一区域信息指示的区域在第四服务器的区域信息指示的区域内，例如第四服务器的区域信息为{DNAI1，DNAI2，DNAI3}，第一区域信息为DNAI1，则确定前述两个区域匹配。
可选的，当该第四服务器的区域信息和该第一区域信息不匹配时，该用户设备将触发该第四服务器的更新，也可以理解为触发第四服务器的“更换”或“切换”或“替换”或“变更”，即将服务用户的设备的第四服务器替换为其他功能对等的服务器，或将由其他和第四服务器功能对应的服务器为该用户设备提供服务。其中，不匹配可以理解为第一区域信息与第四服务器的区域信息不相同时或第一区域信息不是第四服务器的区域信息的一个子集时。为便于介绍，称该用户设备将第四服务器更换为第五服务器，该第五服务器的区域信息与该第一区域信息匹配。应当注意的是，前述第四服务器与第五服务器是同类型的服务器。例如，若前述第四服务器为EES，则该第五服务器也应当为EES。又例如，若前述第四服务器为EAS，则该第五服务器也应当为EAS。
在一种具体的实现方式中，若前述第四服务器为EES服务器，该第四服务器的区域信息为EES关联的DNAI，前述第一区域信息为目标DNAI，该目标DNAI用于指示用户设备当 前所在的区域，则用户设备将前述目标DNAI和EES关联的DNAI比对。若目标DNAI与EES关联的DNAI不匹配，则用户设备将更新前述EES。具体地，该用户设备将从本地检索出匹配目标DNAI的目标EES，即该目标EES关联的DNAI与前述目标DNAI匹配。可选的，该用户设备还将向EES或目标EES发送应用上下文迁移请求，以进行应用上下文迁移。
在另一种具体的实现方式中，若前述第四服务器为EAS服务器，该第四服务器的区域信息为EAS关联的DNAI，前述第一区域信息为目标DNAI，该目标DNAI用于指示用户设备当前所在的区域，则用户设备将前述目标DNAI和EAS关联的DNAI比对。若目标DNAI与EAS关联的DNAI不匹配，则用户设备将更新前述EAS。具体地，该用户设备将从本地检索出匹配目标DNAI的目标EAS，即该目标EAS关联的DNAI与前述目标DNAI匹配。可选的，该用户设备还可以向EAS或目标EAS发送上下文迁移请求，以进行应用数据迁移。可选的，该用户设备还将向EES或目标EES发送应用上下文迁移请求，以进行应用上下文迁移。
在另一种具体的实现方式中，该用户设备还可以请求第一服务器(例如，前述ECS)为该用户设备配置新的EES。例如，当该第四服务器的区域信息和该第一区域信息不匹配时，该用户设备向第一服务器发送请求消息，该请求消息用于请求该第一服务器更新前述第四服务器，或者，用于请求该第一服务器为该用户设备分配一个新的服务器(例如，第五服务器)。其中，该第五服务器可以是EES，也可以是EAS，具体此处不做限定。
本实施例中，第一服务器在为用户设备确定了第四服务器之后，可以将前述第四服务器的区域信息发送至用户设备，然后，用户设备可以根据获得的第一区域信息和前述第四服务器的区域信息确定是否要更新第四服务器。在这样的实施方式中，用户设备可以根据前述两个区域信息的比对情况触发更新第四服务器。这样使能层或应用层可以获取到第四服务器对应的DNAI信息，不必要求运营商提供第四服务器对应的网络格式的拓扑信息(小区标识列表或者追踪去列表)，也能够结合从网络层获取的DNAI和使能层获取的第四服务器的DNAI的信息，判断是否需要变更第四服务器。由此还可以保护运营商网络的拓扑信息。
如图16所示，为本申请提供的另一种获取信息的方法，在该方法中UE为图15对应实施例中用户设备的一种实现方式，ECS为图15对应实施例中第一服务器的一种实现方式，EES为图15对应实施例中第四服务器的一种实现方式。也可以理解为，EES为图15对应实施例中第一服务器的一种实现方式，EAS为图15对应实施例中第四服务器的一种实现方式。如图16所示，UE、ECS、EES将执行如下步骤：
1601a、UE向ECS发送消息1。相应的，ECS从UE接收消息1。
当UE需要获得某个服务器提供的应用服务时，该UE可以请求ECS为该UE分配服务器。具体地，该UE可以将该UE的信息和应用的信息发送至ECS，以使得ECS根据UE的信息和应用的信息为该UE分配服务器。
具体地，该UE可以向ECS发送消息1，该消息1用于向ECS请求EES的信息。其中，该消息1携带了用户标识信息，该用户标识可以是边缘使能客户端EEC的标识和UE的标识，该消息中还可以携带应用的信息，如应用的标识，应用客户端的配置文件，对应用服务器的其他需求如时延、带宽等。
可选地，该消息1还可以携带UE的位置。其中，该UE的位置可以是追踪区标识 (tracking area identity，TAI)、小区ID(cell ID)或小区列表(cell ID list)、经纬度或行政区域信息等，具体此处不做限定。此外，前述消息1还可以携带应用的标识、应用客户端的配置信息(application client profile)等应用的信息，具体此处不做限定。上述UE的位置信息和应用的信息可以用于ECS查找EES时，匹配符合UE的位置和可以提供前述应用服务的EAS的EES。
在一种可选的实施方式中，前述消息1为服务配置请求(service provision request)。也就是说，前述UE的位置、UE的标识、应用的标识以及EEC的标识等信息均可以携带于服务配置请求中，以使得该UE能够将前述信息发送至ECS。
在另一种可选的实施方式中，前述消息1为订阅消息，该订阅消息用于订阅ECS为UE分配EES的服务。
1601b、EES向ECS发送消息2。相应的，ECS从EES接收消息2。
步骤1601b为可选的步骤。步骤1061a与步骤1061b是相互独立的，并且，步骤1061a与步骤1061b之间无时间先后顺序的限定。也就是说，可以由UE先执行步骤1061a，再由EES执行步骤1061b；也可以由EES执行步骤1061b，再由UE执行步骤1061a；也可能存在UE和EES同时向ECS发送消息的情况。具有此处不做限定。例如，1601发生在用户移动过程中导致的应用上下文迁移(relocation)过程中。
也就是说，UE可以基于获取应用服务的需求向ECS发送消息1(即执行前述步骤1061a)，同样的，EES也可以在获知UE需要获取应用服务之后，向ECS发送消息2，以使得ECS为确定目标EES，该目标EES可以提供为UE上的前述应用服务的边缘应用服务器的信息。
其中，消息2可以携带了UE的标识和UE的位置，该消息2用于向ECS请求EES的信息。可选的，该消息2还可以携带应用的信息，例如，应用的标识，应用客户端的配置信息，用于过滤EES的应用相关的信息还可以参考EEC向ECS发送的消息1中的对应的应用的信息。此外，该消息2还可以携带EES的区域信息(例如，EES的DNAI)或EAS的区域信息(例如，EAS的DNAI)，该信息用于ECS去选择可以在EES DNAI或EAS DNAI提供服务的EES。
在一种可选的实施方式中，前述消息2为EES发现请求(EES discover request)。也就是说，前述UE的位置、UE的标识以及应用的标识等信息均可以携带于EES发现请求中，以使得该EES能够将前述信息发送至ECS，进而可以促使ECS发现UE所需要的EES。
在另一种可选的实施方式中，前述消息1为订阅消息，该订阅消息用于订阅EES，也可以理解为，订阅能够为UE提供应用服务的EES。
1602、ECS根据消息1或消息2确定第一EES。
本实施例中，ECS收到前述消息1和消息2中的任意一项之后，该ECS便会根据前述消息中携带的应用的信息和UE的信息为UE选择合适的EES。为便于介绍，称该ECS为UE选定的EES为第一EES。
在一种可选的实施方式中，该ECS将获取本地配置信息，将根据用户的信息、应用的信息以及本地配置信息确定前述目标EES。其中，本地配置信息可以包括UE和应用的对应关系，于是，该ECS可以根据UE的信息和对应关系查找与该UE对应的应用，并判断该应用是否是前述消息1或消息2中携带的应用信息所指示的应用。
在另一种可选的实施方式中，该ECS将获取本地策略信息，该本地策略信息用于指示当ECS未获取到应用的信息时，是否允许提供部分或全部的EES的信息。示例性的，若前述EES仅向ECS提供了UE的标识和UE的位置而未提供应用的信息，并且，本地策略信息允许在未获取到应用的信息时提供一部分EES的信息或者默认EES的信息。于是，该ECS将根据UE的位置匹配到的部分EES或默认EES确定为第一EES。也就是说，ECS可以根据UE的位置或应用的信息为该UE选择一个或多个EES作为第一EES，并确定该第一EES的信息，该第一EES的信息包括第一EES关联的DNAI。
当ECS为UE选择出第一EES之后，该ECS需要将第一EES的信息发送至EEC或源EES(即执行步骤1601b的EES)。一般地，若ECS是基于消息1中的信息确定的第一EES，则该ECS将执行步骤1603a；若ECS是基于消息2中的信息确定的第一EES，则该ECS将执行步骤1603b。也可以理解为，若该ECS从UE接收到消息1，则该ECS在确定第一EES之后也需要向UE回复该第一EES的信息，具体请参阅步骤1603a。类似的，若该ECS从EES接收到消息2，则该ECS在确定第一EES之后也需要向EES回复该第一EES的信息，具体请参阅步骤1603b。
1603a、ECS向UE发送第一EES关联的DNAI。相应的，UE从ECS接收第一EES关联的DNAI。
可选的，该第一EES关联的DNAI可以携带于前述消息1的响应消息中。
在一种可选的实施方式中，该第一EES关联的DNAI携带于前述服务配置响应(service provision response)消息中。此时，前述步骤1061a与步骤1063a之间采用的是请求-响应(request-response)机制。
在另一种可选的实施方式中，该第一EES关联的DNAI携带于前述基于订阅的通知消息中。此时，前述步骤1061a与步骤1063a之间采用的是订阅-通知(subscribe-notification)机制的消息。在这种实施方式中，该ECS可以在符合通知消息的触发条件时，发送多次通知消息，每个通知消息中均可以携带第一EES。但是，不同的通知消息中携带的第一EES可能不完全相同。
应当注意的是，若第一EES为一个EES，则该第一EES关联的DNAI为一个EES的DNAI；若第一EES为多个EES，则该第一EES的DNAI为包含多个EES关联的DNAI的列表。
可选的，该ECS还可以在发送第一EES关联的DNAI的消息中携带其他的关于第一EES的信息，具体此处不做限定。
应当注意的是，UE在收到第一EES关联的DNAI之后，若UE也收到了步骤1606中的第一DNAI，那么，该UE将执行步骤1608。
1603b、ECS向EES发送第一EES关联的DNAI。相应的，EES从ECS接收第一EES关联的DNAI。
步骤1603b为可选的步骤。当EES执行了步骤1601b且ECS执行了步骤1602之后，该ECS将执行步骤1603b。
在一种可选的实施方式中，该第一EES的DNAI携带于前述EES发现响应(EES discover response)消息中。此时，前述步骤1061b与步骤1063b之间采用的是请求-响应(request-response)机制。
在另一种可选的实施方式中，该第一EES关联的DNAI携带于前述基于订阅的通知消息中。此时，前述步骤1061b与步骤1063b之间采用的是订阅-通知(subscribe-notification)机制的消息。在这种实施方式中，该ECS可以在符合通知消息的触发条件时，发送多次通知消息给EES，每个通知消息中均可以携带第一EES。但是，不同的通知消息中携带的第一EES可能不完全相同。
可选的，该ECS还可以在发送第一EES关联的DNAI的消息中携带其他的关于第一EES的信息，具体此处不做限定。
在另一种可选的实施方式中，该EES在收到来自ECS的第一EES之后，该EES还可以将从ECS获取到的第一EES的信息(包含第一EES关联的DNAI)发送给UE，也可以理解为，发送给UE中的EEC。此时，该UE根据在1607中获取的DNAI信息与第一EES的信息做匹配，进而，该UE可以向该第一EES中的一个或多个EES发起边缘应用服务器EAS发现过程,以使得该EES执行后续的步骤1604。
EEC在获得第一EES的信息后，在当从1607获取到当前所处的DNAI后，判断当前所处的DNAI与第一EES的DNAI匹配，则该EEC连接到该第一EES。EEC向EES发送请求消息用于获取EAS的信息。EEC可以在消息中携带UE的信息，UE的信息可以包含用户的标识、用户的位置，还可以携带应用的信息。具体对于用户标识和应用信息的解释可以参考前面描述。
1604、EES根据UE的信息和应用的信息确定第一EAS。
本实施例中，EES本地有注册的EAS的信息，EES根据匹配满足EEC请求中携带的UE的信息和应用的信息的EAS。
在该EES为UE选择了第一EAS之后，该EES将执行步骤1605。
1605、EES向UE发送第一EAS关联的DNAI。
可选的，该EES还可以将除了EAS关联的DNAI之外的其他信息也发送给UE。
应当注意的是，步骤1605可以是由步骤1604触发的，也就是说，EES在为UE选择了第一EAS之后，该EES便将第一EAS关联的DNAI发送给EES。也可以是UE中的EEC在应用上下文迁移时实现的。具体地，UE中的EEC可以在应用上下文迁移过程中从EES接收到第一EAS的信息(包括第一EAS关联的DNAI)。
1606、AMF根据UE的位置确定目标DNAI。
其中，该目标DNAI用于指示UE当前所在的区域。
具体地，AMF存储有UE当前的位置与DNAI的对应关系，AMF可以根据UE的位置(例如，前文所介绍的组追踪区标识TAI、小区ID(cell ID)、小区列表(cell ID list)、经纬度或行政区域信息等)和前述对应关系确定UE当前所在的区域，即目标DNAI。
应当注意的是，若UE当前位置对应的DNAI发生变化(即UE前一次位置对应的DNAI和当前的DNAI不一致)。因此，该AMF确定的目标DNAI为UE当前所在区域的DNAI。
1607、AMF向UE发送该目标DNAI。相应的，UE从AMF接收到目标DNAI。
在一种可选的实施方式中，在步骤1607之前，UE向AMF发送注册、周期性注册、移动性注册或者切换消息等消息时，AMF在上述消息的响应消息中向UE发送目标DNAI。
在一种可选的实施方式中，在步骤1607之前，UE可以在注册、周期性注册、移动性 注册或者切换消息等消息中携带指示参数，用于指示请求获取目标DNAI。也就是说，步骤1607中AMF向UE发送的目标DNAI是基于前述注册消息或切换消息的响应消息。该UE与AMF之间采用的是请求-响应(request-response)机制。
在另一种可选的实施方式中，在步骤1607之前，该UE也可以通过订阅消息向AMF订阅目标DNAI。每当UE的位置发生改变时，例如，UE的TAI发生改变或UE所在的小区ID发生改变，该AMF便会根据变更后的TAI/小区ID为UE确定新的DNAI(即目标DNAI)，并将该目标DNAI发送至UE。
还应注意的是步骤1606和步骤1607也可以由SMF或NEF实现。也就是说，步骤1606也可以替换为由SMF或NEF根据UE的位置确定目标DNAI。步骤1607也可以替换为由SMF或NEF向UE发送该目标DNAI。具体地，如果替换为SMF或AMF，则SMF可以从AMF订阅UE的位置变化，从而获取UE当前的最新位置。进而可以采取与AMF判断UE的目标DNAI一样的逻辑判断目标DNAI。
应当注意的是，步骤1606和步骤1607与前述步骤1601a(或步骤1601b)至步骤1605是相互独立的。也就是说，当UE收到来自AMF的目标DNAI时，该UE不一定收到了前述来自ECS的第一EES的DNAI或来自EES的第一EAS的DNAI。
1608、UE根据目标DNAI和第一EES关联的DNAI(或第一EAS关联的DNAI)确定是否更新第一EES或第一EAS。
本实施例中，当前述UE收到前述第一EES关联的DNAI(或第一EAS关联的DNAI)和目标DNAI之后，该UE将判断前述第一EES关联的DNAI(或第一EAS关联的DNAI)与目标DNAI是否匹配。
在一种具体的实现方式中，当UE收到的是第一EES关联的DNAI和目标DNAI，则该UE将该第一EES关联的DNAI和目标DNAI比对。若该目标DNAI与第一EES关联的DNAI不匹配，则该UE将从本地检索出匹配目标DNAI的目标EES，即该目标EES关联的DNAI与前述目标DNAI匹配。进一步地，EEC还可以向目标EES发送应用发现请求消息，用于获取目标EAS的信息。
在另一种具体的实现方式中，当UE收到的是第一EAS关联的DNAI和目标DNAI，则该UE将该第一EAS关联的DNAI和目标DNAI比对。若该目标DNAI与第一EAS关联的DNAI不匹配，则该UE将从本地检索出匹配目标DNAI的目标EAS，即该目标EAS关联的DNAI与前述目标DNAI匹配。进一步地，EEC还可以向第一EES(即第一EAS注册的EES)发送的应用上下文迁移请求，还可以在请求中携带目标EAS的信息，用于请求第一EES执行应用上下文迁移。
在另一种具体的实现方式中，该UE还将向ECS触发服务配置更新(service provisioning update)流程，以使得该ECS为重新为UE分配EES。
在另一种具体的实现方式中，若该目标DNAI与第一EES关联的DNAI不匹配，或该目标DNAI与第一EAS关联的DNAI不匹配时，EEC可以向第一EES发送请求消息，该请求用于迁移应用上下文。
1609、ECS向SMF发送消息3。
步骤1609为可选的步骤。
本实施例中，当ECS为UE确定了第一EES之后，该ECS还将向SMF发送消息3，该消息3用于影响UE到EDN的路由。可以理解为，该消息3用于指示SMF确定从UE到EDN的路由；也可以理解为，该消息3用于配置SMF确定从UE到EDN的路由；还可以理解为，该消息3用于调整SMF确定从UE到EDN的路由。可选的，该消息3为AF influence消息。
在一种可选的实施方式中，前述消息3携带了第一EES的用户流量(traffic)描述信息和第一EES关联的DNAI。此时，该消息3用于影响UE到第一EES的路由。此时，前述第一EES的traffic描述信息包括数据网络DNN、单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)、第一EES的应用标识符以及UE与第一EES之间的流量过滤器(traffic filter)中的一项或多项。在这种实施方式中，当SMF收到前述消息3之后，该SMF将为UE配置从该UE到前述第一EES的路由，以使得该UE能够根据前述路由访问到前述第一EES。
在一种可选的实施方式中，该ECS还可以为UE选择一个或多个EAS，为便于介绍，称为第二EAS。此时，该ECS还将向SMF发送第二EAS的用户流量描述信息。此时，该消息3用于影响UE到第二EAS的路由。此时，前述第二EAS的traffic描述信息包括数据网络DNN、单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)、第二EAS的应用标识符以及UE与第二EAS之间的流量过滤器(traffic filter)中的一项或多项。在这种实施方式中，当SMF收到前述消息3之后，该SMF将为UE配置从该UE到前述第二EAS的路由，以使得该UE能够根据前述路由访问到前述第二EAS。
应当注意的是，前述第一EES关联的DNAI与前述第二EAS关联的DNAI可能是相同的DNAI，也可能是不同的DNAI，具体此处不做限定。而上述ECS影响EES的traffic和影响EAS的traffic可以在同一条消息中实现，或者在不同的消息中实现。
本实施例中，ECS在为UE确定了第一ESS或第一EAS之后，可以将前述第一ESS关联的DNAI或第一EAS关联的DNAI发送至UE，然后，UE可以根据获得的目标DNAI和前述第一EES关联的DNAI或第一EAS关联的DNAI确定是否要更新前述第一ESS或第一EAS。有利于及时触发UE更新第一EES或第一EAS，降低因DNAI不匹配而影响UE获得应用服务的几率。
在一种可选的实施方式中，前述步骤1607也可以替换为如下步骤：
a1、ECS从SMF接收目标DNAI；
a2、该ECS将该目标DNAI发送至UE。
在另一种可选的实施方式中，前述步骤1607也可以替换为如下步骤：
b1、EES从SMF接收目标DNAI；
b2、该EES将该目标DNAI发送至UE。
还应注意的是前述步骤a1、a2、b1和b2中的SMF可以替换为AMF或NEF。也就是说，ECS或EES也可以从AMF或NEF获取目标DNAI，然后，再将该目标DNAI发送至UE。
在这样的实施方式中，ECS或EES可以接收来自AMF、SMF或NEF的目标DNAI，然后，再由ECS或EES将该目标DNAI发送至UE。该方式下无需依赖UE与AMF/SMF等之间的NAS协议，而且可以利用现有ECS与SMF之间的接口实现获取UE位置对应的DNAI。
如图17所示，为本申请提供的另一种获取信息的方法的流程图。如图17所示，该方法包括以下步骤：
1701a、用户设备UE向边缘配置服务器ECS发送消息1。
1701b、边缘使能服务器EES向ECS发送消息2。
1702、ECS根据消息1或消息2确定第一EES。
1703a、ECS向UE发送第一EES的DNAI。
1703b、ECS向第一EES发送第一EES的DNAI。
1704、EES根据UE的信息和应用的信息确定第一EAS。
1705、EES向UE发送第一EAS的DNAI。
本实施例中，步骤1701a至步骤1705与前述步骤1601a至步骤1605类似，具体可以参阅前述步骤1061a至步骤1065，此处不再赘述。
1706、SMF向UE发送UE的位置与DNAI的对应关系。
本实施例中，当UE在前述SMF注册之后，SMF可以获取该用户设备的位置如用户设备所位于的小区标识或追踪区标识。当接收到用户设备的初始小区标识或追踪区标识信息或当用户设备的小区标识或追踪区标识发生变化时(即终端设备的位置发生变化时)，SMF可以将对应于用户设备的小区标识或追踪区标识关联的第一区域的信息及其对应的第一信息发送给UE。具体地，请参阅步骤1502中的相关介绍，具体此处不做赘述。
1707、UE根据UE的位置和对应关系确定目标DNAI。
本实施例中，当UE收到来自SMF的对应关系之后，该UE将基于该UE的位置该从前述对应关系中查找到与前述与UE当前的位置对应的DNAI，并将该DNAI确定为目标DNAI。
1708、UE根据目标DNAI和第一EES的DNAI(或第一EAS的DNAI)确定是否更新第一EES或第一EAS。
1709、ECS向SMF发送消息3。
本实施例中，步骤1708至步骤1709与前述步骤1608至步骤1609类似，具体可以参阅前述步骤1068至步骤1069，此处不再赘述。
本实施例中，ECS在为UE确定了第一ESS或第一EAS之后，可以将前述第一ESS的DNAI或第一EAS的DNAI发送至UE。然后，UE可以从SMF获得对应关系，并基于对应关系和UE的位置确定目标DNAI。然后，该UE将根据目标DNAI和前述第一EES的DNAI或第一EAS的DNAI确定是否要更新前述第一ESS或第一EAS。有利于及时触发UE更新第一EES或第一EAS，降低因DNAI不匹配而影响UE获得应用服务的几率。
在一种可选的实施方式中，前述步骤1706和步骤1707也可以替换为如下步骤：
c1、AMF/SMF/NEF向ECS发送DNAI及其对应的cell/TA list的对应关系。
c2、ECS将根据UE的位置确定该UE的位置对应的DNAI，即目标DNAI。
由于，ECS可以获取UE的位置信息，例如来自UE的上报或者从核心网获得该UE的位置信息。当该ECS收到前述对应关系之后，该ECS可以基于ECS中的UE的位置和该对应关系确定目标DNAI。
c3、该ECS将该目标DNAI发送至UE。
在另一种可选的实施方式中，前述步骤1706和步骤1707也可以替换为如下步骤：
d1、AMF/SMF/NEF向EES发送DNAI及其对应的cell/TA list的对应关系。其中cell/TA包含UE的位置对应的TA/cell。
d2、EES将根据UE的位置确定该UE的位置对应的DNAI，即目标DNAI。
由于，EES可以获取UE的位置信息，例如来自UE的上报或者从核心网获得该UE的位置信息。当该EES收到前述对应关系之后，该EES可以基于EES中的UE的位置和该对应关系确定目标DNAI。
d3、该EES将该目标DNAI发送至UE。
在一种可选的实施方式中，前述步骤1706和步骤1707也可以替换为如下步骤：
e1、EEC向ECS订阅UE位置对应的DNAI。
e2、可选地，如果ECS本地没有DNAI及其对应的cell/TA list的对应关系，则ECS可以向AMF/SMF/NEF订阅UE对应的DNAI，该DNAI可以与EES或EAS的用户面数据相关，也可以仅仅和UE的任何用户面数据相关。
e3、可选地，ECS从AMF/SMF/NEF获取UE位置对应的DNAI。
e4、ECS可以根据本地DNAI及其对应的cell/TA list的对应关系确定UE当前位置对应的DNAI，其中ECS可以从EEC或者核心网设备获取UE的位置即cell和TA，将根据UE的位置确定该UE的位置对应的DNAI，即目标DNAI。或者ECS从AMF/SMF/NEF获取UE位置对应的DNAI。
e5、该ECS将该目标DNAI发送至UE。
在一种可选的实施方式中，前述步骤1706和步骤1707也可以替换为如下步骤：
f1、EEC向EES订阅UE位置对应的DNAI。
f2、可选地，如果EES本地没有DNAI及其对应的cell/TA list的对应关系，则EES可以向AMF/SMF/NEF订阅UE对应的DNAI，该DNAI可以与EES或EAS的用户面数据相关，也可以仅仅和UE的任何用户面数据相关。
f3、可选地，EES从AMF/SMF/NEF获取UE位置对应的DNAI。
f4、EES可以根据本地DNAI及其对应的cell/TA list的对应关系确定UE当前位置对应的DNAI，其中EES可以从EEC或者核心网设备获取UE的位置即cell和TA，将根据UE的位置确定该UE的位置对应的DNAI，即目标DNAI。或者EES从AMF/SMF/NEF获取UE位置对应的DNAI。
f5、该EES将该目标DNAI发送至UE。
在这样的实施方式中，ECS或EES可以接收来自AMF、SMF或NEF的对应关系，然后，再由ECS或EES基于内部存储的UE的位置以及收到的对应关系确定目标DNAI，并将该目标DNAI发送至UE。有利于使得ECS在向UE发送第一EES的DNAI时将前述目标DNAI一并发送至UE，缩短UE等待目标DNAI的时延。类似的，有利于使得EES在向UE发送第一EAS的DNAI时将前述目标DNAI一并发送至UE，缩短UE等待目标DNAI的时延。可以使得UE尽快将第一EES的DNAI(或第一EAS的DNAI)与目标DNAI进行比对，进而可以缩短时延。
以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。所述处理器可以包括但不限于以 下至少一种：中央处理单元、微处理器、数字信号处理器(digital signal processing，DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。该处理器可以内置于片上系统(system on chip，SoC)或专用集成电路(application specific integrated circuit，ASIC)，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、可编程逻辑电路(programable logic device，PLD)或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微控制器、DSP、MCU、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
当以上模块或单元使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital versatile disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (36)

  1. 一种获取信息的方法，其特征在于，包括：
    第一服务器从第二服务器接收应用的第一实例的信息，所述第一实例的信息包括所述应用的标识信息和第一信息，所述第一信息用于指示所述第一实例的位置；
    所述第一服务器从第三服务器接收所述应用的第二实例的信息，所述第二实例的信息包括所述应用的标识信息和第二信息，所述第二信息用于指示所述第二实例的位置，所述第一服务器为服务所述第二服务器和所述第三服务器的服务器；
    所述第一服务器保存所述第一实例的信息和所述第二实例的信息。
  2. 根据权利要求1所述的方法，其特征在于，还包括：
    所述第一服务器从第二服务器接收或第一网元接收所述第二服务器的区域信息；
    所述第一服务器获取用户设备的位置信息；
    所述第一服务器根据所述第二服务器的区域信息和所述用户设备的位置信息确定目标服务器。
  3. 根据权利要求2所述的方法，其特征在于，所述第一网元为网络能力开放功能NEF网元、统一数据管理UDM网元、统一数据存储库UDR网元、策略控制功能PCF网元、或网络存储功能NRF网元。
  4. 根据权利要求2或3所述的方法，其特征在于，还包括：
    所述第一服务器从边缘客户使能端EEC接收应用标识，所述目标服务器服务于所述应用标识对应的应用实例。
  5. 根据权利要求2至4中任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一服务器向所述用户设备发送所述目标服务器的区域信息。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一服务器向所述用户设备发送所述目标服务器区域信息对应的小区标识或追踪区标识。
  7. 根据权利要求2至6中任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一服务器向所述用户设备发送所述用户设备所在位置的区域信息。
  8. 根据权利要求2至7中任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一服务器向第二网元发送第一消息，所述第一消息用于影响所述用户设备到所述目标服务器的路由信息，所述第一消息包括所述用户设备的用户标识和应用标识，所述第一消息还包括所述目标服务器的用户流量描述信息和/或所述目标服务器的区域信息。
  9. 根据权利要求2至7中任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一服务器向第二网元发送第二消息，所述第二消息用于影响所述用户设备到所述目标服务器对应的应用实例的路由信息，所述第二消息包括所述用户设备的用户标识和应用标识，所述第一消息还包括所述应用实例的用户流量描述信息和/或所述应用实例的区域信息。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第二网元包括会话管理功能SMF网元、接入管理功能AMF网元、网络能力开放功能NEF网元中的任意一项。
  11. 根据权利要求1至10中任意一项所述的方法，其特征在于，
    所述应用的第一实例的信息还包括如下一项或多项：
    第一边缘使能服务器的标识信息，或者，所述第一实例的服务范围信息；
    所述应用的第二实例的信息还包括如下一项或多项：
    第二边缘使能服务器的标识信息，或者，所述第二实例的服务范围信息。
  12. 根据权利要求1至11中任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一服务器从第一设备接收所述应用的标识信息和所述第一设备的位置信息；
    所述第一服务器向所述第一设备发送第三实例的IP地址，所述第三实例由所述应用的标识信息、所述第一设备的位置信息、所述应用的第一实例的信息和所述应用的第二实例的信息确定，所述第三实例为所述第一实例或所述第二实例。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    当所述第三实例的IP地址为所述第一实例的IP地址时，所述第一服务器向所述第一设备发送如下一项或多项：
    所述第一边缘网络的接入标识信息、所述第一边缘网络的IP地址、或所述第一边缘使能服务器的IP地址；
    当所述第三实例的IP地址为所述第二实例的IP地址时，所述第一服务器向所述第一设备发送如下一项或多项：
    所述第二边缘网络的接入标识信息、所述第二边缘网络的IP地址、或所述第二边缘使能服务器的IP地址。
  14. 一种获取信息的方法，其特征在于，包括：
    第二服务器获取应用的第一实例的信息，所述第一实例的信息包括所述应用的标识信息和第一信息，所述第一信息用于指示所述第一实例的位置；
    所述第二服务器向第一服务器发送所述第一实例的信息，所述第一服务器为服务所述第二服务器的服务器。
  15. 根据权利要求14所述的方法，其特征在于，还包括：
    所述第二服务器向所述第一服务器发送所述第二服务器的区域信息。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一信息包括所述第一实例的互联网协议IP地址和如下一项或多项：
    第一边缘网络的接入标识信息、所述第一边缘网络的IP地址、或第一边缘使能服务器的IP地址，所述第二服务器位于所述第一边缘网络中。
  17. 根据权利要求14至16中任意一项所述的方法，其特征在于，所述第二服务器获取应用的第一实例的信息，包括：
    所述第二服务器从所述应用的第一实例服务器接收所述第一实例的标识信息和所述第一实例的IP地址；
    所述第二服务器从所述第二服务器获取所述第一信息。
  18. 根据权利要求14至16中任意一项所述的方法，其特征在于，所述第二服务器获取应用的第一实例的信息，包括：
    所述第二服务器从所述应用的第一实例服务器接收所述第一实例的信息。
  19. 根据权利要求14至18中任意一项所述的方法，其特征在于，所述应用的第一实 例的信息还包括如下一项或多项：
    第一边缘使能服务器的标识信息，或者，所述第一实例的服务范围信息。
  20. 一种获取信息的方法，其特征在于，包括：
    用户设备从第一服务器接收第四服务器的区域信息，所述第一服务器为服务于所述第四服务器的服务器；
    所述用户设备获取第一区域信息，所述第一区域信息用于指示所述用户设备所在的区域；
    所述用户设备根据所述第四服务器的区域信息和所述第一区域信息，触发所述第四服务器的切换。
  21. 根据权利要求20所述的方法，其特征在于，所述第四服务器的区域信息和所述第一区域信息不匹配。
  22. 根据权利要求20或21所述的方法，其特征在于，触发所述第四服务器的切换，包括：
    所述用户设备确定第五服务器，所述第五服务器的区域信息与所述第一区域信息匹配。
  23. 根据权利要求20至22中任意一项所述的方法，其特征在于，所述用户设备获取第一区域信息，包括：
    所述用户设备从第二网元接收所述第一区域信息；
    或者，
    所述用户设备从第二网元接收第一信息与所述第一区域信息的对应关系，所述第一信息为对应于所述第一区域信息指示的区域的小区标识或追踪区标识；
    所述用户设备根据所述对应关系和所述用户设备的第二信息，确定所述第一区域信息，所述第二信息用于指示所述用户设备所在位置的小区标识或追踪区标识。
  24. 根据权利要求20至23中任意一项所述的方法，其特征在于，所述用户设备从第一服务器接收第四服务器的区域信息之前，所述方法还包括：
    所述用户设备向所述第一服务器发送应用标识，所述应用标识用于所述第四服务器的确定。
  25. 根据权利要求24所述的方法，其特征在于，
    当所述第一服务器为边缘配置服务器时，所述第四服务器为边缘使能服务器，所述第四服务器服务于所述应用标识对应的应用实例；
    或者，
    当所述第一服务器为边缘使能服务器时，所述第四服务器为所述应用标识对应的应用实例。
  26. 根据权利要求23所述的方法，其特征在于，所述第二网元包括会话管理功能SMF网元或接入管理功能AMF网元、网络能力开放功能NEF、边缘配置服务器ECS、边缘使能服务器EES。
  27. 一种获取信息的方法，其特征在于，包括：
    第一服务器从用户设备接收应用标识；
    所述第一服务器根据所述应用标识确定第四服务器，所述第一服务器为服务所述第四 服务器的服务器；
    第一服务器向用户设备发送第四服务器的区域信息，所述第四服务器的区域信息和第一区域信息用于触发所述第四服务器的切换，所述第一区域信息用于指示所述用户设备所在的区域。
  28. 根据权利要求27所述的方法，其特征在于，所述第四服务器的区域信息和第一区域信息用于确定第五服务器，所述第五服务器的区域信息与所述第一区域信息匹配。
  29. 根据权利要求27或28所述的方法，其特征在于，
    当所述第一服务器为边缘配置服务器时，所述第四服务器为边缘使能服务器，所述第四服务器服务于所述应用标识对应的应用实例；
    或者，
    当所述第一服务器为边缘使能服务器时，所述第四服务器为所述应用标识对应的应用实例。
  30. 根据权利要求27至29中任意一项所述的方法，其特征在于，当所述第一服务器为边缘配置服务器时，所述方法还包括：
    所述第一服务器向第二网元发送第一消息，所述第一消息用于影响所述用户设备到所述第四服务器的路由信息，所述第一消息包括所述用户设备的用户标识和应用标识，所述第一消息还包括所述目标服务器的用户流量描述信息和/或所述目标服务器的区域信息。
  31. 根据权利要求27至29中任意一项所述的方法，其特征在于，当所述第一服务器为边缘配置服务器时，所述方法还包括：
    所述第一服务器向第二网元发送第二消息，所述第二消息用于影响所述用户设备到所述第四服务器对应的应用实例的路由信息，所述第二消息包括所述用户设备的用户标识和应用标识，所述第一消息还包括所述应用实例的用户流量描述信息和/或所述应用实例的区域信息。
  32. 一种获取信息的装置，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器存储有程序，当所述存储器存储的程序指令被所述处理器执行时使得所述路径选择装置实现权利要求1至13中任意一项所述的方法，或者，实现权利要求27至31中任意一项所述的方法。
  33. 一种获取信息的装置，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器存储有程序，当所述存储器存储的程序指令被所述处理器执行时使得所述路径选择装置实现权利要求14至19中任意一项所述的方法。
  34. 一种获取信息的装置，其特征在于，包括处理器，所述处理器和存储器耦合，所述存储器存储有程序，当所述存储器存储的程序指令被所述处理器执行时使得所述路径选择装置实现权利要求20至26中任意一项所述的方法。
  35. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行如权利要求1至31中任意一项所述的方法。
  36. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至31中任意一项所述的方法。
PCT/CN2020/127921 2019-08-20 2020-11-10 一种获取信息的方法及装置 WO2021189869A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202080054615.6A CN114175600B (zh) 2019-08-20 2020-11-10 一种获取信息的方法及装置

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
PCT/CN2019/101650 WO2021031127A1 (zh) 2019-08-20 2019-08-20 一种获取信息的方法及装置
PCT/CN2020/080966 WO2021031562A1 (zh) 2019-08-20 2020-03-24 一种获取信息的方法及装置
CNPCT/CN2020/080966 2020-03-24

Publications (1)

Publication Number Publication Date
WO2021189869A1 true WO2021189869A1 (zh) 2021-09-30

Family

ID=74660192

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/CN2019/101650 WO2021031127A1 (zh) 2019-08-20 2019-08-20 一种获取信息的方法及装置
PCT/CN2020/080966 WO2021031562A1 (zh) 2019-08-20 2020-03-24 一种获取信息的方法及装置
PCT/CN2020/127921 WO2021189869A1 (zh) 2019-08-20 2020-11-10 一种获取信息的方法及装置

Family Applications Before (2)

Application Number Title Priority Date Filing Date
PCT/CN2019/101650 WO2021031127A1 (zh) 2019-08-20 2019-08-20 一种获取信息的方法及装置
PCT/CN2020/080966 WO2021031562A1 (zh) 2019-08-20 2020-03-24 一种获取信息的方法及装置

Country Status (4)

Country Link
US (1) US20220174585A1 (zh)
EP (1) EP4016961A4 (zh)
CN (2) CN114270789B (zh)
WO (3) WO2021031127A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141827A1 (en) * 2022-01-26 2023-08-03 Huawei Technologies Co., Ltd. Area of interest-specific information for mulit-access edge computing

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110727633A (zh) * 2019-09-17 2020-01-24 广东高云半导体科技股份有限公司 基于SoC FPGA的边缘人工智能计算系统构架
US11956332B2 (en) * 2019-12-31 2024-04-09 Convida Wireless, Llc Edge aware distributed network
KR20220065409A (ko) * 2020-11-13 2022-05-20 삼성전자주식회사 에지 컴퓨팅 서비스를 수행하는 전자 장치 및 전자 장치의 동작 방법
CN115175256A (zh) * 2021-04-07 2022-10-11 华为技术有限公司 一种用于传输上下文的方法和通信装置
US11689982B2 (en) * 2021-08-24 2023-06-27 Verizon Patent And Licensing Inc. Weighted MEC selection for application-based MEC traffic steering
US11936736B2 (en) * 2021-11-10 2024-03-19 Electronics And Telecommunications Research Institute Interworking method between different 5G multi-access edge computing (MEC) platforms using common application programing interface framework (CAPIF)
CN114884941B (zh) * 2022-04-12 2023-09-05 中国电信股份有限公司 针对边缘计算平台的业务处理方法、装置、系统及介质
CN116528397B (zh) * 2023-06-29 2023-09-19 新华三技术有限公司 5g双域专网的实现方法及装置、5g双域专网系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140108674A1 (en) * 2010-12-27 2014-04-17 Limelight Networks, Inc. Anycast redirect to unicast content download
CN106488504A (zh) * 2015-08-28 2017-03-08 华为技术有限公司 网络系统和网络通信的方法
US20180041424A1 (en) * 2016-08-05 2018-02-08 Huawei Technologies Co., Ltd. Slice/service-based routing in virtual networks
CN109040312A (zh) * 2018-09-17 2018-12-18 云迅智能科技南京有限公司 一种多接入边缘计算网络系统及方法
CN109831548A (zh) * 2019-03-18 2019-05-31 中国联合网络通信集团有限公司 虚拟内容分发网络vCDN节点建立方法及服务器

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159750B (zh) * 2007-11-20 2011-12-07 杭州华三通信技术有限公司 一种身份认证方法和装置
US10380634B2 (en) * 2008-11-22 2019-08-13 Callidus Software, Inc. Intent inference of website visitors and sales leads package generation
US8949307B2 (en) * 2011-11-15 2015-02-03 Google Inc. Cloud-to-device messaging for application activation and reporting
WO2017100640A1 (en) * 2015-12-11 2017-06-15 Interdigital Patent Holdings, Inc. Method and apparatus for enabling third party edge clouds at the mobile edge
CN107566437B (zh) * 2016-07-01 2020-04-14 大唐移动通信设备有限公司 信息传输方法及装置
CN109952741A (zh) * 2016-10-05 2019-06-28 康维达无线有限责任公司 服务实例化的能力暴露
CN108574728B (zh) * 2017-03-08 2021-05-04 中兴通讯股份有限公司 用于移动边缘计算的流量路径改变检测的方法和装置
CN113194157B (zh) * 2017-06-30 2022-10-28 华为技术有限公司 一种应用实例地址的转换方法和装置
CN109257193A (zh) * 2017-07-11 2019-01-22 中国移动通信有限公司研究院 边缘缓存管理方法、个人云系统和计算机可读存储介质
US10660016B2 (en) * 2017-11-08 2020-05-19 Ofinno, Llc Location based coexistence rules for network slices in a telecommunication network
CN112291381B (zh) * 2017-11-13 2022-01-21 华为技术有限公司 应用服务器切换方法、设备及系统
WO2019100266A1 (zh) * 2017-11-22 2019-05-31 华为技术有限公司 移动边缘主机服务通知方法和装置
DE112018005693T5 (de) * 2017-11-27 2020-07-09 Intel IP Corporation Multi-access edge computing (mec)-basierte mehrbetreiberunterstützung für cellular vehicle-to-everything (c-v2x) systeme
CN109862581B (zh) * 2017-11-30 2022-05-17 华为技术有限公司 一种通信方法及装置
CN109981316B (zh) * 2017-12-27 2022-11-25 华为技术有限公司 应用服务器的切换方法及会话管理网元、终端设备
CN110049070B (zh) * 2018-01-15 2021-09-14 华为技术有限公司 事件通知方法及相关设备
CN110098947B (zh) * 2018-01-31 2021-01-29 华为技术有限公司 一种应用的部署方法、设备及系统
CN110120879B (zh) * 2018-02-06 2020-12-01 华为技术有限公司 一种应用服务水平协议的保障方法、设备及系统
CN110730499B (zh) * 2018-07-16 2021-06-15 华为技术有限公司 一种mec信息获取方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140108674A1 (en) * 2010-12-27 2014-04-17 Limelight Networks, Inc. Anycast redirect to unicast content download
CN106488504A (zh) * 2015-08-28 2017-03-08 华为技术有限公司 网络系统和网络通信的方法
US20180041424A1 (en) * 2016-08-05 2018-02-08 Huawei Technologies Co., Ltd. Slice/service-based routing in virtual networks
CN109040312A (zh) * 2018-09-17 2018-12-18 云迅智能科技南京有限公司 一种多接入边缘计算网络系统及方法
CN109831548A (zh) * 2019-03-18 2019-05-31 中国联合网络通信集团有限公司 虚拟内容分发网络vCDN节点建立方法及服务器

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023141827A1 (en) * 2022-01-26 2023-08-03 Huawei Technologies Co., Ltd. Area of interest-specific information for mulit-access edge computing

Also Published As

Publication number Publication date
US20220174585A1 (en) 2022-06-02
CN114175600B (zh) 2023-06-20
WO2021031562A1 (zh) 2021-02-25
WO2021031127A1 (zh) 2021-02-25
CN114175600A (zh) 2022-03-11
EP4016961A4 (en) 2022-10-12
CN114270789A (zh) 2022-04-01
CN114270789B (zh) 2023-09-01
EP4016961A1 (en) 2022-06-22

Similar Documents

Publication Publication Date Title
WO2021189869A1 (zh) 一种获取信息的方法及装置
US20220248318A1 (en) Control of Network Slice
US20240056509A1 (en) Access network with service-based interfaces
US11729137B2 (en) Method and device for edge application server discovery
US11706705B2 (en) Multimedia priority service
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
US20200252837A1 (en) Method for checking change in wireless connection type of terminal in third-party application server
WO2022152238A1 (zh) 一种通信方法及通信装置
WO2020015634A1 (zh) 一种mec信息获取方法及装置
US20210385283A1 (en) Multimedia Priority Service
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
US20230189192A1 (en) Access to Second Network by Wireless Device
CN114365518A (zh) 一种通过服务应用影响核心网络中数据业务路由的方法
CN114666859A (zh) 用于选择服务无线通信设备的会话管理实体的方法和装置
JP2023526542A (ja) 無線通信システムで端末にローカルデータネットワーク情報を提供するための方法及び装置
US20220264690A1 (en) Method for influencing data traffic routing in a core network
CN116530111A (zh) Wtru上的用户装备/无线发射/接收单元提供的数据网络
WO2021233395A1 (zh) 一种通信方法、装置及计算机可读存储介质
WO2021081712A1 (zh) 一种dns查询方法及装置
WO2023143212A1 (zh) 一种通信方法及装置
WO2021244622A1 (zh) 一种通信方法、装置及计算机可读存储介质
US20230345347A1 (en) Method for determining mec access point and apparatus
WO2023061207A1 (zh) 一种通信方法、通信装置及通信系统
WO2023082858A1 (zh) 确定移动性管理策略的方法、通信装置及通信系统
WO2023015973A1 (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: 20926749

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20926749

Country of ref document: EP

Kind code of ref document: A1