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

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

Info

Publication number
WO2021031127A1
WO2021031127A1 PCT/CN2019/101650 CN2019101650W WO2021031127A1 WO 2021031127 A1 WO2021031127 A1 WO 2021031127A1 CN 2019101650 W CN2019101650 W CN 2019101650W WO 2021031127 A1 WO2021031127 A1 WO 2021031127A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
instance
information
application
api
Prior art date
Application number
PCT/CN2019/101650
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 PCT/CN2019/101650 priority Critical patent/WO2021031127A1/zh
Priority to EP20854354.6A priority patent/EP4016961A4/en
Priority to CN202080058580.3A priority patent/CN114270789B/zh
Priority to PCT/CN2020/080966 priority patent/WO2021031562A1/zh
Priority to PCT/CN2020/127921 priority patent/WO2021189869A1/zh
Priority to CN202080054615.6A priority patent/CN114175600B/zh
Publication of WO2021031127A1 publication Critical patent/WO2021031127A1/zh
Priority to US17/675,705 priority patent/US20220174585A1/en

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 universal 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 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,
  • 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.
  • 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 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 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, where 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 the 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 second server
  • the three servers send information about 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. Application delay.
  • 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 respectively, and the second server or the third server does not need to be configured to send the application information separately.
  • the information message of the instance Therefore, signaling overhead can be saved, and the delay of access applications caused by increased signaling can be reduced.
  • the first server receiving information about 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 respectively, and the second server or the third server does not need to be configured to send the application information separately.
  • the information message of the instance Therefore, signaling overhead can be saved, and the delay of access applications caused by increased signaling can be reduced.
  • 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, and the publication type information is used to indicate the publication of 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 can 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 , Then 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 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 information of an application instance, or to indicate the type of the application instance to which the first server requests subscription.
  • 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 scope 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 range information of the instance of the application is used to indicate the range of users who use the instance of the application, and may also refer to the location 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 be implemented in multiple ways, the diversity of solutions is increased.
  • the method It further 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 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 for the first device to obtain the information of the application instance 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 to the first device one or more of the following: 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 the 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 device 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 for deploying 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 the 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 Send 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). In addition, 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, thus saving The process for the first server to obtain the information of the application instance.
  • 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 about 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 guarantee 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 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. Therefore, the first server can use existing signaling to 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 applications caused by increased signaling can be reduced.
  • 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 applications caused by increased signaling can be reduced.
  • 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 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 can 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 reduced.
  • 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 information of an application instance, or to indicate the type of the application instance to which the first server requests subscription.
  • 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 scope 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 range information of the instance of the application is used to indicate the range of users who use the instance of the application, and may also refer to the location 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 can be the same server among the aforementioned multiple servers, or can be a different server among the aforementioned multiple servers. Since the second server can have multiple implementation manners, 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.
  • an embodiment of the present application provides an apparatus for acquiring information, which 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, 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 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, and 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 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; Three servers, used to obtain information about the second instance of the application; the first server, used to receive information about the first instance of the application and information about 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 car networking network device can implement the functions of the network device involved in the fifth, seventh, or ninth aspect.
  • the first server can implement any one of the implementation manners of the first aspect and the first aspect The function of the first server involved.
  • the second server may implement any one of the implementation manners of the second aspect and the second aspect The function of the second server involved.
  • the embodiments of the present application provide a computer program product containing instructions, which when run on a computer, cause the computer to execute any one of the foregoing first aspect and the first aspect, or the second Aspect and the method introduced in any one of the implementation manners in the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, when the instructions run on a computer, so that the computer executes any one of the foregoing first aspect and the first aspect or The second aspect and the method introduced in any one of the second 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,
  • 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.
  • Figure 1A is a system architecture diagram provided in an embodiment of the 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. 3 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 this application.
  • FIG. 5 is another flowchart of the method for obtaining information in an embodiment of the 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 obtaining information in an embodiment of the application.
  • FIG. 10 is a schematic diagram of another embodiment of an apparatus for obtaining information in an embodiment of this application.
  • FIG. 11 is a schematic diagram of another embodiment of an apparatus for obtaining information in an embodiment of the application.
  • Fig. 12 is a schematic diagram of another embodiment of an apparatus for acquiring 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 the 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 application instance, and the information of the application instance 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 information about an 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 capacity, or a terminal device with limited computing capacity, 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 here. 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 application instance, and the information of the application instance 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 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 simultaneously, 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 chronological order, 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 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 are 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 among 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 Figure 2 below.
  • 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 a 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 part 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 is only 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
  • EES edge enabler server
  • 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 it may have a first server.
  • 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 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 second edge network is referred to as the application instance server 1041 through the seventh interface 117.
  • 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.
  • 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. There are no restrictions. In this embodiment and subsequent embodiments, only the multiple application instances are different instances of the same application as an example for introduction. Therefore, for an application deployed on the edge network where the second server is located, 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 operations 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.
  • the instance of the application refers to the running instance of the application server in one server of the application server program, and different instances of one 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
  • the data center can provide a server that can provide the operating environment of the Huawei Video application server, then the Huawei Video application can run its Huawei Video application server program on the server deployed in the Beijing data center.
  • the operation is deployed in
  • the application server program of Huawei Video on the Huawei Application Server in the Beijing Data Center can be called an application instance of Huawei Video (referred to as "Huawei Video-Beijing Instance"), and this server is a Huawei Video application instance server. Therefore, a Huawei Video client that is close to the data center can connect to the Huawei Video-Beijing instance to access the content provided by Huawei Video.
  • Huawei Video-Beijing Instance an application instance of 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 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 called 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 the identification information of the first edge-enabled server or the 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 it may be 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, and 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 called the second instance. It should be understood that the aforementioned 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 will not be 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 information 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 first appears in the second server, for example, the second server acquires 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 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 aforementioned step 202a and the aforementioned step 202b have no clear time sequence limitation, there is no time 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 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, signaling overhead can be saved and service delays 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, where 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 happening.
  • 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 obtained by the first device is called the third instance, and the third instance is 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 that indicated by the location information of the first device and the location If the distance of the location 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 second instance information.
  • 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 interaction 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, the second server, and the third server as an example, 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 search for 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, can reduce the signaling procedure for the first device to obtain the information of the instance of the application, 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 for the first device to obtain the information of the application instance is optimized.
  • the aforementioned first server may be an edge network configuration server, or other servers, which are 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 has been configured with information about the application instance, 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 application instance information 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 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 the reference point 4 (edge-4). Therefore, 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 FIG. 1A, FIG. 1C or FIG. 1D.
  • edge-enabled server 302 and application instance server 303 are both located in the edge network.
  • the edge network EDN is a peer-to-peer concept of the central cloud, which can be understood as a local data center, and 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).
  • 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 application instance. 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 application instance 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 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.
  • 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
  • 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 . Or, 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 to the edge-enabled server one or more 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 are no restrictions.
  • the edge network configuration server sends a first request to the edge enabling server.
  • the edge network configuration server may send the 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 information about 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 from the local database of the edge-enabled server, which is not 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 tracking area identification TAI, cell ID, or cell ID list of the UE, and save the tracking area identification TAI, cell ID, or cell ID of the UE.
  • 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 will identify the tracking area TAI , Cell ID or cell ID list and other information is sent to the edge network configuration server.
  • UDR unified data repository
  • SMF session management function
  • the service range information of the first example 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 may 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
  • 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 application instance 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 instance of the application 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 to the UE the IP address of the instance that the UE wants to obtain.
  • 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 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 application instance, 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 subscription to the
  • the information of the application instance in the edge-enabled server is such that when the information of the application instance in the edge-enabled server is updated, the edge-enabled server can actively notify the edge network configuration server of the information of the application instance.
  • 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, which are not specifically limited here.
  • the number of edge-enabled servers in step 501 may be one or multiple. Therefore, 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 corresponds to the edge-enabled server one-to-one, or each edge-enabled server corresponds to multiple application instance servers. There are no restrictions.
  • step 503 and the foregoing steps 501 and 502 have no clear time sequence limitation. That is, 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 Simultaneous execution; or, step 503 and step 502 are executed simultaneously.
  • 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 Simultaneous execution; or, step 503 and step 502 are executed simultaneously.
  • the details are not limited here.
  • step 503 is similar to the aforementioned step 401, and the details are not 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 application instance includes the identification information of the application instance in step 503 and the IP address of the application instance, and the information of the application instance also includes the access identification information of the edge network or 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 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 from the local database of the edge-enabled server, which is not 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 are not 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 enable server is based on the subscription-notification mechanism, when the edge network configuration server subscribes to an instance of the application or a certain number of the application from the edge enable server In the case of an instance, the edge enabling server can send the instance information 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
  • the signaling overhead of the information of the application instance further reduces the delay of accessing the application.
  • the method for obtaining information proposed in the embodiments of the present application can be applied to the system shown in Figure 3 above, and can also be combined with the common application programming interface framework (common API framework, CAPIF) by reusing the common API framework Part of the signaling process in the, to save the signaling construction between the edge network configuration server and the edge enable server.
  • common API framework common API framework
  • 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 opening 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 opening 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) )in.
  • 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), The API common architecture core function CCF 601 is connected to the API open 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 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 API common architecture core function CCF601 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).
  • CAPIF-1e connection point 1e
  • CAPIF connection point 2e
  • -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 applications can be run in terminal devices or network devices.
  • the API calling entity 6051/6052 can also be equipment in the PLMN network, for example, the mobility management entity (MME) in the 4G communication system, the radio access network (RAN) equipment, policies and Charging rules function (policy and charging rules function, PCRF) network elements, etc.; it can also be the access and mobility management function (AMF) network elements in the 5G communication system, and session management function (session management) function, SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, application function (AF) network element, etc.
  • 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 APIs.
  • 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 CCF601; it can monitor the events reported by the API common architecture core function CCF601; 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 CCF of the two API common architectures are located in different trust domains, the aforementioned system architecture of FIG. 6A can be extended to FIG. 6C.
  • the units or modules in FIG. 6B and FIG. 6C please refer to the introduction corresponding to FIG. 6A above, and the details will not be repeated here.
  • connection point 6 can interact through connection point 6 (CAPIF-6), and the API common architecture core function CCF1 in FIG. 6C It can also interact with the core function of API Common Architecture CCF2 through connection point 6e (CAPIF-6e).
  • the connection point 6 or the connection point 6e can support one API common architecture core function CCF to publish 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 general architecture core function 2 the application instance server can realize the function of one or more functional modules in the API provider 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 the aforementioned FIG. 3 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 realize the functions 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. Send the identification information of the application instance and the IP address of the application instance.
  • 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. 3 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.
  • the application instance server may include some or all of the interface functions of the connection point 4; for example, the seventh interface 117 in FIG. 1D may include some or all of the interface functions of the connection point 4.
  • the application instance server when the application instance server implements the API open 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 publish 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 the 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 to the edge-enabled server through connection point 6 or connection point 6e.
  • API discovery response service API publish 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.
  • 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 details are not repeated here.
  • the edge network configuration server saves information about 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, 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 application instance information from the API common architecture core function CCF1 without traversing the edge enable server (ie, the API common architecture core function 2) 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 application instance, 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 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.
  • 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 enabling server is not specifically limited here.
  • both the edge network configuration server and the edge-enabled 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 storage problem of the application instance information 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 the aforementioned FIG. 3 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 enabling server, and the subscription request is used to request to subscribe to the information of the application instance, so that when the information of the application instance in the edge enabling server is updated, the edge
  • the network configuration server may notify the edge-enabled server of the information of the application instance.
  • 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 to notify the edge network configuration server 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 function 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 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. 3 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 some or all of the interface functions of the connection point 4; for example, the seventh interface 117 in FIG. 1D may include some or all of the interface functions of the connection point 4.
  • the application instance server when the application instance server implements the API open 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 The communication type, API interface information (IP address and port number) and protocol information.
  • API information for example, the name of the API, the type of the API, the version number of the API, and the API The communication type, API interface information (IP address and port number) and protocol information.
  • 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 release response may indicate whether the API release 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 application instance.
  • 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 the instance of the application, the first API publishing request carries the 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 application instance may include the identification information of the application instance in step 803 and the IP address of the application instance, and the information of the application instance may also include the access identification information of the edge network or the edge network information. 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 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, 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.
  • edge network configuration server may use the following methods to reuse 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 Figure 6A, and the edge enable server can implement the functions of one or more functional modules in the API service domain in Figure 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 part or all of the interface functions of the connection point 4; for example, the reference point 5 in FIG. It includes part or all of the interface functions of the connection point 4; for example, the first interface 111 in 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 the aforementioned FIG. 3 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 software modules.
  • 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 also 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 Information and 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 apparatus 90 for acquiring 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 discovers
  • the 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 and API, examples of the application include the first instance and the second instance.
  • the information acquisition device 90 can reuse the discovery mechanism in the API general framework CAPIF.
  • 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 thus 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, the first API discovery response including 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 device 90 for acquiring information can reuse the discovery mechanism in the API general framework CAPIF, but also that the information of the first instance is carried in the first API discovery response or the second API discovery response. in.
  • 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 application instance. Therefore, signaling overhead can be saved, and the delay of access applications caused by increased signaling can be reduced.
  • the receiving module 901 is specifically configured to: receive a first API publishing request from the second server, the first API publishing request includes information about the first instance of the application, and the first API publishing request 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 about 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 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, or to include the second instance The information is carried in the second API release request.
  • the information acquisition device 90 can use existing signaling to receive the information of the application instance from other information acquisition devices (for example, the second server, the third server), and other information acquisition 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 applications caused by increased signaling can be reduced.
  • 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 further 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 obtaining 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, thereby slowing down the increase in information. Network delay caused by the order.
  • the information acquiring apparatus 90 can 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 for the first device to obtain the information of the application instance is optimized.
  • the sending module 903 is further configured to send one or more of the following to the first device: access identification information of the first edge network, 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.
  • One or more of information, the IP address of the edge network, or the IP address of the edge-enabled server is increased, so that the information of the application instance that the information obtaining apparatus 90 sends to the first device can better satisfy the first device.
  • Equipment requirements the diversity of the information provided by the information obtaining apparatus 90 to the first device is increased, so that the information of the application instance that the information obtaining apparatus 90 sends to the first device can better satisfy the first device. Equipment requirements.
  • 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, wherein:
  • 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 information acquiring apparatus 100 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 of the information acquired by the information acquiring apparatus 100 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 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 first instance server of the application.
  • the processing module 1002 is also used to determine the first information. In such an implementation manner, the manner in which the information obtaining apparatus 100 obtains the information of the first instance of the application is clarified.
  • the identification information of the first instance in the information of the first instance and the IP address of the first instance may be 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. In such an embodiment, the information of the first instance is obtained by the apparatus 100 for obtaining information from different servers. Therefore, the information acquiring apparatus 100 can ensure the integrity of the information of the first instance.
  • the apparatus 100 for acquiring information further includes: the receiving module, configured to receive the information of the first instance from the first instance server of the application.
  • the apparatus 100 for obtaining information can directly obtain the information of the first instance from the first instance server of the application, that is, the apparatus 100 for obtaining information can 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, 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, and further reduce 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, and the first API discovery response includes the information of the first instance.
  • the device 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 be separately configured to send the information of the application instance. Therefore, signaling overhead can be saved, and the delay of access applications caused by increased signaling can be reduced.
  • 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 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 applications caused by increased signaling can be reduced.
  • 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, where 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 acquiring information may be the first server in the embodiment corresponding to FIG. 2, or the edge network configuration server in the embodiment corresponding to FIG. 4 to FIG. 5 or FIG. 7 to FIG. 8.
  • the first server or edge network configures the chip or system on chip on the 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 the method embodiments 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 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 technology 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.
  • Various components can be connected through 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 executed can also be regarded as driver programs 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 information acquiring apparatus 110 further includes an input/output device 1103, and the input/output device 1103 can be used for the information acquiring apparatus 110 to communicate with other devices.
  • the information of the first instance of the application is received from the second server, and 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 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 further 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.
  • one or more power supplies 1104 and/or one or more 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 steps shown in FIG. 11 The structure of the information acquisition device 110.
  • 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 Information and 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, or the edge-enabled server in the embodiment corresponding to FIG. 4 to FIG. 5 or FIG. 7 to FIG. 8, or the The chip or system on 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 functions 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 one storage device 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 obtaining apparatus 120 further includes an input/output device 1203, which can be used for the information obtaining 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 edge-enabled server can be based on the steps shown in FIG. 12
  • the structure of the apparatus 120 for obtaining information can be based on the steps 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 FIG. 2, FIG. 4 to FIG. 5, and FIG. 7 to FIG. 8 has similar functions to the foregoing second server, and the third server performs The steps may also be based on the structure of the apparatus 120 for obtaining information shown in FIG. 12.
  • 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: central processing unit, microprocessor, digital signal processing (DSP), microcontroller (microcontroller unit, MCU), or artificial intelligence processor, etc.
  • DSP digital signal processing
  • MCU microcontroller unit
  • Artificial intelligence processor etc.
  • Each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the processor can be built in a system on chip (SoC) or an application specific integrated circuit (ASIC), or it can 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
  • PLD 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 Any one or any combination of these can run necessary software or do 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

一种获取信息的方法及装置 技术领域
本申请实施例涉及通信领域，尤其涉及一种获取信息的方法及装置。
背景技术
随着移动互联网和物联网的快速发展，为了解决终端设备计算能力有限和存储能力有限以及能耗等问题，需要将高复杂度、高能耗计算任务迁移至云计算数据中心的服务器，从而降低终端设备的能耗，延长该终端设备的待机时长。然而，将计算任务迁移至云计算数据中心的服务器的方式不仅会造成大量的数据传输而增加网络负荷，还会带来数据传输时延而影响时延敏感的业务。因此，为了有效解决移动互联网和物联网快速发展带来的高网络负荷、高带宽以及低时延等要求，提出了多接入边缘计算(multi-access edge computing，MEC)的概念。该多接入边缘计算技术可以通过在无线接入侧部署通用服务器，从而为无线接入网提供信息技术(information technology，IT)的能力和云计算的能力。
在多接入边缘计算技术的系统架构中，一个应用可以对应一个实例或多个实例。当一个应用对应多个实例时，该多个实例中的每个实例分别由一个边缘使能服务器管理。当其他设备需要获取该应用的多个实例的信息时，需要通过分别查询管理上述多个实例的多个边缘使能服务器来获取。由此，会带来大量的信令开销以及业务的时延，从而影响用户的体验。
发明内容
本申请实施例提供了一种获取信息的方法，用于获取并保存应用的实例的信息，以使得用户可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
第一方面，本申请实施例提供了一种获取信息的方法，该方法的实施主体包括第一服务器、第二服务器和第三服务器。其中，该第一服务器为服务第二服务器和第三服务器的服务器。该第一服务器可以从第二服务器接收应用的第一实例的信息，并且，第一服务器可以从第三服务器接收该应用的第二实例的信息。其中，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置；该第二实例的信息包括该应用的标识信息和第二信息，该第二信息用于指示该第二实例的位置。然后，该第一服务器将保存该第一实例的信息和该第二实例的信息。因此，解决了该应用的第一实例的信息和该应用的第二实例的信息的保存问题。
本申请实施例中，由于，管理应用的实例的信息的第一服务器可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存于该第一服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该第一服务器向其他设备(例如第一设备)发送该应 用的实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
根据第一方面，本申请实施例第一方面的第一种实施方式中，该第一信息包括该第一实例的互联网协议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网元。
根据第二方面、第二方面的第一种实施方式至第二方面的第十二种实施方式中的任意一种实施方式，本申请实施例第一方面的第十五种实施方式中，该第二服务器为如下任意一项：应用实例管理网元，该应用实例管理网元为用于部署所述应用实例的网元；或者， 边缘使能服务器管理网元，该边缘使能服务器管理网元用于管理该边缘使能服务器。
本实施方式中，提出该第二服务器还可以是除了边缘网络之外的其他网元，例如，应用实例管理网元或边缘使能服务器管理网元。因此，该前述实施方式还可以适用于该第一服务器与边缘网络之外的网络的信令交互流程。
第三方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以实现上述方法中第一服务器的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，上述获取信息的装置的结构中包括处理器和收发器，该处理器被配置为处理该获取信息的装置执行上述方法中相应的功能。该收发器用于实现上述获取信息的装置与第二服务器或第三服务器之间的通信。该获取信息的装置还可以包括存储器，该存储器用于与处理器耦合，其保存该获取信息的装置必要的程序指令和数据。
第四方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以实现上述方法中第二服务器的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，上述获取信息的装置的结构中包括处理器和收发器，该处理器被配置为处理该获取信息的装置执行上述方法中相应的功能。该收发器用于实现上述获取信息的装置与第一服务器和应用实例服务器之间的通信。该获取信息的装置还可以包括存储器，该存储器用于与处理器耦合，其保存该获取信息的装置必要的程序指令和数据。
第五方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以是第一服务器，也可以是第一服务器内的芯片。该获取信息的装置可以包括处理模块和收发模块。当该获取信息的装置是第一服务器时，该处理模块可以是处理器，该收发模块可以是收发器；该第一服务器还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理模块执行该存储模块所存储的指令，以使该第一服务器执行第一方面或第一方面的任一种实施方式所介绍的方法。当该获取信息的装置是第一服务器内的芯片时，该处理模块可以是处理器，该收发模块可以是输入/输出接口、管脚或电路等；该处理模块执行存储模块所存储的指令，以使该第一服务器执行第一方面或第一方面的任一种实施方式所介绍的方法。此外，该存储模块可以是该芯片内的存储模块(例如，寄存器、缓存等)，也可以是该第一服务器内的位于该芯片外部的存储模块(例如，只读存储器、随机存取存储器等)。
第六方面，本申请实施例提供了一种获取信息的装置，该获取信息的装置可以是第二服务器，也可以是第二服务器内的芯片。该获取信息的装置可以包括处理模块和收发模块。当该获取信息的装置是第二服务器时，该处理模块可以是处理器，该收发模块可以是收发器；该车联网获取信息的装置还可以包括存储模块，该存储模块可以是存储器；该存储模块用于存储指令，该处理模块执行该存储模块所存储的指令，以使该第二服务器执行第二方面或第二方面的任一种实施方式所介绍的方法。当该获取信息的装置是第二服务器内的芯片时，该处理模块可以是处理器，该收发模块可以是输入/输出接口、管脚或电路等；该处理模块执行存储模块所存储的指令，以使该第二服务器执行第二方面或第二方面的任一 种实施方式中所介绍的方法。该存储模块可以是该芯片内的存储模块(例如，寄存器、缓存等)，也可以是第二服务器内的位于该芯片外部的存储模块(例如，只读存储器、随机存取存储器等)。
第七方面，本申请实施例提供了一种通信系统，该通信系统包括：第一服务器、第二服务器和第三服务器；该第二服务器，用于获取应用的第一实例的信息；该第三服务器，用于获取应用的第二实例的信息；该第一服务器，用于从该第二服务器和该第三服务器接收该应用的第一实例的信息和该应用的第二实例的信息，并保存该应用的第一实例的信息和该应用的第二实例的信息。
根据第七方面，本申请实施例第七方面的第一种实施方式中，该车联网网络设备可以实现如第五方面、第七方面或第九方面所涉及的网络设备的功能。
根据第七方面或第七方面的第一种实施方式，本申请实施例第七方面的第二种实施方式中，该第一服务器可以实现如第一方面以及第一方面中任意一种实施方式所涉及的第一服务器的功能。
根据第七方面或第七方面的第一种实施方式，本申请实施例第七方面的第三种实施方式中，该第二服务器可以实现如第二方面以及第二方面中任意一种实施方式所涉及的第二服务器的功能。
第八方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得该计算机执行如前述第一方面以及第一方面中任意一种实施方式、或第二方面以及第二方面中任意一种实施方式所介绍的方法。
第九方面，本申请实施例提供了一种计算机可读存储介质，包括指令，当该指令在计算机上运行时，以使得计算机执行如前述第一方面以及第一方面中任意一种实施方式或第二方面以及第二方面中任意一种实施方式所介绍的方法。
从以上技术方案可以看出，本申请实施例具有以下优点：
本申请实施例中，由于，管理应用的实例的信息的第一服务器可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存于该第一服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该第一服务器向其他设备(例如第一设备)发送该应用实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例。
图1A为本申请实施例中提供的一个系统架构图；
图1B为本申请实施例中获取信息的方法的一个流程图；
图1C为本申请实施例中获取信息的方法的另一个系统架构图；
图1D为本申请实施例中获取信息的方法的另一个系统架构图；
图2为本申请实施例中获取信息的方法的另一个流程图；
图3为本申请实施例中获取信息的方法适应的另一个系统架构图；
图4为本申请实施例中获取信息的方法的另一个流程图；
图5为本申请实施例中获取信息的方法的另一个流程图；
图6A为本申请实施例中获取信息的方法适应的另一个系统架构图；
图6B为本申请实施例中获取信息的方法适应的另一个系统架构图；
图6C为本申请实施例中获取信息的方法适应的另一个系统架构图；
图7为本申请实施例中获取信息的方法的另一个流程图；
图8为本申请实施例中获取信息的方法的另一个流程图；
图9为本申请实施例中获取信息的装置的一个实施例示意图；
图10为本申请实施例中获取信息的装置的另一个实施例示意图；
图11为本申请实施例中获取信息的装置的另一个实施例示意图；
图12为本申请实施例中获取信息的装置的另一个实施例示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例提供了一种获取信息的方法，用于获取并保存应用的实例的信息，以使得用户可以直接从该第一服务器中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
为便于理解，下面先对本申请实施例所涉及的部分技术术语进行解释：
应用(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以及后续步骤。
为便于进一步理解，下面将以该第一服务器为边缘网络配置服务器、第二服务器为边缘使能服务器和该第一设备为用户设备的实现方式进行进一步介绍。具体地，如图3所示， 该多接入边缘计算网络架构主要包括：边缘网络配置服务器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网络连接。
下面将以前述图3所示的系统架构为基础，介绍当边缘网络配置服务器和边缘使能服务器之间的消息基于请求-响应机制时的流程，具体如图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类似，具体此处不再赘述。
本实施例中，由于，管理应用的实例的信息的边缘网络配置服务器可以从边缘使能服务器接收应用的实例的信息，并将获取的应用实例的信息保存于该边缘网络配置服务器中。因此，解决了边缘网络中应用的实例的信息的保存问题。此外，由于该边缘网络配置服务器与该边缘使能服务器之间的信令交互基于请求-响应机制，该边缘网络配置服务器在需要获取应用的实例的信息时向该边缘使能服务器发送第一请求，该边缘使能服务器也可以基于该第一请求向该边缘网络配置服务器发送应用的实例的信息。因此，可以满足该边缘网络配置服务器获取应用的实例的需求，以进一步实现该边缘网络配置服务器保存该应用的实例的信息的功能。此外，该方法还使得该UE可以从该边缘网络配置服务器中获取到该应用的实例的信息，而无需从多个边缘使能服务器或其他服务器处获取该应用的实例的信息，进而可以节省该UE获取该应用的实例的信息的信令开销，进而减少接入应用的延迟。
下面将以前述图3所示的系统架构为基础，介绍当边缘网络配置服务器和边缘使能服务器之间的消息基于订阅-通知机制时的流程，具体如图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获取该应用实例的信息的信令开销，进而减少接入应用的延迟。
本申请实施例所提出的获取信息的方法除了可以适用于前述图3所示的系统，还可以与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通用架构核心功能CCF601通过连接点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提供商域2中的一个或多个功能模块的功能，例如，该应用实例服务器实现API发布功能。此时，边缘使能服务器和边缘网络配置服务器之间的接口包含连接点6或连接点6e的部分或全部接口功能，例如，前述图3中的参考点5可以包含连接点6或连接点6e的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点6或连接点6e的部分或全部接口功能。
701、应用实例服务器向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。
本实施例中，由于，应用实例服务器可以实现图6B或图6C中的API服务域2中的一个或多个功能模块的功能，因此，该应用实例服务器可以通过不同的接口向边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。例如，当该应用实例服务器实现API发布功能时，应用实例服务器通过连接点4向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址。此时，边缘使能服务器和应用实例服务器之间的接口包含连接点4的部分或全部接口功能，例如，前述图3中的参考点3可以包含连接点4的部分或全部接口功能；例如，前述图1C或图1D中的第四接口114可以包含连接点4的部分或全部接口功能；例如，前述图1D中的第七接口117可以包含连接点4的部分或全部接口功能。此外，当该应用实例服务器实现API开放功能时，应用实例服务器通过连接点3向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址；当该应用实例服务器实现API管理功能时，应用实例服务器通过连接点5向该边缘使能服务器发送应用的实例的标识信息和该应用的实例的IP地址，具体此处不做限定。
702、边缘网络配置服务器向边缘使能服务器发送第一API发现请求。
本实施例中，边缘网络配置服务器通过连接点6或连接点6e向边缘使能服务器发送第一API发现请求(service API publish 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 publish 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的部分或全部接口功能，例如，前述图3中的参考点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的部分或全部接口功能，例如，前述图3中的参考点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的部分或全部接口功能；例如，前述图3中的参考点5可以包含连接点4的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点4的部分或全部接口功能。可选的，该应用实例服务器可以实现API调用实体的功能，并且，该应用实例服务器通过连接点1e与边缘网络配置服务器连接，该应用实例服务器通过连接点2e与边缘使能服务器连接。该应用实例服务器可以实现API调用实体的功能，此时，该应用实例服务器可以通过连接点1e与边缘网络配置服务器连接。
此外，还存在一些实施方式，该边缘网络配置服务器可以直接从该应用实例服务器获取该应用的实例的信息。此时，可以采用如下方式复用CAPIF架构中的功能模块。
具体地，边缘网络配置服务器可以实现图6A中的API通用架构核心功能的功能，该应用实例服务器可以实现图6A中的API服务域中的一个或多个功能模块的功能，此时，该应用实例服务器和边缘网络配置服务器之间的接口可以为连接点3、连接点4或连接点5。例如，该应用实例服务器实现API发布功能，此时，应用实例服务器和边缘网络配置服务器之间的接口包含连接点4的部分或全部接口功能；例如，前述图3中的参考点5可以包含连接点4的部分或全部接口功能；例如，前述图1A或图1C或图1D中的第一接口111可以包含连接点4的部分或全部接口功能。
上述实施例中，分别从各个服务器或网元本身、以及从各个服务器或网元之间交互的角度对本申请实施例提供的方法的各方案进行了介绍。可以理解的是，前述服务器或设备，例如前述第一服务器、第二服务器、第三服务器、第一设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
如图9所示，本实施例提供了一种获取信息的装置90，该获取信息的装置90可以通过软件模块来实现相应的功能。此时，该获取信息的装置90可以为第一服务器中的芯片或片上系统。该获取信息的装置90可包括接收模块901和处理模块902，其中：
该接收模块901，用于从第二服务器接收应用的第一实例的信息，该第一实例的信息包括该应用的标识信息和第一信息，该第一信息用于指示该第一实例的位置；该接收模块901，还用于从第三服务器接收该应用的第二实例的信息，该第二实例的信息包括该应用的 标识信息和第二信息，该第二信息用于指示该第二实例的位置，该第一服务器为服务该第二服务器和该第三服务器的服务器。
此外，该处理模块902，用于保存该第一实例的信息和该第二实例的信息。
由此，本实施例中的获取信息的装置90可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该获取信息的装置90向其他设备(例如第一设备)发送该应用的实例的信息。当该其他设备需要获取该应用的实例的信息时，该其他设备可以直接从该获取信息的装置90中获取应用的实例的信息，而无需通过查询该第二服务器和该第三服务器获取应用的实例的信息，可以节省信令开销，减缓业务时延。
在一种可选的实施方式中，该获取信息的装置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获取应用的实例的信息，可以节省信令开销，减缓业务时延。
在一种可选的实施方式中，该获取信息的装置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对应的实施例中的第一服务器，也可以为图4至图5或图7至图8对应的实施例中的边缘网络配置服务器，也可以为该第一服务器或边缘网络配置服务器上的芯片或片上系统。
该获取信息的装置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等；前述图3中的参考点5或参考点4等。
可选的，该获取信息的装置110还可以包括一个或一个以上电源1104，和/或，一个或一个以上操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM等。
还应理解的是，上述图2、图4至图5以及图7至图8所对应的方法实施例中，该第一服务器或边缘网络配置服务器所执行的步骤均可以基于该图11所示的获取信息的装置110结构。
由此，本实施例中的获取信息的装置110可以分别从第二服务器和第三服务器接收应用的第一实例的信息和该应用的第二实例的信息，并将该应用的第一实例的信息和该应用的第二实例的信息保存。因此，解决了边缘网络中应用的实例的信息的保存问题，便于该获取信息的装置90向其他设备(例如第一设备)发送该应用的实例的信息。
如图12所示，本实施例提供了另一种获取信息的装置120的结构示意图。该获取信息的装置120可以为前述图2对应的实施例中的第二服务器，也可以为图4至图5或图7至 图8对应的实施例中的边缘使能服务器，也可以为该第二服务器或边缘使能服务器上的芯片或片上系统。
该获取信息的装置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；前述图3中的参考点1、参考点2、参考点3或参考点5等。
可选的，该获取信息的装置120还可以包括一个或一个以上电源1204，和/或，一个或一个以上操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM等。
还应理解的是，上述图2、图4至图5以及图7至图8所对应的方法实施例中，该第二服务器或边缘使能服务器所执行的步骤均可以基于该图12所示的获取信息的装置120结构。
由此，本实施例中的获取信息的装置120可以将获取的应用的第一实例的信息发送给该第一服务器，以使得该第一服务器可以及时保存该获取信息的装置120发送的第一实例的信息。因此，有利于该第一服务器保存该边缘网络中应用的实例的信息，便于该第一服务器向其他设备(例如第一设备)发送该应用的实例的信息。此外，还可以使其他设备(例如第一设备)无需从该获取信息的装置120中获取该应用的实例的信息，而是可以直接从该第一服务器中获取该应用的实例的信息，因此，可以节省该第一服务器获取该应用的实例的信息的流程。
还应理解的是，上述图2、图4至图5以及图7至图8所对应的方法实施例中的第三服务器与前述第二服务器所实现的功能类似，该第三服务器所执行的步骤也可以基于该图12所示的获取信息的装置120结构。
以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。所述处理器可以包括但不限于以下至少一种：中央处理单元、微处理器、数字信号处理器(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 (30)

  1. 一种获取信息的方法，其特征在于，包括：
    第一服务器从第二服务器接收应用的第一实例的信息，所述第一实例的信息包括所述应用的标识信息和第一信息，所述第一信息用于指示所述第一实例的位置；
    所述第一服务器从第三服务器接收所述应用的第二实例的信息，所述第二实例的信息包括所述应用的标识信息和第二信息，所述第二信息用于指示所述第二实例的位置，所述第一服务器为服务所述第二服务器和所述第三服务器的服务器；
    所述第一服务器保存所述第一实例的信息和所述第二实例的信息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一信息包括所述第一实例的互联网协议IP地址和如下一项或多项：
    第一边缘网络的接入标识信息、所述第一边缘网络的IP地址、或第一边缘使能服务器的IP地址，所述第二服务器位于所述第一边缘网络中；
    所述第二信息包括所述第二实例的IP地址和如下一项或多项：
    第二边缘网络的接入标识信息、所述第二边缘网络的IP地址、或第二边缘使能服务器的IP地址，所述第三服务器位于所述第二边缘网络中。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述第一服务器向所述第二服务器发送第一应用程序接口API发现请求，所述第一API发现请求包括发现类型信息，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例，或，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例和API，所述应用的实例包括所述第一实例和所述第二实例；
    所述第一服务器向所述第三服务器发送所述第一API发现请求。
  4. 根据权利要求3所述的方法，其特征在于，
    所述第一服务器从所述第二服务器接收应用的第一实例的信息，包括：
    所述第一服务器从所述第二服务器接收第一API发现响应，所述第一API发现响应包括所述第一实例的信息；
    所述第一服务器从所述第三服务器接收应用的第二实例的信息，包括：
    所述第一服务器从所述第三服务器接收第二API发现响应，所述第二API发现响应包括所述第二实例的信息。
  5. 根据权利要求1所述的方法，其特征在于，
    所述第一服务器从第二服务器接收应用的第一实例的信息，包括：
    所述第一服务器从所述第二服务器接收第一API发布请求，所述第一API发布请求包括所述应用的第一实例的信息，所述第一API发布请求用于发布所述API和/或所述第一实例；
    所述第一服务器从第三服务器接收应用的第二实例的信息，包括：
    所述第一服务器从所述第三服务器接收第二API发布请求，所述第二API发布请求包括所述应用的第二实例的信息，所述第二API发布请求用于发布所述API和/或所述第二实例。
  6. 根据权利要求1至5中任意一项所述的方法，其特征在于，
    所述应用的第一实例的信息还包括如下一项或多项：
    第一边缘使能服务器的标识信息，或者，所述第一实例的服务范围信息；
    所述应用的第二实例的信息还包括如下一项或多项：
    第二边缘使能服务器的标识信息，或者，所述第二实例的服务范围信息。
  7. 根据权利要求1至6所述的方法，其特征在于，所述方法还包括：
    所述第一服务器从第一设备接收所述应用的标识信息和所述第一设备的位置信息；
    所述第一服务器向所述第一设备发送第三实例的IP地址，所述第三实例由所述应用的标识信息、所述第一设备的位置信息、所述应用的第一实例的信息和所述应用的第二实例的信息确定，所述第三实例为所述第一实例或所述第二实例。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    当所述第三实例的IP地址为所述第一实例的IP地址时，所述第一服务器向所述第一设备发送如下一项或多项：
    所述第一边缘网络的接入标识信息、所述第一边缘网络的IP地址、或所述第一边缘使能服务器的IP地址；
    当所述第三实例的IP地址为所述第二实例的IP地址时，所述第一服务器向所述第一设备发送如下一项或多项：
    所述第二边缘网络的接入标识信息、所述第二边缘网络的IP地址、或所述第二边缘使能服务器的IP地址。
  9. 一种获取信息的方法，其特征在于，包括：
    第二服务器获取应用的第一实例的信息，所述第一实例的信息包括所述应用的标识信息和第一信息，所述第一信息用于指示所述第一实例的位置；
    所述第二服务器向第一服务器发送所述第一实例的信息，所述第一服务器为服务所述第二服务器的服务器。
  10. 根据权利要求9所述的方法，其特征在于，所述第一信息包括所述第一实例的互联网协议IP地址和如下一项或多项：
    第一边缘网络的接入标识信息、所述第一边缘网络的IP地址、或第一边缘使能服务器的IP地址，所述第二服务器位于所述第一边缘网络中。
  11. 根据权利要求9或10所述的方法，其特征在于，所述第二服务器获取应用的第一实例的信息，包括：
    所述第二服务器从所述应用的第一实例服务器接收所述第一实例的标识信息和所述第一实例的IP地址；
    所述第二服务器从所述第二服务器获取所述第一信息。
  12. 根据权利要求9或10所述的方法，其特征在于，所述第二服务器获取应用的第一实例的信息，包括：
    所述第二服务器从所述应用的第一实例服务器接收所述第一实例的信息。
  13. 根据权利要求9至12中任意一项所述的方法，其特征在于，还包括：
    所述第二服务器从所述第一服务器接收第一应用程序接口API发现请求，所述第一API发现请求包括发现类型信息，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例，或，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例和API，所述应用的实例包括所述第一实例。
  14. 根据权利要求13所述的方法，其特征在于，
    所述第二服务器向第一服务器发送所述第一实例的信息，包括：
    所述第二服务器向第一服务器发送第一API发现响应，所述第一API发现响应包括所述第一实例的信息。
  15. 根据权利要求9至12中任意一项所述的方法，其特征在于，
    所述第二服务器向第一服务器发送所述第一实例的信息，包括：
    所述第二服务器向所述第一服务器发送第一API发布请求，所述第一API发布请求包括所述应用的第一实例的信息，所述第一API发布请求用于发布所述API和/或所述第一实例。
  16. 根据权利要求15所述的方法，其特征在于，所述第二服务器获取应用的第一实例的信息，包括：
    所述第二服务器从应用的第一实例服务器接收第三API发布请求，所述第三API发布请求包括所述第一实例的标识信息和所述第一实例的IP地址，所述第三API发布请求用于发布API和/或所述第一实例。
  17. 根据权利要求9至16中任意一项所述的方法，其特征在于，所述应用的第一实例的信息还包括如下一项或多项：
    第一边缘使能服务器的标识信息，或者，所述第一实例的服务范围信息。
  18. 一种获取信息的装置，其特征在于，包括：
    接收模块，用于从第二服务器接收应用的第一实例的信息，所述第一实例的信息包括所述应用的标识信息和第一信息，所述第一信息用于指示所述第一实例的位置；
    所述接收模块，还用于从第三服务器接收所述应用的第二实例的信息，所述第二实例的信息包括所述应用的标识信息和第二信息，所述第二信息用于指示所述第二实例的位置，所述第一服务器为服务所述第二服务器和所述第三服务器的服务器；
    处理模块，用于保存所述第一实例的信息和所述第二实例的信息。
  19. 根据权利要求18所述的获取信息的装置，其特征在于，所述获取信息的装置还包括：
    发送模块，用于向所述第二服务器发送第一应用程序接口API发现请求，所述第一API发现请求包括发现类型信息，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例，或，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例和API，所述应用的实例包括所述第一实例和所述第二实例；
    所述发送模块，还用于向所述第三服务器发送所述第一API发现请求。
  20. 根据权利要求18所述的获取信息的装置，其特征在于，所述接收模块，具体用于：
    从所述第二服务器接收第一API发布请求，所述第一API发布请求包括所述应用的第 一实例的信息，所述第一API发布请求用于发布所述API和/或所述第一实例；
    从所述第三服务器接收第二API发布请求，所述第二API发布请求包括所述应用的第二实例的信息，所述第二API发布请求用于发布所述API和/或所述第二实例。
  21. 根据权利要求18至20所述的获取信息的装置，其特征在于，
    所述接收模块，还用于从第一设备接收所述应用的标识信息和所述第一设备的位置信息；
    所述发送模块，还用于向所述第一设备发送第三实例的IP地址，所述第三实例由所述应用的标识信息、所述第一设备的位置信息、所述应用的第一实例的信息和所述应用的第二实例的信息确定，所述第三实例为所述第一实例或所述第二实例。
  22. 根据权利要求21所述的获取信息的装置，其特征在于，所述发送模块，还用于：
    向所述第一设备发送如下一项或多项：
    所述第一边缘网络的接入标识信息、所述第一边缘网络的IP地址、或所述第一边缘使能服务器的IP地址；
    向所述第一设备发送如下一项或多项：
    所述第二边缘网络的接入标识信息、所述第二边缘网络的IP地址、或所述第二边缘使能服务器的IP地址。
  23. 一种获取信息的装置，其特征在于，包括：
    处理模块，用于获取应用的第一实例的信息，所述第一实例的信息包括所述应用的标识信息和第一信息，所述第一信息用于指示所述第一实例的位置；
    发送模块，用于向第一服务器发送所述第一实例的信息，所述第一服务器为服务所述第二服务器的服务器。
  24. 根据权利要求23所述的获取信息的装置，其特征在于，所述获取信息的装置还包括：
    接收模块，用于从所述应用的第一实例服务器接收所述第一实例的标识信息和所述第一实例的IP地址；
    所述处理模块，还用于确定所述第一信息。
  25. 根据权利要求23所述的获取信息的装置，其特征在于，所述获取信息的装置还包括：
    所述接收模块，用于从所述应用的第一实例服务器接收所述第一实例的信息。
  26. 根据权利要求23至25中任意一项所述的获取信息的装置，其特征在于，所述接收模块，还用于从所述第一服务器接收第一应用程序接口API发现请求，所述第一API发现请求包括发现类型信息，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例，或，所述发现类型信息用于指示所述第一API发现请求用于请求所述应用的实例和API，所述应用的实例包括所述第一实例。
  27. 根据权利要求23至26中任意一项所述的获取信息的装置，其特征在于，所述发送模块，具体用于向所述第一服务器发送第一API发布请求，所述第一API发布请求包括所述应用的第一实例的信息，所述第一API发布请求用于发布所述API和/或所述第一实例。
  28. 根据权利要求27所述的获取信息的装置，其特征在于，所述处理模块，具体用于从应用的第一实例服务器接收第三API发布请求，所述第三API发布请求包括所述第一实例的标识信息和所述第一实例的IP地址，所述第三API发布请求用于发布API和/或所述第一实例。
  29. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行如权利要求1至17中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至17中任一项所述的方法。
PCT/CN2019/101650 2019-08-20 2019-08-20 一种获取信息的方法及装置 WO2021031127A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
PCT/CN2019/101650 WO2021031127A1 (zh) 2019-08-20 2019-08-20 一种获取信息的方法及装置
EP20854354.6A EP4016961A4 (en) 2019-08-20 2020-03-24 METHOD AND MECHANISM FOR OBTAINING INFORMATION
CN202080058580.3A CN114270789B (zh) 2019-08-20 2020-03-24 一种获取信息的方法及装置
PCT/CN2020/080966 WO2021031562A1 (zh) 2019-08-20 2020-03-24 一种获取信息的方法及装置
PCT/CN2020/127921 WO2021189869A1 (zh) 2019-08-20 2020-11-10 一种获取信息的方法及装置
CN202080054615.6A CN114175600B (zh) 2019-08-20 2020-11-10 一种获取信息的方法及装置
US17/675,705 US20220174585A1 (en) 2019-08-20 2022-02-18 Information Obtaining Method And Apparatus

Applications Claiming Priority (1)

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

Publications (1)

Publication Number Publication Date
WO2021031127A1 true WO2021031127A1 (zh) 2021-02-25

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 After (2)

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

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
US20210081770A1 (en) * 2019-09-17 2021-03-18 GOWN Semiconductor Corporation System architecture based on soc fpga for edge artificial intelligence computing

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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)
WO2023141827A1 (en) * 2022-01-26 2023-08-03 Huawei Technologies Co., Ltd. Area of interest-specific information for mulit-access edge computing
CN114884941B (zh) * 2022-04-12 2023-09-05 中国电信股份有限公司 针对边缘计算平台的业务处理方法、装置、系统及介质
CN116528397B (zh) * 2023-06-29 2023-09-19 新华三技术有限公司 5g双域专网的实现方法及装置、5g双域专网系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107566437A (zh) * 2016-07-01 2018-01-09 大唐移动通信设备有限公司 信息传输方法及装置
CN109257193A (zh) * 2017-07-11 2019-01-22 中国移动通信有限公司研究院 边缘缓存管理方法、个人云系统和计算机可读存储介质
WO2019104280A1 (en) * 2017-11-27 2019-05-31 Intel IP Corporation Multi-access edge computing (mec) based multi-operator support for c-v2x systems
CN110098947A (zh) * 2018-01-31 2019-08-06 华为技术有限公司 一种应用的部署方法、设备及系统

Family Cites Families (20)

* 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
US8621042B2 (en) * 2010-12-27 2013-12-31 Limelight Networks, Inc. Anycast redirect to unicast content download
US8949307B2 (en) * 2011-11-15 2015-02-03 Google Inc. Cloud-to-device messaging for application activation and reporting
CN111163133B (zh) * 2015-08-28 2022-03-11 华为技术有限公司 网络系统和网络通信的方法
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
US10841208B2 (en) * 2016-08-05 2020-11-17 Huawei Technologies Co., Ltd. Slice/service-based routing in virtual networks
CN109952741A (zh) * 2016-10-05 2019-06-28 康维达无线有限责任公司 服务实例化的能力暴露
CN108574728B (zh) * 2017-03-08 2021-05-04 中兴通讯股份有限公司 用于移动边缘计算的流量路径改变检测的方法和装置
CN113194157B (zh) * 2017-06-30 2022-10-28 华为技术有限公司 一种应用实例地址的转换方法和装置
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 华为技术有限公司 移动边缘主机服务通知方法和装置
CN109862581B (zh) * 2017-11-30 2022-05-17 华为技术有限公司 一种通信方法及装置
CN109981316B (zh) * 2017-12-27 2022-11-25 华为技术有限公司 应用服务器的切换方法及会话管理网元、终端设备
CN110049070B (zh) * 2018-01-15 2021-09-14 华为技术有限公司 事件通知方法及相关设备
CN110120879B (zh) * 2018-02-06 2020-12-01 华为技术有限公司 一种应用服务水平协议的保障方法、设备及系统
CN110730499B (zh) * 2018-07-16 2021-06-15 华为技术有限公司 一种mec信息获取方法及装置
CN109040312B (zh) * 2018-09-17 2021-03-23 云迅智能科技南京有限公司 一种多接入边缘计算网络系统及方法
CN109831548B (zh) * 2019-03-18 2022-02-18 中国联合网络通信集团有限公司 虚拟内容分发网络vCDN节点建立方法及服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107566437A (zh) * 2016-07-01 2018-01-09 大唐移动通信设备有限公司 信息传输方法及装置
CN109257193A (zh) * 2017-07-11 2019-01-22 中国移动通信有限公司研究院 边缘缓存管理方法、个人云系统和计算机可读存储介质
WO2019104280A1 (en) * 2017-11-27 2019-05-31 Intel IP Corporation Multi-access edge computing (mec) based multi-operator support for c-v2x systems
CN110098947A (zh) * 2018-01-31 2019-08-06 华为技术有限公司 一种应用的部署方法、设备及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210081770A1 (en) * 2019-09-17 2021-03-18 GOWN Semiconductor Corporation System architecture based on soc fpga for edge artificial intelligence computing
US11544544B2 (en) * 2019-09-17 2023-01-03 Gowin Semiconductor Corporation System architecture based on SoC FPGA for edge artificial intelligence computing

Also Published As

Publication number Publication date
US20220174585A1 (en) 2022-06-02
CN114175600B (zh) 2023-06-20
WO2021031562A1 (zh) 2021-02-25
CN114175600A (zh) 2022-03-11
WO2021189869A1 (zh) 2021-09-30
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
WO2021031562A1 (zh) 一种获取信息的方法及装置
US20230171618A1 (en) Communication method and apparatus
WO2020015634A1 (zh) 一种mec信息获取方法及装置
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
WO2020224622A1 (zh) 一种信息配置方法及装置
WO2022152238A1 (zh) 一种通信方法及通信装置
US10999768B2 (en) Session context handling method, network element, and terminal device
KR20230141914A (ko) 에지 컴퓨팅 서버들의 효율적인 발견
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2022105897A1 (zh) 业务路径建立方法、通信装置及存储介质
US20240056496A1 (en) Method and Apparatus for Selecting Edge Application Server
WO2022022322A1 (zh) 访问本地网络的方法和装置
CN112954768B (zh) 通信方法、装置及系统
WO2023024931A1 (zh) 用于设备间通信的方法和装置
WO2022222745A1 (zh) 一种通信方法及装置
CN114071649B (zh) 访问本地网络的方法和装置
WO2021233395A1 (zh) 一种通信方法、装置及计算机可读存储介质
WO2021203794A1 (zh) 通信方法、装置及系统
WO2022067736A1 (zh) 一种通信方法及装置
WO2021081712A1 (zh) 一种dns查询方法及装置
WO2021244622A1 (zh) 一种通信方法、装置及计算机可读存储介质
WO2023143212A1 (zh) 一种通信方法及装置
WO2023082858A1 (zh) 确定移动性管理策略的方法、通信装置及通信系统
WO2023005440A1 (zh) 通信方法、通信装置及通信系统
WO2023061207A1 (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: 19942218

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

Country of ref document: EP

Kind code of ref document: A1