Vertical Applications in Edge Computing

Abstract

The embodiments herein relate to vertical applications in edge computing. The embodiments propose a method (900) implemented by a first network function (421) implementing an edge enabler server (EES) in an edge data network (EDN) (402). The method may include at least a step of receiving a registration request message from a second network function (422, 423) implementing an edge application server (EAS) in the EDN (402), the registration request message including information pointing to a first list of related EAS information. According to the embodiments herein, based on the related EAS information, the UE (401) may perform joint EAS discovery and selection for vertical applications in edge deployment, so that both the application enabler client (414) and the application specific server (424) in the UE (401) may communicate with the same application enabler server (423).

Description

Technical Field

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

Background Art

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

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

[0004] To enable smart factories in manufacturing, the 3GPP SA6 working group is also researching application enabling services aiming at the general applicability of future factories (FF) based on the service requirements of 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] Future Factory (FF) For the FF application (app), one proposed architecture in the research (section 7.1 of TR 23.745) is shown in Figure 2, which is a schematic block diagram showing the application layer architecture 200 for FF.

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

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

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

[0009] The FAE server 222 interacts with another FAE server 222 via the 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 5GS) via the N33 reference point as specified in 3GPP TS 23.501 [7].

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

[0012] The following SEAL services for the FF application 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 - Identification information management as specified in 3GPP TS 23.434 - Key management as specified in 3GPP TS 23.434 - Network resource management as specified in 3GPP TS 23.434

[0013] Edge application 3GPP TS 23.558 specifies the application layer architecture, procedures, and information flows necessary to enable edge applications over a 3GPP network. 3GPP TS 23.558 includes architecture requirements for enabling edge applications, an application layer architecture that meets the architecture requirements, and procedures for enabling the deployment of edge applications.

[0014] For edge computing support, the objectives include the evolution of application layer requirements and architecture for hosting edge applications on an Edge Data Network (EDN), including the exposure of northbound APIs for edge applications and the integration of an edge enabling layer with the 3GPP network.

[0015] Figure 3 is a schematic block diagram showing 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 configurations 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 can interact with the 3GPP core network 303.

Summary of the Invention

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

[0017] In view of the above, embodiments herein propose, among other things, an integrated view for facilitating the use of different applications and enablers in a vertical domain, particularly when there is some relationship between those servers, for a UE to select an application server deployed at the edge.

[0018] In an embodiment, a first method implemented by a first network function that implements an edge enabler server (EES) in an edge data network (EDN) is proposed. The method may comprise receiving a registration request message comprising information indicating a list of related EAS information from a second network function that implements an edge application server (EAS) in the EDN.

[0019] In another embodiment, a second method implemented by a second network function that implements an edge application server (EAS) in an edge data network (EDN) is proposed. The method may comprise sending a registration request message comprising information indicating a first list of related EAS information to a first network function that implements an edge enabler server (EES) in the EDN.

[0020] In yet another embodiment, a third method implemented by a first network function that implements an edge enabler server (EES) in an edge data network (EDN) is proposed. The method may comprise receiving, from a functional component of a user equipment (UE), a first message for discovering at least one second network function that implements an edge application server (EAS) in the EDN. The method may further comprise sending a second message comprising information indicating a first list of related EAS information to the functional component of the UE.

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

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

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

[0024] In yet another embodiment, a communication system for vertical applications in edge deployment is proposed, which comprises 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 vertical applications, and a fourth network function implementing an application-specific server for vertical applications. 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 at least one service.

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

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

[0027] In yet another embodiment, a user equipment (UE) is proposed that includes 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 implement the fourth and fifth methods described above.

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

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

[0030] According to embodiments herein, based on related EAS information, a UE may perform joint EAS discovery and selection for vertical applications in edge deployment, whereby both the application enablement client and the application-specific server in the UE may communicate with the same application enablement server.

[0031] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure and to enable one of ordinary skill in the art to make and use the embodiments disclosed herein. In the drawings, like reference numerals refer to the same or functionally similar elements.

Brief Description of the Drawings

[0032]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

[0033] The embodiments herein will be described in detail below with reference to the accompanying drawings in which the embodiments are illustrated. However, these embodiments herein may be embodied in many different forms and should not be construed as limited to the embodiments described herein. The elements of the drawings are not necessarily to scale with each other.

[0034] References to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the 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] As used herein, the term "A, B, or C" 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 major problem #9 described in TR 23.745, section 5.9, and the existing solutions #5 and #6 place the FF enablers (client and server) as EAS in the context of an edge application architecture. However, it is unclear how the FF-specific applications (client and server) can utilize the edge application services.

[0038] According to section 5.1 of TS 22.104, a local approach for network-side communication services is preferred to reduce latency (between UEs via Uu and between a UE and a network server) or to keep confidential data in a non-public network on the factory premises. In that case, the problem still remains as to how to support FFAPP communication via a network-side edge deployment.

[0039] In FFAPP TR 23.745, according to solution #4 (for device onboarding support), the FAE client 212 registers with the FAE server 222 via the FAE-1 reference point. The FF application-specific client 213 registers with the FAE client 212 via the FAE-C reference point. Also, 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 be registered with the FAE server 222, and the FAE client 212 also needs to be registered with the FAE server 222. However, from the perspective of the UE, under edge deployment, the EAS discovery service provided by the edge application is used. If the selection of the FFAS server 223 and the FAE server 222 is handled separately, the selected FAE server 222 may not hold the registered FFAS server 223, whereby some functions may not be able to operate 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 via 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 via the FAE server 222.

[0041] Generally, in the case of edge deployment, when the application enablement client in the UE and the application-specific server need to communicate with the same application enablement server, the selection of the application enablement server and the application-specific server lacks some cooperation.

[0042] In view of the above problems, the embodiments in this specification provide additional information, namely related EAS information, in the EAS registration procedure to explain the relationship between servers. The additional information may help the UE select the appropriate EAS using an integrated view.

[0043] Edge Computing for FFAPP This solution in the present disclosure addresses the above important problem #9, namely, communication services in edge deployment. "Table number", "Dependent section number", etc. are in 3GPP TR 23.745 V1.2.0.

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

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

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

[0046] In EDN402, there can be several EESs provided by the same or different Edge Computing Service Providers (ECSPs). The FFAS server 424 and the FAE server 423 can discover and register with an appropriate EES421. When CAPIF is used, this can be done by leveraging the AEF serving area and / or AEF location as described in 3GPP TS 23.222

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

[0047] In sol#4, the FFAS server 424 needs to register with the FAE server 423, and the FAE client 413 needs to register with the FAE server 423 during the onboarding process. Similarly, the FFAS server 424 can discover and register with an appropriate FAE server 423. Ideally, the FFAS server 424, the FAE server 423, and the EES421 are all placed in the same area to achieve low-latency communication between servers in the edge deployment. However, from the perspective of the UE, under edge deployment, the EAS discovery service provided by the edge enablers 411 / 421 is used. If the selection of the FFAS server 424 and the FAE server 423 is handled separately, the selected FFAS server 424 may not be onboarded onto the selected FAE server 423, whereby some functions may not be able to operate. That is, 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] In order to enable the selection of the FFAS server 424 and the onboarding FAE server 423 of the FFAS server 424 in edge deployment, the FFAS server 424 and the FAE server 423 need to exchange the application server information of the FFAS server 424 and the FAE server 423 during onboarding. After both parties store the relevant application server information, the FAE server 423 and the FFAS server 424 register with the EES 421 via the Edge-3 reference point. Also, as a result, the EEC 411 can discover a list of candidate FAE servers 423 including its associated FFAS server 424, and a list of candidate FFAS servers 424 including its associated FAE server 423 based on the interaction with the FAE client 413 via the Edge-5 reference point.

[0049] Regarding SEAL, there is no such association between the VAL servers 423, 424 and the SEAL server 422 by the sparse administrative procedures specified in 3GPP. For the SEAL identification information management (IM) function, before any token is granted to the SEAL IM client 412 from the SEAL IM server 422, the SEAL IM client 412 needs to register with the SEAL IM server 422 as described in 3GPP TS 33.434 [TS33434]. For token validity verification purposes outside the scope of 3GPP (and further, IETF RFC 6749 [rfc6749]), if there is an interaction between the VAL servers 423, 424 and the SEAL IM server 422, the EAS discovery needs to take into account the association between the VAL server (e.g., the FAE server 423) and the SEAL IM server 424.

[0050] In the UE 401, there are several ways to achieve the selection of the associated EAS servers 422, 423, 424. The following list describes two alternative forms for information purposes since both FAE-C and Edge-5 are not detailed within the Rel-17 timeline.

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

[0052] b. The FFAS client 414 can also delegate the discovery of the FFAE server 424 to the FAE client 413 via the FAE-C reference point. In that case, the FAE client 413 triggers the discovery (possibly using requests to discover the FAE server 423 as well), and further selects the FFAE server 424 that matches the selected FAE server 423 from the discovered results.

[0053] According to 3GPP TS 23.558

[10] , when the EEC 411 provides the discovery results to the application clients 412, 413, 414, it can limit the number of discovered application servers 422, 423, 424. If such a function in the EEC 411 is used (e.g., delegated by the application clients 412, 413, 414), the EEC 411 does not limit the number of discovered application servers 422, 423, 424 based on only a single application with related EAS information.

[0054] Table 1 shows the impact (in bold and italic) in the EAS profile including the 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. TIFF0007690035000001.tif77170

[0055] Other edge-3 public services are not re-published by the FAE server 423 or the SEAL server 422 to the FFAS server 424. For example, note that the FFAS server 424 directly consumes the location or QoS API provided by the EES 421.

[0056] Solution Evaluation This solution addresses the important question #9 of "how to support FFAPP communication via edge deployment" and provides deployment options for FF applications in the edge application architecture.

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

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

[0059] The benefit of this is to reduce the number of discovered EASs 422, 423, 424 in the discovery response / notification so that the UE 401 can process less information in the selection of the EASs 422, 423, 424 using the integrated view.

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

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

[0062] The Edge-3 reference point in FIG. 4 enables interaction between EES421 and EAS422, 423, 424. The Edge-3 reference point supports a) registration of EAS422, 423, 424 with availability information (e.g., time constraints, location constraints), b) deregistration of EAS422, 423, 424 from EES421, c) discovery of target EAS information for supporting application context transfer, d) providing access to network capability information (e.g., location information, service quality (QoS) related information), and e) requesting setup of data sessions between application clients 412, 413, 414 and EAS422, 423, 424 using a specific QoS.

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

[0064] FIG. 5 is a schematic block diagram showing a more general edge deployment 500 for vertical applications. Specifically, FIG. 5 shows edge deployment options for supporting applications (application-specific servers and their enabling servers) in vertical domains (e.g., future factories, V2X, unmanned aerial systems). In FIG. 5, different application clients and servers are split across different application layers.

[0065] In FIG. 5, the reference point names between two entities are strings concatenated using a dash delimiter between two entity names in uppercase letters followed by a single character c or s (representing the corresponding client or server).

[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. Server A522 has an association with server B523 as a child EAS.

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

[0068] The embodiments propose a user equipment (UE) comprising a plurality of functional components. For example, the plurality of functional components may include a first functional component implementing an edge enabling client (EEC) and a second functional component implementing an application enabling client of a vertical application. In the embodiments, 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 a vertical application. The first functional component and the third functional component may communicate via an Edge-5 reference point. The second functional component and the third functional component may communicate via an AE-C reference point.

[0070] In an embodiment, the UE may further include a fourth functional component that implements a Service Enablement Architecture Layer (SEAL) client for a vertical application. 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 a future factory (FF), V2X, unmanned aerial system (UAS), and smart grid.

[0072] In an embodiment, the first functional component may communicate with a first network function implementing an Edge Enablement Server (EES) via an Edge-1 reference point. The second functional component may communicate with a second network function implementing an application enablement server for a vertical application via an AE-1 reference point. The third functional component may communicate with a third network function implementing an application-specific server for a vertical application via a VA-1 reference point. For example, the VA-1 reference point may be a reference point between an application-specific client and an application-specific server. The fourth functional component may communicate with a fourth network function implementing a Service Enablement Architecture Layer (SEAL) server for a vertical application via a SEAL-UU reference point.

[0073] In an embodiment, a communication system for a vertical application in edge deployment, which includes a plurality of network functions in an edge data network (EDN), is further proposed. The plurality of network functions may include a first network function that implements an edge enable server (EES) and a second network function that implements an application enable server for a 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 that implements an application-specific server for a 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 that implements a service enable architecture layer (SEAL) server for a vertical application. 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 a future factory (FF), V2X, an unmanned aerial system (UAS), and a smart grid.

[0077] In an embodiment, the first network function can communicate with a first functional component implementing an Edge-Enabled Client (EEC) via an Edge-1 reference point. The second network function can communicate with a second functional component implementing an application-enabled client of a vertical application via an AE-1 reference point. The third network function can communicate with a third functional component implementing an application-specific client of a vertical application via a VA-1 reference point. For example, the VA-1 reference point can be a reference point between the application-specific client and the application-specific server. The fourth network function can communicate with a fourth functional component implementing a Service-Enabled Architecture Layer (SEAL) client of a vertical application via a SEAL-UU reference point.

[0078] In some embodiments, each of EAS422, 423, 424, 522, 523, 524, 525 registers with EES421, 521 using its own profile and optional associated EAS information (see the messages in FIG. 6 below), such that after EAS discovery (see the messages in FIGS. 7 and 8 below), UE401, 501 can have joint consideration when selecting edge application servers 422, 423, 424, 522, 523, 524, 525 that have a management relationship with each other. For example, there can be cooperation between client B513 and client D514 via, for example, the Dc-Bc reference point, such that the selected servers B523 and D524, which are used for client B513 and client D514 respectively, are associated.

[0079] In some embodiments, only one of the EASs 422, 522 in the root or bottom layer needs to be registered to the EESs 421, 521 in place of its children 423, 424, 523, 524 and its siblings (see the messages in FIG. 6 below). In the onboard EAS profile, it may further include a list of the onboard EAS profiles. Briefly speaking, this is an embedded EAS profile in another EAS profile that may include several layers.

[0080] Table 2 shows (in bold and italic) the impact on the EAS profile that includes a list of the onboard EAS profiles. TIFF0007690035000002.tif83170

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

[0082] The embodiments are described below mainly by referring to the architecture of FIG. 4, and 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 the messages in the vertical EAS registration in the edge deployment.

[0084] In the embodiments, the following preconditions are satisfied before implementing the vertical EAS registration.

[0085] (1). The EAS identification information is set in the EAS 422. (2). The address (e.g., URI) of EES421 is set in EAS422. (3). Both EAS422 and EES421 have the credentials necessary to enable communication.

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

[0087] Step 1. EAS422 determines that registration with EES421 is required (e.g., EAS422 is instantiated and started up).

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

[0089] In an embodiment, the request may also include related EAS information to register the association between EAS422, 423, 424. For example, information about the EAS profile in Table 1 or Table 2 above may be included in the request. As a result, in subsequent EAS discovery procedures, UE401 may discover the association between EAS422, 423, 424 that can be used to select EAS422, 423, 424 in joint consideration.

[0090] Step 3. EES421 performs a permission check to verify whether EAS422 has permission for registration on EES421.

[0091] Step 4. If the permission check is successful, EES421 stores the EAS profile for later use (e.g., to serve the edge application server discovery request received from EEC411), and returns a reply to EAS422 using the 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 update request before the expiration time. If the registration update request is not received before the expiration time, EES421 treats EAS422 as if it were implicitly deregistered.

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

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

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

[0095] (1). EEC411 has received information related to EES421 (e.g., URI, IP address). (2). EEC411 has received an appropriate security credential that permits EEC411 to communicate with EES421. (3). An ECSP policy for EAS discovery is set in EES421.

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

[0097] Step 1. EEC411 sends an EAS discovery request to EES421. The EAS discovery request includes a requester identifier, e.g., an EEC ID, along with a security proof, and may include an EAS discovery filter for retrieving information regarding a specific EAS or category of EAS, e.g., a game application.

[0098] Step 2. Upon receiving the request from EEC411, EES421 checks whether EEC411 is permitted to discover the requested EAS. The permission check can be applied to individual EAS, categories of EAS, or to the EDN, in other words, to all EAS. EES421 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 EEC411, EES421 identifies EAS422, 423, 424 based on the provided EAS discovery filter and the UE location. When no EAS discovery filter is provided, - If available, EES421 identifies EAS422, 423, 424 based on the UE-specific service information in EES421 and the UE location, - EES421 identifies EAS422, 423, 424 by applying the ECSP policy (e.g., based on the UE location only).

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

[0100] If UE401 is located outside the geographical area or topology service area of EAS422, 423, 424, EES421 does not include these 422, 423, 424 in the discovery response.

[0101] If the processing of the request is successful in step 3, EES421 sends an EAS discovery response containing information about the discovered EASs422, 423, 424 to EEC411. For the discovered EASs422, 423, 424, this includes endpoint information. Depending on the EAS discovery filter received during the EAS discovery request, the response may include additional information about the matching capabilities, such as service permission levels, application client locations that the EAS can support, key performance indicators, etc.

[0102] In an embodiment, the response may also include related 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, UE401 may discover the associations between EASs422, 423, 424 that can be used to select EASs422, 423, 424 in joint consideration.

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

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

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

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

[0107] In an embodiment, the signaling chart in FIG. 8 may include the following messages or steps. Step 1. The event occurs at the EES421 that satisfies the trigger condition for providing the EAS discovery information of the subscribed EEC411. If the UE's location information is not available, the EES421 may obtain the UE location by using the capabilities of the 3GPP core network 403 as specified in Section 8.9.2. If an EAS discovery filter is provided by the EEC411 during subscription creation, the EES421 identifies the EAS422, 423, 424 based on the provided EAS discovery filter and the UE location. If no EAS discovery filter is provided, - If available, the EES421 identifies the EAS422, 423, 424 based on the UE-specific service information in the EES421 and the UE location, - The EES421 identifies the EAS422, 423, 424 by applying an ECSP policy (e.g., based only on the UE location).

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

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

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

[0111] Figure 9 is a schematic flowchart showing an exemplary EAS registration method 900 implemented by a first network function according to an embodiment herein. In an embodiment, the flowchart in Figure 9 may be implemented in the above-described EES (such as EES421).

[0112] Method 900 may begin at step S901, where the first network function may receive a registration request message comprising information indicating a first list of related EAS information from a second network function (such as EAS422) that implements EAS in the EDN.

[0113] In an embodiment, the information indicating the first list of related EAS information may be included in the EAS profile of the second network function. The EAS profile of the second network function may further include information indicating an EAS ID and information indicating 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 (such as EAS423) that implements EAS in the EDN respectively. Each first entry may indicate the EAS profile of the respective third network function. The EAS profile of each respective third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

[0115] For example, EAS422 may send an EAS profile of EAS422 including a first list of related EAS information (which may indicate the association of EAS422 with other EAS423 and / or 424) to EES421.

[0116] In another example, EAS423 may send an EAS profile of EAS423 that includes a first list of associated EAS information (which may indicate the association of EAS423 with other EAS424) to EES421.

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

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

[0119] In an embodiment, the first entry for the third network function further comprises information indicating 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 (such as EAS424) that implements EAS in each respective EDN. Each second entry may indicate an EAS profile of each respective fourth network function. The EAS profile of each respective fourth network function may include the EAS ID of each respective fourth network function and the relationship between the third network function and each respective fourth network function.

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

[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 can be seen from FIG. 4 or FIG. 5.

[0122] In an embodiment, each of at least one second entry of the second list of related EAS information may further indicate the endpoint information of the 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 a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the related EAS information.

[0124] In an embodiment, the vertical application is any one of a future factory (FF), V2X, unmanned aerial system (UAS), and smart grid.

[0125] In an embodiment, the second network function is implemented as a service enable architecture layer (SEAL) server 422 for a vertical application, 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 a part of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the border setting).

[0126] In an embodiment, the SEAL server 422 may include a SEAL identification information management (IM) server. The SEAL IM server may provide a token validity confirmation service for the VAL servers 423, 424 to confirm the validity of the tokens assigned by the SEAL IM server.

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

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

[0129] In an embodiment, the second network function is implemented as the FF application enabler (FAE) server 423, and the third network function is implemented as the FF application specific (FFAS) server 424.

[0130] Next, method 900 may proceed to step S902, where the first network function may store information indicating a first list of associated EAS information.

[0131] In an embodiment, the first network function may store information indicating other lists of associated EAS information. For example, the network function may store information indicating 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 a list of associated EAS information received from the EAS.

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

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

[0135] Figure 10 is a schematic flowchart showing an exemplary EAS registration method 1000 implemented by a second network function (such as EAS422, 423, 424, etc.) according to an embodiment in this specification. In the embodiment, the flowchart in Figure 10 can be implemented in the above-mentioned EAS422, 423, 424.

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

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

[0138] In the embodiment, the registration request can include information indicating the EAS profile of the third network function, and the EAS profile of the third network function can further include information about the associated fourth network function.

[0139] Next, method 1000 can proceed to step S1002. In step S1002, the second network function can store the above information received from the third network function as the registration information of the third network function. For example, the second network function can store the registration information in a list of relevant EAS information within the EAS profile of the second network function. When doing this, an association can be established between the second network function and the third network function (and further network functions).

[0140] Next, method 1000 may proceed to step S1003, where the second network function may send a registration request message to the first network function that implements EES in the EDN (such as EES421), the registration request message including information indicating a first list of relevant EAS information.

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

[0142] In an embodiment, the first list of relevant EAS information may include at least one first entry for at least one third network function that implements EAS in the EDN respectively. Each first entry may indicate the EAS profile of the respective third network function. The EAS profile of each respective third network function may include the EAS ID of each respective third network function and the relationship between the second network function and each 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 can be seen from FIG. 4 or FIG. 5.

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

[0145] In an embodiment, the first entry for the third network function further includes information indicating a second list of related EAS information. The second list of related EAS information may further include at least one second entry for at least one fourth network function that implements EAS in each EDN. Each second entry may indicate the EAS profile of each respective fourth network function. The EAS profile of each respective fourth network function may include the EAS ID of each respective fourth network function and the relationship between the third network function and each respective fourth network function (such as EAS424).

[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 can be seen from FIG. 4 or FIG. 5.

[0147] In an embodiment, each of at least one second entry of the second list of related EAS information may further indicate the endpoint information of each 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 a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the related EAS information.

[0149] In an embodiment, the vertical application is any one of a future factory (FF), V2X, an unmanned aerial system (UAS), and a smart grid.

[0150] In an embodiment, the second network function (such as EAS422) is implemented as a Service Enablement Architecture Layer (SEAL) server for vertical applications, and the third network function is implemented as a Vertical Application Layer (VAL) server (such as EAS423, 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 a part of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the border setting).

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

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

[0153] In an embodiment, the VAL servers 423, 424 are FF Application Specific (FFAS) servers 424 or FF Application Enable (FAE) servers 423.

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

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

[0156] The above steps are merely examples, and the second network function may perform the actions described with respect to FIGS. 6-8 to manage related EAS information for providing an integrated view for the UE to select an application server deployed at the edge.

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

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

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

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

[0161] In the embodiment, the first message further includes an indicator explicitly indicating an EAS association. For example, the EEC411 may explicitly indicate for EAS association in an EAS discovery request or an EAS discovery subscription request such that only EASs having an EAS association are discovered.

[0162] Next, method 1100 may proceed to step S1102, where the first network function may perform an EAS discovery process to discover the 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 an embodiment, the information indicating the first list of related EAS information may be included in the EAS profile of the second network function. (such as EAS422) The EAS profile of the second network function may further include information indicating the EAS ID and information indicating the EAS endpoint of the second network function.

[0164] In an embodiment, the first list of related EAS information may include at least one first entry for at least one third network function (such as EAS423) that implements the EAS in the EDN respectively. Each first entry may indicate the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of each third network function and the relationship between the second network function and each 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 can be seen from FIG. 4 or FIG. 5.

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

[0167] In an embodiment, the first entry for the third network function further comprises information indicating a second list of related EAS information. The second list of related EAS information may further comprise at least one second entry for at least one fourth network function that implements an EAS (such as EAS424) in the EDN respectively. Each second entry may indicate an EAS profile of each respective fourth network function. The EAS profile of each respective fourth network function may include an EAS ID of each respective fourth network function and a relationship between the third network function and each 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 can be seen from FIG. 4 or FIG. 5.

[0169] In an embodiment, each of at least one second entry of the second list of related EAS information may further indicate endpoint information of each 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 a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the related EAS information.

[0171] In an embodiment, the vertical application is any one of a future factory (FF), V2X, an unmanned aerial system (UAS), and a smart grid.

[0172] In an embodiment, the second network function is implemented as a Service Enablement Architecture Layer (SEAL) server 422 for vertical applications, 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 a part of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the border setting).

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

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

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

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

[0177] Next, the method 1100 may proceed to step S1103, in which the first network function may send a second message including information indicating a first list of related EAS information to a functional component of the UE.

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

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

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

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

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

[0183] Method 1200 may start from step S1201, in which the 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. Moreover, the first functional component may receive, from a third functional component (such as another one 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 Enablement Architecture Layer (SEAL) client 412 for vertical applications. Further, the third functional component is implemented as vertical application layer (VAL) clients 413, 414.

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

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

[0187] Next, method 1200 may proceed to step S1202, in which the first functional component may send a first message to a first network function implementing an edge enablement 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 for discovering an EAS server.

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

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

[0191] In an embodiment, after receiving a first message from a first functional component in a UE, a first network function (such as EES421) 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 at least one EAS. For example, the first network function may discover at least a first list of associated EAS information.

[0192] Next, method 1200 may proceed to step S1203, in which the first functional component may receive, from the first network function, a second message including information indicating a first list of associated EAS information.

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

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

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

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

[0197] 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 (such as EAS423) in an EDN respectively. Each first entry may indicate the EAS profile of the respective third network function. The EAS profile of each third network function may include the EAS ID of the respective third network function and the relationship between the second network function and the respective third network function.

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

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

[0200] In an embodiment, the first entry for the third network function further includes information indicating a second list of related EAS information. The second list of related EAS information may further include at least one second entry for at least one fourth network function that implements EAS (such as EAS424) in an EDN respectively. Each second entry may indicate the EAS profile of the respective fourth network function. The EAS profile of each fourth network function may include the EAS ID of the respective fourth network function and the relationship between the third network function and the respective fourth network function.

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

[0202] In an embodiment, each of at least one second entry of the second list of related 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 a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the related EAS information.

[0204] In an embodiment, the vertical application is any one of a future factory (FF), V2X, unmanned aerial system (UAS), and smart grid.

[0205] In an embodiment, the second network function is implemented as a service enable architecture layer (SEAL) server 422 for a vertical application, 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 a part of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the border setting).

[0206] In an embodiment, the SEAL server 422 may include a SEAL identification information management (IM) server. The SEAL IM server may provide a token validity confirmation service for the VAL server to confirm the validity of a token assigned by the SEAL IM server.

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

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

[0209] In an embodiment, the second network function is implemented as the FF application enable (FAE) server 423, and the third network function is implemented as the FF application specific (FFAS) server 424.

[0210] In an embodiment, the information indicating the first list of related EAS information is included in the set of EAS profiles of the first set of network functions implementing EAS in the EDN. For example, the first network function may discover a set of EASs (in other words, two or more EASs or at least one EAS) and provide information (such as an EAS profile) of the discovered set of EASs.

[0211] Next, the method 1200 may proceed to step S1204, where the first functional component may determine an EAS for selection. For example, the first functional component (e.g., the EEC) may determine the first set of network functions implementing EAS in the EDN from the set of EAS profiles. Additionally, the first functional component may determine the second set of network functions implementing EAS in the EDN from the first list of related EAS information. Note 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 top of (in other words, in a bordering configuration) the other of the two network functions.

[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 a delegation request. For example, the first functional component may provide several options (i.e., provide 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 and third functional components. That is, the first functional component may determine the network functions for the second functional component and the network functions for the third functional component according to the delegation request.

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

[0216] Upon receiving the notification, the second and third functional components may cooperate to select network functions such that the selected network functions are associated. For example, the selected network functions have an administrative or management relationship. For example, one of the selected network functions is registered on top of (in other words, on the border settings of) the other of the selected network functions. On the other hand, the third functional component may send a delegation request to the second functional component, whereby the second functional component may perform the selection on behalf of the third functional component.

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

[0218] The above steps are merely examples, and the UE may perform actions for managing related EAS information for selecting an application server deployed at the edge in an integrated view.

[0219] FIG. 13 is a schematic flowchart showing an exemplary EAS discovery method 1300 implemented by a second functional component in a UE according to an embodiment 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 start from step S1301, in which a second functional component (such as one of application clients 412, 413, or 414) may receive a delegation request for EAS discovery and selection for a third functional component from a third functional component (such as another one of application clients 412, 413, or 414) in the UE.

[0221] In an embodiment, the second functional component is implemented as a service enable architecture layer (SEAL) client 412 for a vertical application. Further, the third functional component is implemented as vertical application layer (VAL) clients 413, 414.

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

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

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

[0225] Next, after receiving a request from the second functional component, the first functional component (such as EEC411) may further request the first functional component (such as EES421) regarding the EAS discovery process. Next, the first network function may perform an EAS discovery process to discover EASs (such as EAS422, 423, 424, etc.). As a result, the first network function may discover at least one EAS. There may be an association between 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 above steps regarding FIG. 12.

[0226] Next, method 1300 may 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 related edge application server (EAS) information. In an embodiment, the first functional component is implemented as an edge enable client (EEC) 411. In an embodiment, the message is an EAS discovery response message or an EAS discovery notification message sent via an edge-5 reference point.

[0227] In an embodiment, the information indicating the first list of related EAS information may be included in the EAS profile of the second network function. The EAS profile of the second network function may further include information indicating an EAS ID and information indicating 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 an EDN respectively. Each first entry may indicate the EAS profile of each third network function. The EAS profile of each third network function may include the EAS ID of each third network function and the relationship between the second network function and each third network function.

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

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

[0231] In an embodiment, the first entry for a third network function (such as EAS423) further includes information indicating a second list of related EAS information. The second list of related EAS information may further include at least one second entry for at least one fourth network function (such as EAS424) that implements EAS in an EDN respectively. Each second entry may indicate the EAS profile of each fourth network function. The EAS profile of each fourth network function may include the EAS ID of each fourth network function and the relationship between the third network function and each fourth network function.

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

[0233] In an embodiment, each of at least one second entry of the second list of related EAS information may further indicate the endpoint information of the 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 a vertical application. Then, on the UE side, the UE may select at least two of the associated servers based on the related EAS information.

[0235] In an embodiment, the vertical application is any one of a future factory (FF), V2X, an unmanned aerial system (UAS), and a smart grid.

[0236] In an embodiment, the second network function is implemented as a service enable architecture layer (SEAL) server 422 for a vertical application, 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 a part of the procedures of the VAL servers 423, 424. For example, the VAL servers 423, 424 are registered on the SEAL server 422 (in other words, on the border setting).

[0237] In an embodiment, the SEAL server 422 may include a SEAL identification information management (IM) server. The SEAL IM server may provide a token validity confirmation service for the VAL servers 423, 424 to confirm the validity of the token assigned by the SEAL IM server.

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

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

[0240] In an embodiment, the second network function is implemented as the FF application enable (FAE) server 423, and the third network function is implemented as the FF application specific (FFAS) server 424.

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

[0242] Next, the method 1300 may proceed to step S1304, in which 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. Moreover, 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 a 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 the border setting).

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

[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 a network function for the second functional component and a network function 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 cooperate to select a network function so that the selected network function is 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 the border setting).

[0248] It should be noted that the above step S1301 and steps S1302 to S1303 may be implemented in any manner. For example, they may be implemented in any sequence, implemented simultaneously, or implemented separately.

[0249] The above step S1301 (in other words, delegation of EAS discovery and selection) may be an essential step, whereby the subsequent EAS selection step S1304 may be performed in the second functional component, or otherwise, it should be further noted that step S1304 is performed in the third functional component. Moreover, the above step S1301 may be an optional step, that is, 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 related EAS information is received.

[0250] The above steps are merely examples, and the UE may perform actions for managing related EAS information for selecting an application server deployed at the edge in an integrated view.

[0251] FIG. 14 is a schematic block diagram showing an exemplary first network function (such as EES421) according to an embodiment 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 the steps in the exemplary method 900 shown in the schematic flowchart of FIG. 9 and the exemplary method 1100 shown in the schematic flowchart of FIG. 11, the details of which are omitted here.

[0253] Note that the first network function 1400 can be implemented as hardware, software, firmware, and any combination thereof. For example, the first network function 1400 may include a plurality of units, circuits, modules, etc., each of which may be used to implement one or more steps of the exemplary methods 900 / 1100 or one or more steps shown in FIGS. 6-8 related to the EES.

[0254] It should be understood that the network function can 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, e.g., on a cloud infrastructure.

[0255] FIG. 15 is a schematic block diagram showing an exemplary second network function (such as EAS422, 423, 424, etc.) according to an embodiment 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 the steps in the exemplary method 1000 shown in the schematic flowchart of FIG. 10, the details of which are omitted here.

[0257] Note that the second network function 1500 can be implemented as hardware, software, firmware, and any combination thereof. For example, the second network function 1500 may include a plurality of units, circuits, modules, etc., each of which may be used to implement one or more steps of the exemplary method 1000 or one or more steps shown in FIGS. 6-8 related to EAS.

[0258] Note that, similar to the second network function, the above-described third network function and / or fourth network function can also be implemented as an EAS in the EDN. Thereby, the above-described 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] FIG. 16 is a schematic block diagram showing an exemplary UE according to an embodiment herein. In the embodiment, the UE 1600 may include functional components (such as EEC 411, SEAL 412, enabled client 413, application-specific client 414, etc.) as shown in FIGS. 4-5.

[0260] In the 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 the steps in the exemplary method 1200 shown in the schematic flowchart of FIG. 12 and / or the steps in the exemplary method 1300 shown in the schematic flowchart of FIG. 13, the details of which are omitted here.

[0261] Note that UE1600 may include hardware, software, firmware, and any combination thereof. For example, UE1600 may include a plurality of units, circuits, modules, etc., each of which may be used to perform one or more steps of exemplary methods 1200 / 1300, or one or more steps shown in FIGS. 6-8 related to the UE.

[0262] Also, the functional components in the UE (such as EEC, SEAL, enable client, application-specific client, etc.) can be hardware, software, firmware, and any combination thereof. For example, the functional components can be implemented as a plurality of units, circuits, modules, etc., each of which may be used to perform one or more steps of exemplary methods 1200 / 1300, or one or more steps shown in FIGS. 6-8 related to the UE.

[0263] In some embodiments, the non-limiting term UE is used. The UE1600 described herein can be any type of wireless device that is configured, arranged, and / or operable to communicate wirelessly with a network node and / or another wireless device via a wireless signal. Communicating wirelessly can involve transmitting and / or receiving a wireless signal using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for transmitting information through air. In certain embodiments, UE1600 can be configured to transmit and / or receive information without direct human interaction. For example, the UE can be designed to transmit information to the network at 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 capable of wireless communication, configured for wireless communication, arranged for wireless communication, and / or operable for wireless communication, such as a wireless communication device. Examples of UEs include, but are not limited to, smartphones. Further examples include wireless cameras, wireless-enabled tablet computers, laptop embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, and / or wireless customer premise equipment (CPE). Also, UE 900 may be a wireless communication device, a target device, a D2D UE, a machine type communication (MTC) UE or a machine-to-machine (M2M) communication-capable UE, a low-cost and / or low-complexity UE, a sensor equipped with a UE, a tablet, a mobile terminal, an Internet of Things (IoT) device, or a narrowband IoT (NB-IoT) device, or any other suitable device.

[0265] As one particular example, a UE may be configured for communication according to one or more communication standards published by the Third Generation Partnership Project (3GPP), such as the 3GPP global system for New Radio (NR), Global System for 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. The term "UE" as used herein 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 initially be associated with a particular human user.

[0266] FIG. 17 is a schematic block diagram showing an exemplary computer implementation device 1700 according to an embodiment herein. In an embodiment, the device 1700 can be configured as the above-described device, such as a first network function 1400, a second network function 1500, a third network function, a fourth network function, or a UE 1600.

[0267] In an embodiment, the device 1700 can include at least one processor, such as a central processing unit (CPU) 1701, a computer-readable medium 1702, and a memory 1703, without limitation. The memory 1703 can 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 can be configured to store a computer program and / or instructions that, when executed by the processor 1701, cause the processor 1701 to perform any of the above-described methods.

[0268] In an embodiment, the computer-readable medium 1702 (such as a non-transitory computer-readable medium) can be stored in the memory 1703. In another embodiment, the computer program can be stored (and can be embodied as a computer-readable medium) in a remote location, such as a computer program product 1704, and can be accessible by the processor 1701 via, for example, a 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 floppy disk, CD (compact disk), DVD (digital video disk), 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, a 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 via a network (e.g., Ethernet, ATM, ISDN, PSTN, X.25, the Internet, local area network (LAN), or similar network capable of transporting data packets to an infrastructure node).

[0270] Exemplary embodiments are described herein with reference to block diagrams and / or flowchart diagrams of a computer-implemented method, apparatus (system and / or device), and / or non-transitory computer program product. It should be understood that the blocks of the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions cause the instructions executed via the processor of a computer and / or other programmable data processing apparatus to implement the functions / acts specified in the block diagrams and / or one or more flowchart blocks by transforming and controlling transistors, values stored in memory locations, and other hardware components within such circuits, thereby creating means (functionality) and / or structures for implementing the functions / acts specified in the block diagrams and / or flowchart blocks, and can be provided to the processor circuits of general-purpose computer circuits, dedicated computer circuits, and / or other programmable data processing circuits to cause the machine to create a machine for implementing the functions / acts specified in the block diagrams and / or flowchart blocks.

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

[0272] Also, note that in some alternative implementations, the functions / acts recited in a block may be performed out of the order recited in the flowchart. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order depending on the functionality / acts involved. Additionally, the functionality of a given block of the flowchart and / or block diagram may be split into multiple blocks, and / or the functionality of two or more blocks of the flowchart and / or block diagram may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks shown, and / or blocks / acts may be omitted without departing from the scope of the inventive concept. Also, understand that while some of the figures include arrows on communication paths to indicate a primary direction of communication, communication may occur in the opposite direction of the drawn 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 regarded as illustrative and not restrictive, and the appended 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. Thus, 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 should not be limited or restricted by the forms for carrying out the above invention.

[0274] Abbreviations 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 Enable Client EES Edge Enable Server FAE Future Factory Application Enable FF Future Factory FFAPP Future Factory Application QoS Quality of Service SEAL Service Enable Architecture Layer for Vertical UAS Unmanned Aerial System UE User Equipment V2X Vehicle to Everything VAL Vertical Application Layer

Claims

1. A method (1000) implemented by a second network function (422) that implements an edge application server (EAS) in an edge data network (EDN) (402), comprising: - Sending (S1003) a registration request message to a first network function (421) that implements an edge enable server (EES) in the EDN (402), the registration request message comprising information indicating a first list of associated EAS information including wherein the first list of associated EAS information comprises at least one first entry for at least one third network function (423) that implements an EAS in the EDN (402), each first entry indicating an EAS profile of a respective third network function (423), and the EAS profile of each respective third network function (423) includes an EAS ID of each respective third network function (423) and a relationship between the second network function (422) and each respective third network function (423).

2. The method (1000) according to claim 1, wherein the first entry for the third network function (423) further comprises information indicating 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 an EAS in the EDN, each second entry indicating an EAS profile of a respective fourth network function (424), and the EAS profile of each respective fourth network function (424) includes an EAS ID of each respective fourth network function (424) and a relationship between the third network function (423) and each respective fourth network function (424).

3. 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, child, or sibling of the third network function (423). The method (1000) according to claim 2.

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

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

6. At least two of the second network function (422), the third network function (423), and the fourth network function (424) are set to jointly provide services for vertical applications. The method (1000) according to any one of claims 2 to 4.

7. The vertical application is any one of a future factory (FF), V2X (Vehicle to Everything), an unmanned aerial system (UAS), and a smart grid. The method (1000) according to claim 6.

8. - Receiving (S1001) from the third network function (423), the EAS ID of the third network function (423), the endpoint of the third network function (423), and registration information indicating the relationship between the second network function (422) and the third network function (423); - Storing (S1002) the registration information in the first list of related EAS information The method (1000) according to claim 6 or 7, further comprising.

9. - Receiving (S1001) from the third network function (423), registration information indicating the EAS profile of the third network function (423); - Storing (S1002) the registration information in the first list of related EAS information The method (1000) according to claim 6 or 7, further comprising.

10. The second network function (422) is implemented as a Service Enablement Architecture Layer (SEAL) server for the vertical application, and the third network function (423) is implemented as a Vertical Application Layer (VAL) server, wherein the SEAL server manages the procedures of the VAL server, The method (1000) according to any one of claims 6 to 9.

11. The SEAL server includes a SEAL Identification Information Management (IM) server, wherein the SEAL IM server provides the VAL server with a token validity confirmation service for confirming the validity of a token assigned by the SEAL IM server, The method (1000) according to claim 10.

12. The method (1000) according to claim 11, wherein the token is an access token and / or an ID token.

13. The method (1000) according to claim 11 or 12, wherein the VAL server is a FF Application Specific (FFAS) server or a FF Application Enable (FAE) server.

14. The method (1000) according to any one of claims 6 to 13, wherein the second network function (422) is implemented as a FF Application Enable (FAE) server, and the third network function (423) is implemented as a FF Application Specific (FFAS) server.

15. 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) that implements an edge enable server (EES) in an edge data network (EDN) (402) to discover at least one second network function (422) that implements an edge application server (EAS) in the EDN (402); - receiving (S1203) from the first network function (421) a second message containing information indicating a first list of related EAS information; and The first list of associated 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 indicating the EAS profile of a respective third network function (423), and the EAS profile of each respective third network function (423) including the EAS ID of each respective third network function (423) and the relationship between the second network function (422) and each respective third network function (423). Method (1200). Claim 16 The method (1200) according to claim 15, wherein the information indicating the first list of associated EAS information is included in the EAS profile of the at least one second network function (422). Claim 17 The method (1200) according to claim 15 or 16, wherein the first message further comprises an indicator explicitly indicating an EAS association. Claim 18 A second network function (422, 1500) that implements an edge application server (EAS) in an edge data network (EDN) (402), 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) including instructions executable by the at least one processor (1501) such that the at least one processor (1501) is configured to execute the method (1000) according to any one of claims 1 to 14. A second network function (422, 1500) comprising. Claim 19 A first network function (421, 1400) that implements an edge enabler server (EES) in an edge data network (EDN) (402), 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) including instructions executable by the at least one processor (1401), whereby the at least one processor (1401) is configured to execute the method (1200) according to any one of claims 15 to 17, non-transitory computer-readable medium (1402) and Comprising a first network function (421, 1400).

20. A computer program comprising computer-readable code that, when executed on a device (1700), causes at least one processor of the device (1700) to execute the method according to any one of claims 1 to 17.

Images