WO2024099147A1 - 一种获取边缘计算服务的方法、通信系统及装置 - Google Patents

一种获取边缘计算服务的方法、通信系统及装置 Download PDF

Info

Publication number
WO2024099147A1
WO2024099147A1 PCT/CN2023/127925 CN2023127925W WO2024099147A1 WO 2024099147 A1 WO2024099147 A1 WO 2024099147A1 CN 2023127925 W CN2023127925 W CN 2023127925W WO 2024099147 A1 WO2024099147 A1 WO 2024099147A1
Authority
WO
WIPO (PCT)
Prior art keywords
ees
eas
information
eec
group
Prior art date
Application number
PCT/CN2023/127925
Other languages
English (en)
French (fr)
Inventor
胡雅婕
杨艳梅
葛翠丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024099147A1 publication Critical patent/WO2024099147A1/zh

Links

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present application relates to the field of communication technology, and in particular to a method, communication system and device for obtaining edge computing services.
  • the edge enabler client (EEC) on the user equipment (UE) side discovers the edge enabler server (EES) in the edge data network (EDN) through the edge configuration server (ECS). Furthermore, the EEC can discover the edge application server (EAS) through the EES. Then, the application client (AC) on the UE side can establish a connection with the EAS and obtain business data from the EAS.
  • EES edge enabler server
  • EES edge data network
  • EES edge configuration server
  • the application client (AC) on the UE side can establish a connection with the EAS and obtain business data from the EAS.
  • the present application provides a method, a communication system and a device for obtaining edge computing services, which are used to solve the problem that the EAS discovery method in the prior art is not flexible enough.
  • a method for obtaining edge computing services is provided, which can be applied to a first EEC, and the method may include: the first EEC may send information of at least one EES to the first entity, and the at least one EES can provide edge computing services for the first EEC.
  • the first EEC may also receive information of at least one EAS from the first entity, and the at least one EAS corresponds to at least one EES, and the at least one EAS can provide edge computing services for the first AC.
  • the first EEC can obtain at least one EAS that can provide edge computing services for the first AC, so that the first EEC can select an EAS from at least one EAS to provide edge computing services for the first AC. This method can improve the flexibility of the EEC in selecting EAS.
  • the first entity may be a first EES.
  • the first EEC is an edge enabling server deployed in the first UE
  • the first AC is an application client deployed in the first UE
  • the first EEC, the first AC and the first UE can be considered to be the same entity.
  • the first AC can be said to correspond to the first EEC.
  • the method may further include: the first EEC sends information of the first group to the first EES, and the information of the first group can be used to determine the EAS that provides edge computing services for the UEs included in the first group. Based on this, the solution of the present application can also be used to determine a common EAS for a group of UEs.
  • the first group may include the above-mentioned first UE.
  • the information of the first group includes a group identifier and/or a UE list, wherein the UE list is a list of UEs included in the first group.
  • the method may further include: a first EEC receives information of a first group, the information of the first group is associated with a first EAS in at least one EAS, wherein the first EAS can provide edge computing services for UEs included in the first group.
  • the information of the first EAS and the information of the first group can be received together to reflect the correspondence between the first EAS and the first group, so that the first EEC can know that the first EAS can provide edge computing services for the UE included in the first group.
  • the method may further include: the first EEC determines the first EAS as an EAS that can provide edge computing services for the first AC according to the correspondence between the first EAS and the first group.
  • the first EAS corresponds to a second EES in at least one EES
  • the second EES can provide edge computing services for the UE included in the first group.
  • the method may further include: the first EEC
  • the first EAS is determined to be an EAS that can provide edge computing services for the UEs included in the first group.
  • the method may further include: the first EEC sends information of the first EAS to the first EES.
  • the first EEC may send the information of the first EAS determined by it and the information of the first group to the first EES.
  • This implementation may reflect the correspondence between the first EAS and the first group, so that the first EES learns that the first EAS can provide edge computing services for the UEs included in the first group.
  • the first EAS corresponds to the first EES, and the first EAS is an EAS registered on the first EES.
  • the method may further include: the first EEC may send first service information to the first EES, where the first service information is used to determine at least one EAS.
  • the first service information is service information corresponding to the first AC.
  • the information of any one of the at least one EES may include at least one of the following: identification information of the EES, address information of the EES, or deployment information corresponding to the EES.
  • the deployment information corresponding to the EES may include at least one of the following: EDN information of the EES, the topological service scope of the EES, the geographical service scope of the EES, the DNAI corresponding to the EES, or the level to which the EES belongs.
  • any one of the information of at least one EAS may include at least one of the following: address information of the EAS, identification information of the EAS, or endpoint information of the EAS.
  • the endpoint information of EAS may include at least one of the following: EAS URI, FQDN, or IP address.
  • the method further includes: the first EEC sends location information of the first UE to the first ECS, and the first EEC and the first AC are deployed in the first UE.
  • the method may further include: the first EEC receives information from at least one EES of the first ECS.
  • the method may further include: the first EEC determines the information of at least one EES sent to the first entity based on the information of at least one EES received from the first ECS.
  • the information of at least one EES received by the first EEC from the first ECS can be recorded as the information of m EESs
  • the information of at least one EES sent by the first EEC to the first EES can be recorded as the information of n EESs.
  • the information of the n EESs is determined from the information of the m EESs.
  • the method may further include: the first EEC may send location information of the first UE to the first ECS.
  • the first EEC and the first AC are deployed in the first UE.
  • the location information of the first UE may be used to enable the first ECS to determine information of at least one EES.
  • the method may further include: the first EEC may also send the EDN information, edge computing service level information, or EES service level information expected by the first UE to the first ECS.
  • the EDN information, edge computing service level information, or EES service level information expected by the first UE may also be used to enable the first ECS to determine the information of at least one EES.
  • the method may further include: the first EEC may also send a first group of information to the first ECS, and the first group of information may be used to determine information of at least one EES.
  • a method for obtaining edge computing services is provided, which can be applied to a first EES.
  • the method may include: the first edge enabling server EES receives information from at least one EES of a second entity, and the information of the at least one EES is used to determine an EES that can provide edge computing services for the second entity.
  • the second entity is a first EEC.
  • the method may further include: the first EES obtains information of at least one EAS, and the at least one EAS can provide edge computing services for the first AC.
  • the first EEC is an edge enabling server deployed in the first UE
  • the first AC is an application client deployed in the first UE
  • the first EEC, the first AC, and the first UE can be considered to be the same entity.
  • the first AC can be said to correspond to the first EEC.
  • the method may further include: the first EES sends information of at least one EAS to the first EEC.
  • the method may further include: the first EES receives information of a first group from a first EEC, where the information of the first group is used to indicate information of UEs included in the first group.
  • the method may further include: the first EES sends the first group of information to at least one EES.
  • the information of the first group includes a group identifier and/or a UE list.
  • the first group may include the first UE where the first EEC and the first AC are located.
  • the method also includes: the first EES sends information of a first group associated with a first EAS to the first EEC, the first EAS is one EAS among at least one EAS, and the first EAS can provide edge computing services for UEs included in the first group.
  • the first EAS may correspond to the first EES, and the information of the first EAS may be determined by the first EES.
  • the first EAS may correspond to the second EES in at least one EES, and the second EES may provide edge computing services for the UEs included in the first group.
  • the information of the first EAS may be received by the first EES from the second EES.
  • the information of the first EAS is received by the first EES from the second EES through the third EES, and the third EES is used to relay the communication between the first EES and the second EES.
  • the method may also include: the first EES receives information of the first EAS from the first EEC, the first EAS belongs to at least one EAS, and the first EAS can provide edge computing services for the UE included in the first group.
  • the method may further include: the first EES sends information of the first EAS to at least one EES.
  • the method may further include: the first EES receives first service information from the first EEC, where the first service information is used to determine at least one EAS.
  • the method may further include: the first EES sends first service information to at least one EES.
  • the information of any one of the at least one EES may include at least one of the following: identification information of the EES, address information of the EES, or deployment information corresponding to the EES.
  • the deployment information corresponding to the EES may include at least one of the following: EDN information of the EES, the topological service scope of the EES, the geographical service scope of the EES, the DNAI corresponding to the EES, or the level to which the EES belongs.
  • any one of the at least one EAS information includes at least one of the following: EAS address information, EAS identification information, or EAS endpoint information.
  • the endpoint information of EAS may include at least one of the following: EAS URI, FQDN, or IP address.
  • a method for obtaining edge computing services is provided, which can be applied to a second EES.
  • the method may include: the second EES receives information of a first group from a third entity, and the information of the first group can be used to determine an EAS that provides edge computing services for UEs included in the first group.
  • the third entity is a first EES.
  • the method may further include: the second EES sends information of the first EAS to the first EES, and the first EAS is used to provide edge computing services for the UEs included in the first group.
  • the information of the first group is received by the second EES through the third EES.
  • the method may also include: the second EES sends information of the first EAS to the first EES through the third EES, and the first EAS is used to provide edge computing services for the UEs included in the first group.
  • the first EAS corresponds to the second EES, and the information of the first EAS is determined by the second EES.
  • the information of the first EAS may be determined by the second EES and sent to the first EES.
  • the method may further include: the second EES receives information from the first EAS of the first EES, and the first EAS can provide edge computing services for the UEs included in the first group. Based on this solution, the information of the first EAS may be received by the second EES from the first EES.
  • the information of the first EAS and the information of the first group may be received together by the second EES, so that the second EES learns that the first EAS can provide edge computing services for the UEs included in the first group.
  • the method may further include: the second EES receives the The first service information is used to determine the first EAS.
  • the information of the first EAS may include at least one of the following: address information of the first EAS, identification information of the first EAS, or endpoint information of the first EAS.
  • the endpoint information of the first EAS may include at least one of the following: EAS URI, FQDN, or IP address.
  • a method for obtaining edge computing services is provided.
  • the method can be applied to a first ECS.
  • the method may include: the first ECS sends information of at least one EES to a fourth entity, and the at least one EES can provide edge computing services for the fourth entity.
  • the fourth entity is the first EEC.
  • the information of any one of the at least one EES may include at least one of the following: identification information of the EES, address information of the EES, or deployment information corresponding to the EES.
  • the deployment information corresponding to the EES includes at least one of the following: EDN information of the EES, the topological service scope of the EES, the geographical service scope of the EES, the DNAI corresponding to the EES, or the level to which the EES belongs.
  • the method may further include: the first ECS receives location information of a first UE from a first EEC, where the location information of the first UE is used to determine information of at least one EES.
  • the method may also include: the first ECS receives EDN information, edge computing service level information or EES service level information expected by the first UE from the first EEC, and the EDN information, edge computing service level information or EES service level information expected by the first UE is used to determine the information of at least one EES.
  • the first ECS determines the information of multiple EESs according to the location information of the first UE, which may specifically include: the first ECS determines the EDN available to the first UE according to the location information of the first UE. Furthermore, the first ECS may determine the information of multiple EESs from the EDN available to the first UE according to the policy information.
  • the method may further include: the first ECS determines at least one EES information according to information of the first AC.
  • the information of the first AC may include at least one of the following: the identification of the first AC, the type of the first AC, the service KPI required by the first AC, the identification information of the EAS required by the first AC, or the service KPI of the EAS required by the first AC.
  • the method may further include: the first ECS receives a first group of information from a first EEC, and the information of the first group can be used to determine information of at least one EES.
  • a method for obtaining edge computing services is provided, which can be applied to a second EEC, and the method may include: the second EEC sends information of a second group to a fourth EES, and the information of the second group is used to determine an EAS that provides edge computing services for UEs included in the second group.
  • the second EEC receives information of a second EAS from the fourth EES, and the second EAS can provide edge computing services for UEs included in the second group.
  • the method may further include: the second EEC sends second service information to at least one EES, and the second service information may also be used to determine the EAS that provides edge computing services for the UE included in the second group.
  • the second EAS corresponds to the fourth EES, and the information of the second EAS is determined by the fourth EES.
  • the second EEC is an edge enabling server deployed in the second UE
  • the second AC is an application client deployed in the second UE
  • the second EEC, the second AC, and the second UE can be considered to be the same entity.
  • the second AC can be said to correspond to the second EEC.
  • the second group may include a second UE.
  • a method for obtaining edge computing services is provided, which can be applied to a fourth EES, and the method may include: the fourth EES receives information of a second group from a second EEC, where the information of the second group is used to indicate information of UEs included in the second group.
  • the fourth EES sends information of a second EAS to the second EEC, and the second EAS can provide edge computing services for the UEs included in the second group.
  • the method may further include: the fourth EES receives second service information from the second EEC, and the second service information can be used to determine the second EAS.
  • the second EAS corresponds to the fourth EES, and the information of the second EAS is determined by the fourth EES.
  • the second EEC is an edge enabling server deployed in the second UE
  • the second AC is an application client deployed in the second UE
  • the second EEC, the second AC and the second UE can be considered to be the same entity.
  • the second AC corresponds to the second EEC.
  • the second group may include a second UE.
  • a communication device for implementing the above method.
  • the communication device may be the first EEC of the above first aspect, or the first EES of the above second aspect, or the second EES of the above third aspect, or the first ECS of the above fourth aspect, or the second EEC of the above fifth aspect, or the fourth EES of the above sixth aspect.
  • the communication device may include a module, unit, or means corresponding to the above method, and the module, unit, or means may be implemented by hardware, software, or by executing the corresponding software implementation by hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • the communication device includes a processing module and a transceiver module, the transceiver module is used to execute the message receiving and sending operations performed by the communication device side in the method of the first, second, third, fourth, fifth, sixth or seventh aspect above; the processing module is used to call instructions to execute the message processing or control operations performed by the communication device side in the method of the first, second, third, fourth, fifth, sixth or seventh aspect above.
  • a communication device comprising: a processor; the processor is used to couple with a memory, and after reading the computer instructions stored in the memory, execute the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect or the seventh aspect according to the instructions.
  • the communication device further includes a memory; the memory is used to store computer instructions.
  • the communication device further includes a communication interface; the communication interface is used for the communication device to communicate with other devices.
  • the communication interface can be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.
  • the communication device may be a chip or a chip system.
  • the communication device may be composed of a chip, or may include a chip and other discrete devices.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system, etc.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • a computer-readable storage medium which stores instructions, and when the computer-readable storage medium is run on a computer, the computer can execute the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect or the seventh aspect.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first, second, third, fourth, fifth, sixth or seventh aspect above.
  • a communication system which includes a first EEC that executes the method for obtaining edge computing services described in the first aspect and a first EES that executes the method for obtaining edge computing services described in the second aspect.
  • the communication system may also include a second EES that executes the method for obtaining edge computing services described in the third aspect above.
  • the communication system may also include a first ECS that executes the method for obtaining edge computing services described in the fourth aspect above.
  • FIG1 is a schematic diagram of the structure of an edge application architecture and a functional model provided by an embodiment of the present application
  • FIG2 is a schematic diagram of a discovery process of an EES platform and an EAS provided in an embodiment of the present application
  • FIG3 is a schematic diagram of the structure of an edge network provided in an embodiment of the present application.
  • FIG4 is a flowchart of discovering and determining an EAS provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of a hierarchical relationship of an EDN provided in an embodiment of the present application.
  • FIG6 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of a process of an ECS obtaining deployment information of an EES provided in an embodiment of the present application
  • FIG8 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG9 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG10 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG11 is a schematic diagram of another hierarchical relationship of an EDN provided in an embodiment of the present application.
  • FIG12 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG13 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG14 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG15 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG16 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG17 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG18 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG19 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG20 is a flow chart of a method for obtaining edge computing services provided in an embodiment of the present application.
  • FIG21 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG22 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • 3GPP SA6 is conducting research on application-enabled mobile edge computing (MEC), and defines an edge (EDGE) application architecture and functional model as shown in Figure 1.
  • MEC mobile edge computing
  • EDGE edge
  • the functional entities are introduced as follows:
  • EDN Edge Data Network
  • a general understanding is that EDN corresponds to only one data network, which is a special local data network (local data network) that includes edge-enabling functions. It can be identified using a data network access identifier (DNAI) and a data network name (DNN). It is a network logical concept.
  • DNN data network name
  • Another understanding of EDN is that EDN is a peer-to-peer concept of the central cloud. It can be understood as a local data center (geographic location concept), which can be identified using DNAI and can include multiple local data networks.
  • EDN can be used to provide edge business services.
  • Applications deployed in edge data networks are called application instances or edge applications.
  • An application instance or edge application can be an instance of an application (for example, social media software, augmented reality (AR), virtual reality (VR)) deployed and running on EDN.
  • a general understanding is that EDN corresponds to only one data network, which is a special local data network (local data network) that includes edge-enabling functions. It can be identified
  • EAS Edge Application Server
  • An application can deploy one or more EAS in one or more EDNs.
  • EAS deployed and running in different EDNs can be considered as different EAS of an application. They can share a domain name, use an IP address, or use different IP addresses.
  • EAS can also be called edge application (server), application instance, edge application instance, MEC application (server), EAS function, etc.
  • EES Edge Enabling Server
  • EES is deployed in the EDN and can provide some enabling capabilities for application instances in the EDN.
  • EES can support the registration of application instances, authentication and authorization of UEs, and provide UEs with IP address information of application instances.
  • EES can further support obtaining the identification and IP address information of application instances, and further send the identification and IP address information of application instances to ECS.
  • an EAS is registered to an EES, or the information of an EAS is configured on an EES through the management system.
  • the EES is called the EES associated with the EAS.
  • EES can be used to control, manage, register, or configure the EAS associated with the EES.
  • the application client is a client program applied on the terminal side.
  • Application users can use the application client to obtain application services from the application server.
  • the application client can connect to the application server on the cloud to obtain application services, or it can connect to the EAS deployed and running in one or more EDNs to obtain application services.
  • the application client is deployed in the UE and can be considered as the peer entity of the EAS on the UE side.
  • EEC Edge Enablement Server
  • EEC is used to register EEC information and application client information with EES, perform security authentication and authorization, obtain EAS IP address from EES, and provide edge computing enabling capabilities to application clients, such as EAS discovery service returns EAS IP address to application clients.
  • EEC is deployed in UE and can be considered as the peer entity of EES on the UE side.
  • ECS Edge Configuration Server
  • application users can log in to the AC on the UE and establish a connection with the EAS through the AC to communicate, thereby obtaining application services.
  • the edge enabling client since the edge enabling client is deployed in the UE, the interaction between other devices and the edge enabling client can also be regarded as the interaction between other devices and the UE. It can also be replaced by UE. In the embodiment of the present application, if not specifically stated, the edge-enabled client and the UE are replaceable.
  • the embodiments of the present application do not limit the specific names of the edge enabling client, edge data network, edge configuration server, edge application server, and edge enabling server.
  • the edge enabling client may be an EEC.
  • the edge enabling client may also have other names.
  • this application takes the edge enabling client as an EEC, the edge data network as an EDN, the edge configuration server as an ECS, the edge application server as an EAS, and the edge enabling server as an EES as an example.
  • the EEC described later in this application can be replaced with an edge enabling client
  • the EDN can be replaced with an edge data network
  • the ECS can be replaced with an edge configuration server
  • the EAS can be replaced with an edge application server
  • the EES can be replaced with an edge enabling server.
  • the application context migration process based on the above EDGE application architecture can mainly include the following four stages:
  • Detection of application context migration that is, determining whether context migration may be required.
  • the detection entity detects some events, such as a change in the UE location or an update to the UE user plane path.
  • Execution of application context migration mainly transferring the application context from the source EAS to the target EAS. It may also further include notifying the terminal of the target EAS information, notifying the network of the completion of the context migration and the relevant information of the target EAS (such as the address of the target EAS, the routing information corresponding to the target EAS, etc.).
  • the application client can switch the connection to the target EAS.
  • the 3GPP SA6 standard defines the discovery process of the EES platform and the EAS, and the architecture and function are designed to use a two-level discovery mechanism: first discover EES from ECS, and then discover EAS from EES.
  • Figure 2 shows a schematic diagram of the discovery process of the EES platform and the EAS provided by the present application, wherein steps 1a to 1c are the process of the terminal side EEC discovering EES from ECS, and steps 2a to 2c are the process of the EEC discovering EAS from EES.
  • the terminal-side EEC discovers the EES from the ECS:
  • Step 1a The EEC sends a request message to the ECS to request to subscribe to the EES available to the UE.
  • the request message may carry EEC identification information, security credentials, AC profile, UE identifier (ID), UE location information, etc.
  • the AC profile may include at least one of the following information: AC identifier (ACID), AC type, expected AC geographic service area, EASID of EAS that can provide services for AC, expected AC service key performance indicator (KPI), and minimum service KPI required by AC.
  • the EEC and AC are entities deployed in the UE, and the actions performed by the EEC, AC, and UE can be considered to be the same execution subject.
  • the EEC and AC deployed in the same UE can be considered to be "corresponding".
  • the AC corresponding to the EEC refers to the AC deployed in the same UE as the EEC, or the EEC is connected to the AC, or the EEC provides services for the AC. This is a unified explanation here and will not be repeated below.
  • EEC requests ECS to subscribe to EES it can be considered that EEC requests ESC to subscribe to EES available to EEC, or EEC requests ESC to subscribe to EES available to AC corresponding to EEC.
  • Step 1b The ECS determines the information of the EES available to the UE.
  • the ECS can determine the information of the EES available to the UE based on at least one of the information such as the AC configuration file, the UE location information, the edge computing service provider (ECSP) policy information, etc.
  • the information such as the AC configuration file, the UE location information, the edge computing service provider (ECSP) policy information, etc.
  • ECSP edge computing service provider
  • the EES available to the UE determined by the ECS may include at least one, and thus, the information of the EES available to the UE may include an EES list, and the EES list may include the identifier of at least one EES.
  • the information of each EES may specifically include at least one of the following information: identification information of the EES, address information of the EES, endpoint information of the EES, EASID information of services on the EES, provider identification of the EES, EDN information of the EES, topological service scope of the EES, geographic service scope of the EES, and DNAI corresponding to the EES.
  • Step 1c ECS returns EES information to EEC.
  • the ECS may also return the EDN information of the EES to the EEC.
  • EEC discovers EAS from EES:
  • Step 2a EEC requests EES to discover EAS.
  • EEC can send an EAS discovery request (EAS discovery request) to EES to request EES to discover EAS.
  • EAS discovery request EAS discovery request
  • the EAS discovery request may include at least one of the following information: UE identifier, EEC identifier, EAS discovery filter, Or UE location information.
  • the EAS discovery filter may include AC profile, EAS feature information and other information.
  • the EAS feature information may include at least one of the following information: EASID, EAS provider ID, EAS type, EAS geographic service range, or EAS topology service range.
  • Step 2b EES determines EAS.
  • EES can determine the edge application instance that meets the user's request based on the information of the locally registered/online edge application instance, the UE location information, and at least one of the EAS discovery filter parameters provided by the user. If multiple edge application instances are satisfied, multiple edge application instances can be returned.
  • Step 2c EES sends the information of EAS discovered by EES to EEC.
  • EES can send an EAS discovery response (EAS discovery response) to EEC, and the EAS discovery response includes the information of EAS discovered by EES.
  • EAS discovery response EAS discovery response
  • the EAS information may include at least one of the following: EAS address information, EAS identification information, or EAS endpoint information.
  • the EAS endpoint information may include at least one of the following: EAS uniform resource identifier (URI), fully qualified domain name (FQDN), or Internet protocol (IP) address.
  • URI EAS uniform resource identifier
  • FQDN fully qualified domain name
  • IP Internet protocol
  • the EAS information may be carried in an EAS profile.
  • the EEC may provide the acquired EAS information to the application client, so that the application client can connect to the edge application instance.
  • a key issue is how to select the same EAS for a group of UEs. For example, for gaming applications, different users can team up to play games. Selecting the same application server for a group of UEs can ensure the fairness of the game and reduce the synchronization signaling overhead between servers.
  • multiple UEs included in a group are located in the same EDN or multiple UEs included in a group are connected to an EES of an EDN.
  • a UE in the group can send the EAS selected by the UE and the information of the group (the UE list included in the group, or the Group ID of the group) to at least one EES in the EDN. Therefore, when other UEs in the group are connected to the EES in the EDN, they can learn the EAS selected by the UE from the EES to which they are connected, and then they can connect to the same EAS.
  • EDN-1 may include UE-1, UE-2, EES-1 and EES-2.
  • UE-1 may include UE-1, UE-2, EES-1 and EES-2.
  • Figure 4 a method for UE-1 and UE-2 to select the same EAS may be shown in Figure 4, and the process may include the following steps 401 to 412.
  • Step 401 EEC-1 determines to trigger the EAS discovery process.
  • the EAS discovery process may be triggered by EEC-1, or AC-1 may trigger EEC-1 to perform the EAS discovery process.
  • EEC-1 may be an edge enabling server in UE-1
  • AC-1 may be an application client in UE-1
  • actions performed by EEC-1 or AC-1 may be considered to be performed by UE-1.
  • Step 402 EEC-1 requests EES-1 to discover EAS.
  • EEC-1 can send an EAS discovery request (EAS discovery request) to EES-1 to request the discovery of EAS.
  • EAS discovery request EAS discovery request
  • the EAS discovery request may include at least one of UE ID, AC profile, or group information.
  • UE ID is the identifier of UE-1
  • AC profile may be the configuration information of AC-1
  • group information is the information of the group to which UE-1 belongs.
  • Step 403 EES-1 sends the EAS discovered by EES-1 to EEC-1.
  • EES-1 can send an EAS discovery response to EEC-1 to carry the information of the EAS discovered by EES-1.
  • the EAS discovery response may include information of at least one EAS, where the information of the at least one EAS is determined by EES-1.
  • Step 404 EEC-1 determines the EAS to be used (which may be referred to as EAS-1).
  • the EEC-1 may determine an EAS to be used from among the at least one EAS.
  • Step 405 EEC-1 sends the EAS (ie, EAS-1) that EEC-1 determines to use to EES-1.
  • EEC-1 may indicate to EES-1 the EAS it has determined to use via a selected EAS announcement request.
  • Step 406 EES-1 sends a success or failure indication to EEC-1.
  • Step 407 EES-1 determines that other EESs need to know the common EAS (common EAS).
  • a common EAS refers to an EAS to which a group of UEs can be connected together.
  • a common EAS may also be referred to as a shared EAS, shared EAS, etc. are explained here in a unified manner.
  • Step 408 EES-1 indicates to EES-2 that EAS-1 is the common EAS.
  • EES-1 can indicate to EES-2 that EAS-1 is the common EAS by an announce common EAS request message.
  • Step 409 EES-2 sends success or failure indication information to EES-1.
  • the success or failure indication information can be carried in the announce common EAS response.
  • Step 410 EEC-2 requests EES-2 to discover EAS.
  • EEC-2 may send an EAS discovery request to EES-2 to request discovery of the EAS.
  • Step 411 EES-2 checks whether the common EAS is available.
  • Step 412 EES-2 sends the EAS discovery result to EEC-2.
  • EEC-2 may send an EAS discovery response to EES-2.
  • the EAS discovery response may include information of the common EAS (ie, EAS-1).
  • a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple.
  • the words "first”, “second” and the like are used to distinguish the same items or similar items with substantially the same functions and effects.
  • the EEC and AC in the edge application network architecture are deployed in the UE, the EEC and AC in the same UE can be considered to be corresponding, the EEC and AC deployed in the same UE can be considered to be the same entity, and the EEC or AC and the UE to which it belongs are also considered to be the same entity.
  • This application provides a unified explanation here.
  • the EDN may have a deployment hierarchical relationship, such as province, city, district, county, town, etc., and a low-level EDN may be located in a high-level EDN.
  • the EDN in the embodiment of the present application may be indicated by parameters such as topological service area, geographic service area, DNAI, deployment level, etc., which are used to characterize the service area/service level, and are uniformly described here.
  • FIG5 shows a schematic diagram of the hierarchical relationship of an EDN, wherein the EDN may include EDN-1, EDN-2, EDN-3, EDN-4, and EDN-5.
  • EDN-1 may include UE-1 and EES-1
  • EDN-2 may include UE-2 and EES-2
  • EDN-1 and EDN-2 are at the same level.
  • EDN-1 and EDN-2 are both located in EDN-3, which is the upper level of EDN-1 and EDN-2, and EDN-3 may also include EES-3 and UE-3.
  • EDN-4 is at the same level as EDN-3, and EDN-4 may include UE-4 and EES-4.
  • EDN-3 and EDN-4 are both located in EDN-5, which is the upper level of EDN-3 and EDN-4, and EDN-5 may also include EES-5 and UE-5.
  • EDN-1 may be Haidian District
  • EDN-2 may be Chaoyang District
  • EDN-3 may be Beijing
  • EDN-4 may be Tianjin
  • FIG6 a method for obtaining edge computing services provided by the present application may be shown in FIG6.
  • the method may include The steps are as follows:
  • Step 600 The ECS determines an EES that provides services for a group of UEs in each EDN according to preconfigured rule information.
  • the ECS may determine a unique EES in the EES corresponding to each EDN, and the unique EES is used to provide edge computing services for a group of UEs.
  • the ECS may determine multiple EESs that can provide services for a group of UEs in the EES corresponding to each EDN.
  • the multiple EESs that can provide services for a group of UEs may negotiate to further determine a unique EES for providing edge computing services for a group of UEs.
  • each EDN After a unique EES that provides services for a group of UEs is determined in each EDN, when at least one UE needs to connect to an EES in the EDN, it will connect to the unique EES.
  • the unique EES used to provide edge computing services for a group of UEs can also be called a common EES in the EDN.
  • the common EES in EDN-1 may be EES-1
  • the common EES in EDN-2 may be EES-2
  • the common EES in EDN-3 may be EES-3
  • the common EES in EDN-4 may be EES-4.
  • the prerequisite for executing step 600 is that the EES has been registered with the ECS, or the information of the EES is pre-configured in the ECS, or the ECS can obtain the information of the EES through the network management system.
  • FIG. 7 shows a schematic diagram of a process of an ECS acquiring deployment information of an EES.
  • the process may include step 701 and step 702 .
  • Step 701 EES sends EES information to ECS.
  • the information of any EES sent by the EES to the ECS may include at least one of the following information: identification information of the EES, address information of the EES, endpoint information of the EES, EASID information of the service on the EES, provider identification of the EES, or deployment information corresponding to the EES.
  • the deployment information corresponding to the EES may include at least one of the following information: EDN information of the EES, the topological service scope of the EES, the geographical service scope of the EES, the DNAI corresponding to the EES, or the level to which the EES belongs.
  • the EDN information of the EES may include: at least one of the following: the EDN identifier, the topological service scope of the EDN, the connection information of the EDN (such as access point name (APN), data network name (DNN), or single network slice selection assistance information (s-nssai), etc.).
  • the EDN identifier such as access point name (APN), data network name (DNN), or single network slice selection assistance information (s-nssai), etc.
  • the EES endpoint information may include at least one of the following: an EES uniform resource identifier (URI), a fully qualified domain name (FQDN) of the EES, or an Internet protocol (IP) address of the EES, etc.
  • URI EES uniform resource identifier
  • FQDN fully qualified domain name
  • IP Internet protocol
  • the EES information may be carried in a registration request message.
  • other messages may also be used to carry the EES information, which is not limited in this application.
  • Step 702 The ECS sends an indication message indicating whether the registration is successful or failed to the EES.
  • the indication information indicating the success or failure of the registration can be carried in the EES registration response message.
  • other messages can also be used to carry the indication information indicating the success or failure of the registration, and this application does not limit this.
  • step 600 is optional and may not be performed.
  • the EEC may further instruct the ECS to select a common EES for each EDN.
  • Step 601 EEC-1 requests EES information from ECS.
  • EEC-1 may send a service configuration request message to ECS to request to obtain EES information.
  • ECS may send a service configuration request message to ECS to request to obtain EES information.
  • other messages may also be used to request to obtain EES information, which is not limited in this application.
  • EEC-1 may also send location information of UE-1 to ECS, and the location information of UE-1 may be used to enable ECS to determine information of EES corresponding to UE-1.
  • EEC-1 may also send EDN information or edge computing service level information expected by EEC-1 to ECS, and the EDN information or edge computing service level information expected by EEC-1 may also be used to enable ECS to determine the EES information corresponding to UE-1.
  • EEC-1 may also send information about AC-1 to ECS, and the information about AC-1 is used to enable ECS to determine information about EES corresponding to EEC-1.
  • the information about AC-1 may include at least one of the following information: an identifier (ACID) of AC-1, a type of AC-1, a key performance indicator (KPI) of a service required by AC-1, identification information of an EAS required by AC-1, or a service KPI of an EAS required by AC-1.
  • the information about AC-1 may be included in an AC profile.
  • EEC-1 is the edge enablement client in UE-1
  • AC-1 can be the application client in UE-1
  • AC-1, EEC-1 and UE-1 can be considered as the same entity. Therefore, the EDN information or the level information of edge computing services expected by EEC-1 can also be considered as The EDN information or edge computing service level information expected by UE-1 can be used to enable ECS to determine the EES information corresponding to UE-1.
  • the information of AC-1 can also be considered as the information of UE-1, so it can also be used to enable ECS to determine the EES information corresponding to UE-1.
  • the above-mentioned UE-1 location information, EDN information or edge computing service level information expected by EEC-1, and AC-1 information can be used in any combination to enable ECS to determine the EES information corresponding to UE-1. They can also be used alone to enable ECS to determine the EES information corresponding to UE-1.
  • EEC-1 may also send information of group 1 to ECS.
  • Group 1 is a UE grouping, which may include a group of UEs, and UE-1 may be a UE in group 1.
  • the information of group 1 may include at least one of a group ID and/or a UE list.
  • the above information may be carried in a service configuration request message and sent to the EC.
  • Step 602 ECS determines the EES corresponding to UE-1.
  • EES corresponding to UE-1 is also the EES corresponding to EEC-1 and AC-1, and they are described here uniformly.
  • the EES determined by ECS is the EES that can provide edge computing services for AC-1.
  • the ECS may determine the EDN corresponding to UE-1. Further, the ECS may determine the EES corresponding to UE-1 from the EDN corresponding to UE-1.
  • the method in which the ECS determines the EDN and EES corresponding to the UE-1 may specifically include at least one of the following:
  • the ECS may randomly select at least one EES from at least one EDN as the EES corresponding to UE-1.
  • ECS can determine the EDN and EES corresponding to UE-1 based on the received location information of UE-1.
  • ECS can determine at least one level of EDN where UE-1 is located or can be connected as the EDN corresponding to UE-1, and then determine the EES corresponding to EEC-1 in the EDN corresponding to UE-1.
  • UE-1 is located in EDN-1, so EES-1 can be the EES corresponding to UE-1.
  • UE-1 is also located in EDN-3, so EES-3 can also be the EES corresponding to UE-1.
  • UE-1 is also located in EDN-5, so EES-5 can also be the EES corresponding to UE-1.
  • ECS can also determine the EDN corresponding to UE-1 and the EES in the EDN based on the EDN information or the level information of the edge computing service expected by EEC-1.
  • the EDN expected to be used by EEC-1 is EDN-1 and EDN-3, or the level of the edge computing service expected by EEC-1 is 2 levels (ie, EDN-1 and EDN-3), so the EDN corresponding to EEC-1 determined by ECS is EDN-1 and EDN-3, and then the corresponding EES is determined in EDN-1 and EDN-3, such as EES-1 and EES-3.
  • each EDN uses a unique EES. If a certain EDN is the EDN corresponding to EEC-1, the corresponding EES determined by the ECS in the EDN is also the common EES in the EDN. Then, only one corresponding EES will be determined in each corresponding EDN.
  • Figure 5 of the present application is illustrated by taking each EDN including one EES as an example.
  • one EDN may include multiple EESs. If an EDN is an EDN corresponding to EEC-1, the number of corresponding EESs determined by the ECS for the EDN may be multiple. Thus, the number of corresponding EESs determined by the ECS may be greater than the number of corresponding EDNs determined.
  • the EES has been registered with the ECS, or the deployment information of the EES is pre-configured in the ECS, or the ECS can obtain the deployment information of the EES through the network management system. Therefore, after determining the EES corresponding to EEC-1, the ECS can determine the information of the EES corresponding to EEC-1.
  • the information of the EES in the embodiment of the present application may include at least one of the following information: identification information of the EES, address information of the EES, or at least one of corresponding deployment information of the EES.
  • the corresponding deployment information of the EES may include at least one of the following: EDN information of the EES, the topological service scope of the EES, the geographical service scope of the EES, the DNAI corresponding to the EES, or the level to which the EES belongs.
  • Step 603 The ECS sends information of at least one EES to EEC-1.
  • the information of the at least one EES is the information of the at least one EES corresponding to the UE-1 determined by the ECS.
  • the information of the at least one EES can refer to the description of the EES information in the above step 701, which will not be repeated here.
  • the information of the at least one EES may be carried in a service configuration response message.
  • other messages may also be used to carry the information of the EES, which is not limited in this application.
  • Step 604 EEC-1 selects EES.
  • EEC-1 can select the EES to be used from at least one EES determined by ECS.
  • the EES selected by EEC-1 can be used to determine the EAS that provides edge computing services for AC-1. It can also be understood that the EES selected by EEC-1 is the EES corresponding to the EAS that EEC-1 expects to use to provide edge computing services for AC-1.
  • EEC-1 selects EES, and the specific implementation is as follows:
  • EEC-1 may select an EES based on its desired EDN information or the level information of the edge computing service. For example, EEC-1 may select the EES closest to the UE or with the lowest level as the EES to be used.
  • EEC-1 can learn the positions of other UEs except UE in group 1, and then select the EES to be used according to the position relationship between UE-1 and other UEs. For example, EEC-1 can select an EES with an equal distance from other UEs as the EES to be used.
  • EEC-1 may not force the same group of UEs to connect to the same EAS, that is, to select the same EES.
  • a UE in the same group is far away from other UEs, and the effect of connecting to the same EAS is poor, so EEC-1 can determine that the UE connects to the EAS alone, that is, selects a separate EES.
  • the corresponding EES determined by the ECS in step 602 may include EES-1, EES-3, and EES-5.
  • EES-1 is located in Haidian
  • UE-4 is located in Tianjin
  • UE-1 and UE-4 are not in the same urban area
  • EEC-1 can determine that the two do not need to be connected to the same EAS
  • EEC-1 does not need to select an EES at the level of North China Urban Area (EES-3). Therefore, the EES that EEC-1 determines to be used may include EES-1 and EES-3.
  • EES selected by EEC-1 are EES-1 and EES-3, which are described uniformly here.
  • Step 605 EEC-1 requests EES-1 to discover EAS.
  • EEC-1 can request EES-1 to discover EAS through an EAS discovery request message.
  • EAS discovery request message can also be used to request to discover EAS, which is not limited in this application.
  • EEC-1 requests EES-1 to discover EAS, which may specifically include: EEC-1 requests EES-1 to discover EAS that provides edge computing services for AC-1.
  • EEC-1 may also send service information corresponding to AC-1 to EES-1, and the service information corresponding to AC-1 may be used to determine the EAS that can provide edge computing services for AC-1.
  • the service information corresponding to AC-1 sent by EEC-1 to EES-1 may be information about services required or requested by AC-1.
  • the service information corresponding to AC-1 may be carried in an EAS discovery request message or other messages sent by EEC-1 to EES-1, which is not limited in the present application.
  • the service information corresponding to AC-1 may include at least one of the following: an AC configuration file for matching EAS parameters, EAS features required by AC, an EAS identifier, or an EAS vendor identifier and other information.
  • EES-1 can determine the EAS that can provide edge computing services for AC-1 from the EAS managed on the EES-1 according to the service information corresponding to AC-1.
  • the EAS that provides edge computing services for AC-1 can be recorded as EAS-1.
  • EEC-1 requests EES-1 to discover EAS which may also include: EEC-1 requests EES-1 to discover the common EAS corresponding to group 1.
  • Group 1 is a UE group, group 1 may include multiple UEs, and UE-1 may be a UE in group 1.
  • the common EAS corresponding to group 1 refers to an EAS that can provide edge computing services for the UEs included in group 1.
  • EEC-1 may also send information of group 1 to EES-1, where the information of group 1 may indicate information of UEs included in group 1.
  • the information of group 1 may include information such as a group ID and/or a UE list.
  • the information of group 1 may be used to enable EES-1 to determine a common EAS for the UEs included in group 1.
  • the information of group 1 may be carried in an EAS discovery request message or other messages, which is not limited in the present application.
  • EES-1 can determine whether a common EAS corresponding to group 1 is maintained locally. If EES-1 maintains a common EAS corresponding to group 1 locally, EES-1 can send the common EAS corresponding to group 1 to EEC-1. For example, other UEs in group 1 except UE-1 have previously requested to discover and determined the common EAS corresponding to group 1. Thus, EES-1 can learn the common EAS corresponding to group 1 before step 605. Furthermore, after EES-1 receives the information of group 1 sent by EEC-1, EES-1 can send the previously learned common EAS corresponding to group 1 to EEC-1.
  • EES-1 does not locally maintain a common EAS corresponding to group 1, EES-1 needs to further determine a corresponding EAS for group 1.
  • the common EAS corresponding to group 1 can be determined in at least one EAS corresponding to at least one EES selected by EEC-1. Therefore, if EES-1 does not maintain the common EAS corresponding to group 1, it can further request other EESs to obtain or subscribe to the common EAS corresponding to group 1.
  • EEC-1 may also send information about at least one EES to EES-1.
  • the information about at least one EES sent by EEC-1 to EES-1 is information about other EESs other than EES-1 in at least one EES selected by EEC-1.
  • the EESs that EEC-1 determines to be used may include EES-1 and EES-3, but the EAS discovery request message sent by EEC-1 to EES-1
  • the candidate EES list in may include only the information of EES-3 but not the information of EES-1.
  • the information of the at least one EES can be used to instruct EES-1 to request at least one EES to obtain or subscribe to the common EAS corresponding to group 1.
  • EEC-1 can send the information of EES-3 to EES-1, thereby instructing EES-1 to subsequently request EES-3 to obtain or subscribe to the common EAS corresponding to group 1.
  • Step 606 EES-1 sends the information of the EAS discovered by EES-1 to EEC-1.
  • the information of the EAS discovered by the EES-1 is the information of the EAS that can provide edge computing services for AC-1.
  • the EAS discovered by the EES-1 is the EAS in EDN-1, and the EAS discovered by the EES-1 corresponds to the EES-1 and EDN-1.
  • all of the multiple EASs may be EASs in EDN-1, and all of the multiple EASs correspond to EES-1 and EDN-1.
  • step 606 may be followed by the following steps X, Y, and Z.
  • Step X EEC-1 selects an EAS to be used from the multiple EASs discovered by EES-1.
  • Step Y EEC-1 sends the EAS determined by EEC-1 to EES-1.
  • EEC-1 may indicate to EES-1 the EAS it has determined to use via a selected EAS announcement request.
  • Step Z EES-1 sends a success or failure indication to EEC-1.
  • the success or failure indication information can be carried in a selected EAS announcement response.
  • EEC- 1 may send information of at least one EES and/or information of group 1 to EES- 1 in step Y .
  • EEC-1 can determine the only EAS that provides edge computing services for AC-1. After that, EEC-1 can connect AC-1 to the EAS. For example, assuming that the EAS selected by EEC-1 to provide edge computing services for AC-1 is EAS-1, then EEC-1 can transmit the acquired information of EAS-1 to AC-1, so that AC-1 is connected to EAS-1.
  • the EAS information discovered by EES-1 may be carried in an EAS discovery response message and sent to EEC-1.
  • EES-1 EAS discovery response message
  • Step 607 EES-1 subscribes to the common EAS information corresponding to group 1 from EES-3.
  • EEC- 1 sends the information of group 1 and the information of EES- 3 to EES- 1 . Based on this, EES- 1 can request EES- 3 to obtain the common EAS corresponding to group 1 .
  • EES-1 can request EAS information from EES-3 by sending an announce common EAS subscription request message.
  • EES-1 may also send information of group 1 to EES-3, where the information of group 1 is used to instruct EES-3 to determine the common EAS corresponding to group 1.
  • the information of group 1 may be carried in a common EAS subscription request message or other messages, which is not limited in the present application.
  • EES-1 may also send service information corresponding to AC-1 to EES-3.
  • the service information corresponding to AC-1 may be used to assist in determining the common EAS corresponding to group 1.
  • the service information corresponding to AC-1 may make the common EAS corresponding to group 1 determined by EES-3 more suitable for the service scenario of AC-1.
  • the service information corresponding to AC-1 may refer to the description in step 605 and will not be repeated here.
  • Step 608 EES-3 sends a success or failure indication to EES-1.
  • EES-3 can indicate the subscription ID to EES-1.
  • EES-3 can indicate the reason for the failure to EES-1.
  • an indication of success or failure may be carried in an announce common EAS subscription response message.
  • group 1 may include UE-1, UE-2 and UE-3, and EEC-2 in UE-2 and EEC-3 in UE-3 may also perform steps similar to the above steps 601 to 608.
  • EEC-2 and EES-2 may perform the following steps:
  • Step 601a EEC-2 requests EES information from ECS.
  • ECS EES information from ECS.
  • Step 602a The ECS determines the EES corresponding to UE-2. For this step, refer to the description of step 602.
  • Step 603a ECS sends information of at least one EES to EEC-2.
  • ECS sends information of at least one EES to EEC-2.
  • Step 604a EEC-2 selects EES. For this step, please refer to the description of step 604.
  • the EES selected by EEC-2 may be the same as the EES selected by EEC-1.
  • Step 605a EEC-2 requests EES-2 to discover EAS. For this step, please refer to the description of step 605.
  • the EAS that EEC-2 requests EES-2 to discover is an EAS that can provide edge computing services for AC-2.
  • Step 606a EES-2 sends the information of the EAS discovered by EES-2 to EEC-2.
  • EES-2 sends the information of the EAS discovered by EES-2 to EEC-2.
  • Step 606a please refer to the description of step 606.
  • the information of the EAS discovered by EES-2 is the information of the EAS that can provide edge computing services for AC-2.
  • the EAS discovered by EES-2 is the EAS in EDN-2, and the EAS discovered by EES-2 corresponds to EES-2 and EDN-2.
  • Step 607a EES-2 requests EES-3 to subscribe to the common EAS corresponding to group 1. For this step, refer to the description of step 605.
  • Step 608a EES-3 sends a success or failure indication to EES-2.
  • EES-3 may receive the information of group 1 and/or the service information corresponding to AC-2.
  • EEC-3 and EES-3 may perform the following steps:
  • Step 601b EEC-3 requests EES information from ECS.
  • ECS EES information from ECS.
  • Step 602b ECS determines the EES corresponding to UE-3. For this step, refer to the description of step 603.
  • Step 603b ECS sends information of at least one EES to EEC-3.
  • ECS sends information of at least one EES to EEC-3.
  • Step 604b EEC-3 selects EES. For this step, please refer to the description of step 604.
  • the EES selected by EEC-3 may be the same as the EES selected by EEC-1.
  • Step 605b EEC-3 requests EES-3 to discover EAS.
  • EES-3 requests EES-3 to discover EAS.
  • the EAS that EEC-3 requests EES-3 to discover is an EAS that can provide edge computing services for AC-3.
  • Step 606b EES-3 sends the information of the EAS discovered by EES-3 to EEC-3.
  • EES-3 sends the information of the EAS discovered by EES-3 to EEC-3.
  • Step 606b please refer to the description of step 606.
  • the information of the EAS discovered by EES-3 is the information of the EAS that can provide edge computing services for AC-3.
  • the EAS discovered by EES-3 is the EAS in EDN-3, and the EAS discovered by EES-3 corresponds to EES-3 and EDN-3.
  • the highest-level EES selected by EEC-3 is EES-3, so EEC-3 does not need to send information of other EESs to EES-3, and EES-3 does not need to interact with other EESs, so that EES-3 can determine the common EAS corresponding to group 1 from EDN-3.
  • EES-3 may receive the information of group 1 and/or the service information corresponding to AC-3.
  • Step 609 EES-3 determines the common EAS corresponding to group 1.
  • EES-3 may determine the common EAS corresponding to group 1 based on the previously acquired information of group 1 and at least one of the service information corresponding to AC-1, AC-2, or AC-3.
  • EES-3 after receiving the information of group 1, EES-3 can first determine whether the local maintains the common EAS corresponding to group 1. If yes, directly feedback the common EAS corresponding to group 1 to EES-1. If not, EES-3 needs to further obtain the common EAS corresponding to group 1.
  • EES-3 can learn the common EAS corresponding to group 1 before step 605.
  • EES-3 can send the previously learned common EAS corresponding to group 1 to EES-1.
  • EES-3 does not locally maintain the common EAS corresponding to group 1. In this case, EES-3 needs to determine the common EAS corresponding to group 1 by itself.
  • EES-3 may determine the EAS determined for the AC in group 1 (eg, AC-1) as the common EAS for the UEs in group 1.
  • EES-3 can determine the EAS required for the services corresponding to AC-1 and AC-2 in at least one EAS corresponding to EES-3 based on the service information corresponding to AC-1 and AC-2.
  • This EAS can be considered as an EAS that can provide edge computing services for AC-1 and AC-2, and this EAS can be used as the common EAS for the UEs included in group 1.
  • the common EAS of group 1 can be EAS-3.
  • EES-3 can determine to send EAS-3 (directly or through other EES) to other UEs in the group based on the information of group 1. Therefore, when the UEs in the group obtain EAS information from EES-3, they can obtain the same EAS, so that multiple different UEs (actually ACs in UEs) can connect to the same EAS.
  • step 609 may be performed only when EES-3 receives service information corresponding to ACs in multiple UEs in group 1. If EES-3 only receives service information corresponding to ACs in one UE in group 1 (for example, only receives service information corresponding to AC-1), step 609 may not be performed. In this case, it is only necessary to determine EAS for AC-1, and there is no need to determine a common EAS for group 1.
  • EES-3 has received service information corresponding to AC in other UEs in group 1 before receiving service information corresponding to AC-1 (for example, it has previously received service information of AC-2), then when receiving service information corresponding to AC-1, a common EAS can be determined for group 1.
  • Step 610 EES-3 sends the common EAS information corresponding to group 1 to EES-1.
  • EES-3 may send information of EAS-3 to EES-1.
  • EES- 3 may also send information of group 1 to EES- 1 , and the information of group 1 may be sent together with information of a common EAS corresponding to group 1 , to indicate that EAS- 3 is the common EAS corresponding to group 1 .
  • EES-3 can feedback EAS information by announcing common EAS notification messages.
  • EES-3 may receive information of group 1 and/or information of AC-2 from EEC-2, then the method may further include: step 610a, EES-3 sends common EAS information corresponding to group 1 to EES-2, so that EES-2 further indicates the common EAS information corresponding to group 1 to EEC-2.
  • EES-3 may receive information of group 1 and/or AC-3 from EEC-3, then the method may further include: step 610b, EES-3 sends common EAS information corresponding to group 1 to EEC-3.
  • Step 611 EES-1 may trigger application context migration for EEC-1.
  • AC-1 can establish a connection with EAS-1 fed back by EES-1.
  • EES-1 can obtain EAS-3 sent by EES-3 to AC-1. Based on this, EES-1 can determine to switch the connection of AC-1 to EAS-3, so that EES-1 can trigger application context migration for AC-1.
  • AC-1 will receive the EAS information and AC can connect to the new EAS.
  • EEC-1 can determine multiple EESs that need to be used, and the multiple EESs can be located in different levels of EDN.
  • the multiple EESs that need to be used can be used to determine the EAS that provides edge computing services for AC-1. This method has good flexibility.
  • EEC-1 when EEC-1 receives an EAS at a higher level, EEC-1 can switch AC-1 to the EAS corresponding to the higher level EDN.
  • step 608 and step 610 may be combined for execution, that is, the common EAS information corresponding to group 1 may be sent together with the success or failure indication information, thereby saving signaling resources.
  • an EDN may include multiple available EESs.
  • EEC-1 requests multiple EESs in the same EDN to discover EAS
  • the multiple EESs may negotiate to determine a common EES.
  • the common EES may be used to discover EAS for EEC-1.
  • FIG. 8 a method for obtaining edge computing services provided in the present application may be shown in FIG. 8 , and the method may include the following steps:
  • Steps 800 to 810 may be the same as steps 600 to 610. The difference is that: 1.
  • EEC-1 may request EES-1 to discover EAS through an EAS discovery subscription request message. 2.
  • EES-1 sends the information of the EAS it discovered to EEC-1 through an EAS discovery subscription response message.
  • the advantage of using a subscription type message is that EES-1 can actively indicate information to EEC-1 later (for example, in the subsequent step 811).
  • Step 811 EES-1 sends the common EAS information corresponding to group 1 to EEC-1.
  • EES-1 can send the EAS information to EEC-1 via a discovery notification (EAS discovery notification) message.
  • EAS discovery notification EAS discovery notification
  • the information of the EAS discovered by EES-3 and sent in step 811 is the information of the common EAS corresponding to group 1 determined by EES-3, for example, the information of EAS-3.
  • Step 812 EES-1 triggers application context migration for AC-1, or EES-1 determines the EAS to be used.
  • AC-1 may also establish a connection with EAS-1 fed back by EES-1.
  • EEC-1 may receive EAS-3 indicated by EES-1 that can provide edge computing services for AC-1. Based on this, EEC-1 may determine to switch the connection of AC-1 to EAS-3, so that EEC-1 may trigger application context migration for AC-1.
  • EEC-1 may not instruct AC-1 to connect to the EAS-1. Instead, AC-1 is put in a waiting state. Subsequently, after step 811, EEC-1 may receive EAS-3 indicated by EES-1 that it can provide edge computing services for AC-1. In this case, EEC-1 may choose one of EAS-1 and EAS-3 to provide edge computing services for AC-1.
  • EEC-1 may set a timer, and EEC-1 may not connect to EAS during the running time of the timer, so that EEC-1 can receive the subsequently issued EAS information (such as EAS-3 information) during the waiting time.
  • EEC-1 directly determines an EAS to be used among multiple EASs, avoiding the process of switching after EEC-1 connects to EAS. This solution can reduce the switching of connections and the migration of application contexts to a certain extent, thereby reducing the signaling waste problem in the dynamic group scenario.
  • EEC-1 can instruct AC-1 to connect to EAS-1, and then EES-1 or EEC-1 can trigger the application context migration of AC-1.
  • step 806 and step 811 can be combined, that is, the information of EAS-3 discovered by EES-3 can be sent to EEC-1 together with the information of EAS-1 discovered by EES-1.
  • This implementation method can save signaling resources.
  • the method embodiment corresponding to FIG8 is similar to the method embodiment corresponding to FIG6 .
  • FIG. 9 a method for obtaining edge computing services provided by the present application may be shown in FIG. 9 , and the method may include the following:
  • Steps 900 to 904 may be the same as steps 600 to 604 .
  • Step 905 EEC-1 requests EES-1 to discover EAS.
  • EEC-1 can request EES-1 to discover EAS through an EAS discovery request message.
  • EAS discovery request message can also be used to request to discover EAS, which is not limited in this application.
  • EEC-1 may also send business information corresponding to AC-1 to EES-1, and the business information corresponding to AC-1 may be used to determine the EAS that can provide edge computing services for AC-1. This action may refer to the description in step 605, which will not be repeated here.
  • Step 906 EES-1 sends the information of the EAS discovered by EES-1 to EEC-1.
  • step 906 can be completely referred to in step 606, and will not be repeated here.
  • Step 907 EEC-1 subscribes to the common EAS information corresponding to group 1 from EES-1.
  • step 907 can be implemented through a common EAS information subscription request (common EAS information subscription request) message.
  • Step 908 EES-1 sends a success or failure indication to EEC.
  • step 908 can be implemented through a common EAS information subscription response (Common EAS information subscription response) message.
  • Steps 909 to 914 are the same as steps 607 to 612 and will not be described again here.
  • the method embodiment corresponding to Figure 9 does not reuse the messages in the existing EAS discovery process (such as EAS discovery subscription request message), but uses new messages (such as common EAS information subscription request message) to indicate the information of group 1 and the service information corresponding to AC-1 to EES-1.
  • This solution provides another implementation method for obtaining edge computing services, which improves the flexibility of the method of this application.
  • a method for obtaining edge computing services provided in the present application can be as shown in Figure 10, and the method can include the following steps 1000 to 1011.
  • Steps 1000 to 1006 may be the same as steps 600 to 606 .
  • step 1004 among the EES information determined by EEC-1, the highest level is EES-3.
  • Steps 1005 and 1006 may be the EAS discovery process of the prior art, and the description of steps 402 and 403 may be referred to for steps 1005 and 1006.
  • Step 1007 EEC-1 subscribes to the common EAS information corresponding to group 1 from EES-3.
  • step 1007 can be implemented through a common EAS information subscription request (Common EAS information subscription request) message.
  • EEC-1 may determine that the EES to be used is only EES-3, so that EEC-1 may directly request EES-3 to discover the EAS.
  • EEC-1 may send at least one of the information of group 1 and the service information corresponding to AC-1 to EES-3.
  • the content of the above information can refer to the description of the method embodiment corresponding to FIG6 above, which will not be repeated here.
  • Step 1008 EES-3 sends a success or failure indication to EEC-1.
  • EES-3 can indicate the subscription ID to EES-1.
  • EES-3 can indicate the reason for the failure to EES-1.
  • the success or failure indication information be carried in the (announce common EAS subscription response) message?
  • Steps 1009 to 1010 are the same as steps 609 to 610, and steps 1011 to 1012 are the same as steps 811 to 812, which will not be repeated here.
  • EEC-1 can directly send a request message to the highest-level EES in at least one EES to be used to obtain EAS information.
  • This method does not require step-by-step interaction between EESs of different levels, can simplify the complexity of the solution implementation, and can reduce the workload of EES.
  • FIG11 shows a schematic diagram of another hierarchical relationship of EDN, and FIG11 can refer to the relevant description of EDN in FIG5.
  • EDN-1 also includes EDN-0
  • EDN-0 is the next level of EDN-1
  • EDN-0 can include UE-0 and EES-0.
  • EDN-0 can be "Shangdi" Street, which belongs to the streets in Haidian District and belongs to the next level of Haidian District.
  • a method for obtaining edge computing services provided in the present application may be as shown in Figure 12, and the method may include the following steps 1200 to 1216.
  • Step 1200 The ECS determines an EES that provides services for a group of UEs in each EDN according to pre-configured rule information. Step 1200 is the same as step 600 and will not be described again.
  • Step 1201 EEC-0 requests EES information from ECS.
  • EEC-0 may send a service configuration request message to ECS to request to obtain EES information.
  • ECS service configuration request message
  • other messages may also be used to request to obtain EES information, which is not limited in this application.
  • This step can refer to the relevant description in step 601. You only need to replace EEC-1 with EEC-0, EES-1 with EES-0, and AC-1 with AC-0. No further details will be given here.
  • Step 1202 ECS determines the EES corresponding to UE-0.
  • This step may refer to the relevant description in step 602, and only requires replacing EEC-1 with EEC-0, EES-1 with EES-0, and AC-1 with AC-0, which will not be repeated here.
  • Step 1203 ECS sends information of at least one EES to EEC-0.
  • the information of the at least one EES may be carried in a service configuration response message.
  • other messages may also be used to carry the information of the EES, which is not limited in this application.
  • This step may refer to the relevant description in step 603, and only requires replacing EEC-1 with EEC-0, EES-1 with EES-0, and AC-1 with AC-0, which will not be repeated here.
  • Step 1204 EEC-0 selects EES.
  • This step may refer to the relevant description in step 604, and only requires replacing EEC-1 with EEC-0, EES-1 with EES-0, and AC-1 with AC-0, which will not be repeated here.
  • the EES required to be used determined by EEC-0 may include information of EES-0, EES-1 and EES-3.
  • Step 1205 EEC-0 requests EES-0 to discover EAS.
  • EEC-0 can request EES-0 to discover EAS through an EAS discovery request message.
  • EAS discovery request message can also be used to request to discover EAS, which is not limited in this application.
  • This step may refer to the relevant description in step 605, and only requires replacing EEC-1 with EEC-0, EES-1 with EES-0, and AC-1 with AC-0, which will not be repeated here.
  • the information of at least one EES sent by EEC-0 to EES-0 may include the information of EES-1 and EES-3, but need not include the information of EES-0.
  • Step 1206 EES-0 sends the information of the EAS discovered by EES-0 to EEC-0.
  • the EAS information discovered by EES-0 may be carried in an EAS discovery response message and sent to EEC-0.
  • EES-0 EAS discovery response message
  • This step may refer to the relevant description in step 606, and only requires replacing EEC-1 with EEC-0, EES-1 with EES-0, and AC-1 with AC-0, which will not be repeated here.
  • Step 1207 EES-0 determines to obtain the common EAS information corresponding to group 0.
  • EES-0 may receive the information of group 0 sent by EEC-0, where group 0 is the group where UE-0 is located. 0 can determine the corresponding common EAS for group 0. If EES-0 locally maintains the common EAS corresponding to group 0, EES-0 can directly feedback to EEC-0. If EES-0 locally maintains no common EAS corresponding to group 0, EES-0 needs to further obtain the common EAS corresponding to group 0 through other means.
  • EEC-0 may send information of EES-1 and EES-3 to EES-0, based on which EES-0 may determine to request EES-1 or EES-3 to obtain the common EAS corresponding to group 0.
  • EES-0 may determine to request EES-1 (which is lower in level than EES-3) to obtain the common EAS information corresponding to group 0 based on the hierarchical relationship between EES-1 and EES-3.
  • Step 1208 EES-0 subscribes to the common EAS information corresponding to group 0 from EES-1.
  • EES-0 may subscribe to EAS information from EES-1 by announcing a common EAS subscription request message.
  • This step can refer to the relevant description in step 607. You only need to replace EEC-1 with EEC-0, EES-1 with EES-0, EES-3 with EES-1, and AC-1 with AC-0. No further details will be given here.
  • EES-0 may send the information of EES-3 to EES-1 without sending the information of EES-1.
  • Step 1209 EES-1 sends a success or failure indication message to EES-0.
  • EES-3 can indicate the subscription ID to EES-1.
  • EES-3 can indicate the reason for the failure to EES-1.
  • an indication of success or failure may be carried in an announce common EAS subscription response message.
  • This step can refer to the relevant description in step 608. You only need to replace EEC-1 with EEC-0, EES-1 with EES-0, EES-3 with EES-1, and AC-1 with AC-0. No further details will be given here.
  • EES-0 can determine EAS-1 that can provide edge computing services for AC-0 based on the service information corresponding to AC-0 in the received announce common EAS subscription request message, and EAS-1 is associated with EES-1.
  • the announce common EAS subscription response message sent by EES-0 to EEC-0 can include information about EAS-1.
  • Step 1210 EES-1 determines to obtain the common EAS information corresponding to group 0.
  • the EAS discovery request message sent by EES-0 to EES-1 may include information about group 0, and EES-1 needs to determine the corresponding common EAS for group 0. If EES-1 locally maintains a common EAS corresponding to group 0, EES-1 can feedback to EEC-0. If EES-1 locally maintains a common EAS that does not correspond to group 0, EES-1 needs to further obtain the common EAS corresponding to group 0 through other means.
  • EES-1 may request EES-3 to obtain the common EAS corresponding to group 0.
  • Step 1211 EES-1 subscribes to the common EAS information corresponding to group 0 from EES-3.
  • Step 1212 EES-3 sends a success or failure indication to EES-1.
  • Step 1213 EES-3 determines the common EAS corresponding to group 0.
  • Step 1214 EES-3 sends the common EAS information corresponding to group 0 to EES-1.
  • Step 1211 to step 1214 are similar to step 607 to step 610, and the description of step 607 to step 610 may be referred to, and will not be repeated here.
  • step 1212 and step 1214 may be combined for execution, that is, the common EAS information corresponding to group 0 may be sent together with the success or failure indication information, thereby saving signaling resources.
  • Step 1215 EES-1 sends the common EAS information corresponding to group 0 to EES-0.
  • the information of the EAS discovered by EES-3 may be carried in a announce common EAS notification message and sent. Accordingly, EES-0 receives the announce common EAS notification message.
  • Step 1216 EES-0 triggers application context migration for EEC-0.
  • This step is similar to the above step 611 , and reference may be made to the description of EES-1 triggering EEC-1 application context migration in the embodiment corresponding to FIG6 , which will not be repeated here.
  • FIG. 12 The embodiment corresponding to the above-mentioned FIG. 12 is different from the embodiment corresponding to FIG. 6, FIG. 8, FIG. 9 or FIG. 10 in that there is one more level, thereby one more layer of EES interaction process.
  • the scheme shown in FIG. 12 is a process of interacting step by step from the low-level EES (EES-0) to the high-level EES (EES-3) to obtain EAS information.
  • a method for obtaining edge computing services provided in the present application can be shown in Figure 13, and the method can include the following steps 1300 to 1315.
  • Step 1300 to step 1306 are the same as step 1200 to step 1206, and reference may be made to the foregoing description.
  • Step 1307 EEC-0 subscribes to the common EAS information corresponding to group 0 from EES-1.
  • EEC-0 may subscribe to the common EAS information corresponding to group 0 from EES-1 through a common EAS subscription request message.
  • EEC- 0 may send information of group 0 to EES- 1 to request EES- 1 to discover the common EAS corresponding to group 0 .
  • EEC-0 may also send service information corresponding to AC-0 to EES-1, and the service information corresponding to AC-0 may also be used to determine the common EAS corresponding to group 0.
  • UE-0 can refer to the relevant description of UE-1
  • AC-0 can refer to the relevant description of AC-1
  • group 0 can refer to the relevant description of group 1, which will not be repeated here.
  • Step 1308 EES-1 sends a success or failure indication to EEC-0.
  • the indication information may also indicate the reason for the failure.
  • the success or failure indication information may be carried in a common EAS subscription response message.
  • Steps 1309 to 1315 are the same as steps 1210 to 1216, and reference may be made to the foregoing description.
  • the embodiment corresponding to FIG13 is different from the embodiment corresponding to FIG12 in that: in the embodiment corresponding to FIG12, EEC-0 first subscribes to the common EAS information corresponding to group 0 from EES-0, and then EES-0 subscribes to the common EAS information corresponding to group 0 step by step. In the embodiment corresponding to FIG13, EEC-0 directly subscribes to the common EAS information corresponding to group 0 from EES-1, and then EES-1 subscribes to the common EAS information corresponding to group 0 step by step. This solution is a possible implementation method.
  • FIG 14 a method for obtaining edge computing services provided in the present application can be shown in Figure 14, and the method can include the following steps 1400 to 1411.
  • Step 1400 to step 1406 are the same as step 1200 to step 1206, and reference may be made to the foregoing description.
  • Step 1407 EEC-0 subscribes to the common EAS information corresponding to group 0 from EES-1.
  • EEC-0 may request EES-1 to discover EAS by sending a common EAS subscription request message.
  • the common EAS subscription request message sent by EEC-0 to EES-1 may not include EES information.
  • the common EAS subscription request message sent by EEC-0 to EES-1 may include information of group 0 and/or service information corresponding to AC-0.
  • EEC-0 requests EES-1 to discover that the EAS is the common EAS corresponding to group 0.
  • the information of group 0 can refer to the relevant description of the information of group 1 above, and the service information corresponding to AC-0 can refer to the relevant description of the service information corresponding to AC-1 above, which will not be repeated here.
  • Step 1408 EES-1 sends the information of the common EAS corresponding to group 0 to EEC-0.
  • the information of the EAS discovered by EES-1 is carried in a common EAS subscription response message.
  • Step 1409 EEC-0 subscribes to the common EAS information corresponding to group 0 from EES-3.
  • EEC-0 may request EES-3 to discover EAS by sending a common EAS subscription request message.
  • Step 1409 is similar to step 1407 (just replace EES-3 with EES-1). Please refer to the previous description and will not be repeated here.
  • Step 1410 EES-3 sends the information of the common EAS corresponding to group 0 to EEC-0.
  • the information of the EAS discovered by the EES-3 is carried in a common EAS subscription response message.
  • Step 1411 EEC-0 selects the EAS used by AC-0 from the EAS determined by EES-3 and the EAS determined by EES-1.
  • EEC-0 may select the EAS corresponding to the EES at the highest level.
  • EEC-0 determines that the EES to be used may be EES-1 and EES-3. Moreover, EEC-0 can directly send a common EAS subscription request message to EES-1 and EES-3 without forwarding it step by step through other EES.
  • EEC-0 can select from multiple EASs. This method of directly interacting with the EES to be used is more efficient.
  • the present application provides a method for obtaining edge computing services as shown in FIG15.
  • the method can be applied to a first EEC.
  • the method may include the following steps:
  • Step 1501 A first EEC sends information of at least one EES to a first entity.
  • the first EEC may be an edge enabled client in the first UE, and the first EEC is located in the first UE.
  • the first UE may be UE-1, and the first EEC may be an EEC deployed in UE-1.
  • the first UE may be For UE-0, the first EEC may be an EEC deployed in UE-0.
  • the first entity may be a first EES
  • the first EES may provide edge computing services for the first EEC.
  • the first EEC may be EEC-1, and the first EES may be EES-1.
  • the first EEC may be EEC-0, and the first EES may be EES-0.
  • the first EEC may be EEC-0, and the first EES may be EES-1.
  • At least one EES sent by the first EEC to the first entity can provide edge computing services for the first EEC.
  • the first EEC may be EEC-1, the first EES may be EES-1, and the at least one EES may include EES-3.
  • the first EEC may be EEC-0, the first EES may be EES-0, and the at least one EES may include EES-1 and EES-3.
  • the first EEC may be EEC-0, the first EES may be EES-1, and the at least one EES may include EES-3.
  • the information of any one of the at least one EES may include at least one of the following information: identification information of the EES, address information of the EES, or deployment information corresponding to the EES.
  • the deployment information corresponding to the EES may include at least one of the following: EDN information of the EES, topological service scope of the EES, geographic service scope of the EES, DNAI corresponding to the EES, or the level to which the EES belongs.
  • the embodiment of the present application does not limit the type of message that carries the information of at least one EES.
  • the information of at least one EES can be carried in a discovery request message, a discovery subscription request message, or a common EAS information subscription request message.
  • the first EEC may be EEC-1, the first EES may be EES-1, and step 1501 may be performed in step 605.
  • the first EEC may be EEC-1, the first EES may be EES-1, and step 1501 may be performed in step 805.
  • the first EEC may be EEC-1, the first EES may be EES-1, and step 1501 may be performed in step 907.
  • the first EEC may be EEC-0, the first EES may be EES-0, and step 1501 may be performed in step 1205.
  • the first EEC may be EEC-0, the first EES may be EES-1, and step 1501 may be implemented through step 1307.
  • Step 1502 The first EEC receives information of at least one EAS from a first entity.
  • At least one EAS can provide edge computing services for the first AC.
  • the first AC corresponds to the first EEC, and the first AC and the first EEC can be deployed in the same UE.
  • the first EEC is an edge enabling server deployed in the first UE
  • the first AC is an application client deployed in the first UE
  • the first EEC, the first AC and the first UE can be considered to be the same entity.
  • At least one EAS corresponds to the first entity (ie, the first EES) and/or the at least one EES mentioned above.
  • the first EEC may be EEC-1
  • the first EES may be EES-1
  • at least one EES may be EES-3
  • at least one EAS received by EEC-1 may include EAS-1 and EAS-3; wherein EAS-1 corresponds to EES-1, and EAS-3 corresponds to EES-3.
  • step 1502 may be performed in step 606 and step 611.
  • step 1502 may be performed in step 806 and step 811.
  • step 1502 may be performed in step 908 and step 913.
  • the first EEC may be EEC-0
  • the first EES may be EES-0
  • the at least one EES may include EES-1 and EES-3
  • the at least one EAS received by EEC-0 may include EAS-0, EAS-1, and EAS-3; wherein EAS-0 corresponds to EES-0, EAS-1 corresponds to EES-1, and EAS-3 corresponds to EES-3.
  • step 1502 may be performed in steps 1206 and 1216.
  • the first EEC may be EEC-0
  • the first EES may be EES-1
  • the at least one EES may include EES-3
  • the at least one EAS received by EEC-0 may include EAS-1 and EAS-3; wherein EAS-1 corresponds to EES-1, and EAS-3 corresponds to EES-3.
  • step 1502 may be implemented through steps 1308 and 1315.
  • the first EEC may be EEC-1
  • the first EES may be EES-1
  • the content of the information of the at least one EAS may refer to the description in the above step 610, which will not be repeated here.
  • the first EEC receives information of at least one EAS, which may specifically include: the first EEC receives information of at least one EAS, and information of the first group corresponding to the first EAS in the at least one EAS.
  • the first EAS is used to provide edge computing services for the UEs included in the first group, that is, the first EAS is the common EAS corresponding to the first group.
  • the common EAS corresponding to the first group can be indicated by the first EES, and the first EEC can obtain the common EAS corresponding to the first group after executing step 1502.
  • the first UE may be UE-1
  • the first EEC may be EEC-1
  • the first EES may be EES-1
  • the first group may be group 1.
  • the at least one EAS message received by EEC-1 may include messages of EAS-1 and EAS-3.
  • EAS-3 is the EAS used by group 1
  • EAS-3 is the first EAS.
  • the method may further include:
  • Step 1503 The first EEC sends first service information to the first EES, where the first service information is used to determine at least one EAS.
  • the first service information is service information corresponding to the first AC, and the first AC is the AC corresponding to the first EEC.
  • Step 1504 The first EEC sends the first group of information to the first EES.
  • step 1503 and step 1504 may refer to the relevant description in the above step 605, which will not be repeated here.
  • the information of at least one EAS received by the first EEC does not include the first EAS associated with the information of the first group.
  • the information of the common EAS corresponding to the first group is not indicated by the first EES.
  • the method may further include: step 1505, the first EEC sends first service information to the first EES, the first service information is used to determine at least one EAS.
  • step 1505 is the same as step 1503, and will not be repeated here.
  • the method may further include: step 1506, the first EEC determines the first EAS in the at least one EES as the EAS for providing edge computing services for the UEs included in the first group. In other words, the first EEC determines the EAS used by the first group.
  • Step 1507 The first EEC sends the information of the first group and the information of the first EAS to the first EES. Step 1507 is to indicate to the first EES that the common EAS corresponding to the first group is the first EAS.
  • the first EEC after the first EEC receives at least one EAS that can provide edge computing services for the first AC, it can determine the common EAS (ie, the first EAS) that can correspond to the first group, and then notify the determined first EAS to other EES.
  • the common EAS ie, the first EAS
  • step 605 and step 607 do not include the information of group 1.
  • the first EAS may correspond to the first EES, and the information of the first EAS may be determined by the first EES.
  • the first EEC may be EEC-3 in UE-3
  • the first EES may be EES-3
  • the common EAS corresponding to the first group may be EAS-3 corresponding to EES-3.
  • the first EAS may also correspond to the second EES in at least one EES, and the second EES may provide edge computing services for the UE included in the first group.
  • the information of the first EAS may be received by the first EES from the second EES.
  • the first EES may be EES-1
  • the second EES may be EES-3
  • the EAS corresponding to the first group may be EAS-3
  • the EAS-3 may be sent to EES-1 by EES-3.
  • the information of the first EAS is received by the first EES from the second EES through the third EES, and the third EES is used to relay the communication between the first EES and the second EES.
  • the first EES may be EES-0
  • the second EES may be EES-3
  • the third EES may be EES-1
  • the EAS corresponding to the first group may be EAS-3
  • the EAS-3 may be forwarded to EES-0 by EES-3 through EES-1.
  • the present application provides a method for obtaining edge computing services as shown in FIG16.
  • the method can be applied to a first EES.
  • the method may include the following steps:
  • Step 1601 A first EES receives information of at least one EES from a second entity, where the information of the at least one EES is used to determine an EES that can provide edge computing services for the second entity.
  • the second entity may be the first EEC.
  • Step 1601 is an action corresponding to step 1501. For details of this step, please refer to the relevant description in step 1501 and will not be repeated here.
  • the method may further include: step 1602, the first EES obtains information of at least one edge application server EAS, and the at least one EAS can provide edge computing services for the first AC.
  • the information of the at least one EAS may be determined by the first EES and/or the at least one EES, and the at least one EAS corresponds to the first EES and/or the at least one EES.
  • the first EES may be EES-1
  • the information of the at least one EAS may include information of EAS-1 and EAS-3.
  • the method may further include: step 1603, the first EES sends information of at least one EAS to the first EEC.
  • This step may refer to the description of step 1502, which will not be repeated here.
  • the first EES sends information of at least one EAS to the first EEC, which may specifically include: the first EES sends information of at least one EAS and information of a first group associated with a first EAS in the at least one EAS to the first EEC.
  • the first EAS is used to provide edge computing services for the UEs included in the first group, that is, the first EAS is a common EAS corresponding to the first group.
  • the common EAS corresponding to the first group can be indicated to the first EEC by the first EES.
  • the method may further include:
  • Step 1604 The first EES receives first service information from the first EEC.
  • Step 1605 The first EES sends first service information to at least one EES.
  • Step 1606 The first EES receives the first group of information from the first EEC.
  • Step 1607 The first EES sends the first group of information of the first EEC to at least one EES.
  • the information of the first group and the first service information can refer to the previous description and will not be repeated here.
  • steps 1604 to 1607 may refer to the relevant description in the embodiment corresponding to FIG. 6 , which will not be repeated here.
  • the information of at least one EAS sent by the first EES does not include the first EAS associated with the information of the first group.
  • the first EES or other EESs have not yet determined the EAS used by the first group.
  • the method may further include:
  • Step 1608 The first EES receives first service information from the first EEC, where the first service information is used to determine at least one EAS.
  • Step 1609 The first EES sends first service information to at least one EES.
  • Step 1608 is the same as step 1604
  • step 1609 is the same as step 1605 . Please refer to the previous description.
  • the method may further include:
  • Step 1610 The first EES receives information of the first group from the first EEC and information of the first EAS, and the first EAS is used to provide edge computing services for UEs included in the first group.
  • Step 1611 The first EES sends the information of the first group and the information of the first EAS to at least one EES.
  • step 605 and step 607 do not include the information of group 1.
  • the present application provides a method for obtaining edge computing services as shown in FIG. 17 .
  • the method can be applied to the second EES.
  • the method may include the following steps:
  • Step 1701 The second EES receives information of a first group from a third entity, where the information of the first group is used to determine an EAS that provides edge computing services for UEs included in the first group.
  • the third entity may be the first EES.
  • the method also includes: step 1702, the second EES sends information of the first EAS to the first EES, and the first EAS is used to provide edge computing services for the UEs included in the first group.
  • the first EAS may be associated with the second EES.
  • the method may further include: step 1703, the second EES determines that the first EAS is used to provide edge computing services for the UEs included in the first group.
  • the first EAS capable of providing edge computing services for the UEs in the first group may be determined and sent by the second EES.
  • the first EAS may be determined by the first EEC.
  • the second EES receives information from the first group of the first EES, specifically including: the second EES receives information from the first group of the first EES and information from the first EAS.
  • the first EAS is used to provide edge computing services for the UEs included in the first group.
  • the second EES may be EES-3
  • the first EAS may be EAS-3.
  • the present application provides a method for obtaining edge computing services as shown in FIG. 18 .
  • the method can be applied to a first ECS.
  • the method may include the following steps:
  • Step 1801 The first ECS sends information of at least one EES to a fourth entity, where the at least one EES can provide edge computing services for the fourth entity.
  • the fourth entity is the first EEC.
  • the method may further include:
  • Step 1802 The first ECS receives at least one of the following information: location information of the first UE, EDN information expected by the first EEC, and information of the first AC from the first EEC, wherein the first EEC and the first AC are deployed in the first UE.
  • Step 1803 The first ECS determines information of at least one EES according to at least one of the location information of the first UE, the EDN information expected by the first EEC, and the information of the first AC.
  • the first ECS may be the ECS in FIG. 6
  • the first EEC may be the EES-1 in FIG. 6
  • the actions of the first ECS may refer to the relevant description of the actions performed by the ECS in the method embodiment corresponding to FIG. 6 , which will not be repeated here.
  • the present application provides a method for obtaining edge computing services as shown in FIG. 19 .
  • the method can be applied to the second EEC.
  • the method may include the following steps:
  • Step 1901 The second EEC sends information of the second group to the fourth EES, where the information of the second group is used to determine the EAS that provides edge computing services for the UEs included in the second group.
  • the second EEC may be an edge-enabled client deployed in a second UE, where the second UE is a UE in the second group.
  • the fourth EES is an EES directly subscribed by the second EEC.
  • the second EEC may be EEC-0
  • the fourth EES may be EES-1 or EES-3.
  • Step 1901 may be implemented through step 1407 or step 1409, and reference may be made to the relevant description in the embodiment corresponding to Figure 14, which will not be repeated here.
  • Step 1902 The second EEC receives information from the second EAS of the fourth EES, and the second EAS can provide edge computing services for the UEs included in the second group.
  • the second EEC may be EEC-0, and the fourth EES may be EES-1 or EES-3.
  • the second EAS may be EAS-1 or EAS-3, wherein EAS-1 is associated with EES-1, and EAS-3 is associated with EES-3.
  • Step 1901 may be implemented through step 1408 or step 1410, and reference may be made to the relevant description in the embodiment corresponding to FIG14 , which will not be repeated here.
  • step 1902 may be performed multiple times, so that the second EEC may acquire multiple EASs that can provide edge computing services for the UEs included in the second group. Furthermore, the second EEC may select one of the multiple EASs as a common EAS corresponding to the second group.
  • the method may further include: step 1903, the second EEC sends second service information to the fourth EES.
  • the second service information is service information corresponding to the second AC, and the second service information can refer to the related description of the first service information above, which is similar (just replace the second AC with the first AC), and will not be repeated here.
  • the second AC may be an application client deployed in the second UE, and the second AC, the second EEC, and the second UE may be considered to be the same entity.
  • the second service information can also be used to determine the EAS that provides edge computing services for the UEs included in the second group.
  • the fourth EES can refer to the second service information to make a determination, so that the determined second EAS can better meet the service requirements of the UEs included in the second group.
  • the second service information may refer to the relevant description of the service information corresponding to AC-1 in the method embodiment corresponding to FIG6 , and will not be described in detail here.
  • the method may further include:
  • Step 1904 The second EEC receives information about multiple EESs from the second ECS.
  • the information about multiple EESs may be information about available EESs determined by the second ECS for the second EEC.
  • step 1905 reference may be made to the relevant description of step 603, which will not be repeated here.
  • Step 1905 The second EEC determines the fourth EES.
  • the fourth EES may be the EES that the second EEC determines needs to use.
  • step 1905 reference may be made to the relevant description in step 604, which will not be repeated here.
  • interaction between the second ECS and the second EEC can refer to the interaction between the first ECS and the first EEC
  • the actions performed by the second ECS can refer to the actions performed by the first ECS, which will not be repeated here.
  • the present application provides a method for obtaining edge computing services as shown in Figure 20, which can be applied to the fourth EES.
  • the method may include the following steps:
  • Step 2001 The fourth EES receives the second group of information from the second EEC.
  • Step 2002 The fourth EES determines information of the second EAS based on the information of the second group, and the second EAS can provide edge computing services for the UEs included in the second group.
  • Step 2003 The fourth EES sends the information of the second EAS to the second EEC.
  • the information of the second group can refer to the relevant description of the information of group 1 in the embodiment corresponding to Figure 6, and the information of the second EAS can refer to the relevant description of the information of at least one EAS in the embodiment corresponding to Figure 6, which will not be repeated here.
  • the method may further include: step 2004, the fourth EES receives the second service information from the second EEC.
  • step 2002 may specifically be: the fourth EES determines the information of the second EAS according to the information of the second group and the second service information.
  • the second service information may refer to the relevant description of the service information corresponding to AC-1 in the embodiment corresponding to FIG6, which will not be repeated here.
  • FIG21 is a schematic diagram of the structure of a communication device 210 provided in the embodiment of the present application.
  • the communication device 210 includes One or more processors 2101, communication lines 2102, and at least one communication interface (FIG. 21 is merely an example of a communication interface 2103 and a processor 2101), and may optionally include a memory 2104.
  • Processor 2101 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 2102 may include a pathway for communication between different components.
  • the communication interface 2103 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 2103 may also be a transceiver circuit located in the processor 2101, for realizing signal input and signal output of the processor.
  • the memory 2104 may be a device with a storage function.
  • it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
  • the memory may exist independently and be connected to the processor through the communication line 2102. The memory may also be integrated with the processor.
  • the memory 2104 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 2101.
  • the processor 2101 is used to execute the computer-executable instructions stored in the memory 2104, thereby realizing the communication method provided in the embodiment of the present application.
  • the processor 2101 may also perform processing-related functions in the communication method provided in the following embodiments of the present application, and the communication interface 2103 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.
  • the processor 2101 may include one or more CPUs, such as CPU0 and CPU1 in Figure 21.
  • the communication device 210 may include multiple processors, such as the processor 2101 and the processor 2107 in FIG. 21. Each of these processors may be a single-core processor or a multi-core processor.
  • the processor here may include but is not limited to at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or an artificial intelligence processor and other types of computing devices running software, each of which may include one or more cores for executing software instructions to perform calculations or processing.
  • the communication device 210 may also include an output device 2105 and an input device 2106.
  • the output device 2105 communicates with the processor 2101 and can display information in a variety of ways.
  • the output device 2105 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
  • the input device 2106 communicates with the processor 2101 and can receive user input in a variety of ways.
  • the above-mentioned communication device 210 may sometimes also be referred to as a communication device, which may be a general device or a special device.
  • the communication device 210 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the above-mentioned terminal device, the above-mentioned network device, or a device with a similar structure in Figure 21.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of the communication device 210.
  • the action of the EEC can be performed by the processor 2101 in the communication device 210 shown in Figure 21 calling the application code stored in the memory 2104 to instruct the EEC to execute
  • the action of the EES can be performed by the processor 2101 in the communication device 210 shown in Figure 21 calling the application code stored in the memory 2104 to instruct the EES to execute
  • the action of the ECS can be performed by the processor 2101 in the communication device 210 shown in Figure 21 calling the application code stored in the memory 2104 to instruct the ECS to execute.
  • the present application embodiment also provides another communication device, which is used to implement the above-mentioned various methods.
  • the communication device can be a target node in the above-mentioned method embodiment, or a device including the above-mentioned target node, or a component that can be used for the target node. It is understandable that the communication device includes a hardware structure and/or software module corresponding to each function in order to realize the above-mentioned functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software.
  • the embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment.
  • each functional module can be divided according to each function, or two or more functions can be integrated into one processing module.
  • the above integrated module can be implemented in the form of hardware or in the form of software functional 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. There may be other division methods in actual implementation.
  • FIG22 shows a schematic diagram of the structure of a communication device 220.
  • the communication device 220 may include a transceiver module 2201.
  • the transceiver module 2201 which may also be referred to as a transceiver unit, is used to implement a transceiver function, and may be, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the communication device 220 may also include a processing module 2202.
  • the transceiver module 2201 can be used to send information of at least one EES to the first entity, and the at least one EES can provide edge computing services for the first EEC.
  • the transceiver module 2201 can be used to receive information of at least one EAS from the first entity, and the at least one EAS is associated with the first entity and/or at least one EES, and the at least one EAS can provide edge computing services for the first AC.
  • the transceiver module 2201 can also be used to send information of the first group to the first EES, and the information of the first group can be used to determine the EAS that provides edge computing services for the UE included in the first group.
  • the transceiver module 2201 can also be used to receive information of the first group, where the information of the first group is associated with a first EAS in at least one EAS, and the first EAS can provide edge computing services for the UEs included in the first group.
  • the processing module 2202 may also be used for the first EEC to determine a first EAS from at least one EAS, where the first EAS can provide edge computing services for the UEs included in the first group.
  • the transceiver module 2201 may also be configured to send information of the first EAS to the first EES.
  • the transceiver module 2201 may also be configured to send first service information to the first EES, where the first service information is used to determine at least one EAS.
  • the transceiver module 2201 may also be used to receive information of at least one EES from the first edge configuration server ECS.
  • the processing module 2202 may also be configured to determine information of at least one EES to be sent to the first entity according to information of at least one EES received from the first ECS.
  • the transceiver module 2201 can be used to receive information of at least one EES from the second entity, and the information of the at least one EES is used to determine the EES that can provide edge computing services for the second entity.
  • the transceiver module 2201 can also be used to send information of at least one EAS to the first EEC, and the at least one EAS can provide edge computing services for the first AC.
  • the transceiver module 2201 may also be used to receive information of a first group from a first EEC, where the information of the first group is used to indicate information of user equipment UE included in the first group.
  • the transceiver module 2201 may also be configured to send the first group of information to at least one EES.
  • the transceiver module 2201 can also be used to send information of a first group associated with a first EAS to the first EEC, where the first EAS is one EAS among at least one EAS, and the first EAS can provide edge computing services for UEs included in the first group.
  • the transceiver module 2201 can also be used to receive information of a first EAS from a first EEC, where the first EAS belongs to at least one EAS and can provide edge computing services for UEs included in the first group.
  • the transceiver module 2201 may also be configured to send information of the first EAS to at least one EES.
  • the transceiver module 2201 may also be used to receive first service information from a first EEC, where the first service information is used to determine at least one EAS.
  • the transceiver module 2201 may also be configured to send the first service information to at least one EES.
  • the transceiver module 2201 can be used to receive information of the first group from a third entity, and the information of the first group can be used to determine the EAS that provides edge computing services for the UE included in the first group.
  • the transceiver module 2201 can also be used to send information of the first EAS to the first EES, and the first EAS can provide edge computing services for the UEs included in the first group.
  • the transceiver module 2201 can also be used to receive information from a first EAS of the first EES, and the first EAS can provide edge computing services for the UEs included in the first group.
  • the transceiver module 2201 may also be used to receive first service information from a first EES, where the first service information is used to determine the first EAS.
  • the transceiver module 2201 can be used to send information of at least one EES to the fourth entity, and the at least one EES can provide edge computing services for the fourth entity.
  • the transceiver module 2201 may also be used to receive location information of a first UE from a first EEC, where the location information of the first UE is used to determine information of at least one EES.
  • the transceiver module 2201 may also be used to receive EDN information, edge computing service level information, or EES service level information expected by the first UE from the first EEC.
  • the EDN information, edge computing service level information, or EES service level information expected by the first UE is used to determine information of at least one EES.
  • the processing module 2202 may be configured to determine an EDN available to the first UE according to the location information of the first UE. Also, the processing module 2202 may be configured to determine information of multiple EESs from the EDN available to the first UE according to the policy information.
  • the EEC, EES, or ECS in the embodiments of the present application may also be referred to as a communication device, which may be a general device or a dedicated device, and the embodiments of the present application do not specifically limit this.
  • the communication device 220 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above functions.
  • the communication device 220 can take the form of the communication device 210 shown in Figure 21.
  • the processor 2101 in the communication device 210 shown in FIG. 21 may call computer-executable instructions stored in the memory 2104 to enable the communication device 210 to execute the communication method in the above method embodiment.
  • the functions/implementation process of the transceiver module 2201 and the processing module 2202 in FIG22 can be implemented by the processor 2101 in the communication device 210 shown in FIG21 calling the computer execution instructions stored in the memory 2104.
  • the functions/implementation process of the transceiver module 2201 in FIG22 can be implemented by the communication interface 2103 in the communication device 210 shown in FIG21
  • the functions/implementation process of the processing module 2202 in FIG22 can be implemented by the processor 2101 in the communication device 210 shown in FIG21 calling the computer execution instructions stored in the memory 2104.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be 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 distributed on multiple network units. Some or all of the units may 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, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof.
  • all or part of the embodiments may be implemented in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method.
  • 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, data center, etc. that includes one or more available media integrated therein.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a DVD
  • a semiconductor medium e.g., a solid-state drive (SSD)
  • a component can be, but is not limited to: a process running on a processor, a processor, an object, an executable file, a thread in execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can both be components.
  • One or more components can exist in a process and/or thread in execution, and a component can be located in a computer and/or distributed between two or more computers. In addition, these components can be executed from various computer-readable media with various data structures thereon.
  • These components can communicate in a local and/or remote process manner, such as according to a signal with one or more data packets (for example, data from a component, which interacts with another component in a local system, a distributed system, and/or interacts with other systems in a signal manner through a network such as the Internet).
  • data packets for example, data from a component, which interacts with another component in a local system, a distributed system, and/or interacts with other systems in a signal manner through a network such as the Internet.
  • the present application presents various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and/or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. In addition, combinations of these schemes may also be used.
  • the word “exemplary” is used to indicate an example, illustration or description. Any embodiment or design described as “exemplary” in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the word “exemplary” is used to present concepts in a concrete way.
  • information, signal, message, and channel can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are consistent. “Of,” “corresponding,” and “corresponding” can sometimes be used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are consistent. “System” and “network” can sometimes be used interchangeably. When the distinction between them is not emphasized, the meanings they intend to express are consistent. For example, "communication network” also refers to "communication system.”
  • the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application.
  • a person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

Landscapes

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

Abstract

本申请提供了一种获取边缘计算服务的方法、通信系统及装置，应用于通信技术领域。该获取边缘计算服务的方法包括：第一EEC向第一EES发送至少一个EES的信息，至少一个EES能够为第一EEC提供边缘计算服务。第一EEC接收来自第一EES的至少一个EAS的信息，至少一个EAS与第一EES和/或至少一个EES关联，至少一个EAS能够为第一AC提供边缘计算服务。基于该方法，第一AC可以灵活地获取边缘计算服务。

Description

一种获取边缘计算服务的方法、通信系统及装置
本申请要求于2022年11月07日提交国家知识产权局、申请号为202211385370.2、申请名称为“一种获取边缘计算服务的方法、通信系统及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种获取边缘计算服务的方法、通信系统及装置。
背景技术
现有标准规定的边缘(EDGE)应用架构中，用户设备(user equipment，UE)侧的边缘使能客户端(edge enabler client，EEC)通过边缘配置服务器(edge configuration server，ECS)发现边缘数据网络(edge data network，EDN)中的边缘使能服务器(edge enabler server，EES)。进一步，EEC可以通过该EES发现边缘应用服务器(edge application server，EAS)。进而，UE侧的应用客户端(application client，AC)可以与该EAS建立连接，从该EAS中获取业务数据。
但是，目前发现EAS的方式还不够灵活，难以适用于复杂的网络架构中。
发明内容
本申请提供了一种获取边缘计算服务的方法、通信系统及装置，用于解决现有技术中EAS的发现方式不够灵活的问题。
为达到上述目的，本申请采用如下技术方案：
第一方面，提供了一种获取边缘计算服务的方法，该方法可以应用于第一EEC，该方法可以包括：第一EEC可以向第一实体发送至少一个EES的信息，至少一个EES能够为第一EEC提供边缘计算服务。以及，第一EEC还可以接收来自第一实体的至少一个EAS的信息，至少一个EAS与至少一个EES对应，至少一个EAS能够为第一AC提供边缘计算服务。基于该方案，第一EEC可以获取到至少一个能够为第一AC提供边缘计算服务的EAS，从而可以使得第一EEC在至少一个EAS中选择用于为第一AC提供边缘计算服务的EAS。该方法可以提高EEC选择EAS的灵活性。
结合上述第一方面，在一种可能的实现方式中，第一实体可以为第一EES。
结合上述第一方面，在一种可能的实现方式中，第一EEC是部署在第一UE中的边缘使能服务器，第一AC是部署在第一UE中的应用客户端，第一EEC、第一AC和第一UE可以认为是同一主体。其中，可以称第一AC与第一EEC是对应的。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC向第一EES发送第一组的信息，第一组的信息可以用于确定为第一组包括的UE提供边缘计算服务的EAS。基于此，本申请的方案还可以用于为一组UE确定共同的EAS。
结合上述第一方面，在一种可能的实现方式中，第一组可以包括上述第一UE。
结合上述第一方面，在一种可能的实现方式中，第一组的信息包括组标识和/或UE列表。其中，UE列表即是第一组包括的UE的列表。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC接收第一组的信息，第一组的信息与至少一个EAS中的第一EAS关联。其中，第一EAS能够为第一组包括的UE提供边缘计算服务。
结合上述第一方面，在一种可能的实现方式中，第一EAS的信息和第一组的信息可以是一起接收的，以体现第一EAS与第一组的对应关系，从而使得第一EEC可以获知该第一EAS能够为第一组包括的UE提供边缘计算服务。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC根据第一EAS与第一组的对应关系，将第一EAS确定为能够为第一AC提供边缘计算服务的EAS。
结合上述第一方面，在一种可能的实现方式中，第一EAS与至少一个EES中的第二EES对应，第二EES能够为所述第一组包括的UE提供边缘计算服务。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC将至少一个EAS中的 第一EAS，确定为能够为第一组包括的UE提供边缘计算服务的EAS。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC向第一EES发送第一EAS的信息。
结合上述第一方面，在一种可能的实现方式中，第一EEC可以将其确定的第一EAS的信息和第一组的信息一同发送给第一EES。该实现方式可以体现第一EAS与第一组的对应关系，进而使得第一EES获知该第一EAS能够为第一组包括的UE提供边缘计算服务。
结合上述第一方面，在一种可能的实现方式中，第一EAS与第一EES对应，第一EAS是注册在第一EES上的EAS。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC可以向第一EES发送第一业务信息，第一业务信息用于确定至少一个EAS。
结合上述第一方面，在一种可能的实现方式中，第一业务信息为第一AC对应的业务信息。
结合上述第一方面，在一种可能的实现方式中，至少一个EES的信息中任一个EES的信息可以包括以下至少一项：EES的标识信息、EES的地址信息、或者EES对应的部署信息。
结合上述第一方面，在一种可能的实现方式中，EES对应的部署信息可以包括以下至少一项：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI、或EES所属的层级。
结合上述第一方面，在一种可能的实现方式中，至少一个EAS的信息中的任一个EAS的信息可以包括以下至少一项：EAS的地址信息、EAS的标识信息、或EAS的端点信息。
结合上述第一方面，在一种可能的实现方式中，EAS的端点信息可以包括以下至少一项：EAS URI、FQDN、或者IP地址。
结合上述第一方面，在一种可能的实现方式中，该方法还包括：第一EEC向第一ECS发送第一UE的位置信息，第一EEC和第一AC部署在第一UE中。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC接收来自第一ECS的至少一个EES的信息。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC根据其从第一ECS接收到的至少一个EES的信息，确定其向第一实体发送的至少一个EES的信息。示例地，第一EEC从第一ECS接收到的至少一个EES的信息可以记作m个EES的信息，第一EEC向第一EES发送的至少一个EES的信息可以记作n个EES的信息。从而，该n个EES的信息是从m个EES的信息中确定出来的。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC可以向第一ECS发送第一UE的位置信息。其中，第一EEC和第一AC部署在该第一UE中。该第一UE的位置信息可以用于使第一ECS确定出至少一个EES的信息。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC也可以向第一ECS发送第一UE期望的EDN信息、边缘计算服务层级信息或者EES服务层级信息。该第一UE期望的EDN信息、边缘计算服务层级信息或者EES服务层级信息也可以用于使第一ECS确定出至少一个EES的信息。
结合上述第一方面，在一种可能的实现方式中，该方法还可以包括：第一EEC也可以向第一ECS发送第一组的信息，第一组的信息可以用于确定至少一个EES的信息。
第二方面，提供了一种获取边缘计算服务的方法，该方法可以应用于第一EES，该方法可以包括：第一边缘使能服务器EES接收来自第二实体的至少一个EES的信息，至少一个EES的信息用于确定能够为第二实体提供边缘计算服务的EES。
结合上述第二方面，在一种可能的实现方式中，第二实体为第一EEC。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES获取至少一个EAS的信息，至少一个EAS能够为第一AC提供边缘计算服务。
结合上述第一方面，在一种可能的实现方式中，第一EEC是部署在第一UE中的边缘使能服务器，第一AC是部署在第一UE中的应用客户端，第一EEC、第一AC和第一UE可以认为是同一主体。并且，可以称第一AC与第一EEC是对应的。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES向第一EEC发送至少一个EAS的信息。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES接收来自第一EEC的第一组的信息，第一组的信息用于指示第一组包括的UE的信息。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES向至少一个EES发送第一组的信息。
结合上述第二方面，在一种可能的实现方式中，第一组的信息包括组标识和/或UE列表。
结合上述第二方面，在一种可能的实现方式中，第一组中可以包括第一EEC和第一AC所在的第一UE。
结合上述第二方面，在一种可能的实现方式中，该方法还包括：第一EES向第一EEC发送第一EAS关联的第一组的信息，第一EAS为至少一个EAS中的一个EAS，第一EAS能够为第一组包括的UE提供边缘计算服务。
结合上述第二方面，在一种可能的实现方式中，第一EAS可以与第一EES对应，第一EAS的信息可以是第一EES确定的。
结合上述第二方面，在一种可能的实现方式中，第一EAS可以与至少一个EES中的第二EES对应，第二EES能够为第一组包括的UE提供边缘计算服务。其中，第一EAS的信息可以是第一EES从第二EES接收到的。或者，第一EAS的信息是第一EES通过第三EES从第二EES接收到的，第三EES用于中继第一EES与第二EES的通信。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES接收来自第一EEC的第一EAS的信息，第一EAS属于至少一个EAS，第一EAS能够为第一组包括的UE提供边缘计算服务。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES向至少一个EES发送第一EAS的信息。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES接收来自第一EEC的第一业务信息，第一业务信息用于确定至少一个EAS。
结合上述第二方面，在一种可能的实现方式中，该方法还可以包括：第一EES向至少一个EES发送第一业务信息。
结合上述第二方面，在一种可能的实现方式中，至少一个EES的信息中任一个EES的信息可以包括以下至少一项：EES的标识信息、EES的地址信息、或者EES对应的部署信息。
结合上述第二方面，在一种可能的实现方式中，EES对应的部署信息可以包括以下至少一项：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI、或EES所属的层级。
结合上述第二方面，在一种可能的实现方式中，至少一个EAS的信息中的任一个EAS的信息包括以下至少一项：EAS的地址信息、EAS标识信息、或EAS端点信息。
结合上述第二方面，在一种可能的实现方式中，EAS的端点信息可以包括以下至少一项：EAS URI、FQDN、或者IP地址。
第三方面，提供了一种获取边缘计算服务的方法，该方法可以应用于第二EES，该方法可以包括：第二EES接收来自第三实体的第一组的信息，第一组的信息可以用于确定为第一组包括的UE提供边缘计算服务的EAS。
结合上述第三方面，在一种可能的实现方式中，第三实体为第一EES。
结合上述第三方面，在一种可能的实现方式中，该方法还可以包括：第二EES向第一EES发送第一EAS的信息，第一EAS用于为第一组包括的UE提供边缘计算服务。
结合上述第三方面，在一种可能的实现方式中，第一组的信息是第二EES通过第三EES接收到的。该方法还可以包括：第二EES通过第三EES向第一EES发送第一EAS的信息，第一EAS用于为第一组包括的UE提供边缘计算服务。
结合上述第三方面，在一种可能的实现方式中，第一EAS与第二EES对应，第一EAS的信息是第二EES确定的。
基于上述两种实现方式，第一EAS的信息可以是第二EES确定并下发给第一EES的。
结合上述第三方面，在一种可能的实现方式中，该方法还可以包括：第二EES接收来自第一EES的第一EAS的信息，第一EAS能够为第一组包括的UE提供边缘计算服务。基于该方案，第一EAS的信息可以是第二EES从第一EES接收到的。
结合上述第三方面，在一种可能的实现方式中，第一EAS的信息和第一组的信息可以是第二EES一起接收到的，使得第二EES获知第一EAS能够为第一组包括的UE提供边缘计算服务。
结合上述第三方面，在一种可能的实现方式中，该方法还可以包括：第二EES接收来自第一EES的 第一业务信息，第一业务信息用于确定第一EAS。
结合上述第三方面，在一种可能的实现方式中，第一EAS的信息可以包括以下至少一项：第一EAS的地址信息、第一EAS的标识信息、或第一EAS的端点信息。
结合上述第三方面，在一种可能的实现方式中，第一EAS的端点信息可以包括以下至少一项：EAS URI、FQDN、或者IP地址。
第四方面，提供了一种获取边缘计算服务的方法，该方法可以应用于第一ECS，该方法可以包括：第一ECS向第四实体发送至少一个EES的信息，至少一个EES能够为第四实体提供边缘计算服务。
结合上述第四方面，在一种可能的实现方式中，第四实体为第一EEC。
结合上述第四方面，在一种可能的实现方式中，至少一个EES的信息中任一个EES的信息可以包括以下至少一项：EES的标识信息、EES的地址信息、或者EES对应的部署信息。
结合上述第四方面，在一种可能的实现方式中，EES对应的部署信息包括以下至少一项：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI、或EES所属的层级。
结合上述第四方面，在一种可能的实现方式中，该方法还可以包括：第一ECS接收来自第一EEC的第一UE的位置信息，第一UE的位置信息用于确定至少一个EES的信息。
结合上述第四方面，在一种可能的实现方式中，该方法还可以包括：第一ECS接收来自第一EEC的第一UE期望的EDN信息、边缘计算服务层级信息或者EES服务层级信息，第一UE期望的EDN信息、边缘计算服务层级信息或者EES服务层级信息用于确定至少一个EES的信息。
结合上述第四方面，在一种可能的实现方式中，第一ECS根据第一UE的位置信息确定多个EES的信息，具体可以包括：第一ECS根据第一UE的位置信息确定第一UE可用的EDN。进而，第一ECS可以根据策略信息，从第一UE可用的EDN中确定多个EES的信息。
结合上述第四方面，在一种可能的实现方式中，该方法还可以包括：第一ECS根据第一AC的信息确定至少一个EES信息。
结合上述第四方面，在一种可能的实现方式中，第一AC的信息可以包括以下至少一项：第一AC的标识，第一AC的类型，第一AC所需的服务KPI，第一AC所需EAS的标识信息，或第一AC所需EAS的服务KPI。
结合上述第四方面，在一种可能的实现方式中，该方法还可以包括：第一ECS接收来自第一EEC的第一组的信息，第一组的信息可以用于确定至少一个EES的信息。
第五方面，提供了一种获取边缘计算服务的方法，该方法可以应用于第二EEC，该方法可以包括：第二EEC向第四EES发送第二组的信息，第二组的信息用于确定为第二组包括的UE提供边缘计算服务的EAS。第二EEC接收来自第四EES的第二EAS的信息，第二EAS能够为第二组包括的UE提供边缘计算服务。
结合上述第五方面，在一种可能的实现方式中，该方法还可以包括：第二EEC向至少一个EES发送第二业务信息，第二业务信息也可以用于确定为第二组包括的UE提供边缘计算服务的EAS。
结合上述第五方面，在一种可能的实现方式中，第二EAS与第四EES对应，第二EAS的信息是第四EES确定的。
结合上述第五方面，在一种可能的实现方式中，第二EEC是部署在第二UE中的边缘使能服务器，第二AC是部署在第二UE中的应用客户端，第二EEC、第二AC和第二UE可以认为是同一主体。并且，可以称第二AC与第二EEC是对应的。
结合上述第五方面，在一种可能的实现方式中，第二组可以包括第二UE。
第六方面，提供了一种获取边缘计算服务的方法，该方法可以应用于第四EES，该方法可以包括：第四EES接收来自第二EEC的第二组的信息，第二组的信息用于指示第二组包括的UE的信息。第四EES向第二EEC发送第二EAS的信息，第二EAS能够为第二组包括的UE提供边缘计算服务。
结合上述第六方面，在一种可能的实现方式中，该方法还可以包括：第四EES接收来自第二EEC的第二业务信息，第二业务信息可以用于确定第二EAS。
结合上述第六方面，在一种可能的实现方式中，第二EAS与第四EES对应，第二EAS的信息是第四EES确定的。
结合上述第六方面，在一种可能的实现方式中，第二EEC是部署在第二UE中的边缘使能服务器，第二AC是部署在第二UE中的应用客户端，第二EEC、第二AC和第二UE可以认为是同一主体。并且， 可以称第二AC与第二EEC是对应的。
结合上述第六方面，在一种可能的实现方式中，第二组可以包括第二UE。
第七方面，提供了一种通信装置用于实现上述方法。该通信装置可以为上述第一方面的第一EEC，或者可以为上述第二方面的第一EES，或者可以为上述第三方面的第二EES，或者可以为上述第四方面的第一ECS，或者为上述第五方面的第二EEC，或者为上述第六方面的第四EES。该通信装置可以包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
一种可能的实现方式中，该通信装置包括处理模块和收发模块，该收发模块用于执行上述第一方面、第二方面、第三方面、第四方面、第五方面、第六方面或第七方面的方法中，由通信装置侧进行消息接收和发送的操作；该处理模块用于调用指令，执行上述第一方面、第二方面、第三方面、第四方面、第五方面、第六方面或第七方面的方法中，由通信装置侧进行的消息处理或控制操作。
第八方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中存储的计算机指令之后，根据该指令执行如上述第一方面、第二方面、第三方面、第四方面、第五方面、第六方面或第七方面所述的方法。
在一种可能的实现方式中，通信装置还包括存储器；该存储器用于存储计算机指令。
在一种可能的实现方式中，通信装置还包括通信接口；该通信接口用于该通信装置与其它设备进行通信。示例性的，该通信接口可以为收发器、输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。
在一种可能的实现方式中，该通信装置可以是芯片或芯片系统。其中，当该通信装置是芯片系统时，该通信装置可以由芯片构成，也可以包含芯片和其他分立器件。
在一种可能的实现方式中，当通信装置为芯片或芯片系统时，上述通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。上述处理器也可以体现为处理电路或逻辑电路。
第九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面、第二方面、第三方面、第四方面、第五方面、第六方面或第七方面所述的方法。
第十方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面、第二方面、第三方面、第四方面、第五方面、第六方面或第七方面所述的方法。
第十一方面，提供一种通信系统，该通信系统包括执行上述第一方面所述的获取边缘计算服务的方法的第一EEC和执行上述第二方面所述的获取边缘计算服务的方法的第一EES。
在一种可能的实现方式中，该通信系统还可以包括执行上述第三方面所述的获取边缘计算服务的方法的第二EES。
在一种可能的实现方式中，该通信系统还可以包括执行上述第四方面所述的获取边缘计算服务的方法的第一ECS。
其中，第七方面至第十一方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面、第二方面、第三方面、第四方面、第五方面、第六方面或第七方面中不同实现方式所带来的技术效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种边缘应用架构及功能模型的结构示意图；
图2为本申请实施例提供的一种EES平台的发现和EAS的发现流程的示意图；
图3为本申请实施例提供的一种边缘网络的结构示意图；
图4为本申请实施例提供的一种发现和确定EAS的流程图；
图5为本申请实施例提供的一种EDN的层级关系的示意图；
图6为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图7为本申请实施例提供的一种ECS获取EES的部署信息的流程示意图；
图8为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图9为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图10为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图11为本申请实施例提供的一种另一种EDN的层级关系的示意图；
图12为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图13为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图14为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图15为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图16为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图17为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图18为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图19为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图20为本申请实施例提供的一种获取边缘计算服务的方法的流程示意图；
图21为本申请实施例提供的一种通信装置的结构示意图；
图22为本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
介绍本申请实施例之前，对本申请涉及的技术术语以及相关技术进行解释说明。需要说明的是，下述解释说明是为了让本申请实施例更容易被理解，而不应该视为对本申请实施例所要求的保护范围的限定。
目前，3GPP SA6正在进行应用使能的移动边缘计算(mobile edge computing，MEC)的研究，定义了一种边缘(EDGE)应用架构及功能模型可以如图1所示，其中的功能实体的介绍如下：
边缘数据网络(EDN):一种通用的理解，EDN只对应一个数据网络，是一个特别的本地数据网络(local data network)，包含边缘使能功能，可以使用数据网络接入标识符(data network access identifier，DNAI)和数据网络名称(data network name，DNN)标识，是网络逻辑概念。另一种EDN的理解，EDN是中心云的对等概念，可以理解为是一个本地的数据中心(地理位置概念)，可以使用DNAI来标识，可以包含多个本地数据网络。EDN可以用于提供边缘业务服务，部署在边缘数据网络中的应用称为应用实例或边缘应用。应用实例或边缘应用可以是一个应用(例如，社交媒体软件、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR))部署运行在EDN的实例(instance)。
边缘应用服务器(EAS)：EAS部署在EDN中，用于承载应用部署运行在EDN的实例。一个应用可在一个或多个EDN中部署一个或多个EAS，部署运行在不同的EDN中的EAS可以认为是一个应用的不同的EAS，它们可以共享一个域名，可以使用一个IP地址，也可以使用不同的IP地址。EAS也可以称为边缘应用(服务器)、应用实例、边缘应用实例、MEC应用(服务器)、EAS功能等。
边缘使能服务器(EES)：EES部署在EDN中，可以为EDN中的应用实例提供一些使能能力。EES可以支持应用实例的注册、对UE的认证和鉴权，为UE提供应用实例的IP地址信息等。EES还可以进一步支持获取应用实例的标识和IP地址信息，并进一步向应用实例的标识和IP地址信息发送给ECS。一般情况下，EAS注册到一个EES上，或者，通过管理系统将一个EAS的信息配置在一个EES上，该EES称为该EAS关联的EES。EES可以用于控制、管理注册或配置该EES关联的EAS。
应用程序客户端(AC):应用程序客户端是应用在终端侧的客户端程序。应用用户(user)可以使用应用程序客户端从应用服务器获取应用业务。应用程序客户端可以连接到云上的应用服务器以获取应用业务，也可以连接到部署运行在一个或多个EDN中的EAS以获取应用业务。应用程序客户端部署在UE中，可以认为是EAS在UE侧的对等实体。
边缘使能服务器(EEC)：EEC用于向EES注册EEC的信息及应用客户端的信息、执行安全认证和鉴权、从EES获取EAS的IP地址、向应用客户端提供边缘计算使能能力，如EAS发现服务将EAS的IP地址返回给应用客户端。EEC部署在UE中，可以认为是EES在UE侧的对等实体。
边缘配置服务器(ECS)：负责EDN的配置，如向UE提供EES的信息。还可以直接向UE提供应用实例的信息，以及和应用的DNS交互获取应用实例的信息。进一步从其他功能实体获取并保存应用实例和IP地址的信息。
基于上述EDGE应用架构，应用用户可以通过登录UE上的AC，通过AC与EAS建立连接以进行通信，从而获取应用服务。
参考图1所示的EDGE应用架构，由于边缘使能客户端部署在UE中，因此其他设备与边缘使能客户端的交互，也可以视为其他设备与UE的交互。因而，本申请对于消息交互等的描述中，边缘使能客户端 也可以替换为UE。在本申请实施例中，如无特说明，边缘使能客户端与UE可替换。
本申请实施例对边缘使能客户端、边缘数据网络、边缘配置服务器、边缘应用服务器，以及边缘使能服务器的具体名称不作限制。例如，在5G通信系统中，边缘使能客户端可以是EEC。在未来的通信系统(如6G通信系统)中，边缘使能客户端也可以具有其它名称。为方便说明，本申请以边缘使能客户端可以是EEC，边缘数据网络可以是EDN，边缘配置服务器可以是ECS，边缘应用服务器可以是EAS，边缘使能服务器可以是EES为例。即本申请后续所描述的EEC均可替换为边缘使能客户端，EDN均可替换为边缘数据网络，ECS均可替换为边缘配置服务器，EAS均可替换为边缘应用服务器，EES均可替换为边缘使能服务器。
基于上述EDGE应用架构的应用上下文迁移流程，主要可以包括可以以下四个阶段：
(1)应用上下文迁移的检测：即判断可能需要进行上下文迁移，此时多由检测实体检测到一些事件，例如UE位置变化，或UE用户面路径发生更新等。
(2)应用上下文迁移的决策：决策实体确定需要进行上下文迁移。
(3)应用上下文迁移的执行：主要是将应用的上下文从源EAS传送从目标EAS。还可以进一步包含通知终端目标EAS的信息，通知网络上下文迁移完成和目标EAS的相关信息(如目标EAS的地址，目标EAS对应的路由信息等)。
在应用上下文迁移后，应用客户端可以将连接切换至目标EAS。
(4)应用上下文迁移后的清理工作：涉及到多个实体，在应用客户端的连接切换之后，源EAS相关的实体可以清理/释放应用上下文。
3GPP SA6标准中定义了EES平台的发现和EAS的发现流程，架构和功能上设计使用两级发现机制：先从ECS发现EES，然后从EES发现EAS。图2示出了本申请提供的一种EES平台的发现和EAS的发现流程的示意图，其中，步骤1a至步骤1c为终端侧EEC从ECS发现EES的流程，步骤2a至步骤2c为EEC从EES发现EAS的流程。
终端侧EEC从ECS发现EES：
步骤1a、EEC向ECS发送请求消息以请求订阅UE可用的EES。
可选地，该请求消息可以携带EEC标识信息，安全凭证，AC配置文件(profile)，UE标识(identifier，ID)，UE位置信息等信息。其中AC配置文件可以包括以下信息的至少一项：AC标识(ACID)，AC类型，预期的AC地理服务区域，可以为AC提供服务的EAS的EASID，期望的AC服务关键性能指标(key performance indicator，KPI)，AC所需的最小服务KPI。
本申请实施例中，EEC和AC是部署在UE中的实体，EEC、AC、UE所做的动作可以认为是同一个执行主体。部署在同一个UE中的EEC和AC可以认为是“对应的”。EEC对应的AC则是指与EEC部署在同一个UE中的AC或者是EEC与该AC有连接或者是EEC为该AC提供服务。在此统一说明，下文不再赘述。
从而，EEC向ECS请求订阅EES，可以认为是EEC在向ESC请求订阅EEC可用的EES，或者是EEC在向ESC请求订阅EEC对应的AC可用的EES。
步骤1b、ECS确定UE可用的EES的信息。
可选地，ECS可以根据AC配置文件，UE位置信息，边缘计算服务提供商(edge computing service provider，ECSP)策略信息等信息中的至少一项确定UE可用的EES的信息。
可选地，ECS确定出的UE可用的EES可以包括至少一个，从而，该UE可用的EES的信息可以包括EES列表(list)，EES list中可以包括至少一个EES的标识。
可选地，每个EES的信息具体可以包括以下至少一项信息：EES的标识信息、EES的地址信息、EES的端点信息、EES上服务的EASID信息、EES的提供商标识、EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI。
步骤1c、ECS向EEC返回EES的信息。
可选地，ECS还可以向EEC返回EES的EDN信息。
EEC从EES发现EAS：
步骤2a、EEC向EES请求发现EAS。作为一种实现方式，EEC可以向EES发送EAS发现请求(EAS discovery request)，以请求EES发现EAS。
可选地，该EAS发现请求可以包括以下信息中的至少一项：UE标识，EEC标识，EAS发现过滤器， 或UE位置信息。其中，EAS发现过滤器可以包括AC配置文件，EAS特征信息等信息。EAS特征信息又可以包括以下至少一项信息：EASID，EAS提供者ID，EAS类型，EAS地理服务范围，或EAS拓扑服务范围。
步骤2b、EES确定EAS。
EES可以根据本地注册/上线的边缘应用实例的信息，UE位置信息用户提供的EAS发现过滤参数中的至少一项，确定满足用户请求的边缘应用实例。如果多个都满足，则可以返回多个边缘应用实例。
步骤2c、EES向EEC发送EES发现的EAS的信息。
作为一种实现方式，EES可以向EEC发送EAS发现响应(EAS discovery response)，该EAS发现响应包括EES发现的EAS的信息。
可选地，EAS的信息可以包括以下至少一项：EAS的地址信息、EAS的标识信息、或EAS端点信息。其中，EAS的端点信息可以包括以下至少一项：EAS统一资源标识符(uniform resource identifier，URI)、完全限定域名(fully qualified domain name，FQDN)、或者网际协议(internet protocol，IP)地址。作为一种可能的实现方式，EAS的信息可以携带在EAS配置文件(EAS profile)中。
可选地，EEC可以将获取到的EAS的信息提供给应用客户端，用于应用客户端连接到该边缘应用实例。
在SA6边缘应用的研究中，有一个关键问题是，如何为一组UE选择同一个EAS。例如，对于游戏类应用，不同的用户可以组队打游戏，对于一组的UE选择同一个应用服务器，可以保证游戏的公平性，并且可以减少服务器之间的同步信令开销。
一种可能的情况，一个组包括的多个UE均位于同一个EDN中或一个组包括的多个UE均连接至一个EDN的EES。此种情况下，该组中的某个UE在选择EAS后，可以向EDN中的至少一个EES发送该UE选择的EAS，以及该组的信息(该组包括的UE list，或者该组的Group ID)。从而，当该组中的其他UE连接至该EDN中的EES时，可以从其连接的EES上获知该UE所选择的EAS，进而可以连接到相同的EAS上。
示例地，如图3所示，EDN-1中可以包括UE-1、UE-2、EES-1以及EES-2。以图3的场景为例，UE-1和UE-2选择同一个EAS的一种方法可以如图4所示，该流程可以包括如下步骤401至步骤412。
步骤401、EEC-1确定触发EAS发现流程。
可选地，可以由EEC-1触发EAS发现流程，也可以由AC-1触发EEC-1执行EAS发现流程。
可选地，EEC-1可以为UE-1中的边缘使能服务器，AC-1可以为UE-1中的应用客户端，EEC-1或AC-1执行的动作可以认为是UE-1执行的。
步骤402、EEC-1向EES-1请求发现EAS。
作为一种实现方式，EEC-1可以向EES-1发送EAS发现请求(EAS discovery request)，以请求发现EAS。
可选地，该EAS发现请求中可以包括UE ID、AC配置文件(profile)、或组(group)信息中的至少一项。其中，UE ID为UE-1的标识，AC profile可以为AC-1的配置信息，group信息为UE-1所在的组的信息。
步骤403、EES-1向EEC-1发送EES-1发现的EAS。
作为一种实现方式，EES-1可以向EEC-1发送EAS发现响应(EAS discovery response)，以携带EES-1发现的EAS的信息。
可选地，该EAS发现响应可以包括至少一个EAS的信息，该至少一个EAS的信息是由EES-1确定的。
步骤404、EEC-1确定需要使用的EAS(可以记作EAS-1)。
EEC-1可以在至少一个EAS中确定需要使用的EAS。
步骤405、EEC-1向EES-1发送EEC-1确定使用的EAS(即EAS-1)。
可选的，EEC-1可以通过选定的EAS公告请求(selected EAS announcement request)向EES-1指示其确定使用的EAS。
步骤406、EES-1向EEC-1发送成功或失败的指示信息。
步骤407、EES-1确定其他EES需要获知共同的EAS(common EAS)。
共同的EAS是指一组UE可以共同连接的EAS。本申请实施例中，共同的EAS也可以称为共用的 EAS、共享的EAS等，在此统一说明。
步骤408、EES-1向EES-2指示EAS-1为共同的EAS。
作为一种实现方式，EES-1可以通过宣布共同EAS请求(announce common EAS request)消息来向EES-2指示EAS-1为共同的EAS。
步骤409、EES-2向EES-1发送成功或者失败的指示信息。
作为一种实现方式，该成功或者失败的指示信息可以承载在宣布共同EAS响应(announce common EAS response)中。
步骤410、EEC-2向EES-2请求发现EAS。
作为一种实现方式，EEC-2可以向EES-2发送EAS发现请求，以请求发现EAS。
步骤411、EES-2检查共同EAS是否可用。
步骤412、EES-2向EEC-2发送EAS发现结果。
作为一种实现方式，EEC-2可以向EES-2发送EAS发现响应。该EAS发现响应中可以包括共同的EAS(即EAS-1)的信息。
不过，图4对应的方案仅适用于一组UE位于同一个EDN中的情况，对于同一组UE位于不同的EDN的情况则不适用。另外，EES在EDN内部广播EAS的信息会造成大量的信令浪费，并且还会占用通信资源。如何使不同的EDN中的UE选择到同一个EAS，是目前尚未解决的问题。
鉴于此，提供了本申请实施例的技术方案。下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
下述实施例均可以基于图1所示的边缘应用架构实现。本申请各实施例之间涉及的动作，术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。
另外，由于边缘应用网络架构中的EEC和AC是部署在UE中的，因此同一UE中的EEC和AC可以认为是对应的，部署在同一UE中的EEC和AC可以认为是同一主体，EEC或AC与其所属的UE也认为是同一主体，本申请在此统一说明。
本申请实施例中，EDN可以具备部署层级关系，例如省、市、区、县、镇等，低层级的EDN可以位于高层级的EDN中。本申请实施例中的EDN可以通过拓扑服务范围(service area)、地理服务范围、DNAI、部署层级等用于表征服务范围/服务层级的参数来指示，在此统一说明。
图5示出了一种EDN的层级关系的示意图，其中的EDN可以包括EDN-1、EDN-2、EDN-3、EDN-4和EDN-5。其中，EDN-1中可以包括UE-1和EES-1，EDN-2中可以包括UE-2和EES-2，EDN-1和EDN-2是同一层级的。EDN-1和EDN-2均位于EDN-3中，EDN-3是EDN-1和EDN-2的上一层级，EDN-3还可以包括EES-3和UE-3。EDN-4与EDN-3是同一层级的，EDN-4可以包括UE-4和EES-4。EDN-3和EDN-4均位于EDN-5中，EDN-5是EDN-3和EDN-4的上一层级，EDN-5还可以包括EES-5和UE-5。示例性的，EDN-1可以为海淀区、EDN-2可以为朝阳区、EDN-3可以为北京市、EDN-4可以为天津市，EDN-5可以为华北地区，海淀区和朝阳区可以为同一层级，北京市可以为海淀区和朝阳区的上一层级，北京市和天津市可以是同一层级，华北地区可以为北京市和天津市的上一层级。
以图5的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图6所示，该方法可以包 括如下步骤：
步骤600、ECS根据预配置的规则信息，在每个EDN中确定出为一组UE提供服务的EES。
作为一种可能的实现方式，ECS可以在每个EDN对应的EES中确定出唯一一个EES，该唯一的EES用于为一组UE提供边缘计算服务。
作为另一种可能的实现方式，ECS可以在每个EDN对应的EES中确定出多个能够为一组UE提供服务的EES。此种情况下，该多个能够为一组UE提供服务的EES可以进行协商，进一步确定出唯一一个用于为一组UE提供边缘计算服务的EES。
在每个EDN中确定出唯一一个为一组UE提供服务的唯一的EES之后，至少一个UE需要连接至该EDN中的EES时，都会连接到该唯一的EES上。该唯一用于为一组UE提供边缘计算服务的EES，也可以称为EDN中共同的EES。
示例地，以图5为例，EDN-1中共同EES可以为EES-1，EDN-2中共同的EES可以为EES-2，EDN-3中共同的EES可以为EES-3，EDN-4中共同的EES可以为EES-4。
步骤600执行的前提是：EES已经注册到ECS上，或者，EES的信息预配置在ECS中，或者ECS可以通过网络管理系统获取EES的信息。
示例地，图7示出了ECS获取EES的部署信息的一种情况的流程示意图，该流程可以包括步骤701和步骤702。
步骤701、EES向ECS发送EES的信息。
可选地，EES向ECS发送的任一个EES的信息可以包括以下至少一项信息：EES的标识信息、EES的地址信息、EES的端点信息、EES上服务的EASID信息、EES的提供商标识、或者EES对应的部署信息。
可选地，EES对应的部署信息可以包括以下至少一项信息：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI、或EES所属的层级。
可选地，EES的EDN信息可以包括：EDN的标识、EDN的拓扑服务范围、EDN的连接信息(例如接入点名称(access point name，APN)、数据网络名称(data network name，DNN)、或单网络切片选择辅助信息(single network slice selection assistance information，s-nssai)等)中的至少一项。
可选地，EES端点信息可以包括以下至少一项：EES统一资源标识符(uniform resource identifier，URI)，EES的完全限定域名(fully qualified domain name，FQDN)，或EES的网际协议(internet protocol，IP)地址等。
作为一种可能的实现方式，EES的信息可以承载在注册请求消息中。当然，也可以使用其他的消息携带EES的信息，本申请对此不作限定。
步骤702、ECS向EES发送指示注册成功或失败的指示信息。
作为一种可能的实现方式，该指示注册成功或失败的指示信息可以承载在EES注册响应消息中。当然，也可以使用其他的消息携带指示注册成功或失败的指示信息，本申请对此不作限定。
需要说明的是，步骤600是可选地，也可以不执行步骤600。
可选地，在步骤600之前，EEC还可以指示ECS需要针对每个EDN选择一个共同的EES。
步骤601、EEC-1向ECS请求EES的信息。
作为一种可能的实现方式，EEC-1可以向ECS发送服务配置请求消息来请求获取EES的信息。当然，也可以使用其他的消息来请求获取EES的信息，本申请对此不作限定。
可选地，EEC-1还可以向ECS发送UE-1的位置信息，UE-1的位置信息可以用于使ECS确定UE-1对应的EES的信息。
可选地，EEC-1还可以向ECS发送EEC-1期望的EDN信息或边缘计算服务的层级信息，该EEC-1期望的EDN信息或边缘计算服务的层级信息也可以用于使ECS确定UE-1对应的EES的信息。
可选地，EEC-1还可以向ECS发送AC-1的信息，AC-1的信息用于使ECS确定EEC-1对应的EES的信息。AC-1的信息可以包括以下至少一项信息：AC-1的标识(ACID)，AC-1的类型，AC-1所需的服务关键性能指标(key performance indicator，KPI)，AC-1所需EAS的标识信息，或AC-1所需EAS的服务KPI。作为一种可能的实现方式，AC-1的信息可以包括在AC profile中。
应理解，EEC-1为UE-1中的边缘使能客户端，AC-1可以为UE-1中的应用客户端，AC-1、EEC-1以及UE-1可以认为是同一主体。从而，EEC-1期望的EDN信息或边缘计算服务的层级信息，也可以认为是 UE-1期望的EDN信息或边缘计算服务的层级信息，从而可以用于使ECS来确定UE-1对应的EES的信息。另外，AC-1的信息也可以认为是UE-1的信息，从而也可以用于使ECS来确定UE-1对应的EES的信息。
可选地，上述UE-1的位置信息、EEC-1期望的EDN信息或边缘计算服务的层级信息、以及AC-1的信息可以任意组合使用，用于使ECS来确定UE-1对应的EES的信息。也可以单独使用，用于使ECS来确定UE-1对应的EES的信息。
可选地，EEC-1还可以向ECS发送组1的信息。组1是一个UE分组，组1中可以包括一组UE，该UE-1可以是组1中的UE。其中，组1的信息可以包括组标识(group ID)和/或UE列表等信息中的至少一项。
可选地，上述信息可以承载在服务配置请求消息中发送给EC。
步骤602、ECS确定UE-1对应的EES。
AC-1、EEC-1以及UE-1是同一主体，因此，UE-1对应的EES，也是EEC-1和AC-1对应的EES，在此统一说明。ECS确定的EES是能够为AC-1提供边缘计算服务的EES。
首先，ECS可以确定UE-1对应的EDN。进一步地，ECS可以在UE-1对应的EDN中确定UE-1对应的EES。
可选地，ECS确定UE-1对应的EDN以及EES的方法，具体可以包括以下至少一种：
方法一：ECS可以随机在至少一个EDN中选择至少一个EES，作为UE-1对应的EES。
方法二：ECS可以根据接收到的UE-1的位置信息，来确定UE-1对应的EDN以及EES。作为一种可能的实现方式，ECS可以将UE-1位于的或可以连接的至少一个层级的EDN确定为UE-1对应的EDN，进而在UE-1对应的EDN中的中确定EEC-1对应的EES。例如，以图5为例，UE-1位于EDN-1，从而EES-1可以是UE-1对应的EES。UE-1也位于EDN-3中，从而EES-3也可以是UE-1对应的EES。UE-1也位于EDN-5中，从而EES-5也可以是UE-1对应的EES。
方法三：ECS还可以根据EEC-1期望的EDN信息或边缘计算服务的层级信息，来确定UE-1对应的EDN和EDN中的EES。比如，EEC-1期望使用的EDN为EDN-1和EDN-3，或者EEC-1期望的边缘计算服务的层级为2个层级(即EDN-1和EDN-3)，从而ECS确定的EEC-1对应的EDN为EDN-1和EDN-3，进而在EDN-1和EDN-3中确定对应的EES，例如EES-1和EES-3。
可选地，在上述步骤600执行的情况下，每个EDN使用唯一的一个EES。若某EDN是EEC-1对应的EDN，则ECS在该EDN确定出的对应的EES也是该EDN中共同的EES。那么，每个对应的EDN中仅会确定出一个对应的EES。本申请附图5就是以每个EDN包括一个EES为例进行说明的。
可选地，在上述步骤600不执行的情况下，一个EDN中可以包括多个EES。若某EDN是EEC-1对应的EDN，则ECS在该EDN确定出的对应的EES的数量可以为多个。从而，ECS确定出的对应的EES的数量，可以大于确定出的对应的EDN的数量。
应理解，EES已经注册到ECS上，或者，EES的部署信息预配置在ECS中，或者ECS可以通过网管系统获取EES的部署信息。因此，ECS在确定EEC-1对应的EES后，即可确定EEC-1对应的EES的信息。
可选地，本申请实施例中的EES的信息可以包括以下至少一项信息：EES的标识信息、EES的地址信息、或EES的对应的部署信息中的至少一项。
可选地，EES的对应的部署信息可以包括以下至少一项：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI、或EES所属的层级。
步骤603、ECS向EEC-1发送至少一个的EES的信息。
该至少一个EES的信息为ECS确定的UE-1对应的至少一个EES的信息。至少一个EES的信息可以参考上述步骤701中对于EES的信息的描述，此处不再赘述。
作为一种可能的实现方式，该至少一个的EES的信息可以承载在服务配置响应消息中。当然，也可以使用其他的消息携带EES的信息，本申请对此不作限定。
步骤604、EEC-1选择EES。
EEC-1可以在ECS确定的至少一个EES中，选择需要使用EES。本申请实施例中，EEC-1选择的EES，可以用于确定为AC-1提供边缘计算服务的EAS。也可以理解为，EEC-1选择的EES，是EEC-1期望用于为AC-1提供边缘计算服务的EAS对应的EES。
可选地，EEC-1选择EES，具体的实现方式如下：
作为一种可能的实现方式，EEC-1可以根据其期望的EDN信息或边缘计算服务的层级信息，选择EES。例如，EEC-1可以选择距离UE最近或层级最低的EES作为需要使用的EES。
作为一种可能的实现方式，EEC-1可以获知组1中除UE外的其他UE的位置，进而可以根据UE-1与其他UE的位置关系选择需要使用的EES。例如，EEC-1可以选择与其他UE的位置距离均等的EES作为需要使用的EES。
可选地，本申请实施例中，EEC-1也可以不强制要求同一组UE连接到同一个EAS，也就是选择到同一个EES。一种可能的实现方式，同一组中的某个UE与其他UE的距离较远，连接至同一个EAS的效果较差，从而EEC-1可以确定该UE单独连接EAS，也即是选择单独的EES。
示例性的，步骤602中ECS确定的对应的EES可以包括EES-1、EES-3和EES-5。应理解，UE-1位于海淀，UE-4位于天津，UE-1和UE-4不在同一市区，EEC-1可以确定二者无需连接至同一个EAS，EEC-1不需要选择到华北市区(EES-3)这一层级的EES。从而，EEC-1确定需要使用的EES可以包括EES-1和EES-3。
下述步骤以EEC-1选择的EES为EES-1和EES-3为例进行描述，在此统一说明。
步骤605、EEC-1向EES-1请求发现EAS。
作为一种实现方式，EEC-1可以EES-1通过EAS发现请求消息向EES-1请求发现EAS。当然，也可以通过其他的消息请求发现EAS，本申请对此不作限定。
EEC-1向EES-1请求发现EAS，具体可以包括：EEC-1向EES-1请求发现为AC-1提供边缘计算服务的EAS。
可选地，在执行步骤605时，EEC-1还可以向EES-1发送AC-1对应的业务信息，AC-1对应的业务信息可以用于确定能够为AC-1提供边缘计算服务的EAS。其中，EEC-1向EES-1发送的AC-1对应的业务信息可以为AC-1所需要的或者请求获取的业务的信息。
作为一种可能的实现方式，AC-1对应的业务信息可以承载在EEC-1向EES-1发送的EAS发现请求消息或者其他消息中，本申请对此不作限定。
作为一种可能的实现方式，AC-1对应的业务信息可以包括以下至少一项：用于匹配EAS参数的AC配置文件、AC所需的EAS特征、EAS的标识、或EAS供应商标识符等信息。
在EEC-1向EES-1发送AC-1对应的业务信息的情况下，EES-1可以根据AC-1对应的业务信息，在该EES-1上管理的EAS中确定出能够为AC-1提供边缘计算服务的EAS。为AC-1提供边缘计算服务的EAS可以记作EAS-1。
EEC-1向EES-1请求发现EAS，还可以包括：EEC-1向EES-1请求发现组1对应的共同的EAS。其中，组1为一个UE组，组1可以包括多个UE，UE-1可以是组1中的UE。组1对应的共同的EAS是指能够为组1包括的UE提供边缘计算服务的EAS。
可选地，在执行步骤605时，EEC-1还可以向EES-1发送组1的信息，组1的信息可以指示组1中包括的UE的信息。其中，组1的信息可以包括组ID和/或UE列表等信息。该组1的信息可以用于使得EES-1为组1包括的UE确定共同的EAS。
可选地，组1的信息可以承载在EAS发现请求消息或者其他消息中，本申请对此不作限定。
可选地，EES-1在接收到EEC-1发送的组1的信息之后，可以判断本地是否维护有组1对应的共同的EAS。如果EES-1本地维护有组1对应的共同的EAS，则EES-1可以向EEC-1发送该组1对应的共同的EAS。例如，组1中除UE-1之外的其他UE之前已经请求发现、并且确定了组1对应的共同的EAS。从而，EES-1在步骤605之前可以获知组1对应的共同的EAS。进而，在EES-1在接收到EEC-1发送的组1的信息之后，EES-1可以将之前获知的组1对应的共同的EAS，发送给EEC-1。
如果EES-1本地没有维护组1对应的共同的EAS，则EES-1需要进一步为组1确定对应EAS。
本申请实施例中，可以在EEC-1所选择的至少一个EES对应的至少一个EAS中，确定组1对应的共同的EAS。从而，在EES-1没有维护组1对应的共同的EAS的情况下，可以进一步向其他EES请求获取或订阅组1对应的共同的EAS。
可选地，在执行步骤605时，EEC-1还可以向EES-1发送至少一个EES的信息。其中，EEC-1向EES-1发送的至少一个EES的信息，为EEC-1选择的至少一个EES中除EES-1之外的其他EES的信息。例如，EEC-1确定的需要使用的EES可以包括EES-1和EES-3，但是EEC-1向EES-1发送的EAS发现请求消息 中的候选EES列表可以仅包括EES-3的信息，不包括EES-1的信息。
应理解，该至少一个EES的信息可以用于指示EES-1向至少一个EES请求获取或者订阅组1对应的共同的EAS。示例地，EEC-1可以向EES-1发送EES-3的信息，从而可以指示EES-1后续向EES-3请求获取或者订阅组1对应的共同的EAS。
步骤606、EES-1向EEC-1发送EES-1发现的EAS的信息。
该EES-1发现的EAS的信息，是能够为AC-1提供边缘计算服务的EAS的信息。该EES-1发现的EAS是EDN-1中的EAS，该EES-1发现的EAS与EES-1和EDN-1对应。
可选地，如果EES-1发现的EAS有多个，该多个EAS均可以是EDN-1中的EAS，该多个EAS均与EES-1和EDN-1对应。
在EES-1发现的EAS包括多个EAS的情况下，步骤606之后还可以包括如下步骤X、步骤Y和步骤Z。
步骤X、EEC-1在EES-1发现的多个EAS中选择一个确定使用的EAS。
步骤Y、EEC-1向EES-1发送EEC-1确定使用的EAS。
作为一种可能的实现方式，EEC-1可以通过选定的EAS公告请求(selected EAS announcement request)向EES-1指示其确定使用的EAS。
步骤Z、EES-1向EEC-1发送成功或失败的指示信息。
作为一种实现方式，该成功或失败的指示信息可以承载在选定的EAS公告响应(selected EAS announcement response)中。
可选地，如果在步骤605中，EEC-1没有向EES-1发送至少一个EES的信息和/或组1的信息，那么EEC-1可以在步骤Y中向EES-1发送至少一个EES的信息和/或组1的信息。
在执行步骤606，或执行步骤606、步骤X、步骤Y以及步骤Z后，EEC-1可以确定出唯一一个为AC-1提供边缘计算服务的EAS。之后，EEC-1可以让AC-1连接至该EAS上。例如，假设EEC-1选择的为AC-1提供边缘计算服务的EAS为EAS-1，那么EEC-1可以将获取到的EAS-1的信息传输给AC-1，使得AC-1连接至EAS-1上。
可选地，EES-1发现的EAS的信息可以承载在EAS发现响应消息中发送给EEC-1。当然，也可以有其他的承载方式，本申请对此不作限定。
步骤607、EES-1向EES-3订阅组1对应的共同的EAS的信息。
在之前的步骤605中，EEC-1向EES-1发送了组1的信息和EES-3的信息，基于此，EES-1可以向EES-3请求获取组1对应的共同的EAS。
作为一种可能的实现方式，EES-1可以通过发送宣布共同EAS订阅请求(announce common EAS subscription request)消息，向EES-3请求获取EAS的信息。
可选地，在执行步骤607时，EES-1还可以向EES-3发送组1的信息，组1的信息用于指示EES-3确定组1对应的共同的EAS。该组1的信息可以承载在宣布共同EAS订阅请求消息或者其他消息中，本申请对此不作限定。
可选地，在执行步骤607时，EES-1还可以向EES-3发送AC-1对应的业务信息，AC-1对应的业务信息可以用于辅助确定组1对应的共同的EAS，该AC-1对应的业务信息可以使得EES-3确定出的组1对应的共同的EAS更适合AC-1的业务场景。AC-1对应的业务信息可以参考步骤605中的描述，此处不再赘述。
步骤608、EES-3向EES-1发送成功或者失败的指示信息。
其中，当订阅成功时，EES-3可以向EES-1指示订阅ID。当订阅失败时，EES-3可以向EES-1指示失败的原因。
作为一种可能的实现方式，成功或者失败的指示信息可以承载在宣布共同EAS订阅响应(announce common EAS subscription response)消息中。
本申请实施例中，组1中的除UE-1之外的其他UE也可以执行上述步骤601至步骤608。比如，组1可以包括UE-1、UE-2和UE-3，UE-2中的EEC-2和UE-3中的EEC-3也可以执行上述步骤601至步骤608类似的步骤。
示例地，EEC-2与EES-2可以执行如下步骤：
步骤601a、EEC-2向ECS请求EES的信息。该步骤可以参考步骤601的描述。
步骤602a、ECS确定UE-2对应的EES。该步骤可以参考步骤602的描述。
步骤603a、ECS向EEC-2发送至少一个的EES的信息。该步骤可以参考步骤603的描述。
步骤604a、EEC-2选择EES。该步骤可以参考步骤604的描述。
可选地，EEC-2选择的EES可以与EEC-1选择的EES相同。
步骤605a、EEC-2向EES-2请求发现EAS。该步骤可以参考步骤605的描述。
其中，EEC-2向EES-2请求发现的EAS，是能够为AC-2提供边缘计算服务的EAS。
步骤606a、EES-2向EEC-2发送EES-2发现的EAS的信息。该步骤可以参考步骤606的描述。
其中，EES-2发现的EAS的信息是能够为AC-2提供边缘计算服务的EAS的信息。该EES-2发现的EAS是EDN-2中的EAS，该EES-2发现的EAS与EES-2和EDN-2对应。
步骤607a、EES-2向EES-3请求订阅组1对应的共同的EAS。该步骤可以参考步骤605的描述。
步骤608a、EES-3向EES-2发送成功或者失败的指示信息。
经过上述步骤601a至步骤608a，EES-3可以接收到组1的信息和/或AC-2对应的业务信息。
又示例地，EEC-3与EES-3可以执行如下步骤：
步骤601b、EEC-3向ECS请求EES的信息。该步骤可以参考步骤601的描述。
步骤602b、ECS确定UE-3对应的EES。该步骤可以参考步骤603的描述。
步骤603b、ECS向EEC-3发送至少一个的EES的信息。该步骤可以参考步骤603的描述。
步骤604b、EEC-3选择EES。该步骤可以参考步骤604的描述。
可选地，EEC-3选择的EES可以与EEC-1选择的EES相同。
步骤605b、EEC-3向EES-3请求发现EAS。该步骤可以参考步骤605的描述。
其中，EEC-3向EES-3请求发现的EAS，是能够为AC-3提供边缘计算服务的EAS。
步骤606b、EES-3向EEC-3发送EES-3发现的EAS的信息。该步骤可以参考步骤606的描述。
其中，EES-3发现的EAS的信息是能够为AC-3提供边缘计算服务的EAS的信息。该EES-3发现的EAS是EDN-3中的EAS，该EES-3发现的EAS与EES-3和EDN-3对应。
可选地，在图5所示的场景中，EEC-3选择的EES中层级最高的EES就是EES-3，那么EEC-3无需向EES-3发送其他EES的信息，EES-3也就无需与其他EES交互，从而EES-3可以从EDN-3中确定组1对应的共同的EAS。
经过上述步骤601b至步骤606b，EES-3可以接收到组1的信息和/或AC-3对应的业务信息。
步骤609、EES-3确定组1对应的共同的EAS。
EES-3可以根据之前获取到的组1的信息、以及AC-1、AC-2、或AC-3对应的业务信息中的至少一项，确定组1对应的共同的EAS。
作为一种实现方式，EES-3在接收到组1的信息后，可以先判断本地是否维护有组1对应的共同的EAS。如果有，直接向EES-1反馈组1对应的共同的EAS。如果没有，EES-3则需要进一步获取组1对应的共同的EAS。
一种可能的情况中，组1中除UE-1之外的其他UE之前已经请求发现、并为组1确定了共同的EAS。那么，EES-3在步骤605之前可以获知组1对应的共同的EAS。从而，EES-3可以将之前获知的组1对应的共同的EAS，发送给EES-1。
一种可能的情况中，EES-3本地没有维护有组1对应的共同的EAS，此种情况下，EES-3需要自行确定组1对应的共同的EAS。
可选地，EES-3可以将为组1中的AC(例如AC-1)确定的EAS，确定为组1中的UE共同的EAS。
示例地，以EES-3接收到组1中的AC-1(对应UE-1)和AC-2(对应UE-2)对应的业务信息为例，EES-3可以根据AC-1和AC-2对应的业务信息，在EES-3对应的至少一个EAS中确定出AC-1和AC-2对应的业务所需的EAS，该EAS即可认为是能够为AC-1和AC-2提供边缘计算服务的EAS，该EAS即可作为组1包括的UE共同的EAS。例如，该组1共同的EAS可以为EAS-3。
EAS的信息可以参考步骤2c中的描述，此处不再赘述。
基于此，后续组1中的其他UE在向EES-3请求发现EAS时，EES-3可以基于组1的信息，确定将EAS-3发送(直接发送或通过其他EES发送)给该组中的其他UE。从而，该组中的UE在从EES-3获取EAS的信息时，可以获取到相同的EAS，从而多个不同的UE(实际上是UE中AC)可以连接至相同的EAS上。
可选地，步骤609可以在EES-3接收到组1中的多个UE中的AC对应的业务信息时才执行。如果EES-3只收到了组1中的一个UE中的AC对应的业务信息(例如只收到AC-1对应的业务信息)，可以无需执行步骤609。此种情况下，只需要为AC-1确定EAS即可，无需为组1确定共同的EAS。
可选地，如果EES-3在接收到AC-1对应的业务信息之前，接收到过组1中其他UE中的AC对应的业务信息(例如之前接收到过AC-2的业务信息)，那么在接收到AC-1对应的业务信息时，可以为组1确定共同的EAS。
步骤610、EES-3向EES-1发送组1对应的共同的EAS的信息。
示例地，假设EES-3确定的组1对应的共同的EAS为EAS-3，则EES-3可以向EES-1发送EAS-3的信息。
可选地，在步骤610中，EES-3还可以向EES-1发送组1的信息，该组1的信息可以与组1对应的共同的EAS的信息一同发送，以指示EAS-3为组1对应的共同的EAS。
作为一种可能的实现方式，EES-3可以通过宣布共同EAS通知(announce common EAS notification)消息反馈EAS的信息。
可选地，在步骤609之前，EES-3可以接收到来自EEC-2的组1的信息和/或AC-2的信息，那么，该方法还可以包括：步骤610a、EES-3向EES-2发送组1对应的共同的EAS的信息。以便EES-2向EEC-2进一步指示组1对应的共同的EAS的信息。
可选地，在步骤609之前，EES-3可以接收到来自EEC-3的组1的信息和/或AC-3的信息，那么，该方法还可以包括：步骤610b、EES-3向EEC-3发送组1对应的共同的EAS的信息。
步骤611、EES-1可以为EEC-1触发应用上下文迁移。
上述步骤606后，AC-1可以与EES-1反馈的EAS-1建立连接。而在步骤610之后，EES-1可以获取到EES-3为AC-1下发的EAS-3。基于此，EES-1可以确定将AC-1的连接切换至EAS-3，从而EES-1可以为AC-1触发应用上下文迁移。
在应用上下文迁移完成后，AC-1会收到EAS的信息，AC可以连接至新的EAS上。
通过上述方法，EEC-1可以确定出多个需要使用的EES，该多个EES可以位于不同层级的EDN中，该多个需要使用的EES可以用于确定为AC-1提供边缘计算服务的EAS，该方法的灵活性较好。并且，基于上述方法，当EEC-1接收到较高层级的EAS时，EEC-1可以将AC-1切换连接到较高层级EDN对应的的EAS上。
可选地，在图6对应的实施例中，步骤608和步骤610可以合并执行，即组1对应的共同的EAS的信息可以与成功或者失败的指示信息一同发送，从而可以节约信令资源。
可选地，在上述步骤600不执行的情况下，一个EDN中可以包括多个可用的EES。在EEC-1向同一个EDN中的多个EES请求发现EAS的情况下，该多个EES可以进行协商确定出一个共同的EES。进而，该共同的EES可以用于为EEC-1发现EAS。
继续以图5中的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图8所示，该方法可以包括如下步骤：
步骤800至步骤810可以与步骤600至步骤610相同。区别在于：1、步骤805中，EEC-1可以通过EAS发现订阅请求消息，向EES-1请求发现EAS。2、步骤806中，EES-1通过EAS发现订阅响应消息，向EEC-1发送其发现的EAS的信息。采用订阅类型的消息的好处在于，后续EES-1可以主动向EEC-1指示信息(例如后续步骤811)。
步骤811、EES-1向EEC-1发送组1对应的共同的EAS的信息。
作为一种实现方式，EES-1可以通过发现通知(EAS discovery notification)消息向发送EEC-1该EAS的信息。
示例性地，步骤811中发送的EES-3发现的EAS的信息，是EES-3确定出的组1对应的共同的EAS的信息，例如为EAS-3的信息。
步骤812、EES-1为AC-1触发应用上下文迁移，或者，EES-1确定要使用的EAS。
可选地，在步骤806之后，AC-1也可以与EES-1反馈的EAS-1建立连接。而在步骤811之后，EEC-1又可以接收到了EES-1指示的能够为AC-1提供边缘计算服务的EAS-3。基于此，EEC-1可以确定将AC-1的连接切换至EAS-3，从而EEC-1可以为AC-1触发应用上下文迁移。
可选地，在步骤806之后，EEC-1在收到EES-1指示的EAS-1后，可以不指示AC-1与该EAS-1连 接，而是让AC-1处于等待状态。后续，在步骤811之后，EEC-1又可以接收到了EES-1指示的能够为AC-1提供边缘计算服务的EAS-3。此种情况下，进而，EEC-1可以在EAS-1和EAS-3中选择一个使用，为AC-1提供边缘计算服务。
可选地，在步骤806之前，EEC-1可以设置一个定时器，EEC-1可以在该定时器的运行时间内不连接EAS，以便EEC-1在等待时间内接收到后续下发的EAS的信息(例如EAS-3的信息)。从而，使得EEC-1直接在多个EAS中确定一个使用的EAS，避免了EEC-1连接EAS之后进行切换的流程，该方案可以一定程度上减少连接的切换和应用上下文的迁移，进而可以减少动态组场景下的信令浪费问题。
当然，如果在定时器的运行时间内，EEC-1没有接收到其他EAS的信息，该EEC-1可以指示AC-1连接到EAS-1上，后续则可以由EES-1或者EEC-1来触发AC-1的应用上下文迁移。
也就是说，在图8对应地实施例中，步骤806和步骤811可以合并执行，即EES-3发现的EAS-3的信息可以与EES-1发现的EAS-1的信息，一同发送给EEC-1。此种实现方式可以节约信令资源。
图8对应的方法实施例与图6对应的方法实施例类似，上述图8对应的方法实施例带来的其他技术效果可以参考上述图6对应的方法实施例的技术效果描述。
继续以图5中的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图9所示，该方法可以包括如下：
步骤900至步骤904可以与步骤600至步骤604相同。
步骤905、EEC-1向EES-1请求发现EAS。
作为一种实现方式，EEC-1可以EES-1通过EAS发现请求消息向EES-1请求发现EAS。当然，也可以通过其他的消息请求发现EAS，本申请对此不作限定。
可选地，在EEC-1向EES-1请求发现EAS的同时，EEC-1还可以向EES-1发送AC-1对应的业务信息，AC-1对应的业务信息可以用于确定能够为AC-1提供边缘计算服务的EAS。该动作可以参考步骤605中的描述，此处不再赘述。
步骤906、EES-1向EEC-1发送EES-1发现的EAS的信息。
该步骤906可以完全参考步骤606的描述，此处不再赘述。
步骤907、EEC-1向EES-1订阅组1对应的共同的EAS的信息。
作为一种可能的实现方式，步骤907可以通过共同EAS信息订阅请求(common EAS information subscription request)消息实现。
步骤908、EES-1向EEC发送成功或失败的指示信息。
作为一种可能的实现方式，步骤908可以通过共同EAS信息订阅响应(Common EAS information subscription response)消息实现。
步骤909至步骤914与步骤607至步骤612相同，此处均不再赘述。
图9对应的方法实施例相较于图6和图8对应的方法实施例，EEC-1可以不复用现有的EAS发现流程中的消息(如EAS发现订阅请求消息)，而是采用新的消息(如共同EAS信息订阅请求消息)向EES-1指示组1的信息、AC-1对应的业务信息。该方案提供了获取边缘计算服务的方法的又一种实现方式，提高了本申请方法的灵活性。
继续以图5中的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图10所示，该方法可以包括如下步骤1000至步骤1011。
步骤1000至步骤1006可以与步骤600至步骤606相同。
其中，步骤1004中，EEC-1确定的EES信息中，层级最高的为EES-3。步骤1005和步骤1006可以为现有技术的EAS发现流程，步骤1005和步骤1006可以参考步骤402和步骤403的描述。
步骤1007、EEC-1向EES-3订阅组1对应的共同的EAS的信息。
作为一种可能的实现方式，步骤1007可以通过共同EAS信息订阅请求(Common EAS information subscription request)消息实现。
可选地，在图10对应的方法实施例中，EEC-1确定要使用的EES可以仅为EES-3，从而EEC-1可以直接向EES-3请求发现EAS。
可选地，在执行步骤1007时，EEC-1可以向EES-3发送组1的信息、AC-1对应的业务信息中的至少一项。上述信息的内容可以参考上述图6对应的方法实施例中的描述，此处不再赘述。
步骤1008、EES-3向EEC-1发送成功或失败的指示信息。
其中，当订阅成功时，EES-3可以向EES-1指示订阅ID。当订阅失败时，EES-3可以向EES-1指示失败的原因。
作为一种可能的实现方式，成功或失败的指示信息是否可以承载在(announce common EAS subscription response)消息中。
步骤1009至步骤1010与步骤609至步骤610相同，步骤1011至步骤1012与步骤811至步骤812相同，此处不再赘述。
在图10对应的方法实施例中，EEC-1可以直接向至少一个需要使用的EES中的最高层级的EES发送请求消息，以获得EAS信息。该方法不需要不同层级的EES之间进行逐级的交互，可以简化方案实现的复杂度，可以降低EES的工作负担。
图11示出了另一种EDN的层级关系的示意图，图11可以参考图5中的EDN的相关描述。图11相较于图5的区别在于，EDN-1中还包括EDN-0，EDN-0为EDN-1的下一层级，EDN-0中可以包括UE-0和EES-0。示例性的，EDN-0可以为“上地”街道，“上地”街道属于海淀区中的街道，属于海淀区的下一层级。
以图11中的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图12所示，该方法可以包括如下步骤1200至步骤1216。
步骤1200、ECS根据预配置的规则信息，在每个EDN中确定出为一组UE提供服务的EES。该步骤1200与步骤600相同，此处不再赘述。
步骤1201、EEC-0向ECS请求EES的信息。
作为一种可能的实现方式，EEC-0可以向ECS发送服务配置请求消息来请求获取EES的信息。当然，也可以使用其他的消息来请求获取EES的信息，本申请对此不作限定。
该步骤可以参考步骤601中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、以及AC-1替换为AC-0即可，此处不再赘述。
步骤1202、ECS确定UE-0对应的EES。
该步骤可以参考步骤602中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、以及AC-1替换为AC-0即可，此处不再赘述。
步骤1203、ECS向EEC-0发送至少一个的EES的信息。
作为一种可能的实现方式，该至少一个的EES的信息可以承载在服务配置响应消息中。当然，也可以使用其他的消息携带EES的信息，本申请对此不作限定。
该步骤可以参考步骤603中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、以及AC-1替换为AC-0即可，此处不再赘述。
步骤1204、EEC-0选择EES。
该步骤可以参考步骤604中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、以及AC-1替换为AC-0即可，此处不再赘述。
在该实施例中，EEC-0确定的需要使用的EES可以包括EES-0、EES-1和EES-3的信息。
步骤1205、EEC-0向EES-0请求发现EAS。
作为一种实现方式，EEC-0可以EES-0通过EAS发现请求消息向EES-0请求发现EAS。当然，也可以通过其他的消息请求发现EAS，本申请对此不作限定。
该步骤可以参考步骤605中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、以及AC-1替换为AC-0即可，此处不再赘述。
在该实施例中，EEC-0向EES-0发送的至少一个EES的信息可以包括EES-1和EES-3的信息，无需包括EES-0的信息。
步骤1206、EES-0向EEC-0发送EES-0发现的EAS的信息。
可选地，EES-0发现的EAS的信息可以承载在EAS发现响应消息中发送给EEC-0。当然，也可以有其他的承载方式，本申请对此不作限定。
该步骤可以参考步骤606中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、以及AC-1替换为AC-0即可，此处不再赘述。
步骤1207、EES-0确定获取组0对应的共同的EAS的信息。
在步骤1205中，EES-0可以接收到EEC-0发送的组0的信息，组0为UE-0所在的组。基于此，EES- 0可以为组0确定对应的共同的EAS。如果EES-0本地维护有组0对应的共同的EAS，则EES-0可以直接反馈给EEC-0。如果EES-0本地维护没有组0对应的共同的EAS，则EES-0需要进一步通过其他方式获取组0对应的共同的EAS。
在步骤1205中，EEC-0可以向EES-0发送EES-1和EES-3的信息，基于此，EES-0可以确定向EES-1或EES-3请求获取组0对应的共同的EAS。作为一种实现方式，EES-0可以根据EES-1和EES-3的层级关系，确定向EES-1(层级低于EES-3)请求获取组0对应的共同的EAS的信息。
步骤1208、EES-0向EES-1订阅组0对应的共同的EAS的信息。
作为一种可能的实现方式，EES-0可以通过宣布共同EAS订阅请求消息向EES-1订阅EAS的信息。
该步骤可以参考步骤607中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、EES-3替换为EES-1、以及AC-1替换为AC-0即可，此处不再赘述。
可选地，在执行步骤1208时，EES-0可以向EES-1发送EES-3的信息，无需发送EES-1的信息。
步骤1209、EES-1向EES-0发送成功或者失败的指示信息。
其中，当订阅成功时，EES-3可以向EES-1指示订阅ID。当订阅失败时，EES-3可以向EES-1指示失败的原因。
作为一种可能的实现方式，成功或者失败的指示信息可以承载在宣布共同EAS订阅响应(announce common EAS subscription response)消息中。
该步骤可以参考步骤608中的相关描述，只需将EEC-1替换为EEC-0、EES-1替换为EES-0、EES-3替换为EES-1、以及AC-1替换为AC-0即可，此处不再赘述。
可选地，EES-0可以根据接收到的宣布共同EAS订阅请求消息中的AC-0对应的业务信息，确定出能够为AC-0提供边缘计算服务的EAS-1，EAS-1与EES-1关联。从而，EES-0向EEC-0发送的宣布共同EAS订阅响应消息中可以包括EAS-1的信息。
步骤1210、EES-1确定获取组0对应的共同的EAS的信息。
可选的，EES-0向EES-1发送的EAS发现请求消息中可以包括组0的信息，EES-1需要为组0确定对应的共同的EAS。如果EES-1本地维护有组0对应的共同的EAS，则EES-1可以反馈给EEC-0。如果EES-1本地维护没有组0对应的共同的EAS，则EES-1需要通过其他方式进一步获取组0对应的共同的EAS。
可选的，由于EES-0向EES-1发送的EAS发现请求消息中包括EES-3的信息，因此EES-1可以向EES-3请求获取组0对应的共同的EAS。
步骤1211、EES-1向EES-3订阅组0对应的共同的EAS的信息。
步骤1212、EES-3向EES-1发送成功或者失败的指示信息。
步骤1213、EES-3确定组0对应的共同的EAS。
步骤1214、EES-3向EES-1发送组0对应的共同的EAS的信息。
步骤1211至步骤1214与步骤607至步骤610类似，可以参考步骤607至步骤610的描述，此处不再赘述。
可选地，步骤1212和步骤1214可以合并执行，即组0对应的共同的EAS的信息可以与成功或者失败的指示信息一同发送，从而可以节约信令资源。
步骤1215、EES-1向EES-0发送组0对应的共同的EAS的信息。
作为一种可能的实现方式，EES-3发现的EAS的信息可以承载在宣布共同EAS通知消息中发送。相应地，EES-0接收宣布共同EAS通知消息。
步骤1216、EES-0为EEC-0触发应用上下文迁移。
该步骤与上述步骤611类似，可以参考图6对应的实施例中EES-1触发EEC-1应用上下文迁移的描述，此处不再赘述。
上述图12对应的实施例，相较于图6、图8、图9或图10对应的实施例，区别在于多了一个层级，从而多了一层EES的交互流程。其他交互过程及消息内容均可参考上文图6、图8、图9或图10对应的实施例中的描述。图12展示的方案是从低层级的EES(EES-0)到高层级的EES(EES-3)逐级交互，从而获取EAS的信息的过程。
下面，继续以图11中的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图13所示，该方法可以包括如下步骤1300至步骤1315。
步骤1300至步骤1306与步骤1200至步骤1206相同，可以参考前文的描述。
步骤1307、EEC-0向EES-1订阅组0对应的共同的EAS的信息。
作为一种可能的实现方式，EEC-0可以通过共同EAS订阅请求消息，向EES-1订阅组0对应的共同的EAS的信息。
在步骤1307中，EEC-0可以向EES-1发送组0的信息，以请求EES-1发现组0对应的共同EAS。
可选地，EEC-0还可以向EES-1发送AC-0对应的业务信息，AC-0对应的业务信息也可以用于确定组0对应的共同EAS。
应理解，上述信息的内容可以参考上述图6对应的方法实施例中的描述，UE-0可以参考UE-1的相关描述，AC-0可以参考AC-1的相关描述，组0可以参考组1的相关描述，此处不再赘述。
步骤1308、EES-1向EEC-0发送成功或失败的指示信息。
可选地，如果失败了，该指示信息还可以指示失败的原因。
作为一种可能的实现方式，该成功或失败的指示信息可以承载在共同EAS订阅响应消息中。
步骤1309至步骤1315与步骤1210至步骤1216相同，可以参考前文的描述。
图13对应的实施例与图12对应的实施例相比，区别在于：在图12对应的实施例中，EEC-0是先向EES-0订阅组0对应的共同的EAS的信息，进而EES-0再逐级向上订阅组0对应的共同的EAS的信息。而在图13对应的实施例中，EEC-0直接向EES-1订阅组0对应的共同的EAS的信息，再由EES-1再逐级向上订阅组0对应的共同的EAS的信息。该方案是一种可能的实现方式。
下面，继续以图11中的网络架构为例，本申请提供的一种获取边缘计算服务的方法可以如图14所示，该方法可以包括如下步骤1400至步骤1411。
步骤1400至步骤1406与步骤1200至步骤1206相同，可以参考前文的描述。
步骤1407、EEC-0向EES-1订阅组0对应的共同的EAS的信息。
作为一种可能的实现方式，EEC-0可以通过发送共同EAS订阅请求消息向EES-1请求发现EAS。
可选地，EEC-0向EES-1发送的共同EAS订阅请求消息中可以不包括EES的信息。
可选地，EEC-0向EES-1发送的共同EAS订阅请求消息中可以包括组0的信息和/或AC-0对应的业务信息。EEC-0向EES-1请求发现EAS是组0对应的共同EAS。
应理解，组0的信息可以参考前文组1的信息的相关描述，AC-0对应的业务信息可以参考前文AC-1对应的业务信息的相关描述，此处不再赘述。
步骤1408、EES-1向EEC-0发送组0对应共同的EAS的信息。
作为一种可能的实现方式，EES-1发现的EAS的信息承载在共同EAS订阅响应消息中。
步骤1409、EEC-0向EES-3订阅组0对应的共同的EAS的信息。
作为一种可能的实现方式，EEC-0可以通过发送共同EAS订阅请求消息向EES-3请求发现EAS。
该步骤1409与步骤1407类似(只需要把EES-3换成EES-1即可)，可参考之前的描述，此处不再赘述。
步骤1410、EES-3向EEC-0发送组0对应共同的EAS的信息。
作为一种可能的实现方式，EES-3发现的EAS的信息承载在共同EAS订阅响应消息中。
步骤1411、EEC-0从EES-3确定的EAS和EES-1确定的EAS中，选择AC-0使用的EAS。
可选地，EEC-0可以选择层级最高的EES对应的EAS。
需要说明的是，在图14对应的方法实施例中，EEC-0确定需要使用的EES可以为EES-1和EES-3。并且，EEC-0可以直接向EES-1和EES-3发送共同EAS订阅请求消息，无需通过其他EES逐级转发。
可选地，如果EES-1和EES-3都反馈了EAS的信息，那么EEC-0可以在多个EAS中进行选择。这种直接与需要使用的EES进行交互的方式，比较高效。
需要说明的是，上述图6、图8、图9、图10、图12、图13和图14所示的实施例为本申请提供的获取边缘计算服务的方法的几种示例性的说明。
基于上述各种场景的示例性的描述，本申请提供了一种获取边缘计算服务的方法可以如图15所示，该方法可以应用于第一EEC，该方法可以包括如下步骤：
步骤1501、第一EEC向第一实体发送至少一个EES的信息。
可选地，第一EEC可以是第一UE中的边缘使能客户端，第一EEC位于第一UE中。示例地，以图5为例，第一UE可以为UE-1，第一EEC可以是UE-1中部署的EEC。或者，以图11为例，第一UE可以 为UE-0，第一EEC可以为UE-0中部署的EEC。
可选地，第一实体可以为第一EES，第一EES能够为第一EEC提供边缘计算服务。
以图6、图8或图9为例，第一EEC可以为EEC-1，第一EES可以为EES-1。以图12为例，第一EEC可以为EEC-0，第一EES可以为EES-0。以图13为例，第一EEC可以为EEC-0，第一EES可以为EES-1。
第一EEC向第一实体发送的至少一个EES能够为第一EEC提供边缘计算服务。以图6、图8或图9为例，第一EEC可以为EEC-1，第一EES可以为EES-1，该至少一个EES可以包括EES-3。以图12为例，第一EEC可以为EEC-0，第一EES可以为EES-0，该至少一个EES可以包括EES-1和EES-3。以图13为例，第一EEC可以为EEC-0，第一EES可以为EES-1，该至少一个EES可以包括EES-3。
可选地，至少一个EES的信息中任一个EES的信息可以包括以下至少一项信息：EES的标识信息、EES的地址信息、或EES对应的部署信息。其中，EES对应的部署信息可以包括以下至少一项：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的DNAI、或EES所属的层级。
本申请实施例不限制携带至少一个EES的信息的消息类型。可选地，至少一个EES的信息可以携带在发现请求消息、发现订阅请求消息、或共同EAS信息订阅请求消息等消息中。
示例地，在图6对应的实施例中，第一EEC可以为EEC-1，第一EES可以为EES-1，步骤1501可以在步骤605中执行。又示例地，在图8对应的实施例中，第一EEC可以为EEC-1，第一EES可以为EES-1，步骤1501可以在步骤805中执行。又示例地，在图9对应的实施例中，第一EEC可以为EEC-1，第一EES可以为EES-1，步骤1501可以在步骤907中执行。又示例地，在图12对应的实施例，第一EEC可以为EEC-0，第一EES可以为EES-0，步骤1501可以在步骤1205中执行。又示例地，在图13对应的实施例中，第一EEC可以为EEC-0，第一EES可以为EES-1，步骤1501可以通过步骤1307实现。
步骤1502、第一EEC接收来自第一实体的至少一个EAS的信息。
其中，至少一个EAS能够为第一AC提供边缘计算服务。可选地，第一AC与第一EEC对应，第一AC和第一EEC可以部署在同一UE中。作为一种可能的实现方式，第一EEC是部署在第一UE中的边缘使能服务器，第一AC是部署在第一UE中的应用客户端，第一EEC、第一AC和第一UE可以认为是同一主体。
可选地，至少一个EAS与第一实体(即第一EES)和/或上述至少一个EES对应。
以图6、图8或图9对应的实施例为例，第一EEC可以为EEC-1，第一EES可以为EES-1，至少一个EES可以为EES-3，EEC-1接收到的至少一个EAS可以包括EAS-1和EAS-3；其中，EAS-1与EES-1对应，EAS-3与EES-3对应。在图6对应的实施例中，步骤1502可以在步骤606和步骤611中执行。在图8对应的实施例中，步骤1502可以在步骤806和步骤811中执行。在图9对应的实施例中，步骤1502可以在步骤908和步骤913中执行。
以图12对应的实施例为例，第一EEC可以为EEC-0，第一EES可以为EES-0，该至少一个EES可以包括EES-1和EES-3，EEC-0接收到的至少一个EAS可以包括EAS-0、EAS-1和EAS-3；其中，EAS-0与EES-0对应，EAS-1与EES-1对应，EAS-3与EES-3对应。在图12对应的实施例中，步骤1502可以在步骤1206和步骤1216中执行。
以图13为例，第一EEC可以为EEC-0，第一EES可以为EES-1，该至少一个EES可以包括EES-3，EEC-0接收到的至少一个EAS可以包括EAS-1和EAS-3；其中，EAS-1与EES-1对应，EAS-3与EES-3对应。在图13对应的实施例中，步骤1502可以通过步骤1308和步骤1315实现。
可选地，以第一EEC为EEC-1，第一EES可以为EES-1，该至少一个EAS的信息的内容可以参考上述步骤610中的描述，此处不再赘述。
对于图15对应的方案，有以下2种可能的实现方式：
第一种实现方式中，第一EEC接收至少一个EAS的信息，具体可以包括：第一EEC接收至少一个EAS的信息、以及与至少一个EAS中的第一EAS对应的第一组的信息。其中，第一EAS用于为第一组包括的UE提供边缘计算服务，即第一EAS为第一组对应的共同的EAS。基于该第一种实现方式，第一组对应的共同的EAS可以由第一EES指示，第一EEC在执行步骤1502后即可获取到第一组对应的共同的EAS。
示例地，以图6对应的实施例为例，第一UE可以为UE-1，第一EEC可以为EEC-1，第一EES可以为EES-1，第一组可以为组1。EEC-1接收到的至少一个EAS的消息可以包括EAS-1和EAS-3的消息。 其中，EAS-3是组1使用的EAS，EAS-3为第一EAS。在EES-1向EEC-1发送EAS-3的信息时，可以一同发送组1的信息，以指示EAS-3是组1对应的共同的EAS。详细内容可以参考上述图6对应的实施例中的描述，此处不再赘述。
基于该第一种实现方式，在步骤1502之前，该方法还可以包括：
步骤1503、第一EEC向第一EES发送第一业务信息，第一业务信息用于确定至少一个EAS。
其中，第一业务信息为第一AC对应的业务信息，第一AC是第一EEC对应的AC。
步骤1504、第一EEC向第一EES发送第一组的信息。
以第一UE为UE-1、第一EEC为EEC-1、第一EES为EES-1为例，该步骤1503和步骤1504可以参考上述步骤605中的相关描述，此处不再赘述。
第二种实现方式中，第一EEC接收到的至少一个EAS的信息，不包括与第一组的信息关联的第一EAS。换言之，在该第二种实现方式中，第一组对应的共同的EAS的信息不由第一EES指示。
在第二种实现方式中，在步骤1502之前，该方法还可以包括：步骤1505、第一EEC向第一EES发送第一业务信息，第一业务信息用于确定至少一个EAS。步骤1505与步骤1503相同，此处不再赘述。
在步骤1502之后，该方法还可以包括：步骤1506、第一EEC将至少一个EES中的第一EAS，确定为用于为第一组包括的UE提供边缘计算服务的EAS。换言之，由第一EEC来确定第一组使用的EAS。
步骤1507、第一EEC在向第一EES发送第一组的信息和第一EAS的信息。步骤1507是为了向第一EES指示第一组对应的共同的EAS为第一EAS。
在第二种实现方式中：第一EEC接收到至少一个能够为第一AC提供边缘计算服务的EAS后，并可以在其中确定出能够为第一组对应的共同的EAS(即第一EAS)，进而再将确定出的第一EAS通告给其他EES。
应理解，以第一UE为UE-1、第一EEC为EEC-1、第一EES为EES-1，第一组为组1为例，参考图6，如果第一EEC执行的是第二种实现方式的方案，那么步骤605和步骤607中不包括组1的信息。
可选地，第一EAS可以与第一EES对应，第一EAS的信息可以是第一EES确定的。例如，以图5为例，第一EEC可以为UE-3中的EEC-3，第一EES可以为EES-3，第一组对应的共同的EAS可以是EES-3对应的EAS-3。
可选地，第一EAS也可以与至少一个EES中的第二EES对应，第二EES能够为第一组包括的UE提供边缘计算服务。其中，第一EAS的信息可以是第一EES从第二EES接收到的。例如，以图5为例，第一EES可以为EES-1，第二EES可以为EES-3，第一组对应的EAS可以为EAS-3，该EAS-3可以由EES-3发送给EES-1。或者，第一EAS的信息是第一EES通过第三EES从第二EES接收到的，第三EES用于中继第一EES与第二EES的通信。例如，以图11为例，第一EES可以为EES-0，第二EES可以为EES-3，第三EES可以为EES-1，第一组对应的EAS可以为EAS-3，该EAS-3可以由EES-3通过EES-1转发给EES-0。
基于上述各种场景的示例性的描述，本申请提供了一种获取边缘计算服务的方法可以如图16所示，该方法可以应用于第一EES，该方法可以包括如下步骤：
步骤1601、第一EES接收来自第二实体的至少一个EES的信息，至少一个EES的信息用于确定能够为所述第二实体提供边缘计算服务的EES。
可选地，第二实体可以为第一EEC。
步骤1601是与步骤1501对应的动作，该步骤可以参考步骤1501中的相关描述，此处不再赘述。
可选地，该方法还可以包括：步骤1602、第一EES获取至少一个边缘应用服务器EAS的信息，至少一个EAS能够为第一AC提供边缘计算服务。其中，该至少一个EAS的信息可以是第一EES和/或上述至少一个EES确定的，该至少一个EAS与第一EES和/或上述至少一个EES对应。
示例地，以图6对应的实施例为例，第一EES可以为EES-1，至少一个EAS的信息可以包括EAS-1和EAS-3的信息。
可选地，该方法还可以包括：步骤1603、第一EES向第一EEC发送至少一个EAS的信息。该步骤可以参考步骤1502的描述，此处不再赘述。
对于图16对应的方案，有以下2种可能的实现方式：
在第一种实现方式中，第一EES向第一EEC发送至少一个EAS的信息，具体可以包括：第一EES向第一EEC发送至少一个EAS的信息，以及与至少一个EAS中的第一EAS关联的第一组的信息。其中， 第一EAS用于为第一组包括的UE提供边缘计算服务，即第一EAS为第一组对应的共同的EAS。基于该第一种实现方式，第一组对应的共同的EAS可以由第一EES指示给第一EEC。
基于第一种实现方式，在步骤1602之前，该方法还可以包括：
步骤1604、第一EES接收来自第一EEC的第一业务信息。
步骤1605、第一EES向至少一个EES发送第一业务信息。
步骤1606、第一EES接收来自第一EEC的第一组的信息。
步骤1607、第一EES向至少一个EES发送第一EEC的第一组的信息。
其中，第一组的信息和第一业务信息可以参考前文的描述，此处不再赘述。
以第一UE为UE-1、第一EEC为EEC-1、第一EES为EES-1为例，步骤1604至步骤1607可以参考图6对应的实施例中的相关描述，此处不再赘述。
在第二种实现方式中，第一EES发送的至少一个EAS的信息，不包括与第一组的信息关联的第一EAS。换言之，第一EES或其他EES还没有为第一组确定其使用的EAS。
基于第二种实现方式，在步骤1602之前，该方法还可以包括：
步骤1608、第一EES接收来自第一EEC的第一业务信息，第一业务信息用于确定至少一个EAS。
步骤1609、第一EES向至少一个EES发送第一业务信息。
步骤1608与步骤1604相同，步骤1609与步骤1605相同，可以参考之前的描述。
在步骤1602之后，该方法还可以包括：
步骤1610、第一EES接收来自第一EEC的第一组的信息和第一EAS的信息，第一EAS用于为第一组包括的UE提供边缘计算服务。
步骤1611、第一EES向至少一个EES发送第一组的信息和第一EAS的信息。
应理解，以第一UE为UE-1、第一EEC为EEC-1、第一EES为EES-1，第一组为组1为例，参考图6，如果第一EES执行的是第二种实现方式的方案，那么步骤605和步骤607中不包括组1的信息。
基于上述各种场景的示例性的描述，本申请提供了一种获取边缘计算服务的方法可以如图17所示，该方法可以应用于第二EES，该方法可以包括如下步骤：
步骤1701、第二EES接收来自第三实体的第一组的信息，第一组的信息用于确定为第一组包括的UE提供边缘计算服务的EAS。
可选地，第三实体可以为第一EES。
可选地，该方法还包括：步骤1702、第二EES向第一EES发送第一EAS的信息，第一EAS用于为第一组包括的UE提供边缘计算服务。
对于图17对应的方案，有以下2种可能的实现方式：
第一种实现方式中，第一EAS可以与第二EES关联。该方法还可以包括：步骤1703、第二EES确定第一EAS用于为第一组包括的UE提供边缘计算服务。换言之，能够为第一组内UE提供边缘计算服务的第一EAS，可以是由第二EES确定和发送的。
第二种实现方式中，第一EAS可以是由第一EEC确定的。此种情况下，第二EES接收来自第一EES的第一组的信息，具体包括：第二EES接收来自第一EES的第一组的信息和第一EAS的信息。其中，第一EAS用于为第一组包括的UE提供边缘计算服务。
示例地，参考图6，第二EES可以为EES-3，第一EAS可以为EAS-3，相关描述可以参考图6对应的方法实施例。
基于上述各种场景的示例性的描述，本申请提供了一种获取边缘计算服务的方法可以如图18所示，该方法可以应用于第一ECS，该方法可以包括如下步骤：
步骤1801、第一ECS向第四实体发送至少一个EES的信息，至少一个EES能够为第四实体提供边缘计算服务。
可选地，第四实体为第一EEC。
可选地该方法还可以包括：
步骤1802、第一ECS接收来自第一EEC的第一UE的位置信息、第一EEC期望的EDN信息、第一AC的信息中的至少一项信息。其中，第一EEC和第一AC部署在第一UE中。
步骤1803、第一ECS根据第一UE的位置信息、第一EEC期望的EDN信息、第一AC的信息中的至少一项信息，确定至少一个EES的信息。
示例地，第一ECS可以为图6中的ECS，第一EEC可以为图6中的EES-1，上述第一ECS的动作可以参考上述图6对应的方法实施例中ECS执行的动作的相关描述，此处不再赘述。
基于上述各种场景的示例性的描述，本申请提供了一种获取边缘计算服务的方法可以如图19所示，该方法可以应用于第二EEC，该方法可以包括如下步骤：
步骤1901、第二EEC向第四EES发送第二组的信息，第二组的信息用于确定为第二组包括的UE提供边缘计算服务的EAS。
可选地，第二EEC可以是部署在第二UE中的边缘使能客户端，该第二UE是第二组中的UE。第四EES为第二EEC直接订阅的EES。
示例地，如图14所示，第二EEC可以为EEC-0，第四EES可以为EES-1或EES-3。步骤1901可以通过步骤1407或步骤1409实现，可以参考图14对应的实施例中的相关描述，此处不再赘述。
步骤1902、第二EEC接收来自第四EES的第二EAS的信息，第二EAS能够为第二组包括的UE提供边缘计算服务。
示例地，如图14所示，第二EEC可以为EEC-0，第四EES为EES-1或EES-3。第二EAS可以为EAS-1或EAS-3，其中，EAS-1与EES-1关联，EAS-3与EES-3关联。步骤1901可以通过步骤1408或步骤1410实现，可以参考图14对应的实施例中的相关描述，此处不再赘述。
可选地，对于不同的第四EES，步骤1902可以执行多次，从而第二EEC可以获取到多个能够为第二组包括的UE提供边缘计算服务的EAS。进而，第二EEC可以在多个EAS中选择一个作为第二组对应的共同的EAS。
可选地，该方法还可以包括：步骤1903、第二EEC向第四EES发送第二业务信息。其中，第二业务信息是第二AC对应的业务信息，第二业务信息可以参考前文第一业务信息的相关描述，二者是类似的(将第二AC换成第一AC即可)，此处不再赘述。
可选地，第二AC可以是部署在第二UE中的应用客户端，第二AC、第二EEC、以及第二UE可以认为是同一主体。
可选地，第二业务信息也可以用于确定为第二组包括的UE提供边缘计算服务的EAS。第四EES在确定第二EAS时，可以参考第二业务信息进行确定，使得确定出的第二EAS可以更符合该第二组包括的UE的业务需求。
应理解，第二业务信息可以参考图6对应的方法实施例中AC-1对应的业务信息的相关描述，此处不再赘述。
可选地，该方法还可以包括：
步骤1904、第二EEC接收来自第二ECS的多个EES的信息。该多个EES的信息可以是第二ECS为第二EEC确定的可用的EES的信息。步骤1905可以参考步骤603的相关描述，此处不再赘述。
步骤1905、第二EEC确定第四EES。第四EES可以是第二EEC确定的需要使用的EES。步骤1905可以参考步骤604中的相关描述，此处不再赘述。
需要说明的是，第二ECS与第二EEC的交互可以参考第一ECS与第一EEC的交互，第二ECS所做的动作可以参考上述第一ECS所做的动作，此处不再赘述。
基于上述各种场景的示例性的描述，本申请提供了一种获取边缘计算服务的方法可以如图20所示，该方法可以应用于第四EES。该方法可以包括如下步骤：
步骤2001、第四EES接收来自第二EEC的第二组的信息。
步骤2002、第四EES根据第二组的信息确定第二EAS的信息，第二EAS能够为第二组包括的UE提供边缘计算服务。
步骤2003、第四EES向第二EEC发送第二EAS的信息。
其中，第二组的信息可以参考图6对应的实施例中组1的信息的相关描述，第二EAS的信息可以参考图6对应的实施例中至少一个EAS的信息的相关描述，此处不再赘述。
可选地，该方法还可以包括：步骤2004、第四EES接收来自第二EEC的第二业务信息。此种情况下，步骤2002具体可以为：第四EES根据第二组的信息和第二业务信息确定第二EAS的信息。其中，第二业务信息可以参考图6对应的实施例中AC-1对应的业务信息的相关描述，此处不再赘述。
可选地，本申请实施例中的EEC、EES、以及ECS可采用图21所示的组成结构或者包括图21所示的部件。图21为本申请实施例提供的一种通信装置210的结构示意图，如图21所示，该通信装置210包括 一个或多个处理器2101，通信线路2102，以及至少一个通信接口(图21中仅是示例性的以包括通信接口2103，以及一个处理器2101为例进行说明)，可选的还可以包括存储器2104。
处理器2101可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路2102可包括一通路，用于不同组件之间的通信。
通信接口2103，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口2103也可以是位于处理器2101内的收发电路，用以实现处理器的信号输入和信号输出。
存储器2104可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路2102与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器2104用于存储执行本申请方案的计算机执行指令，并由处理器2101来控制执行。处理器2101用于执行存储器2104中存储的计算机执行指令，从而实现本申请实施例中提供的通信方法。
或者，可选的，本申请实施例中，也可以是处理器2101执行本申请下述实施例提供的通信方法中的处理相关的功能，通信接口2103负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器2101可以包括一个或多个CPU，例如图21中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置210可以包括多个处理器，例如图21中的处理器2101和处理器2107。这些处理器中的每一个可以是一个单核(single-core)处理器，也可以是一个多核(multi-core)处理器。这里的处理器可以包括但不限于以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。
在具体实现中，作为一种实施例，通信装置210还可以包括输出设备2105和输入设备2106。输出设备2105和处理器2101通信，可以以多种方式来显示信息。例如，输出设备2105可以是液晶显示器(liquid crystal display，LCD)，发光二极管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备2106和处理器2101通信，可以以多种方式接收用户的输入。上述的通信装置210有时也可以称为通信装置，其可以是一个通用设备或者是一个专用设备。例如通信装置210可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备、上述终端设备，上述网络设备、或具有图21中类似结构的设备。本申请实施例不限定通信装置210的类型。
可选地，上述方法实施例中EEC的动作可以由图21所示的通信装置210中的处理器2101调用存储器2104中存储的应用程序代码以指令该EEC执行，EES的动作可以由图21所示的通信装置210中的处理器2101调用存储器2104中存储的应用程序代码以指令该EES执行，ECS的动作可以由图21所示的通信装置210中的处理器2101调用存储器2104中存储的应用程序代码以指令该ECS执行。
可选地，本申请实施例还提供了另一种通信装置，该通信装置用于实现上述各种方法。该通信装置可以为上述方法实施例中的目标节点，或者包含上述目标节点的装置，或者为可用于目标节点的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法实施例中对通信装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图22示出了一种通信装置220的结构示意图。该通信装置220可以包括收发模块2201。收发模块2201，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。可选地，该通信装置220还可以包括处理模块2202。
以通信装置220为上述方法实施例中的第一EEC为例：
收发模块2201，可以用于向第一实体发送至少一个EES的信息，至少一个EES能够为第一EEC提供边缘计算服务。收发模块2201，可以用于接收来自第一实体的至少一个EAS的信息，至少一个EAS与第一实体和/或至少一个EES关联，至少一个EAS能够为第一AC提供边缘计算服务。
可选地，收发模块2201，还可以用于向第一EES发送第一组的信息，第一组的信息可以用于确定为第一组包括的UE提供边缘计算服务的EAS。
可选地，收发模块2201，还可以用于接收第一组的信息，第一组的信息与至少一个EAS中的第一EAS关联，第一EAS能够为第一组包括的UE提供边缘计算服务。
可选地，处理模块2202，还可以用于第一EEC从至少一个EAS中确定第一EAS，第一EAS能够为第一组包括的UE提供边缘计算服务。
可选地，收发模块2201，还可以用于向第一EES发送第一EAS的信息。
可选地，收发模块2201，还可以用于向第一EES发送第一业务信息，第一业务信息用于确定至少一个EAS。
可选地，收发模块2201，还可以用于接收来自第一边缘配置服务器ECS的至少一个EES的信息。
可选地，处理模块2202，还可以用于根据从第一ECS接收到的至少一个EES的信息，确定向第一实体发送的至少一个EES的信息。
以通信装置220为上述方法实施例中的第一EES为例：
收发模块2201，可以用于接收来自第二实体的至少一个EES的信息，至少一个EES的信息用于确定能够为第二实体提供边缘计算服务的EES。
可选地，收发模块2201，还可以用于向第一EEC发送至少一个EAS的信息，至少一个EAS能够为第一AC提供边缘计算服务。
可选地，收发模块2201，还可以用于接收来自第一EEC的第一组的信息，第一组的信息用于指示第一组包括的用户设备UE的信息。
可选地，收发模块2201，还可以用于向至少一个EES发送第一组的信息。
可选地，收发模块2201，还可以用于向第一EEC发送第一EAS关联的第一组的信息，第一EAS为至少一个EAS中的一个EAS，第一EAS能够为第一组包括的UE提供边缘计算服务。
可选地，收发模块2201，还可以用于接收来自第一EEC的第一EAS的信息，第一EAS属于至少一个EAS，第一EAS能够为第一组包括的UE提供边缘计算服务。
可选地，收发模块2201，还可以用于向至少一个EES发送第一EAS的信息。
可选地，收发模块2201，还可以用于接收来自第一EEC的第一业务信息，第一业务信息用于确定至少一个EAS。
可选地，收发模块2201，还可以用于向至少一个EES发送第一业务信息。
以通信装置220为上述方法实施例中的第二EES为例：
收发模块2201，可以用于接收来自第三实体的第一组的信息，第一组的信息可以用于确定为第一组包括的UE提供边缘计算服务的EAS。
可选地，收发模块2201，还可以用于向第一EES发送第一EAS的信息，第一EAS能够为第一组包括的UE提供边缘计算服务。
可选地，收发模块2201，还可以用于接收来自第一EES的第一EAS的信息，第一EAS能够为第一组包括的UE提供边缘计算服务。
可选地，收发模块2201，还可以用于接收来自第一EES的第一业务信息，第一业务信息用于确定第一EAS。
以通信装置220为上述方法实施例中的第一ECS为例：
收发模块2201，可以用于向第四实体发送至少一个EES的信息，至少一个EES能够为第四实体提供边缘计算服务。
可选地，收发模块2201，还可以用于接收来自第一EEC的第一UE的位置信息，第一UE的位置信息用于确定至少一个EES的信息。
可选地，收发模块2201，还可以用于接收来自第一EEC的第一UE期望的EDN信息、边缘计算服务层级信息或者EES服务层级信息。该第一UE期望的EDN信息、边缘计算服务层级信息或者EES服务层级信息用于确定至少一个EES的信息。
可选地，处理模块2202，可以用于根据第一UE的位置信息确定第一UE可用的EDN。以及，处理模块2202，还可以用于根据策略信息，从第一UE可用的EDN中确定多个EES的信息。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。由于本实施例提供的通信装置220可执行上述通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例中的EEC、EES、或者ECS也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
在本实施例中，该通信装置220以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置220可以采用图21所示的通信装置210的形式。
比如，图21所示的通信装置210中的处理器2101可以通过调用存储器2104中存储的计算机执行指令，使得通信装置210执行上述方法实施例中的通信方法。
具体的，图22中的收发模块2201和处理模块2202的功能/实现过程可以通过图21所示的通信装置210中的处理器2101调用存储器2104中存储的计算机执行指令来实现。或者，图22中的收发模块2201的功能/实现过程可以通过图21中所示的通信装置210中的通信接口2103来实现，图22中的处理模块2202的功能/实现过程可以通过图21所示的通信装置210中的处理器2101调用存储器2104中存储的计算机执行指令来实现。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指 令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
如本申请所使用的，术语“组件”、“模块”、“系统”等等旨在指代计算机相关实体，该计算机相关实体可以是硬件、固件、硬件和软件的结合、软件或者运行中的软件。例如，组件可以是，但不限于是：在处理器上运行的处理、处理器、对象、可执行文件、执行中的线程、程序和/或计算机。作为示例，在计算设备上运行的应用和该计算设备都可以是组件。一个或多个组件可以存在于执行中的过程和/或线程中，并且组件可以位于一个计算机中以及/或者分布在两个或更多个计算机之间。此外，这些组件能够从在其上具有各种数据结构的各种计算机可读介质中执行。这些组件可以通过诸如根据具有一个或多个数据分组(例如，来自一个组件的数据，该组件与本地系统、分布式系统中的另一个组件进行交互和/或以信号的方式通过诸如互联网之类的网络与其它系统进行交互)的信号，以本地和/或远程过程的方式进行通信。
本申请围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例中，信息(information)，信号(signal)，消息(message)，信道(channel)有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“的(of)”，“相应的(corresponding，relevant)”和“对应的(corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。“系统”和“网络”有时可以混用，在不强调其区别时，其所要表达的含义是一致的，比如，“通信网络”也即是指“通信系统”。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (34)

  1. 一种获取边缘计算服务的方法，其特征在于，所述方法包括：
    第一边缘使能服务器EES接收来自第一边缘使能客户端EEC的用户设备UE组的信息、至少一个EES的信息、和至少一个EAS的信息，所述至少一个EES中的第二EES为所述UE组包括的UE服务，所述至少一个EAS与所述第二EES对应，且为所述UE组包括的UE服务；
    所述第一EES向所述至少一个EES发送所述EAS的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述UE组的信息包括作数UE组的标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述至少一个EES的信息包括所述至少一个EES的地址信息。
  4. 一种获取边缘计算服务的方法，其特征在于，所述方法包括：
    第一边缘使能服务器EES接收来自第一边缘使能客户端EEC的至少一个EES的信息，所述至少一个EES的信息用于确定能够为所述第一EEC提供边缘计算服务的EES。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    所述第一EES向所述第一EEC发送所述至少一个EAS的信息，所述至少一个EAS能够为第一应用客户端AC提供边缘计算服务。
  6. 根据权利要求4或5所述的方法，其特征在于，所述方法还包括：
    所述第一EES接收来自所述第一EEC的第一组的信息，所述第一组的信息用于指示所述第一组包括的用户设备UE的信息。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一EES向所述至少一个EES发送所述第一组的信息，所述第一组的信息包括组标识和/或UE列表。
  8. 根据权利要求6或7所述的方法，其特征在于，所述方法还包括：
    所述第一EES向所述第一EEC发送第一EAS关联的第一组的信息，所述第一EAS为所述至少一个EAS中的一个EAS，所述第一EAS能够为所述第一组包括的UE提供边缘计算服务。
  9. 根据权利要求8所述的方法，其特征在于，所述第一EAS与所述第一EES对应，所述第一EAS的信息是所述第一EES确定的。
  10. 根据权利要求8所述的方法，其特征在于，所述第一EAS与所述至少一个EES中的第二EES对应，所述第二EES能够为所述第一组包括的UE提供边缘计算服务，所述第一EAS的信息是所述第一EES从所述第二EES接收到的。
  11. 根据权利要求8至10任一项所述的方法，其特征在于，所述方法还包括：
    所述第一EES接收来自所述第一EEC的第一EAS的信息，所述第一EAS属于所述至少一个EAS，所述第一EAS能够为所述第一组包括的UE提供边缘计算服务。
  12. 根据权利要求7至11任一项所述的方法，其特征在于，所述方法还包括：
    所述第一EES向所述至少一个EES发送所述第一EAS的信息。
  13. 根据权利要求4-12任一项所述的方法，其特征在于，所述方法还包括：
    所述第一EES接收来自所述第一EEC的第一业务信息，所述第一业务信息用于确定所述至少一个EAS。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第一EES向所述至少一个EES发送所述第一业务信息。
  15. 根据权利要求4-14任一项所述的方法，其特征在于，所述EES对应的部署信息包括以下至少一项：EES的EDN信息、EES的拓扑服务范围、EES的地理服务范围、EES对应的数据网络接入标识符DNAI、或EES所属的层级。
  16. 一种获取边缘计算服务的方法，其特征在于，所述方法包括：
    第二边缘使能服务器EES接收来自第一EES的第一组的信息，所述第一组的信息用于确定为所述第一组包括的UE提供边缘计算服务的边缘应用服务器EAS。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述第二EES向所述第一EES发送第一EAS的信息，所述第一EAS能够为所述第一组包括的UE提 供边缘计算服务。
  18. 根据权利要求17所述的方法，其特征在于，所述第一EAS与所述第二EES对应，所述第一EAS是所述第二EES确定的。
  19. 根据权利要求16-18任一项所述的方法，其特征在于，所述方法还包括：
    所述第二EES接收来自所述第一EES的第一EAS的信息，所述第一EAS能够为所述第一组包括的UE提供边缘计算服务。
  20. 根据权利要求16-19任一项所述的方法，其特征在于，所述方法还包括：
    所述第二EES接收来自所述第一EES的第一业务信息，所述第一业务信息用于确定所述第一EAS。
  21. 一种获取边缘计算服务的方法，其特征在于，所述方法包括：
    第一边缘使能客户端EEC向第一边缘使能服务器EES发送至少一个EES的信息，所述至少一个EES能够为所述第一EEC提供边缘计算服务；
    所述第一EEC接收来自所述第一EES的至少一个边缘应用服务器EAS的信息，所述至少一个EAS与所述第一EES和/或所述至少一个EES对应，所述至少一个EAS能够为第一应用客户端AC提供边缘计算服务。
  22. 根据权利要求21所述的方法，其特征在于，所述方法还包括：
    所述第一EEC向所述第一EES发送第一组的信息，所述第一组的信息用于确定为所述第一组包括的用户设备UE提供边缘计算服务的EAS，所述第一组的信息包括组标识和/或UE列表。
  23. 根据权利要求21或22所述的方法，其特征在于，所述方法还包括：
    所述第一EEC接收所述第一组的信息，所述第一组的信息与所述至少一个EAS中的第一EAS关联，所述第一EAS能够为所述第一组包括的UE提供边缘计算服务。
  24. 根据权利要求21-23任一项所述的方法，其特征在于，所述第一EAS与所述至少一个EES中的第二EES对应，所述第二EES能够为所述第一组包括的UE提供边缘计算服务。
  25. 根据权利要求21或22所述的方法，其特征在于，所述方法还包括：
    所述第一EEC从所述至少一个EAS中确定第一EAS，所述第一EAS能够为所述第一组包括的UE提供边缘计算服务；
    所述第一EEC向所述第一EES发送所述第一EAS的信息；
    其中，所述第一EAS与所述第一EES对应。
  26. 根据权利要求21-25任一项所述的方法，其特征在于，所述方法还包括：
    所述第一EEC向所述第一EES发送第一业务信息，所述第一业务信息用于确定所述至少一个EAS。
  27. 根据权利要求21-26所述的方法，其特征在于，所述至少一个EES的信息中任一个EES的信息包括以下至少一项：EES的标识信息、EES的地址信息、或者EES对应的部署信息。
  28. 根据权利要求21-27任一项所述的方法，其特征在于，所述方法还包括：
    所述第一EEC接收来自第一边缘配置服务器ECS的至少一个EES的信息。
  29. 根据权利要求28所述的方法，其特征在于，所述方法还包括：
    所述第一EEC根据从所述第一ECS接收到的至少一个EES的信息，确定向所述第一EES发送的至少一个EES的信息。
  30. 一种获取边缘计算服务的方法，其特征在于，所述方法包括：
    第一边缘配置服务器ECS向第一边缘使能客户端EEC发送至少一个边缘使能服务器EES的信息，所述至少一个EES能够为所述第一EEC提供边缘计算服务。
  31. 根据权利要求30所述的方法，其特征在于，所述至少一个EES的信息中任一个EES的信息包括以下至少一项：EES的标识信息、EES的地址信息、或者EES对应的部署信息。
  32. 一种通信装置，其特征在于，所述通信装置包括：处理器和存储器；
    所述存储器用于存储计算机执行指令，当所述处理器执行所述计算机执行指令时，以使所述通信装置执行如权利要求1-31中任一项所述的方法。
  33. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，当所述计算机程序被计算机执行时使得所述计算机执行权利要求1-31中任一项所述的方法。
  34. 一种通信系统，其特征在于，包括：
    用于执行如权利要求1-31中任一项所述方法的一个或多个通信装置。
PCT/CN2023/127925 2022-11-07 2023-10-30 一种获取边缘计算服务的方法、通信系统及装置 WO2024099147A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211385370.2A CN117998333A (zh) 2022-11-07 2022-11-07 一种获取边缘计算服务的方法、通信系统及装置
CN202211385370.2 2022-11-07

Publications (1)

Publication Number Publication Date
WO2024099147A1 true WO2024099147A1 (zh) 2024-05-16

Family

ID=90885936

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/127925 WO2024099147A1 (zh) 2022-11-07 2023-10-30 一种获取边缘计算服务的方法、通信系统及装置

Country Status (2)

Country Link
CN (1) CN117998333A (zh)
WO (1) WO2024099147A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022176426A1 (ja) * 2021-02-17 2022-08-25 日本電気株式会社 サーバ、要求エンティティ、及びこれらの方法
CN114980223A (zh) * 2021-02-24 2022-08-30 华为技术有限公司 一种通信方法及装置
CN116896558A (zh) * 2022-03-30 2023-10-17 华为技术有限公司 一种通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022176426A1 (ja) * 2021-02-17 2022-08-25 日本電気株式会社 サーバ、要求エンティティ、及びこれらの方法
CN114980223A (zh) * 2021-02-24 2022-08-30 华为技术有限公司 一种通信方法及装置
CN116896558A (zh) * 2022-03-30 2023-10-17 华为技术有限公司 一种通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhanced architecture for enabling Edge Applications; (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-98, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V1.3.0, 28 October 2022 (2022-10-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 225, XP052211695 *

Also Published As

Publication number Publication date
CN117998333A (zh) 2024-05-07

Similar Documents

Publication Publication Date Title
JP7047113B2 (ja) アプリケーションのサービスレベル合意を保証するための方法、デバイスおよびシステム
US11445039B2 (en) Method and apparatus for providing edge computing services
US9906464B2 (en) Optimization of multimedia service over an IMS network
EP3005822B1 (en) Mac layer transport for wi-fi direct services application service platform without internet protocol
WO2020063213A1 (zh) 本地局域网通信方法、设备及系统
WO2021135663A1 (zh) 应用实例确定的方法、装置及系统
JP2021518075A (ja) サービス加入方法および装置
US8102846B2 (en) Method and apparatus for managing a multicast tree using a multicast tree manager and a content server
EP3654619B1 (en) A dynamic content distribution protocol for an enterprise environment
US10270622B2 (en) Method for enabling mobility of client devices in large scale unified networks
WO2014164342A1 (en) Exchanging a contact profile between client devices during a communication session
WO2021136180A1 (zh) 一种业务处理的方法、装置和系统
WO2014190791A1 (zh) 一种网关设备身份设置的方法及管理网关设备
CN112533177A (zh) 一种提供、发现移动边缘计算的方法及设备、装置、介质
WO2021170033A1 (zh) 一种网络配置方法及装置
CN110768818B (zh) 一种网络管理方法和装置
US11489762B2 (en) Distributed sub-controller permission for control of data-traffic flow within software-defined networking (SDN) mesh network
WO2024099147A1 (zh) 一种获取边缘计算服务的方法、通信系统及装置
WO2018113633A1 (zh) 报文转发方法、报文转发控制器、bras、计算机存储介质
TW201101737A (en) IPMI server system and method thereof
WO2019184725A1 (zh) 一种更新配置的方法及装置
JP2020061135A (ja) 企業ネットワーク内の動的コンテンツ配信
WO2023185567A1 (zh) 发现应用服务器的方法和装置
WO2023241465A1 (zh) T-ees发现方法及相关装置
WO2024016333A1 (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: 23887837

Country of ref document: EP

Kind code of ref document: A1