WO2023020249A1 - 获取边缘服务的方法和装置 - Google Patents

获取边缘服务的方法和装置 Download PDF

Info

Publication number
WO2023020249A1
WO2023020249A1 PCT/CN2022/108796 CN2022108796W WO2023020249A1 WO 2023020249 A1 WO2023020249 A1 WO 2023020249A1 CN 2022108796 W CN2022108796 W CN 2022108796W WO 2023020249 A1 WO2023020249 A1 WO 2023020249A1
Authority
WO
WIPO (PCT)
Prior art keywords
ecs
information
network element
ees
request information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/108796
Other languages
English (en)
French (fr)
Inventor
姚琦
雷扎加罗亚
宗在峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP22857561.9A priority Critical patent/EP4383779A4/en
Publication of WO2023020249A1 publication Critical patent/WO2023020249A1/zh
Priority to US18/443,404 priority patent/US20240187303A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/18—Network planning tools
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0226—Traffic management, e.g. flow control or congestion control based on location or mobility
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present application relates to the technical field of communications, and more specifically, to a method and device for obtaining edge services.
  • the user equipment generally adopts the following scheme to obtain edge services: the edge enabler client (edge enabler client, EEC), as a part of the UE, will first configure the edge configuration server (edge configuration server, ECS) on the EEC Then, the EEC sends a service provisioning request (service provisioning request) or a service subscription update request (service subscription update request) to the ECS to obtain the address information of the edge enabler server (EES), which is obtained by the UE or EEC After receiving the address information of the EES, the EEC sends an EAS discovery request (EAS discovery request) to the EES to obtain the address information of the edge application server (EAS) and further obtain edge services.
  • EAS edge enabler client
  • EAS edge application server
  • the UDM unified data management
  • SMF session management function
  • the address information of the ECS is preconfigured in EEC or UDM
  • the ECS that the UE wants to access is different from the preconfigured ECS, or the UE moves out of a certain
  • the service range of an ECS is exceeded, the UE cannot obtain edge services through the preconfigured ECS.
  • This application provides a method and device for obtaining edge services, which can enable other ECSs to be obtained when the configuration information of an ECS changes, or when a terminal device is in a roaming scene, or when a terminal device moves out of the service range of an ECS. edge services provided.
  • a method for obtaining edge services is provided.
  • the method may be executed by the first ECS, or may also be executed by a component configured in the first ECS (such as a chip or a chip system, etc.), which is not limited in the present application.
  • the method includes: if the first edge configuration server ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device, the first ECS obtains the information of the second ECS, the first ECS sends the first information to the first device, and the The first information includes information of the first EES or information of the second ECS, and the first EES is an EES managed by the second ECS.
  • the terminal device can obtain an ECS or EES that can provide edge services for the terminal device in the roaming scenario, or when the pre-configured ECS for the terminal device changes or the terminal device moves out of the service range of an ECS .
  • the first ECS acquires the information of the second ECS according to configuration information.
  • the first ECS configures the configuration files of other ECSs, so the information of the second ECS can be obtained according to the configured configuration files of other ECSs.
  • the first ECS sends a first request message to the federated control network element, the first request message is used to request information from the second ECS, and the first ECS receives information from the federated control network The first response information of the unit, where the first response information includes the information of the second ECS.
  • the ECS can register the configuration file to the federated control network element. Therefore, when the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device, it can query the federated control network element that can provide edge services for the terminal device. The EES of the service, so as to determine the ECS corresponding to the EES.
  • the first ECS sends second request information to the second ECS, where the second request information is used to request information about the first EES, and the first ECS receives information from the second ECS Second response information, where the second response information includes information about the first EES.
  • the first ECS when the first ECS obtains the information of the second ECS according to the local configuration or from the federal control network element, it requests the second ECS for an EES that can provide services for the terminal device.
  • the first ECS receives third request information from the first device, the third request information is used to request information of the first EES, and the first ECS receives the third request information according to the third request information It is determined that the EES managed by the first ECS cannot provide the edge service for the terminal device.
  • the first device may be a terminal device, EEC, or EES, which is not limited in this application.
  • the first device is a terminal device.
  • the terminal device obtains EES that can provide edge services for the terminal device from the pre-configured or network-delivered ECS (the first ECS)
  • the location of the terminal device may have moved, etc.
  • the EES managed by the first ECS cannot provide edge services for terminal devices.
  • the first ECS can obtain an EES that can provide edge services for terminal devices through local configuration, or query other ECSs from the federal control network element.
  • the first request information, the second request information, or the third request information includes at least one of the following: a public land mobile network PLMN identifier accessed by the terminal device, an edge computing service The identifier of the provider ECSP, the characteristic information of the first EES, and the application information.
  • a method for obtaining edge services is provided.
  • the method may be executed by the second ECS, or may also be executed by a component configured in the second ECS (such as a chip or a chip system, etc.), which is not limited in the present application.
  • the method includes: the second edge configuration server ECS receives second request information from the first ECS, the second request information is used to request information of the first EES, the second ECS determines the information of the first EES according to the second request information, The second ECS sends second response information to the first ECS, where the second response information includes information of the first EES.
  • the second request information includes at least one of the following: the identity of the public land mobile network PLMN accessed by the terminal device, the identity of the edge computing service provider ECSP, and the characteristics of the first EES Information, application information, location information of terminal equipment.
  • the second ECS determines the information of the first EES according to the second request information and a local ECS configuration file
  • the ECS configuration file includes at least one of the following: the address of the ECS Information, the service scope of the ECS, the EES configuration file managed by the ECS, the ECSP ID of the ECS, and the PLMN ID corresponding to the ECS.
  • the second ECS determines the information of the first EES according to the PLMN identifier in the second request information and the PLMN identifier in the ECS configuration file. Or the second ECS determines the information of the first EES according to the ECSP identifier in the second request information and the ECSP identifier in the ECS configuration file. Or the second ECS determines the information of the first EES according to the feature information of the first EES in the second request information and the EES configuration file managed by the ECS in the ECS configuration file. Or the second ECS determines the information of the first EES according to the application information in the second request information and the EES configuration file managed by the ECS in the ECS configuration file.
  • the second ECS determines the information of the first EES according to the location information of the terminal device in the second request information and the service range of the ECS in the ECS configuration file.
  • the second ECS may also determine the information of the first EES according to two or more items in the second request information, which is not limited in this application.
  • a method for obtaining edge services may be executed by a terminal device, or may also be executed by a component configured in the terminal device (such as a chip or a chip system, etc.), which is not limited in the present application.
  • the method includes: the terminal device sends the first request information to the first functional network element, the first request information is used to request the information of the first edge configuration server ECS, and the first functional network element is a federal control network element or the first ECS discovery For proxying, the first functional network element stores information about at least one ECS, and the terminal device receives first response information from the first functional network element, where the first response information includes information about the first ECS.
  • the ECS registers the configuration file on the first functional network element, so that the terminal device can obtain an ECS that can provide edge services for the terminal device.
  • the solution provided by this application It is not necessary for different operators to configure different ECSs for terminal equipment, and all terminal equipment can discover ECS through the first functional network element, which is more flexible and applicable to a wider range.
  • the terminal device acquires address information of the first functional network element.
  • the address information of the first functional network element can be configured in the terminal device, or in the EEC, or in the core network element. If the address information of the first functional network element is configured on the network element of the core network, the network element of the core network may send it to the terminal device.
  • the first request information includes at least one of the following: an identifier of the public land mobile network PLMN accessed by the terminal device, an edge computing service provider ECSP identifier, and location information of the terminal device .
  • a method for obtaining edge services may be executed by the first functional network element, or may also be executed by a component (such as a chip or a chip system) configured in the first functional network element, which is not limited in this application.
  • the method includes: a first functional network element receives first request information from a terminal device, the first request information is used to request information of a first edge configuration server ECS, and the first functional network element is a federal control network element or a first ECS Discovery agent, the first functional network element stores the information of at least one ECS, the first functional network element determines the first ECS according to the first request information, and the first functional network element sends the first response information to the terminal device, the first response information Include the information of the first ECS.
  • the first functional network element is a first ECS discovery agent
  • the first ECS discovery agent determines the information of the second ECS discovery agent according to the first request information and/or local configuration
  • the first ECS discovery agent sends second request information to the second ECS discovery agent
  • the second request information is used to request the information of the first ECS
  • the first ECS discovery agent receives the second response information from the second ECS discovery agent
  • the second response information includes information of the first ECS.
  • the ECS discovery agent stores configuration files of multiple ECSs, and the ECS discovery agent configures the information of other ECS discovery agents, so that the ECS discovery agents can interactively obtain the ECS information stored separately.
  • the first ECS discovery agent sends third request information to the federal control network element according to the first request information, and the third request information is used to request the second ECS discovery agent's information, the first ECS discovery agent receives third response information from the federal control network element, where the third response information includes information of the second ECS discovery agent.
  • the ECS discovery agent stores multiple ECS configuration files, and the ECS discovery agent registers with the federated control network element, so that the ECS discovery agent can query the federated control network element for information about other ECS discovery agents.
  • the first request information includes at least one of the following: a public land mobile network PLMN identifier accessed by the terminal device, an edge computing service provider ECSP identifier, and location information of the terminal device.
  • a method for obtaining edge services is provided.
  • the method may be executed by the first control plane core network element, or may also be executed by a component (such as a chip or chip system, etc.) configured in the first control plane core network element, which is not limited in this application.
  • the method includes: the first control plane core network element of the first network receives first indication information from the second control plane core network element of the second network, the first indication information indicating that the terminal device supports access to the first network edge service, the first control plane core network element sends the first request information to the third control plane core network element of the first network according to the first indication information, and the first request information is used to request the first The edge configuration server ECS information, the first control plane core network element receives first response information from the third control plane core network element, where the first response information includes the first ECS information.
  • the first network is the network of the visited domain
  • the second network is the network of the home domain
  • the control plane core network element of the network of the home domain informs the control plane core network of the network of the visited domain through instruction information Element
  • the terminal device supports access to the edge service of the first network, so as to obtain ECS information that can provide the edge service for the terminal device under the visited domain network.
  • the first request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an ECSP identifier of an edge computing service provider, and location information of the terminal device.
  • PLMN public land mobile network
  • a method for obtaining edge services is provided.
  • the method may be executed by a third control plane core network element, or may also be executed by a component (such as a chip or a chip system, etc.) configured in the third control plane core network element, which is not limited in this application.
  • the method includes: the third control plane core network element receives first request information from the first control plane core network element, the first request information is used to request information of the first edge configuration server ECS, the first request information Including at least one of the following: the PLMN identifier of the public land mobile network accessed by the terminal device, the ECSP identifier of the edge computing service provider, the location information of the terminal device, and the third control plane core network element determining the location of the first ECS according to the first request information information, the third control plane core network element sends first response information to the first control plane core network element, where the first response information includes information about the first ECS.
  • the core network element of the third control plane determines the information of the first ECS according to the PLMN identifier and the corresponding relationship between the PLMN identifier and the ECS, and/or, the third control plane The core network element determines the information of the first ECS according to the ECSP identifier and the corresponding relationship between the ECSP identifier and the ECS, and/or, the third control plane core network element determines the first ECS information according to the location information of the terminal device and the service range of the ECS. ECS information.
  • an apparatus for obtaining edge services may be the first ECS, or may also be a component configured in the first ECS (such as a chip or a chip system, etc.), which is not limited in this application.
  • the device includes a transceiver unit and a processing unit: if it is determined that the EES managed by the first ECS cannot provide edge services for the terminal device, the processing unit is used to acquire information of the second ECS, and the transceiver unit is used to send the first information to the first device , the first information includes the information of the first EES or the information of the second ECS, and the first EES is an EES managed by the second ECS.
  • the terminal device can obtain an ECS or EES that can provide edge services for the terminal device in the roaming scenario, or when the pre-configured ECS for the terminal device changes or the terminal device moves out of the service range of an ECS .
  • the processing unit is configured to acquire information of the second ECS according to configuration information.
  • the first ECS configures the configuration files of other ECSs, so the information of the second ECS can be obtained according to the configured configuration files of other ECSs.
  • the transceiver unit is further configured to send first request information to the federal control network element, where the first request information is used to request information about the second ECS, and the transceiver unit further uses For receiving the first response information from the federal control network element, the first response information includes the information of the second ECS.
  • the ECS can register the configuration file to the federated control network element. Therefore, when the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device, it can query the federated control network element that can provide edge services for the terminal device. The EES of the service, so as to determine the ECS corresponding to the EES.
  • the transceiver unit is further configured to send second request information to the second ECS, where the second request information is used to request information about the first EES, and the transceiver unit is also configured to Receive second response information from the second ECS, where the second response information includes information of the first EES.
  • the first ECS when the first ECS obtains the information of the second ECS according to the local configuration or from the federal control network element, it requests the second ECS for an EES that can provide services for the terminal device.
  • the transceiver unit is further configured to receive third request information from the first device, where the third request information is used to request information about the first EES, and the processing unit further uses It is determined according to the third request information that the EES managed by the first ECS cannot provide the edge service for the terminal device.
  • the first device may be a terminal device, EEC, or EES, which is not limited in this application.
  • the first device is a terminal device, and when the terminal device acquires EES that can provide edge services for the terminal device from the ECS (first ECS) that is preconfigured or delivered by the network side, the location of the terminal device may have moved, etc.
  • the EES managed by the first ECS cannot provide edge services for terminal devices.
  • the first ECS can obtain an EES that can provide edge services for terminal devices through local configuration or by querying other ECSs from the federal control network element.
  • the first request information, the second request information, or the third request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an edge computing service The identifier of the provider ECSP, the characteristic information of the first EES, and the application information.
  • PLMN public land mobile network
  • an apparatus for obtaining edge services may be the second ECS, or may also be a component configured in the second ECS (such as a chip or a chip system, etc.), which is not limited in this application.
  • the device includes a transceiver unit and a processing unit: the transceiver unit is used to receive second request information from the first ECS, the second request information is used to request the information of the first EES, and the processing unit is used to determine according to the second request information For information about the first EES, the transceiving unit is further configured to send second response information to the first ECS, where the second response information includes information about the first EES.
  • the second request information includes at least one of the following: an identifier of the public land mobile network PLMN accessed by the terminal device, an identifier of the edge computing service provider ECSP, and a feature of the first EES Information, application information, location information of terminal equipment.
  • the processing unit is further configured to determine the information of the first EES according to the second request information and a local ECS configuration file, where the ECS configuration file includes at least one of the following: The address information of the ECS, the service scope of the ECS, the EES configuration file managed by the ECS, the ECSP ID of the ECS, and the PLMN ID corresponding to the ECS.
  • the second ECS determines the information of the first EES according to the PLMN identifier in the second request information and the PLMN identifier in the ECS configuration file. Or the second ECS determines the information of the first EES according to the ECSP identifier in the second request information and the ECSP identifier in the ECS configuration file. Or the second ECS determines the information of the first EES according to the feature information of the first EES in the second request information and the EES configuration file managed by the ECS in the ECS configuration file. Or the second ECS determines the information of the first EES according to the application information in the second request information and the EES configuration file managed by the ECS in the ECS configuration file.
  • the second ECS determines the information of the first EES according to the location information of the terminal device in the second request information and the service range of the ECS in the ECS configuration file.
  • the second ECS may also determine the information of the first EES according to two or more items in the second request information, which is not limited in this application.
  • an apparatus for obtaining edge services may be a terminal device, or may also be a component configured in the terminal device (such as a chip or a chip system, etc.), which is not limited in this application.
  • the device includes a transceiver unit: the transceiver unit is used to send the first request information to the first functional network element, the first request information is used to request the information of the first edge configuration server ECS, and the first functional network element is a federal control network element Or the first ECS discovery agent, the first functional network element stores information about at least one ECS, and the transceiver unit is further configured to receive first response information from the first functional network element, where the first response information includes information about the first ECS .
  • the ECS registers the configuration file on the first functional network element, so that the terminal device can obtain an ECS that can provide edge services for the terminal device.
  • the solution provided by this application It is not necessary for different operators to configure different ECSs for terminal equipment, and all terminal equipment can discover ECS through the first functional network element, which is more flexible and applicable to a wider range.
  • the apparatus further includes a processing unit, where the processing unit is configured to acquire address information of the first functional network element.
  • the address information of the first functional network element can be configured in the terminal device, or in the EEC, or in the core network element. If the address information of the first functional network element is configured on the network element of the core network, the network element of the core network may send it to the terminal device.
  • the first request information includes at least one of the following: an identifier of the public land mobile network PLMN accessed by the terminal device, an edge computing service provider ECSP identifier, and location information of the terminal device .
  • an apparatus for obtaining edge services may be the first functional network element, or may also be a component configured in the first functional network element (such as a chip or a chip system, etc.), which is not limited in this application.
  • the device includes a transceiver unit and a processing unit: the transceiver unit is used to receive the first request information from the terminal equipment, the first request information is used to request the information of the first edge configuration server ECS, and the first functional network element is the federal control network element or the first ECS discovery agent, the first functional network element stores information of at least one ECS, the processing unit is used to determine the first ECS according to the first request information, and the transceiver unit is also used to send the first response information to the terminal device , the first response information includes information about the first ECS.
  • the first functional network element is a first ECS discovery agent
  • the processing unit is specifically configured to determine the address of the second ECS discovery agent according to the first request information and/or local configuration.
  • the transceiving unit is also used to send the second request information to the second ECS discovery agent
  • the second request information is used to request the information of the first ECS
  • the transceiver unit is also used to receive the second request information from the second ECS discovery agent Response information
  • the second response information includes information of the first ECS.
  • the ECS discovery agent stores configuration files of multiple ECSs, and the ECS discovery agent configures the information of other ECS discovery agents, so that the ECS discovery agents can interactively obtain the ECS information stored separately.
  • the processing unit is configured to control the transceiver unit to send third request information to the federal control network element according to the first request information, and the third request information is used to request the second
  • the ECS discovers the information of the agent
  • the transceiving unit is further configured to receive third response information from the federal control network element, where the third response information includes the information of the second ECS discovery agent.
  • the ECS discovery agent stores multiple ECS configuration files, and the ECS discovery agent registers with the federated control network element, so that the ECS discovery agent can query the federated control network element for information about other ECS discovery agents.
  • the first request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an ECSP identifier of an edge computing service provider, and location information of the terminal device.
  • PLMN public land mobile network
  • an apparatus for obtaining edge services may be implemented by a network element of the first control plane core network, or may be a component (such as a chip or a chip system, etc.) configured in the first control plane core network element, which is not limited in this application.
  • the device includes a transceiver unit and a processing unit: the transceiver unit is configured to receive first indication information from a second control plane core network element of the second network, the first indication information indicating that the terminal device supports access to an edge of the first network service, the processing unit is configured to control the transceiver unit to send first request information to the third control plane core network element of the first network according to the first instruction information, and the first request information is used to request the first edge of the first network
  • the configuration server ECS information the transceiving unit is further configured to receive first response information from the third control plane core network element, where the first response information includes the first ECS information.
  • the first network is the network of the visited domain
  • the second network is the network of the home domain
  • the control plane core network element of the network of the home domain informs the control plane core network of the network of the visited domain through instruction information Element
  • the terminal device supports access to the edge service of the first network, so as to obtain ECS information that can provide the edge service for the terminal device under the visited domain network.
  • the first request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an edge computing service provider ECSP identifier, and location information of the terminal device .
  • PLMN public land mobile network
  • ECSP edge computing service provider
  • an apparatus for obtaining edge services may be a third control plane core network element, or may also be a component (such as a chip or a chip system) configured in the third control plane core network element, which is not limited in this application.
  • the device includes a transceiving unit and a processing unit: the transceiving unit is used to receive first request information from a first control plane core network element, the first request information is used to request information of a first edge configuration server ECS, the first The request information includes at least one of the following items: the identifier of the public land mobile network PLMN accessed by the terminal device, the identifier of the edge computing service provider ECSP, the location information of the terminal device, and the processing unit is used to determine the information of the first ECS according to the first request information
  • the transceiving unit is further configured to send first response information to the first control plane core network element, where the first response information includes information of the first ECS.
  • the processing unit is specifically configured to determine the information of the first ECS according to the PLMN identifier and the correspondence between the PLMN identifier and the ECS, and/or, the processing unit specifically uses The information of the first ECS is determined according to the ECSP identifier and the correspondence between the ECSP identifier and the ECS, and/or the processing unit is specifically configured to determine the information of the first ECS according to the location information of the terminal device and the service range of the ECS.
  • a communication device in a thirteenth aspect, includes a processor, the processor is coupled with a memory, and can be used to execute instructions in the memory, so as to realize any one of the above first to third aspects or the first aspect to the method in any possible implementation of the third aspect.
  • the device further includes a memory, and the memory and the processor may be deployed separately or in a centralized manner.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication interface may be a transceiver, or an input/output interface.
  • the apparatus is a chip configured in the first ECS, or the second ECS, or a terminal device.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pipe feet or related circuits, etc.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc. .
  • the input signal received by the input circuit may be received and input by the receiver, but the signal output by the output circuit may be but not limited to be output to the transmitter and transmitted by the transmitter, and the input circuit and the output circuit may be The same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.
  • a communication device in a fourteenth aspect, includes a processor, the processor is coupled with a memory, and can be used to execute instructions in the memory, so as to realize any one of the fourth to sixth aspects or the fourth aspect to the method in any possible implementation manner of the sixth aspect.
  • the device further includes a memory, and the memory and the processor may be deployed separately or in a centralized manner.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip configured in the first functional network element, or the first control plane core network network element, or the third control plane core network network element.
  • the communication interface may be an input/output on the chip or the chip system Interface, interface circuit, output circuit, input circuit, pin or related circuit, etc.
  • the processor may also be embodied as a processing circuit or logic circuit.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc. .
  • the input signal received by the input circuit may be received and input by the receiver, but the signal output by the output circuit may be but not limited to be output to the transmitter and transmitted by the transmitter, and the input circuit and the output circuit may be The same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.
  • a computer program product includes: a computer program (also referred to as code, or an instruction), when the computer program is executed, the computer executes the above-mentioned first to sixth aspects. Any one of the aspects, and the method in any possible implementation manner of the first aspect to the sixth aspect.
  • a computer-readable storage medium stores a computer program (also referred to as code, or instruction) when it is run on a computer, so that the computer executes the above-mentioned first aspect Any aspect from the sixth aspect to the sixth aspect, and a method in any possible implementation manner from the first aspect to the sixth aspect.
  • a computer program also referred to as code, or instruction
  • FIG. 1 is a system architecture diagram applicable to the embodiment of the present application.
  • FIG. 2 is a schematic diagram of an edge service architecture according to an embodiment of the present application.
  • 3-11 are interactive flowcharts of the method for obtaining edge services provided by this application.
  • Fig. 12 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • Fig. 13 is a schematic block diagram of another communication device provided by an embodiment of the present application.
  • Fig. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the wireless communication systems mentioned in the embodiments of this application include but are not limited to: global system of mobile communication (GSM) system, long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system , LTE time division duplex (time division duplex, TDD), LTE system, advanced long-term evolution (LTE-Advanced, LTE-A) system, next-generation communication system (for example, 6G communication system), integration of multiple access systems system, or evolved system.
  • GSM global system of mobile communication
  • LTE long term evolution
  • FDD frequency division duplex
  • FDD frequency division duplex
  • LTE time division duplex time division duplex
  • LTE-A advanced long-term evolution
  • next-generation communication system for example, 6G communication system
  • integration of multiple access systems system or evolved system.
  • the technical solution provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long-term evolution technology (Long Term Evolution-machine, LTE-M), device to device (device to device, D2D) network , machine to machine (machine to machine, M2M) network, Internet of things (internet of things, IoT) network or other networks.
  • MTC machine type communication
  • LTE-M inter-machine communication long-term evolution technology
  • D2D device to device
  • machine to machine machine to machine
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (vehicle to pedestrian, V2P) or vehicle to network (vehicle to network, V2N) communication, etc.
  • vehicle to vehicle vehicle to vehicle
  • V2V vehicle to vehicle
  • V2I vehicle to infrastructure
  • V2P vehicle to pedestrian
  • V2N vehicle to network
  • FIG. 1 is a system architecture diagram 100 applicable to the embodiment of the present application. As shown in the figure, the network architecture 100 may specifically include the following network elements:
  • Radio access network radio access network, RAN
  • the access network that realizes the access network function based on wireless communication technology can be called a radio access network.
  • the wireless access network can manage wireless resources, provide access services for terminals, and complete the forwarding of control signals and user data between terminals and the core network.
  • the wireless access network can be, for example, a base transceiver station (BTS) in a global system of mobile communication (GSM) system or a code division multiple access (CDMA), or it can be a broadband code division
  • BTS base transceiver station
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • the base station (nodeB, NB) in the multiple access (wideband code division multiple access, WCDMA) system can also be an evolved base station (evolutional nodeB, eNB or eNodeB) in the LTE system, and it can also be a cloud wireless access network (cloud radio access network (CRAN), or the network device can be a relay station, access point, vehicle-mounted device, wearable device, network device in the future 5G network or network device in the future evolved PLMN network, etc.
  • CRAN cloud radio access network
  • the embodiment of the present application is not limited.
  • Authentication server function authentication server function, AUSF
  • network element mainly used for user authentication, etc.
  • Access and mobility management function network element (access and mobility management function, AMF): mainly used for mobility management and access management, etc., and can be used to implement the mobility management entity (mobility management entity, MME) function Functions other than session management, such as lawful interception or access authorization (or authentication). In the embodiment of the present application, it can be used to implement functions of access and mobility management network elements.
  • AMF access and mobility management function
  • MME mobility management entity
  • Session management function network element (session management function, SMF): mainly used for session management, IP address allocation and management of terminal equipment, selection and management of user plane functions, policy control, or endpoints of charging function interfaces and downlink data notification etc. In the embodiment of the present application, it can be used to realize the function of the session management network element.
  • Policy control network element Policy control function, PCF: a unified policy framework for guiding network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).
  • Application function network element (Application function, AF): It is used for data routing affected by the application, accessing network opening function network elements, or interacting with the policy framework for policy control, etc.
  • Unified data management network element used for unified data management, 5G user data management, processing user identification, access authentication, registration, or mobility management, etc.
  • User plane function It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data.
  • User data can be accessed to a data network (data network, DN) through this network element.
  • data network data network, DN
  • it can be used to realize the functions of the user plane network element.
  • Network slice selection function network element used to manage information related to network slices.
  • Data network a network used to provide data transmission.
  • DN Data network
  • a network of an operator's business an Internet (Internet) network, a business network of a third party, and the like.
  • User equipment can also be called terminal, access terminal, subscriber unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device , User Agent, or User Device.
  • the terminal in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality, AR) terminal, an industrial Wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety Wireless terminals in smart cities, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop ( wireless local loop (WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, 5G network A terminal or a terminal in
  • wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the above-mentioned network elements or devices may still use their names in the 5G communication system, or may have other names, which are not limited in this embodiment of the present application.
  • the functions of the above-mentioned network element or device may be performed by an independent network element, or jointly performed by several network elements.
  • network elements in the core network can be deployed on the same or different physical devices.
  • the AMF and the SMF may be deployed on the same physical device.
  • the network elements of the 5G core network can be deployed on the same physical device as the network elements of the 4G core network. This embodiment of the present application does not limit it.
  • FIG. 1 is only an example, and does not constitute any limitation to the protection scope of the present application.
  • the communication method provided in the embodiment of the present application may also involve network elements not shown in FIG. 1 , and of course the communication method provided in the embodiment of the present application may only include some of the network elements shown in FIG. 1 .
  • the above-mentioned network architecture also includes a network function (network function (NF) repository function, NRF): used to store description information of network function entities and services provided by them, and support service discovery, network element entity discovery, etc.; Network exposure function (NEF): used to securely open services and capabilities provided by the 3rd Generation Partnership Project (3GPP) network function to the outside.
  • Unified data repository (UDR) used for UDM to store or read subscription data and PCF to store or read policy data.
  • the network system architecture in this application may also include an edge configuration server (edge configuration server, ECS) network element, and the ECS network element may be a global management network element, maintaining the network elements of each edge data network (edge data network, EDN).
  • Information including the service scope of the edge data network and the address of the edge enabler server (EES) in the edge data network.
  • the service scope of the edge data network can be topological address information (such as Cell ID, TAI (Trach area id), etc.) or geometric address information (for example, information such as province, city, district or latitude and longitude), and the service scope can be address information collection.
  • ECS network elements are deployed in a distributed manner, that is, each ECS can manage edge data networks in different regions. It should be understood that the ECS network element can be co-located with other network elements or can be an independent network element. This application does not make any limitation on the deployment of the ECS network element in the network architecture.
  • the network system architecture in this application may also include an edge enabler server (EES) network element, and the EES network element may be a mobile edge computing (MEC) node (MEC may also be called
  • EES edge enabler server
  • MEC mobile edge computing
  • the control network element or management network element in multi access edge computing is responsible for managing each EAS deployed in the EDN, such as registration, domain name system (domain name system, DNS) resolution content routing, Upper layer application registration management, wireless information interaction and other basic functions.
  • the EES can invoke the capability opening function network element in the 3GPP network.
  • the EES network element can be co-located with other network elements or can be an independent network element. This application does not make any restrictions on the deployment of the EES network element in the network architecture.
  • the N2 interface is the interface between the RAN and the AMF network element, and is used for sending non-access stratum (non-access stratum, NAS) messages, etc.
  • the N3 interface is the interface between the RAN and the UPF network element, used
  • the N4 interface is the interface between the SMF network element and the UPF network element, and is used to transmit such information as the tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages.
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture capable of implementing the functions of the foregoing network elements is applicable to this embodiment of the present application.
  • the name of the interface between network elements in FIG. 1 is just an example, and the name of the interface in a specific implementation may be another name, which is not specifically limited in this application.
  • the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.
  • FIG. 2 is a schematic diagram of an edge service architecture in an embodiment of the present application.
  • the network architecture 200 may specifically include: an edge data network (edge data network, EDN) may be a local data center, and the EDN includes an edge enabler server. server, EES) and multiple edge application servers (edge application server, EAS), each EDN has a specific service scope.
  • the EES can be a control network element or a management network element in a mobile edge computing (MEC) node (MEC can also be called multi-access edge computing), responsible for managing Each EAS in the network, such as registration, domain name system (domain name system, DNS) resolution content routing, upper-layer application registration management, wireless information interaction and other basic functions.
  • MEC mobile edge computing
  • EES can call the network element with the capability opening function in the 3GPP network.
  • Edge data network configuration server (EDNCS) or edge configuration server (ECS) can be a global management network element, maintaining information of each EDN, including service scope and EES address, etc.
  • EES edge data network configuration server
  • AF application function
  • the user equipment may include: an edge enabler client (edge enabler client, EEC) and an application client, where the EEC provides necessary support for the application client on the terminal, and the functions of the EEC include: through EDGE-4 retrieves EDN information, UE registers to EES, retrieves available EAS, EAS availability changes, EAS migration notification to EEC.
  • EEC edge enabler client
  • the EDGE-8 reference point in Figure 2 supports the interaction between the edge provisioning server and the core network, which supports: (1) access to core network functions and application programming interfaces (APIs) for retrieving network capability information; (2) Provide a service release notification to the core network (for example: SMF).
  • EDGE-1 The interface between EES and EEC, supporting the registration/de-registration of EEC in EES; the discovery of edge application servers in the edge data network.
  • EDGE-2 the interface between EES and 3GPP core network, used for EES to obtain 3GPP network capabilities.
  • EDGE-3 The interface between EES and EAS, supports EES registration/de-registration EAS, including EAS availability information, service scope information, address information, etc.; EES provides 3GPP network capability information (such as location information) to EAS.
  • EDGE-4 The interface between EEC and ECS, supporting ECS to provide/push configuration information to EEC.
  • EDGE-5 The interface between the AC and the EEC, which supports the AC to obtain the access EAS information from the EEC.
  • EDGE-6 The interface between ECS and EES, which supports configuring EES information on ECS.
  • EDGE-7 The interface between EAS and 3GPP core network, which supports EAS to obtain 3GPP network capabilities.
  • EDGE-8 The interface between ECS and 3GPP core network, supporting ECS to obtain 3GPP network capabilities.
  • EDGE-9 Cross-MEC nodes/interfaces between different EESs within the same MEC node, supporting application migration.
  • the ECS is pre-configured on the terminal device, or the ECS is pre-configured on the EEC, or the ECS is pre-configured on the UDM in a pre-configuration manner.
  • the terminal device generally adopts the following scheme to obtain edge services: the edge enables the client EEC as a part of the UE, and the EEC sends a service provisioning request (service provisioning request) or a service subscription update request (service subscription update request) to the preconfigured ECS to obtain edge services.
  • the address information of the EES after the UE or EEC obtains the address information of the EES, the EEC sends an EAS discovery request (EAS discovery request) to the EES to obtain the address information of the edge application server EAS, and further obtain the edge service.
  • the UE cannot obtain edge services through the pre-configured ECS.
  • the pre-configuration process is generally static , will only be executed once. If you want to update the pre-configured ECS information, it is difficult to obtain edge services through the updated ECS information, and it is not easy to implement. Because updating the pre-configured ECS information may require reinstalling the software or restarting the terminal device to be implemented.
  • configuring multiple ECSs in the UDM may cause the UDM to be overloaded, and in the prior art, the UDM only configures the configuration information of the ECS in the home domain.
  • the terminal device moves to the range covered by the network of the visited domain, the edge service cannot be obtained through the pre-configured configuration information of the ECS of the home domain, and the terminal device cannot obtain the configuration information of the ECS of the visited domain, so it cannot Obtain edge services through the configuration information of the ECS of the visited domain.
  • This application proposes a method for obtaining edge services, which enables a terminal device to obtain an ECS that can provide edge services for the terminal device after the ECS it wants to access changes.
  • Fig. 3 is an interaction flowchart of a method for obtaining edge services provided by the present application.
  • the method 100 shown in FIG. 3 includes:
  • Step S110 if the first edge configuration server ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device, the first ECS acquires information of the second ECS. In other words, the first ECS determines that the first ECS cannot provide the edge service for the terminal device, and the first ECS obtains the information of the second ECS.
  • the EES will register the EES configuration file (profile) to the ECS. If an EES is registered to a certain ECS, it can be considered that the EES is managed by the ECS, that is, the EES managed by the first ECS can be understood as registered to the second ECS. EES on an ECS.
  • the EES profile can include at least one of the following items: EES identifier, EES endpoint information (endpoint), registered EAS information, edge computing service provider (edge computing service provider, ECSP) information, EES service scope, EES associated data Network access identifier (data network access identifier, DNAI).
  • the EES managed by the first ECS can provide edge services for the terminal device, and it needs to meet the requirements of managing or registering the information of the EAS that the terminal device wants to access on the EES. If an unregistered terminal device on the EES wants to access EAS information, even if the service scope of EES or the service scope of other registered EAS includes the location area where the terminal device is located, it will be deemed that the EES managed by the first ECS cannot serve as a terminal device. Provide edge services. In one implementation manner, the EAS is registered with the EES, and the EES is registered with the ECS, so the ECS can determine which EASs are managed by the EESs managed by itself.
  • the first ECS determines that the EES managed by the first ECS cannot provide edge services for terminal devices, which can be divided into the following situations:
  • Case 1 The first ECS determines that the EES managed by the first ECS cannot provide the edge service for the terminal device. For example, the terminal device is located in area 1, and the service range of the EES managed by the first ECS does not include area 1, then the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device. Wherein, the first ECS can manage multiple EESs, and the service scope of each EES does not include area 1 .
  • Case 2 the first ECS determines that the first ECS cannot provide the edge service for the terminal device. For example, if the ECSP ID requested by the terminal device is ECSP_1, and the ECSP corresponding to the first ECS is ECSP_2, or the ECSP corresponding to the EES managed by the first ECS is ECSP_2, then the first ECS determines that the first ECS cannot provide edge services for the terminal device. Or, the terminal device accesses PLMN_1, and the ECSP corresponding to the first ECS is PLMN_2, or the ECSP corresponding to the EES managed by the ECS is PLMN_2, then the first ECS determines that the first ECS cannot provide edge services for the terminal device.
  • the first ECS determines that the first ECS cannot provide edge services for the terminal device.
  • the service scope of the ECS may be specifically composed of one or more service areas, or may be a set of service scopes of each EES managed by the ECS.
  • Case 3 Although the EES managed by the first ECS can provide edge services for terminal devices, the service quality may not be optimal.
  • the first ECS can try to obtain the EES information managed by the second ECS from the second ECS to determine the optimal
  • the EES provides edge services for end devices.
  • the terminal device is located in area 1, and the service range of the EES managed by the first ECS includes area 1, but the first ECS can still search for the second ECS and obtain EES information from the second ECS.
  • the first ECS determines that the terminal device can access the second ECS through the subscription data of the terminal device (for example, the terminal device has signed both the first ECS and the second ECS).
  • the second ECS obtains the EES information managed by the second ECS.
  • the first ECS determines an optimal EES from the EES managed by the first ECS and the EES managed by the second ECS to provide the service for the UE.
  • the first edge configuration server ECS determines that the EES managed by the first ECS cannot provide edge services for terminal devices. It can be case 2, case 3 or case 4. The same is true when the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device, and will not be described in detail below.
  • the method 100 also includes:
  • step S101 the first device sends third request information to the first ECS, where the third request information is used to request information of the first EES.
  • the first ECS receives the third request information.
  • the third request information can be a service provisioning request, or an EES discovery request.
  • This application does not limit the specific information or message name, and the information or message name that will appear later Also, it is only an example and does not constitute any limitation to the present application.
  • the third request information includes at least one of the following: a public land mobile network (public land mobile network, PLMN) identifier accessed by the terminal device, an edge computing service provider (edge computing service provider, ECSP) identifier, the terminal device
  • PLMN public land mobile network
  • edge computing service provider edge computing service provider
  • the first ECS After the first ECS receives the third request information, it determines that the EES managed by the first ECS cannot provide edge services for terminal devices according to the third request information (that is, the EES managed by the first ECS does not include the first EES, and thus determines that the first ECS The EES managed by ECS cannot provide edge services for terminal devices). Or, the first ECS tries to obtain the EES information managed by the second ECS from the second ECS, so as to determine the optimal EES to provide the edge service for the terminal device.
  • the first ECS determines according to the PLMN identifier accessed by the terminal device that the EES managed by the first ECS cannot provide the edge service for the terminal device. For example, the terminal device accesses PLMN_1, and the ECSP corresponding to the first ECS is PLMN_2, or the ECSP corresponding to the EES managed by the first ECS is PLMN_2, then the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device; or
  • the first ECS determines according to the ECSP identifier accessed by the terminal device that the EES managed by the first ECS cannot provide the edge service for the terminal device. For example, if the ECSP identifier requested by the terminal device is ECSP_1, and the ECSP corresponding to the first ECS is ECSP_2, or the ECSP corresponding to the EES managed by the first ECS is ECSP_2, then the first ECS determines that the EES managed by the first ECS cannot provide Edge Services; or
  • the first ECS determines according to the location information of the terminal device that the EES managed by the first ECS cannot provide the edge service for the terminal device. For example, if the location information of the terminal device is location_1, but the service scope of the first ECS does not include location_1, or the service scope corresponding to the EES managed by the first ECS does not include location_1, then the first ECS determines that the first ECS Managed EES cannot provide edge services to end devices; or
  • the first ECS determines according to the characteristic information of the EES that the EES managed by the first ECS cannot provide the edge service for the terminal device. For example, if a terminal device or an EES requests an EES whose ECSP ID is ECSP_1, and the ECSP corresponding to the first ECS is ECSP_2, or the ECSP corresponding to the EES managed by the first ECS is ECSP_2, then the first ECS determines that the EES managed by the first ECS cannot be End devices provide edge services.
  • the first ECS can also determine that the EES managed by the first ECS cannot provide the terminal device with two or more items based on the PLMN identifier accessed by the terminal device, the ECSP identifier, the location information of the terminal device, and the characteristic information of the EES. Edge services, this application does not impose any restrictions on this.
  • the first ECS can obtain the information of the second ECS in at least one of the following ways:
  • the first ECS obtains the information of the second ECS according to the configuration information.
  • the first ECS configures profiles of other ECSs.
  • the ECS obtains the EES information managed by the second ECS to determine the optimal EES to provide edge services for the terminal device. It can obtain the information of the second ECS according to the configuration files of other ECSs configured locally.
  • the EES managed by the second ECS can serve as the terminal device.
  • the device provides edge services.
  • the ECS configuration file includes one or more of the address or endpoint information of the ECS, the service scope of the ECS, the EES configuration file managed by the ECS, the ECSP ID of the ECS, and the PLMN ID corresponding to the ECS, which are mentioned later
  • the specific content of the ECS configuration file is the same as above, and will not be repeated in the following description.
  • the service scope of the ECS may be specifically composed of one or more service areas, or may be a set of service scopes of each EES managed by the ECS.
  • the first ECS determines the second ECS according to the third request information and/or the configuration file of the ECS saved/configured by the first ECS.
  • the first ECS obtains the information of the second ECS ;
  • the ECSP identifier in the third request information is the same as the ECSP identifier of the second ECS, then the first ECS obtains the information of the second ECS; or
  • the PLMN identifier in the third request information is the same as the PLMN identifier of the second ECS, then the first ECS obtains the information of the second ECS; or
  • the characteristic information of the EES in the third request information matches the EES managed by the second ECS, and the first ECS obtains the information of the second ECS.
  • the ECS configuration file is saved or configured on the federal control network element.
  • the method 100 also includes:
  • Step S102 the first ECS sends first request information to the federal control network element, where the first request information is used to request information of the second ECS.
  • the federal control network element receives the first request information.
  • the federated control network element supports the function of discovering ECS. This application does not limit the name of the network element, and the network element can also be called a federated management network element, or an ECS discovery network element, etc.
  • the federated control network element may be an independent network element, or may be integrated in other network elements, for example, it may be integrated in NRF or UDM, which is not limited in this application.
  • step S103 the federal control network element sends first response information to the first ECS, where the first response information includes information of the second ECS.
  • the corresponding first ECS receives the first response information.
  • the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device according to the third request information, or the first ECS tries to obtain the EES information managed by the second ECS from the second ECS, so as to determine the When the excellent EES provides the edge service for the terminal equipment, it sends the first request information to the federal control network element, so as to obtain the information of the second ECS.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the ECS can register or send the configuration file to the federation control network element. Therefore, when the first ECS determines that the EES managed by the first ECS cannot provide edge services for the terminal device, or the first ECS tries to obtain from the second ECS
  • the EES information managed by the second ECS so as to determine the optimal EES to provide edge services for terminal devices, can query the ECS that can provide edge services for terminal devices from the federal control network element, or query the EES that can provide edge services for terminal devices Corresponding/registered ECS.
  • the method for the federal control network element to query/determine the second ECS information includes but is not limited to:
  • the location corresponding to the location information of the terminal device in the first request information is within the service range of the second ECS or within the service range of the EES managed by the second ECS, then the federal control network element determines that the second ECS can be a terminal ECS where the device provides edge services; or
  • the ECSP identifier in the first request information is the same as the ECSP identifier of the second ECS, then the federal control network element determines that the second ECS is an ECS that can provide edge services for terminal devices; or
  • the PLMN identifier in the first request information is the same as the PLMN identifier of the second ECS, then the federal control network element determines that the second ECS is an ECS that can provide edge services for terminal devices; or
  • the federal control network element determines that the second ECS is an ECS that can provide edge services for terminal devices.
  • the federal control network element After determining the second ECS, the federal control network element sends the information of the second ECS to the first ECS.
  • local policy information is saved or pre-configured on the first ECS.
  • the local policy information includes: the first ECS can obtain the EES information managed by the second ECS from the second ECS (refer to the case 3 in step S110), so as to determine the optimal EES to provide the edge service for the terminal device.
  • the first ECS determines that the terminal device can access the second ECS through the subscription data of the terminal device (for example, the terminal device has signed both the first ECS and the second ECS), and the first ECS tries to obtain the second ECS from the second ECS. 2.
  • EES information managed by ECS is managed by ECS.
  • the first ECS first determines that a second ECS needs to be searched according to the local policy information, and then determines the second ECS through the above method 1 or method 2.
  • the method 100 further includes:
  • Step S104 the first ECS sends second request information to the second ECS, where the second request information is used to request information of the first EES.
  • the second ECS receives the second request information.
  • Step S105 the second ECS sends second response information to the first ECS, where the second response information includes the information of the first EES.
  • the corresponding first ECS receives the second response information.
  • the second request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the second ECS determines the first EES according to the second request information and/or the EES configuration file saved by the ECS, including at least one of the following:
  • the second ECS determines the first EES according to the PLMN identifier accessed by the terminal device and the PLMN identifier of the EES configuration file;
  • the second ECS determines the first EES according to the ECSP identifier in the second request and the ECSP information of the EES configuration file;
  • the second ECS determines the first EES according to the location information of the terminal device and the service scope information of the EES configuration file, wherein the location information of the terminal device may be included in the second request information, or may be obtained by the second ECS from the 5GC.
  • Step S120 the first ECS sends first information to the first device, the first information includes information of the first EES or information of the second ECS, and the first EES is an EES managed by the second ECS.
  • the first device receives the first information.
  • the first device may be a UE, an EEC, or an EES, which is not limited in this application.
  • the first device can directly determine the first EES; when the first information sent by the first ECS to the first device is the information of the second ECS
  • the first device may send fifth request information to the second ECS, so as to obtain the information of the first EES through the fifth response information from the second ECS.
  • the specific content and function of the fifth request information and the third request information are similar, and will not be repeated here.
  • the EEC can send an EAS discovery request to the first EES to obtain the address information of the EAS, and then access the edge service.
  • the information of the ECS described above may be a uniform resource identifier (uniform resource identifier, URI) of the ECS, an Internet protocol (internet protocol, IP) address, or a fully qualified domain name (fully qualified domain name). , FQDN), which is not limited in this application.
  • the UE can establish a connection with the ECS based on the information of the ECS.
  • the EES information may also be information such as the URI, IP address, or FQDN of the EES, which is not limited in this application.
  • the information of the ECS mentioned later and the information of the EES specifically include the same content as above, and will not be repeated in the description below.
  • the above-mentioned method 100 is used in a specific scenario below to introduce a method for obtaining edge services.
  • Fig. 4 is an interactive flowchart of the method for obtaining edge services in a federation scenario provided by the present application.
  • the application scenario of the method 200 shown in FIG. 4 is a federation (Federation) scenario, that is, a federation is formed by multiple ECSPs and/or multiple PLMNs.
  • a federation Federation
  • the edge service can be obtained through the method 200, and the edge service can also be obtained through the method 200 when the terminal device is in a non-roaming scenario.
  • the method 200 includes:
  • Step S210 one or more ECSs (ECS1 and ECS2 are examples in FIG. 4 ) register the ECS configuration file with a federation control network element (federation controller, FC), where FC is a logical network element, which may be integrated in an existing functional network Elements, such as FC integrated in NRF, ECS, UDR or UDM.
  • FC federation control network element
  • the FC may also be called by other names, such as federation manager (federation manager, FM) or edge computing federation manager (MEFM), etc., which is not limited in this application.
  • each ECS configures the configuration files of other ECSs, for example, ECS1 configures the configuration files of ECS2, and ECS2 configures the configuration files of ECS1.
  • ECS1 and ECS2 may belong to the same PLMN, or may belong to different PLMNs, or the ECSP identifiers of ECS1 and ECS2 may be the same, and the ECSP identifiers of ECS1 and ECS2 may also be different.
  • Step S220 EEC or UE (corresponding to the first device in method 100) sends a third request message to ECS1 (corresponding to the first ECS in method 100), for example, the third request message may be a service provisioning request , the third request information is used to request the information of the first EES.
  • the third request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the EEC can configure the address information of the ECS1, so the EEC can obtain the address information of the ECS1 locally before sending the third request message to the ECS1. Or, the EEC can also obtain the address information of the ECS1 in other ways, for example, the 5GC network sends it to the UE/EEC.
  • Step S230 after ECS1 receives the third request message, it determines that the EES managed by ECS1 cannot provide the edge service for the terminal device. In other words, it is determined that ECS1 cannot provide edge services for the terminal device.
  • ECS1 tries to acquire EES information managed by the second ECS from the second ECS, so as to determine (compared with the EES managed by ECS1) an optimal EES to provide edge services for terminal devices. For example, after ECS1 receives the third request message, it does not find a suitable EES, or does not find an EDN where the application that the terminal device wants to access is deployed. Wherein, no suitable EES is found, including: the EAS requested by the UE is not registered with the EES, or the EAS requested by the UE is registered with the EES but is overloaded.
  • ECS1 records the third request message, which is used for triggering to search for other ECSs when ECS1 receives another request from EEC.
  • the method 200 also includes:
  • Step S240 if ECS1 does not find a suitable EES, ECS1 sends a third response message to the EEC/UE, indicating that ECS1 does not find a suitable EES or EDN.
  • the third response information includes indication information indicating that the ECS1 cannot provide the edge service for the terminal device or indicates that the EES managed by the ECS1 cannot provide the edge service for the terminal device.
  • step S250 the EEC/UE sends fourth request information to ECS1 after receiving the third response information.
  • the fourth request information is the same as the third request information.
  • ECS1 receives the fourth request information, it determines that it needs to search for other ECSs according to the previously recorded third request information.
  • the fourth request information is different from the third request information, and the fourth request information includes indication information, instructing ECS1 to search for other ECSs, and ECS1 may search for other ECSs according to the indication information.
  • the fourth request information is an ECS discovery (discovery) request, and the fourth request information includes at least one of the ECSP identifier, EES or EAS feature information, PLMN identifier, and terminal device location information and application information. Item, the fourth request information is used to find the ECS.
  • the ECSP logo can be the PLMN logo and/or the name of the third-party service provider.
  • the EAS will register the EAS configuration file (profile) on the EES, and the EAS profile may include at least one of the following: EAS identifier, EAS endpoint information (endpoint), ECSP information, EAS service scope, and DNAI associated with the EAS.
  • the characteristic information of EES or EAS can be one or more items in EES/EAS profile.
  • steps S240 and S250 are optional, that is, when ECS1 does not find a suitable EES in step S230, the information of ECS2 can be obtained directly.
  • ECS1 may obtain information about ECS2 (corresponding to the second ECS in method 100) in at least one of the following ways:
  • ECS1 and ECS2 register the configuration files to the federal control network element.
  • ECS1 determines that the EES managed by ECS1 cannot provide edge services for terminal devices, it can query the federal control network element for the EES that can provide edge services for terminal devices, so as to determine the EES corresponding to the EES.
  • ECS such as ECS2 (the EES2 managed by ECS2 can meet the request of EEC).
  • ECS1 determines the information of ECS2 through steps S251 and S252.
  • Step S251 ECS1 sends first request information to the federal control network element, where the first request information is used to request information from ECS2.
  • the federal control network element receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • step S252 the federal control network element sends first response information to ECS1, where the first response information includes the information of ECS2.
  • the corresponding ECS1 receives the first response information.
  • ECS1 is configured with the configuration file of ECS2.
  • ECS1 determines that the EES managed by ECS1 cannot provide edge services for terminal devices, it can obtain the information of ECS2 according to the configuration file of ECS2 configured locally.
  • EES2 managed by ECS2 can provide edge services for terminal devices.
  • ECS1 determines the information of EES2 through steps S253 and S254.
  • step S253 ECS1 sends second request information to ECS2, where the second request information is used to request information of EES2 (corresponding to the first EES in method 100).
  • ECS2 receives the second request information.
  • step S254 ECS2 sends second response information to ECS1, where the second response information includes the information of EES2.
  • the corresponding ECS1 receives the second response information.
  • the second request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • ECS1 may determine the information of the target EES (for example, EES2) according to the first response information or the second response information.
  • step S270 ECS1 sends the information of ECS2 to EEC, correspondingly, EEC receives the information of ECS2, and subsequently EEC can send a service provisioning request to ECS2 to obtain the information of EES2, so as to obtain the edge service.
  • step S270
  • step S280 EES2 registers its configuration file to ECS1.
  • step S281 ECS1 sends the information of EES2 to EEC, and EEC receives the information of EES2 accordingly.
  • the information of ECS2 in step S270 or the information of EES2 in step S281 is the first information in step S120 of method 100 .
  • EEC After UE/EEC receives the information of EES2, EEC can send EAS discovery request to EES2 to obtain the address information of EAS, and then access the edge service.
  • Fig. 5 is an interactive flowchart of another method for obtaining edge services in a federation scenario provided by the present application.
  • the application scenario of the method 300 shown in FIG. 5 is a federation scenario, that is, a federation is formed by multiple ECSPs and/or multiple PLMNs.
  • a roaming scenario such as home routing or local distribution
  • the edge service can be obtained through the method 300, and the edge service can also be obtained through the method 300 when the terminal device is in a non-roaming scenario.
  • Method 300 includes:
  • Step S310 one or more ECSs (ECS1 and ECS2 are examples in FIG. 5 ) register the ECS configuration file with the federation control network element.
  • each ECS configures the configuration files of other ECSs, for example, ECS1 configures the configuration files of ECS2, and ECS2 configures the configuration files of ECS1.
  • ECS1 and ECS2 may belong to the same PLMN, or may belong to different PLMNs, or the ECSP identifiers of ECS1 and ECS2 may be the same, and the ECSP identifiers of ECS1 and ECS2 may also be different.
  • Step S320 the source EES (EES1, corresponding to the first device in the method 100) cannot find a suitable EAS and/or EES to serve the terminal device.
  • EES receives an EAS discovery request from EEC (the connection between EEC and EES has been established), EES finds that no suitable EAS can be found, or EES detects that the terminal device moves and needs to switch EAS, but finds that no suitable EAS can be found.
  • EES receives an EAS discovery request from EEC (the connection between EEC and EES has been established), EES finds that no suitable EAS can be found, or EES detects that the terminal device moves and needs to switch EAS, but finds that no suitable EAS can be found. The EAS.
  • Step S330 the source EES sends a third request message to ECS1 (corresponding to the first ECS in method 100) (the source EES registers with ECS1), for example, the third request message may be a service provisioning request or an EES discovery request , the third request information is used to request the information of the first EES.
  • the third request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • ECS1 determines that the EES managed by ECS1 cannot provide edge services for the terminal device. Alternatively, it is determined that ECS1 cannot provide edge services for the terminal device. Alternatively, ECS1 tries to acquire EES information managed by the second ECS from the second ECS, so as to determine (compared with the EES managed by ECS1) an optimal EES to provide edge services for terminal devices.
  • the source EES cannot find a suitable EAS and/or EES to serve the terminal device, for example, the EES receives an EAS discovery request from the EEC, and the EES finds that no suitable EAS can be found, or, the EES detects that the terminal device moves and needs to be switched While EASing, it was found that no suitable EAS could be found.
  • the source EES sends an EES discovery request to ECS1 to request the information of the first EES, and ECS1 searches for an unsuitable EES to provide edge services for the terminal device.
  • ECS1 may obtain information about ECS2 (corresponding to the second ECS in method 100) in at least one of the following ways:
  • ECS1 and ECS2 register the configuration files to the federation control network element.
  • ECS1 determines that the EES managed by ECS1 cannot provide edge services for terminal devices, it can query the federation control network element for ECS/EES that can provide edge services for terminal devices, such as ECS2( EES2 managed by ECS2 can meet the request of EEC).
  • ECS1 determines the information of ECS2 through steps S341 and S342.
  • Step S341 ECS1 sends first request information to the federal control network element, where the first request information is used to request information from ECS2.
  • the federal control network element receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • step S342 the federal control network element sends first response information to ECS1, where the first response information includes the information of ECS2.
  • the corresponding ECS1 receives the first response information.
  • ECS1 is configured with the configuration file of ECS2.
  • ECS1 determines that the EES managed by ECS1 cannot provide edge services for terminal devices, it can obtain the information of ECS2 according to the configuration file of ECS2 configured locally.
  • EES2 managed by ECS2 can provide edge services for terminal devices.
  • ECS1 may determine the information of the target EES (for example, EES2) according to the first response information or the second response information.
  • ECS1 determines the information of EES2 through steps S343 and S344.
  • step S343 ECS1 sends second request information to ECS2, where the second request information is used to request information of EES2 (corresponding to the first EES in method 100).
  • ECS2 receives the second request information.
  • Step S344 ECS2 sends second response information to ECS1, where the second response information includes the information of EES2.
  • the corresponding ECS1 receives the second response information.
  • the second request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • step S360 the ECS1 sends the first information (the information of the EES2) to the source EES, and the source EES receives the first information accordingly.
  • Step S370 optionally, the terminal device sends an application discovery request to the EES, for requesting the EAS (target EAS) managed by the EES2.
  • the EAS (source EAS) visited by the terminal device can perform context migration with the target EAS, or perform context synchronization/context migration between EES1 and EES2, so that the terminal device can obtain edge services through EES2, or ensure business continuity.
  • Fig. 6 is an interactive flowchart of another method for obtaining edge services provided by the present application.
  • the method 400 shown in FIG. 6 includes:
  • Step S410 the terminal device sends the first request information to the first functional network element, the first request information is used to request the information of the first ECS, the first functional network element is the federal control network element or the first ECS discovery agent, the first A functional network element stores information of at least one ECS. Correspondingly, the first functional network element receives the first request information.
  • the ECS discovery proxy (ECS discovery proxy), supports the function of discovering ECS, the name is not limited, or the ECS discovery network element (ECS discovery function), etc.
  • the ECS discovery agent may be an independent network element, or may be integrated in other network elements.
  • the ECS discovery agent may be integrated in NRF, UDM, or ECS, which is not limited in this application.
  • each PLMN deploys an ECS discovery agent for topology hiding.
  • the first request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the method 400 also includes:
  • step S411 the network element of the core network sends address information of the first functional network element to the terminal device, and correspondingly, the terminal device receives the address information of the first functional network element.
  • the address information of the first functional network element is configured on the terminal device, or on the EEC, or on a core network element. If the address information of the first functional network element is configured on a core network element (such as a UDM), the core network element may deliver it to the terminal device.
  • a core network element such as a UDM
  • Step S420 after receiving the first request information, the first functional network element determines the information of the first ECS according to the first request information.
  • the first functional network element is a first ECS discovery agent
  • the first ECS discovery agent obtains the information of the first ECS from the second ECS discovery agent.
  • the first ECS discovery agent can obtain the information of the second ECS discovery agent in the following ways:
  • the first ECS discovery agent configures or saves the relevant information of the second ECS discovery agent (one or more of address information, service scope, managed EES information, ECSP identifier, PLMN identifier, etc.), and the first ECS discovery agent according to The first request information and/or the local configuration determine the information of the second ECS discovery agent.
  • the PLMN identifier in the first request information is the same as the PLMN identifier of the locally configured second ECS discovery agent, then the first ECS discovery agent obtains the information of the second ECS discovery agent, and/or
  • the ECSP identifier in the first request information is the same as the ECSP identifier of the second ECS discovery agent, then the first ECS discovery agent determines the second ECS discovery agent and obtains corresponding address information; and/or
  • the PLMN identifier in the first request information is the same as the PLMN identifier of the second ECS discovery agent, then the first ECS discovery agent determines the second ECS discovery agent and obtains corresponding address information; and/or
  • the characteristic information of the EES in the first request information matches the EES managed by the second ECS discovery agent, and then the first ECS discovery agent determines the second ECS discovery agent and obtains corresponding address information.
  • the second ECS discovery agent registers its configuration information (one or more of address information, service scope, managed EES information, ECSP identifier, PLMN identifier, etc.) with the federal control network element.
  • the federal control network element saves the ECS configuration information.
  • the first ECS discovery agent sends third request information to the federal control network element according to the first request information, the third request information is used to request the information of the second ECS discovery agent, and the first ECS discovery agent receives the information from the federal control network element Third response information, where the third response information includes information about the second ECS discovery agent.
  • the third request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the method for the federal control network element to determine the second ECS discovery agent is similar to the method for the first ECS discovery agent to determine the information of the second ECS discovery agent based on the first request information and/or local configuration in mode 1, the difference is that In mode 1, the execution subject is the first ECS discovery agent, and in mode 2, the execution subject is the federal control network element, which will not be repeated here.
  • the method 400 further includes:
  • Step S412 the first ECS discovery agent sends second request information to the second ECS discovery agent, where the second request information is used to request information of the first ECS.
  • the second ECS discovery agent receives the second request information.
  • the second request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S413 the second ECS discovery agent sends second response information to the first ECS discovery agent, where the second response information includes the information of the first ECS.
  • the first ECS discovery agent receives the second response information.
  • the method for the second ECS discovery agent to determine the first ECS according to the second request information and the ECS configuration information saved/configured by the second ECS discovery agent is similar to the method for the first ECS to determine the second ECS in step S101, the difference lies in the step In S101, the execution subject is the first ECS, and here the execution subject is the discovery agent of the second ECS, which will not be repeated here.
  • Step S430 the first functional network element sends first response information to the terminal device, where the first response information includes the information of the first ECS.
  • the terminal device receives the first response information, and obtains the edge service through the first ECS.
  • the EEC can send a service provisioning request to the target ECS (the first ECS) to obtain the EES; the EEC then sends an EAS discovery request to the EES to obtain the EAS address information, and then access the edge service.
  • the above-mentioned method 400 is used in a specific scenario below to introduce a method for obtaining edge services.
  • Fig. 7 is an interaction flowchart of a method for obtaining edge services in a federation scenario provided by this application.
  • the application scenario of the method 500 shown in FIG. 7 is a federation scenario.
  • the edge service can be obtained through the method 500 .
  • the method 500 includes:
  • Step S510 one or more ECSs (ECS1, ECS2 and ECS3 are examples in FIG. 7) register the ECS configuration file to the federal control network element FC, where FC is a logical network element, which may be integrated in an existing functional network element, For example FC is integrated in NRF, UDR or UDM.
  • FC is a logical network element, which may be integrated in an existing functional network element, For example FC is integrated in NRF, UDR or UDM.
  • each ECS configures one or more configuration files of other ECSs, for example, ECS1 configures configuration files of ECS2 and ECS3, ECS2 configures configuration files of ECS1 and ECS3, and ECS3 configures configuration files of ECS1 and ECS2.
  • ECS1, ECS2 and ECS3 may belong to the same PLMN, or may belong to different PLMNs, or the ECSP identifiers of ECS1, ECS2 and ECS3 may be the same, and the ECSP identifiers of ECS1, ECS2 and ECS3 may also be different.
  • the ECSP identifier may be a PLMN identifier, which is not limited in this application.
  • step S520 the UE/EEC configures the address information of the federated control network element.
  • Step S520' the core network element (using UDM as an example) configures the address information of the federated control network element.
  • step S521 the network element of the core network sends the address information of the federated control network element to the UE/EEC, and correspondingly, the UE/EEC receives the address information of the federated control network element.
  • step S530 the UE/EEC sends first request information to the federal control network element, where the first request information is used to request information of a target ECS (an ECS capable of providing edge services for a terminal device).
  • the federal control network element receives the first request information.
  • the first request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S540 the federal control network element determines the information of the target ECS.
  • the federal control network element determines the target ECS according to the locally configured ECS configuration file and the first request information.
  • the federated control network element determines the target ECS according to the PLMN identifier of the locally configured ECS and the PLMN identifier accessed by the terminal device in the first request message;
  • the federal control network element obtains the location information of the terminal device from the 5G core network, and according to the location information of the terminal device in the first request information and the locally configured ECS service scope to determine the target ECS;
  • the federal control network element determines the target ECS according to the ECSP identifier of the local ECS and the ECSP identifier in the first request information.
  • step S550 the federal control network element sends first response information to the UE/EEC, where the first response information includes the information of the target ECS, and correspondingly, the UE/EEC receives the first response information.
  • the EEC can send a service provisioning request to the target ECS to obtain the EES, and the EEC then sends an EAS discovery request to the EES to obtain the EAS address information, and then access the edge service.
  • Fig. 8 is an interaction flowchart of another method for obtaining edge services in a federation scenario provided by the present application.
  • the application scenario of the method 600 shown in FIG. 8 is a federation scenario.
  • each operator deploys an ECS discovery proxy (discovery proxy), and when the terminal device is in a roaming scene or a non-roaming scene, the edge service can be obtained through the method 600.
  • the method 600 includes:
  • Step S610 one or more ECSs register the ECS configuration file with the ECS discovery agent (ECS1 and ECS3 are registered with the first ECS discovery agent in Figure 8, and ECS2 and ECS4 are registered with the second ECS discovery agent), wherein the ECS discovery agent can It is a logical network element, which may be integrated in an existing functional network element, for example, the ECS discovery agent is integrated in NRF, UDR or UDM.
  • Step S620 one or more ECS discovery agents register their relevant information (one or more of address information, service scope, managed EES information, ECSP identification, PLMN identification, etc.) to the federal control network element (in FIG. 8
  • the first ECS discovery agent and the second ECS discovery agent are registered with the federated control network element), and the federated control network element may not belong to any operator to which the first ECS discovery agent and the second ECS discovery agent belong.
  • the first ECS discovery agent configures relevant information of the second ECS discovery agent
  • the second ECS discovery agent configures relevant information of the first ECS discovery agent
  • the first ECS discovery agent belongs to a first network, for example, the first network is a home domain network
  • the second ECS discovery agent belongs to a second network, for example, the second network is a visited domain network.
  • step S630 the UE/EEC configures address information of the first ECS discovery agent.
  • Step S630' the core network element (using UDM as an example) configures or obtains the address information of the first ECS discovery agent.
  • step S640 the network element of the core network sends the address information of the federal control network element or the first ECS discovery agent to the UE/EEC, and correspondingly, the UE/EEC receives the address information of the federation control network element or the first ECS discovery agent.
  • the UE/EEC may obtain the address information of the first ECS discovery agent from the local configuration, or the UE/EEC may obtain the address information of the first ECS discovery agent from the core network element, or the UE/EEC may obtain the address information of the first ECS discovery agent from the core network
  • the network element obtains the address information of the federated control network element, and then obtains the address information of the first ECS discovery agent from the federated control network element.
  • the UE/EEC sends first request information to the first ECS discovery agent, where the first request information is used to request information of a target ECS (an ECS capable of providing an edge service for a terminal device).
  • the first ECS discovery agent receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S660 the first ECS discovery agent determines the information of the target ECS discovery agent.
  • the first ECS discovery agent determines according to the first request information that the ECS registered on the first ECS discovery agent has an ECS that can provide edge services for the terminal, then the first ECS discovery agent is the target ECS discovery agent.
  • step S664 the first ECS discovery agent sends the determined target ECS information to the UE/EEC, and correspondingly, the UE/EEC obtains the edge service after receiving the target ECS information.
  • the first ECS discovery agent determines according to the first request information that the ECS registered on the first ECS discovery agent does not have an ECS that can provide edge services for the terminal, the first ECS discovery agent determines that the target ECS discovery agent is the second ECS discovery agent.
  • the method for the first ECS discovery agent to determine the target ECS discovery agent refer to the method 1 in step S420, which will not be repeated here.
  • step S661 the first ECS discovery agent sends second request information to the second ECS discovery agent, where the second request information is used to request information about the first ECS.
  • the second ECS discovery agent receives the second request information.
  • the second request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the second ECS discovery agent determines, according to the first request information, a target ECS that is registered on the second ECS discovery agent and can provide edge services for the terminal.
  • the method for the second ECS discovery agent to determine the target ECS refers to the method for the first ECS to obtain the information of the target ECS (second ECS) in method 100.
  • the difference is that the execution subject in method 100 is the first ECS, and here the execution subject is the second ECS. Discovery agent, no more details here.
  • Step S663 the second ECS discovery agent sends second response information to the first ECS discovery agent, where the second response information includes the information of the first ECS.
  • the first ECS discovery agent receives the second response information.
  • Step S664 the first ECS discovery agent sends first response information to the UE/EEC, where the first response information includes the information of the first ECS.
  • the UE/EEC receives the first response information, and obtains the edge service through the target ECS.
  • Fig. 9 is an interactive flow chart of a method for acquiring edge services provided by the present application.
  • the method 700 shown in FIG. 9 includes:
  • Step S710 the second control plane core network element of the second network sends first indication information to the first control plane core network element, where the first indication information indicates that the terminal device supports access to the edge service of the first network.
  • the first control plane core network element of the first network receives the first indication information.
  • the first network is a network of a visited domain
  • the second network is a network of a home domain.
  • Step S720 the first control plane core network element sends the first request information to the third control plane core network element of the first network according to the first indication information, the first request information is used to request the first edge of the first network Configure server ECS information.
  • the third control plane core network network element of the first network receives the first request information.
  • the first request information includes at least one of the following: the identity of the public land mobile network PLMN accessed by the terminal device, the identity of the edge computing service provider ECSP, characteristic information of EES or EAS, location information of the terminal device, and application information .
  • Step S730 the third control plane core network element of the first network determines the information of the first ECS according to the first request information.
  • the third control plane core network element stores or configures the ECS configuration file.
  • the third control plane core network element determines the information of the first ECS according to the PLMN identifier and the correspondence between the PLMN identifier and the ECS; and/or
  • the third control plane core network element determines the information of the first ECS according to the ECSP identifier and the correspondence between the ECSP identifier and the ECS; and/or
  • the third control plane core network element determines the information of the first ECS according to the location information of the terminal device and the service range of the ECS; and/or
  • the third control plane core network element determines the information of the first ECS according to the application information.
  • Step S740 the first control plane core network element receives first response information from the third control plane core network element, where the first response information includes the information of the first ECS.
  • the above method 700 is used in a specific scenario below to introduce a method for obtaining edge services.
  • FIG. 10 is an interaction flowchart of a method for obtaining edge services in a roaming access scenario of a home route provided by the present application.
  • the UDM stores UE subscription data (the subscription data is at UE granularity), and the subscription data includes edge services of which visited domain networks (such as V-PLMNs) the UE supports to access.
  • V-PLMNs visited domain networks
  • the subscription data also includes information about the corresponding ECS of the VDN.
  • the UE subscription data preconfigured by UDM is not UE granular subscription data, but home domain network granular subscription data, that is, for the same Any UE in the same domain subscribes to the same ECS.
  • the UDM is pre-configured with ECS information, that is, each UE under the home domain network can obtain edge services through the ECS.
  • ECS In another implementation manner, it is applicable to a scenario where an operator deploys/manages multiple ECSs.
  • ECS registers service scope, address information, ECSP identification, etc. with NRF.
  • the ECS can be deployed by the operator or a third party. If the ECS is deployed by the operator itself, the ECSP ID can be the PLMN ID. If the ECS is deployed by a third party, the ECSP ID can be the name of the third-party service provider or the PLMN ID and the name of the third-party service provider.
  • Method 800 includes:
  • step S810 the UE/EEC sends a first request message to the SMF in the visited domain (V-SMF as an example), where the first request message is used to request information of a target ECS (an ECS capable of providing edge services for a terminal device).
  • the V-SMF receives the first request information.
  • the first request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the UE sends a session establishment request to the V-SMF, and the session establishment request includes first request information.
  • the session establishment request also carries indication information, and the indication information indicates that the EEC supports receiving ECS information).
  • the V-SMF sends a session context establishment request to the SMF in the home domain (take the H-SMF as an example).
  • the session context establishment request includes the ID of the V-PLMN (for example, V-PLMN), or the H-SMF can determine the ID of the V-PLMN according to the ID of the V-SMF or other information.
  • step S820 the H-SMF acquires the subscription data of the UE from the H-UDM, and determines that the UE supports access to the edge service of the first network (the V-PLMN currently accessed by the UE).
  • the subscription information acquired by the H-SMF from the H-UDM also includes information about the ECS (take the V-ECS as an example) of the V-PLMN corresponding to the V-PLMN. Then the H-SMF sends the ECS information of the visited domain to the V-SMF.
  • the H-SMF can query/obtain the information of the V-ECS from the H-NRF, and forward it to the V-SMF Information on V-ECS.
  • step S860 the H-SMF sends the first request information to the H-NRF, and the first request information is used to request the information of the V-ECS.
  • the H-NRF receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the H-NRF obtains the information of the V-ECS from the V-NRF.
  • the H-NRF forwards the first request information to the V-NRF.
  • Step S862 the V-NRF sends the first response information to the H-NRF, the first response information includes the information of the V-ECS, and the H-NRF receives the first response information correspondingly.
  • step S863 the H-NRF forwards the first response information to the V-SMF.
  • step S830 the H-SMF sends first indication information to the V-SMF, where the first indication information indicates that the UE supports access to the edge service of the first network.
  • the V-SMF receives the first indication information.
  • the first indication information is also used to instruct the V-SMF to determine the V-ECS, and the indication information may specifically be subscription information supporting access to V-PLMN edge services, or the indication information may be displayed indication information.
  • step S830 may be replaced by the H-SMF sending the first indication information to the V-SMF, where the first indication information instructs the V-SMF to determine the V-ECS.
  • the V-SMF may determine the information of the V-ECS in the following manner.
  • Step S840 the V-SMF sends the first request information to the V-NRF, where the first request information is used to request the information of the V-ECS.
  • the V-NRF receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S841 the V-NRF sends the first response information to the V-SMF, the first response information includes the information of the V-ECS, and correspondingly, the V-SMF receives the first response information.
  • V-NRF can determine V-ECS through the following implementation methods:
  • the V-NRF determines the V-ECS according to the PLMN identifier in the first request information and the local V-PLMN identifier;
  • the V-NRF determines the V-ECS according to the location information of the UE in the first request information and the service range of the local ECS.
  • the V-NRF determines the V-ECS according to the ECSP identifier in the first request information and the local ECSP identifier.
  • V-SMF queries V-UDM for V-ECS.
  • V-UDM stores the V-ECS information of V-PLMN.
  • the V-ECS information is not UE granular subscription data.
  • the V-ECS information is applicable to the home domain network. per UE.
  • the V-SMF sends first request information to the V-UDM, where the first request information is used to request the information of the V-ECS.
  • the V-UDM receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S851 The V-NRF sends the first response information to the V-UDM, the first response information includes the information of the V-ECS, and correspondingly, the V-SMF receives the first response information.
  • V-SMF executes after determining the information of the V-ECS
  • Step S870 the V-SMF forwards the first response information to the UE/EEC (it may be any first response information in steps S841, S851, or S863), the first response information includes the information of the V-ECS, correspondingly, The UE/EEC receives the first response information, so as to further obtain the edge service.
  • V-UDM determines the V-ECS according to the request information. It should be understood that the manner in which the V-NRF determines the V-ECS according to the request information is the same as the manner in which the V-NRF determines the V-ECS, and will not be repeated here.
  • FIG. 11 is an interaction flowchart of a method for obtaining edge services in a roaming access scenario of local offloading provided by the present application.
  • the UDM stores the subscription data of the UE (the subscription data is at UE granularity), and the subscription data includes the edge services of which visited domain networks (such as V-PLMN) the UE supports to access. .
  • V-PLMN visited domain networks
  • the subscription data also includes information about the corresponding ECS of the VDN.
  • the subscription data of the UE pre-configured by the UDM is not the subscription data at the UE granularity, but the subscription data at the home domain network granularity.
  • the UDM is pre-configured with ECS information, that is, each UE under the home domain network can obtain edge services through the ECS.
  • ECS In another implementation manner, it is applicable to a scenario where an operator deploys/manages multiple ECSs.
  • ECS registers service scope, address information, ECSP identification, etc. with NRF.
  • the ECS can be deployed by the operator or a third party. If the ECS is deployed by the operator itself, the ECSP ID can be the PLMN ID. If the ECS is deployed by a third party, the ECSP ID can be the name of the third-party service provider or the PLMN ID and the name of the third-party service provider.
  • Method 900 includes:
  • Step S910 the UE/EEC sends the first request information to the SMF of the visited domain (V-SMF as an example), the first request information is used to request the target ECS (the ECS that can provide edge services for the terminal equipment, V-ECS) Information.
  • the V-SMF receives the first request information.
  • the first request information includes at least one of the following: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • the H-UDM determines, according to the subscription data of the UE, that the UE supports access to the edge service of the first network (the visited domain network currently accessed by the UE, taking V-PLMN as an example).
  • step S930 the H-UDM sends first indication information to the V-SMF, where the first indication information indicates that the UE supports accessing the edge service of the V-PLMN.
  • the V-SMF receives the first indication information.
  • the first indication information is also used to instruct the V-SMF to determine the V-ECS, and the indication information may specifically be subscription information supporting access to V-PLMN edge services, or the indication information may be displayed indication information.
  • step S930 may be replaced by the H-UDM sending the first indication information to the V-SMF, where the first indication information instructs the V-SMF to determine the V-ECS.
  • the V-SMF can determine the information of the V-ECS in the following manner.
  • the V-SMF sends first request information to the V-NRF, where the first request information is used to request address information of the V-ECS.
  • the V-NRF receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S941 the V-NRF sends the first response information to the V-SMF, the first response information includes the information of the V-ECS, and correspondingly, the V-SMF receives the first response information.
  • V-NRF can determine V-ECS through the following implementation methods:
  • the V-NRF determines the V-ECS according to the PLMN identifier in the first request information and the local V-PLMN identifier;
  • the V-NRF determines the V-ECS according to the location information of the UE in the first request information and the service range of the local ECS.
  • the V-NRF determines the V-ECS according to the ECSP identifier in the first request information and the local ECSP identifier.
  • V-SMF queries V-UDM for V-ECS.
  • V-UDM stores the V-ECS information of V-PLMN.
  • the V-ECS information is not UE granular subscription data.
  • the V-ECS information is applicable to the home domain network. per UE.
  • step S950 the V-SMF sends first request information to the V-UDM, where the first request information is used to request the information of the V-ECS.
  • the V-UDM receives the first request information.
  • the first request information includes at least one of the following items: PLMN identifier accessed by the terminal device, ECSP identifier, location information of the terminal device, characteristic information of EES or EAS, and application information.
  • Step S951 the V-NRF sends the first response information to the V-UDM, the first response information includes the information of the V-ECS, and correspondingly, the V-SMF receives the first response information.
  • V-SMF executes after determining the information of the V-ECS
  • step S960 the V-SMF forwards the first response information (it may be the first response information in step S941 or S951) to the UE/EEC, the first response information includes the information of the V-ECS, correspondingly, the UE/EEC receives The first response information, so as to further obtain the edge service.
  • V-UDM determines the V-ECS
  • V-NRF determines the V-ECS
  • execution subject illustrated in Figure 3- Figure 11 is only an example, and the execution subject may also be a chip, a chip system, or a processor that supports the execution subject to implement the method shown in Figure 3- Figure 11, the present application There is no limit to this.
  • the methods and operations implemented by the functional network element may also be implemented by components (such as chips or circuits) that can be used for the functional network element.
  • the methods and operations implemented by the terminal equipment may also be implemented by components (such as chips or circuits) that can be used in terminal equipment, and the methods and operations implemented by ECS can also be implemented by components (such as chips or circuits) that can be used in ECS.
  • the methods and operations implemented by the network elements of the control plane core network may also be implemented by components (such as chips or circuits) that can be used for the network elements of the control plane core network.
  • each network element such as a transmitting end device or a receiving end device, includes a corresponding hardware structure and/or software module for performing each function in order to realize the above functions.
  • 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 drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.
  • Fig. 12 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 300 includes a transceiver unit 310 and a processing unit 320 .
  • the transceiver unit 310 can communicate with the outside, and the processing unit 320 is used for data processing.
  • the transceiver unit 310 may also be called a communication interface or a communication unit.
  • the communication device 300 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 320 may read instructions or and/or data in the storage unit.
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 320 may read instructions or and/or data in the storage unit.
  • the communication device 300 may be the first ECS
  • the transceiver unit 310 is used to perform the operation of receiving or sending the first ECS in the method embodiment above
  • the processing unit 320 is used to perform the operation in the method embodiment above Operations processed internally by the first ECS.
  • the communication apparatus 300 may be a device including the first ECS.
  • the communication device 300 may be a component configured in the first ECS, for example, a chip in the first ECS.
  • the transceiver unit 310 may be an interface circuit, a pin, and the like.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 320 may include a processing circuit.
  • the processing unit 320 is configured to obtain information about the second ECS, and the transceiver unit 310 is configured to send the first Information, the first information includes the information of the first EES or the information of the second ECS, and the first EES is the EES managed by the second ECS.
  • the processing unit 320 is further configured to acquire information of the second ECS according to configuration information.
  • the transceiving unit 310 is also used to send the first request information to the federal control network element, the first request information is used to request the information of the second ECS, and the transceiver unit 310 is also used to receive the information from the federation First response information of the control network element, where the first response information includes information of the second ECS.
  • the transceiving unit 310 is further configured to send second request information to the second ECS, where the second request information is used to request information from the first EES, and the transceiving unit 310 is also configured to receive information from the second ECS.
  • the second response information of the ECS where the second response information includes the information of the first EES.
  • the transceiving unit 310 is further configured to receive third request information from the first device, the third request information is used to request information about the first EES, and the processing unit 320 is further configured to The request information determines that the EES managed by the first ECS cannot provide edge services for the terminal device.
  • the first request information, the second request information, or the third request information includes at least one of the following: the identity of the public land mobile network PLMN accessed by the terminal device, the identity of the edge computing service provider ECSP, Feature information and application information of the first EES.
  • the communication device 300 may be a second ECS
  • the transceiver unit 310 is used to perform the operation of receiving or sending the second ECS in the method embodiment above
  • the processing unit 320 is used to perform the operation in the method embodiment above Operations handled internally by the second ECS.
  • the communication apparatus 300 may be a device including the second ECS.
  • the communication device 300 may be a component configured in the second ECS, for example, a chip in the second ECS.
  • the transceiver unit 310 may be an interface circuit, a pin, and the like.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 320 may include a processing circuit.
  • the transceiver unit 310 is configured to receive second request information from the first ECS, the second request information is used to request information of the first EES, and the processing unit 320 is configured to To determine the information of the first EES, the transceiving unit 310 is further configured to send second response information to the first ECS, where the second response information includes the information of the first EES.
  • the second request information includes at least one of the following: the identity of the public land mobile network PLMN accessed by the terminal device, the identity of the edge computing service provider ECSP, feature information of the first EES, application information, terminal Device location information.
  • the processing unit 320 is further configured to determine the information of the first EES according to the second request information and a local ECS configuration file, where the ECS configuration file includes at least one of the following: address information of the ECS, The service scope of the ECS, the EES configuration file managed by the ECS, the ECSP ID of the ECS, and the PLMN ID corresponding to the ECS.
  • the communication device 300 may be a terminal device, the transceiver unit 310 is used to perform the receiving or sending operation of the terminal device in the method embodiment above, and the processing unit 320 is used to perform the operation of the terminal device in the method embodiment above Operations handled internally.
  • the communication apparatus 300 may be a device including a terminal device.
  • the communication apparatus 300 may be a component configured in a terminal device, for example, a chip in the terminal device.
  • the transceiver unit 310 may be an interface circuit, a pin, and the like.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 320 may include a processing circuit.
  • the transceiver unit 310 is configured to send the first request information to the first functional network element, the first request information is used to request the information of the first edge configuration server ECS, and the first functional network element is a federated The control network element or the first ECS discovery agent, the first functional network element stores information about at least one ECS, and the transceiver unit 310 is further configured to receive first response information from the first functional network element, where the first response information includes the first Information of an ECS.
  • the processing unit 320 is configured to acquire address information of the first functional network element.
  • the first request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an ECSP identifier of an edge computing service provider, and location information of the terminal device.
  • PLMN public land mobile network
  • Fig. 13 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 400 includes a transceiver unit 410 and a processing unit 420 .
  • the transceiver unit 410 can communicate with the outside, and the processing unit 420 is used for data processing.
  • the transceiver unit 410 may also be called a communication interface or a communication unit.
  • the communication device 400 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 420 may read instructions or and/or data in the storage unit.
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 420 may read instructions or and/or data in the storage unit.
  • the communication device 400 may be a first functional network element
  • the transceiver unit 410 is used to perform the receiving or sending operation of the first functional network element in the method embodiment above
  • the processing unit 420 is used to perform the above The internal processing operation of the first functional network element in the method embodiment.
  • the communications apparatus 400 may be a device including the first functional network element.
  • the communication device 400 may be a component configured in the first functional network element, for example, a chip in the first functional network element.
  • the transceiver unit 410 may be an interface circuit, a pin, and the like.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 420 may include a processing circuit.
  • the transceiver unit 410 is configured to receive first request information from a terminal device, the first request information is used to request information of the first edge configuration server ECS, and the first functional network element is a federal control network
  • the first functional network element stores the information of at least one ECS.
  • the processing unit 420 is used to determine the first ECS according to the first request information.
  • the transceiver unit 410 is also used to send the first ECS to the terminal device. Response information, where the first response information includes information about the first ECS.
  • the first functional network element is a first ECS discovery agent
  • the processing unit 420 is specifically configured to determine the information of the second ECS discovery agent according to the first request information and/or local configuration
  • the transceiver unit 410 is further configured to send second request information to the second ECS discovery agent, where the second request information is used to request information about the first ECS, and the transceiver unit 410 is also configured to receive second response information from the second ECS discovery agent,
  • the second response information includes information of the first ECS.
  • the processing unit 420 is configured to control the transceiver unit 410 to send third request information to the federal control network element according to the first request information, where the third request information is used to request the second ECS to discover the agent's information, the transceiving unit 410 is further configured to receive third response information from the federal control network element, where the third response information includes information about the second ECS discovery agent.
  • the first request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an ECSP identifier of an edge computing service provider, and location information of the terminal device.
  • PLMN public land mobile network
  • the communication device 400 may be a network element of the first control plane core network
  • the transceiver unit 410 is used to perform the receiving or sending operation of the first control plane core network element in the method embodiment above
  • the processing unit Step 420 is used to execute the internal processing operation of the first control plane core network element in the method embodiment above.
  • the communications apparatus 400 may be a device including a first control plane core network element.
  • the communication device 400 may be a component configured in a network element of the first control plane core network, for example, a chip in the network element of the first control plane core network.
  • the transceiver unit 410 may be an interface circuit, a pin, and the like.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 420 may include a processing circuit.
  • the transceiving unit 410 is configured to receive first indication information from a network element of the second control plane core network of the second network, where the first indication information indicates that the terminal device supports access to an edge of the first network.
  • the processing unit 420 is configured to control the transceiver unit to send first request information to the third control plane core network element of the first network according to the first instruction information, and the first request information is used to request the first
  • the transceiving unit 410 is further configured to receive first response information from the third control plane core network element, where the first response information includes information about the first ECS.
  • the first request information includes at least one of the following: an identifier of a public land mobile network (PLMN) accessed by the terminal device, an ECSP identifier of an edge computing service provider, and location information of the terminal device.
  • PLMN public land mobile network
  • the communication device 400 may be a third control plane core network element
  • the transceiver unit 410 is configured to perform the receiving or sending operation of the third control plane core network element in the method embodiment above
  • the processing unit Step 420 is used to execute the internal processing operation of the core network element of the third control plane in the method embodiment above.
  • the communications apparatus 400 may be a device including a third control plane core network element.
  • the communication device 400 may be a component configured in a network element of the third control plane core network, for example, a chip in the network element of the third control plane core network.
  • the transceiver unit 410 may be an interface circuit, a pin, and the like.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 420 may include a processing circuit.
  • the transceiving unit 410 is configured to receive first request information from a network element of the first control plane core network, where the first request information is used to request information of the first edge configuration server ECS, and the first The request information includes at least one of the following items: the public land mobile network PLMN identifier accessed by the terminal device, the edge computing service provider ECSP identifier, and the location information of the terminal device.
  • the processing unit 420 is used to determine the location of the first ECS according to the first request information.
  • the transceiving unit 410 is further configured to send first response information to the first control plane core network element, where the first response information includes information about the first ECS.
  • the processing unit 420 is specifically configured to determine the information of the first ECS according to the PLMN identifier and the corresponding relationship between the PLMN identifier and the ECS, and/or, the processing unit 420 is specifically configured to, according to the ECSP identifier, And the correspondence between the ECSP identifier and the ECS determines the information of the first ECS, and/or, the processing unit 420 is specifically configured to determine the information of the first ECS according to the location information of the terminal device and the service range of the ECS.
  • the embodiment of the present application further provides a communication device 500 .
  • the communication device 500 includes a processor 510, the processor 510 is coupled with a memory 520, the memory 520 is used to store computer programs or instructions and/or data, and the processor 510 is used to execute the computer programs or instructions and/or data stored in the memory 520 , so that the methods in the above method embodiments are executed.
  • the communication device 500 includes one or more processors 510 .
  • the communication device 500 may further include a memory 520 .
  • the communication device 500 may include one or more memories 520 .
  • the memory 520 may be integrated with the processor 510, or set separately.
  • the communication device 500 may further include a transceiver 530 and/or a communication interface, and the transceiver 530 and/or the communication interface are used for receiving and/or sending signals.
  • the processor 510 is configured to control the transceiver 530 to receive and/or send signals.
  • the communication device 500 is configured to implement the operations performed by the first ECS in the above method embodiments.
  • the processor 510 is configured to implement the operations performed internally by the first ECS in the above method embodiments
  • the transceiver 530 is configured to implement the receiving or sending operations performed by the first ECS in the above method embodiments.
  • the processing unit 320 in the apparatus 300 may be the processor in FIG. 14
  • the transceiver unit 310 may be the transceiver and/or the communication interface in FIG. 14 .
  • the operations performed by the processor 510 reference may be made to the description of the processing unit 320 above, and for the operations performed by the transceiver 530, reference may be made to the description of the transceiver unit 310, which will not be repeated here.
  • the communication device 500 is configured to implement the operations performed by the second ECS in the above method embodiments.
  • the processor 510 is configured to implement the operations performed internally by the second ECS in the above method embodiments
  • the transceiver 530 is configured to implement the receiving or sending operations performed by the second ECS in the above method embodiments.
  • the processing unit 320 in the apparatus 300 may be the processor in FIG. 14
  • the transceiver unit 310 may be the transceiver and/or the communication interface in FIG. 14 .
  • the operations performed by the processor 510 reference may be made to the description of the processing unit 320 above, and for the operations performed by the transceiver 530, reference may be made to the description of the transceiver unit 310, which will not be repeated here.
  • the communication apparatus 500 is configured to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 510 is configured to implement the operations performed internally by the terminal device in the above method embodiments
  • the transceiver 530 is configured to implement the receiving or sending operations performed by the terminal device in the above method embodiments.
  • the processing unit 320 in the apparatus 300 may be the processor in FIG. 14
  • the transceiver unit 310 may be the transceiver and/or the communication interface in FIG. 14 .
  • the operations performed by the processor 510 reference may be made to the description of the processing unit 320 above, and for the operations performed by the transceiver 530, reference may be made to the description of the transceiver unit 310, which will not be repeated here.
  • the embodiment of the present application further provides a communication device 600 .
  • the communication device 600 includes a processor 610, the processor 610 is coupled with a memory 620, the memory 620 is used to store computer programs or instructions and/or data, and the processor 610 is used to execute the computer programs or instructions and/or data stored in the memory 620 , so that the methods in the above method embodiments are executed.
  • the communication device 600 includes one or more processors 610 .
  • the communication device 600 may further include a memory 620 .
  • the communication device 600 may include one or more memories 620 .
  • the memory 620 may be integrated with the processor 610, or set separately.
  • the communication device 600 may further include a transceiver 630 and/or a communication interface, and the transceiver 630 and/or the communication interface are used for receiving and/or sending signals.
  • the processor 610 is configured to control the transceiver 630 and/or the communication interface to receive and/or send signals.
  • the communication device 600 is configured to implement the operations performed by the first functional network element in the above method embodiments.
  • the processor 610 is used to implement the operations performed internally by the first functional network element in the above method embodiments
  • the transceiver 630 is used to implement the receiving or sending operations performed by the first functional network element in the above method embodiments .
  • the processing unit 420 in the apparatus 400 may be the processor in FIG. 15
  • the transceiver unit 410 may be the transceiver in FIG. 15 .
  • the communication device 600 is configured to implement the operations performed by the network element of the first control plane core network in the above method embodiments.
  • the processor 610 is used to implement the operations performed internally by the network element of the first control plane core network in the above method embodiment
  • the transceiver 630 is used to implement the operation performed by the network element of the first control plane core network in the above method embodiment.
  • the processing unit 420 in the apparatus 400 may be the processor in FIG. 15
  • the transceiver unit 410 may be the transceiver in FIG. 15 .
  • the communication device 600 is configured to implement the operations performed by the network element of the third control plane core network in the above method embodiments.
  • the processor 610 is used to implement the operation performed by the third control plane core network element in the above method embodiment
  • the transceiver 630 is used to implement the operation performed by the third control plane core network element in the above method embodiment.
  • the processing unit 420 in the apparatus 400 may be the processor in FIG. 15
  • the transceiver unit 410 may be the transceiver in FIG. 15 .
  • the present application also provides a computer-readable medium, the computer-readable medium stores program codes, and when the program codes are run on a computer, the computer is made to perform the operations shown in Figures 3-11. The method of any one of the embodiments is illustrated.
  • the computer when the computer program is executed by a computer, the computer can implement the method executed by the first ECS in the above method embodiments, or the method executed by the second ECS, or the method executed by the terminal device, or the method executed by the first function A method performed by a network element, or a method performed by a network element of the first control plane core network, or a method performed by a network element of the third control plane core network.
  • the embodiment of the present application also provides a computer program product containing instructions, which, when executed by a computer, enable the computer to implement the method executed by the first ECS in the above method embodiment, or the method executed by the second ECS, or the method executed by the terminal.
  • An embodiment of the present application further provides a communication system, where the communication system includes the first ECS, the second ECS and the terminal device in the above embodiments.
  • the communication system further includes the first functional network element in the above embodiments, or the first control plane core network element, or the third control plane core network element.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • 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 available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (digital video disc, DVD)
  • a semiconductor medium for example, a solid state disk (solid state disc, SSD)
  • the network element corresponds to the core network element of the control plane, and corresponding steps are performed by corresponding modules or units, for example, the communication unit (transceiver) performs the steps of receiving or sending in the method embodiments, and other steps except sending and receiving can be performed by
  • the processing unit (processor) executes.
  • the functions of the specific units reference may be made to the corresponding method embodiments. Wherein, there may be one or more processors.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can be components.
  • One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more packets of data (e.g., data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet via a signal interacting with other systems). Communicate through local and/or remote processes.
  • packets of data e.g., data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet via a signal interacting with other systems.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: various media that can store program codes such as U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种获取边缘服务的方法和装置，该方法包括：若第一边缘配置服务器ECS确定该第一ECS管理的EES不能为终端设备提供边缘服务，则该第一ECS获取第二ECS的信息，该第一ECS向第一设备发送第一信息，该第一信息包括第一EES的信息或该第二ECS的信息，该第一EES为第二ECS管理的EES。通过本申请提供的方法和装置，可以使得在ECS的配置信息发生变更时，或者终端设备处于漫游场景时，能够获取边缘服务。

Description

获取边缘服务的方法和装置
本申请要求于2021年8月18日提交中国专利局、申请号为202110950242.7、申请名称为“获取边缘服务的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，并且更具体地，涉及一种获取边缘服务的方法和装置。
背景技术
用户设备(user equipment，UE)要获取边缘服务一般采用如下方案：边缘使能客户端(edge enabler client，EEC)作为UE的一部分，会先在EEC上配置边缘配置服务器(edge configuration server，ECS)的地址信息，然后，EEC向ECS发送服务配置请求(service provisioning request)或服务订阅请求(service subscription update request)以获取边缘使能服务器(edge enabler server，EES)的地址信息，UE或EEC获取到EES的地址信息后，EEC向EES发送EAS发现请求(EAS discovery request)以获取边缘应用服务器(edge application server，EAS)的地址信息，进一步获取边缘服务。
在现有技术中，ECS的地址信息除了配置在EEC上之外，还可以配置在统一数据管理(unified data management，UDM)网元中，在会话建立过程中，由UDM将ECS的地址信息通过会话管理功能(session management function，SMF)转发给UE。
上述将ECS的地址信息预配置在EEC或UDM中的情况下，如果ECS的地址信息发生变化，或者UE在漫游的场景下，想访问的ECS与预配置的ECS不同时，或者，UE移出某个ECS的服务范围时，该UE无法通过预配置的ECS获取边缘服务。
发明内容
本申请提供了一种获取边缘服务的方法和装置，可以使得在ECS的配置信息发生变更时，或者终端设备处于漫游场景时，或者，终端设备移出某个ECS的服务范围时，能够获取其它ECS提供的边缘服务。
第一方面，提供了一种获取边缘服务的方法。该方法可以由第一ECS执行，或者，也可以由配置在第一ECS中的部件(如芯片或芯片系统等)执行，本申请对此不作限定。该方法包括：若第一边缘配置服务器ECS确定该第一ECS管理的EES不能为终端设备提供边缘服务，第一ECS获取第二ECS的信息，第一ECS向第一设备发送第一信息，该第一信息包括第一EES的信息或该第二ECS的信息，第一EES为第二ECS管理的EES。
基于上述方案，能使得终端设备在漫游场景下，或者为终端设备预配置的ECS发生变更或者终端设备移出某个ECS的服务范围的场景下，获取能够为终端设备提供边缘服务的ECS，或者EES。
结合第一方面，在某些可能的实现方式中，第一ECS根据配置信息获取该第二ECS的信息。
基于上述方案，第一ECS配置其他ECS的配置文件，因此可根据配置的其他ECS的配置文件获取第二ECS的信息。
结合第一方面，在某些可能的实现方式中，第一ECS向联邦控制网元发送第一请求信息，该第一请求信息用于请求第二ECS的信息，第一ECS接收来自联邦控制网元的第一响应信息，第一响应信息包括第二ECS的信息。
基于上述方案，ECS可将配置文件注册至联邦控制网元，因此，第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务时，可向联邦控制网元查询能为终端设备提供边缘服务的EES，从而确定该EES对应的ECS。
结合第一方面，在某些可能的实现方式中，第一ECS向第二ECS发送第二请求信息，该第二请求信息用于请求第一EES的信息，第一ECS接收来自第二ECS的第二响应信息，该第二响应信息包括第一EES的信息。
基于上述方案，当第一ECS根据本地配置，或者向联邦控制网元查询到第二ECS的信息后，向第二ECS请求能为终端设备提供服务的EES。
结合第一方面，在某些可能的实现方式中，第一ECS接收来自第一设备的第三请求信息，第三请求信息用于请求该第一EES的信息，第一ECS根据第三请求信息确定该第一ECS管理的EES不能为终端设备提供边缘服务。
基于上述方案，第一设备可以为终端设备，EEC，或EES，本申请对此不做任何限制。例如，第一设备为终端设备，终端设备向预配置的或网络侧下发的ECS(第一ECS)获取能为终端设备提供边缘服务的EES时，可能由于终端设备的位置发生了移动等原因，第一ECS管理的EES不能为终端设备提供边缘服务，此时第一ECS可通过本地配置，或者向联邦控制网元查询其他ECS，从而获取能为终端设备提供边缘服务的EES。
结合第一方面，在某些可能的实现方式中，第一请求信息，第二请求信息，或第三请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，第一EES的特征信息，应用信息。
第二方面，提供了一种获取边缘服务的方法。该方法可以由第二ECS执行，或者，也可以由配置在第二ECS中的部件(如芯片或芯片系统等)执行，本申请对此不作限定。该方法包括：第二边缘配置服务器ECS接收来自第一ECS的第二请求信息，该第二请求信息用于请求第一EES的信息，第二ECS根据第二请求信息确定第一EES的信息，第二ECS向第一ECS发送第二响应信息，该第二响应信息包括第一EES的信息。
结合第二方面，在某些可能的实现方式中，第二请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，第一EES的特征信息，应用信息，终端设备的位置信息。
结合第二方面，在某些可能的实现方式中，第二ECS根据该第二请求信息，以及本地的ECS配置文件确定第一EES的信息，该ECS配置文件包括以下至少一项：ECS的地址信息，ECS的服务范围，ECS管理的EES配置文件，ECS的ECSP标识，ECS对应的PLMN标识。
基于上述方案，第二ECS根据第二请求信息中的PLMN标识，以及ECS配置文件的 中的PLMN标识确定第一EES的信息。或第二ECS根据第二请求信息中的ECSP标识，以及ECS配置文件的中的ECSP标识确定第一EES的信息。或第二ECS根据第二请求信息中的第一EES的特征信息，以及ECS配置文件的中的ECS管理的EES配置文件确定第一EES的信息。或第二ECS根据第二请求信息中的应用信息，以及ECS配置文件的中的ECS管理的EES配置文件确定第一EES的信息。或第二ECS根据第二请求信息中的终端设备的位置信息，以及ECS配置文件的中的ECS的服务范围确定第一EES的信息。当然，第二ECS还可根据第二请求信息中的两项或者两项以上确定第一EES的信息，本申请对此不做任何限制。
第三方面，提供了一种获取边缘服务的方法。该方法可以由终端设备执行，或者，也可以由配置在终端设备中的部件(如芯片或芯片系统等)执行，本申请对此不作限定。该方法包括：终端设备向第一功能网元发送第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息，终端设备接收来自该第一功能网元的第一响应信息，该第一响应信息包括第一ECS的信息。
基于上述方案，ECS将配置文件注册在第一功能网元上，从而终端设备可以获取能为终端设备提供边缘服务的ECS，与现有技术中预配置ECS的方案相比，本申请提供的方案不用使不同的运营商给终端设备配置不同的ECS，所有终端设备均通过第一功能网元发现ECS，更加灵活，适用范围更广。
结合第三方面，在某些可能的实现方式中，终端设备获取第一功能网元的地址信息。
基于上述方案，可将第一功能网元的地址信息配置在终端设备，或者配置在EEC，或者配置在核心网网元。若将第一功能网元的地址信息配置在核心网网元，可由核心网网元将其下发至终端设备。
结合第三方面，在某些可能的实现方式中，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
第四方面，提供了一种获取边缘服务的方法。该方法可以由第一功能网元执行，或者，也可以由配置在第一功能网元中的部件(如芯片或芯片系统等)执行，本申请对此不作限定。该方法包括：第一功能网元接收来自终端设备的第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息，第一功能网元根据该第一请求信息确定第一ECS，第一功能网元向终端设备发送第一响应信息，该第一响应信息包括该第一ECS的信息。
结合第四方面，在某些可能的实现方式中，第一功能网元为第一ECS发现代理，第一ECS发现代理根据该第一请求信息和/或本地配置确定第二ECS发现代理的信息，第一ECS发现代理向第二ECS发现代理发送第二请求信息，该第二请求信息用于请求第一ECS的信息，第一ECS发现代理接收来自第二ECS发现代理的第二响应信息，该第二响应信息包括第一ECS的信息。
基于上述方案，ECS发现代理存储多个ECS的配置文件，并且ECS发现代理配置其他ECS发现代理的信息，从而ECS发现代理之间可以交互获取各自存储的ECS的信息。
结合第四方面，在某些可能的实现方式中，第一ECS发现代理根据第一请求信息，向联邦控制网元发送第三请求信息，该第三请求信息用于请求第二ECS发现代理的信息，第一ECS发现代理接收来自联邦控制网元的第三响应信息，该第三响应信息包括第二ECS发现代理的信息。
基于上述方案，ECS发现代理存储多个ECS的配置文件，ECS发现代理向联邦控制网元注册，从而ECS发现代理可向联邦控制网元查询其他ECS发现代理的信息。
结合第四方面，在某些可能的实现方式中，第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
第五方面，提供了一种获取边缘服务的方法。该方法可以由第一控制面核心网网元执行，或者，也可以由配置在第一控制面核心网网元中的部件(如芯片或芯片系统等)执行，本申请对此不作限定。该方法包括：第一网络的第一控制面核心网网元接收来自第二网络的第二控制面核心网网元的第一指示信息，该第一指示信息指示终端设备支持接入第一网络的边缘服务，第一控制面核心网网元根据第一指示信息向第一网络的第三控制面核心网网元发送第一请求信息，该第一请求信息用于请求第一网络的第一边缘配置服务器ECS的信息，第一控制面核心网网元接收来自第三控制面核心网网元的第一响应信息，该第一响应信息包括第一ECS的信息。
在上述方案中，例如，第一网络为拜访域的网络，第二网络为归属域的网络，归属域的网络的控制面核心网网元通过指示信息告知拜访域的网络的控制面核心网网元，终端设备支持接入第一网络的边缘服务，从而获取在拜访域网络下能为终端设备提供边缘服务的ECS信息。
结合第五方面，在某些可能的实现方式中，第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
第六方面，提供了一种获取边缘服务的方法。该方法可以由第三控制面核心网网元执行，或者，也可以由配置在第三控制面核心网网元中的部件(如芯片或芯片系统等)执行，本申请对此不作限定。该方法包括：第三控制面核心网网元接收来自第一控制面核心网网元的第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息，第三控制面核心网网元根据第一请求信息确定第一ECS的信息，第三控制面核心网网元向第一控制面核心网网元发送第一响应信息，该第一响应信息包括第一ECS的信息。
结合第六方面，在某些可能的实现方式中，第三控制面核心网网元根据PLMN标识，以及PLMN标识与ECS的对应关系确定该第一ECS的信息，和/或，第三控制面核心网网元根据ECSP标识，以及该ECSP标识与ECS的对应关系确定第一ECS的信息，和/或，第三控制面核心网网元根据终端设备的位置信息以及ECS的服务范围确定第一ECS的信息。
第七方面，提供了一种获取边缘服务的装置。该装置可以是第一ECS，或者，也可以是配置在第一ECS中的部件(如芯片或芯片系统等)，本申请对此不作限定。该装置包 括收发单元和处理单元：若确定第一ECS管理的EES不能为终端设备提供边缘服务，该处理单元用于获取第二ECS的信息，该收发单元用于向第一设备发送第一信息，该第一信息包括第一EES的信息或该第二ECS的信息，第一EES为第二ECS管理的EES。
基于上述方案，能使得终端设备在漫游场景下，或者为终端设备预配置的ECS发生变更或者终端设备移出某个ECS的服务范围的场景下，获取能够为终端设备提供边缘服务的ECS，或者EES。
结合第七方面，在某些可能的实现方式中，该处理单元用于根据配置信息获取该第二ECS的信息。
基于上述方案，第一ECS配置其他ECS的配置文件，因此可根据配置的其他ECS的配置文件获取第二ECS的信息。
结合第七方面，在某些可能的实现方式中，该收发单元还用于向联邦控制网元发送第一请求信息，该第一请求信息用于请求第二ECS的信息，该收发单元还用于接收来自联邦控制网元的第一响应信息，第一响应信息包括第二ECS的信息。
基于上述方案，ECS可将配置文件注册至联邦控制网元，因此，第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务时，可向联邦控制网元查询能为终端设备提供边缘服务的EES，从而确定该EES对应的ECS。
结合第七方面，在某些可能的实现方式中，该收发单元还用于向第二ECS发送第二请求信息，该第二请求信息用于请求第一EES的信息，该收发单元还用于接收来自第二ECS的第二响应信息，该第二响应信息包括第一EES的信息。
基于上述方案，当第一ECS根据本地配置，或者向联邦控制网元查询到第二ECS的信息后，向第二ECS请求能为终端设备提供服务的EES。
结合第七方面，在某些可能的实现方式中，该收发单元还用于接收来自第一设备的第三请求信息，第三请求信息用于请求该第一EES的信息，该处理单元还用于根据第三请求信息确定该第一ECS管理的EES不能为终端设备提供边缘服务。
基于上述方案，第一设备可以为终端设备，EEC，或EES，本申请对此不做任何限制。例如，第一设备为终端设备，终端设备向预配置或网络侧下发的ECS(第一ECS)获取能为终端设备提供边缘服务的EES时，可能由于终端设备的位置发生了移动等原因，第一ECS管理的EES不能为终端设备提供边缘服务，此时第一ECS可通过本地配置，或者向联邦控制网元查询其他ECS，从而获取能为终端设备提供边缘服务的EES。
结合第七方面，在某些可能的实现方式中，第一请求信息，第二请求信息，或第三请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，第一EES的特征信息，应用信息。
第八方面，提供了一种获取边缘服务的装置。该装置可以是第二ECS，或者，也可以是配置在第二ECS中的部件(如芯片或芯片系统等)，本申请对此不作限定。该装置包括收发单元和处理单元：该收发单元用于接收来自第一ECS的第二请求信息，该第二请求信息用于请求第一EES的信息，该处理单元用于根据第二请求信息确定第一EES的信息，该收发单元还用于向第一ECS发送第二响应信息，该第二响应信息包括第一EES的信息。
结合第八方面，在某些可能的实现方式中，第二请求信息包括以下至少一项：终端设 备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，第一EES的特征信息，应用信息，终端设备的位置信息。
结合第八方面，在某些可能的实现方式中，该处理单元还用于根据该第二请求信息，以及本地的ECS配置文件确定第一EES的信息，该ECS配置文件包括以下至少一项：ECS的地址信息，ECS的服务范围，ECS管理的EES配置文件，ECS的ECSP标识，ECS对应的PLMN标识。
基于上述方案，第二ECS根据第二请求信息中的PLMN标识，以及ECS配置文件的中的PLMN标识确定第一EES的信息。或第二ECS根据第二请求信息中的ECSP标识，以及ECS配置文件的中的ECSP标识确定第一EES的信息。或第二ECS根据第二请求信息中的第一EES的特征信息，以及ECS配置文件的中的ECS管理的EES配置文件确定第一EES的信息。或第二ECS根据第二请求信息中的应用信息，以及ECS配置文件的中的ECS管理的EES配置文件确定第一EES的信息。或第二ECS根据第二请求信息中的终端设备的位置信息，以及ECS配置文件的中的ECS的服务范围确定第一EES的信息。当然，第二ECS还可根据第二请求信息中的两项或者两项以上确定第一EES的信息，本申请对此不做任何限制。
第九方面，提供了一种获取边缘服务的装置。该装置可以是终端设备，或者，也可以是配置在终端设备中的部件(如芯片或芯片系统等)，本申请对此不作限定。该装置包括收发单元：该收发单元用于向第一功能网元发送第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息，该收发单元还用于接收来自该第一功能网元的第一响应信息，该第一响应信息包括第一ECS的信息。
基于上述方案，ECS将配置文件注册在第一功能网元上，从而终端设备可以获取能为终端设备提供边缘服务的ECS，与现有技术中预配置ECS的方案相比，本申请提供的方案不用使不同的运营商给终端设备配置不同的ECS，所有终端设备均通过第一功能网元发现ECS，更加灵活，适用范围更广。
结合第九方面，在某些可能的实现方式中，该装置还包括处理单元，该处理单元用于获取第一功能网元的地址信息。
基于上述方案，可将第一功能网元的地址信息配置在终端设备，或者配置在EEC，或者配置在核心网网元。若将第一功能网元的地址信息配置在核心网网元，可由核心网网元将其下发至终端设备。
结合第九方面，在某些可能的实现方式中，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
第十方面，提供了一种获取边缘服务的装置。该装置可以是第一功能网元，或者，也可以是配置在第一功能网元中的部件(如芯片或芯片系统等)，本申请对此不作限定。该装置包括收发单元和处理单元：该收发单元用于接收来自终端设备的第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息，该处理单元用于根据该第一请求信息确定第一ECS，该收发单元还用于向终端设备发送第一响应信息，该第一响 应信息包括该第一ECS的信息。
结合第十方面，在某些可能的实现方式中，第一功能网元为第一ECS发现代理，该处理单元具体用于根据该第一请求信息和/或本地配置确定第二ECS发现代理的信息，该收发单元还用于向第二ECS发现代理发送第二请求信息，该第二请求信息用于请求第一ECS的信息，该收发单元还用于接收来自第二ECS发现代理的第二响应信息，该第二响应信息包括第一ECS的信息。
基于上述方案，ECS发现代理存储多个ECS的配置文件，并且ECS发现代理配置其他ECS发现代理的信息，从而ECS发现代理之间可以交互获取各自存储的ECS的信息。
结合第十方面，在某些可能的实现方式中，该处理单元用于根据第一请求信息，控制该收发单元向联邦控制网元发送第三请求信息，该第三请求信息用于请求第二ECS发现代理的信息，该收发单元还用于接收来自联邦控制网元的第三响应信息，该第三响应信息包括第二ECS发现代理的信息。
基于上述方案，ECS发现代理存储多个ECS的配置文件，ECS发现代理向联邦控制网元注册，从而ECS发现代理可向联邦控制网元查询其他ECS发现代理的信息。
结合第十方面，在某些可能的实现方式中，第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
第十一方面，提供了一种获取边缘服务的装置。该装置可以是第一控制面核心网网元执行，或者，也可以是配置在第一控制面核心网网元中的部件(如芯片或芯片系统等)，本申请对此不作限定。该装置包括收发单元和处理单元：该收发单元用于接收来自第二网络的第二控制面核心网网元的第一指示信息，该第一指示信息指示终端设备支持接入第一网络的边缘服务，该处理单元用于根据第一指示信息控制该收发单元向第一网络的第三控制面核心网网元发送第一请求信息，该第一请求信息用于请求第一网络的第一边缘配置服务器ECS的信息，该收发单元还用于接收来自第三控制面核心网网元的第一响应信息，该第一响应信息包括第一ECS的信息。
在上述方案中，例如，第一网络为拜访域的网络，第二网络为归属域的网络，归属域的网络的控制面核心网网元通过指示信息告知拜访域的网络的控制面核心网网元，终端设备支持接入第一网络的边缘服务，从而获取在拜访域网络下能为终端设备提供边缘服务的ECS信息。
结合第十一方面，在某些可能的实现方式中，第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
第十二方面，提供了一种获取边缘服务的装置。该装置可以是第三控制面核心网网元，或者，也可以是配置在第三控制面核心网网元中的部件(如芯片或芯片系统等)，本申请对此不作限定。该装置包括收发单元和处理单元：该收发单元用于接收来自第一控制面核心网网元的第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息，该处理单元用于根据第一请求信息确定第一ECS的信息，该收发单元还用于向第一控制面核心网网元发送第一响应信息，该 第一响应信息包括第一ECS的信息。
结合第十二方面，在某些可能的实现方式中，该处理单元具体用于根据PLMN标识，以及PLMN标识与ECS的对应关系确定该第一ECS的信息，和/或，该处理单元具体用于根据ECSP标识，以及该ECSP标识与ECS的对应关系确定第一ECS的信息，和/或，该处理单元具体用于根据终端设备的位置信息以及ECS的服务范围确定第一ECS的信息。
第十三方面，提供一种通信装置，该装置包括处理器，该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面至第三方面中任一方面或第一方面至第三方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，该存储器与处理器可能是分离部署的，也可能是集中部署的。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于第一ECS，或第二ECS，或终端设备中的芯片。当该装置为配置于第一ECS，或第二ECS，或终端设备中的芯片时，该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
可选地，该收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是但不限于接收器接收并输入的，输出电路所输出的信号可以是但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十四方面，提供一种通信装置，该装置包括处理器，该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第四方面至第六方面中任一方面或第四方面至第六方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，该存储器与处理器可能是分离部署的，也可能是集中部署的。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于第一功能网元，或第一控制面核心网网元，第三控制面核心网网元中的芯片。当该装置为配置于第一功能网元，或第一控制面核心网网元，第三控制面核心网网元中的芯片时，该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
可选地，该收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是但不限于接收器接收并输入的，输出电路所输出的信 号可以是但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十五方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述第一方面至第六方面中的任一方面，以及第一方面至第六方面中任一种可能实现方式中的方法。
第十六方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第六方面中的任一方面，以及第一方面至第六方面中任一种可能实现方式中的方法。
附图说明
图1本申请实施例适用系统架构图。
图2是本申请实施例边缘业务架构示意图。
图3-图11是本申请提供的获取边缘服务的方法的交互流程图。
图12是本申请实施例提供的一种通信装置的示意性框图。
图13是本申请实施例提供的另一种通信装置的示意性框图。
图14是本申请实施例提供的一种通信装置的结构示意图。
图15是本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提及的无线通信系统包括但不限于：全球移动通信(global system of mobile communication，GSM)系统、长期演进(long term evolution，LTE)频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、LTE系统、先进的长期演进(LTE-Advanced，LTE-A)系统、下一代通信系统(例如，6G通信系统)、多种接入系统的融合系统，或演进系统。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(Long Term Evolution-machine，LTE-M)、设备到设备(device to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
下面结合图1和图2详细介绍本申请实施例涉及网络系统架构以及该架构下的边缘业务架构。
图1是本申请实施例适用的系统架构图100，如图所示，该网络架构100具体可以包括下列网元：
1、无线接入网(radio access network，RAN)：基于无线通信技术实现接入网络功能 的接入网可以称为无线接入网。无线接入网能够管理无线资源，为终端提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以是全球移动通讯(global system of mobile communication，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(nodeB，NB)，还可以是LTE系统中的演进型基站(evolutional nodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
2、认证服务功能(authentication server function，AUSF)网元：主要用于用户鉴权等。
3、接入和移动性管理功能网元(access and mobility management function，AMF)：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。在本申请实施例中，可用于实现接入和移动管理网元的功能。
4、会话管理功能网元(session management function，SMF)：主要用于会话管理、终端设备的IP地址分配和管理、选择和管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
5、策略控制网元(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
6、应用功能网元(application function，AF)：用于进行应用影响的数据路由，接入网络开放功能网元，或，与策略框架交互进行策略控制等。
7、统一数据管理网元(unified data management，UDM)：用于统一数据管理、5G用户数据管理、处理用户标识、接入鉴权、注册、或移动性管理等。
8、用户面功能网元(user plane function，UPF)：可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网元的功能。
9、网络切片选择功能网元(network slice selection function，NSSF)：用于管理网络切片相关的信息。
10、数据网络(digital network,DN)：用于提供传输数据的网络。例如，运营商业务的网络、因特(Internet)网、第三方的业务网络等。
11、用户设备(user equipment，UE)：用户设备也可以称为终端、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL) 站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端或者未来演进网络中的终端等。
其中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在未来的通信系统，例如6G通信系统中，上述网元或设备仍可以使用其在5G通信系统中的名称，或者也可以有其它名称，本申请实施例对此不作限定。上述网元或设备的功能可以由一个独立网元完成，也可以由若干个网元共同完成。在实际部署中，核心网中的网元可以部署在相同或者不同的物理设备上。例如作为一种可能的部署，可以将AMF和SMF部署在同一个物理设备上。又例如，5G核心网的网元可以和4G核心网的网元部署在同一物理设备上。本申请实施例对此不作限定。
可以理解，图1只是一种示例，对本申请的保护范围不构成任何限定。本申请实施例提供的通信方法还可以涉及图1中未示出的网元，当然本申请实施例提供的通信方法也可以只包括图1示出的部分网元。
另外，上述网络架构还包括网络存储功能网元((network function(NF)repository function，NRF)：用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等；网络开放功能网元(network exposure function，NEF)：用于安全地向外部开放由第三代合作伙伴计划(3GPP)网络功能提供的业务和能力等。统一数据存储功能(unified data repository，UDR)，用于UDM存储订阅数据或读取订阅数据以及PCF存储策略数据或者读取策略数据。
需要说明的是本申请中的网络系统架构还可以包括边缘配置服务器(edge configuration server，ECS)网元，ECS网元可以是全局管理网元，维护各个边缘数据网络(edge data network，EDN)的信息，包括边缘数据网络的服务范围和边缘数据网络中的边缘使能服务器(edge enabler server，EES)地址等。其中，边缘数据网络的服务范围可以是拓扑地址信息(例如Cell ID、TAI(Trach area id)等)或几何地址信息(例如，省、市、区或经纬度等信息)，服务范围可以是地址信息的集合。在一种实现方式中，ECS网元是分布式部署的，即每个ECS可以管理不同区域的边缘数据网络。应该理解ECS网元可以与其它网元合设也可以是独立的网元，本申请对ECS网元在网络架构中的部署情况并不做任何限定。
需要说明的是本申请中的网络系统架构还可以包括边缘使能服务器(edge enabler server，EES)网元，EES网元可以是移动边缘计算(mobile edge computing，MEC)节点(MEC也可称为多接入边缘计算(multi acess edge computing))中的控制网元或者管理网元，负责管理部署在该EDN里的各个EAS，比如注册，域名系统(domain name system，DNS)解析内容路由选择、上层应用注册管理、无线信息交互等基础功能。此外，EES可 以调用3GPP网络中的能力开放功能网元。应该理解EES网元可以与其它网元合设也可以是独立的网元，本申请对EES网元在网络架构中的部署情况并不做任何限定。
在该网络架构中，N2接口为RAN和AMF网元的接口，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN和UPF网元之间的接口，用于传输用户面的数据等；N4接口为SMF网元和UPF网元之间的接口，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
应理解，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图2是本申请实施例边缘业务架构示意图，如图所示，该网络架构200具体可以包括：边缘数据网络(edge data network，EDN)可以是本地数据中心，EDN包含边缘使能服务器(edge enabler server，EES)和多个边缘应用服务器(edge application server，EAS)，每个EDN有特定的服务范围。其中，EES可以是移动边缘计算(mobile edge computing，MEC)节点(MEC也可称为多接入边缘计算(multi acess edge computing))中的控制网元或者管理网元，负责管理部署在该EDN里的各个EAS，比如注册，域名系统(domain name system，DNS)解析内容路由选择、上层应用注册管理、无线信息交互等基础功能。此外，EES可以调用3GPP网络中的能力开放功能网元。边缘数据网络配置服务器(edge data network configuration server，EDNCS)或者边缘配置服务器(edge configuration server，ECS)可以是全局管理网元，维护各个EDN的信息，包括服务范围和EES地址等。需要说明的是，在有的标准协议中，比如技术规范(technical specification，TS)23.501、TS23.502等，上述EES，EAS，ECS等都可以称之为AF(application function)，以下不再赘述。
用户设备(user equipment，UE)中可以包括：边缘使能客户端(edge enabler client，EEC)和应用客户端，其中，EEC为终端上的应用客户端提供必要的支持，EEC的功能包括：通过EDGE-4检索EDN信息、UE注册到EES、检索可用的EAS、EAS可用性变化、EAS迁移通知给EEC。
图2中的EDGE-8参考点支持边缘配置服务器和核心网之间的交互，它支持：(1)访问用于检索网络能力信息的核心网功能和应用程序接口(application programming interface，API)；(2)向核心网(例如：SMF)提供业务发放通知。EDGE-1：EES与EEC之间的接口，支持EEC在EES的注册/去注册；边缘数据网络中的边缘应用服务器发现。EDGE-2：EES与3GPP核心网之间的接口，用于EES获取3GPP网络能力。EDGE-3：EES与EAS之间的接口，支持EES注册/去注册EAS，包括EAS的可用性信息、服务范围信息、地址信息等；EES给EAS提供3GPP网络能力信息(如位置信息)。EDGE-4：EEC与ECS之间的接口，支持ECS提供/推送配置信息给EEC。EDGE-5：AC与EEC之间的接口，支持AC从EEC获取接入的EAS信息。EDGE-6：ECS与EES之间的接口，支持在ECS上配置EES信息。EDGE-7：EAS与3GPP核心网之间的接口，支持EAS获取3GPP网络能力。EDGE-8：ECS与3GPP核心网之间的接口，支持ECS获取3GPP网 络能力。EDGE-9：跨MEC节点/同一MEC节点内不同EES之间的接口，支持做应用迁移。
在现有技术中，采用预配置的方式，将ECS预配置在终端设备，或者将ECS预配置在EEC，或者将ECS预配置在UDM。
终端设备要获取边缘服务一般采用如下方案：边缘使能客户端EEC作为UE的一部分，EEC向预配置的ECS发送服务配置请求(service provisioning request)或服务订阅请求(service subscription update request)以获取边EES的地址信息，UE或EEC获取到EES的地址信息后，EEC向EES发送EAS发现请求(EAS discovery request)以获取边缘应用服务器EAS的地址信息，进一步获取边缘服务。
上述采用预配置ECS的方案，如果ECS的信息发生变化，想访问的ECS与配置的ECS不同时，该UE无法通过预配置的ECS获取边缘服务，此时，因为预配置的过程一般是静态的，只会执行一次，若要更新预配置的ECS信息，从而通过更新后ECS信息获取边缘服务的难度较大，不易实现。因为更新预配置的ECS信息可能需要重新安装软件或重启终端设备才能使实现。
若存在多个ECS或者UE在漫游的场景下，在UDM配置多个ECS可能会造成UDM的负载过重，并且在现有技术中，UDM只配置归属域的ECS的配置信息。此时，若终端设备移动至拜访域网络覆盖的范围内，则不能通过预配置的归属域的ECS的配置信息获取边缘服务，同时终端设备也无法获得拜访域的ECS的配置信息，因此也无法通过拜访域的ECS的配置信息获取边缘服务。
本申请提出一种获取边缘服务的方法，能够使得终端设备在想访问的ECS发生变更后，获取能为终端设备提供边缘服务的ECS。
图3是本申请提供的一种获取边缘服务的方法的交互流程图。图3示出的方法100包括：
步骤S110，若第一边缘配置服务器ECS确定该第一ECS管理的EES不能为终端设备提供边缘服务，第一ECS获取第二ECS的信息。或者说，第一ECS确定该第一ECS不能为终端设备提供边缘服务，第一ECS获取第二ECS的信息。
其中，EES会将EES配置文件(profile)注册到ECS上，若某个EES注册到了某个ECS，则可以视为该EES由该ECS管理，即第一ECS管理的EES可以理解成注册到第一ECS上的EES。其中，EES profile可以包含以下至少一项：EES标识、EES端点信息(endpoint)、注册的EAS信息、边缘计算服务提供商(edge computing service provider，ECSP)信息、EES服务范围、EES所关联的数据网络接入标识(data network access identifier，DNAI)。应理解，本申请中，第一ECS管理的EES能为终端设备提供边缘服务，需要满足EES上管理或者注册了终端设备想要访问的EAS的信息。若EES上未注册终端设备想要访问EAS的信息，即使EES的服务范围或者注册的其它EAS的服务范围包括了终端设备所在的位置区域，也将视为第一ECS管理的EES不能为终端设备提供边缘服务。在一种实现方式中，EAS注册到EES上，EES注册到ECS上，因此ECS可以确定自身管理的EES分别管理了哪些EAS。
第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务可以分为以下几种情况：
情况1：第一ECS确定该第一ECS管理的EES不能为终端设备提供边缘服务。例如，终端设备所在的位置为区域1，第一ECS管理的EES的服务范围不包括区域1，则第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务。其中，第一ECS可以管理多个EES，各EES的服务范围均不包括区域1。
情况2：第一ECS确定该第一ECS不能为终端设备提供边缘服务。例如，终端设备请求的ECSP标识为ECSP_1,而第一ECS对应的ECSP是ECSP_2，或者第一ECS管理的EES对应的ECSP为ECSP_2,则第一ECS确定第一ECS不能为终端设备提供边缘服务。或者，终端设备接入PLMN_1,而第一ECS对应的ECSP是PLMN_2，或者ECS管理的EES对应的ECSP为PLMN_2，则第一ECS确定第一ECS不能为终端设备提供边缘服务。又例如，终端设备所在的位置为区域1，第一ECS的服务范围不包括区域1，则第一ECS确定第一ECS不能为终端设备提供边缘服务。其中，ECS的服务范围可以具体的由一个或多个服务区域组成，也可以是ECS管理的各EES的服务范围组成的集合。
情况3：第一ECS管理的EES虽然能为终端设备提供边缘服务，但服务的质量可能不是最优的，第一ECS可以尝试从第二ECS获取第二ECS管理的EES信息，从而确定最优的EES为终端设备提供边缘服务。例如，终端设备所在的位置为区域1，第一ECS管理的EES的服务范围包括区域1，但第一ECS仍然可以查找第二ECS并从第二ECS获取EES信息。在一种实现方式中，第一ECS通过终端设备的签约数据(例如终端设备既签约了第一ECS，又签约了第二ECS)确定终端设备可以接入第二ECS，第一ECS尝试从第二ECS获取第二ECS管理的EES信息。可选的，第一ECS从第一ECS管理的EES和第二ECS管理的EES中确定一个最优的EES为UE提供服务。
情况4：虽然第一ECS管理的EES的服务范围包括终端设备所在的位置为区域1，但EES上没有管理或者注册了终端设备想要访问的EAS的信息。
应理解，第一边缘配置服务器ECS确定该第一ECS管理的EES不能为终端设备提供边缘服务，也可以理解成第一ECS确定没有EAS能为终端设备提供边缘服务，即可以是情况1，也可以是情况2或情况3或情况4，后文中出现第一ECS确定该第一ECS管理的EES不能为终端设备提供边缘服务也是如此，以下不再赘述。
可选地，该方法100还包括：
步骤S101，第一设备向第一ECS发送第三请求信息，第三请求信息用于请求该第一EES的信息。对应的，第一ECS接收该第三请求信息。
示例地，第三请求信息可以为服务提供请求(service provisioning request)，也可以为EES发现请求(EES discovery request)，本申请对具体信息或消息名称不做限定，后文出现的信息或消息名称同样也仅为举例，不对本申请构成任何限定。
可选地，第三请求信息包括以下至少一项：终端设备接入的公共陆地移动网(public land mobile network，PLMN)标识，边缘计算服务提供商(edge computing service provider，ECSP)标识，终端设备的位置信息，EES的特征信息(可以是上述EES profile中的任意一项或多项)或EAS的特征信息，请求的应用的信息。
第一ECS接收该第三请求信息后，根据第三请求信息确定该第一ECS管理的EES不能为终端设备提供边缘服务(即第一ECS管理的EES不包括第一EES，从而确定该第一ECS管理的EES不能为终端设备提供边缘服务)。或者，第一ECS尝试从第二ECS获取 第二ECS管理的EES信息，从而确定最优的EES为终端设备提供边缘服务。
示例地，第一ECS根据终端设备接入的PLMN标识确定第一ECS管理的EES不能为终端设备提供边缘服务。例如，终端设备接入PLMN_1,而第一ECS对应的ECSP是PLMN_2，或者第一ECS管理的EES对应的ECSP为PLMN_2，则第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务；或
第一ECS根据终端设备接入的ECSP标识确定第一ECS管理的EES不能为终端设备提供边缘服务。例如，终端设备请求的ECSP标识为ECSP_1,而第一ECS对应的ECSP是ECSP_2，或者第一ECS管理的EES对应的ECSP为ECSP_2,则第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务；或
第一ECS根据终端设备的位置信息确定第一ECS管理的EES不能为终端设备提供边缘服务。例如，终端设备的位置信息为位置_1,而第一ECS的服务范围不包括位置_1，或者第一ECS管理的EES对应的服务范围不包括位置_1,则第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务；或
第一ECS根据EES的特征信息确定第一ECS管理的EES不能为终端设备提供边缘服务。例如，终端设备或EES请求ECSP标识为ECSP_1的EES,而第一ECS对应的ECSP是ECSP_2，或者第一ECS管理的EES对应的ECSP为ECSP_2,则第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务。
应理解，第一ECS也可根据终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES的特征信息中的两项或两项以上确定第一ECS管理的EES不能为终端设备提供边缘服务，本申请对此不做任何限制。
第一ECS可通过以下至少一种方式获取第二ECS的信息：
方式1：
可选地，第一ECS根据配置信息获取该第二ECS的信息。
在一种实现方式中，第一ECS配置了其他ECS的配置文件(profile)，当第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务时，或者，第一ECS尝试从第二ECS获取第二ECS管理的EES信息，从而确定最优的EES为终端设备提供边缘服务时，可根据本地配置的其他ECS的配置文件获取第二ECS的信息，第二ECS管理的EES能为终端设备提供边缘服务。
可选地，ECS的配置文件包括ECS的地址或端点信息，ECS的服务范围，ECS管理的EES配置文件，ECS的ECSP标识，ECS对应的PLMN标识中的一项或多项，后文提及的ECS的配置文件具体包括的内容同上，在后文描述中不再赘述。其中，ECS的服务范围可以具体的由一个或多个服务区域组成，也可以是ECS管理的各EES的服务范围组成的集合。第一ECS根据第三请求信息，和/或第一ECS保存/配置的ECS的配置文件确定第二ECS。
示例地，第三请求信息中的终端设备的位置信息对应的位置，处于第二ECS的服务范围内或处于第二ECS管理的EES的服务范围内，则第一ECS获取该第二ECS的信息；或
第三请求信息中的ECSP标识与第二ECS的ECSP标识相同，则第一ECS获取该第二ECS的信息；或
第三请求信息中的PLMN标识与第二ECS的PLMN标识相同，则第一ECS获取该第二ECS的信息；或
第三请求信息中的EES的特征信息与第二ECS管理的EES相匹配，则第一ECS获取该第二ECS的信息。
方式2：
联邦控制网元上保存或配置了ECS配置文件。
可选地，该方法100还包括：
步骤S102，第一ECS向联邦控制网元发送第一请求信息，该第一请求信息用于请求第二ECS的信息。对应的，联邦控制网元接收该第一请求信息。其中，联邦控制网元，支持发现ECS的功能，本申请对该网元的名字不做限定，该网元也可以称为联邦管理网元，或ECS发现网元等。联邦控制网元可以是单独的网元，也可以集成在其它网元中，例如可以集成在NRF、UDM中，本申请不做限定。
以及步骤S103，联邦控制网元向第一ECS发送第一响应信息，该第一响应信息包括第二ECS的信息。对应的第一ECS接收该第一响应信息。
具体地，第一ECS根据第三请求信息确定该第一ECS管理的EES不能为终端设备提供边缘服务时，或者，第一ECS尝试从第二ECS获取第二ECS管理的EES信息，从而确定最优的EES为终端设备提供边缘服务时，向联邦控制网元发送第一请求信息，从而获取第二ECS的信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
应理解，ECS可将配置文件注册至或发送到联邦控制网元，因此，第一ECS确定第一ECS管理的EES不能为终端设备提供边缘服务时，或者，第一ECS尝试从第二ECS获取第二ECS管理的EES信息，从而确定最优的EES为终端设备提供边缘服务时，可向联邦控制网元查询能为终端设备提供边缘服务的ECS，或者查询能为终端设备提供边缘服务的EES对应的/注册的ECS。其中，联邦控制网元查询/确定第二ECS信息的方法包括但不限于：
第一请求信息中的终端设备的位置信息对应的位置，处于第二ECS的服务范围内或处于第二ECS管理的EES的服务范围内，则联邦控制网元确定该第二ECS为能为终端设备提供边缘服务的ECS；或
第一请求信息中的ECSP标识与第二ECS的ECSP标识相同，则联邦控制网元确定该第二ECS为能为终端设备提供边缘服务的ECS；或
第一请求信息中的PLMN标识与第二ECS的PLMN标识相同，则联邦控制网元确定该第二ECS为能为终端设备提供边缘服务的ECS；或
第一请求信息中的EES的特征信息与第二ECS管理的EES相匹配，则联邦控制网元确定该第二ECS为能为终端设备提供边缘服务的ECS。
联邦控制网元确定第二ECS后，将第二ECS的信息发送给第一ECS。
可选的，第一ECS上保存或预配置了本地策略信息。其中，本地策略信息包括：第一ECS可以从第二ECS获取第二ECS管理的EES信息(可参考步骤S110中的情况3)，从而确定最优的EES为终端设备提供边缘服务。示例地，第一ECS通过终端设备的签约数据(例如终端设备既签约了第一ECS，又签约了第二ECS)确定终端设备可以接入第二 ECS，第一ECS尝试从第二ECS获取第二ECS管理的EES信息。
具体地，第一ECS先根据本地策略信息确定需要查找一个第二ECS，再通过上述方式1或方式2确定第二ECS。
可选地，在第一ECS获取第二ECS的信息后，该方法100还包括：
步骤S104，第一ECS向第二ECS发送第二请求信息，该第二请求信息用于请求第一EES的信息。对应的，第二ECS接收该第二请求信息。
步骤S105，第二ECS向第一ECS发送第二响应信息，该第二响应信息包括第一EES的信息。对应的第一ECS接收该第二响应信息。
可选地，该第二请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
可选的，第二ECS根据第二请求信息和/或ECS保存的EES配置文件确定第一EES，包括以下至少一项：
第二ECS根据终端设备接入的PLMN标识和EES配置文件的PLMN标识确定第一EES；
第二ECS根据第二请求中ECSP标识和EES配置文件的ECSP信息确定第一EES；
第二ECS根据终端设备的位置信息和EES配置文件的服务范围信息确定第一EES，其中，终端设备的位置信息可以包含于第二请求信息中，也可以由第二ECS向5GC获取。
步骤S120，第一ECS向第一设备发送第一信息，该第一信息包括第一EES的信息或该第二ECS的信息，第一EES为第二ECS管理的EES。对应的，第一设备接收该第一信息。
应理解，第一设备可以是UE，EEC，也可以是EES，本申请对此不作任何限制。当第一ECS向第一设备发送的第一信息为第一EES的信息时，第一设备可直接确定第一EES，当第一ECS向第一设备发送的第一信息为第二ECS的信息时，第一设备可向第二ECS发送第五请求信息，从而通过来自第二ECS的第五响应信息获取第一EES的信息。其中，第五请求信息与第三请求信息的具体内容和作用类似，在此不再赘述。EEC接收第一EES的信息后，EEC可向第一EES发送EAS discovery请求用于获取EAS的地址信息，进而访问边缘服务。
还应理解，上文描述的ECS的信息可以是ECS的统一资源标识符(uniform resource identifier，URI)、网际互连协议(internet protocol，IP)地址，还可以是全限定域名(fully qualified domain name，FQDN)，本申请对此不做限定。UE基于ECS的信息可以与ECS建立连接。EES的信息也可以是EES的URI、IP地址或FQDN等信息，本申请对此也不做限定。后文提及的ECS的信息，和EES的信息具体包括的内容同上，在后文描述中不再赘述。
下面将上述方法100用于具体的场景以介绍获取边缘服务的方法。
图4是本申请提供的联邦场景下的获取边缘服务的方法的交互流程图。图4示出的方法200的应用场景为联邦(Federation)场景，即由多个ECSP和/或多个PLMN组成联邦。当终端设备处于漫游场景，例如归属路由(home-routed)，或本地分流(local breakout)，可通过方法200获取边缘服务，当终端设备处于非漫游场景也可通过方法200获取边缘服务。该方法200包括：
步骤S210，一个或多个ECS(图4中以ECS1和ECS2示例)将ECS配置文件注册到联邦控制网元(federation controller，FC)，其中，FC是逻辑网元，可能集成在现有功能网元中，例如FC集成在NRF，ECS，UDR或UDM中。FC也可以是其它名字，例如联邦管理网元(federation manager，FM)或边缘计算联邦管理网元(MEC federation manager，MEFM)等，本申请对此不做任何限定。
或者，每个ECS都配置其它ECS的配置文件，例如ECS1配置ECS2的配置文件，ECS2配置ECS1的配置文件。其中，ECS1和ECS2可以属于相同的PLMN，也可以属于不同的PLMN，或者ECS1和ECS2的ECSP标识可以相同，ECS1和ECS2的ECSP标识也可以不同。
步骤S220，EEC或UE(对应方法100中的第一设备)向ECS1(对应方法100中的第一ECS)发送第三请求消息，例如，该第三请求消息可以为服务提供(service provisioning)请求，第三请求信息用于请求第一EES的信息。第三请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用的信息。
应理解，EEC可以配置ECS1的地址信息，因此EEC向ECS1发送第三请求消息之前，可从本地获ECS1的地址信息。或者，EEC还可通过其他方式获取ECS1的地址信息，例如由5GC网络下发给UE/EEC。
步骤S230，ECS1接收第三请求消息之后，确定ECS1管理的EES不能为终端设备提供边缘服务。或者说，确定ECS1不能为终端设备提供边缘服务。或者，ECS1尝试从第二ECS获取第二ECS管理的EES信息，从而(可以与ECS1管理的EES比较)确定最优的EES为终端设备提供边缘服务。示例地，ECS1接收第三请求消息之后，没有查找到合适的EES，或没有查找到EDN部署了终端设备想访问的应用。其中，没有查找到合适的EES，包括：UE请求的EAS没有注册到EES上，或者UE请求的EAS虽然注册到EES上了但过载了。
可选的，ECS1记录该第三请求消息，用于后续ECS1收到EEC的再一次请求时触发查找其它ECS。
可选的，方法200还包括：
步骤S240，若ECS1没有查找到合适的EES，ECS1向EEC/UE发送第三响应信息，表示ECS1没有查找到合适的EES，或EDN。
在一种实现方式中，第三响应信息包括指示信息，指示ECS1不能为终端设备提供边缘服务或者指示ECS1管理的EES不能为终端设备提供边缘服务。
步骤S250，EEC/UE收到第三响应信息后，向ECS1发送第四请求信息。
示例地，第四请求信息与第三请求信息相同，ECS1收到第四请求信息时，根据之前记录的第三请求信息，确定需要查找其它ECS。
或者，第四请求信息与第三请求信息不相同，第四请求信息中包括指示信息，指示ECS1查找其它ECS，ECS1可根据指示信息查找其它ECS。
在一种实现方式中，第四请求信息为ECS发现(discovery)请求，第四请求信息包括ECSP标识、EES或EAS的特征信息，PLMN标识，以及终端设备的位置信息，应用信息中的至少一项，该第四请求信息用于查找ECS。其中ECSP标识可以是PLMN标识 和/或第三方服务商名称。其中，EAS会将EAS配置文件(profile)注册到EES上，EAS profile可以包括以下至少一项：EAS标识、EAS端点信息(endpoint)、ECSP信息、EAS服务范围、EAS所关联的DNAI。EES或EAS的特征信息可以是EES/EAS profile中的一项或多项。
应理解，步骤S240，S250都是可选的，即当步骤S230中ECS1没有查找到合适的EES时，可直接获取ECS2的信息。
ECS1可通过以下至少一种方式获取ECS2(对应方法100中的第二ECS)的信息：
方式1：
ECS1和ECS2将配置文件注册至联邦控制网元，ECS1确定ECS1管理的EES不能为终端设备提供边缘服务时，可向联邦控制网元查询能为终端设备提供边缘服务的EES，从而确定该EES对应的ECS，例如ECS2(ECS2管理的EES2能满足EEC的请求)。
示例地，ECS1通过步骤S251和S252确定ECS2的信息。
步骤S251：ECS1向联邦控制网元发送第一请求信息，该第一请求信息用于请求ECS2的信息。对应的，联邦控制网元接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
以及步骤S252，联邦控制网元向ECS1发送第一响应信息，该第一响应信息包括ECS2的信息。对应的ECS1接收该第一响应信息。
方式2：
ECS1配置了ECS2的配置文件，当ECS1确定ECS1管理的EES不能为终端设备提供边缘服务时，可根据本地配置的ECS2的配置文件获取ECS2的信息，ECS2管理的EES2能为终端设备提供边缘服务。
示例地，ECS1通过步骤S253和S254确定EES2的信息。
步骤S253，ECS1向ECS2发送第二请求信息，该第二请求信息用于请求EES2(对应方法100中的第一EES)的信息。对应的，ECS2接收该第二请求信息。
步骤S254，ECS2向ECS1发送第二响应信息，该第二响应信息包括EES2的信息。对应的ECS1接收该第二响应信息。
可选地，该第二请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S260，ECS1可根据第一响应信息或第二响应信息确定目标EES(例如EES2)的信息。
步骤S270，ECS1将ECS2的信息发送至EEC，对应地，EEC接收该ECS2的信息，后续EEC可向ECS2发送service provisioning request获取EES2的信息，从而获取边缘服务。
或者作为步骤S270的可替代步骤：
步骤S280，EES2将其配置文件注册至ECS1。
以及步骤S281，ECS1向EEC发送EES2的信息，对应地，EEC接收该EES2的信息。
应理解，步骤S270中的ECS2的信息，或步骤S281中的EES2的信息即为方法100中步骤S120中的第一信息。
UE/EEC接收EES2的信息后，EEC可再向EES2发送EAS discovery请求用于获取EAS的地址信息，进而访问边缘服务。
图5是本申请提供的另一种联邦场景下的获取边缘服务的方法的交互流程图。图5示出的方法300的应用场景为联邦场景，即由多个ECSP和/或多个PLMN组成联邦。当终端设备处于漫游场景，例如归属路由，或本地分流，可通过方法300获取边缘服务，当终端设备处于非漫游场景也可通过方法300获取边缘服务。方法300包括：
步骤S310，一个或多个ECS(图5中以ECS1和ECS2示例)将ECS配置文件注册到联邦控制网元。
或者，每个ECS都配置其它ECS的配置文件，例如ECS1配置ECS2的配置文件，ECS2配置ECS1的配置文件。其中，ECS1和ECS2可以属于相同的PLMN，也可以属于不同的PLMN，或者ECS1和ECS2的ECSP标识可以相同，ECS1和ECS2的ECSP标识也可以不同。
步骤S320，源EES(EES1，对应方法100中的第一设备)无法查找到合适的EAS和或EES来服务终端设备。
例如，EES接收来着EEC的EAS发现请求(EEC与EES之间已建立连接)，EES发现找不到合适的EAS，或者，EES检测到终端设备移动，需要切换EAS时，发现找不到合适的EAS。
步骤S330，源EES向ECS1(对应方法100中的第一ECS)发送第三请求消息(源EES注册至ECS1)，例如，该第三请求消息可以为服务提供(service provisioning)请求或EES discovery请求，第三请求信息用于请求第一EES的信息。第三请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用的信息。
步骤S340，ECS1确定ECS1管理的EES不能为终端设备提供边缘服务。或者，确定ECS1不能为终端设备提供边缘服务。或者，ECS1尝试从第二ECS获取第二ECS管理的EES信息，从而(可以与ECS1管理的EES比较)确定最优的EES为终端设备提供边缘服务。
示例地，源EES无法查找到合适的EAS和或EES来服务终端设备，例如，EES接收来自EEC的EAS发现请求，EES发现找不到合适的EAS，或者，EES检测到终端设备移动，需要切换EAS时，发现找不到合适的EAS。源EES向ECS1发送EES discovery请求，用于请求第一EES的信息，ECS1查找不大合适的EES为终端设备提供边缘服务。
ECS1可通过以下至少一种方式获取ECS2(对应方法100中的第二ECS)的信息：
方式1：
ECS1和ECS2将配置文件注册至联邦控制网元，ECS1确定ECS1管理的EES不能为终端设备提供边缘服务时，可向联邦控制网元查询能为终端设备提供边缘服务的ECS/EES，例如ECS2(ECS2管理的EES2能满足EEC的请求)。
示例地，ECS1通过步骤S341和S342确定ECS2的信息。
步骤S341：ECS1向联邦控制网元发送第一请求信息，该第一请求信息用于请求ECS2的信息。对应的，联邦控制网元接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信 息，应用信息。
以及步骤S342，联邦控制网元向ECS1发送第一响应信息，该第一响应信息包括ECS2的信息。对应的ECS1接收该第一响应信息。
方式2：
ECS1配置了ECS2的配置文件，当ECS1确定ECS1管理的EES不能为终端设备提供边缘服务时，可根据本地配置的ECS2的配置文件获取ECS2的信息，ECS2管理的EES2能为终端设备提供边缘服务。
步骤S350，ECS1可根据第一响应信息或第二响应信息确定目标EES(例如EES2)的信息。
示例地，ECS1通过步骤S343和S344确定EES2的信息。
步骤S343，ECS1向ECS2发送第二请求信息，该第二请求信息用于请求EES2(对应方法100中的第一EES)的信息。对应的，ECS2接收该第二请求信息。
步骤S344，ECS2向ECS1发送第二响应信息，该第二响应信息包括EES2的信息。对应的ECS1接收该第二响应信息。
可选地，该第二请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S360，ECS1将第一信息(EES2的信息)发送至源EES，对应地，源EES接收该第一信息。
步骤S370，可选的，终端设备向EES发送应用发现请求，用于请求EES2管理的EAS(目标EAS)。终端设备之前访问的EAS(源EAS)可以与目标EAS进行上下文迁移，或者EES1和EES2之间进行上下文同步/上下文迁移，从而使得终端设备可通过EES2获取边缘服务，或保障业务连续性。
图6是本申请提供的另一种获取边缘服务的方法的交互流程图。图6示出的方法400包括：
步骤S410，终端设备向第一功能网元发送第一请求信息，该第一请求信息用于请求第一ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息。对应的，第一功能网元接收该第一请求信息。
其中，ECS发现代理(ECS discovery proxy)，支持发现ECS的功能，名字不做限定，或ECS发现网元(ECS discovery function)等。ECS发现代理可以是单独的网元，也可以集成在其它网元中，例如ECS发现代理集成在NRF、UDM或ECS中，本申请不做限定。
在一种实现方式中，每一个PLMN分别部署一个ECS发现代理，用于做拓扑隐藏。
可选地，第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
可选地，该方法400还包括：
步骤S411，核心网网元向终端设备发送第一功能网元的地址信息，对应的，终端设备接收该第一功能网元的地址信息。
可选地，将第一功能网元的地址信息配置在终端设备，或者配置在EEC，或者配置在核心网网元。若将第一功能网元的地址信息配置在核心网网元(例如UDM)，可由核心网网元将其下发至终端设备。
步骤S420，第一功能网元接收到第一请求信息后，根据该第一请求信息确定第一ECS的信息。
可选地，第一功能网元为第一ECS发现代理，第一ECS发现代理从第二ECS发现代理获取第一ECS的信息。
第一ECS发现代理可通过以下方式获取第二ECS发现代理的信息：
方式1：
第一ECS发现代理配置或保存了第二ECS发现代理的相关信息(地址信息，服务范围、管理的EES信息、ECSP标识、PLMN标识等信息中的一个或多个)，第一ECS发现代理根据该第一请求信息和/或本地配置确定第二ECS发现代理的信息。
示例地，第一请求信息中的PLMN标识与本地配置的第二ECS发现代理的PLMN标识相同，则第一ECS发现代理获取该第二ECS发现代理的信息，和/或
第一请求信息中的ECSP标识与第二ECS发现代理的ECSP标识相同，则第一ECS发现代理确定该第二ECS发现代理并获取对应的地址信息；和/或
第一请求信息中的PLMN标识与第二ECS发现代理的PLMN标识相同，则第一ECS发现代理确定该第二ECS发现代理并获取对应的地址信息；和/或
第一请求信息中的EES的特征信息与第二ECS发现代理管理的EES相匹配，则第一ECS发现代理确定该第二ECS发现代理并获取对应的地址信息。
方式2：
第二ECS发现代理将其配置信息(地址信息，服务范围、管理的EES信息、ECSP标识、PLMN标识等信息中的一个或多个)注册至联邦控制网元。对应的，联邦控制网元保存ECS配置信息。
第一ECS发现代理根据第一请求信息，向联邦控制网元发送第三请求信息，该第三请求信息用于请求第二ECS发现代理的信息，第一ECS发现代理接收来自联邦控制网元的第三响应信息，该第三响应信息包括第二ECS发现代理的信息。该第三请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
在方式2中，联邦控制网元确定第二ECS发现代理的方法同方式1第一ECS发现代理根据该第一请求信息和/或本地配置确定第二ECS发现代理的信息的方法类似，差异在于方式1中执行主体为第一ECS发现代理，方式2中执行主体为联邦控制网元，此处不再赘述。
可选地，在第一ECS发现代理获取第二ECS发现代理的信息后，该方法400还包括：
步骤S412，第一ECS发现代理向第二ECS发现代理发送第二请求信息，该第二请求信息用于请求第一ECS的信息。对应的，第二ECS发现代理接收该第二请求信息。
可选地，该第二请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S413，第二ECS发现代理向第一ECS发现代理发送第二响应信息，该第二响应信息包括第一ECS的信息。对应的，第一ECS发现代理接收该第二响应信息。
其中，第二ECS发现代理根据第二请求信息和第二ECS发现代理保存/配置的ECS配置信息确定第一ECS的方法，同步骤S101中第一ECS确定第二ECS的方法类似，差 异在于步骤S101中执行主体为第一ECS，此处执行主体为第二ECS发现代理，此处不再赘述。
步骤S430，第一功能网元向终端设备发送第一响应信息，该第一响应信息包括第一ECS的信息。对应的，终端设备接收该第一响应信息，通过第一ECS获取边缘服务。
终端设备(UE/EEC)接收目标ECS后，EEC可向目标ECS(第一ECS)发送service provisioning请求获取EES；EEC再向EES发送EAS discovery请求用于获取EAS地址信息，进而访问边缘服务。
下面将上述方法400用于具体的场景以介绍获取边缘服务的方法。
图7是本申请提供的联邦场景下的一种获取边缘服务的方法的交互流程图。图7示出的方法500的应用场景为联邦场景。当终端设备处于漫游场景或非漫游场景都可通过方法500获取边缘服务。该方法500包括：
步骤S510，一个或多个ECS(图7中以ECS1，ECS2和ECS3示例)将ECS配置文件注册到联邦控制网元FC，其中，FC是逻辑网元，可能集成在现有功能网元中，例如FC集成在NRF，UDR或UDM中。
或者，每个ECS都配置一个或多个其它ECS的配置文件，例如ECS1配置ECS2和ECS3的配置文件，ECS2配置ECS1和ECS3的配置文件，ECS3配置ECS1和ECS2的配置文件。其中，ECS1，ECS2和ECS3可以属于相同的PLMN，也可以属于不同的PLMN，或者ECS1，ECS2和ECS3的ECSP标识可以相同，ECS1，ECS2和ECS3的ECSP标识也可以不同。
具体地，若只考虑一个PLMN非漫游场景，不需要配置PLMN标识。若一个PLMN只有一个ECS，可以不配置ECS的服务范围。若ECSP是运营商，那么ECSP标识可以为PLMN标识，本申请对此不作任何限制。
步骤S520，UE/EEC配置联邦控制网元的地址信息。或
步骤S520’，核心网网元(以UDM示例)配置联邦控制网元的地址信息。
步骤S521，核心网网元向UE/EEC发送联邦控制网元的地址信息，对应地，UE/EEC接收该联邦控制网元的地址信息。
步骤S530，UE/EEC向联邦控制网元发送第一请求信息，该第一请求信息用于请求目标ECS(能为终端设备提供边缘服务的ECS)的信息。对应的，联邦控制网元接收该第一请求信息。
可选地，第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S540，联邦控制网元确定目标ECS的信息。
示例地，联邦控制网元根据本地配置的ECS配置文件和第一请求信息确定目标ECS。
在一种实现方式中，联邦控制网元根据本地配置的ECS的PLMN标识，与第一请求信息中终端设备接入的PLMN标识确定目标ECS；
在另一种实现方式中，若同一个PLMN下有多个ECS，联邦控制网元从5G核心网获取终端设备的位置信息，根据第一请求信息中终端设备的位置信息以及本地配置的ECS的服务范围来确定目标ECS；
在另一种实现方式中，联邦控制网元根据本地ECS的ECSP标识以及第一请求信息中 的ECSP标识来确定目标ECS。
步骤S550，联邦控制网元向UE/EEC发送第一响应信息，该第一响应信息包括目标ECS的信息，对应地，UE/EEC接收该第一响应信息。
UE/EEC接收目标ECS后，EEC可向目标ECS发送service provisioning请求获取EES，EEC再向EES发送EAS discovery请求用于获取EAS地址信息，进而访问边缘服务。
图8是本申请提供的联邦场景下的另一种获取边缘服务的方法的交互流程图。图8示出的方法600的应用场景为联邦场景。为了做网络和拓扑隐藏，每个运营商都部署一个ECS发现代理(discovery proxy)，当终端设备处于漫游场景或非漫游场景都可通过方法600获取边缘服务。该方法600包括：
步骤S610，一个或多个ECS将ECS配置文件注册到ECS发现代理(图8中ECS1和ECS3注册至第一ECS发现代理，ECS2和ECS4注册至第二ECS发现代理)，其中，ECS发现代理可以是逻辑网元，可能集成在现有功能网元中，例如ECS发现代理集成在NRF，UDR或UDM中。
步骤S620，一个或多个ECS发现代理将其相关信息(地址信息，服务范围、管理的EES信息、ECSP标识、PLMN标识等信息中的一个或多个)注册至联邦控制网元(图8中第一ECS发现代理和第二ECS发现代理注册至联邦控制网元)，联邦控制网元可以不属于第一ECS发现代理和第二ECS发现代理所属的任一运营商。
或者，第一ECS发现代理配置第二ECS发现代理的相关信息，第二ECS发现代理配置第一ECS发现代理的相关信息。
示例地，第一ECS发现代理属于第一网络，例如第一网络为归属域网络，第二ECS发现代理属于第二网络，例如第二网络为拜访域网络。
步骤S630，UE/EEC配置第一ECS发现代理的地址信息。或
步骤S630’，核心网网元(以UDM示例)配置或获取第一ECS发现代理的地址信息。
步骤S640，核心网网元向UE/EEC发送联邦控制网元，或第一ECS发现代理的地址信息，对应地，UE/EEC接收该联邦控制网元或第一ECS发现代理的地址信息。
应理解，UE/EEC可从本地配置获取第一ECS发现代理的地址信息，或者，UE/EEC可从核心网网元获取第一ECS发现代理的地址信息，或者，UE/EEC可从核心网网元获取联邦控制网元的地址信息，再从联邦控制网元获取第一ECS发现代理的地址信息。
步骤S650，UE/EEC向第一ECS发现代理发送第一请求信息，该第一请求信息用于请求目标ECS(能为终端设备提供边缘服务的ECS)的信息。对应的，第一ECS发现代理接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S660：第一ECS发现代理确定目标ECS发现代理的信息。
若第一ECS发现代理根据第一请求信息确定第一ECS发现代理上注册的ECS有能为终端提供边缘服务的ECS，则第一ECS发现代理即为目标ECS发现代理。
步骤S664，第一ECS发现代理将确定的目标ECS的信息发送给UE/EEC，对应地，UE/EEC接收到目标ECS的信息后，获取边缘服务。
若第一ECS发现代理根据第一请求信息确定第一ECS发现代理上注册的ECS没有能为终端提供边缘服务的ECS，则第一ECS发现代理确定目标ECS发现代理为第二ECS发 现代理。第一ECS发现代理确定目标ECS发现代理的方法参考步骤S420方式1，此处不再赘述。
步骤S661，第一ECS发现代理向第二ECS发现代理发送第二请求信息，该第二请求信息用于请求第一ECS的信息。对应的，第二ECS发现代理接收该第二请求信息。
可选地，该第二请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S662，第二ECS发现代理根据第一请求信息确定第二ECS发现代理上注册的ECS能为终端提供边缘服务的目标ECS。
第二ECS发现代理确定目标ECS的方法参考方法100中第一ECS获取目标ECS(第二ECS)的信息的方法，差异在于方法100中执行主体为第一ECS，此处执行主体为第二ECS发现代理，此处不再赘述。
步骤S663，第二ECS发现代理向第一ECS发现代理发送第二响应信息，该第二响应信息包括第一ECS的信息。对应的，第一ECS发现代理接收该第二响应信息。
步骤S664，第一ECS发现代理向UE/EEC发送第一响应信息，该第一响应信息包括第一ECS的信息。对应的，UE/EEC接收该第一响应信息，通过目标ECS获取边缘服务。
图9是本申请提供的一种获取边缘服务的方法的交互流程图。图9示出的方法700包括：
步骤S710，第二网络的第二控制面核心网网元向第一控制面核心网网元发送第一指示信息，该第一指示信息指示终端设备支持接入第一网络的边缘服务。对应的，第一网络的第一控制面核心网网元接收该第一指示信息。
示例地，第一网络为拜访域的网络，第二网络为归属域的网络。
步骤S720，第一控制面核心网网元根据第一指示信息向第一网络的第三控制面核心网网元发送第一请求信息，该第一请求信息用于请求第一网络的第一边缘配置服务器ECS的信息。对应的，第一网络的第三控制面核心网网元接收该第一请求信息。
可选地，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，EES或EAS的特征信息，终端设备的位置信息，应用信息。
步骤S730，第一网络的第三控制面核心网网元根据第一请求信息确定第一ECS的信息。
第三控制面核心网网元保存或配置了ECS配置文件。可选地，第三控制面核心网网元根据PLMN标识，以及PLMN标识与ECS的对应关系确定该第一ECS的信息；和/或
第三控制面核心网网元根据ECSP标识，以及该ECSP标识与ECS的对应关系确定第一ECS的信息；和/或
第三控制面核心网网元根据终端设备的位置信息以及ECS的服务范围确定第一ECS的信息；和/或
第三控制面核心网网元根据应用信息确定第一ECS的信息。
步骤S740，第一控制面核心网网元接收来自第三控制面核心网网元的第一响应信息，该第一响应信息包括第一ECS的信息。
下面将上述方法700用于具体的场景以介绍获取边缘服务的方法。
图10是本申请提供的归属路由的漫游接入场景下的获取边缘服务的方法的交互流程图。
在图10示出的方法800中，UDM存储UE的签约数据(该签约数据是UE粒度的)，该签约数据包括UE支持访问哪些拜访域网络(例如V-PLMN)的边缘服务。
可选的，该签约数据还包括拜访域网络的对应的ECS的信息。
在一种实现方式中，对于单一运营商只部署一个ECS或少量ECS的场景，UDM预配置的UE的签约数据不是UE粒度的签约数据，是归属域网络粒度的签约数据，即对于同一个归属域的任何UE，都签约相同的ECS。
示例地，UDM预配置了ECS的信息，即归属域网络下的每个UE都可通过该ECS获取边缘服务。
在另一种实现方式中，适用于一个运营商部署/管理多个ECS的场景。ECS将服务范围、地址信息、ECSP标识等注册到NRF。ECS可以由运营商或第三方部署，若ECS由运营商自身部署，ECSP标识可以是PLMN标识。若ECS由第三方部署，ECSP标识可以是第三方服务商名称或者是PLMN标识以及第三方服务商名称。
方法800包括：
步骤S810，UE/EEC向拜访域的SMF(以V-SMF示例)发送第一请求信息，该第一请求信息用于请求目标ECS(能为终端设备提供边缘服务的ECS)的信息。对应的，V-SMF接收该第一请求信息。
可选地，第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
示例地，可参照现有SA2标准，UE向V-SMF发送会话建立请求，该会话建立请求包括第一请求信息，可选地，该会话建立请求还携带指示信息，该指示信息指示EEC支持接收ECS的信息)。
步骤S811，V-SMF向归属域的SMF(以H-SMF示例)发送会话上下文建立请求。可选的，会话上下文建立请求中包括拜访域PLMN(以V-PLMN示例)的标识，或者H-SMF可根据V-SMF的标识或其它信息确定拜访域PLMN的标识。
步骤S820，H-SMF从H-UDM获取UE的签约数据，确定UE支持接入第一网络(UE目前接入的拜访域网络，以V-PLMN示例)的边缘服务。
可选的，H-SMF从H-UDM获取的签约信息中还包含V-PLMN对应的拜访域的ECS(以V-ECS示例)的信息。则H-SMF将该拜访域的ECS的信息发送至V-SMF。
如果H-SMF从H-UDM获取的签约信息中不包含V-PLMN对应的V-ECS的信息，则H-SMF可从H-NRF查询/获取V-ECS的信息，从而向V-SMF转发V-ECS的信息。
具体地，包括步骤S860，H-SMF向H-NRF发送第一请求信息，该第一请求信息用于请求V-ECS的信息。对应的，H-NRF接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
若H-NRF上没有V-ECS的地址信息，则H-NRF向V-NRF获取V-ECS的信息。
具体地，包括步骤S861，H-NRF向V-NRF转发该第一请求信息。
步骤S862，V-NRF向H-NRF发送第一响应信息，该第一响应信息包括V-ECS的信 息，对应地，H-NRF接收该第一响应信息。
步骤S863，H-NRF向V-SMF转发该第一响应信息。
或者步骤S820之后执行
步骤S830，H-SMF向V-SMF发送第一指示信息，该第一指示信息指示UE支持接入第一网络的边缘服务。对应的，V-SMF接收该第一指示信息。
可选地，该第一指示信息还用于指示V-SMF确定V-ECS，该指示信息具体可以为支持接入V-PLMN边缘服务的签约信息，或者该指示信息可以是显示的指示信息。
或者上述步骤S830可替换为，H-SMF向V-SMF发送第一指示信息，该第一指示信息指示V-SMF确定V-ECS。
若H-SMF从H-UDM获取的签约信息中不包含第一网络对应的V-ECS的信息，则V-SMF可通过以下方式确定该V-ECS的信息。
方式1：
步骤S840，V-SMF向V-NRF发送第一请求信息，该第一请求信息用于请求V-ECS的信息。对应的，V-NRF接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S841：V-NRF向V-SMF发送第一响应信息，该第一响应信息包括V-ECS的信息，对应地，V-SMF接收该第一响应信息。
V-NRF确定V-ECS可通过以下实施方式实现：
在一种实现方式中，V-NRF根据第一请求信息中的PLMN标识，与本地的V-PLMN标识确定V-ECS；
在另一种实现方式中，若同一个PLMN下有多个ECS，V-NRF根据第一请求信息中的UE的位置信息，以及本地的ECS的服务范围来确定V-ECS。
在另一种实现方式中，V-NRF根据第一请求信息中ECSP标识以及本地的ECSP标识来确定V-ECS。
方式2：
V-SMF向V-UDM查询V-ECS，V-UDM存储了V-PLMN的V-ECS信息，该V-ECS信息不是UE粒度的签约数据，该V-ECS信息适用于归属域网络下的每个UE。
步骤S850，V-SMF向V-UDM发送第一请求信息，该第一请求信息用于请求V-ECS的信息。对应的，V-UDM接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S851：V-NRF向V-UDM发送第一响应信息，该第一响应信息包括V-ECS的信息，对应地，V-SMF接收该第一响应信息。
V-SMF确定该V-ECS的信息后执行
步骤S870，V-SMF向UE/EEC转发第一响应信息(可以是步骤S841，S851，或S863中的任一第一响应信息)，该第一响应信息包括V-ECS的信息，对应地，UE/EEC接收该第一响应信息，从而进一步获取边缘服务。
应理解，V-UDM根据请求信息确定V-ECS的方式同V-NRF确定V-ECS的方式，在 此不再赘述。
图11是本申请提供的本地分流的漫游接入场景下的获取边缘服务的方法的交互流程图。
在图11示出的方法900中，同方法800，UDM存储UE的签约数据(该签约数据是UE粒度的)，该签约数据包括UE支持访问哪些拜访域网络(例如V-PLMN)的边缘服务。
可选的，该签约数据还包括拜访域网络的对应的ECS的信息。
在一种实现方式中，对于单一运营商只部署一个ECS或少量ECS的场景，UDM预配置的UE的签约数据不是UE粒度的签约数据，是归属域网络粒度的签约数据。
示例地，UDM预配置了ECS的信息，即归属域网络下的每个UE都可通过该ECS获取边缘服务。
在另一种实现方式中，适用于一个运营商部署/管理多个ECS的场景。ECS将服务范围、地址信息、ECSP标识等注册到NRF。ECS可以由运营商或第三方部署，若ECS由运营商自身部署，ECSP标识可以是PLMN标识。若ECS由第三方部署，ECSP标识可以是第三方服务商名称或者是PLMN标识以及第三方服务商名称。
方法900包括：
步骤S910，UE/EEC向拜访域的SMF(以V-SMF示例)发送第一请求信息，该第一请求信息用于请求目标ECS(能为终端设备提供边缘服务的ECS，以V-ECS)的信息。对应的，V-SMF接收该第一请求信息。
可选地，第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S920，H-UDM根据UE的签约数据，确定UE支持接入第一网络(UE目前接入的拜访域网络，以V-PLMN示例)的边缘服务。
步骤S930，H-UDM向V-SMF发送第一指示信息，该第一指示信息指示UE支持接入V-PLMN的边缘服务。对应的，V-SMF接收该第一指示信息。
可选地，该第一指示信息还用于指示V-SMF确定V-ECS，该指示信息具体可以为支持接入V-PLMN边缘服务的签约信息，或者该指示信息可以是显示的指示信息。
或者上述步骤S930可替换为，H-UDM向V-SMF发送第一指示信息，该第一指示信息指示V-SMF确定V-ECS。
V-SMF可通过以下方式确定该V-ECS的信息。
方式1：
步骤S940，V-SMF向V-NRF发送第一请求信息，该第一请求信息用于请求V-ECS的地址信息。对应的，V-NRF接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S941：V-NRF向V-SMF发送第一响应信息，该第一响应信息包括V-ECS的信息，对应地，V-SMF接收该第一响应信息。
V-NRF确定V-ECS可通过以下实施方式实现：
在一种实现方式中，V-NRF根据第一请求信息中的PLMN标识，与本地的V-PLMN 标识确定V-ECS；
在另一种实现方式中，若同一个PLMN下有多个ECS，V-NRF根据第一请求信息中的UE的位置信息，以及本地的ECS的服务范围来确定V-ECS。
在另一种实现方式中，V-NRF根据第一请求信息中ECSP标识以及本地的ECSP标识来确定V-ECS。
方式2：
V-SMF向V-UDM查询V-ECS，V-UDM存储了V-PLMN的V-ECS信息，该V-ECS信息不是UE粒度的签约数据，该V-ECS信息适用于归属域网络下的每个UE。
步骤S950，V-SMF向V-UDM发送第一请求信息，该第一请求信息用于请求V-ECS的信息。对应的，V-UDM接收该第一请求信息。第一请求信息包括以下至少一项：终端设备接入的PLMN标识，ECSP标识，终端设备的位置信息，EES或EAS的特征信息，应用信息。
步骤S951：V-NRF向V-UDM发送第一响应信息，该第一响应信息包括V-ECS的信息，对应地，V-SMF接收该第一响应信息。
V-SMF确定该V-ECS的信息后执行
步骤S960，V-SMF向UE/EEC转发第一响应信息(可以是步骤S941，或S951中的第一响应信息)，该第一响应信息包括V-ECS的信息，对应地，UE/EEC接收该第一响应信息，从而进一步获取边缘服务。
应理解，V-UDM确定V-ECS的方式同V-NRF确定V-ECS的方式，在此不再赘述。
应理解，上述流程图中所示的虚线步骤为可选地步骤，并且各步骤的先后顺序依照方法的内在逻辑确定，图中所示的序号仅为示例，不对本申请步骤的先后顺序造成限制。
还应理解，本申请实施例提供的方法可以单独使用，也可以结合使用，本申请对此不做任何限制。
需注意的是，图3-图11中示意的执行主体仅为示例，该执行主体也可以是支持该执行主体实现图3-图11所示方法的芯片、芯片系统、或处理器，本申请对此不作限制。
上文结合附图描述了本申请实施例的方法实施例，下面描述本申请实施例的装置实施例。可以理解，方法实施例的描述与装置实施例的描述可以相互对应，因此，未描述的部分可以参见前面方法实施例。
可以理解的是，上述各个方法实施例中，由功能网元实现的方法和操作，也可以由可用于功能网元的部件(例如芯片或者电路)实现。由终端设备实现的方法和操作，也可以由可用于终端设备的部件(例如芯片或者电路)实现，由ECS实现的方法和操作，也可以由可用于ECS的部件(例如芯片或者电路)实现。由控制面核心网网元实现的方法和操作，也可以由可用于控制面核心网网元的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方 法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图12是本申请实施例提供的通信装置的示意性框图。该通信装置300包括收发单元310和处理单元320。收发单元310可以与外部进行通信，处理单元320用于进行数据处理。收发单元310还可以称为通信接口或通信单元。
可选地，该通信装置300还可以包括存储单元，该存储单元可以用于存储指令或者和/或数据，处理单元320可以读取存储单元中的指令或者和/或数据。
在一种设计中，该通信装置300可以为第一ECS，收发单元310用于执行上文方法实施例中第一ECS的接收或发送的操作，处理单元320用于执行上文方法实施例中第一ECS内部处理的操作。
或者，该通信装置300可以为包括第一ECS的设备。或者，该通信装置300可以为配置在第一ECS中的部件，例如，第一ECS中的芯片。这种情况下，收发单元310可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元320可以包括处理电路。
一种可能的实现方式中，若确定第一ECS管理的EES不能为终端设备提供边缘服务，该处理单元320用于获取第二ECS的信息，该收发单元310用于向第一设备发送第一信息，该第一信息包括第一EES的信息或该第二ECS的信息，第一EES为第二ECS管理的EES。
一种可能的实现方式中，该处理单元320还用于根据配置信息获取该第二ECS的信息。
一种可能的实现方式中，该收发单元310还用于向联邦控制网元发送第一请求信息，该第一请求信息用于请求第二ECS的信息，该收发单元310还用于接收来自联邦控制网元的第一响应信息，第一响应信息包括第二ECS的信息。
一种可能的实现方式中，该收发单元310还用于向第二ECS发送第二请求信息，该第二请求信息用于请求第一EES的信息，该收发单元310还用于接收来自第二ECS的第二响应信息，该第二响应信息包括第一EES的信息。
一种可能的实现方式中，该收发单元310还用于接收来自第一设备的第三请求信息，第三请求信息用于请求该第一EES的信息，该处理单元320还用于根据第三请求信息确定该第一ECS管理的EES不能为终端设备提供边缘服务。
一种可能的实现方式中，第一请求信息，第二请求信息，或第三请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，第一EES的特征信息，应用信息。
在一种设计中，该通信装置300可以为第二ECS，收发单元310用于执行上文方法实施例中第二ECS的接收或发送的操作，处理单元320用于执行上文方法实施例中第二ECS 内部处理的操作。
或者，该通信装置300可以为包括第二ECS的设备。或者，该通信装置300可以为配置在第二ECS中的部件，例如，第二ECS中的芯片。这种情况下，收发单元310可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元320可以包括处理电路。
一种可能的实现方式中，该收发单元310用于接收来自第一ECS的第二请求信息，该第二请求信息用于请求第一EES的信息，该处理单元320用于根据第二请求信息确定第一EES的信息，该收发单元310还用于向第一ECS发送第二响应信息，该第二响应信息包括第一EES的信息。
一种可能的实现方式中，第二请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，第一EES的特征信息，应用信息，终端设备的位置信息。
一种可能的实现方式中，该处理单元320还用于根据该第二请求信息，以及本地的ECS配置文件确定第一EES的信息，该ECS配置文件包括以下至少一项：ECS的地址信息，ECS的服务范围，ECS管理的EES配置文件，ECS的ECSP标识，ECS对应的PLMN标识。
在一种设计中，该通信装置300可以为终端设备，收发单元310用于执行上文方法实施例中终端设备的接收或发送的操作，处理单元320用于执行上文方法实施例中终端设备内部处理的操作。
或者，该通信装置300可以为包括终端设备的设备。或者，该通信装置300可以为配置在终端设备中的部件，例如，终端设备中的芯片。这种情况下，收发单元310可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元320可以包括处理电路。
一种可能的实现方式中，该收发单元310用于向第一功能网元发送第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息，该收发单元310还用于接收来自该第一功能网元的第一响应信息，该第一响应信息包括第一ECS的信息。
一种可能的实现方式中，该处理单元320用于获取第一功能网元的地址信息。
一种可能的实现方式中，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
图13是本申请实施例提供的通信装置的示意性框图。该通信装置400包括收发单元410和处理单元420。收发单元410可以与外部进行通信，处理单元420用于进行数据处理。收发单元410还可以称为通信接口或通信单元。
可选地，该通信装置400还可以包括存储单元，该存储单元可以用于存储指令或者和/或数据，处理单元420可以读取存储单元中的指令或者和/或数据。
在一种设计中，该通信装置400可以为第一功能网元，收发单元410用于执行上文方法实施例中第一功能网元的接收或发送的操作，处理单元420用于执行上文方法实施例中第一功能网元内部处理的操作。
或者，该通信装置400可以为包括第一功能网元的设备。或者，该通信装置400可以 为配置在第一功能网元中的部件，例如，第一功能网元中的芯片。这种情况下，收发单元410可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元420可以包括处理电路。
一种可能的实现方式中，该收发单元410用于接收来自终端设备的第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，第一功能网元为联邦控制网元或者第一ECS发现代理，第一功能网元存储至少一个ECS的信息，该处理单元420用于根据该第一请求信息确定第一ECS，该收发单元410还用于向终端设备发送第一响应信息，该第一响应信息包括该第一ECS的信息。
一种可能的实现方式中，第一功能网元为第一ECS发现代理，该处理单元420具体用于根据该第一请求信息和/或本地配置确定第二ECS发现代理的信息，该收发单元410还用于向第二ECS发现代理发送第二请求信息，该第二请求信息用于请求第一ECS的信息，该收发单元410还用于接收来自第二ECS发现代理的第二响应信息，该第二响应信息包括第一ECS的信息。
一种可能的实现方式中，该处理单元420用于根据第一请求信息，控制该收发单元410向联邦控制网元发送第三请求信息，该第三请求信息用于请求第二ECS发现代理的信息，该收发单元410还用于接收来自联邦控制网元的第三响应信息，该第三响应信息包括第二ECS发现代理的信息。
一种可能的实现方式中，第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
在一种设计中，该通信装置400可以为第一控制面核心网网元，收发单元410用于执行上文方法实施例中第一控制面核心网网元的接收或发送的操作，处理单元420用于执行上文方法实施例中第一控制面核心网网元内部处理的操作。
或者，该通信装置400可以为包括第一控制面核心网网元的设备。或者，该通信装置400可以为配置在第一控制面核心网网元中的部件，例如，第一控制面核心网网元中的芯片。这种情况下，收发单元410可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元420可以包括处理电路。
一种可能的实现方式中，该收发单元410用于接收来自第二网络的第二控制面核心网网元的第一指示信息，该第一指示信息指示终端设备支持接入第一网络的边缘服务，该处理单元420用于根据第一指示信息控制该收发单元向第一网络的第三控制面核心网网元发送第一请求信息，该第一请求信息用于请求第一网络的第一边缘配置服务器ECS的信息，该收发单元410还用于接收来自第三控制面核心网网元的第一响应信息，该第一响应信息包括第一ECS的信息。
一种可能的实现方式中，第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息。
在一种设计中，该通信装置400可以为第三控制面核心网网元，收发单元410用于执行上文方法实施例中第三控制面核心网网元的接收或发送的操作，处理单元420用于执行上文方法实施例中第三控制面核心网网元内部处理的操作。
或者，该通信装置400可以为包括第三控制面核心网网元的设备。或者，该通信装置400可以为配置在第三控制面核心网网元中的部件，例如，第三控制面核心网网元中的芯 片。这种情况下，收发单元410可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元420可以包括处理电路。
一种可能的实现方式中，该收发单元410用于接收来自第一控制面核心网网元的第一请求信息，该第一请求信息用于请求第一边缘配置服务器ECS的信息，该第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，终端设备的位置信息，该处理单元420用于根据第一请求信息确定第一ECS的信息，该收发单元410还用于向第一控制面核心网网元发送第一响应信息，该第一响应信息包括第一ECS的信息。
一种可能的实现方式中，该处理单元420具体用于根据PLMN标识，以及PLMN标识与ECS的对应关系确定该第一ECS的信息，和/或，该处理单元420具体用于根据ECSP标识，以及该ECSP标识与ECS的对应关系确定第一ECS的信息，和/或，该处理单元420具体用于根据终端设备的位置信息以及ECS的服务范围确定第一ECS的信息。
如图14所示，本申请实施例还提供一种通信装置500。该通信装置500包括处理器510，处理器510与存储器520耦合，存储器520用于存储计算机程序或指令或者和/或数据，处理器510用于执行存储器520存储的计算机程序或指令和/或者数据，使得上文方法实施例中的方法被执行。
可选地，该通信装置500包括的处理器510为一个或多个。
可选地，如图14所示，该通信装置500还可以包括存储器520。
可选地，该通信装置500包括的存储器520可以为一个或多个。
可选地，该存储器520可以与该处理器510集成在一起，或者分离设置。
可选地，如图14所示，该通信装置500还可以包括收发器530和/或通信接口，收发器530和/或通信接口用于信号的接收和/或发送。例如，处理器510用于控制收发器530进行信号的接收和/或发送。
作为一种方案，该通信装置500用于实现上文方法实施例中由第一ECS执行的操作。
例如，处理器510用于实现上文方法实施例中由第一ECS内部执行的操作，收发器530用于实现上文方法实施例中由第一ECS执行的接收或发送的操作。装置300中的处理单元320可以为图14中的处理器，收发单元310可以为图14中的收发器和/或通信接口。处理器510执行的操作具体可以参见上文对处理单元320的说明，收发器530执行的操作可以参见对收发单元310的说明，这里不再赘述。
作为另一种方案，该通信装置500用于实现上文方法实施例中由第二ECS执行的操作。
例如，处理器510用于实现上文方法实施例中由第二ECS内部执行的操作，收发器530用于实现上文方法实施例中由第二ECS执行的接收或发送的操作。装置300中的处理单元320可以为图14中的处理器，收发单元310可以为图14中的收发器和/或通信接口。处理器510执行的操作具体可以参见上文对处理单元320的说明，收发器530执行的操作可以参见对收发单元310的说明，这里不再赘述。
作为另一种方案，该通信装置500用于实现上文方法实施例中由终端设备执行的操作。
例如，处理器510用于实现上文方法实施例中由终端设备内部执行的操作，收发器530用于实现上文方法实施例中由终端设备执行的接收或发送的操作。装置300中的处理 单元320可以为图14中的处理器，收发单元310可以为图14中的收发器和/或通信接口。处理器510执行的操作具体可以参见上文对处理单元320的说明，收发器530执行的操作可以参见对收发单元310的说明，这里不再赘述。
如图15所示，本申请实施例还提供一种通信装置600。该通信装置600包括处理器610，处理器610与存储器620耦合，存储器620用于存储计算机程序或指令或者和/或数据，处理器610用于执行存储器620存储的计算机程序或指令和/或者数据，使得上文方法实施例中的方法被执行。
可选地，该通信装置600包括的处理器610为一个或多个。
可选地，如图15所示，该通信装置600还可以包括存储器620。
可选地，该通信装置600包括的存储器620可以为一个或多个。
可选地，该存储器620可以与该处理器610集成在一起，或者分离设置。
可选地，如图15所示，该通信装置600还可以包括收发器630和/或通信接口，收发器630和/或通信接口用于信号的接收和/或发送。例如，处理器610用于控制收发器630和/或通信接口进行信号的接收和/或发送。
作为一种方案，该通信装置600用于实现上文方法实施例中由第一功能网元执行的操作。例如，处理器610用于实现上文方法实施例中由第一功能网元内部执行的操作，收发器630用于实现上文方法实施例中由第一功能网元执行的接收或发送的操作。装置400中的处理单元420可以为图15中的处理器，收发单元410可以为图15中的收发器。处理器610执行的操作具体可以参见上文对处理单元420的说明，收发器630执行的操作可以参见对收发单元410的说明，这里不再赘述。
作为另一种方案，该通信装置600用于实现上文方法实施例中由第一控制面核心网网元执行的操作。例如，处理器610用于实现上文方法实施例中由第一控制面核心网网元内部执行的操作，收发器630用于实现上文方法实施例中由第一控制面核心网网元执行的接收或发送的操作。装置400中的处理单元420可以为图15中的处理器，收发单元410可以为图15中的收发器。处理器610执行的操作具体可以参见上文对处理单元420的说明，收发器630执行的操作可以参见对收发单元410的说明，这里不再赘述。
作为另一种方案，该通信装置600用于实现上文方法实施例中由第三控制面核心网网元执行的操作。例如，处理器610用于实现上文方法实施例中由第三控制面核心网网元内部执行的操作，收发器630用于实现上文方法实施例中由第三控制面核心网网元执行的接收或发送的操作。装置400中的处理单元420可以为图15中的处理器，收发单元410可以为图15中的收发器。处理器610执行的操作具体可以参见上文对处理单元420的说明，收发器630执行的操作可以参见对收发单元410的说明，这里不再赘述。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图3-图11所示实施例中任意一个实施例的方法。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由第一ECS执行的方法，或由第二ECS执行的方法，或由终端设备执行的方法，或由第一功能网元执行的方法，或由第一控制面核心网网元执行的方法，或由第三控制面核心网网元执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由第一ECS执行的方法，或由第二ECS执行的方法，或由终端设备执行的方法，或由第一功能网元执行的方法，或由第一控制面核心网网元执行的方法，或由第三控制面核心网网元执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文实施例中的第一ECS，第二ECS和终端设备。可选地，该通信系统还包括上文实施例中的第一功能网元，或者第一控制面核心网网元，或者第三控制面核心网网元。
上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中的第一ECS，第二ECS，终端设备，第一功能网元和控制面核心网网元与方法实施例中的第一ECS，第二ECS，终端设备，第一功能网元和控制面核心网网元对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可 以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-onlymemory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种获取边缘服务的方法，其特征在于，包括：
    若第一边缘配置服务器ECS确定所述第一ECS管理的边缘使能服务器EES不能为终端设备提供边缘服务，所述第一ECS获取第二ECS的信息；
    所述第一ECS向第一设备发送第一信息，所述第一信息包括第一EES的信息或所述第二ECS的信息，所述第一EES为所述第二ECS管理的EES。
  2. 根据权利要求1所述的方法，其特征在于，所述第一ECS获取第二ECS的信息，包括：
    所述第一ECS根据配置信息获取所述第二ECS的信息。
  3. 根据权利要求1所述的方法，其特征在于，所述第一ECS获取第二ECS的信息，包括：
    所述第一ECS向联邦控制网元发送第一请求信息，所述第一请求信息用于请求所述第二ECS的信息，所述联邦控制网元存储至少一个ECS的信息；
    所述第一ECS接收来自所述联邦控制网元的第一响应信息，所述第一响应信息包括所述第二ECS的信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，在所述第一ECS向第一设备发送所述第一信息之前，所述方法还包括：
    所述第一ECS向所述第二ECS发送第二请求信息，所述第二请求信息用于请求所述第一EES的信息；
    所述第一ECS接收来自所述第二ECS的第二响应信息，所述第二响应信息包括所述第一EES的信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一ECS接收来自所述第一设备的第三请求信息，所述第三请求信息用于请求所述第一EES的信息；
    所述第一ECS根据所述第三请求信息确定所述第一ECS管理的EES不能为所述终端设备提供边缘服务。
  6. 根据权利要求5所述的方法，其特征在于，所述第三请求信息包括以下至少一项：
    所述终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，所述第一EES的特征信息，应用信息。
  7. 一种获取边缘服务的方法，其特征在于，包括：
    第二边缘配置服务器ECS接收来自第一ECS的第二请求信息，所述第二请求信息用于请求第一边缘使能服务器EES的信息；
    所述第二ECS根据所述第二请求信息确定所述第一EES的信息；
    所述第二ECS向所述第一ECS发送第二响应信息，所述第二响应信息包括所述第一EES的信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第二请求信息包括以下至少一项：
    终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP的标识，所 述第一EES的特征信息，应用信息。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第二ECS根据所述第二请求信息确定所述第一EES的信息，包括：
    所述第二ECS根据所述第二请求信息，以及本地的ECS配置文件确定所述第一EES的信息，所述ECS配置文件包括以下至少一项：所述ECS的地址信息，所述ECS的服务范围，所述ECS管理的EES配置文件，所述ECS的ECSP标识，所述ECS对应的PLMN标识。
  10. 一种获取边缘服务的方法，其特征在于，包括：
    终端设备向第一功能网元发送第一请求信息，所述第一请求信息用于请求第一边缘配置服务器ECS的信息，所述第一功能网元为联邦控制网元或者第一ECS发现代理，所述第一功能网元存储至少一个ECS的信息；
    所述终端设备接收来自所述第一功能网元的第一响应信息，所述第一响应信息包括第一ECS的信息。
  11. 根据权利要求10所述的方法，其特征在于，在所述终端设备向第一功能网元发送第一请求信息之前，所述方法还包括：
    所述终端设备获取所述第一功能网元的地址信息。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第一请求信息包括以下至少一项：
    所述终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，所述终端设备的位置信息。
  13. 一种获取边缘服务的方法，其特征在于，包括：
    第一功能网元接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一边缘配置服务器ECS的信息，所述第一功能网元为联邦控制网元或者第一ECS发现代理，所述第一功能网元存储至少一个ECS的信息；
    所述第一功能网元根据所述第一请求信息确定第一ECS的信息；
    所述第一功能网元向所述终端设备发送第一响应信息，所述第一响应信息包括所述第一ECS的信息。
  14. 根据权利要求13所述的方法，其特征在于，所述第一功能网元为第一ECS发现代理，在所述第一功能网元根据所述第一请求信息确定第一ECS的信息，包括：
    所述第一ECS发现代理根据所述第一请求信息，和/或本地配置确定第二ECS发现代理的信息；
    所述第一ECS发现代理向所述第二ECS发现代理发送第二请求信息，所述第二请求信息用于请求所述第一ECS的信息；
    所述第一ECS发现代理接收来自所述第二ECS发现代理的第二响应信息，所述第二响应信息包括所述第一ECS的信息。
  15. 根据权利要求14所述的方法，其特征在于，所述第一ECS发现代理根据所述第一请求信息和/或本地配置确定第二ECS发现代理的信息，包括：
    所述第一ECS发现代理根据所述第一请求信息，向所述联邦控制网元发送第三请求信息，所述第三请求信息用于请求所述第二ECS发现代理的信息；
    所述第一ECS发现代理接收来自所述联邦控制网元的第三响应信息，所述第三响应信息包括第二ECS发现代理的信息。
  16. 根据权利要求15所述的方法，其特征在于，所述第一请求信息，所述第二请求信息，或所述第三请求信息包括以下至少一项：
    所述终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，所述终端设备的位置信息。
  17. 一种获取边缘服务的方法，其特征在于，包括：
    第一网络的第一控制面核心网网元接收来自第二网络的第二控制面核心网网元的第一指示信息，所述第一指示信息指示终端设备支持接入所述第一网络的边缘服务；
    所述第一控制面核心网网元根据所述第一指示信息向所述第一网络的第三控制面核心网网元发送第一请求信息，所述第一请求信息用于请求所述第一网络的第一边缘配置服务器ECS的信息；
    所述第一控制面核心网网元接收来自所述第三控制面核心网网元的第一响应信息，所述第一响应信息包括所述第一ECS的信息。
  18. 根据权利要求17所述的方法，其特征在于，所述第一请求信息包括以下至少一项：
    所述终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，所述终端设备的位置信息。
  19. 一种获取边缘服务的方法，其特征在于，包括：
    第一网络的第三控制面核心网网元接收来自第一网络的第一控制面核心网网元的第一请求信息，所述第一请求信息用于请求第一网络的第一边缘配置服务器ECS的信息，所述第一请求信息包括以下至少一项：终端设备接入的公共陆地移动网PLMN标识，边缘计算服务提供商ECSP标识，所述终端设备的位置信息；
    所述第三控制面核心网网元根据所述第一请求信息确定所述第一ECS的信息；
    所述第三控制面核心网网元向所述第一控制面核心网网元发送第一响应信息，所述第一响应信息包括所述第一ECS的信息。
  20. 根据权利要求19所述的方法，其特征在于，所述第三控制面核心网网元根据所述第一请求信息确定所述第一ECS的信息，包括以下至少一项：
    所述第三控制面核心网网元根据所述PLMN标识，以及所述PLMN标识与ECS的对应关系确定所述第一ECS的信息；
    所述第三控制面核心网网元根据所述ECSP标识，以及所述ECSP标识与ECS的对应关系确定所述第一ECS的信息；
    所述第三控制面核心网网元根据所述终端设备的位置信息，以及ECS的服务范围确定所述第一ECS的信息。
  21. 一种通信装置，其特征在于，包括用于执行如权利要求1至6中任一项所述方法的模块，或包括用于执行如权利要求7至9中任一项所述方法的模块，或包括用于执行如权利要求10至12中任一项所述方法的模块，或包括用于执行如权利要求13至16中任一项所述方法的模块，或包括用于执行如权利要求17至18中任一项所述方法的模块，或包括用于执行如权利要求19至20中任一项所述方法的模块。
  22. 一种通信装置，其特征在于，包括处理器和存储器；所述存储器用于存储一个或多个计算机程序，当所述一个或多个计算机程序被运行时，使得如权利要求1至6中任一项所述的方法被执行，或使得如权利要求7至9中任一项所述的方法被执行，或使得如权利要求10至12中任一项所述的方法被执行；或使得如权利要求13至16中任一项所述的方法被执行，或使得如权利要求17至18中任一项所述的方法被执行，或使得如权利要求19至20中任一项所述的方法被执行。
  23. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至6中任一项所述的方法，或使得所述计算机执行如权利要求7至9中任一项所述的方法，或使得所述计算机执行如权利要求10至12中任一项所述的方法，或使得所述计算机执行如权利要求13至16中任一项所述的方法，或使得所述计算机执行如权利要求17至18中任一项所述的方法，或使得所述计算机执行如权利要求19至20中任一项所述的方法。
  24. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，实现如权利要求1至6中任一项所述的方法，或实现如权利要求7至9中任一项所述的方法，或实现如权利要求10至12中任一项所述的方法，或实现如权利要求13至16中任一项所述的方法，或实现如权利要求17至18中任一项所述的方法，或实现如权利要求19至20中任一项所述的方法。
PCT/CN2022/108796 2021-08-18 2022-07-29 获取边缘服务的方法和装置 Ceased WO2023020249A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22857561.9A EP4383779A4 (en) 2021-08-18 2022-07-29 METHOD AND APPARATUS FOR OBTAINING ON-BOARD SERVICE
US18/443,404 US20240187303A1 (en) 2021-08-18 2024-02-16 Method and apparatus for obtaining edge service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110950242.7 2021-08-18
CN202110950242.7A CN113840293B (zh) 2021-08-18 2021-08-18 获取边缘服务的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/443,404 Continuation US20240187303A1 (en) 2021-08-18 2024-02-16 Method and apparatus for obtaining edge service

Publications (1)

Publication Number Publication Date
WO2023020249A1 true WO2023020249A1 (zh) 2023-02-23

Family

ID=78960803

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/108796 Ceased WO2023020249A1 (zh) 2021-08-18 2022-07-29 获取边缘服务的方法和装置

Country Status (4)

Country Link
US (1) US20240187303A1 (zh)
EP (1) EP4383779A4 (zh)
CN (1) CN113840293B (zh)
WO (1) WO2023020249A1 (zh)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113840293B (zh) * 2021-08-18 2023-04-18 华为技术有限公司 获取边缘服务的方法和装置
CN116546479A (zh) * 2022-01-26 2023-08-04 华为技术有限公司 一种通信方法及装置
CN114599022B (zh) * 2022-01-30 2024-08-09 华为技术有限公司 设备选择的方法以及装置
CN116567523A (zh) * 2022-01-30 2023-08-08 华为技术有限公司 设备选择的方法以及装置
CN116614824A (zh) * 2022-02-08 2023-08-18 华为技术有限公司 请求应用功能的方法、装置和系统
EP4476899A1 (en) * 2022-02-08 2024-12-18 Qualcomm Incorporated Using an edge repository
CN116709291A (zh) * 2022-02-28 2023-09-05 华为技术有限公司 通信的方法和装置
CN116939573A (zh) * 2022-03-29 2023-10-24 中国移动通信有限公司研究院 Eas的发现方法、装置及网络设备
CN116939009A (zh) * 2022-03-29 2023-10-24 华为技术有限公司 一种通信方法、装置及设备
CN117014907A (zh) * 2022-05-06 2023-11-07 维沃移动通信有限公司 Edi获取、路由重配置、ecs地址配置信息的获取、dns处理方法、装置及设备
CN117241256A (zh) * 2022-06-15 2023-12-15 华为技术有限公司 T-ees发现方法及相关装置
WO2023240657A1 (zh) * 2022-06-17 2023-12-21 北京小米移动软件有限公司 认证与授权方法、装置、通信设备及存储介质
WO2024022278A1 (en) * 2022-07-26 2024-02-01 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for mobility management
CN115499470B (zh) * 2022-09-17 2023-08-04 浙江晨泰科技股份有限公司 一种智能电表数据的存储管理方法及装置
WO2024065706A1 (zh) * 2022-09-30 2024-04-04 北京小米移动软件有限公司 一种构建连接的方法及装置
CN115767638B (zh) * 2022-11-11 2025-10-28 中国联合网络通信集团有限公司 通信方法、装置及存储介质
US20240248537A1 (en) * 2023-01-25 2024-07-25 Indian Institute Of Technology Delhi System and method for enabling a multi-operator edge environment
CN120785950A (zh) * 2024-04-02 2025-10-14 华为技术有限公司 确定边缘应用服务器eas的方法和通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111787038A (zh) * 2019-04-04 2020-10-16 华为技术有限公司 一种提供边缘服务的方法、系统及计算设备
WO2021138069A1 (en) * 2019-12-31 2021-07-08 Convida Wireless, Llc Edge service configuration
CN113132897A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 应用实例确定的方法、装置及系统
CN113840293A (zh) * 2021-08-18 2021-12-24 华为技术有限公司 获取边缘服务的方法和装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112217856B (zh) * 2019-07-11 2024-06-18 华为技术有限公司 应用实例的地址获取方法、装置、设备及存储介质
US11277305B2 (en) * 2019-10-09 2022-03-15 Qualcomm Incorporated Edge discovery techniques in wireless communications systems
WO2021086157A1 (en) * 2019-11-02 2021-05-06 Samsung Electronics Co., Ltd. Method and system for managing discovery of edge application servers
CN113132908B (zh) * 2019-12-31 2023-04-07 华为技术有限公司 一种业务管理方法及装置
EP4055805B1 (en) * 2020-02-03 2024-09-11 Samsung Electronics Co., Ltd. Method and apparatus for providing edge computing services
CN113938910B (zh) * 2020-07-13 2024-10-29 华为技术有限公司 一种通信方法及装置
CN112202844B (zh) * 2020-09-10 2022-05-06 中国联合网络通信集团有限公司 一种跨域多接入边缘计算能力开放的方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111787038A (zh) * 2019-04-04 2020-10-16 华为技术有限公司 一种提供边缘服务的方法、系统及计算设备
WO2021138069A1 (en) * 2019-12-31 2021-07-08 Convida Wireless, Llc Edge service configuration
CN113132897A (zh) * 2019-12-31 2021-07-16 华为技术有限公司 应用实例确定的方法、装置及系统
CN113840293A (zh) * 2021-08-18 2021-12-24 华为技术有限公司 获取边缘服务的方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Service provisioning in roaming scenario", 3GPP DRAFT; S6-202185, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. e-meeting; 20201116 - 20201124, 11 November 2020 (2020-11-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051953660 *
QUALCOMM INCORPORATED: "Correction of ECS Address Configuration Information - Option 2", 3GPP DRAFT; S2-2106485, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20210816 - 20210827, 10 August 2021 (2021-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052054218 *

Also Published As

Publication number Publication date
EP4383779A1 (en) 2024-06-12
US20240187303A1 (en) 2024-06-06
EP4383779A4 (en) 2024-11-27
CN113840293A (zh) 2021-12-24
CN113840293B (zh) 2023-04-18

Similar Documents

Publication Publication Date Title
CN113840293B (zh) 获取边缘服务的方法和装置
CN114270789B (zh) 一种获取信息的方法及装置
WO2021027177A1 (en) Method and apparatus for network function service discovery
CN108323245B (zh) 一种注册及会话建立的方法、终端和amf实体
CN113630749B (zh) 一种获取边缘服务的方法和装置
WO2019157942A1 (zh) 通信方法和通信装置
WO2022012310A1 (zh) 一种通信方法及装置
WO2023051428A1 (zh) 信息传输的方法和装置
WO2019196680A1 (zh) 通信方法和通信装置
WO2023051431A1 (zh) 通信的方法和装置
US20240380848A1 (en) Communication method and apparatus
WO2023051427A1 (zh) 通信的方法和装置
WO2022170518A1 (zh) 一种确定终端设备的地址的方法及装置、网络设备
WO2020024865A1 (zh) 一种会话对应关系的管理方法和终端设备
WO2022100197A1 (zh) 获取边缘服务的方法和装置
WO2023124457A1 (zh) 选择网络的方法和装置
WO2023011078A1 (zh) 去注册的方法和通信装置
US20240121672A1 (en) Context relocation method and apparatus
WO2023142632A1 (zh) 通信方法及通信装置
WO2023185620A1 (zh) 通信的方法和装置
WO2022237631A1 (zh) 用于信息传输的方法和装置
JP7782061B2 (ja) 通信方法及び通信装置
WO2023185561A1 (zh) 通信方法和通信装置
WO2023151420A1 (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: 22857561

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022857561

Country of ref document: EP

Effective date: 20240305

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11202400990T

Country of ref document: SG