Method and apparatus for improved capability disclosure in edge enabler servers - Patents.com

Abstract

Various embodiments of the present disclosure provide methods and apparatus for improved capability disclosure in an edge enabler entity. The method implemented in the edge enabler entity comprises receiving a request for 3GPP core network capability disclosure from an edge application entity, the request comprising a UE group identifier that identifies a group of user equipment (UE). The method further comprises communicating with the 3GPP core network based on the request and sending a response to the edge application entity.

Description

[Technical field]

[0001] The present disclosure relates generally to the field of edge computing, and more particularly to a method and apparatus for improved capability exposure in an edge enabler server. [Background technology]

[0002] This section introduces aspects that may facilitate a better understanding of the present disclosure. Accordingly, the statements in this section are to be read in this light and not understood as admissions about what is in the prior art or what is not in the prior art.

[0003] I. Introduction to Edge Computing Application Enablers 3GPP TS 23.558 v1.0.0 specifies the application layer architecture, procedures, and information flows necessary to enable edge applications over 3GPP networks. 3GPP TS 23.558 v1.0.0 includes architectural requirements for enabling edge applications, application layer architectures that meet the architectural requirements, and procedures for enabling the deployment of edge applications.

[0004] One of the key areas of focus will be minimizing the impact on edge-based applications so that they do not require major application redevelopment for user equipment (UE) use at the edge.

[0005] FIG. 1 shows an architecture for enabling edge applications. An edge data network (EDN) is a local data network. An edge application server and an edge enabler server (EES) are included within the EDN. An edge configuration server provides configuration related to the EES, including details of the edge data network that hosts the EES. A UE includes an application client and an edge enabler client. The edge application server, edge enabler server, and edge configuration server may interact with a 3GPP core network.

[0006] The EDGE-3 reference point enables interaction between the edge enabler server and the edge application server. The EDGE-3 reference point is: a) registration of edge application servers with availability information (e.g., time constraints, location constraints); b) deregistering the Edge Application Server from the Edge Enabler Server; c) Providing access to network capability information (e.g., location information); and d) requesting the setup of a data session between the application client and the edge application server with a particular QoS. Support.

[0007] II. Exposing EES capabilities to Edge Application Servers (EAS) One important functionality in the edge enabling layer is EES exposed capabilities, including EES capabilities, and exposed 3GPP core network capabilities. 3GPP core network capabilities can be exposed from the EES to the edge application server using extensions. The re-exposed 3GPP core network capabilities are: 1) UE location API (Application Programming Interface), 2) User Plane Path Management API, and 3) Session with QoS API It could be. Summary of the Invention

[0008] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0009] The present disclosure proposes a method and apparatus for improved capability disclosure in the EES, in particular for re-disclosed 3GPP core network capabilities via the EES.

[0010] According to a first aspect of the present disclosure, a method is provided that is implemented in an edge enabler entity. The method comprises receiving a request for exposed capabilities of a 3GPP core network from an edge application entity, the request comprising a UE group identifier that identifies a group of user equipments (UEs). The method further comprises communicating with the 3GPP core network based on the request and sending a response to the edge application entity.

[0011] According to an example embodiment, the UE group identifier may be an internal group identifier or an external group identifier.

[0012] According to an example embodiment, the publishing capability may be a UE location publishing capability, or a user plane path management publishing capability, or a session with quality of service (QoS) publishing capability.

[0013] According to an example embodiment, the publishing capability may be a UE location publishing capability, the request may be a UE location subscribe request, and the response may be a UE location subscribe response. In an embodiment, communicating with the 3GPP core network may comprise subscribing to UE locations of a group of UEs identified by a UE group identifier and subscribing to UE expected behavior analysis for the group of UEs.

[0014] According to an example embodiment, the UE expected behavior analysis may comprise a UE mobility analysis.

[0015] According to an example embodiment, the method may further comprise: detecting UE location information of UEs in the group of UEs; determining whether to aggregate UE location information of the group of UEs and determining an aggregation period based on an analysis result of the UE expected behavior analysis received from the 3GPP core network, a local policy of the edge enabler entity, and UE location subscription information for the group of UEs received from the edge application entity; aggregating the detected UE location information of one or more UEs of the group of UEs for the aggregation period in response to the decision to aggregate the UE location information; and sending a UE location notification to the edge application entity, wherein the UE location notification comprises aggregated UE location information, in which each piece of UE location information comprises a UE identifier that identifies the UE, a location of the UE, and a location type indicating whether the UE location is actual or predicted; and in response to determining not to aggregate the UE location information, sending the UE location notification to the edge application entity comprising the detected UE location information of the UE.

[0016] According to an example embodiment, detecting UE location information of UEs in the group of UEs may comprise at least one of receiving UE location information of UEs in the group of UEs from a 3GPP core network, and deriving the UE location information of UEs in the group of UEs from an analysis result of the UE expected behavior analysis.

[0017] According to an example embodiment, the analysis result of the UE predicted behavior analysis may comprise UE mobility statistics and a UE mobility prediction. In an embodiment, the determining may be based on the UE mobility statistics and the retrieving may be based on the UE mobility prediction.

[0018] According to an example embodiment, the UE location subscription information may comprise a group reporting guard time.

[0019] According to an example embodiment, the method may further comprise receiving a UE location subscription update request from the edge application entity, updating a UE location subscription associated with the UE location subscription update request, updating a UE expected behavior analysis subscription in response to the UE location subscription update request related to the UE location subscription for the group of UEs, and sending a UE location subscription update response to the edge application entity.

[0020] According to an example embodiment, the method may further comprise receiving a UE location unsubscribe request from an edge application entity, unsubscribing from a UE location associated with the UE location unsubscribe request, unsubscribing from a UE expected behavior analysis in response to the UE location unsubscribe request related to a UE location subscription for the group of UEs, and sending a UE location unsubscribe response to the edge application entity.

[0021] According to an example embodiment, the publishing capability may be a user plane path management publishing capability, the request may be a user plane path management event subscribe request, and the response may be a user plane path management event subscribe response. In an embodiment, communicating with the 3GPP core network may comprise checking user plane path management events for a group of UEs identified by a UE group identifier and subscribing to UE expected behavior analysis for the group of UEs.

[0022] According to an example embodiment, the UE predicted behavior analysis may comprise both a UE mobility analysis and a UE communication analysis.

[0023] According to an example embodiment, the method may comprise detecting user plane path management events of UEs in a group of UEs; determining whether to aggregate user plane path management events for the group of UEs and determining an aggregation period based on an analysis result of the UE expected behavior analysis received from the 3GPP core network, a local policy of the edge enabler entity, and user plane path management event subscription information for the group of UEs received from the edge application entity; aggregating detected user plane path management events of one or more UEs of the group of UEs for the aggregation period in response to determining to aggregate user plane path management events; sending a user plane path management event notification to the edge application entity, where the user plane path management event notification comprises the aggregated user plane path management events; and in response to determining not to aggregate the user plane path management events, sending a user plane path management event notification to the edge application entity comprising the detected user plane path management events of the UEs.

[0024] According to an example embodiment, detecting a user plane path management event for a UE in the group of UEs may comprise receiving a user plane path management event notification for the UE in the group of UEs from the 3GPP core network.

[0025] According to an example embodiment, the analysis results of the UE predicted behavior analysis may comprise UE mobility statistics and UE communication statistics.

[0026] According to an example embodiment, the user plane path management event subscription information may comprise a group reporting guard time and an indication of an edge application server (EAS) acknowledgment response.

[0027] According to an example embodiment, the method may further comprise receiving a user plane path management event subscription update request from the edge application entity, checking a user plane path management event associated with the user plane path management event subscription update request, updating a UE expected behavior analysis subscription in response to the user plane path management event subscription update request related to a user plane path management event subscription for the group of UEs, and sending a user plane path management event subscription update response to the edge application entity.

[0028] According to an example embodiment, the method may further comprise receiving a user plane path management event unsubscribe request from the edge application entity, unsubscribing from a user plane path management event associated with the user plane path management event unsubscribe request, unsubscribing from the UE expected behavior analysis in response to the user plane path management event unsubscribe request related to a user plane path management event subscription for the group of UEs, and sending a user plane path management event unsubscribe response to the edge application entity.

[0029] According to an example embodiment, the publishing capability may be a session-with-QoS publishing capability, the request may be a session-with-QoS creation request, and the response may be a session-with-QoS creation response. In an embodiment, communicating with the 3GPP core network may comprise subscribing to protocol data unit (PDU) session status monitoring for a group of UEs identified by a UE group identifier, retrieving one or more IP addresses of one or more UEs in the group of UEs that already have an ongoing data session with the edge application entity, and requesting a data session with a particular QoS for each of the one or more UEs.

[0030] According to an example embodiment, the method may further comprise, after sending the Session with QoS creation response, receiving from the 3GPP core network a PDU session status notification comprising an IP address of a UE in the group of UEs, requesting a data session with a specific QoS for the UE, and sending a Session with QoS event notification for the UE to an edge application entity, where the Session with QoS event notification indicates an event related to the requested data session with the specific QoS.

[0031] According to an example embodiment, the method may further comprise receiving a session with QoS update request from the edge application entity, updating the data session with a specific QoS for the UE when an IP address of the UE to which the session with QoS update request is associated is known by the edge enabler entity, and sending a session with QoS update response to the edge application entity.

[0032] According to an example embodiment, the method may further comprise receiving a Session with QoS cancellation request from the edge application entity, unsubscribing from PDU session status monitoring for a group of UEs to which the Session with QoS cancellation request is associated, canceling a data session with a particular QoS associated with the Session with QoS cancellation request, and sending a Session with QoS cancellation response to the edge application entity.

[0033] According to a second aspect of the present disclosure, there is provided a method implemented in an edge application entity, comprising: sending a request for exposed capabilities of a 3GPP core network to an edge enabler entity, the request comprising a UE group identifier that identifies a group of user equipments (UEs), and receiving a response from the edge enabler entity.

[0034] According to an example embodiment, the publishing capability may be a UE location publishing capability, the request may be a UE location subscribe request, and the response may be a UE location subscribe response. In an embodiment, the method may further comprise at least one of receiving a UE location notification from an edge enabler entity, where the UE location notification comprises aggregated UE location information of one or more UEs in a group of UEs, where in the aggregated UE location information, each piece of UE location information comprises a UE identifier that identifies a UE in the group of UEs, a location of the UE, and a location type indicating whether the UE location is actual or predicted, and receiving a UE location notification from the edge enabler entity comprising detected UE location information of a UE in the group of UEs.

[0035] According to an example embodiment, the publishing capability may be a user plane path management publishing capability, the request may be a user plane path management event subscribe request, and the response may be a user plane path management event subscribe response. In an embodiment, the method may further comprise at least one of receiving a user plane path management event notification from the edge enabler entity, where the user plane path management event notification comprises aggregated user plane path management events of one or more UEs in the group of UEs, and receiving a user plane path management event notification from the edge enabler entity comprising detected user plane path management events of UEs in the group of UEs.

[0036] According to an example embodiment, the publishing capability may be a session with QoS publishing capability, the request may be a session with QoS creation request, and the response may be a session with QoS creation response. In an embodiment, the method may further comprise receiving, after receiving the session with QoS creation response, from the edge enabler entity, a session with QoS event notification for UEs in the group of UEs, where the session with QoS event notification indicates an event related to the requested data session with a particular QoS for the UE.

[0037] According to a third aspect of the present disclosure, an edge enabler entity is provided. The edge enabler entity may comprise one or more processors and one or more memories comprising computer program code. The one or more memories and the computer program code, together with the one or more processors, may be configured to cause the edge enabler entity to at least perform any of the steps of the method according to the first aspect of the present disclosure.

[0038] According to a fourth aspect of the present disclosure, an edge application entity is provided. The edge application entity may comprise one or more processors and one or more memories comprising computer program code. The one or more memories and the computer program code, together with the one or more processors, may be configured to cause the edge application entity to at least perform any of the steps of the method according to the second aspect of the present disclosure.

[0039] According to a fifth aspect of the present disclosure, a method is provided implemented in an edge enabler entity. The method comprises receiving a session with quality of service (QoS) creation request from an edge application entity, where the session with QoS creation request comprises a UE identifier that identifies a user equipment (UE). The method further comprises subscribing to protocol data unit (PDU) session status monitoring for the UE with a 3GPP core network, retrieving an IP address of the UE from the 3GPP core network if the UE already has an ongoing data session with the edge application entity, requesting a data session with a specific QoS for the UE, and sending a session with QoS creation response to the edge application entity.

[0040] According to an example embodiment, the method may further comprise: when the UE does not have an ongoing data session with the edge application entity and after sending the Session with QoS creation response, receiving a PDU session status notification from the 3GPP core network comprising an IP address of the UE; requesting a data session with a specific QoS for the UE; and sending a Session with QoS event notification for the UE to the edge application entity, where the Session with QoS event notification indicates an event related to the requested data session with the specific QoS.

[0041] According to an example embodiment, the method may further comprise receiving a session with QoS update request from the edge application entity, updating the data session with a specific QoS for the UE when an IP address of the UE to which the session with QoS update request is associated is known by the edge enabler entity, and sending a session with QoS update response to the edge application entity.

[0042] According to an example embodiment, the method may further comprise receiving a session with QoS cancellation request from the edge application entity, unsubscribing from PDU session status monitoring for a UE to which the session with QoS cancellation request is associated, canceling a data session with a particular QoS for the UE, and sending a session with QoS cancellation response to the edge application entity.

[0043] According to a sixth aspect of the present disclosure, there is provided a method implemented in an edge application entity, comprising: sending a session with quality of service (QoS) creation request to an edge enabler entity, the session with QoS creation request comprising a UE identifier that identifies a user equipment (UE), and receiving a session with QoS creation response from the edge enabler entity.

[0044] According to an example embodiment, the method may further comprise receiving, after receiving the session with QoS creation response, a user plane path management event notification for the UE from the edge enabler entity, where the user plane path management event notification indicates an event related to the requested data session with a particular QoS of the UE.

[0045] According to a seventh aspect of the present disclosure, an edge enabler entity is provided. The edge enabler entity may comprise one or more processors and one or more memories comprising computer program code. The one or more memories and the computer program code, together with the one or more processors, may be configured to cause the edge enabler entity to at least perform any step of the method according to the fifth aspect of the present disclosure.

[0046] According to an eighth aspect of the present disclosure, an edge application entity is provided. The edge application entity may include one or more processors and one or more memories comprising computer program code. The one or more memories and the computer program code, together with the one or more processors, may be configured to cause the edge application entity to perform at least any step of the method according to the sixth aspect of the present disclosure.

[0047] According to a ninth aspect of the present disclosure, there is provided a method implemented in an edge enabler entity. The method comprises receiving a subscribe request for published capabilities of a 3GPP core network from an edge application entity, the subscribe request comprising a UE identifier that identifies a user equipment (UE). The method further comprises acting on the subscribe request, subscribing to a UE expected behavior analysis for the UE with the 3GPP core network, and sending a subscribe response to the edge application entity.

[0048] According to an example embodiment, the publishing capability may be a UE location publishing capability or a user plane path management publishing capability.

[0049] According to an example embodiment, the publishing capability may be a UE location publishing capability. In an example, the subscribe request may be a UE location subscribe request and the subscribe response may be a UE location subscribe response. In an embodiment, the UE expected behavior analysis may comprise a UE mobility analysis.

[0050] According to an example embodiment, the method may further comprise detecting UE location information of the UE; determining whether to aggregate UE location information of the UE based on an analysis result of the UE expected behavior analysis received from the 3GPP core network, a local policy of the edge enabler entity, and UE location subscription information for the UE received from the edge application entity, and determining an aggregation period; in response to determining to aggregate the UE location information, aggregating the detected UE location information of the UE for the aggregation period; and sending a UE location notification to the edge application entity, wherein the UE location notification comprises aggregated UE location information, in the aggregated UE location information, each piece of UE location information comprises a location of the UE and a location type indicating whether the UE location is actual or predicted; and in response to determining not to aggregate the UE location information, sending the UE location notification to the edge application entity comprising the detected UE location information of the UE.

[0051] According to an example embodiment, the method may further comprise receiving a UE location subscription update request from the edge application entity, updating a UE location subscription for a UE to which the UE location subscription update request is associated, updating a UE expected behavior analysis subscription for the UE, and sending a UE location subscription update response to the edge application entity.

[0052] According to an example embodiment, the method may further comprise receiving a UE location unsubscribe request from the edge application entity, unsubscribing from a UE location of a UE to which the UE location unsubscribe request is associated, unsubscribing from a UE expected behavior analysis for the UE, and sending a UE location unsubscribe response to the edge application entity.

[0053] According to an example embodiment, the exposed capability may be a user plane path management exposed capability. In an example, the subscribe request may be a user plane path management event subscribe request and the subscribe response may be a user plane path management event subscribe response. In an example, the UE expected behavior analysis may comprise both a UE mobility analysis and a UE communication analysis.

[0054] According to an example embodiment, the method may further comprise detecting a user plane path management event of the UE; determining whether to aggregate user plane path management events for the UE based on an analysis result of the UE expected behavior analysis received from the 3GPP core network, a local policy of the edge enabler entity, and user plane path management event subscription information for the UE received from the edge application entity, determining an aggregation period; in response to determining to aggregate the user plane path management events, aggregating the detected user plane path management events of the UE for the aggregation period; and sending a user plane path management event notification to the edge application entity, where the user plane path management event notification comprises the aggregated user plane path management events; and in response to determining not to aggregate the user plane path management events, sending a user plane path management event notification to the edge application entity comprising the detected user plane path management events of the UE.

[0055] According to an example embodiment, the method may further comprise receiving a user plane path management event subscription update request from the edge application entity, checking a user plane path management event for a UE to which the user plane path management event subscription update request is associated, updating a UE expected behavior analysis subscription for the UE, and sending a user plane path management event subscription update response to the edge application entity.

[0056] According to an example embodiment, the method may further comprise receiving a user plane path management event unsubscribe request from the edge application entity, unsubscribing from user plane path management events for the UE to which the user plane path management event unsubscribe request is associated, unsubscribing from UE expected behavior analysis for the UE, and sending a user plane path management event unsubscribe response to the edge application entity.

[0057] According to a tenth aspect of the present disclosure, an edge enabler entity is provided. The edge enabler entity may comprise one or more processors and one or more memories comprising computer program code. The one or more memories and the computer program code, together with the one or more processors, may be configured to cause the edge enabler entity to at least perform any of the steps of the method according to the ninth aspect of the present disclosure.

[0058] According to an eleventh aspect of the present disclosure, there is provided a computer readable medium having computer program code disposed thereon which, when executed on a computer, causes the computer to perform any of the steps of the methods according to the first, second, fifth, sixth and ninth aspects of the present disclosure.

[0059] According to embodiments of the present disclosure, EES capability disclosure may be enhanced to support capability disclosure for groups of UEs.

[0060] The disclosure itself, preferred mode of use and further objects will best be understood by reference to the following detailed description of the embodiments when read in conjunction with the accompanying drawings. [Brief description of the drawings]

[0061] [Figure 1]FIG. 1 illustrates an architecture for enabling edge applications. [Diagram 2] FIG. 1 illustrates a subscribe operation for an existing UE location API. [Diagram 3] FIG. 1 illustrates notification operations for an existing UE location API. [Figure 4] FIG. 1 illustrates a subscribe operation for an existing user plane path management API. [Diagram 5] FIG. 1 illustrates notification operations for an existing user plane path management API. [Figure 6] FIG. 1 illustrates a create operation for an existing Session with QoS API. [Figure 7] FIG. 1 illustrates notification operations for existing Session with QoS APIs. [Figure 8] 1 is a flowchart illustrating a method implemented in an edge enabler entity according to some embodiments of the present disclosure. [Figure 9] FIG. 1 illustrates an improved subscribe operation for a UE location API according to some embodiments of the present disclosure. [Figure 10] FIG. 1 illustrates improved notification operations for a UE location API in accordance with some embodiments of the present disclosure. [Figure 11] FIG. 1 illustrates an improved subscription update operation for a UE location API in accordance with some embodiments of the present disclosure. [Figure 12] FIG. 1 illustrates an improved unsubscribe operation for a UE location API according to some embodiments of the present disclosure. [Figure 13] FIG. 1 illustrates an improved subscribe operation for a user plane path management API in accordance with some embodiments of the present disclosure. [Figure 14] FIG. 1 illustrates improved notification operations for a user plane path management API in accordance with some embodiments of the present disclosure. [Figure 15] FIG. 1 illustrates an improved subscription update operation for a user plane path management API in accordance with some embodiments of the present disclosure. [Figure 16] FIG. 1 illustrates an improved unsubscribe operation for a user plane path management API in accordance with some embodiments of the present disclosure. [Figure 17] FIG. 1 illustrates an improved create operation for a Session with QoS API in accordance with some embodiments of the present disclosure. [Figure 18] FIG. 1 illustrates an improved update operation for a Session with QoS API in accordance with some embodiments of the present disclosure. [Figure 19] FIG. 1 illustrates an improved cancellation operation for a Session with QoS API in accordance with some embodiments of the present disclosure. [Figure 20] 1 is a flowchart illustrating a method implemented in an edge application entity according to some embodiments of the present disclosure. [Figure 21] 1 is a flowchart illustrating a method implemented in an edge application entity according to some embodiments of the present disclosure. [Figure 22] FIG. 1 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0062] The embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be understood that these embodiments are not intended to imply any limitation on the scope of the present disclosure, but are merely discussed for the purpose of enabling those skilled in the art to better understand and implement the present disclosure. References to features, advantages, or similar phrases throughout this specification do not imply that all of the features and advantages that may be realized with the present disclosure should or are in a single embodiment of the present disclosure. Instead, phrases referring to features and advantages should be understood to mean that the particular features, advantages, or characteristics described in connection with an embodiment are included in at least one embodiment of the present disclosure. Moreover, the described features, advantages, and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a specific embodiment. In other cases, additional features and advantages may be recognized in some embodiments that may not be present in all embodiments of the present disclosure.

[0063] As used herein, the term "3GPP Core Network" refers to the 5G Core (5GC) in a 5G communications network, or the Evolved Packet Core (EPC) in a Long Term Evolved (LTE) communications network.

[0064] The term "terminal device" refers to any end device capable of accessing and receiving services from a communication network. By way of example and not limitation, a terminal device may refer to a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station, a portable subscriber station, a mobile station (MS) or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smartphone, a tablet, a wearable device, a personal digital assistant (PDA), a vehicle, and the like.

[0065] As yet another specific example, in an Internet of Things (IoT) scenario, a terminal device, sometimes referred to as an IoT device, may represent a machine or other device that performs monitoring, sensing, and / or measurement, etc., and transmits results of such monitoring, sensing, and / or measurement, etc. to another terminal device and / or network equipment. The terminal device, in this case, may be a Machine-to-Machine (M2M) device, which may be referred to in a 3rd Generation Partnership Project (3GPP) context as a Machine-Type Communication (MTC) device.

[0066] As one particular example, the terminal device may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g., personal wearables such as refrigerators, televisions, clocks, etc. In other scenarios, the terminal device may represent a vehicle or other equipment, e.g., medical equipment, capable of monitoring, sensing, and / or reporting on its operational status or other functions related to its operation.

[0067] The terms "first", "second", etc., as used herein refer to different elements. The singular forms "a" and "an" are intended to include the plural unless the context clearly indicates otherwise. The terms "comprises", "comprising", "has", "having", "includes" and / or "including" as used herein specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. The term "based on" should be read as "based at least in part on". The terms "one embodiment" and "an embodiment" should be read as "at least one embodiment". The term "another embodiment" should be read as "at least one other embodiment". Other provisions, both explicit and implicit, may be included below.

[0068] As described above, the re-exposed 3GPP core network capability from EES to EAS at the EDGE-3 reference point can be a UE location exposed capability (corresponding to the UE location API), a user plane path management exposed capability (corresponding to the user plane path management API), or a session with QoS exposed capability (corresponding to the session with QoS API). Next, the above three exposed capabilities are briefly introduced.

[0069] 1. UE Location API The edge enabler server exposes a UE location API to the edge application server to support tracking or checking the valid location of the UE. The UE location API exposed by the edge enabler server relies on 3GPP core network capabilities.

[0070] The edge application server can request a one-time report from the UE location API to check the current UE location and a continuous report to track the UE location. The UE location API supports both a request-response model for a one-time query (to check the UE's current location) and a subscribe-notification model to continuously provide the edge application server with the UE's location and enable the edge application server to track the UE's location (when the UE location changes).

[0071] Figures 2 and 3 respectively illustrate subscribe and notify operations between an edge application server and an edge enabler server for an existing UE location API. As shown in Figure 2, the edge application server sends a UE location subscribe request with a UE identifier that identifies the UE to the edge enabler server, and the edge enabler server responds with a UE location subscribe response. Table 1 shows the UE location subscribe request. TIFF0007603153000001.tif106170

[0072] As shown in Figure 3, the edge enabler server detects the location of the UE and sends a UE location notification with the location of the UE to the edge application server. Table 2 shows the UE location notification. TIFF0007603153000002.tif46170

[0073] 2. User Plane Path Management API The edge enabler server exposes user plane path management event notifications of the UE to the edge application server (e.g., to trigger application context relocation). The user plane path management API exposed by the edge enabler server may rely on the Network Exposed Function (NEF) northbound API for monitoring events of user plane path management events.

[0074] Figures 4 and 5 respectively illustrate the subscribe and notify operations between an edge application server and an edge enabler server for an existing user plane path management API. As shown in Figure 4, the edge application server sends a user plane path management event subscribe request to the edge enabler server, which includes a UE identifier that identifies the UE. The edge enabler server checks the user plane path management event of the UE with the 3GPP core network and responds with a user plane path management event subscribe response. Table 3 shows the user plane path management event subscribe request. TIFF0007603153000003.tif96170

[0075] As shown in Figure 5, the edge enabler server detects the user plane path management of the UE and sends a user plane path management event notification to the edge application server.

[0076] 3. Session with QoS API The edge enabler server exposes a Session with QoS API to the edge application server to support setting up a data session between an application client and the edge application server with a specific QoS, and modifying the QoS of this data session.

[0077] The Session with QoS APIs exposed by the edge enabler server rely on the northbound Policy Authorization Service APIs exposed by the Policy Control Function (PCF) as specified in 3GPP TS 23.502 v16.6.0 and 3GPP TS 23.503 v16.6.0 if the edge enabler server is connected to the PCF via the N5 reference point, or on the northbound Application Function (AF) Session with QoS Service APIs exposed by the NEF as specified in 3GPP TS 23.502 v16.6.0 and 3GPP TS 23.503 v16.6.0 if the edge enabler server is connected to the PCF via the NEF.

[0078] Figures 6 and 7 respectively illustrate the create and notify operations between an edge application server and an edge enabler server for the existing Session with QoS API. As shown in Figure 6, the edge application sends a Create Session with QoS request with the UE's IP address to the edge enabler server. The edge enabler server requests a data session with a specific QoS from the 3GPP core network and responds with a Create Session with QoS response. Table 4 shows the Create Session with QoS request. TIFF0007603153000004.tif120170

[0079] As shown in FIG. 7, the edge enabler server detects a user plane event for an established session with QoS and sends a session with QoS event notification to the edge application server.

[0080] However, the existing EES public APIs mentioned above only support a single UE for the UE location API and the user plane path management API. As shown in Table 1 and Table 3, the UE location subscribe request and the user plane path management event subscribe request comprise an identifier of a single UE, in other words, a GPSI or identity token. Moreover, the Session with QoS API only supports the IP address of a single UE as a target UE for an ongoing session. In addition, each notification is per UE. For example, the UE location notification only indicates the location of a single UE.

[0081] It is therefore desirable to provide an improved capability disclosure solution with more added value, which could be a high level abstraction for ease of use, or additional functionality / features, in order to optimize notification signaling over EDGE-3.

[0082] According to some example embodiments, the present disclosure provides an improved capability exposure solution in an edge enabler server that enables an edge application server to call an EES capability exposure API for a group of UEs via EDGE-3.

[0083] It should be noted that some embodiments of the present disclosure are described primarily with respect to the 5G specification, which is used as a non-limiting example for some exemplary network configurations and system deployments. Therefore, the description of the exemplary embodiments given herein will refer in detail to terminology directly related to the 5G specification. Such terminology is only used in the context of the presented non-limiting examples and embodiments, and of course does not limit the present disclosure in any way. Instead, any other system configuration or radio technology may be equally utilized as long as the exemplary embodiments described herein are applicable.

[0084] FIG. 8 is a flow chart illustrating a method 800 for improved capability exposure according to some embodiments of the present disclosure. The method 800 illustrated in FIG. 8 may be implemented in an edge enabler entity or performed by an apparatus communicatively coupled to the edge enabler entity. In some embodiments, the edge enabler entity may be implemented either on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g., a cloud infrastructure. The edge enabler server described above is an example of an edge enabler entity.

[0085] According to an example method 800 illustrated in FIG. 8, an edge enabler entity receives a request for 3GPP core network exposed capabilities from an edge application entity, as shown in block 802. The request comprises a UE group identifier that identifies a group of UEs. In some embodiments, the 3GPP core network exposed capabilities may be 3GPP core network capabilities that are re-exposed to the edge application entity via the edge enabler entity, including a UE location exposed capability (corresponding to a UE location API), a user plane path management exposed capability (corresponding to a user plane path management API), a session with QoS exposed capability (corresponding to a session with QoS API), or any other re-exposed 3GPP core network capability via EDGE-3. In some embodiments, the UE group identifier uniquely identifies a group of UEs within a public land mobile network (PLMN) domain. For example, the UE group identifier may be an inner group identifier as specified in 3GPP TS 23.501 v16.6.0, or an outer group identifier as specified in 3GPP TS 23.501 v16.6.0, or any other identifier that represents a group of UEs.

[0086] In some embodiments, an edge application entity may be implemented either on dedicated hardware, as a software instance running on the dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g., a cloud infrastructure. The edge application server described above is an example of an edge application entity.

[0087] The edge enabler entity then communicates with the 3GPP core network based on the received request in block 804. Depending on the published capability to which the request pertains, the edge enabler entity may perform a corresponding action with a particular network entity of the 3GPP core network. The edge enabler entity then sends a response to the edge application entity, as shown in block 806.

[0088] Next, the improved solutions for the UE Location API, the User Plane Path Management API, and the Session with QoS API are described in detail, respectively. In the following description, the terms "edge enabler server" and "edge application server" may be used instead of "edge enabler entity" and "edge application entity".

[0089] UE Location API Improvements The existing UE location API makes use of the 3GPP core network providing services that can support a group of UEs or even any UE, as described in TS 23.502, clause 4.15, as follows: "Target of event reporting: This can refer to a specific UE or PDU session, a group of UEs, or any UE (in other words, all UEs). Within a subscription, all event IDs are associated to the same target of event reporting (possibly corresponding to multiple UEs or multiple PDU sessions)."

[0090] With this in mind, in some embodiments of the present disclosure, a group-based UE location disclosure is proposed.

[0091] FIG. 9 illustrates an improved subscribing operation between an edge application entity and an edge enabler entity for continuous UE location reporting in accordance with some embodiments of the present disclosure.

[0092] As shown in Figure 9, an edge application server may send a UE location subscribe request to an edge enabler server at 901 to continuously track the location of the UE. The UE location subscribe request may include a UE group identifier to identify a group of UEs or a UE identifier to identify the UE, and may include a proposed expiration time. The UE location subscribe request may also include a desired format of the location that can be understood by the edge application server, such as a location granularity to indicate a GPS coordinate, a cell ID, a tracking area ID, or an official address (e.g., a road, a district, etc.), and a location accuracy to indicate a desired accuracy of the location information.

[0093] Upon receiving the UE location subscribe request including the UE group identifier, the edge enabler server may check whether the UE location subscribe request is permitted. If permitted, the edge enabler server may subscribe to the UE location of the group of UEs identified by the UE group identifier with the 3GPP core network at 902 by utilizing the UE location publishing capability of the 3GPP core network, e.g., Service Capability Publishing Function (SCEF) / NEF / SCEF+NEF or Location Service (LCS), as specified in 3GPP TS 23.558 v1.0.0 clause 8.9.3. Moreover, the edge enabler server may subscribe to UE expected behavior analysis for the group of UEs with the 3GPP core network (e.g., NEF or Network Data Analysis Function (NWDAF)) at 903, as described in 3GPP TS 23.288 v16.5.0. In an embodiment, the UE expected behavior analysis comprises UE mobility analysis.

[0094] The edge enabler server may then send a UE location subscribe response to the edge application server at 904. The UE location subscribe response includes a subscription identifier and may include an expiration time indicating when the subscription will automatically expire. If the UE location subscribe request is not permitted, the edge enabler server sends a failure response to the edge application server with a rejection cause.

[0095] The UE location subscribe request for the improved subscribe operation may be shown in Table 5 as follows: TIFF0007603153000005.tif92170

[0096] FIG. 10 illustrates an improved notification operation between an edge enabler server and an edge application server for continuous location according to some embodiments of the present disclosure.

[0097] As shown in FIG. 10, an edge enabler server may detect UE locations of UEs in a group of UEs at 1001. In some embodiments, the edge enabler server may receive UE location information of the UEs from a 3GPP core network. The received UE location information of the UEs may indicate an actual location of the UEs. In some embodiments, the edge enabler server may receive an analysis result of a UE expected behavior analysis from the 3GPP core network and retrieve UE location information of the UEs from the analysis result of the UE expected behavior analysis. In some embodiments, the analysis result of the UE expected behavior analysis may comprise UE mobility statistics and UE mobility prediction. The UE mobility statistics may indicate location statistics of the group of UEs during an analysis target period, and the UE mobility prediction may indicate a predicted location of the group of UEs during an analysis target period. Thus, the edge enabler server may retrieve UE location information of the UEs from the UE mobility prediction, and the UE location information indicates a predicted location of the UEs. The edge enabler server may then cache the detected UE location information locally with a timestamp as the latest location information of the UE.

[0098] The edge enabler server may then determine whether to aggregate UE location information of the group of UEs and determine an aggregation period based on the UE mobility statistics of the analysis result of the UE expected behavior analysis, the local policy of the edge enabler server, and the UE location subscription information for the group of UEs received from the edge application server. The aggregation period may indicate how long the aggregation of the UE location information should span. In some embodiments, the UE location subscription information may comprise a group reporting guard time received in the UE location subscribe request and specified in 3GPP TS23.502 v16.6.0, Table 4.15.1-1. The group reporting guard time is a parameter for group-based monitoring configuration to indicate the time during which monitoring event reports related to UEs in the group may be aggregated before sending the monitoring event reports to a consumer network function (NF).

[0099] If it is determined to aggregate the UE location information of the group of UEs, the edge enabler server may aggregate the detected UE location information of one or more UEs of the group of UEs for an aggregation period. The edge enabler server may then send a UE location notification to the edge application server at 1002. The UE location notification may comprise the aggregated UE location information. Each of the UE location information may comprise a UE identifier that identifies the UE, a location of the UE, and a location type that indicates whether the location of the UE is actual or predicted. In addition, the UE location information may also include a location accuracy and a timestamp of the location. If it is determined not to aggregate the UE location information, the edge enabler server may send a UE location notification to the edge application server at 1002, comprising the detected UE location information of the UE.

[0100] The UE location notification for improved notification operation may be shown in Table 6 as follows: TIFF0007603153000006.tif75170

[0101] FIG. 11 illustrates an improved subscription update operation between an edge application server and an edge enabler server for a UE location API according to some embodiments of the disclosure.

[0102] As shown in Figure 11, the edge application server may send a UE location subscription update request to the edge enabler server at 1101. The UE location subscription update request includes a subscription identifier of the subscription to be updated, and may also include a proposed expiration time for the updated subscription, an updated location granularity, and location accuracy information.

[0103] Upon receiving the UE location subscription update request, the edge enabler server may check whether the UE location subscription update request is permitted. If permitted, the edge enabler server may update the UE location subscription associated with the UE location subscription update request in the 3GPP core network at 1102. If the UE location subscription update request relates to a UE location subscription for a group of UEs, the edge enabler server may update the UE expected behavior analysis subscription for the group of UEs in the 3GPP core network at 1103. The edge enabler server may then send a UE location subscription update response to the edge application server at 1104.

[0104] The UE location subscription update request for the improved subscription update operation may be shown in Table 7 as follows, without the UE identifier. TIFF0007603153000007.tif96170

[0105] FIG. 12 illustrates an improved unsubscribe operation between an edge application server and an edge enabler server to stop UE location notification according to some embodiments of the present disclosure.

[0106] As shown in FIG. 12, the edge application server may send a UE location unsubscribe request to the edge enabler server at 1201. Upon receiving the UE location unsubscribe request, the edge enabler server may check whether the edge application server is authorized. If authorized, the edge enabler server may unsubscribe from the UE location associated with the UE location unsubscribe request at 1202. Furthermore, if the UE location unsubscribe request relates to a UE location subscription for a group of UEs, the edge enabler server may unsubscribe from the UE expected behavior analysis for the group of UEs at 1203. The edge enabler server may then send a UE location unsubscribe response to the edge application server at 1204.

[0107] In addition, in some embodiments, aggregation of location information may also be applicable to the case of a single UE. In this case, the UE location subscribe request may comprise a UE identifier that identifies the UE. Upon receiving the UE location subscribe request from the edge application server, the edge enabler server may subscribe to the UE location of the UE identified by the UE identifier and subscribe to a UE expected behavior analysis for the UE using the 3GPP core network. The UE expected behavior analysis may comprise a UE mobility analysis. The edge enabler server may then send a UE location response to the edge application server.

[0108] In the notification operation, the edge enabler server may detect the UE location information of the UE. For example, the edge enabler server may receive the UE location information of the UE as the actual UE location from the 3GPP core network, and / or retrieve the UE location information of the UE as the predicted UE location from the UE mobility prediction received from the 3GPP core network. The edge enabler server may determine whether to aggregate the UE location information of the UE and an aggregation period based on the UE mobility statistics, the local policy of the edge enabler server, and the UE location subscription information for the UE received in the UE location subscribe request. If it is determined to aggregate the UE location information of the UE, the edge enabler server may aggregate the detected UE location information of the UE for the aggregation period and send a UE location notification comprising the aggregated UE location information to the edge application server. If it is determined not to aggregate the UE location information of the UE, the edge enabler server may send a UE location notification comprising the detected UE location information of the UE to the edge application server.

[0109] In a subscription update operation, the edge enabler server may receive a UE location subscription update request from the edge application server. The edge enabler server may then update the UE location subscription of the UE to which the UE location subscription update request is associated, and update the UE predicted behavior analysis subscription for the UE. Finally, the edge enabler server may send a UE location subscription update response to the edge application server.

[0110] In an unsubscribe operation, the edge enabler server may receive a UE location unsubscribe request from the edge application server. The edge enabler server may then unsubscribe from the UE location of the UE to which the UE location unsubscribe request is associated, and unsubscribe from the UE expected behavior analysis for the UE. Finally, the edge enabler server may send a UE location unsubscribe response to the edge application server.

[0111] User Plane Path Management API Improvements The existing user plane path management API also utilizes 3GPP core network providing services, and when NEF is used, the existing user plane path management API can support groups of UEs as targets, as described in TS 23.501 and TS 23.502. In view of this, in some embodiments of the present disclosure, a group-based user plane path management exposure is proposed.

[0112] FIG. 13 illustrates an improved subscribe operation between an edge application server and an edge enabler server for user plane path management event notifications according to some embodiments of the present disclosure.

[0113] As shown in Figure 13, the edge application server may send a user plane path management event subscribe request to the edge enabler server in order to continuously track user plane path changes of the UE at 1301. The user plane path management event subscribe request includes a UE group identifier to identify a group of UEs or a UE identifier to identify the UE. The user plane path management event subscribe request may also include a subscription type (early and / or late notification as specified in clause 5.6.7 of 3GPP TS 23.501 v16.6.0) and / or an indication of EAS acknowledgement as specified in table 8.6.3.3.1 of 3GPP TS 23.588 v1.0.0.

[0114] Upon receiving the user plane path management event subscribe request including the UE group identifier, the edge enabler server may check whether the edge application server is authorized for this operation. If authorized, the edge enabler server may check 1302 for user plane path management events for the group of UEs identified by the UE group identifier. In an embodiment, the edge enabler server may check whether a subscription exists with the 3GPP core network for user plane path management event notifications corresponding to the group of UEs, which may be triggered by other edge application servers for the same group of UEs, as described in 3GPP TS 23.501 v16.6.0 and 3GPP TS 23.502 v16.6.0. The edge enabler server may check the availability of a user plane path management event service for the UE. If there is no user plane path management event subscription with the 3GPP core network, the edge enabler server subscribes with the 3GPP core network (e.g., PCF, NEF or SCEF+NEF) for user plane path management event notification of the group of UEs as described in 3GPP TS23.501 v16.6.0 and 3GPP TS23.502 v16.6.0. If the edge application server provides an indication of subscription type and / or EAS acknowledgement in the user plane path management event subscribe request, the edge enabler server includes an indication of "expected AF acknowledgement" as information about the AF subscription to the corresponding Session Management Function (SMF) event in the AF request. If there is a user plane path management event subscription with the 3GPP core network, the edge enabler server uses the locally cached user plane path management event notification information of the group of UEs to respond to the edge application server. The edge enabler server may store subscriptions related to the edge application server.

[0115] The edge enabler server may then subscribe to UE expected behavior analysis for the group of UEs specified in 3GPP TS23.288 v16.5.0 at 1303. In an embodiment, the UE expected behavior analysis may comprise both UE mobility analysis and UE communication analysis. The edge enabler server may then send a user plane path management event subscribe response to the edge application server at 1304. If the edge application server is not authorized, the edge enabler server provides a reject response with cause information.

[0116] The user plane path management event subscribe request for improved subscribe operation may be shown as Table 8 below. TIFF0007603153000008.tif133170

[0117] FIG. 14 illustrates an improved notification operation between an edge enabler server and an edge application server for continuous user plane path management event notification in accordance with some embodiments of the present disclosure.

[0118] As shown in FIG. 14, an edge enabler server may detect, at 1401, a user plane path management event of a UE in a group of UEs. In some embodiments, the edge enabler server may receive a user plane path management event notification for the UE in the group of UEs from a 3GPP core network. The edge enabler server may cache the detected user plane path management event notification locally with a timestamp as the latest information for the UE. The edge enabler server may then determine whether to aggregate user plane path management events for the group of UEs and determine an aggregation period based on an analysis result of the UE expected behavior analysis received from the 3GPP core network, a local policy of the edge enabler server, and user plane path management event subscription information for the group of UEs received from the edge application entity. The aggregation period may indicate how long the aggregation of the user plane path management events should span. In some embodiments, the analysis result of the UE expected behavior analysis may comprise UE mobility statistics and UE communication statistics. The UE communication statistics may indicate traffic statistics for the group of UEs. In some embodiments, the user plane path management subscription information is received in a user plane path management event subscribe request and may comprise a group reporting guard time and an indication of EAS acknowledgement as specified in 3GPP TS23.502 v16.6.0, Table 4.15.1-1. If the indication of EAS acknowledgement indicates that an EAS acknowledgement is expected, the edge enabler server should not aggregate user plane path management events for the group of UEs as aggregation may delay the overall process.

[0119] If it is determined to aggregate user plane path management events for the group of UEs, the edge enabler server may aggregate detected user plane path management events of one or more UEs of the group of UEs for an aggregation period. The edge enabler server may then send a user plane path management event notification to the edge application server at 1402. The user plane path management event notification may comprise the aggregated user plane path management events. If it is determined not to aggregate user plane path management events for the group of UEs, the edge enabler server may send a user plane path management event notification to the edge application server at 1402 comprising the detected user plane path management events of the UEs.

[0120] The user plane path management event notification for improved notification behavior may be shown in Table 9 as follows: TIFF0007603153000009.tif56170

[0121] FIG. 15 illustrates an improved subscription update operation between an edge application server and an edge enabler server for user plane path management event notifications according to some embodiments of the present disclosure.

[0122] 15, an edge application server may send a user plane path management event subscription update request to an edge enabler server to update an existing user plane path management event subscription at 1501. The user plane path management event subscription update request may include a subscription type (early and / or late notification as specified in clause 5.6.7 of 3GPP TS 23.501 v16.6.0) and / or an indication of an EAS acknowledgement.

[0123] Upon receiving the user plane path management event subscription update request, the edge enabler server may check whether the edge application server is authorized for operation. If authorized, the edge enabler server may check the user plane path management event associated with the user plane path management event subscription update request at 1502. In an embodiment, the edge enabler server may check whether there is a subscription with the 3GPP core network for user plane path management event notification corresponding to the updated information obtained at 1501, as described in 3GPP TS23.501 v16.6.0 and 3GPP TS23.502 v16.6.0. If there is no subscription with the 3GPP core network for user plane path management event notification corresponding to the updated information, the edge enabler server may subscribe with the 3GPP core network (e.g., PCF, NEF or SCEF+NEF) for user plane path management event notification. If a subscription exists with the 3GPP core network that corresponds to the updated information, the edge enabler server may use the locally cached user plane path management event notification information to respond to the edge application server.

[0124] Then, if the user plane path management event subscription update request relates to a user plane path management event subscription for the group of UEs, the edge enabler server may update the UE expected behavior analysis subscription for the group of UEs in the 3GPP core network, at 1503. The edge enabler server may then send a user plane path management event subscription response to the edge application server, at 1504.

[0125] FIG. 16 illustrates an improved unsubscribe operation between an edge application server and an edge enabler server for user plane path management event notifications according to some embodiments of the present disclosure.

[0126] As shown in FIG. 16, the edge application server may send a user plane path management event unsubscribe request to the edge enabler server to cancel the user plane path management event subscription at 1601. Upon receiving the user plane path management event unsubscribe request, the edge enabler server may unsubscribe the user plane path management event associated with the user plane path management event unsubscribe request from the 3GPP core network at 1602 if other edge application servers do not need to track the user plane path changes of the group of UEs or UEs to which the user plane path management event unsubscribe request is associated. Furthermore, if the user plane path management event unsubscribe request relates to a user plane path management event subscription for a group of UEs, the edge enabler server may unsubscribe from the UE expected behavior analysis for the group of UEs at 1603. The edge enabler server may then send a user plane path management event unsubscribe response to the edge application server at 1604.

[0127] The improved UE location API and user plane path management API may support group-based location publishing, which provides the advantage that the edge application server reduces the number of UE location subscriptions or user plane management event subscriptions, in other words, the subscriptions described above are group-based instead of per UE in a group of UEs. Furthermore, the edge enabler server, as a central supporting layer between the edge application server and the 3GPP core network, may aggregate location information or user plane path management events of a group of UEs before publishing them to the edge application server. This is beneficial when several UEs are moving together (e.g., in a bus / train) and aggregation of location information or user plane path management events may add further utility to the republished UE location API and user plane path management API.

[0128] In addition, in some embodiments, aggregation of user plane path management events may also be applicable to the case of a single UE. In this case, the user plane path management event subscribe request may comprise a UE identifier that identifies the UE. Upon receiving the user plane path management event subscribe request from the edge application server, the edge enabler server may check the user plane path management events for the UE identified by the UE identifier and subscribe to UE expected behavior analysis for the UE using the 3GPP core network. The UE expected behavior analysis may comprise UE mobility analysis and UE communication analysis. The edge enabler server may then send a user plane path management event subscribe response to the edge application server.

[0129] In the notification operation, the edge enabler server may detect a user plane path management event of the UE. For example, the edge enabler server may receive a user plane path management event notification of the UE from the 3GPP core network. The edge enabler server may determine whether to aggregate the user plane path management event of the UE and an aggregation period based on the UE mobility statistics and the UE communication statistics, the local policy of the edge enabler server, and the user plane path management event subscription information for the UE received in the user plane path management event subscribe request. If it is determined to aggregate the user plane path management event of the UE, the edge enabler server may aggregate the detected user plane path management event of the UE for the aggregation period and send a user plane path management event notification comprising the aggregated user plane path management event to the edge application server. If it is determined not to aggregate the user plane path management event of the UE, the edge enabler server may send a UE location notification comprising the detected user plane path management event of the UE to the edge application server.

[0130] In a subscription update operation, the edge enabler server may receive a user plane path management event subscription update request from the edge application server. The edge enabler server may then check the user plane path management events of the UE to which the user plane path management event subscription update request is associated, and update the UE expected behavior analysis subscription for the UE. Finally, the edge enabler server may send a user plane path management event subscription update response to the edge application server.

[0131] In an unsubscribe operation, the edge enabler server may receive a user plane path management event unsubscribe request from the edge application server. The edge enabler server may then unsubscribe from user plane path management events for the UE to which the user plane path management event unsubscribe request is associated, and unsubscribe from UE expected behavior analysis for the UE. Finally, the edge enabler server may send a user plane path management event unsubscribe response to the edge application server.

[0132] Session with QoS API improvements The existing Session with QoS API only supports UE IP addresses as target UEs for an ongoing session. In light of this, in some embodiments of the present disclosure, the Session with QoS API may be extended to provide support for more representations of target UEs, such as groups of UEs.

[0133] 17 illustrates an improved session-with-QoS creation operation between an edge application server and an edge enabler server according to some embodiments of the present disclosure, which may be used to request reservation of resources for a data session between an application client and an edge application server with a particular QoS, and to subscribe to certain session-with-QoS event notifications.

[0134] As shown in FIG. 17, an edge application server may send a session with QoS creation request for the establishment of a data session between an application client and the edge application server with a specific QoS (either a QoS reference or a bandwidth) at 1701. The session with QoS creation request may include a UE group identifier for identifying a group of UEs, or a UE identifier for identifying the UE, or an IP address of the UE, and a data network name (DNN) and single network slice selection assistance information (S-NSSAI) used for the data session between the application client and the edge application server. With the same request, the edge application server may subscribe to receive certain session with QoS event notifications (e.g., notifications that a QoS target can no longer be met (or can be met again)).

[0135] Upon receiving the Session with QoS creation request including the UE group identifier or UE identifier, the edge enabler server may check whether the edge application server is authorized for this operation for the group of UEs identified by the UE group identifier or the UE identified by the UE identifier. If authorized, at 1702, the edge enabler server may subscribe to Protocol Data Unit (PDU) session status monitoring for the group of UEs or the UEs using the 3GPP core network (e.g., a public function (NEF / SCEF / SCEF+NEF), or an SMF). Alternatively, the edge enabler server may subscribe to Packet Data Network (PDN) connectivity status monitoring for the group of UEs or the UEs. If one or more UEs or UEs in the group of UEs already have an ongoing data session with the edge application server, the edge enabler server may retrieve one or more IP addresses of one or more UEs or UEs from the 3GPP core network. The edge enabler server may then request a data session with a specific QoS for each of the one or more UEs or for the UE at 1703 and send a session with QoS creation response to the edge application server at 1704. The session with QoS creation response may include a context identifier and a result of the requested data session with the specific QoS. If any UE or UEs in the group of UEs do not have an ongoing data session, the edge enabler server waits for further notification about the PDU session status and sends a session with QoS creation response to the edge application server at 1704.

[0136] In addition, when the edge enabler server did not retrieve the IP address of the UE in 1702, the edge enabler server may receive a PDU session status notification from the 3GPP core network comprising an IP address of a UE in a group of UEs or an IP address of a UE identified by a UE identifier in 1705. The edge enabler server may then request a data session with a specific QoS for the UE and send a session with QoS event notification for the UE to the edge application server in 1706. The session with QoS event notification may indicate an event related to the requested data session with a specific QoS for the UE, e.g., a context identifier for the requested data session.

[0137] The Session with QoS Create request for the improved create operation may be shown in Table 10 as follows: TIFF0007603153000010.tif140170

[0138] 18 illustrates an improved session-with-QoS update operation between an edge application server and an edge enabler server according to some embodiments of the present disclosure, which is used to request a modification of the QoS of a data session between an application client and an edge application server.

[0139] As shown in FIG. 18, an edge application server may send a session with QoS update request to request modification of the QoS of a data session between an application client and the edge application server at 1801. The session with QoS update request may include a context identifier and a different QoS reference or a different bandwidth value. Upon receiving the session with QoS update request, the edge enabler server may check whether there is a context of the context identifier available and whether the edge application server is authorized for this operation. If yes, the edge enabler server may check whether the IP address of the UE to which the session with QoS update request is associated is known by the edge enabler server. If the IP address of the UE is known by the edge enabler server, the edge enabler server may update the data session with the specific QoS of the UE at 1802. For example, the edge enabler server may invoke a policy authorization update service or an AF session with QoS update service with the 3GPP core network (PCF or NEF, respectively) to provide updated information to the PCF or NEF, respectively, as described in 3GPP TS23.501 v16.6.0 and 3GPP TS23.502 v16.6.0. The edge enabler server may subscribe to additional events or unsubscribe to an event, if necessary. The edge enabler server may then send a session with QoS update response to the edge application server, at 1803. If the operation is successful, the edge enabler server responds with the context identifier and the result in the session with QoS update response. If the edge application server is not authorized or other failures occur during the operation, the edge enabler server provides a reject response with cause information.

[0140] 19 illustrates an improved Session with QoS cancellation operation between an edge application server and an edge enabler server according to some embodiments of the present disclosure. This operation is used to cancel a data session between an application client and an edge application server with a particular QoS and to unsubscribe to related Session with QoS event notifications.

[0141] As shown in FIG. 19, an edge application server may send a Session with QoS Cancel request to request cancellation of a data session with QoS between an application client and the edge application server at 1901. The Session with QoS Cancel request may include a context identifier. Upon receiving the Session with QoS Cancel request, the edge enabler server may check whether there is a context of the context identifier available and whether the edge application server is authorized for this operation. If yes, the edge enabler server may unsubscribe from PDU session status monitoring for the group or UE to which the Session with QoS Cancel request is associated at 1902, and cancel the data session with the specific QoS associated with the Session with QoS Cancel request at 1903 by invoking a policy permission removal service or an AF Session with QoS Cancel service with the 3GPP core network (PCF or NEF, respectively) as described in 3GPP TS23.501 v16.6.0 and 3GPP TS23.502 v16.6.0. The edge enabler server may then send a Session with QoS Cancel response to the edge application server at 1904. If the operation is successful, the edge enabler server responds with the context ID and the result in the Session with QoS Cancel response. If the edge application server is not authorized or other failure occurs during the operation, the edge enabler server provides a reject response with cause information.

[0142] With the improved Session with QoS API, the edge enabler server can support applying the required QoS to both ongoing and future sessions for a single UE or a group of UEs.

[0143] According to the embodiment of the present disclosure described above, the edge enabler server may: 1) receive user plane path management events by subscribing with the 3GPP core network for user plane path management event notifications of the UE as described in 3GPP TS23.501 v16.6.0 and 3GPP TS23.502 v16.6.0; 2) receive user plane path management events by subscribing with the 3GPP core network for user plane path management event notifications of the UE as described in 3GPP TS23.682 v16.8.0, 3GPP TS23.502 v16.6.0, 3GPP TS23.271 v16.0.0, 3GPP TS36.305 v16.1.0, 3GPP TS23.273 v16.4.0 and 3GPP TS38.305 v16.2.0 to obtain the location of a group of UEs or the location of the UE. v16.1.0, 3) capabilities exposed by the 3GPP core network, e.g., NEF or PCF, to establish an AF session with QoS, and QoS related event notifications subscribed with the 3GPP core network, as specified in 3GPP TS 23.501 v16.6.0, 3GPP TS 23.502 v16.6.0 and 3GPP TS 23.503 v16.6.0, 4) capabilities exposed by the 3GPP core network, e.g., NEF or NWDAF, to analyze UE expected behavior, as specified in 3GPP TS 23.288 v16.5.0, and 5) capabilities exposed by the 3GPP core network, e.g., NEF or NWDAF, to analyze UE expected behavior, as specified in 3GPP TS 23.501 v16.6.0 and 3GPP TS 23.502 v16.6.0. As specified in v16.6.0, it is possible to utilize the PDU session status / PDN connectivity status monitoring capabilities published by the 3GPP core network (e.g., published functions (NEF / SCEF / SCEF+NEF), or SMF).

[0144] 20 is a flow chart illustrating a method 2000 for improved capability exposure according to some embodiments of the present disclosure. The method 2000 illustrated in FIG. 20 may be performed by an apparatus implemented in an edge application entity or communicatively coupled to an edge application entity.

[0145] According to an example method 2000 illustrated in Figure 20, an edge application entity sends a request for exposed capabilities of a 3GPP core network to an edge enabler entity, as shown in block 2002. The request comprises a UE group identifier that identifies a group of UEs. The edge application entity then receives a response from the edge enabler entity, as shown in block 2004.

[0146] In some embodiments, the UE group identifier may be an inner group identifier as specified in 3GPP TS23.501 v16.6.0, an outer group identifier as specified in 3GPP TS23.501 v16.6.0, or any other identifier that represents a group of UEs.

[0147] In some embodiments, the publishing capability may be a UE location publishing capability. In this case, the request may be a UE location subscribe request and the response may be a UE location subscribe response. Further, in some embodiments, the edge application entity may receive from the edge enabler entity a UE location notification comprising aggregated UE location information of one or more UEs of the group of UEs and / or a UE location notification comprising detected UE location information of UEs in the group of UEs.

[0148] In some embodiments, the publishing capability may be a user plane path management publishing capability. In this case, the request may be a user plane path management event subscribe request and the response may be a user plane path management event subscribe response. Further, in some embodiments, the edge application entity may receive from the edge enabler entity a user plane path management event notification comprising aggregated user plane path management events of one or more UEs in the group of UEs and / or a user plane path management event notification comprising detected user plane path management events of UEs in the group of UEs.

[0149] In some embodiments, the publishing capability may be a session with QoS publishing capability. In this case, the request may be a session with QoS creation request and the response may be a session with QoS creation response. Further, in an embodiment, after receiving the session with QoS creation response, the edge application entity may receive a session with QoS event notification for the UEs in the group of UEs from the edge enabler entity, where the session with QoS event notification may indicate an event related to the requested data session with a particular QoS for the UE.

[0150] 21 is a flow chart illustrating a method 2100 for improved capability publishing according to some embodiments of the present disclosure. The method 2100 illustrated in FIG. 21 may be performed by an apparatus implemented in an edge application entity or communicatively coupled to an edge application entity.

[0151] According to an example method 2100 illustrated in Figure 21, the edge application entity sends a create session with QoS request to the edge enabler entity, as shown in block 2102. The create session with QoS request comprises a UE identifier that identifies the UE. The edge application entity then receives a create session with QoS response from the edge enabler entity, as shown in block 2104.

[0152] Further, in some embodiments, after receiving the Session with QoS creation response, the edge application entity may receive a Session with QoS event notification for the UE from the edge enabler entity, where the Session with QoS event notification may indicate an event related to the requested data session with a particular QoS for the UE.

[0153] It should be noted that the order for performing steps or actions shown in Figures 8-21 is illustrated as an example only. In some implementations, some steps may be performed in reverse order or in parallel. In some other implementations, some steps may be omitted or combined.

[0154] The various blocks or actions depicted in Figures 8-21 may be considered as method steps and / or actions resulting from the operation of computer program code and / or a number of coupled logic circuit elements configured to perform related functions. The schematic flow chart diagrams described above are generally described as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of particular embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the order in which a particular method is performed may or may not strictly follow the order of the corresponding steps shown.

[0155] FIG. 22 is a block diagram illustrating an apparatus 2200 according to various embodiments of the present disclosure. As shown in FIG. 22, the apparatus 2200 may include one or more processors, such as processor 2201, and one or more memories, such as memory 2202, that store computer program code 2203. The memory 2202 may be a non-transitory machine / processor / computer-readable storage medium. According to some exemplary embodiments, the apparatus 2200 may be implemented as an integrated circuit chip or module that may be plugged or attached to an edge enabler entity or edge application entity described with respect to FIGS. 5-21.

[0156] In some implementations, the one or more memories 2202 and the computer program code 2203, together with the one or more processors 2201, may be configured to cause the apparatus 2200 to perform at least the operations of any of the methods described in connection with Figures 5-21. In such embodiments, the apparatus 2200 may be implemented as at least a part of an edge enabler entity or an edge application entity described above, or may be communicatively coupled to an edge enabler entity or an edge application entity. As a particular example, the apparatus 2200 may be implemented as an edge enabler entity or an edge application entity.

[0157] Alternatively or additionally, the one or more memories 2202 and the computer program code 2203, together with the one or more processors 2201, may be configured to cause the apparatus 2200 to perform more or less operations to implement at least the proposed methods according to exemplary embodiments of the present disclosure.

[0158] In general, various exemplary embodiments may be implemented in hardware or dedicated chips, circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be illustrated and described as block diagrams, flow charts, or using some other diagrammatic representation, it should be fully understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controller or other computing device, or any combination thereof.

[0159] It should therefore be appreciated that at least some aspects of the exemplary embodiments of the present disclosure may be practiced in a variety of components, such as integrated circuit chips and modules, etc. Thus, it should be appreciated that the exemplary embodiments of the present disclosure may be realized in an apparatus embodied as an integrated circuit, where the integrated circuit may comprise circuitry (and possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, a baseband circuit, and a radio frequency circuit that are configurable to operate in accordance with the exemplary embodiments of the present disclosure.

[0160] It should be appreciated that at least some aspects of the exemplary embodiments of the present disclosure may be embodied in computer-executable instructions, such as in one or more program modules executed by one or more computers or other devices. Generally, a program module includes routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer-executable instructions may be stored in a computer-readable medium, such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, a random access memory (RAM), etc. As will be appreciated by those skilled in the art, the functionality of the program modules may be combined or distributed as desired in various embodiments. In addition, the functionality may be embodied in whole or in part in firmware or hardware equivalents, such as integrated circuits, field programmable gate arrays (FPGAs), etc.

[0161] The present disclosure includes any novel feature or combination of features explicitly disclosed herein or any generalization thereof. Various modifications and adaptations to the above exemplary embodiments of the present disclosure may become apparent to those skilled in the art in view of the above description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure.

Claims

1. 1. A method implemented in an edge enabler server, comprising: receiving a request for a 3GPP core network publishing capability from an edge application server, the request comprising a UE group identifier that identifies a group of user equipments (UEs), the publishing capability being a UE location publishing capability or a user plane path management publishing capability, and the UE group identifier being an internal group identifier or an external group identifier; communicating with the 3GPP core network based on the request; sending a response to the edge application server; Equipped with The method comprises: determining whether the notification information should be aggregated and determining an aggregation period; In response to determining to aggregate the notification information, sending a notification to the edge application server comprising the aggregated notification information. Furthermore, The method further comprises detecting UE location information of UEs in the group of UEs; determining whether to aggregate notification information for the group of UEs and determining an aggregation period; determining whether to aggregate the UE location information of the group of UEs and determining an aggregation period based on an analysis result of a UE expected behavior analysis (i.e., UE mobility analysis) for the group of UEs received from the 3GPP core network, a local policy of the edge enabler server, and UE location subscription information for the group of UEs received from the edge application server; In response to determining to aggregate the UE location information, sending the notification to the edge application server comprises aggregated notification information. aggregating the detected UE location information of one or more UEs of the group of UEs during the aggregation period; sending a UE location notification to the edge application server, the UE location notification comprising the aggregated UE location information, wherein in the aggregated UE location information, each piece of UE location information comprises a UE identifier that identifies the UE, a location of the UE, and a location type that indicates whether the location is actual or predicted; Equipped with method.

2. the publishing capability is the UE location publishing capability, the request is a UE location subscribe request, and the response is a UE location subscribe response; communicating with the 3GPP core network, Subscribing to UE locations of the group of UEs identified by the UE group identifier; and subscribing to UE expected behavior analysis (i.e., UE mobility analysis) for the group of UEs. Equipped with The method of claim 1.

3. In response to determining not to aggregate the UE location information, sending a UE location notification to the edge application server, the UE location notification comprising the detected UE location information of the UE; The method of claim 2 further comprising:

4. Detecting UE location information of UEs in the group of UEs, receiving, from the 3GPP core network, the UE location information of the UEs in the group of UEs; deriving the UE location information of the UEs in the group of UEs from the analysis result of the UE expected behavior analysis; and the analysis results of the UE expected behavior analysis comprise UE mobility statistics and UE mobility predictions; the determining is based on the UE mobility statistics and the retrieving is based on the UE mobility prediction. The method according to claim 2 or 3.

5. The method of claim 2 , wherein the UE location subscription information comprises a group reporting guard time.

6. receiving a UE location subscription update request from the edge application server; updating the UE location subscription associated with the UE location subscription update request; updating the UE predicted behavior analysis subscription in response to the UE location subscription update request related to the UE location subscription for the group of UEs; sending a UE location subscription update response to the edge application server; The method of claim 2 , further comprising:

7. receiving a UE location unsubscribe request from the edge application server; unsubscribing from the UE location associated with the UE location unsubscribe request; unsubscribing from the UE expected behavior analysis in response to the UE location unsubscribe request related to the UE location subscription for the group of UEs; sending a UE location unsubscribe response to the edge application server; The method of claim 2 , further comprising:

8. the publishing capability is the user plane path management publishing capability, the request is a user plane path management event subscribe request, and the response is a user plane path management event subscribe response; said communicating with said 3GPP core network checking a user plane path management event for the group of UEs identified by the UE group identifier; subscribing to a UE expected behavior analysis for the group of UEs; the UE expected behavior analysis comprises both a UE mobility analysis and a UE communication analysis; The method of claim 1.

9. detecting the user plane path management event of a UE in the group of UEs; Furthermore, determining whether to aggregate notification information for the group of UEs and determining an aggregation period comprises determining whether to aggregate user plane path management events for the group of UEs and determining an aggregation period based on an analysis result of the UE expected behavior analysis received from the 3GPP core network, a local policy of the edge enabler server, and user plane path management event subscription information for the group of UEs received from the edge application server; In response to determining to aggregate the user plane path management events, in response to determining to aggregate the notification information, sending a notification to the edge application server comprising aggregated notification information, aggregating the detected user plane path management events of one or more UEs of the group of UEs during the aggregation period; sending a user plane path management event notification to the edge application server, wherein the user plane path management event notification comprises the aggregated user plane path management event. The method of claim 8.

10. In response to determining not to aggregate the user plane path management events, sending to the edge application server a user plane path management event notification comprising the detected user plane path management event of the UE.

10. The method of claim 9.

11. Detecting the user plane path management event for a UE in the group of UEs includes receiving a user plane path management event notification for the UE in the group of UEs from the 3GPP core network. Equipped with the analysis results of the UE expected behavior analysis comprise UE mobility statistics and UE communication statistics; the user plane path management event subscription information comprises a group reporting guard time and an indication of an edge application server (EAS) acknowledgment; 11. The method according to claim 9 or 10.

12. receiving a user plane path management event subscription update request from the edge application server; checking the user plane path management event associated with the user plane path management event subscription update request; updating the UE expected behavior analysis subscription in response to the user plane path management event subscription update request related to a user plane path management event subscription for the group of UEs; sending a user plane path management event subscription update response to the edge application server; The method of any one of claims 8 to 11, further comprising:

13. receiving a user plane path management event unsubscribe request from the edge application server; unsubscribing from the user plane path management event associated with the user plane path management event unsubscribe request; unsubscribing from the UE expected behavior analysis in response to the user plane path management event unsubscribe request related to the user plane path management event subscription for the group of UEs; sending a user plane path management event unsubscribe response to the edge application server; 13. The method of claim 8, further comprising:

14. 1. A method implemented in an edge application server, comprising: sending a request for a 3GPP core network publishing capability to an edge enabler server, the request comprising a UE group identifier that identifies a group of user equipments (UEs), the publishing capability being a UE location publishing capability or a user plane path management publishing capability, and the UE group identifier being an internal group identifier or an external group identifier; receiving a response from the edge enabler server; Equipped with The method comprises: receiving a notification from the edge enabler server, the notification comprising aggregated notification information; Furthermore, the publishing capability is the UE location publishing capability, the request is a UE location subscribe request, and the response is a UE location subscribe response; Receiving the notification comprising the aggregated notification information comprises: receiving a UE location notification from the edge enabler server, the UE location notification comprising aggregated UE location information of one or more UEs in the group of UEs, wherein in the aggregated UE location information, each piece of UE location information comprises a UE identifier that identifies a UE in the group of UEs, a location of the UE, and a location type that indicates whether the UE location is actual or predicted; Equipped with method.

15. The receiving of the notification comprising the aggregated notification information, comprising: receiving, from the edge enabler server, a UE location notification comprising detected UE location information of UEs in the group of UEs; 15. The method of claim 14.

16. the publishing capability is the user plane path management publishing capability, the request is a user plane path management event subscribe request, and the response is a user plane path management event subscribe response; Receiving the notification comprising the aggregated notification information comprises: receiving a user plane path management event notification from the edge enabler server, the user plane path management event notification comprising aggregated user plane path management events for one or more UEs in the group of UEs; receiving, from the edge enabler server, a user plane path management event notification comprising a detected user plane path management event of a UE in the group of UEs; comprising at least one of:

15. The method of claim 14.

17. an edge enabler server, one or more processors; one or more memories containing computer program code; Equipped with The one or more memories and the computer program code, together with the one or more processors, are configured to cause the edge enabler server to perform the method of any one of claims 1 to 13. Edge Enabler Server.

18. An edge application server, one or more processors; one or more memories containing computer program code; Equipped with The one or more memories and the computer program code, together with the one or more processors, are configured to cause the edge application server to execute the method of any one of claims 14 to 16. Edge application server.

Images