Vertical applications in edge computing

Abstract

To provide a method that is performed by a first network function implementing an edge enabler server (EES) in an edge data network (EDN), regarding a vertical application in edge computing.SOLUTION: A method includes at least a step in which, in an EDN, an EES (421) receives, from a second network function (422) implementing an edge application server (EAS), a registration request message including information pointing to a first list of associated EAS information. Based on the associated EAS information, user equipment performs joint EAS discovery and selection for a vertical application in an edge deployment, thereby both of an application enabler client and an application-specific server in the user equipment communicating with the same application enabler server.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] Embodiments in the present specification relate generally to the field of communications, and more specifically, the embodiments in the present specification relate to vertical applications in edge computing.

Background Art

[0002] Vertical Applications and SEAL Figure 1 is a schematic block diagram illustrating an architecture 100 for 5G vertical applications proposed by the 3GPP SA6 working group. In 3GPP Release 16, a Service Enabler Architecture Layer (SEAL) 112 was introduced to support vertical applications (e.g., V2X (Vehicle to Everything) applications).

[0003] 3GPP TS 23.434 specifies application plane and signaling plane entities for application enabling services (e.g., group management, configuration management, location management, identity / key management, network resource management), which can be reused across vertical applications. In addition, SEAL specifies northbound application programming interfaces (APIs) for individual services of SEAL to enable flexible integration with vertical applications.

[0004] To enable smart factories in manufacturing, the 3GPP SA6 Working Group is also studying application-enabling services aimed at the schematic applicability of the Factory of the Future (FF) based on the service requirements for cyber-physical control applications identified in 3GPP TS 22.104 and 3GPP TS 22.261, and is developing corresponding solutions to ensure the efficient use and deployment of application layer support for FF in 5G networks. The research is captured in 3GPP TR 23.745.

[0005] Factory of the Future (FF) Regarding FF applications (apps), one proposed architecture in the study (Section 7.1 of TR 23.745) is shown in Figure 2, which is a schematic block diagram showing the application layer architecture 200 for FF.

[0006] The FF application layer functional entities 213 and 223 for the FF user equipment (UE) 201 and FF application server are grouped into the FF application-specific layer and the FF application enabler (FAE) layer. The FAE layer provides FAE capabilities to the FF application-specific layer. The FF application-specific layer consists of FF application-specific functionality.

[0007] The FF Application Server (AS) consists of an FAE server 222 and an FF application-specific server 223. The FAE server 222 provides FF application layer support functions to the FF application-specific server 223 via an FAE-S reference point.

[0008] FF UE201 consists of an FAE client 212 and an FF application-specific client 213. The FAE client 212 provides FF application layer support functionality to the FF application-specific client 213 via an FAE-C reference point.

[0009] FAE server 222 interacts with another FAE server 222 via an FAE-E reference point.

[0010] The FAE server 222 (acting as an AF) interacts with the 3GPP system 202, such as the 5G system (5GS), via the N5 reference point, as specified in 3GPP TS 23.501[7]. The FAE server 222 also interacts with the 3GPP system 202 (such as 5GS) via the N33 reference point, as specified in 3GPP TS 23.501[7].

[0011] The FF application-specific server 223 and the FF application enabler server 222 consume SEAL services provided by the SEAL server 221 via the SEAL-S reference point. The FF application-specific client 213 and the FF application enabler client 212 consume SEAL services provided by the SEAL client 211 via the SEAL-C reference point.

[0012] The following SEAL services for FF applications are supported. - Location management as specified in 3GPP TS 23.434 - Group management as specified in 3GPP TS 23.434 -Configuration management specified in 3GPP TS 23.434 - Identification information management as specified in 3GPP TS 23.434 -Key management as specified in 3GPP TS 23.434 - Network resource management as specified in 3GPP TS 23.434

[0013] Edge applications 3GPP TS 23.558 specifies the application layer architecture, procedures, and information flows required to enable edge applications over 3GPP networks. 3GPP TS 23.558 includes the architectural requirements for enabling edge applications, the application layer architecture that satisfies these architectural requirements, and the procedures for enabling the deployment of edge applications.

[0014] To support edge computing, the objectives include the exposure of northbound APIs for edge applications and the development of application layer requirements and architectures for hosting edge applications on edge data networks (EDNs), including the integration of the edge enabling layer with 3GPP networks.

[0015] Figure 3 is a schematic block diagram showing architecture 300 for enabling edge applications. EDN302 is the local data network. The edge application server (EAS) 322 and edge enabler server (EES) 321 are contained within EDN302. The edge configuration server (ECS) 304 provides configuration related to EES321, including details of EDN302 hosting EES321. UE301 contains application clients 312 and edge enabler clients (EEC) 311. EAS322, EES321, and ECS304 can interact with the 3GPP core network 303. [Overview of the project]

[0016] Current technical specifications lack a solution for how vertical applications, such as FF-specific applications (both client and server), can utilize edge application services.

[0017] In view of the foregoing, the embodiments herein propose an integrated view for the UE to select application servers deployed at the edge, and in particular to facilitate the use of different applications and enablers in vertical domains when there is some relationship between those servers.

[0018] In this embodiment, we propose a first method implemented by a first network function that implements an edge enabler server (EES) in an edge data network (EDN). The method may include the step of receiving a registration request message from a second network function that implements an edge application server (EAS) in the EDN, the second network function having information pointing to a list of relevant EAS information.

[0019] In another embodiment, we propose a second method implemented by a second network function that implements an edge application server (EAS) in an edge data network (EDN). The method may include sending a registration request message to a first network function that implements an edge enabler server (EES) in the EDN, the message containing information pointing to a first list of relevant EAS information.

[0020] In another embodiment, a third method is proposed, implemented by a first network function that implements an edge enabler server (EES) in an edge data network (EDN). The method may comprise the step of receiving a first message from a functional component of a user device (UE) to discover at least one second network function that implements an edge application server (EAS) in the EDN. The method may further comprise the step of sending a second message to the functional component of the UE, which contains information pointing to a first list of relevant EAS information.

[0021] In another embodiment, a fourth method is proposed, which is implemented by a first functional component in a user device (UE). The method may comprise the step of sending a first message to a first network function implementing an edge enabler server (EES) in an edge data network (EDN) to discover at least one second network function implementing an edge application server (EAS) in the EDN. The method may further comprise the step of receiving a second message from the first network function, which contains information pointing to a first list of relevant EAS information.

[0022] In another embodiment, a fifth method is proposed, which is implemented by a second functional component in a user device (UE). The method may further comprise the step of receiving a message from a first functional component in the UE that contains information pointing to a list of relevant edge application server (EAS) information.

[0023] Another embodiment proposes a user device (UE) comprising multiple functional components. These functional components further include a first functional component implementing an edge enabler client (EEC), a third functional component implementing an application enabler client for a vertical application, and a fourth functional component implementing an application-specific client for a vertical application. The third functional component may provide at least one service to one or more fourth functional components. The first and third functional components may communicate via an edge-5 reference point to enable at least one service.

[0024] In still another embodiment, a communication system for vertical applications in edge deployment is proposed, the communication system comprising a plurality of network functions in an edge data network (EDN). The plurality of network functions further includes a first network function implementing an edge enabler server (EES), a third network function implementing an application enabler server for a vertical application, and a fourth network function implementing an application-specific server for the vertical application. The third network function may provide at least one service to one or more fourth network functions. The first network function and the third network function may communicate via an Edge-3 reference point to enable the at least one service.

[0025] In still another embodiment, a first network function implementing an edge enabler server (EES) in an edge data network (EDN) is proposed. The EES comprises at least one processor and a non-transitory computer-readable medium coupled to the at least one processor. The non-transitory computer-readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to perform the aforementioned first method and third method.

[0026] In still another embodiment, a second network function implementing an edge application server (EAS) in an edge data network (EDN) is proposed. The EAS comprises at least one processor and a non-transitory computer-readable medium coupled to the at least one processor. The non-transitory computer-readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to perform the aforementioned second method.

[0027] In yet another embodiment, a user equipment (UE) is proposed, comprising at least one processor and a non-transitory computer-readable medium coupled to the at least one processor. The non-transitory computer-readable medium contains instructions executable by the at least one processor, whereby the at least one processor is configured to implement the fourth method and the fifth method described above.

[0028] In yet another embodiment, a computer-readable medium is proposed, comprising computer-readable code that, when run on an apparatus, causes the apparatus to perform any of the methods described above.

[0029] In yet another embodiment, a computer program product is proposed, comprising computer-readable code that, when run on an apparatus, causes the apparatus to perform any of the methods described above.

[0030] With the embodiments herein, based on the relevant EAS information, the UE may perform joint EAS discovery and selection for vertical applications in edge deployment, whereby both the application enabler client and the application-specific server at the UE may communicate with the same application enabler server.

[0031] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate various embodiments of the present disclosure, and together with the description, serve to explain the principles of the present disclosure and to enable a person skilled in the art to make and use the embodiments disclosed herein. In the drawings, like reference numerals refer to equivalent or functionally similar elements. [Brief Description of the Drawings]

[0032] [Figure 1] 1 is a schematic block diagram illustrating an architecture for 5G vertical applications proposed by the 3GPP SA6 working group. [Figure 2]This is a schematic block diagram showing the application layer architecture for FF. [Figure 3] This is a schematic block diagram showing the architecture for enabling edge applications. [Figure 4] This schematic block diagram shows an exemplary wireless communication system in which embodiments of this specification may be implemented. [Figure 5] This is a schematic block diagram illustrating a more versatile edge deployment for vertical applications. [Figure 6] This is a schematic signaling chart showing messages in vertical EAS registration during edge deployment. [Figure 7] This is a schematic signaling chart showing messages in vertical EAS discovery request responses during edge deployment. [Figure 8] This is a schematic signaling chart showing messages in vertical EAS discovery notifications during edge deployment. [Figure 9] This is a schematic flowchart illustrating an exemplary EAS registration method performed by a first network function according to embodiments of this specification. [Figure 10] This is a schematic flowchart illustrating an exemplary EAS registration method performed by a second network function according to embodiments of this specification. [Figure 11] This is a schematic flowchart illustrating an exemplary EAS discovery method performed by a first network function according to embodiments described herein. [Figure 12] This is a schematic flowchart illustrating an exemplary EAS discovery method performed by a first functional component in the UE according to embodiments herein. [Figure 13] This is a schematic flowchart illustrating an exemplary EAS discovery method performed by a second functional component in the UE according to embodiments herein. [Figure 14] This is a schematic block diagram illustrating an exemplary first network function according to embodiments of this specification. [Figure 15] This is a schematic block diagram illustrating an exemplary second network function according to embodiments of this specification. [Figure 16] This is a schematic block diagram showing an exemplary UE according to embodiments of this specification. [Figure 17] This is a schematic block diagram showing an exemplary computer implementation according to embodiments described herein. [Modes for carrying out the invention]

[0033] Embodiments described herein are described in detail below with reference to the accompanying drawings in which the embodiments are shown. However, these embodiments described herein may be embodied in many different forms and should not be construed as being limited to the embodiments described herein. The elements of the drawings are not necessarily to a constant scale relative to one another.

[0034] References to “one embodiment” or “an embodiment” mean that certain features, structures, or characteristics described in relation to an embodiment are included in at least one embodiment. Thus, occurrences of the phrase “in an embodiment” in various places throughout this specification do not necessarily all refer to the same embodiment.

[0035] As used herein, the terms "A, B, or C" mean "A" or "B" or "C", as used herein, the terms "A, B, and C" mean "A" and "B" and "C", and as used herein, the terms "A, B, and / or C" mean "A", "B", "C", "A and B", "A and C", "B and C", or "A, B, and C".

[0036] The following describes a future factory application as an example of a vertical application in one embodiment of this disclosure.

[0037] There is a major issue #9 described in TR 23.745, section 5.9, and existing solutions #5 and #6 place the FF enabler (client and server) as EAS in the context of the edge application architecture. However, it is unclear how FF-specific applications (client and server) can utilize edge application services.

[0038] According to Section 5.1 of TS 22.104, a local approach for network-side communication services is preferred to reduce latency (between UEs via Uu and between UEs and network servers) or to keep sensitive data on non-public networks within the factory premises. In that case, the question remains as to how to support FFAPP communication via network-side edge deployment.

[0039] In FFAPP TR 23.745, according to Solution #4 (for device onboarding support), the FAE client 212 registers with the FAE server 222 via the FAE-1 reference point. The FF application-specific client 213 registers with the FAE client 212 via the FAE-C reference point. The FF application-specific server 223 also registers with the FAE server 222 via the FAE-S reference point.

[0040] According to Solution #4, the FFAS server 223 must register with the FAE server 222, and the FAE client 212 must also register with the FAE server 222. However, from a UE perspective, under edge deployment, the EAS discovery service provided by the edge app is used, but if the selection of the FFAS server 223 and the FAE server 222 is handled separately, the selected FAE server 222 will not retain the registered FFAS server 223, and as a result, some functions may not work as expected. For example, the FF application-specific server 223 may not be able to discover the FF device application management relationship IE stored in the FAE client 212 via the FAE server 222, or the FAE client 212 may not be able to send the device application management operation results to the FF application-specific server 223 via the FAE server 222.

[0041] Generally speaking, in edge deployments, when the application enabler client and application-specific server in the UE need to communicate with the same application enabler server, the selection of the application enabler server and the application-specific server lacks some degree of coordination.

[0042] In view of the above issues, the embodiments herein provide additional information, namely related EAS information, in the EAS registration procedure to describe the relationships between servers. This additional information can help the UE select the appropriate EAS using an integrated view.

[0043] Edge computing for FFAPP The solution in this disclosure addresses the above-mentioned critical issue #9, namely, communication services at edge deployments. Table numbers, subordinate section numbers, etc., are found in 3GPP TR 23.745 V1.2.0.

[0044] The edge application architecture is specified in 3GPP TS 23.558

[10] . Details of the edge-5 reference point are not specified in Rel-17.

[0045] Figure 4 illustrates an example of edge deployment 400 for an FF application. For simplicity, the reference point between the enabler server and 5GS is omitted, as is the reference point for inter-enabler server communication in the same enabler layer. On the UE 401 side, the FF application-specific client 414 and FAE client 413 interact with the edge enabler client (EEC) 411 via the edge-5 reference point. On the edge data network (EDN) 402, the edge application servers (EAS), for example, the FF application-specific server 424 and the FF application enabler server 423, interact with the edge enabler server (EES) 421 via the edge-3 reference point, for example, to register their profiles with the EES 421. The EEC 411 interacts with the edge configuration server (ECS) 404 via the edge-4 reference point, for example, to discover candidate EESs. EEC411 interacts with EES421 via an edge-1 reference point, for example, to discover candidate EAS (e.g., FF application-specific server 424 and FF application enabler server 423) and to provide the discovered EAS to application clients (e.g., FF application-specific client 414 and FF application enabler client 413).

[0046] In EDN402, there may be several EESs provided by the same or different edge computing service providers (ECSPs). The FFAS server 424 and FAE server 423 can discover and register with the appropriate EES 421. If CAPIF is used, this may be done by utilizing the AEF serving area and / or AEF location as described in 3GPP TS 23.222

[16] , otherwise the local configuration of the EES endpoint may be used.

[0047] In sol#4, the FFAS server 424 needs to register with the FAE server 423, and the FAE client 413 needs to register with the FAE server 423 during the onboarding process. Similarly, the FFAS server 424 can discover the appropriate FAE server 423 and register with it. Ideally, the FFAS server 424, FAE server 423, and EES 421 are all located in the same area to achieve low-latency communication between servers in edge deployments. However, from a UE perspective, under edge deployment, while the EAS discovery service provided by the edge enablers 411 / 421 is used, if the selection of FFAS server 424 and FAE server 423 is handled separately, the selected FFAS server 424 may not be onboarded onto the selected FAE server 423, thereby potentially preventing certain functions from operating. For example, the FF application-specific server 424 may not be able to discover FF device application management relationships IE stored in the FAE server 413, or the FAE client 413 may not be able to send device application management operation results to the FF application-specific server 424.

[0048] In order to enable the selection of FFAS server 424 and the onboarding FAE server 423 for FFAS server 424, in edge deployment, FFAS server 424 and FAE server 423 need to exchange application server information during onboarding. After both have stored the relevant application server information, FAE server 423 and FFAS server 424 register with EES 421 via edge-3 reference point. As a result, EEC 411 can discover a list of candidate FAE server 423, including its associated FFAS server 424, and a list of candidate FFAS server 424, including its associated FAE server 423, based on interaction with FAE client 413 via edge-5 reference point.

[0049] Regarding SEAL, the sparse administrative procedures specified in 3GPP do not impose such associations between VAL servers 423, 424 and SEAL server 422. Regarding SEAL Identification Management (IM) functionality, SEAL IM client 412 must register with SEAL IM server 422, as described in 3GPP TS 33.434 [TS33434], before any token is granted by SEAL IM server 422. If there is interaction between VAL servers 423, 424 and SEAL IM server 422 for token validity verification purposes, which is outside the scope of 3GPP (and furthermore, IETF RFC 6749 [rfc6749]), EAS discovery must take into account the association between the VAL server (e.g., FAE server 423) and SEAL IM server 424.

[0050] In UE401, there are several ways to achieve the selection of associated EAS servers 422, 423, and 424, and the following list describes two alternative forms for informational purposes, as neither FAE-C nor Edge-5 are detailed within the Rel-17 timeline.

[0051] a. Separately via the Edge-5 reference point, FFAS client 414 discovers FFAS server 424, and FAE client 413 discovers FAE server 423. The final selection of FFAS server 424 and FAE server 423 relies on coordination between FFAS client 414 and FAE client 413 via the FAE-C reference point.

[0052] b. The FFAS client 414 may also delegate the discovery of the FFAE server 424 to the FAE client 413 via the FAE-C reference point, in which case the FAE client 413 triggers discovery (with a request to discover the FAE server 423 as well, if applicable), and further selects an FFAE server 424 that matches the selected FAE server 423 from the discovered results.

[0053] According to 3GPP TS 23.558

[10] , when EEC411 provides discovery results to application clients 412, 413, and 414, it may narrow down the number of discovered application servers 422, 423, and 424. When such functionality in EEC411 is used (for example, delegated by application clients 412, 413, and 414), EEC411 will not narrow down the number of discovered application servers 422, 423, and 424 based on only a single application with relevant EAS information.

[0054] Table 1 shows the impact on the EAS profile, including a list of relevant EAS information (in bold and italics). In the FFAE server 424 profile, the onboarded FAE server 423 is provided as the parent EAS. In the FAE server 423 profile, one or more onboarded FFAS servers 424 are provided as child EAS. TIFF0007933951000001.tif77170

[0055] Note that other edge-3 exposed services are not republished to FFAS server 424 by FAE server 423 or SEAL server 422, and FFAS server 424 directly consumes location or QoS APIs provided by EES 421, for example.

[0056] Solution Evaluation This solution addresses the critical issue #9, "How to support FFAPP communication via edge deployment," and provides deployment options for FF applications in edge application architectures.

[0057] In such a scenario, if there is a relationship between the FFAS server 424 and the FAE server 423 with respect to the onboarding process, the relevant EAS information must be provided during the EAS registration procedure, and UE401 must select a suitable application server using joint consideration of the associated application servers.

[0058] Furthermore, EEC411 may be explicitly pointed to for EAS association in an EAS discovery request or EAS discovery subscription request so that only EAS422, 423, and 424 with EAS associations are discovered.

[0059] The benefit of this is that it narrows down the number of discovered EAS422, 423, and 424 in the discovery response / notification, allowing UE401 to process less information in selecting EAS422, 423, and 424 using the integrated view.

[0060] As described above, Figure 4 is a schematic block diagram showing an exemplary wireless communication system 400 in which embodiments of the herein may be implemented. In particular, Figure 4 shows an FF application in edge deployment.

[0061] The Edge-1 reference point in Figure 4 enables interaction between EES421 and EEC411. The Edge-1 reference point supports a) registration and unregistration of EEC411 to EES421, b) retrieval and provisioning of EAS configuration information, and c) discovery of available EAS in EDN402.

[0062] The Edge-3 reference point in Figure 4 enables interaction between EES421 and EAS422, 423, and 424. The Edge-3 reference point supports a) registering EAS422, 423, and 424 with availability information (e.g., time constraints, location constraints), b) unregistering EAS422, 423, and 424 from EES421, c) discovering target EAS information to support application context transfer, d) providing access to network capability information (e.g., location information, quality of service (QoS) relationship information), and e) requesting the setup of a data session between application clients 412, 413, and 414 and EAS422, 423, and 424 with a specific QoS.

[0063] In the examples herein, the SEAL server 422, FAE server 423, and FFAS server 424 can all function as EAS from the perspective of EES 421, and it should be noted that the SEAL server 422, FAE server 423, and FFAS server 424 may also be referred to as EAS422, EAS423, and EAS424, respectively. Similarly, the SEAL client 412, FAE client, and FFAS client 414 may be referred to as application clients 412, 413, and 414, respectively.

[0064] Figure 5 is a schematic block diagram illustrating a more general edge deployment 500 for vertical applications. More specifically, Figure 5 shows edge deployment options for supporting applications (application-specific servers and their enabler servers) in vertical domains (e.g., future factories, V2X, unmanned aerial systems). In Figure 5, different application clients and servers are separated into different application layers.

[0065] In Figure 5, the reference point name between the two entities is a string concatenated with a dash delimiter between the two uppercase entity names followed by a single character c or s (correspondingly representing the client or server).

[0066] As shown in Figure 5, server B523 has associations with server D524 as a child EAS, with server C525 as a sibling EAS, and with server A522 as a parent EAS. Server D524 has associations with server B523 as a parent EAS, server C525 has associations with server B523 as a sibling EAS, and server A522 has associations with server B523 as a child EAS.

[0067] As shown in Figures 4 and 5, embodiments herein propose a network architecture for vertical applications in edge deployments.

[0068] In this embodiment, a user device (UE) comprising multiple functional components is proposed. For example, the multiple functional components may include a first functional component implementing an edge enabler client (EEC) and a second functional component implementing an application enabler client for a vertical application. In this embodiment, the first and second functional components may communicate via an edge-5 reference point.

[0069] In this embodiment, the UE may further comprise a third functional component that implements an application-specific client for a vertical application. The first and third functional components may communicate via an edge-5 reference point. The second and third functional components may communicate via an AE-C reference point.

[0070] In an embodiment, the UE may further comprise a fourth functional component that implements a Service Enabler Architecture Layer (SEAL) client for vertical applications. The first and fourth functional components may communicate via an edge-5 reference point. The second and fourth functional components may communicate via a SEAL-C reference point. The second and fourth functional components may communicate via a SEAL-C reference point.

[0071] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0072] In this embodiment, a first functional component may communicate with a first network function implementing an Edge Enabler Server (EES) via an Edge-1 reference point. A second functional component may communicate with a second network function implementing an Application Enabler Server for a vertical application via an AE-1 reference point. A third functional component may communicate with a third network function implementing an Application-Specific Server for a vertical application via a VA-1 reference point. For example, the VA-1 reference point may be a reference point between an Application-Specific Client and an Application-Specific Server. A fourth functional component may communicate with a fourth network function implementing a Service Enabler Architecture Layer (SEAL) Server for a vertical application via a SEAL-UU reference point.

[0073] In this embodiment, we further propose a communication system for vertical applications in edge deployments, comprising multiple network functions in an edge data network (EDN). These multiple network functions may include a first network function implementing an edge enabler server (EES) and a second network function implementing an application enabler server for the vertical application. The first and second network functions communicate via an edge-3 reference point.

[0074] In this embodiment, the communication system may further include a third network function that implements an application-specific server for a vertical application. The first and third network functions may communicate via an edge-3 reference point. The second and third network functions may communicate via an AE-S reference point.

[0075] In the embodiment, the communication system may further include a fourth network function that implements a Service Enabler Architecture Layer (SEAL) server for vertical applications. The first and fourth network functions may communicate via an edge-3 reference point. The second and fourth network functions may communicate via a SEAL-S reference point. The second and fourth network functions may communicate via a SEAL-S reference point.

[0076] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0077] In this embodiment, a first network function may communicate with a first functional component implementing an edge enabler client (EEC) via an edge-1 reference point. A second network function may communicate with a second functional component implementing an application enabler client for a vertical application via an AE-1 reference point. A third network function may communicate with a third functional component implementing an application-specific client for a vertical application via a VA-1 reference point. For example, the VA-1 reference point may be a reference point between an application-specific client and an application-specific server. A fourth network function may communicate with a fourth functional component implementing a service enabler architecture layer (SEAL) client for a vertical application via a SEAL-UU reference point.

[0078] In some embodiments, each EAS 422, 423, 424, 522, 523, 524, 525 registers with EES 421, 521 using its own profile and optional related EAS information (see message in Figure 6 below), so that after EAS discovery (see message in Figures 7 and 8 below), UE 401, 501 can have joint considerations when selecting edge application servers 422, 423, 424, 522, 523, 524, 525 that have a management relationship with each other. For example, coordination between client B513 and client D514 via a Dc-Bc reference point may occur, so that selected servers B523 and D524 used for client B513 and client D514 are associated.

[0079] In some embodiments, only one EAS422, 522 in the root or bottom layer needs to register with EAS421, 521 on behalf of its children 423, 424, 523, 524 and its siblings (see the message in Figure 6 below). In an onboarded EAS profile, it may further include a list of onboarded EAS profiles. Simply put, this is an embedded EAS profile in another EAS profile that may include several layers.

[0080] Table 2 shows the impact on EAS profiles (in bold and italics), including a list of onboarded EAS profiles. TIFF0007933951000002.tif83170

[0081] In some embodiments, in UE401, 501, EEC411, 511 are responsible for joint EAS discovery and selection for all clients 412, 413, 414, 512, 513, 514, and 515 in the above layer. For example, client D514 delegates EAS discovery and selection to client B513, and client B513 then notifies client D514 of the selected server D524 via the Dc-Bc reference point.

[0082] The embodiments are described below primarily by reference to the architecture in Figure 4, and the embodiments may be similarly applicable to the architecture in Figure 5 and similar architectures for vertical applications.

[0083] Figure 6 is a schematic signaling chart showing messages in vertical EAS registration during edge deployment.

[0084] In this embodiment, the following preconditions are met before performing vertical EAS registration.

[0085] (1) EAS422 has EAS identification information set. (2) The address (for example, URI) of EES421 is set in EAS422. (3) Both EAS422 and EES421 have the necessary certifications to enable communication.

[0086] In this embodiment, the signaling chart in Figure 6 may include the following messages or steps:

[0087] Step 1. EAS422 determines that it needs to register with EAS421 (for example, EAS422 is instantiated and started up).

[0088] Step 2. EAS422 sends an edge application server registration request to EES421. The request may include an EAS profile and a proposed expiration time for registration.

[0089] In the embodiment, the request may also include relevant EAS information in order to register the associations between EAS422, 423, and 424. For example, information regarding the EAS profiles in Table 1 or Table 2 above may be included in the request. As a result, in the subsequent EAS discovery procedure, UE401 may discover the associations between EAS422, 423, and 424, which can be used to select EAS422, 423, and 424 in joint consideration.

[0090] Step 3. EES421 performs an authorization check to verify whether EAS422 has authorization to register on EES421.

[0091] Step 4. If the authorization check is successful, EES421 stores the EAS profile for later use (for example, to serve edge application server discovery requests received from EEC411) and returns it to EAS422 with the edge application server registration response. EES421 may provide an expiration time to indicate to EAS422 when the registration will automatically expire. To maintain registration, EAS422 sends a registration renewal request before the expiration time. If a registration renewal request is not received before the expiration time, EES421 implicitly treats EAS422 as unregistered.

[0092] Similarly, EAS423 and / or EAS424 may perform the registration procedure described in Figure 6 to register an EAS profile with EAS421.

[0093] Figure 7 is a schematic signaling chart showing messages in vertical EAS discovery request responses during edge deployment.

[0094] In this embodiment, the following preconditions are met before performing vertical EAS discovery.

[0095] (1) EEC411 receives information related to EES421 (e.g., URI, IP address). (2) EEC411 has received an appropriate security certificate that allows EEC411 to communicate with EES421. (3) The EES421 has an ECSP policy set for EAS discovery.

[0096] In this embodiment, the signaling chart in Figure 7 may include the following messages or steps:

[0097] Step 1. EEC411 sends an EAS discovery request to EES421. The EAS discovery request may include a requester identifier, such as an EEC ID, along with a security certificate, and may include an EAS discovery filter to retrieve information about a specific EAS or EAS category, such as a game application.

[0098] Step 2. Upon receiving a request from EEC411, EES421 checks whether EEC411 is authorized to discover the requested EAS. The authorization check may apply to individual EAS, EAS categories, or EDNs, in other words, to all EAS. EES421 may utilize the capabilities of the 3GPP core network 403 (e.g., UE locations) as specified in Section 8.9.3. If an EAS discovery filter is provided by EEC411, EES421 identifies EAS422, 423, and 424 based on the provided EAS discovery filter and UE locations. When no EAS discovery filter is provided, -If available, EES421 identifies EAS422, 423, and 424 based on UE-specific service information and UE location in EES421. -EES421 identifies EAS422, 423, and 424 by applying an ECSP policy (for example, based only on the UE location).

[0099] If EES421 cannot determine the EAS information using the inputs in the EAS discovery request, UE-specific service information in EES421, or the ECSP policy, EES421 will reject the service provisioning request and respond with the appropriate cause of failure.

[0100] If UE401 is located outside the geographical or topological service area of ​​EAS422, 423, or 424, EAS421 will not include this UE401, 422, 423, or 424 during discovery response.

[0101] Step 3. If the request is processed successfully, EES421 sends an EAS discovery response to EEC411 containing information about the discovered EAS422, 423, and 424. For the discovered EAS422, 423, and 424, this includes endpoint information. Depending on the EAS discovery filter received in the EAS discovery request, the response may include additional information about the matched capabilities, such as service permission levels, application client locations that the EAS can support, and key performance indicators.

[0102] In embodiments, the response may also include relevant EAS information. For example, information regarding the EAS profiles in Table 1 or Table 2 above may be included in the response. As a result, UE401 may discover relationships between EAS422, 423, and 424, which can be used to select EAS422, 423, and 424 in joint consideration.

[0103] Upon receiving an EAS discovery response, the EEC411 may, if necessary, use the endpoint information to route outgoing application data traffic to the EAS and provide necessary notifications to application clients. The EEC may cache the EAS information (e.g., EAS endpoints) for later use, avoiding the need to repeat step 1. If a lifetime IE is included in the response, the EEC411 may cache the EAS information only for the duration specified by the lifetime IE.

[0104] Figure 8 is a schematic signaling chart showing messages in vertical EAS discovery notifications during edge deployment.

[0105] In this embodiment, the following preconditions are met before performing vertical EAS discovery.

[0106] (1) EEC411 subscribed to EES421 for EAS discovery information.

[0107] In this embodiment, the signaling chart in Figure 8 may include the following messages or steps: Step 1. An event occurs in EES421 that meets the trigger conditions for providing EAS discovery information for the subscribed EEC411. If UE location information is not available, EES421 may obtain the UE location by utilizing the capabilities of the 3GPP core network 403 as specified in Section 8.9.2. If an EAS discovery filter was provided by EEC411 during subscription creation, EES421 identifies EAS422, 423, and 424 based on the provided EAS discovery filter and UE location. If no EAS discovery filter was provided, -If available, EES421 identifies EAS422, 423, and 424 based on UE-specific service information and UE location in EES421. -EES421 identifies EAS422, 423, and 424 by applying an ECSP policy (for example, based only on the UE location).

[0108] If UE401 is located outside the geographical area or topology service area of ​​the edge application server, EES421 will not include this EAS during EAS discovery notification.

[0109] Step 2. EES421 sends an EAS discovery notification to EEC411 along with the EAS information determined in Step 1.

[0110] In embodiments, the notification may also include relevant EAS information. For example, information regarding the EAS profiles in Table 1 or Table 2 above may be included in the response. As a result, the UE may discover relationships between EAS 422, 423, and 424, which can be used to select EAS 422, 423, and 424 in joint consideration.

[0111] Figure 9 is a schematic flowchart illustrating an exemplary EAS registration method 900 implemented by a first network function according to embodiments of this specification. In embodiments, the flowchart in Figure 9 may be implemented in the above-mentioned EES (such as EES421).

[0112] Method 900 may begin with step S901, in which a first network function may receive a registration request message from a second network function (such as EAS422) that implements EAS in the EDN, the message containing information pointing to a first list of relevant EAS information.

[0113] In the embodiment, information pointing to a first list of relevant EAS information may be included in the EAS profile of the second network function. The EAS profile of the second network function may further include information pointing to an EAS ID and information pointing to an EAS endpoint of the second network function.

[0114] In embodiments, the first list of related EAS information may comprise at least one first entry for at least one third network function (such as EAS423) that implements EAS in the EDN. Each first entry may point to the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

[0115] For example, EAS422 may send an EAS profile of EAS422 to EAS421 that includes a first list of related EAS information (which may point to EAS422's associations with other EAS423 and / or 424).

[0116] In another example, EAS423 may send an EAS profile of EAS423 to EAS421 that includes a first list of relevant EAS information (which may indicate EAS423's association with other EAS424s).

[0117] In this embodiment, the relationship may indicate that the third network function is the parent, child, or sibling of the second network function, as can be seen from Figure 4 or Figure 5.

[0118] In the embodiment, each of at least one first entry in the first list of related EAS information may further point to endpoint information for each third network function.

[0119] In the embodiment, the first entry for a third network function further comprises information pointing to a second list of related EAS information. The second list of related EAS information may further comprise at least one second entry for at least one fourth network function, each implementing EAS in the EDN (e.g., EAS424). Each second entry may point to the EAS profile of the respective fourth network function. The EAS profile of each fourth network function may include the EAS ID of the respective fourth network function and the relationship between the third network function and the respective fourth network function.

[0120] For example, in the embedded registration of EAS422, 423, and 424 (EAS424 is registered on EAS423, and EAS423 is registered on EAS422), EAS422 may send an EAS profile of EAS422 to EAS421 that includes a first list of related EAS information (which may indicate EAS422's association with other EAS423 and / or 424 by pointing to a second list of related EAS information for the association between EAS423 and EAS424).

[0121] In this embodiment, the relationship may indicate that the fourth network function is the parent, child, or sibling of the third network function, as can be seen from Figure 4 or Figure 5.

[0122] In the embodiment, each of at least one second entry in the second list of related EAS information may further point to endpoint information for each of the fourth network functions.

[0123] In this embodiment, at least two of the second, third, and fourth network functions are configured to jointly provide services for a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the relevant EAS information.

[0124] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0125] In this embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server 422 for vertical applications, and the third network function is implemented as vertical application layer (VAL) servers 423, 424. An administrative or management relationship may exist between the SEAL server 422 and the VAL servers 423, 424. For example, the SEAL server 422 may manage at least some of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the boarding configuration).

[0126] In this embodiment, the SEAL server 422 may include a SEAL Identification Information Management (IM) server. The SEAL IM server may provide a token validity verification service to the VAL servers 423 and 424 to verify the validity of tokens assigned by the SEAL IM server.

[0127] In this embodiment, the token may be, for example, an access token and / or an ID token.

[0128] In this embodiment, the VAL server is either an FF Application Specific (FFAS) server 424 or an FF Application Enabler (FAE) server 423.

[0129] In this embodiment, the second network function is implemented as an FF Application Enabler (FAE) server 423, and the third network function is implemented as an FF Application Specific (FFAS) server 424.

[0130] Method 900 may then proceed to step S902, in which the first network function may store information pointing to a first list of relevant EAS information.

[0131] In the embodiment, the first network function may store information pointing to another list of related EAS information. For example, the network function may store information pointing to a second list of related EAS information.

[0132] In this embodiment, the first network function may store all information received from the EAS. For example, the first network function may store all lists of relevant EAS information received from the EAS.

[0133] Method 900 may then proceed to step S903, in which the first network function may send a registration response message to the second network function implementing the EAS.

[0134] The steps described above are merely examples, and the first network function may perform the actions described with respect to Figures 6-8 to manage relevant EAS information to provide the UE with an integrated view for selecting application servers deployed at the edge.

[0135] Figure 10 is a schematic flowchart illustrating an exemplary EAS registration method 1000 performed by a second network function (EAS 422, 423, 424, etc.) according to embodiments herein. In embodiments, the flowchart in Figure 10 may be implemented in the EAS 422, 423, 424 described above.

[0136] Method 1000 may begin with step S1001, in which a second network function (such as EAS422) may receive a registration request from a third network function (such as EAS423 or 424) to register the third network function with the second network function.

[0137] In this embodiment, the registration request may include information pointing to at least one of the following: the EAS ID of the third network function, the endpoint of the third network function, or the relationship between the third network function and the third network function.

[0138] In this embodiment, the registration request may include information pointing to the EAS profile of a third network function, and the EAS profile of the third network function may further include information about the associated fourth network function.

[0139] Method 1000 may then proceed to step S1002, in which the second network function may store the above information received from the third network function as registration information for the third network function. For example, the second network function may store the registration information in a list of related EAS information within the EAS profile of the second network function. In doing so, associations may be established between the second network function and the third network function (and further network functions).

[0140] Method 1000 may then proceed to step S1003, in which the second network function may send a registration request message to the first network function that implements EES in the EDN (such as EES421), the message containing information pointing to a first list of relevant EAS information.

[0141] In the embodiment, information pointing to a first list of relevant EAS information may be included in the EAS profile of the second network function. The EAS profile of the second network function may further include information pointing to an EAS ID and information pointing to an EAS endpoint of the second network function.

[0142] In embodiments, the first list of related EAS information may comprise at least one first entry for at least one third network function that implements EAS in the EDN. Each first entry may point to the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

[0143] In this embodiment, the relationship may indicate that the third network function is the parent, child, or sibling of the second network function, as can be seen from Figure 4 or Figure 5.

[0144] In the embodiment, each of at least one first entry in the first list of related EAS information may further point to endpoint information for each third network function.

[0145] In the embodiment, the first entry for a third network function further comprises information pointing to a second list of related EAS information. The second list of related EAS information may further comprise at least one second entry for at least one fourth network function, each implementing EAS in the EDN. Each second entry may point to the EAS profile for each fourth network function. The EAS profile for each fourth network function may include the EAS ID for each fourth network function and the relationship between the third network function and each fourth network function (e.g., EAS424).

[0146] In this embodiment, the relationship may indicate that the fourth network function is the parent, child, or sibling of the third network function, as can be seen from Figure 4 or Figure 5.

[0147] In the embodiment, each of at least one second entry in the second list of related EAS information may further point to endpoint information for each of the fourth network functions.

[0148] In this embodiment, at least two of the second, third, and fourth network functions are configured to jointly provide services for a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the relevant EAS information.

[0149] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0150] In this embodiment, a second network function (such as EAS422) is implemented as a Service Enabler Architecture Layer (SEAL) server for vertical applications, and a third network function (such as EAS423, 424) is implemented as a Vertical Application Layer (VAL) server. An administrative or management relationship may exist between the SEAL server 422 and the VAL servers 423, 424. For example, the SEAL server 422 may manage at least some of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the boarding configuration).

[0151] In this embodiment, the SEAL server 422 may include a SEAL Identification Information Management (IM) server. The SEAL IM server may provide a token validity verification service to the VAL servers 423 and 424 to verify the validity of tokens assigned by the SEAL IM server.

[0152] In this embodiment, the token may be, for example, an access token and / or an ID token.

[0153] In this embodiment, the VAL servers 423 and 424 are either FF Application Specific (FFAS) servers 424 or FF Application Enabler (FAE) servers 423.

[0154] In this embodiment, the second network function is implemented as an FF Application Enabler (FAE) server 423, and the third network function is implemented as an FF Application Specific (FFAS) server 424.

[0155] Method 1000 may then proceed to step S1004, in which the second network function may receive a registration response message from the first network function implementing the EES.

[0156] The steps described above are merely examples, and a second network function may perform the actions described with respect to Figures 6-8 to manage relevant EAS information to provide the UE with an integrated view for selecting application servers deployed at the edge.

[0157] Figure 11 is a schematic flowchart illustrating an exemplary EAS discovery method 1100 performed by a first network function according to embodiments herein. In embodiments, the flowchart in Figure 11 may be implemented in the above-mentioned EES (such as EES421).

[0158] Method 1100 may begin with step S1101, in which a first network function may receive a first message from a functional component of user equipment (UE) 401 to discover at least one second network function that implements an edge application server (EAS) in EDN 402.

[0159] In this embodiment, the first message may be a discovery request message for discovering an EAS server.

[0160] In one embodiment, the first message may be a discovery subscription message for subscribing to discovery on the EAS server.

[0161] In the embodiment, the first message further includes an indicator that explicitly points to an EAS association. For example, EEC411 may explicitly point to an EAS association in an EAS discovery request or an EAS discovery subscription request so that only EAS having an EAS association is discovered.

[0162] Method 1100 may then proceed to step S1102, in which the first network function may perform an EAS discovery process to discover an EAS. In embodiments, the EAS discovery process is performed based on indicators that explicitly point to an EAS association. As a result, the first network function may discover at least one EAS. There may be associations between at least one EAS. For example, the first network function may discover at least a first list of related EAS information.

[0163] In the embodiment, information pointing to a first list of relevant EAS information may be included in the EAS profile of a second network function (such as EAS422). The EAS profile of a second network function may further include information pointing to an EAS ID and information pointing to an EAS endpoint of the second network function.

[0164] In embodiments, the first list of related EAS information may comprise at least one first entry for at least one third network function (such as EAS423) that implements EAS in the EDN. Each first entry may point to the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

[0165] In this embodiment, the relationship may indicate that the third network function is the parent, child, or sibling of the second network function, as can be seen from Figure 4 or Figure 5.

[0166] In the embodiment, each of at least one first entry in the first list of related EAS information may further point to endpoint information for each third network function.

[0167] In the embodiment, the first entry for a third network function further comprises information pointing to a second list of related EAS information. The second list of related EAS information may further comprise at least one second entry for at least one fourth network function, each implementing EAS in the EDN (e.g., EAS424). Each second entry may point to the EAS profile of the respective fourth network function. The EAS profile of each fourth network function may include the EAS ID of the respective fourth network function and the relationship between the third network function and the respective fourth network function.

[0168] In this embodiment, the relationship may indicate that the fourth network function is the parent, child, or sibling of the third network function, as can be seen from Figure 4 or Figure 5.

[0169] In the embodiment, each of at least one second entry in the second list of related EAS information may further point to endpoint information for each of the fourth network functions.

[0170] In this embodiment, at least two of the second, third, and fourth network functions are configured to jointly provide services for a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the relevant EAS information.

[0171] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0172] In this embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server 422 for vertical applications, and the third network function is implemented as vertical application layer (VAL) servers 423, 424. An administrative or management relationship may exist between the SEAL server 422 and the VAL servers 423, 424. For example, the SEAL server 422 may manage at least some of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the boarding configuration).

[0173] In this embodiment, the SEAL server 422 may include a SEAL Identification Information Management (IM) server. The SEAL IM server may provide a token validity verification service to the VAL servers 423 and 424 to verify the validity of tokens assigned by the SEAL IM server.

[0174] In this embodiment, the token may be, for example, an access token and / or an ID token.

[0175] In this embodiment, the VAL server is either an FF Application Specific (FFAS) server 424 or an FF Application Enabler (FAE) server 423.

[0176] In this embodiment, the second network function is implemented as an FF Application Enabler (FAE) server 423, and the third network function is implemented as an FF Application Specific (FFAS) server 424.

[0177] Method 1100 may then proceed to step S1103, in which the first network function may send a second message to the functional component of the UE containing information pointing to a first list of relevant EAS information.

[0178] In this embodiment, the second message is a discovery response message that responds to the first message (request message).

[0179] In this embodiment, the second message is a discovery notification message that responds to the first message (subscription message).

[0180] In this embodiment, the first functional component is implemented as an edge enabler client (EEC) 411, and the first and / or second messages are sent via the edge-1 reference point.

[0181] The steps described above are merely examples, and a second network function may perform the actions described with respect to Figures 6-8 to manage relevant EAS information to provide the UE with an integrated view for selecting application servers deployed at the edge.

[0182] Figure 12 is a schematic flowchart illustrating an exemplary EAS discovery method 1200 implemented by a first functional component in the UE according to embodiments herein. In embodiments, the flowchart in Figure 12 may be implemented in the aforementioned EEC (such as EEC411).

[0183] Method 1200 may begin with step S1201, in which a first functional component may receive a first delegation request for EAS discovery and selection for a second functional component from a second functional component in the UE (such as one of application clients 412, 413, or 414). Furthermore, the first functional component may receive a second delegation request for EAS discovery and selection for a third functional component from a third functional component in the UE (such as another of application clients 412, 413, or 414).

[0184] In this embodiment, the second functional component is implemented as a Service Enabler Architecture Layer (SEAL) client 412 for vertical applications. Furthermore, the third functional component is implemented as vertical application layer (VAL) clients 413 and 414.

[0185] In this embodiment, the VAL server is either an application-specific client 414 or an application enabler client 413.

[0186] In this embodiment, the second functional component is implemented as an application enabler client 413, and the third functional component is implemented as an application-specific client 414.

[0187] Method 1200 may then proceed to step S1202, in which the first functional component may send a first message to a first network function that implements an edge enabler server (EES) in the edge data network (EDN) to discover at least one second network function that implements an edge application server (EAS) in the EDN.

[0188] In this embodiment, the first message may be a discovery request message for discovering an EAS server.

[0189] In one embodiment, the first message may be a discovery subscription message for subscribing to discovery on the EAS server.

[0190] In the embodiment, the first message further includes an indicator that explicitly points to an EAS association. For example, EEC411 may explicitly point to an EAS association in an EAS discovery request or an EAS discovery subscription request so that only EAS having an EAS association is discovered.

[0191] In an embodiment, after receiving a first message from a first functional component in the UE, a first network function (such as EES421) may perform an EAS discovery process to discover EAS422, 423, and 424. In an embodiment, the EAS discovery process is performed based on indicators that explicitly point to EAS associations. As a result, the first network function may discover at least one EAS. There may be associations between at least one EAS. For example, the first network function may discover at least a first list of related EAS information.

[0192] Method 1200 may then proceed to step S1203, in which the first functional component may receive a second message from the first network function containing information pointing to a first list of relevant EAS information.

[0193] In this embodiment, the second message is a discovery response message that responds to the first message (request message).

[0194] In this embodiment, the second message is a discovery notification message that responds to the first message (subscription message).

[0195] In this embodiment, the first and / or second messages are sent via the edge-1 reference point.

[0196] In the embodiment, information pointing to a first list of relevant EAS information may be included in the EAS profile of a second network function (such as EAS422). The EAS profile of the second network function may further include information pointing to an EAS ID and information pointing to an EAS endpoint of the second network function.

[0197] In embodiments, the first list of related EAS information may comprise at least one first entry for at least one third network function (such as EAS423) that implements EAS in the EDN. Each first entry may point to the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

[0198] In this embodiment, the relationship may indicate that the third network function is the parent, child, or sibling of the second network function, as can be seen from Figure 4 or Figure 5.

[0199] In the embodiment, each of at least one first entry in the first list of related EAS information may further point to endpoint information for each third network function.

[0200] In the embodiment, the first entry for a third network function further comprises information pointing to a second list of related EAS information. The second list of related EAS information may further comprise at least one second entry for at least one fourth network function, each implementing EAS in the EDN (e.g., EAS424). Each second entry may point to the EAS profile of the respective fourth network function. The EAS profile of each fourth network function may include the EAS ID of the respective fourth network function and the relationship between the third network function and the respective fourth network function.

[0201] In this embodiment, the relationship may indicate that the fourth network function is the parent, child, or sibling of the third network function, as can be seen from Figure 4 or Figure 5.

[0202] In the embodiment, each of at least one second entry in the second list of related EAS information may further point to endpoint information for each of the fourth network functions.

[0203] In this embodiment, at least two of the second, third, and fourth network functions are configured to jointly provide services for a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the relevant EAS information.

[0204] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0205] In this embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server 422 for vertical applications, and the third network function is implemented as vertical application layer (VAL) servers 423, 424. An administrative or management relationship may exist between the SEAL server 422 and the VAL servers 423, 424. For example, the SEAL server 422 may manage at least some of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the boarding configuration).

[0206] In this embodiment, the SEAL server 422 may include a SEAL Identification Information Management (IM) server. The SEAL IM server may provide a token validity verification service to the VAL server to verify the validity of tokens assigned by the SEAL IM server.

[0207] In this embodiment, the token may be, for example, an access token and / or an ID token.

[0208] In this embodiment, the VAL server is either an FF Application Specific (FFAS) server 424 or an FF Application Enabler (FAE) server 423.

[0209] In this embodiment, the second network function is implemented as an FF Application Enabler (FAE) server 423, and the third network function is implemented as an FF Application Specific (FFAS) server 424.

[0210] In the embodiment, information pointing to a first list of relevant EAS information is included in a set of EAS profiles for a first set of network functions that implement EAS in the EDN. For example, a first network function may discover a set of EAS (in other words, two or more EAS or at least one EAS) and provide information (such as EAS profiles) about the discovered set of EAS.

[0211] Method 1200 may then proceed to step S1204, in which the first functional component may determine the EAS for selection. For example, the first functional component (e.g., EEC) may determine a first set of network functions that implement EAS in the EDN from a set of EAS profiles. Furthermore, the first functional component may determine a second set of network functions that implement EAS in the EDN from a first list of relevant EAS information. Note that, depending on the received relevant EAS information, the EEC may use various approaches to determine the EAS for providing vertical application services.

[0212] In the embodiment, at least two network functions for selection are associated. For example, at least two network functions from a first and second set of network functions have an administrative or management relationship. For example, one of the two network functions is registered on the other of the two network functions (in other words, on the boarding configuration).

[0213] In the embodiment, the first functional component may, in response to a delegation request, narrow down the network functions to be selected by the second and third functional components. For example, the first functional component may provide the second and third functional components with several options (i.e., several sets of associated network functions).

[0214] In the embodiment, the first functional component may select only one set of associated network functions for the second and third functional components. That is, the first functional component may determine the network functions for the second functional component and the network functions for the third functional component according to the delegated request.

[0215] In this embodiment, the first functional component may notify the second and third functional components, respectively, of the selected network functions for the second and third functional components.

[0216] Upon receiving notification, the second and third functional components may coordinate to select network functions so that the selected network functions are associated with each other. For example, the selected network functions have an administrative or management relationship. For example, one of the selected network functions is registered on the other of the selected network functions (in other words, on the boarding configuration). Meanwhile, the third functional component may send a delegation request to the second functional component, thereby allowing the second functional component to perform the selection on behalf of the third functional component.

[0217] It should be noted that steps S1201 and S1202-S1203 described above can be carried out in any manner, for example, in any sequence, simultaneously, or separately.

[0218] The steps described above are merely examples; the UE may take actions to manage relevant EAS information for selecting application servers deployed at the edge in a unified view.

[0219] Figure 13 is a schematic flowchart illustrating an exemplary EAS discovery method 1300 implemented by a second functional component in the UE according to embodiments herein. In embodiments, the flowchart in Figure 13 may be implemented in application clients 412, 413, or 414 for a vertical application.

[0220] Method 1300 may begin with step S1301, in which a second functional component (such as one of application clients 412, 413, or 414) may receive a delegation request for EAS discovery and selection for the third functional component from a third functional component (such as another of application clients 412, 413, or 414) in the UE.

[0221] In this embodiment, the second functional component is implemented as a Service Enabler Architecture Layer (SEAL) client 412 for vertical applications. Furthermore, the third functional component is implemented as vertical application layer (VAL) clients 413 and 414.

[0222] In this embodiment, the VAL server is either an application-specific client 414 or an application enabler client 413.

[0223] In this embodiment, the second functional component is implemented as an application enabler client 413, and the third functional component is implemented as an application-specific client 414.

[0224] Method 1300 may then proceed to step S1302, in which the second functional component may initiate the EAS discovery process using any approach. For example, the second functional component may request the EAS discovery process from the first functional component via the edge-5 reference point.

[0225] Subsequently, after receiving a request from the second functional component, the first functional component (e.g., EEC411) may further request the first functional component (e.g., EES421) for the EAS discovery process. The first network function may then perform the EAS discovery process to discover EAS (e.g., EAS422, 423, 424). As a result, the first network function may discover at least one EAS. There may be associations between at least one EAS. For example, the first network function may discover at least a first list of related EAS information. EAS discovery may further refer to the steps described above with respect to Figure 12.

[0226] Method 1300 may then proceed to step S1303, in which the second functional component may receive a message from the first functional component in the UE containing information pointing to a list of relevant edge application server (EAS) information. In the embodiment, the first functional component is implemented as an edge enabler client (EEC) 411. In the embodiment, the message is an EAS discovery response message or an EAS discovery notification message sent via the edge-5 reference point.

[0227] In the embodiment, information pointing to a first list of relevant EAS information may be included in the EAS profile of the second network function. The EAS profile of the second network function may further include information pointing to an EAS ID and information pointing to an EAS endpoint of the second network function.

[0228] In embodiments, the first list of related EAS information may comprise at least one first entry for at least one third network function that implements EAS in the EDN. Each first entry may point to the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

[0229] In this embodiment, the relationship may indicate that the third network function is the parent, child, or sibling of the second network function, as can be seen from Figure 4 or Figure 5.

[0230] In the embodiment, each of at least one first entry in the first list of related EAS information may further point to endpoint information for each third network function.

[0231] In embodiments, a first entry for a third network function (such as EAS423) further comprises information pointing to a second list of related EAS information. The second list of related EAS information may further comprise at least one second entry for at least one fourth network function (such as EAS424) each implementing EAS in the EDN. Each second entry may point to the EAS profile of the respective fourth network function. The EAS profile of each fourth network function may include the EAS ID of the respective fourth network function and the relationship between the third network function and the respective fourth network function.

[0232] In this embodiment, the relationship may indicate that the fourth network function is the parent, child, or sibling of the third network function, as can be seen from Figure 4 or Figure 5.

[0233] In the embodiment, each of at least one second entry in the second list of related EAS information may further point to endpoint information for each of the fourth network functions.

[0234] In this embodiment, at least two of the second, third, and fourth network functions are configured to jointly provide services for a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the relevant EAS information.

[0235] In this embodiment, the vertical application is one of the following: Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

[0236] In this embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server 422 for vertical applications, and the third network function is implemented as vertical application layer (VAL) servers 423, 424. An administrative or management relationship may exist between the SEAL server 422 and the VAL servers 423, 424. For example, the SEAL server 422 may manage at least some of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the boarding configuration).

[0237] In this embodiment, the SEAL server 422 may include a SEAL Identification Information Management (IM) server. The SEAL IM server may provide a token validity verification service to the VAL servers 423 and 424 to verify the validity of tokens assigned by the SEAL IM server.

[0238] In this embodiment, the token may be, for example, an access token and / or an ID token.

[0239] In this embodiment, the VAL server is either an FF Application Specific (FFAS) server 424 or an FF Application Enabler (FAE) server 423.

[0240] In this embodiment, the second network function is implemented as an FF Application Enabler (FAE) server 423, and the third network function is implemented as an FF Application Specific (FFAS) server 424.

[0241] In the embodiment, information pointing to a first list of relevant EAS information is included in a set of EAS profiles for a first set of network functions that implement EAS in the EDN. For example, a first network function may discover a set of EAS (in other words, two or more EAS or at least one EAS) and provide information (such as EAS profiles) about the discovered set of EAS.

[0242] Method 1300 may then proceed to step S1304, in which the second functional component may determine the EAS for selection. For example, the second functional component may determine a first set of network functions that implement EAS in the EDN from a set of EAS profiles. Furthermore, the second functional component may determine a second set of network functions that implement EAS in the EDN from a first list of relevant EAS information. Note that, depending on the received relevant EAS information, the second functional component may use various approaches to determine the EAS for providing vertical application services.

[0243] In the embodiment, at least two network functions for selection are associated. For example, at least two network functions from a first and second set of network functions have an administrative or management relationship. For example, one of the two network functions is registered on the other of the two network functions (in other words, on the boarding configuration).

[0244] In the embodiment, the second functional component may, in response to a delegation request, narrow down the network functions to be selected by the second and third functional components. For example, the second functional component may provide the third functional component with several options (i.e., several sets of associated network functions).

[0245] In the embodiment, the second functional component may select only one set of associated network functions for the second and third functional components. That is, the second functional component may determine the network functions for the second functional component and the network functions for the third functional component according to the delegated request.

[0246] In this embodiment, the second functional component may notify the third functional component of the selected network function for the third functional component.

[0247] In the embodiment, the second and third functional components may cooperate to select network functions so that the selected network functions are associated with each other. For example, the selected network functions have an administrative or management relationship. For example, one of the selected network functions is registered on the other of the selected network functions (in other words, on the boarding configuration).

[0248] It should be noted that steps S1301 and S1302-S1303 described above can be carried out in any manner, for example, in any sequence, simultaneously, or separately.

[0249] It should be further noted that step S1301 above (in other words, delegation of EAS discovery and selection) may be a mandatory step, thereby allowing the subsequent EAS selection step S1304 to be performed in the second functional component, or otherwise in the third functional component. Furthermore, step S1301 above may be an optional step, meaning there is no delegation between the second and third functional components, in which case the second and third functional components must coordinate EAS selection when relevant EAS information is received.

[0250] The steps described above are merely examples; the UE may take actions to manage relevant EAS information for selecting application servers deployed at the edge in a unified view.

[0251] Figure 14 is a schematic block diagram illustrating an exemplary first network function (such as EES421) according to embodiments described herein.

[0252] In some embodiments, the first network function 1400 may include at least one processor 1401 and a non-temporary computer-readable medium 1402 coupled to the at least one processor 1401. The non-temporary computer-readable medium 1402 contains instructions executable by the at least one processor 1401, thereby configuring the at least one processor 1401 to perform the steps in the exemplary method 900 shown in the schematic flowchart of Figure 9 and the exemplary method 1100 shown in the schematic flowchart of Figure 11, details of which are omitted here.

[0253] It should be noted that the first network function 1400 can be implemented as hardware, software, firmware, or any combination thereof. For example, the first network function 1400 may include a plurality of units, circuits, modules, etc., each of which may be used to perform one or more steps of the exemplary method 900 / 1100, or one or more steps shown in Figures 6-8 relating to the EES.

[0254] It should be understood that network functionality can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functionality instantiated on an appropriate platform, such as a cloud infrastructure.

[0255] Figure 15 is a schematic block diagram illustrating exemplary second network functions (EAS422, 423, 424, etc.) according to embodiments herein.

[0256] In some embodiments, the second network function 1500 may include at least one processor 1501 and a non-temporary computer-readable medium 1502 coupled to the at least one processor 1501. The non-temporary computer-readable medium 1502 contains instructions executable by the at least one processor 1501, thereby configuring the at least one processor 1501 to perform the steps in the exemplary method 1000 shown in the schematic flowchart of Figure 10, details of which are omitted here.

[0257] It should be noted that the second network function 1500 can be implemented as hardware, software, firmware, or any combination thereof. For example, the second network function 1500 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of the exemplary method 1000, or one or more steps shown in Figures 6-8 relating to the EAS.

[0258] It should be noted that, like the second network function, the third and / or fourth network functions described above can also be implemented as EAS in the EDN. Therefore, the third and / or fourth network functions may include the same or similar structure and / or functionality as the second network function. Details of the third and / or fourth network functions are omitted here.

[0259] Figure 16 is a schematic block diagram showing an exemplary UE according to embodiments of this specification. In embodiments, the UE 1600 may include functional components (such as EEC 411, SEAL 412, enabler client 413, application-specific client 414, etc.) as shown in Figures 4-5.

[0260] In embodiments, the UE 1600 may include at least one processor 1601 and a non-temporary computer-readable medium 1602 coupled to the at least one processor 1601. The non-temporary computer-readable medium 1602 contains instructions executable by the at least one processor 1601, thereby configuring the at least one processor 1601 to perform the steps in exemplary method 1200 shown in the schematic flowchart of Figure 12, and / or the steps in exemplary method 1300 shown in the schematic flowchart of Figure 13, details of which are omitted here.

[0261] It should be noted that UE1600 may include hardware, software, firmware, and any combination thereof. For example, UE1600 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of exemplary method 1200 / 1300, or one or more steps shown in Figures 6-8 relating to the UE.

[0262] Furthermore, functional components in the UE (such as EEC, SEAL, enabler clients, and application-specific clients) can be hardware, software, firmware, or any combination thereof. For example, functional components may be implemented as multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of exemplary method 1200 / 1300, or one or more steps shown in Figures 6-8 relating to the UE.

[0263] In some embodiments, the non-limiting term UE is used. The UE1600 described herein may be any type of wireless device that is configured to communicate, arranged to communicate, and / or operable to communicate wirelessly with network nodes and / or other wireless devices, for example, via wireless signals. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information through the air. In certain embodiments, the UE1600 may be configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to a network on a predetermined schedule, triggered by internal or external events, or in response to requests from the network.

[0264] In general, UE can represent any device that is capable of wireless communication, configured for wireless communication, arranged for wireless communication, and / or capable of operating for wireless communication, such as a wireless communication device. Examples of UE include, but are not limited to, smartphones. Further examples include wireless cameras, wireless-enabled tablet computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, and / or wireless customer premises equipment (CPEs). Also, UE900 could be a wireless communication device, a target device, a D2D UE, a machine-type communication (MTC) UE or a machine-to-machine (M2M) communication-capable UE, a low-cost and / or low-complexity UE, a sensor equipped with a UE, a tablet, a mobile terminal, an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, or any other suitable device.

[0265] As one specific example, a UE may be configured for communications under one or more communication standards published by the Third Generation Partnership Project (3GPP), such as the 3GPP Global System for New Radio (NR), Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards or other suitable standards. As used herein, “UE” does not necessarily have a “user” in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device intended for sale to a human user or operated by a human user, but which may not initially be associated with a particular human user.

[0266] Figure 17 is a schematic block diagram showing an exemplary computer implementation device 1700 according to embodiments of this specification. In embodiments, the device 1700 may be configured as one of the above-mentioned devices, such as a first network function 1400, a second network function 1500, a third network function, a fourth network function, or an UE 1600.

[0267] In embodiments, the device 1700 may include, but is not limited to, at least one processor such as a central processing unit (CPU) 1701, a computer-readable medium 1702, and memory 1703. The memory 1703 may comprise volatile memory (e.g., random access memory (RAM)) and / or non-volatile memory (e.g., a hard disk or flash memory). In embodiments, the computer-readable medium 1702 may be configured to store computer programs and / or instructions that, when executed by the processor 1701, cause the processor 1701 to perform any of the methods described above.

[0268] In one embodiment, the computer-readable medium 1702 (such as a non-temporary computer-readable medium) may be stored in the memory 1703. In another embodiment, the computer program may be stored in a remote location, for example, in a computer program product 1704 (which may also be embodied as computer-readable medium), and may be accessible by the processor 1701 via, for example, a carrier 1705.

[0269] Computer-readable media 1702 and / or computer program products 1704 may be supplied and / or stored on removable computer-readable media, such as diskettes, CDs (Compact Discs), DVDs (Digital Video Discs), flash or similar removable memory media (e.g., CompactFlash, SD (Secure Digital), Memory Stick, MiniSD Card, MMC Multimedia Card, SmartMedia), HD-DVDs (High Definition DVDs), or Blu-ray DVDs, USB (Universal Serial Bus) based removable memory media, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or supplied as propagating signals over a network (e.g., Ethernet, ATM, ISDN, PSTN, X.25, the Internet, a local area network (LAN), or a similar network capable of transporting data packets to infrastructure nodes).

[0270] Exemplary embodiments have been described herein with reference to block diagrams and / or flowcharts of computer implementation methods, apparatus (systems and / or devices) and / or non-temporary computer program products. It should be understood that blocks in block diagrams and / or flowcharts, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions may be provided to processor circuits of general-purpose computer circuits, dedicated computer circuits, and / or other programmable data processing circuits to create a machine that creates means (functionality) and / or structures for implementing the functions / actions specified in block diagrams and / or flowchart blocks, by having instructions executed via the processor of a computer and / or other programmable data processing circuit.

[0271] These computer program instructions may also be stored on a tangible computer-readable medium, which can instruct a computer or other programmable data processing device to function in a particular manner, such as to produce a product containing instructions that implement functions / actions specified in block diagrams and / or one or more flowchart blocks. Thus, embodiments of the present concept may be embodied in hardware and / or in software (including firmware, resident software, microcode, etc.) that runs on a processor such as a digital signal processor, which may be collectively referred to as “circuits,” “modules,” or variations thereof.

[0272] Furthermore, it should be noted that in some alternative implementations, the functions / actions described within a block may be performed outside the order shown in the flowchart. For example, two consecutively shown blocks may be executed virtually simultaneously, or blocks may sometimes be executed in reverse order depending on the functions / actions involved. Moreover, the functionality of a given block in a flowchart and / or block diagram may be separated into multiple blocks, and the functionality of two or more blocks in a flowchart and / or block diagram may be integrated, at least partially. Finally, other blocks may be added / inserted between the illustrated blocks, and / or blocks / actions may be omitted without deviating from the scope of the inventive concept. Furthermore, while some of the diagrams include arrows on the communication path to indicate the primary direction of communication, it should be understood that communication may occur in the opposite direction to the depicted arrows.

[0273] Many variations and modifications can be made to embodiments without substantially departing from the principles of the inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the above disclosed subject matter should be considered illustrative and not restrictive, and the accompanying examples of embodiments are intended to encompass all such modifications, extensions and other embodiments that fall within the spirit and scope of the inventive concept. Thereafter, to the maximum extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of this disclosure, including the following examples of embodiments and their equivalents, and not limited or restricted by the forms for carrying out the above invention.

[0274] Abbreviation 3GPP Third Generation Partnership Project 5G (Fifth Generation Mobile Network) API Application Programming Interface App Application EAS Edge Application Server ECS Edge Configuration Server ECSP Edge Computing Service Provider EDN Edge Data Network EEC Edge Enabler Client EES Edge Enabler Server FAE Factory Application Enabler for the Future FF Factory of the Future FFAPP Factory Application for the Future QoS Quality of Service SEAL Service Enabler Architecture Layer for Verticals UAS Unmanned Aerial System UE User Equipment V2X Vehicle to Everything VAL Vertical Application Layer

Claims

1. A method (900) performed by a first network function (421) that implements an edge enabler server (EES) in an edge data network (EDN) (402), - The EDN (402) receives a registration request message (S901) from a second network function (422) that implements an edge application server (EAS), which includes information pointing to a first list of related EAS information. Includes, The first list of related EAS information comprises at least one first entry for at least one third network function (423) that implements EAS in the EDN (402), where each first entry points to the EAS profile of each of the third network functions (423), where the EAS profile of each of the third network functions (423) includes the EAS ID of each of the third network functions (423) and the relationship between the second network function (422) and each of the third network functions (423). Method (900).

2. The method according to claim 1 (900), wherein the first entry for the third network function (423) further comprises information pointing to a second list of related EAS information, the second list of related EAS information further comprises at least one second entry for at least one fourth network function (424) that implements an EAS in the EDN (402), each second entry pointing to an EAS profile for each of the fourth network functions (424), the EAS profile for each of the fourth network functions (424) includes the EAS ID for each of the fourth network functions (424) and the relationship between the third network function (423) and each of the fourth network functions (424).

3. The aforementioned relationship indicates that the third network function (423) is the parent, child, or sibling of the second network function (422), or The aforementioned relationship indicates that the fourth network function (424) is the parent, child, or sibling of the third network function (423). The method according to claim 2 (900).

4. Each of the at least one first entry in the first list of related EAS information further points to the endpoint information of each of the third network functions (423), or Each of the at least one second entry in the second list of related EAS information further points to the endpoint information of each of the fourth network functions (424). The method according to claim 2 or 3 (900).

5. The method (900) according to any one of claims 1 to 4, wherein the information pointing to the first list of related EAS information is included in the EAS profile of the second network function (422), and the EAS profile of the second network function (422) further includes information pointing to the EAS ID and information pointing to the EAS endpoint of the second network function (422).

6. -Storing the information that points to the first list of related EAS information (S902), - Sending a registration response message (S903) to the second network function (422) that implements EAS. The method according to any one of claims 1 to 5, further comprising (900).

7. A method (1100) performed by a first network function (421) that implements an edge enabler server (EES) in an edge data network (EDN) (402), - Receiving a first message from a functional component (411) of a user device (UE) (401) to discover at least one second network function (422) that implements an edge application server (EAS) in the EDN (402) (S1101), - Sending a second message to the functional component (411) of the UE (401) (S1103) containing information pointing to a first list of related EAS information. Includes, The first list of related EAS information comprises at least one first entry for at least one third network function (423) that implements EAS in the EDN, each first entry pointing to the EAS profile of each of the third network functions (423), the EAS profile of each of the third network functions (423) including the EAS ID of each of the third network functions (423) and the relationship between the second network function (422) and each of the third network functions (423). Method (1100).

8. The method according to claim 7 (1100), wherein the information pointing to the first list of relevant EAS information is included in the EAS profile of the at least one second network function (422).

9. The method of claim 8 (1100), wherein the first entry for the third network function (423) further comprises information pointing to a second list of related EAS information, the second list of related EAS information further comprises at least one second entry for at least one fourth network function (424) that implements an EAS in the EDN (402), each second entry pointing to an EAS profile for each of the fourth network functions (424), the EAS profile for each of the fourth network functions (424) includes the EAS ID for each of the fourth network functions (424) and the relationship between the third network function (423) and each of the fourth network functions (424).

10. The aforementioned relationship indicates that the third network function (423) is the parent, child, or sibling of the second network function (422), or The aforementioned relationship indicates that the fourth network function (424) is the parent, child, or sibling of the third network function (423). The method according to claim 9 (1100).

11. Each of the at least one first entry in the first list of related EAS information further points to the endpoint information of each of the third network functions (423), or Each of the at least one second entry in the second list of related EAS information further points to the endpoint information of each of the fourth network functions (424). The method according to claim 9 or 10 (1100).

12. The method according to any one of claims 9 to 11 (1100), wherein the EAS profile of the second network function (422) further includes information indicating the EAS ID and information indicating the EAS endpoint of the second network function (422).

13. The first message is a discovery request message for discovering the EAS, The second message is a discovery response message in response to the first message, The first list of related EAS information and the second list of related EAS information are discovered in an EAS discovery process performed by the first network function (421) (S1102). The method according to any one of claims 9 to 12 (1100).

14. The first message is a discovery subscription message for subscribing to the discovery of the EAS, The second message is a discovery notification message in response to the first message, The first list of related EAS information and the second list of related EAS information are discovered in an EAS discovery process performed by the first network function (421) (S1102). The method according to any one of claims 9 to 12 (1100).

15. The first message further includes an indicator that explicitly points to an EAS association, The EAS discovery process is performed based on the indicator. The method according to claim 13 or 14 (1100).

16. The method according to any one of claims 7 to 15 (1100), wherein the functional component (411) is implemented as an edge enabler client (EEC), and the first and / or second message is sent via an edge-1 reference point.

17. A first network function that implements an edge enabler server (EES) in an edge data network (EDN), At least one processor, A non-temporary computer-readable medium coupled to the at least one processor, wherein the non-temporary computer-readable medium includes instructions executable by the at least one processor, thereby configuring the at least one processor to perform the method according to any one of claims 1 to 6. A first network function, which includes the following:

18. A first network function that implements an edge enabler server (EES) in an edge data network (EDN), At least one processor, A non-temporary computer-readable medium coupled to the at least one processor, wherein the non-temporary computer-readable medium includes instructions executable by the at least one processor, thereby configuring the at least one processor to perform the method according to any one of claims 7 to 16. A first network function, which includes the following:

Images