Vertical application 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] FIELD Embodiments herein relate generally to the field of communications, and more particularly, embodiments herein relate to vertical applications in edge computing. [Background technology]

[0002] Vertical Applications and SEALs 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., Vehicle to Everything (V2X) 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) that can be reused across vertical applications. SEAL also specifies northbound application programming interfaces (APIs) for its individual services 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 general applicability of the Factory of the Future (FF) based on the service requirements for cyber-physical control applications specified in 3GPP TS 22.104 and 3GPP TS 22.261, and 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) For FF applications (apps), one proposed architecture in the study (clause 7.1 of TR 23.745) is shown in Figure 2, which is a schematic block diagram showing an application layer architecture 200 for FF.

[0006] The FF application layer function entities 213, 223 for the FF user equipment (UE) 201 and the FF application server are grouped into an FF application-specific layer and an FF application enabler (FAE) layer. The FAE layer provides the FF application-specific layer with FAE capabilities. 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 the FAE-S reference point.

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

[0009] An FAE server 222 interacts with other FAE servers 222 via an FAE-E reference point.

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

[0011] FF application specific server 223 and FF application enabler server 222 consume SEAL services provided by SEAL server 221 via the SEAL-S reference point. FF application specific client 213 and FF application enabler client 212 consume SEAL services provided by 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 as specified in 3GPP TS 23.434 -Identity 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 necessary to enable edge applications over 3GPP networks. 3GPP TS 23.558 includes architectural requirements for enabling edge applications, application layer architectures that meet the architectural requirements, and procedures for enabling the deployment of edge applications.

[0014] For edge computing support, objectives include the exposure of northbound APIs for edge applications and the evolution 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] 3 is a schematic block diagram illustrating an architecture 300 for enabling edge applications. The EDN 302 is a local data network. An edge application server (EAS) 322 and an edge enabler server (EES) 321 are included within the EDN 302. An edge configuration server (ECS) 304 provides configuration related to the EES 321, including details of the EDN 302 that hosts the EES 321. The UE 301 includes an application client 312 and an edge enabler client (EEC) 311. The EAS 322, EES 321, and ECS 304 may interact with a 3GPP core network 303. Summary of the Invention

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

[0017] In view of the above, embodiments herein propose a unified view for at least the UE to select application servers deployed at the edge, particularly to facilitate utilization of different applications and enablers in vertical domains when there is some relationship between those servers.

[0018] In an embodiment, a first method is proposed, which is performed by a first network function implementing an Edge Enabler Server (EES) in an Edge Data Network (EDN). The method may comprise receiving, from a second network function implementing an Edge Application Server (EAS) in the EDN, a registration request message comprising information indicating a list of relevant EAS information.

[0019] In another embodiment, a second method is proposed, which is performed by a second network function implementing an Edge Application Server (EAS) in an Edge Data Network (EDN). The method may comprise sending a registration request message to a first network function implementing an Edge Enabler Server (EES) in the EDN, the registration request message comprising information pointing to a first list of associated EAS information.

[0020] In yet another embodiment, a third method is proposed, which is performed by a first network function implementing an Edge Enabler Server (EES) in an Edge Data Network (EDN). The method may include receiving a first message from a functional component of a User Equipment (UE) for discovering at least one second network function implementing an Edge Application Server (EAS) in the EDN. The method may further include sending a second message to the functional component of the UE, the second message including information indicating a first list of related EAS information.

[0021] In yet another embodiment, a fourth method is proposed, which is implemented by a first functional component in a user equipment (UE). The method may include 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 include receiving a second message from the first network function, the second message including information indicating a first list of related EAS information.

[0022] In yet another embodiment, a fifth method is proposed, which is implemented by a second functional component in a user equipment (UE), and may further comprise receiving, from a first functional component in the UE, a message including information indicating a list of associated edge application server (EAS) information.

[0023] In yet another embodiment, a user equipment (UE) is proposed that includes a plurality of functional components. The plurality of functional components further includes a first functional component that implements an edge enabler client (EEC), a third functional component that implements an application enabler client for a vertical application, and a fourth functional component that implements an application-specific client for the vertical application. The third functional component can provide at least one service to one or more fourth functional components. The first functional component and the third functional component can communicate via an Edge-5 reference point to enable the at least one service.

[0024] In yet another embodiment, a communication system for vertical applications in an 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 the 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 yet another embodiment, a first network function is proposed that implements an Edge Enabler Server (EES) in an Edge Data Network (EDN). 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 includes instructions executable by the at least one processor, whereby the at least one processor is configured to perform the first and third methods described above.

[0026] In yet another embodiment, a second network function is proposed that implements an Edge Application Server (EAS) in an Edge Data Network (EDN). 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 includes instructions executable by the at least one processor, whereby the at least one processor is configured to perform the second method described above.

[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 including instructions executable by the at least one processor, whereby the at least one processor is configured to perform the fourth and fifth methods described above.

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

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

[0030] According to embodiments herein, based on relevant EAS information, the UE may perform joint EAS discovery and selection for vertical applications in edge deployments, such that both the application enabler client and the application-specific server in 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 disclosure and to enable those skilled in the art to make and use the embodiments disclosed herein. In the drawings, like reference numbers indicate equivalent or functionally similar elements. [Brief explanation of the drawings]

[0032] [Figure 1] FIG. 1 is a schematic block diagram illustrating the architecture for 5G vertical applications proposed by the 3GPP SA6 working group. [Figure 2]FIG. 1 is a schematic block diagram illustrating an application layer architecture for FF. [Figure 3] FIG. 1 is a schematic block diagram illustrating an architecture for enabling edge applications. [Figure 4] 1 is a schematic block diagram illustrating an example wireless communication system in which embodiments herein may be implemented. [Figure 5] FIG. 1 is a schematic block diagram illustrating a more general edge deployment for vertical applications. [Figure 6] 1 is a schematic signaling chart showing messages in vertical EAS registration in an edge deployment. [Figure 7] 10 is a schematic signaling chart showing messages in a vertical EAS discovery request response in an edge deployment. [Figure 8] 1 is a schematic signaling chart showing messages in vertical EAS discovery notification in an edge deployment. [Figure 9] 1 is a schematic flow chart illustrating an exemplary EAS registration method performed by a first network function, according to embodiments herein. [Figure 10] 10 is a schematic flow chart illustrating an exemplary EAS registration method performed by a second network function, according to embodiments herein. [Figure 11] 1 is a schematic flow chart illustrating an exemplary EAS discovery method performed by a first network function, according to embodiments herein. [Figure 12] 1 is a schematic flow chart illustrating an exemplary EAS discovery method performed by a first functional component in a UE, according to embodiments herein. [Figure 13] 10 is a schematic flow chart illustrating an exemplary EAS discovery method performed by a second functional component in a UE, according to embodiments herein. [Figure 14] 1 is a schematic block diagram illustrating an exemplary first network function according to embodiments herein. [Figure 15] FIG. 2 is a schematic block diagram illustrating an exemplary second network function according to embodiments herein. [Figure 16] 1 is a schematic block diagram illustrating an exemplary UE, according to embodiments herein. [Figure 17] FIG. 1 is a schematic block diagram illustrating an exemplary computer-implemented device according to embodiments herein. DETAILED DESCRIPTION OF THE INVENTION

[0033] Embodiments herein are described in detail below with reference to the accompanying drawings in which embodiments are shown. However, the embodiments herein may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Elements of the drawings are not necessarily to scale relative to each other.

[0034] A reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, the appearances of the phrase "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment.

[0035] The term "A, B, or C" as used herein means "A" or "B" or "C", the term "A, B, and C" as used herein means "A" and "B" and "C", and the term "A, B, and / or C" as used herein means "A", "B", "C", "A and B", "A and C", "B and C" or "A, B, and C".

[0036] Hereinafter, a future factory application will be described as an example of a vertical application in one embodiment of the present disclosure.

[0037] There is a key problem #9 described in TR 23.745, section 5.9, and existing solutions #5 and #6 place FF enablers (clients and servers) as EAS in the context of Edge App architecture. However, it is unclear how FF specific applications (clients and servers) can utilize Edge App services.

[0038] According to TS 22.104 clause 5.1, a local approach for network-side communication services is preferred to reduce latency (between UE and UE via Uu, and between UE and network server) or to keep sensitive data on a non-public network at the factory site. In that case, the question remains how to support FFAPP communication via edge deployments on the network side.

[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, and the FF application-specific server 223 registers with the FAE server 222 via the FAE-S reference point.

[0040] According to Solution #4, the FFAS server 223 needs to register with the FAE server 222, and the FAE client 212 also needs to register with the FAE server 222. However, from the UE's perspective, under edge deployment, if the EAS discovery service provided by the edge app is used but the selection of the FFAS server 223 and the FAE server 222 is handled separately, the selected FAE server 222 may not have the registered FFAS server 223, and therefore 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 related IE stored in the FAE client 212 through the FAE server 222, or the FAE client 212 may not be able to send the device application management operation result to the FF application-specific server 223 through the FAE server 222.

[0041] Generally, in the case of edge deployment, if the application enabler client and the 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 coordination.

[0042] In view of the above problems, the embodiments herein provide additional information, related EAS information, in the EAS registration procedure to describe the relationship between servers, which can help the UE select an appropriate EAS with a unified view.

[0043] Edge Computing for FFAPP This solution in the present disclosure addresses key problem #9 above, namely, communication services over edge deployment. Table numbers, subclause numbers, etc. are found in 3GPP TR 23.745 V1.2.0.

[0044] The Edge App architecture is specified in 3GPP TS 23.558

[10] . The details of the Edge-5 reference point are not specified in Rel-17.

[0045] FIG. 4 illustrates an example of an edge deployment 400 for an FF app. For simplicity, reference points between the enabler server and the 5GS are omitted, as are reference points for inter-enabler server communication in the same enabler layer. On the UE 401 side, an FF application-specific client 414 and an FAE client 413 interact with an edge enabler client (EEC) 411 via the Edge-5 reference point. In the edge data network (EDN) 402, edge application servers (EAS), such as an FF application-specific server 424 and an FF application enabler server 423, interact with an 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 an edge configuration server (ECS) 404 via the Edge-4 reference point, for example, to discover candidate EESs. EEC411 interacts with EES421 via the Edge-1 reference point, for example, to discover candidate EASs (e.g., FF application-specific servers 424 and FF application enabler servers 423) and to provide the discovered EASs to application clients (e.g., FF application-specific clients 414 and FF application enabler clients 413).

[0046] In the EDN 402, 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, FFAS server 424 needs to register with FAE server 423, and FAE client 413 needs to register with FAE server 423 during the onboarding process. Similarly, FFAS server 424 can discover and register with the appropriate FAE server 423. Ideally, 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 the UE's perspective, under edge deployment, if the EAS discovery service provided by the edge enabler 411 / 421 is used but the selection of the FFAS server 424 and the FAE server 423 is handled separately, the selected FFAS server 424 may not be onboarded on the selected FAE server 423, and therefore some functions may not be able to operate, i.e., for example, the FF application-specific server 424 may not be able to discover the FF device application management related IEs stored in the FAE server 413, or the FAE client 413 may not be able to send the device application management operation results to the FF application-specific server 424.

[0048] To enable the selection of an FFAS server 424 and an onboarding FAE server 423 for the FFAS server 424, in an edge deployment, the FFAS server 424 and the FAE server 423 need to exchange their application server information during onboarding. After both parties store their associated application server information, the FAE server 423 and the FFAS server 424 register with the EES 421 via the Edge-3 reference point. As a result, the EEC 411 can discover a list of candidate FAE servers 423, including their associated FFAS servers 424, and a list of candidate FFAS servers 424, including their associated FAE servers 423, based on interactions with the FAE client 413 via the Edge-5 reference point.

[0049] For SEAL, due to the sparse administrative procedures specified in 3GPP, there is no such association between the VAL servers 423, 424 and the SEAL server 422. For SEAL identity management (IM) functionality, before the SEAL IM client 412 can be granted any tokens from the SEAL IM server 422, the SEAL IM client 412 must register with the SEAL IM server 422 as described in 3GPP TS 33.434 [TS33434]. If there is interaction between the VAL servers 423, 424 and the SEAL IM server 422 for token validation purposes, which is outside the scope of 3GPP (and also IETF RFC 6749 [rfc6749]), EAS discovery must take into account the association between the VAL server (e.g., FAE server 423) and the SEAL IM server 424.

[0050] There are several ways to accomplish the selection of an associated EAS server 422, 423, 424 in the UE 401, and the following list describes two alternatives for informational purposes, as both FAE-C and Edge-5 are not detailed in the Rel-17 timeline.

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

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

[0053] According to 3GPP TS 23.558

[10] , the EEC 411 may throttle the number of discovered application servers 422, 423, 424 when providing discovery results to the application clients 412, 413, 414. If such functionality in the EEC 411 is used (e.g., delegated by the application clients 412, 413, 414), the EEC 411 will not throttle the number of discovered application servers 422, 423, 424 based solely on a single application with associated EAS information.

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

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

[0056] Solution Evaluation This solution addresses key problem #9, "How to support FFAPP communication over edge deployments?" and provides deployment options for FF applications in edge application architectures.

[0057] In such a deployment, if there is a relationship between the FFAS server 424 and the FAE server 423 for the onboarding process, the relevant EAS information needs to be provided during the EAS registration procedure, and the UE 401 needs to select a preferred application server using joint consideration of the associated application servers.

[0058] Additionally, the EEC 411 may explicitly indicate for an EAS association in an EAS discovery request or an EAS discovery subscription request so that only EASs 422, 423, 424 that have an EAS association are discovered.

[0059] The benefit of this is to narrow down the number of discovered EASs 422, 423, 424 in the discovery response / notification so that the UE 401 can process less information in selecting an EAS 422, 423, 424 with a unified view.

[0060] As mentioned above, Figure 4 is a schematic block diagram illustrating an example wireless communication system 400 in which embodiments herein may be implemented. Among other things, Figure 4 illustrates an FF app in an edge deployment.

[0061] The Edge-1 reference point in Figure 4 enables interaction between the EES 421 and the EEC 411. The Edge-1 reference point supports a) registration and deregistration of the EEC 411 with the EES 421, b) retrieval and provisioning of EAS configuration information, and c) discovery of EASs available in the EDN 402.

[0062] 4 enables interaction between the EES 421 and the EASs 422, 423, 424. The Edge-3 reference point supports a) registration of the EASs 422, 423, 424 with availability information (e.g., time constraints, location constraints), b) deregistration of the EASs 422, 423, 424 from the EES 421, c) discovery of target EAS information to support application context transfer, d) providing access to network capability information (e.g., location information, quality of service (QoS) related information), and e) requesting setup of a data session between the application client 412, 413, 414 and the EASs 422, 423, 424 with a specific QoS.

[0063] Note that in the examples herein, SEAL server 422, FAE server 423, and FFAS server 424 may all act as EASs from the perspective of EES 421, and thus SEAL server 422, FAE server 423, and FFAS server 424 may also be referred to as EAS 422, EAS 423, and EAS 424, respectively. Similarly, 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. In particular, Figure 5 illustrates edge deployment options for supporting applications (application-specific servers and their enabler servers) in vertical domains (e.g., Factory of the Future, V2X, Unmanned Aerial Systems). In Figure 5, different application clients and servers are split in different application layers.

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

[0066] As shown in FIG. 5, server B523 has an association with server D524 as a child EAS, an association with server C525 as a sibling EAS, and an association with server A522 as a parent EAS, server D524 has an association with server B523 as a parent EAS, server C525 has an association with server B523 as a sibling EAS, and server A522 has an association 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 an embodiment, a user equipment (UE) is proposed that includes multiple functional components. For example, the multiple functional components may include a first functional component that implements an edge enabler client (EEC) and a second functional component that implements an application enabler client for a vertical application. In an embodiment, the first functional component and the second functional component may communicate via an Edge-5 reference point.

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

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

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

[0072] In an embodiment, the first functional component may communicate with a first network function implementing an edge enabler server (EES) via the Edge-1 reference point. The second functional component may communicate with a second network function implementing an application enabler server for the vertical application via the AE-1 reference point. The third functional component may communicate with a third network function implementing an application-specific server for the vertical application via the 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. The fourth functional component may communicate with a fourth network function implementing a service enabler architecture layer (SEAL) server for the vertical application via the SEAL-UU reference point.

[0073]

[0009] In an embodiment, a communication system for vertical applications in an edge deployment is further proposed, comprising a plurality of network functions in an edge data network (EDN). The plurality of 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 network function and the second network function communicate via an Edge-3 reference point.

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

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

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

[0077] In an embodiment, a first network function may communicate with a first functional component implementing an edge enabler client (EEC) via the Edge-1 reference point. A second network function may communicate with a second functional component implementing an application enabler client of a vertical application via the AE-1 reference point. A third network function may communicate with a third functional component implementing an application-specific client of a vertical application via the 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 of a vertical application via the SEAL-UU reference point.

[0078] In some embodiments, each EAS 422, 423, 424, 522, 523, 524, 525 registers with the EES 421, 521 with its own profile and optional associated EAS information (see messages in FIG. 6 below), so that after EAS discovery (see messages in FIGS. 7 and 8 below), the UEs 401, 501 can have joint consideration in selecting edge application servers 422, 423, 424, 522, 523, 524, 525 that have a management relationship with each other. For example, there can be coordination between client B 513 and client D 514, e.g., via a Dc-Bc reference point, so that the selected server B 523 and server D 524 to be used for client B 513 and client D 514, respectively, are associated.

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

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

[0081] In some embodiments, in the UE 401, 501, the EEC 411, 511 is responsible for joint EAS discovery and selection for all clients 412, 413, 414, 512, 513, 514, 515 in the above layers. For example, client D 514 delegates EAS discovery and selection to client B 513, which then informs client D 514 of the selected server D 524 via the Dc-Bc reference point.

[0082] Although the embodiments are described below primarily with reference to the architecture of FIG. 4, the embodiments may be equally applicable to the architecture of FIG. 5 and similar architectures for vertical applications.

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

[0084] In an embodiment, the following prerequisites are met before performing vertical EAS registration:

[0085] (1) EAS identification information is set in the EAS 422. (2) The address (for example, URI) of the EES 421 is set in the EAS 422. (3) Both EAS 422 and EES 421 have the necessary credentials to enable communication.

[0086] In an embodiment, the signaling chart in FIG. 6 may include the following messages or steps:

[0087] Step 1. The EAS 422 determines that registration with the EES 421 is required (eg, the EAS 422 is instantiated and started up).

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

[0089] In an embodiment, the request may also include associated EAS information to register associations between the EASs 422, 423, 424. For example, information about the EAS profiles in Table 1 or Table 2 above may be included in the request. As a result, in a subsequent EAS discovery procedure, the UE 401 may discover associations between the EASs 422, 423, 424, which may be used to select the EASs 422, 423, 424 for joint consideration.

[0090] Step 3. The EES 421 performs an authorization check to verify whether the EAS 422 has authorization to register on the EES 421.

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

[0092] Similarly, the EAS 423 and / or the EAS 424 may perform the registration procedure described in FIG. 6 to register an EAS profile with the EES 421 .

[0093] FIG. 7 is a schematic signaling chart showing messages in a vertical EAS discovery request response in an edge deployment.

[0094] In an embodiment, the following prerequisites are met before conducting vertical EAS discovery:

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

[0096] In an embodiment, the signaling chart in FIG. 7 may include the following messages or steps:

[0097] Step 1. The EEC 411 sends an EAS discovery request to the EES 421. The EAS discovery request includes a requester identifier, e.g., an EEC ID, along with security credentials, and may include an EAS discovery filter to retrieve information about a particular EAS or category of EAS, e.g., gaming applications.

[0098] Step 2. Upon receiving a request from the EEC 411, the EES 421 checks whether the EEC 411 is authorized to discover the requested EAS. The authorization check may apply to an individual EAS, a category of EAS, or to an EDN, in other words, to all EASs. The EES 421 may utilize the capabilities of the 3GPP core network 403 (e.g., UE location) as specified in Section 8.9.3. If an EAS discovery filter is provided by the EEC 411, the EES 421 identifies the EASs 422, 423, 424 based on the provided EAS discovery filter and the UE location. When no EAS discovery filter is provided, If available, the EES 421 identifies the EAS 422, 423, 424 based on the UE-specific service information in the EES 421 and the UE location; The EES 421 identifies the EASs 422, 423, 424 by applying ECSP policies (eg, based solely on the UE location).

[0099] If the EES 421 is unable to determine the EAS information using the inputs in the EAS discovery request, the UE-specific service information in the EES 421, or the ECSP policy, the EES 421 rejects the service provisioning request and responds with an appropriate failure cause.

[0100] If the UE 401 is located outside the geographical area or topological coverage area of ​​the EAS 422, 423, 424, the EES 421 does not include it 422, 423, 424 in the discovery response.

[0101] Step 3. If the request is processed successfully, the EES 421 sends an EAS discovery response to the EEC 411 containing information about the discovered EASs 422, 423, 424. For the discovered EASs 422, 423, 424, this includes endpoint information. Depending on the EAS discovery filters received in the EAS discovery request, the response may include additional information about the matched capabilities, such as service permission levels, application client locations the EAS can support, key performance indicators, etc.

[0102] In an embodiment, the response may also include relevant EAS information. For example, information about the EAS profiles in Table 1 or Table 2 above may be included in the response. As a result, UE 401 may discover associations between EASs 422, 423, 424, which may be used to select EASs 422, 423, 424 for joint consideration.

[0103] Upon receiving the EAS discovery response, the EEC 411 may use the endpoint information for routing outgoing application data traffic to the EAS, if necessary, 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 EEC 411 may cache the EAS information only for the duration specified by the Lifetime IE.

[0104] FIG. 8 is a schematic signaling chart showing messages in vertical EAS discovery notification in an edge deployment.

[0105] In an embodiment, the following prerequisites are met before conducting vertical EAS discovery:

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

[0107] In an embodiment, the signaling chart in FIG. 8 may include the following messages or steps: Step 1. An event occurs in the EES 421 that satisfies the trigger condition for providing EAS discovery information for the subscribed EEC 411. If the UE location information is not available, the EES 421 may obtain the UE location by utilizing the capabilities of the 3GPP core network 403 as specified in clause 8.9.2. If an EAS discovery filter was provided by the EEC 411 during subscription creation, the EES 421 identifies the EASs 422, 423, 424 based on the provided EAS discovery filter and the UE location. If no EAS discovery filter was provided, If available, the EES 421 identifies the EAS 422, 423, 424 based on the UE-specific service information in the EES 421 and the UE location; The EES 421 identifies the EASs 422, 423, 424 by applying ECSP policies (eg, based solely on the UE location).

[0108] If the UE 401 is located outside the geographical area or topological service area of ​​the edge application server, the EES 421 does not include this EAS in the EAS discovery notification.

[0109] Step 2. The EES 421 sends an EAS discovery notification to the EEC 411 with the EAS information determined in step 1.

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

[0111] 9 is a schematic flowchart illustrating an exemplary EAS registration method 900 performed by a first network function, according to embodiments herein. In embodiments, the flowchart in FIG. 9 may be implemented in the EES described above (such as EES 421).

[0112] Method 900 may begin in 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 registration request message comprising information pointing to a first list of relevant EAS information.

[0113] In embodiments, the information pointing to the first list of associated EAS information may be included in an 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 an embodiment, the first list of related EAS information may comprise at least one first entry for at least one third network function (e.g., EAS 423) that implements EAS in the EDN. Each first entry may point to an EAS profile for the respective third network function. The EAS profile for each third network function may include an EAS ID for the respective third network function and a relationship between the second network function and the respective third network function.

[0115] For example, the EAS 422 may send to the EES 421 an EAS profile of the EAS 422 that includes a first list of associated EAS information (which may indicate associations of the EAS 422 with other EASs 423 and / or 424).

[0116] In another example, the EAS 423 may send the EAS profile of the EAS 423 to the EES 421, which includes a first list of associated EAS information (which may indicate associations of the EAS 423 with other EASs 424).

[0117] In an embodiment, the relationship may indicate that the third network function is a parent, child, or sibling of the second network function, as may be seen from FIG. 4 or FIG.

[0118] In an embodiment, each of the at least one first entry in the first list of associated EAS information may further indicate endpoint information of a respective third network function.

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

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

[0121] In an embodiment, the relationship may indicate that the fourth network function is a parent, child, or sibling of the third network function, as may be seen from FIG. 4 or FIG.

[0122] In an embodiment, each of the at least one second entry in the second list of associated EAS information may further indicate endpoint information of a respective fourth network function.

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

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

[0125] In an embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server for vertical applications 422, and the third network function is implemented as Vertical Application Layer (VAL) servers 423, 424. There may be an administrative or management relationship 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 a boarding configuration).

[0126] In embodiments, the SEAL server 422 may include a SEAL Identity Management (IM) server. The SEAL IM server may provide token validation services to the VAL servers 423, 424 to validate tokens assigned by the SEAL IM server.

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

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

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

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

[0131] In embodiments, the first network function may store information that points to another list of associated EAS information. For example, the network function may store information that points to a second list of associated EAS information.

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

[0133] The method 900 may then proceed to step S903, where the first network function may send a registration response message to the second network function that implements the EAS.

[0134] The above steps are only examples, and the first network function may perform the actions described with respect to Figures 6 to 8 to manage relevant EAS information to provide a unified view for the UE to select an application server deployed at the edge.

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

[0136] Method 1000 may begin in step S1001, in which a second network function (e.g., EAS 422) may receive a registration request from a third network function (e.g., EAS 423 or 424) to register the third network function with the second network function.

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

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

[0139] Method 1000 may then proceed to step S1002, where the second network function may store the 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 associated EAS information in the EAS profile of the second network function. In doing so, an association may be established between the second network function and the third network function (and additional network functions).

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

[0141] In embodiments, the information pointing to the first list of associated EAS information may be included in an 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 an embodiment, the first list of related EAS information may include at least one first entry for at least one third network function that implements EAS in the EDN. Each first entry may point to an EAS profile for the respective third network function. The EAS profile for each third network function may include an EAS ID for the respective third network function and a relationship between the second network function and the respective third network function.

[0143] In an embodiment, the relationship may indicate that the third network function is a parent, child, or sibling of the second network function, as may be seen from FIG. 4 or FIG.

[0144] In an embodiment, each of the at least one first entry in the first list of associated EAS information may further indicate endpoint information of a respective third network function.

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

[0146] In an embodiment, the relationship may indicate that the fourth network function is a parent, child, or sibling of the third network function, as may be seen from FIG. 4 or FIG.

[0147] In an embodiment, each of the at least one second entry in the second list of associated EAS information may further indicate endpoint information of a respective fourth network function.

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

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

[0150] In an embodiment, the second network function (e.g., EAS 422) is implemented as a Service Enabler Architecture Layer (SEAL) server for vertical applications, and the third network function is implemented as a Vertical Application Layer (VAL) server (e.g., EAS 423, 424). There may be an administrative or management relationship 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 a boarding configuration).

[0151] In embodiments, the SEAL server 422 may include a SEAL Identity Management (IM) server. The SEAL IM server may provide token validation services to the VAL servers 423, 424 to validate tokens assigned by the SEAL IM server.

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

[0153] In an embodiment, the VAL server 423, 424 is a FF application specific (FFAS) server 424 or a FF application enabler (FAE) server 423.

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

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

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

[0157] 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 FIG. 11 may be implemented in the EES described above (such as EES 421).

[0158] Method 1100 may begin in 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 implementing an edge application server (EAS) in EDN 402.

[0159] In an embodiment, the first message may be a discovery request message to discover an EAS server.

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

[0161] In an embodiment, the first message further comprises an indicator that explicitly indicates an EAS association. For example, the EEC 411 may explicitly indicate for an EAS association in an EAS discovery request or an EAS discovery subscription request so that only EASs with an EAS association are discovered.

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

[0163] In embodiments, the information pointing to the first list of associated EAS information may be included in an EAS profile of the second network function. The EAS profile of the second network function (e.g., EAS 422) may further include information pointing to an EAS ID and information pointing to an EAS endpoint of the second network function.

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

[0165] In an embodiment, the relationship may indicate that the third network function is a parent, child, or sibling of the second network function, as may be seen from FIG. 4 or FIG.

[0166] In an embodiment, each of the at least one first entry in the first list of associated EAS information may further indicate endpoint information of a respective third network function.

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

[0168] In an embodiment, the relationship may indicate that the fourth network function is a parent, child, or sibling of the third network function, as may be seen from FIG. 4 or FIG.

[0169] In an embodiment, each of the at least one second entry in the second list of associated EAS information may further indicate endpoint information of a respective fourth network function.

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

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

[0172] In an embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server for vertical applications 422, and the third network function is implemented as Vertical Application Layer (VAL) servers 423, 424. There may be an administrative or management relationship 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 a boarding configuration).

[0173] In embodiments, the SEAL server 422 may include a SEAL Identity Management (IM) server. The SEAL IM server may provide token validation services to the VAL servers 423, 424 to validate tokens assigned by the SEAL IM server.

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

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

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

[0177] The method 1100 may then proceed to step S1103, where the first network function may send a second message to the functional component of the UE, the second message including information indicating the first list of relevant EAS information.

[0178] In an embodiment, the second message is a discovery response message in response to the first message (request message).

[0179] In an embodiment, the second message is a discovery notification message in response to the first message (the subscription message).

[0180] In an 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 above steps are only examples, and the second network function may perform the actions described with respect to Figures 6 to 8 to manage relevant EAS information to provide a unified view for the UE to select application servers deployed at the edge.

[0182] 12 is a schematic flowchart illustrating an example EAS discovery method 1200 performed by a first functional component in a UE, according to embodiments herein. In embodiments, the flowchart in FIG. 12 may be implemented in the EEC described above (such as EEC 411).

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

[0184] In an embodiment, the second functional component is implemented as a Service Enabler Architecture Layer for Vertical Applications (SEAL) client 412. Additionally, the third functional component is implemented as a Vertical Application Layer (VAL) client 413, 414.

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

[0186] In an 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 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.

[0188] In an embodiment, the first message may be a discovery request message to discover an EAS server.

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

[0190] In an embodiment, the first message further comprises an indicator that explicitly indicates an EAS association. For example, the EEC 411 may explicitly indicate for an EAS association in an EAS discovery request or an EAS discovery subscription request so that only EASs with an EAS association are discovered.

[0191] In an embodiment, after receiving a first message from a first functional component in the UE, a first network function (e.g., EES 421) may perform an EAS discovery process to discover EASs 422, 423, and 424. In an embodiment, the EAS discovery process is performed based on an indicator that explicitly indicates an EAS association. As a result, the first network function may discover at least one EAS. There may be an association between the 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, where the first functional component may receive a second message from the first network function, the second message including information indicating a first list of relevant EAS information.

[0193] In an embodiment, the second message is a discovery response message in response to the first message (request message).

[0194] In an embodiment, the second message is a discovery notification message in response to the first message (the subscription message).

[0195] In an embodiment, the first and / or second message is sent via the Edge-1 reference point.

[0196] In embodiments, the information pointing to the first list of associated EAS information may be included in an EAS profile of the second network function (such as EAS 422). 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 an embodiment, the first list of related EAS information may comprise at least one first entry for at least one third network function (e.g., EAS 423) that implements EAS in the EDN. Each first entry may point to an EAS profile for the respective third network function. The EAS profile for each third network function may include an EAS ID for the respective third network function and a relationship between the second network function and the respective third network function.

[0198] In an embodiment, the relationship may indicate that the third network function is a parent, child, or sibling of the second network function, as may be seen from FIG. 4 or FIG.

[0199] In an embodiment, each of the at least one first entry in the first list of associated EAS information may further indicate endpoint information of a respective third network function.

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

[0201] In an embodiment, the relationship may indicate that the fourth network function is a parent, child, or sibling of the third network function, as may be seen from FIG. 4 or FIG.

[0202] In an embodiment, each of the at least one second entry in the second list of associated EAS information may further indicate endpoint information of a respective fourth network function.

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

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

[0205] In an embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server for vertical applications 422, and the third network function is implemented as Vertical Application Layer (VAL) servers 423, 424. There may be an administrative or management relationship 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 a boarding configuration).

[0206] In embodiments, the SEAL server 422 may include a SEAL Identity Management (IM) server. The SEAL IM server may provide a token validation service to the VAL server to validate tokens assigned by the SEAL IM server.

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

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

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

[0210] In an embodiment, the information indicating the first list of related EAS information is included in a set of EAS profiles of a first set of network functions that implement EAS in the EDN. For example, the first network function may discover a set of EASs (i.e., two or more EASs or at least one EAS) and provide information (e.g., EAS profiles) of the discovered set of EASs.

[0211] Method 1200 may then proceed to step S1204, where the first functional component may determine an 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 the set of EAS profiles. Additionally, the first functional component may determine a second set of network functions that implement EAS in the EDN from the first list of related EAS information. It should be noted that, depending on the received related EAS information, the EEC may use various approaches to determine an EAS for providing a vertical application service.

[0212] In an embodiment, at least two network functions for selection are associated. For example, at least two network functions from the first and second sets 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 a boarding configuration).

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

[0214] In an embodiment, the first functional component may select only one set of associated network functions for the second functional component and the third functional component, i.e., 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 delegation request.

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

[0216] Upon receiving the notification, the second functional component and the third functional component may coordinate to select a network function with which the selected network function is to be associated. 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 a 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 the above step S1201 and steps S1202-S1203 may be performed in any manner, for example, in any sequence, simultaneously, or separately.

[0218] The above steps are only examples, and the UE may perform actions to manage relevant EAS information to select application servers deployed at the edge in an integrated view.

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

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

[0221] In an embodiment, the second functional component is implemented as a Service Enabler Architecture Layer for Vertical Applications (SEAL) client 412. Additionally, the third functional component is implemented as a Vertical Application Layer (VAL) client 413, 414.

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

[0223] In an 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, where 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] Then, after receiving the request from the second functional component, the first functional component (e.g., EEC 411) may further request the first functional component (e.g., EES 421) for an EAS discovery process. The first network function may then perform an EAS discovery process to discover EASs (e.g., EASs 422, 423, 424). As a result, the first network function may discover at least one EAS. There may be an association between the at least one EAS. For example, the first network function may discover at least a first list of related EAS information. The discovery of EASs may further refer to the steps described above with respect to FIG. 12.

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

[0227] In embodiments, the information pointing to the first list of associated EAS information may be included in an 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 an embodiment, the first list of related EAS information may include at least one first entry for at least one third network function that implements EAS in the EDN. Each first entry may point to an EAS profile for the respective third network function. The EAS profile for each third network function may include an EAS ID for the respective third network function and a relationship between the second network function and the respective third network function.

[0229] In an embodiment, the relationship may indicate that the third network function is a parent, child, or sibling of the second network function, as may be seen from FIG. 4 or FIG.

[0230] In an embodiment, each of the at least one first entry in the first list of associated EAS information may further indicate endpoint information of a respective third network function.

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

[0232] In an embodiment, the relationship may indicate that the fourth network function is a parent, child, or sibling of the third network function, as may be seen from FIG. 4 or FIG.

[0233] In an embodiment, each of the at least one second entry in the second list of associated EAS information may further indicate endpoint information of a respective fourth network function.

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

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

[0236] In an embodiment, the second network function is implemented as a Service Enabler Architecture Layer (SEAL) server for vertical applications 422, and the third network function is implemented as Vertical Application Layer (VAL) servers 423, 424. There may be an administrative or management relationship 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 a boarding configuration).

[0237] In embodiments, the SEAL server 422 may include a SEAL Identity Management (IM) server. The SEAL IM server may provide token validation services to the VAL servers 423, 424 to validate tokens assigned by the SEAL IM server.

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

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

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

[0241] In an embodiment, the information indicating the first list of related EAS information is included in a set of EAS profiles of a first set of network functions that implement EAS in the EDN. For example, the first network function may discover a set of EASs (i.e., two or more EASs or at least one EAS) and provide information (e.g., EAS profiles) of the discovered set of EASs.

[0242] Method 1300 may then proceed to step S1304, where the second functional component may determine an EAS for selection. For example, the second functional component may determine a first set of network functions that implement EAS in the EDN from the set of EAS profiles. Additionally, the second functional component may determine a second set of network functions that implement EAS in the EDN from the first list of related EAS information. It should be noted that, depending on the received related EAS information, the second functional component may use various approaches to determine an EAS for providing the vertical application service.

[0243] In an embodiment, at least two network functions for selection are associated. For example, at least two network functions from the first and second sets 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 a boarding configuration).

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

[0245] In an embodiment, the second functional component may select only one set of associated network functions for the second functional component and the third functional component, 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 delegation request.

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

[0247] In an embodiment, the second functional component and the third functional component may coordinate to select a network function with which the selected network function is to be associated. For example, the selected network function has 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 a boarding configuration).

[0248] It should be noted that the above step S1301 and steps S1302-S1303 may be performed in any manner, for example, in any sequence, simultaneously, or separately.

[0249] It is further noted that the above step S1301 (in other words, delegating EAS discovery and selection) may be a mandatory step, whereby the subsequent EAS selection step S1304 may be performed in the second functional component; otherwise, step S1304 is performed in the third functional component. Moreover, the above step S1301 may be an optional step, i.e., there is no delegation between the second functional component and the third functional component, in which case the second functional component and the third functional component need to coordinate EAS selection when relevant EAS information is received.

[0250] The above steps are only examples, and the UE may perform actions to manage relevant EAS information to select application servers deployed at the edge in an integrated view.

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

[0252] In an embodiment, the first network function 1400 may include at least one processor 1401 and a non-transitory computer-readable medium 1402 coupled to the at least one processor 1401. The non-transitory computer-readable medium 1402 includes instructions executable by the at least one processor 1401, whereby the at least one processor 1401 is configured to perform steps in an exemplary method 900 shown in the schematic flowchart of Figure 9 and an exemplary method 1100 shown in the schematic flowchart of Figure 11, details of which will be omitted here.

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

[0254] It should be understood that a network function may be implemented either as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, for example, on a cloud infrastructure.

[0255] FIG. 15 is a schematic block diagram illustrating an exemplary second network function (such as EAS 422, 423, 424) according to embodiments herein.

[0256] In an embodiment, the second network function 1500 may include at least one processor 1501 and a non-transitory computer-readable medium 1502 coupled to the at least one processor 1501. The non-transitory computer-readable medium 1502 includes instructions executable by the at least one processor 1501, whereby the at least one processor 1501 is configured to perform steps in the exemplary method 1000 shown in the schematic flowchart of Figure 10, details of which will be omitted herein.

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

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

[0259] 16 is a schematic block diagram illustrating an exemplary UE according to embodiments herein. In an embodiment, the UE 1600 may include functional components (such as the EEC 411, the SEAL 412, the enabler client 413, and the application-specific client 414) as shown in FIGS.

[0260] In an embodiment, the UE 1600 may include at least one processor 1601 and a non-transitory computer-readable medium 1602 coupled to the at least one processor 1601. The non-transitory computer-readable medium 1602 includes instructions executable by the at least one processor 1601, whereby the at least one processor 1601 is configured to perform steps in an exemplary method 1200 shown in the schematic flowchart of Figure 12 and / or steps in an exemplary method 1300 shown in the schematic flowchart of Figure 13, details of which are omitted herein.

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

[0262] Additionally, functional components in a UE (e.g., EEC, SEAL, enabler client, application-specific client) may 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 example method 1200 / 1300 or one or more steps shown in Figures 6-8 related to a UE.

[0263] In some embodiments, the non-limiting term UE is used. The UE 1600 described herein may be any type of wireless device capable of, configured to, arranged to, and / or operable to communicate wirelessly with a network node and / or another wireless device, for example, via radio signals. Communicating wirelessly may involve transmitting and / or receiving radio signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for conveying information through the air. In particular embodiments, the UE 1600 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, when triggered by an internal or external event, or in response to a request from the network.

[0264] Generally, a UE may represent any device, e.g., a wireless communication device, that is capable of, configured for, arranged for, and / or operable for wireless communication. Examples of a UE include, but are not limited to, a smartphone. Further examples include a wireless camera, a wireless-enabled tablet computer, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a USB dongle, and / or a wireless customer premises equipment (CPE). Also, the UE 900 may be a wireless communication device, a target device, a D2D UE, a machine-type communication (MTC) UE or a UE capable of machine-to-machine (M2M) communication, a low-cost and / or low-complexity UE, a sensor equipped 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 particular example, a UE may be configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's 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, a "UE" may 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 that is intended for sale to or operation by a human user, but may not be initially associated with a particular human user.

[0266] 17 is a schematic block diagram illustrating an example computer-implemented device 1700 according to embodiments herein. In embodiments, the device 1700 may be configured as a device described above, such as the first network function 1400, the second network function 1500, the third network function, the fourth network function, or the UE 1600.

[0267] In an embodiment, the apparatus 1700 may include at least one processor, such as, but not limited to, a central processing unit (CPU) 1701, a computer-readable medium 1702, and a 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 an embodiment, 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 an embodiment, computer-readable medium 1702 (such as a non-transitory computer-readable medium) may be stored in memory 1703. In another embodiment, the computer program may be stored (and may be embodied as a computer-readable medium) at a remote location, e.g., in computer program product 1704, and may be accessible by processor 1701, e.g., via carrier 1705.

[0269] The computer readable medium 1702 and / or the computer program product 1704 may be provided and / or stored on a removable computer readable medium, such as a diskette, a CD (compact disc), a DVD (digital video disc), flash or similar removable memory medium (e.g., compact flash, SD (secure digital), memory stick, mini SD card, MMC multimedia card, smart media), HD-DVD (high definition DVD) or Blu-ray DVD, USB (universal serial bus) based removable memory medium, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or may be provided as a propagated signal over a network (e.g., Ethernet, ATM, ISDN, PSTN, X.25, the Internet, a local area network (LAN), or similar network capable of transporting data packets to infrastructure nodes).

[0270] Exemplary embodiments have been described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices), and / or non-transitory computer program products. It should be understood that blocks of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, may be implemented by computer program instructions performed by one or more computer circuits. These computer program instructions may be provided to general-purpose computer circuitry, special-purpose computer circuitry, and / or processor circuitry of other programmable data processing circuitry, such that the instructions, executing via a processor of a computer and / or other programmable data processing apparatus, transform and control transistors, values ​​stored in memory locations, and other hardware components within such circuitry to implement the functions / acts specified in the block diagrams and / or one or more flowchart blocks, thereby creating a machine to create the means (functionality) and / or structure for implementing the functions / acts specified in the block diagrams and / or flowchart blocks.

[0271] These computer program instructions may also be stored on a tangible computer-readable medium that may instruct a computer or other programmable data processing apparatus to function in a particular manner to produce an article of manufacture containing instructions that implement the functions / acts specified in the block diagrams and / or one or more flowchart blocks. Thus, embodiments of the inventive concept may be embodied in hardware and / or in software (including firmware, resident software, microcode, etc.) running on a processor, such as a digital signal processor, that may collectively be referred to as "circuitry," "modules," or variations thereof.

[0272] It should also be noted that in some alternative implementations, the functions / acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in reverse order depending on the functionality / acts involved. Moreover, the functionality of a given block of the flowcharts and / or block diagrams may be separated into multiple blocks, and / or the functionality of two or more blocks of the flowcharts and / or block diagrams may be at least partially integrated. Finally, other blocks may be added / inserted between the illustrated blocks, and / or blocks / acts may be omitted without departing from the scope of the inventive concept. Moreover, while some of the figures include arrows on communication paths to indicate a primary direction of communication, it should be understood that communication may occur in the opposite direction of the depicted arrows.

[0273] Numerous variations and modifications may be made to the 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 limiting, 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. Thereby, 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 is not limited or constrained by the detailed description set forth above.

[0274] Abbreviation 3GPP 3rd Generation Partnership Project 5G 5th 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 Future Factory Application Enabler FF Future Factory FFAPP Future Factory Application 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) implementing an Edge Enabler Server (EES) in an Edge Data Network (EDN) (402), comprising: - receiving (S901) a registration request message from a second network function (422) implementing an Edge Application Server (EAS) in said EDN (402), the registration request message comprising information pointing to a first list of relevant EAS information; The method (900) includes:

2. 2. The method (900) of claim 1, wherein 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), each first entry pointing to an EAS profile of the respective third network function (423), the EAS profile of the respective third network function (423) including an EAS ID of the respective third network function (423) and a relationship between the second network function (422) and the respective third network function (423).

3. 3. The method of claim 2, wherein the first entry for the third network function further comprises information pointing to a second list of associated EAS information, the second list of associated EAS information further comprising at least one second entry for at least one fourth network function that implements EAS in the EDN, each second entry pointing to an EAS profile for the respective fourth network function, the EAS profile for the respective fourth network function including an EAS ID for the respective fourth network function and a relationship between the third network function and the respective fourth network function.

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

5. each of said at least one first entry of said first list of associated EAS information further points to endpoint information of said respective third network function (423); or each of the at least one second entry in the second list of associated EAS information further points to endpoint information of the respective fourth network function (424); The method (900) of any one of claims 2 to 4.

6. 6. The method (900) of claim 1, wherein the information pointing to the first list of associated EAS information is included in an 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 an EAS endpoint of the second network function (422).

7. - storing (S902) said information pointing to said first list of relevant EAS information; - sending a registration response message to said second network function (422) that implements EAS (S903); The method (900) of any one of claims 1 to 6, further comprising:

8. A method (1000) performed by a second network function (422) implementing an Edge Application Server (EAS) in an Edge Data Network (EDN) (402), comprising: - sending (S1003) a registration request message comprising information pointing to a first list of relevant EAS information to a first network function (421) implementing an Edge Enabler Server (EES) in said EDN (402); A method (1000) comprising:

9. 9. The method (1000) of claim 8, wherein 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), each first entry pointing to an EAS profile of the respective third network function (423), the EAS profile of the respective third network function (423) including an EAS ID of the respective third network function (423) and a relationship between the second network function (422) and the respective third network function (423).

10. 10. The method of claim 9, wherein the first entry for the third network function further comprises information pointing to a second list of associated EAS information, the second list of associated EAS information further comprising at least one second entry for at least one fourth network function that implements EAS in the EDN, each second entry pointing to an EAS profile for the respective fourth network function, the EAS profile for the respective fourth network function including an EAS ID for the respective fourth network function and a relationship between the third network function and the respective fourth network function.

11. The relationship indicates that the third network function (423) is a parent, child, or sibling of the second network function (422); or the relationship indicates that the fourth network function (424) is a parent, a child, or a sibling of the third network function (423); 11. The method (1000) of claim 9 or 10.

12. each of said at least one first entry of said first list of associated EAS information further points to endpoint information of said respective third network function (423); or each of the at least one second entry in the second list of associated EAS information further points to endpoint information of the respective fourth network function (424); The method (1000) of any one of claims 9 to 11.

13. 13. The method (1000) of any one of claims 8 to 12, wherein the information pointing to the first list of associated EAS information is included in an 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 an EAS endpoint of the second network function (422).

14. - receiving a registration response message from said first network function (421) implementing EES (S1004); 14. The method (1000) of any one of claims 8 to 13, further comprising:

15. 15. The method (1000) of any one of claims 9 to 14, wherein at least two of the second network function (422), the third network function (423), and the fourth network function (424) are configured to jointly provide services for vertical applications.

16. 16. The method (1000) of claim 15, wherein the vertical application is any one of Factory of the Future (FF), Vehicle to Everything (V2X), Unmanned Aerial Systems (UAS), and Smart Grid.

17. - receiving (S1001) from the third network function (423) registration information indicating the EAS ID of the third network function (423), the endpoints of the third network function (423), and the relationship between the second network function (422) and the third network function (423); storing said registration information in said first list of related EAS information (S1002); 17. The method (1000) of claim 15 or 16, further comprising:

18. - receiving (S1001) from said third network function (423) registration information pointing to said EAS profile of said third network function (423); storing said registration information in said first list of related EAS information (S1002); 17. The method (1000) of claim 15 or 16, further comprising:

19. the second network function (422) is implemented as a Service Enabler Architecture Layer (SEAL) server for the vertical application, and the third network function (423) is implemented as a Vertical Application Layer (VAL) server; The SEAL server manages the procedures of the VAL server.

19. The method (1000) of any one of claims 15 to 18.

20. the SEAL server includes a SEAL Identity Management (IM) server; the SEAL IM server providing a token validation service to the VAL server for validating tokens assigned by the SEAL IM server; 20. The method (1000) of claim 19.

21. 21. The method (1000) of claim 20, wherein the token is an access token and / or an ID token.

22. 22. The method (1000) of claim 20 or 21, wherein the VAL server is a FF Application Specific (FFAS) server or a FF Application Enabler (FAE) server.

23. 23. The method (1000) of any one of claims 15 to 22, wherein the second network function (422) is implemented as a FF Application Enabler (FAE) server and the third network function (423) is implemented as a FF Application Specific (FFAS) server.

24. A method (1100) performed by a first network function (421) implementing an Edge Enabler Server (EES) in an Edge Data Network (EDN) (402), comprising: - receiving (S1101) a first message from a functional component (411) of a user equipment (UE) (401) for discovering at least one second network function (422) implementing an Edge Application Server (EAS) in said EDN (402); - sending (S1103) a second message to said functional component (411) of said UE (401) containing information pointing to a first list of relevant EAS information; The method (1100) includes:

25. 25. The method (1100) of claim 24, wherein the information pointing to the first list of associated EAS information is included in an EAS profile of the at least one second network function (422).

26. 26. The method (1100) of claim 25, wherein 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 an EAS profile of the respective third network function (423), the EAS profile of the respective third network function (423) including an EAS ID of the respective third network function (423) and a relationship between the second network function (422) and the respective third network function (423).

27. 27. The method of claim 26, wherein the first entry for the third network function further comprises information pointing to a second list of associated EAS information, the second list of associated EAS information further comprising at least one second entry for at least one fourth network function that implements EAS in the EDN, each second entry pointing to an EAS profile for the respective fourth network function, the EAS profile for the respective fourth network function including an EAS ID for the respective fourth network function and a relationship between the third network function and the respective fourth network function.

28. The relationship indicates that the third network function (423) is a parent, child, or sibling of the second network function (422); or the relationship indicates that the fourth network function (424) is a parent, a child, or a sibling of the third network function (423); 28. The method (1100) of claim 26 or 27.

29. each of said at least one first entry of said first list of associated EAS information further points to endpoint information of said respective third network function (423); or each of the at least one second entry in the second list of associated EAS information further points to endpoint information of the respective fourth network function (424); 29. The method (1100) of any one of claims 26 to 28.

30. 30. The method (1100) of any one of claims 25 to 29, wherein the EAS profile of the second network function (422) further includes information indicating the EAS ID and information indicating an EAS endpoint of the second network function (422).

31. the first message is a discovery request message for discovering the EAS server; the second message is a discovery response message in response to the first message; the first list of associated EAS information and the second list of associated EAS information are discovered in an EAS discovery process performed (S1102) by the first network function (421); 31. The method (1100) of any one of claims 24 to 30.

32. the first message is a discovery subscription message for subscribing to discovery of the EAS server; the second message is a discovery notification message in response to the first message; the first list of associated EAS information and the second list of associated EAS information are discovered in an EAS discovery process performed (S1102) by the first network function (421); 31. The method (1100) of any one of claims 24 to 30.

33. the first message further comprises an indicator explicitly pointing to an EAS association; the EAS discovery process is performed based on the indicator; 33. The method (1100) of any one of claims 24 to 32.

34. 34. The method (1100) of any one of claims 24 to 33, wherein the first functional component (411) is implemented as an Edge Enabler Client (EEC), and the first and / or second messages are sent via an Edge-1 reference point.

35. A method (1200) implemented by a first functional component (411) in a user equipment (UE) (401), comprising: - sending (S1202) a first message to a first network function (421) implementing an Edge Enabler Server (EES) in an Edge Data Network (EDN) (402) to discover at least one second network function (422) implementing an Edge Application Server (EAS) in said EDN (402); receiving (S1203) from said first network function (421) a second message including information pointing to a first list of relevant EAS information; The method (1200) includes:

36. 36. The method (1200) of claim 35, wherein the information pointing to the first list of associated EAS information is included in an EAS profile of the at least one second network function (422).

37. 37. The method (1200) of claim 36, wherein 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), each first entry pointing to an EAS profile of the respective third network function (423), the EAS profile of the respective third network function (423) including an EAS ID of the respective third network function (423) and a relationship between the second network function (422) and the respective third network function (423).

38. 38. The method (1200) of claim 37, wherein the first entry for the third network function (423) further comprises information pointing to a second list of associated EAS information, the second list of associated EAS information further comprising at least one second entry for at least one fourth network function (424) that implements EAS in the EDN (402), each second entry pointing to an EAS profile for the respective fourth network function (424), the EAS profile for the respective fourth network function (424) including an EAS ID for the respective fourth network function (424) and a relationship between the third network function (423) and the respective fourth network function (424).

39. The relationship indicates that the third network function (423) is a parent, child, or sibling of the second network function (422); or the relationship indicates that the fourth network function (424) is a parent, a child, or a sibling of the third network function (423); 39. The method (1200) of claim 37 or 38.

40. each of said at least one first entry of said first list of associated EAS information further points to endpoint information of said respective third network function (423); or each of the at least one second entry in the second list of associated EAS information further points to endpoint information of the respective fourth network function (424); 40. The method (1200) of any one of claims 37 to 39.

41. 41. The method (1200) of any one of claims 36 to 40, wherein the EAS profile of the second network function (422) further includes information indicating the EAS ID and information indicating an EAS endpoint of the second network function (422).

42. the first message is a discovery request message for discovering the EAS server; the second message is a discovery response message in response to the first message; the first list of associated EAS information and the second list of associated EAS information are discovered in an EAS discovery process performed (S1102) by the first network function (421); 42. The method (1200) of any one of claims 35 to 41.

43. the first message is a discovery subscription message for subscribing to discovery of the EAS server; the second message is a discovery notification message in response to the first message; the first list of associated EAS information and the second list of associated EAS information are discovered in an EAS discovery process performed (S1102) by the first network function (421); 42. The method (1200) of any one of claims 35 to 41.

44. 44. The method (1200) of any one of claims 35 to 43, wherein the first message further comprises an indicator that explicitly points to an EAS association.

45. 45. The method (1200) of any one of claims 35 to 44, wherein the first functional component (411) is implemented as an Edge Enabler Client (EEC), and the first message and / or the second message is sent via an Edge-1 reference point.

46. 36. The method (1200) of claim 35, wherein the information pointing to the first list of associated EAS information is included in a set of EAS profiles for a first set of network functions that implement EAS in the EDN.

47. - determining the first set of network capabilities that implement EAS in the EDN from the set of EAS profiles; - determining a second set of network functions that implement EAS in the EDN from the first list of relevant EAS information; Furthermore, wherein at least two network functions from the first set and the second set of network functions are associated.

47. The method (1200) of claim 46.

48. 48. The method (1200) of claim 47, wherein at least two network functions from the first set and second set of network functions are associated by one of the at least two network functions being registered on the other of the at least two network functions.

49. - receiving (S1201) from a second functional component (412) in the UE (401) a first delegation request for EAS discovery and selection for the second functional component (412); - receiving (S1201) from a third functional component (413) in the UE (401) a second delegation request for EAS discovery and selection for the third functional component (413); 49. The method (1200) of claim 48, further comprising:

50. - selecting (S1204) network functions for the second functional component (412) and the third functional component (413) by the first functional component (411), such that the selected at least one network function (422) for the second functional component (412) and the selected at least one network function (422) for the third functional component (413) are associated with each other; - informing the second functional component and the third functional component, respectively, of the selected network functions for the second functional component and the third functional component; 50. The method (1200) of claim 49, further comprising:

51. the second functional component (412) is implemented as an application enabler client for vertical applications; the third functional component (413) is implemented as an application-specific client for a vertical application; 51. The method (1200) of claim 49 or 50.

52. A method (1300) implemented by a second functional component (412) in a user equipment (UE), comprising: - sending (S1302) a first message to a first functional component (411) in the UE (401) for discovering at least one second network function implementing an Edge Application Server (EAS) in an EDN; receiving (S1303) a second message from the first functional component (411) in the UE (401) that includes information pointing to a list of relevant EAS information; The method (1300) includes:

53. 53. The method (1300) of claim 52, wherein the information pointing to the list of related EAS information is included in a set of EAS profiles of a first set of network functions that implement EAS in the EDN.

54. - determining (S1304) from the set of EAS profiles the first set of network functions that implement EAS in the EDN; - determining a second set of network functions that implement EAS in the EDN from said list of relevant EAS information (S1304); Furthermore, wherein at least two network functions from said first and second sets of network functions are associated; 54. The method (1300) of claim 53.

55. 55. The method (1300) of claim 54, wherein at least two network functions from the first set and second set of network functions are associated by one of the at least two network functions being registered on the other of the at least two network functions.

56. - coordinating with a third functional component (413) in the UE (401) to select a network function for the second functional component (412) and the third functional component (413), wherein the selected network function for the second functional component (412) and the selected network function for the third functional component (413) are associated with each other.

56. The method (1300) of any one of claims 52 to 55, further comprising:

57. receiving a delegation request for EAS discovery and selection from a third functional component (413) in the UE, the delegation request selecting an EAS for the third functional component (413) (S1301); 56. The method (1300) of any one of claims 52 to 55, further comprising:

58. - selecting, by the second functional component (412), a network function for the second functional component (412) and the third functional component (413), such that the selected network function for the second functional component (412) and the selected network function for the third functional component (413) are associated; - informing said third functional component (413) of said selected network function for said third functional component (413); 58. The method (1300) of claim 57, further comprising:

59. 59. A method (1300) according to claim 56 or 58, wherein the selected network function for the second functional component (412) and the selected network function for the third functional component (413) are associated by registering the selected network function for the third functional component (413) on the selected network function for the second functional component (412).

60. the second functional component (412) is implemented as a Service Enabler Architecture Layer (SEAL) client for vertical applications; the third component (413) is implemented as a vertical application layer (VAL) client for the vertical application; 60. The method (1300) of claim 59.

61. 61. The method (1300) of claim 60, wherein the VAL client is an application enabler client for the vertical application or an application specific client for the vertical application.

62. the second functional component (412) is implemented as an application enabler client for vertical applications; the third functional component (413) is implemented as an application-specific client for the vertical application; 60. The method (1300) of claim 59.

63. 63. The method (1300) of any one of claims 56 to 62, wherein the vertical application is any one of Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

64. 64. A method (1300) according to any one of claims 52 to 63, wherein the first functional component (411) is implemented as an Edge Enabler Client (EEC), the first message is an EAS discovery request message or an EAS discovery subscription message sent via an Edge-5 reference point, and the second message is an EAS discovery response message or an EAS discovery notification message sent via the Edge-5 reference point.

65. a first functional component (411) implementing an Edge Enabler Client (EEC); a third functional component (413) that implements an application enabler client for the vertical application; a fourth functional component (414) that implements an application-specific client of said vertical application; A plurality of functional components (411, 412, 413, 414) including Equipped with wherein the third functional component (413) provides at least one service to one or more fourth functional components (414); and wherein the first functional component (411) and the third functional component (413) communicate via an Edge-5 reference point to enable the at least one service. User Equipment (UE) (401).

66. the first functional component (411) and the fourth functional component (414) communicate via an Edge-5 reference point; or the third functional component (413) and the fourth functional component (414) communicate via an AE-C reference point to enable at least one service; 66. The UE (401) of claim 65.

67. A second functional component (412) that implements a Service Enabler Architecture Layer (SEAL) client for said vertical application. Furthermore, wherein the first functional component (411) and the second functional component (412) communicate via an Edge-5 reference point; wherein said third functional component (413) and said second functional component (412) communicate via a SEAL-C reference point to enable at least one service; or wherein the fourth functional component (414) and the second functional component (412) communicate via a SEAL-C reference point; 67. The UE (401) of claim 65 or 66.

68. 68. The UE (401) of any one of claims 65 to 67, wherein the vertical application is any one of Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

69. the first functional component (411) communicates with a first network function (421) implementing an Edge Enabler Server (EES) via an Edge-1 reference point; the third functional component (413) communicates with a third network function (423) implementing an application enabler server for the vertical application via an AE-1 reference point to enable at least one service; said fourth functional component (414) communicating via a VA-1 reference point with a fourth network function (424) implementing an application-specific server of said vertical application to enable at least one service; or the second functional component (412) communicates with a second network function (422) implementing a Service Enabler Architecture Layer (SEAL) server for the vertical application via a SEAL-UU reference point to enable at least one service; 69. The UE (401) of any one of claims 65 to 68.

70. A communication system (400) for vertical applications in edge deployments, comprising: a first network function (421) implementing an Edge Enabler Server (EES); a third network function (423) implementing an application enabler server for the vertical applications; a fourth network function (424) implementing an application-specific server of said vertical application; a plurality of network functions (421, 422, 423, 424) in an edge data network (EDN) (402), including Equipped with wherein the third network function (423) provides at least one service to one or more fourth network functions (424); and wherein the first network function (421) and the third network function (423) communicate via an Edge-3 reference point to enable the at least one service. A communication system (400).

71. said first network function (421) and said fourth network function (424) communicate via an Edge-3 reference point; or the third network function (423) and the fourth network function (424) communicate via an AE-S reference point to enable at least one service; 71. The communication system (400) of claim 70.

72. a second network function (422) implementing a Service Enabler Architecture Layer (SEAL) server for said vertical application; Furthermore, wherein the first network function (421) and the second network function (422) communicate via an Edge-3 reference point; wherein said third network function (423) and said second network function (422) communicate via a SEAL-S reference point to enable at least one service; or wherein the third network function (423) and the second network function (422) communicate via a SEAL-S reference point; 72. A communication system (400) according to claim 70 or 71.

73. 73. The communication system (400) of any one of claims 70 to 72, wherein the vertical application is any one of a Factory of the Future (FF), V2X, Unmanned Aerial Systems (UAS), and Smart Grid.

74. said first network function (421) communicating with a first functional component (411) implementing an Edge Enabler Client (EEC) via an Edge-1 reference point; the third network function (423) communicates with a third functional component (413) implementing an application enabler client of the vertical application via an AE-1 reference point to enable at least one service; said fourth network function (424) communicating via a VA-1 reference point with a fourth functional component (414) implementing an application-specific client of said vertical application to enable at least one service; or the second network function (422) communicating with a second functional component (412) implementing a Service Enabler Architecture Layer (SEAL) client of the vertical application via a SEAL-UU reference point to enable at least one service; A communication system (400) according to any one of claims 70 to 73.

75. A first network function (421, 1400) implementing an Edge Enabler Server (EES) in an Edge Data Network (EDN) (402), comprising: At least one processor (1401); a non-transitory computer-readable medium (1402) coupled to the at least one processor (1401), the non-transitory computer-readable medium (1402) including instructions executable by the at least one processor (1401), whereby the at least one processor (1401) is configured to perform a method (900, 1100) according to any one of claims 1 to 7 and 24 to 34; a first network function (421, 1400) comprising:

76. a second network function (422, 1500) implementing an edge application server (EAS) in an edge data network (EDN) (402), At least one processor (1501); a non-transitory computer-readable medium (1502) coupled to the at least one processor (1501), the non-transitory computer-readable medium (1502) including instructions executable by the at least one processor (1501), whereby the at least one processor (1501) is configured to perform the method (1000) of any one of claims 8 to 23; a second network function (422, 1500) comprising:

77. A user equipment (UE) (401, 1600), At least one processor (1601); a non-transitory computer-readable medium (1602) coupled to the at least one processor (1601), the non-transitory computer-readable medium (1602) including instructions executable by the at least one processor (1601), whereby the at least one processor (1601) is configured to perform a method (1200, 1300) according to any one of claims 35 to 64; A user equipment (UE) (401, 1600) comprising:

78. A computer-readable medium (1702) comprising computer-readable code that, when run on an apparatus (1700), causes the apparatus (1700) to perform a method (900, 1000, 1100, 1200, 1300) according to any one of claims 1 to 64.

79. A computer program product (1704) comprising computer-readable code that, when run on an apparatus (1700), causes the apparatus (1700) to perform a method (900, 1000, 1100, 1200, 1300) according to any one of claims 1 to 64.

Images