Edge enabler layer service differentiation

Abstract

[0004] Embodiments herein relate to service differentiation at an edge enabler layer. Some embodiments propose a method (300) performed by a user equipment (UE) (101) implementing an enabler function. In one embodiment, the method (300) may include a step (S301) of sending a first message to an edge configuration server (ECS) to request service provisioning, the first message including one or more edge enabler server (EES) provider identifiers identifying one or more desired EES providers. In one embodiment, the method (300) may further include a step (S302) of receiving a second message from the ECS indicating one or more EESs (121). [0005] Embodiments herein may optimize interactions at the EDGE-4 reference point.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to PCT International Application No. PCT / CN2022 / 122742, entitled "EDGE ENABLER LAYER SERVICE DIFFERENTIATION," filed September 29, 2022, the entire contents of which are incorporated herein by reference.

[0002] FIELD Embodiments herein generally relate to the field of edge computing, and more particularly, embodiments herein relate to service differentiation for edge enabler layers (EELs). [Background technology]

[0003] Edge computing is a concept that allows services to be hosted closer to the service consumers, offering benefits such as efficient service delivery with significantly reduced end-to-end latency and reduced load on transport networks. The benefits of edge computing strengthen the promise of 5G and open the door to several new and enhanced use cases, including virtual and augmented reality, the Internet of Things (IoT), industrial IoT, autonomous driving, real-time multiplayer gaming, etc.

[0004] In Release 17, 3GPP aims to provide native support for edge computing in 3GPP networks. These efforts involve activities across several 3GPP working groups, including SA6, SA2, SA3, SA4, and SA5, covering aspects of application layer architecture, core network hardening, security, media processing, and management, respectively.

[0005] SA6 has initiated work on a standard specification for an architecture for enabling edge applications (EDGEAPP). The objective of this work is to define an enabling layer to facilitate communication between application clients (ACs) running on user equipment (UE) and edge application servers (EASs) deployed on edge data networks (EDNs). This includes aspects of service provisioning and EAS discovery. Additionally, this work aims to provide supporting services such as application context transfer between EASs for service continuity, service activation, and a functional exposure application programming interface (API) for EASs.

[0006] 1 is a schematic block diagram illustrating an example architecture of a wireless communication system 100 for enabling edge applications. As shown in FIG. 1, functional entities may include: Edge Enabler Server (EES): The EES 121 may provide the necessary support functions for the EAS 121 and Edge Enabler Client (EEC) 111, such as EEC registration, EAS discovery, and network APIs for EAS and service continuity support. Edge Enabler Client (EEC): The EEC 111 may provide the necessary support functions for the AC 112, such as obtaining and provisioning configuration information to enable application data traffic, and EAS discovery. Edge Configuration Server (ECS): The ECS 103 may provide the support functions necessary for the EEC 111 to connect with the EES 121, such as provisioning edge configuration information to the EEC 111 and EES discovery. Application Client (AC): The AC 112 is an application residing in the UE 101 that performs client functions. Edge Application Server (EAS): The EAS 122 is an application server that resides in the EDN 102 and performs server functions. The AC 112 may connect to the EAS 122 to utilize the services of applications that have the benefits of edge computing.

[0007] When discussing the next release, say release 18, there are some outstanding issues. Summary of the Invention

[0008] Embodiments herein propose a method, a UE, a network function, a computer-readable medium, and a computer program product for service differentiation of an edge enabler layer.

[0009] Some embodiments propose a method performed by a UE implementing an enabler function. The method may include sending a first message to an ECS to request service provisioning. The first message may include one or more EES provider identifiers that identify one or more desired EES providers. The method may further include receiving a second message from the ECS indicating the one or more EES providers.

[0010] In one embodiment, one or more EESs may be configured with edge subscription data for the UE.

[0011] In one embodiment, the one or more EESs may be provided by at least one of one or more desired EES providers identified by one or more EES provider identifiers.

[0012] In one embodiment, the one or more EESs may be determined based on one or more EES provider identifiers.

[0013] In one embodiment, the one or more EES provider identifiers may correspond to a list of desired EES provider identifiers, and the list may include at least one desired EES provider identifier.

[0014] In one embodiment, one or more EESs may be represented by one or more endpoints of the respective one or more EESs.

[0015] In one embodiment, the method may further include selecting an EES from one or more EESs to provide differentiated services to the UE according to configured edge subscription data for the UE.

[0016] In one embodiment, the edge subscription data may be stored in a selected EES.

[0017] In one embodiment, the edge subscription data may include a UE ID of the UE.

[0018] In one embodiment, the edge subscription data may include at least one of an edge service level or a service policy.

[0019] In one embodiment, the first message may be a service provisioning request message over the EDGE-4 reference point.

[0020] In one embodiment, the second message may be a service provisioning response message over the EDGE-4 reference point.

[0021] In one embodiment, the first message may be a service provisioning subscription request message over the EDGE-4 reference point.

[0022] In one embodiment, the second message may be a service provisioning notification message over the EDGE-4 reference point.

[0023] Some embodiments propose a method performed by an ECS. The method may include receiving a first message for requesting service provisioning from a UE implementing an enabler function. The first message may include one or more EES provider identifiers that identify one or more desired EES providers. The method may further include transmitting a second message to the UE indicating one or more EES providers that take into account the one or more EES provider identifiers included in the first message.

[0024] In one embodiment, the indicated one or more EESs may be configured with edge subscription data for the UE.

[0025] In one embodiment, the one or more EESs may be provided by at least one of one or more EES providers identified by one or more EES provider identifiers.

[0026] In one embodiment, the one or more EES provider identifiers may correspond to a list of desired EES provider identifiers, and the list may include at least one desired EES provider identifier.

[0027] In one embodiment, one or more EESs may be represented by one or more endpoints of the respective one or more EESs.

[0028] In one embodiment, the first message may be a service provisioning request message over the EDGE-4 reference point.

[0029] In one embodiment, the second message may be a service provisioning response message over the EDGE-4 reference point.

[0030] In one embodiment, the first message may be a service provisioning subscription request message over the EDGE-4 reference point.

[0031] In one embodiment, the second message may be a service provisioning notification message over the EDGE-4 reference point.

[0032] In some embodiments, a UE is proposed, comprising at least one processor and a non-transitory computer-readable medium coupled to the at least one processor. In one embodiment, the non-transitory computer-readable medium may store instructions executable by the at least one processor, whereby the at least one processor may be configured to perform the above-described method associated with the above-described UE.

[0033] In some embodiments, a network function is proposed, comprising at least one processor and a non-transitory computer-readable medium coupled to the at least one processor. In one embodiment, the non-transitory computer-readable medium may store instructions executable by the at least one processor, whereby the at least one processor may be configured to perform the above-described method associated with the above-described ECS. In one embodiment, the network function may be configured as the above-described ECS.

[0034] In some embodiments, a computer readable medium is proposed that stores computer readable code that, when run on a device, causes the device to perform any of the above methods.

[0035] In some embodiments, a computer program product is proposed that stores computer readable code that, when run on a device, causes the device to perform any of the methods described above.

[0036] According to embodiments herein, the EEC may provide the ECS with desired EES service providers, thus narrowing down the number of EES candidates in the service provisioning response (i.e., undesired EESs may be filtered by the ECS), thereby optimizing the exchange over the EDGE-4 reference point between the EEC and the ECS.

[0037] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate various embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure and to enable one skilled in the art to make and use the embodiments disclosed herein, in which like reference numbers indicate equivalent or functionally similar elements. [Brief explanation of the drawings]

[0038] [Figure 1] FIG. 1 is a schematic block diagram illustrating an example architecture of a wireless communication system for enabling edge applications. [Figure 2A] 1 is a schematic signaling chart illustrating messages in a service provisioning request-response procedure according to embodiments herein. [Figure 2B] 1 is a schematic signaling chart illustrating messages in a service provisioning subscription-notification procedure according to embodiments herein. [Figure 3] 1 is a schematic flowchart illustrating an exemplary method in a UE, according to embodiments herein. [Figure 4] 1 is a schematic flowchart illustrating an exemplary method in a first network function, according to embodiments herein. [Figure 5] 1 is a schematic block diagram illustrating an exemplary UE, according to embodiments herein. [Figure 6] FIG. 1 is a schematic block diagram illustrating exemplary network functionality, according to embodiments herein. [Figure 7] FIG. 1 is a schematic block diagram illustrating an exemplary computer-implemented device, according to embodiments herein. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0041] When discussing the next release, say Release 18, there are some open issues. Key Issue (KI#12) (Service Differentiation for EEL) states: "Service differentiation in Rel-17 is quite general and not detailed (e.g., ECS uses local policies to determine service provisioning). More details should be specified to allow ECSPs to offer different service quality levels, such as principles based on the role of the service consumer. For example, premium users should get the closest available edge, or there should be certain applications available only to premium users." Open issues: -What service differentiation should EEL enable? -What procedures should be strengthened to support service differentiation? -Which functional entity is responsible for defining or managing service differentiation?”

[0042] Currently, Solution #12 of 3GPP TR23.700-98 focuses on the aspect of service continuity plan authentication based on UE policies configured in the EES, and there is no solution that addresses aspects related to advanced edge computing services for premium users and how to detect EESs that have such UE policies configured.

[0043] In view of the above key challenges, the embodiments propose a solution for detecting the appropriate EES configured UE policy (as part of edge subscription data).

[0044] The embodiment may be implemented in a wireless communication system 100 shown in FIG.

[0045] In one embodiment, the wireless communication system 100 may be configured in an OTT scenario. The OTT connection may be transparent in the sense that the participating communication devices through which the OTT connection passes are unaware of the routing of the uplink and downlink communications. For example, the base station may not, or need not, be informed about the past routing of incoming downlink communications involving data originating from the ECS 103, EES 121, or EAS 122 that are forwarded (e.g., handed over) to the connected UE 101. Similarly, the base station need not be aware of the future routing of outgoing uplink communications originating from the UE 101 toward the ECS 103, EES 121, or EAS 122.

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

[0047] FIG. 2A is a schematic signaling chart illustrating messages in a service provisioning request-response procedure according to an embodiment herein.

[0048] In one embodiment, messages in the service provisioning request-response procedure of Figure 2A may be sent over the EDGE-4 reference point, which enables communication between the ECS 103 and the EEC 111. The EDGE-4 reference point supports a) provisioning of edge configuration information to the EEC 111.

[0049] In one embodiment, the signaling chart of FIG. 2A may include the following messages or steps:

[0050] Step 1: The EEC 111 may send a service provisioning request to the ECS 103. The service provisioning request may include a UE identifier, such as a Generic Public Subscription Identifier (GPSI), connection information, a UE location, and AC profile information.

[0051] In one embodiment, EEC 111 may provide its desired EES service provider (e.g., edge computing service provider, ECSP) to ECS 103. Such information may enable ECS 103 to provision EEC 111 with EES 121 based on the EES registration provider information.

[0052] In one embodiment, the EEC 111 may obtain the preferred EES provider ID through an end-user setting. For example, Alice may sign a VIP contract with Amazon's edge computing service, and then Alice may set the EEC 111 in the UE 101 to "Preferred EES provider=Amazon," or this setting may be done by Amazon's server via short message service (SMS), device trigger, etc.

[0053] In one embodiment, the EEC 111 may be configured with two or more preferred EES providers. For example, the EEC 111 (a special application client for edge computing) may subscribe to multiple EES providers (e.g., Amazon, Google, AT&T). This is similar to everyday life: a person may be a VIP at multiple shopping malls, and when a person wants to know the exact street address of a preferred shopping mall, they can turn to a web service (e.g., Google Maps) to make a query.

[0054] In one embodiment, the EEC 111 may determine the EES provider to be used in the service provisioning request. For example, if the EEC 111 has multiple preferred EES providers (e.g., Amazon, Google, AT&T), the EEC 111 may decide to use one or more of the preferred EES providers. Typically, the EEC 111 may include all preferred EES providers in the service provisioning request and may obtain a list of EESs corresponding to all of the preferred EES providers. However, it is also possible that the end user may apply conditions, such as preferring Amazon on weekdays and Google on holidays. All of these decisions are internal behaviors within the EEC 111.

[0055] Table 1 below describes the information elements for a service provisioning request sent from the EEC 111 to the ECS 103. TIFF2025533611000002.tif142170

[0056] As can be seen from Table 1, the EEC 111 may include one or more EES provider identifiers as parameters in the service provisioning request message. The one or more EES provider identifiers may indicate a list of preferred EES providers.

[0057] Step 2: Upon receiving the request, the ECS 103 may perform an authorization check to verify whether the EEC 111 has the authorization to perform the operation. The ECS 103 may also determine other information that needs to be provisioned, such as, for example, an identification of the EDN, an EDN service area, an EES endpoint, etc. In one embodiment, the ECS 103 may determine the EES endpoint to be provided to the EEC 111 by considering one or more EES provider identifiers in addition to other filters. For example, the ECS 103 may determine, based on the EES registration provider information, from the EESs hosted by the ECS 103, an EES provided by an EES service provider that holds valid edge subscription data for the UE.

[0058] Step 3: If the request is processed successfully, the ECS 103 may respond to the EEC 111's request with a service provisioning response. For example, the ECS 103 may include the endpoint of the EES determined in step 2 in the service provisioning response message. The EEC 111 may cache the service provisioning information (e.g., the EES endpoint) for later use and avoid the need to repeat step 1. In one embodiment, the EEC 111 may receive only the EES corresponding to the EES provider ID sent in step 1.

[0059] Additionally, ECS 103 may reject the service provisioning request and respond with an appropriate failure cause.

[0060] In one embodiment, upon receiving service provisioning information (e.g., EES endpoints), the EEC 111 may select an EES 121 from the received EES information. The selected EES 121 may host or obtain edge subscription data for the UE and thus provide differentiated services to the UE 101.

[0061] For example, the EES 121 may obtain edge subscription data regarding the UE 101 after receiving the EAS discovery request from the EEC 111. The EES 121 may then operate differently in provisioning EAS candidates to the service consumer (e.g., the EEC 111) based on the edge subscription data regarding the UE 101.

[0062] Table 2 below describes the information elements of the edge subscription data for UE 101. TIFF2025533611000003.tif49170

[0063] In one example, the service policy may be the maximum number of applications for edge computing. For example, the EES 121 may only support a maximum of five applications for a free UE. In one example, the service policy may be the temporal and spatial conditions for providing edge services, such as EAS detection under different edge service levels.

[0064] FIG. 2B is a schematic signaling chart illustrating messages in a service provisioning subscription-notification procedure according to an embodiment herein.

[0065] In one embodiment, messages in the service provisioning subscription-notification procedure of Figure 2B may be sent over the EDGE-4 reference point, which allows communication between the ECS 103 and the EEC 111. The EDGE-4 reference point supports a) provisioning of edge configuration information to the EEC 111.

[0066] In one embodiment, the signaling chart of FIG. 2B may include the following messages or steps:

[0067] Step 1: The EEC 111 may send a service provisioning subscription request to the ECS 103. The service provisioning subscription request includes a notification target address (e.g., a URL) and may include a UE identifier such as GPSI, connection information, a proposed expiration date, and AC profile information.

[0068] In one embodiment, EEC 111 may provide its preferred EES service provider (e.g., ECSP) to ECS 103. Such information may enable ECS 103 to provision EEC 111 with EES 121 based on the EES registration provider information.

[0069] In one embodiment, the service provisioning subscription request may include one or more of the information elements shown in Table 1 above. For example, the EEC 111 may include one or more EES provider identifiers as parameters in the service provisioning subscription request message. The one or more EES provider identifiers may indicate a list of preferred EES providers.

[0070] Step 2: Upon receiving the request, the ECS 103 may perform an authorization check to verify whether the EEC 111 has the authorization to perform the operation. If the request is authenticated, the ECS 103 may create and store a subscription for provisioning.

[0071] Step 3: If the request is processed successfully, the ECS 103 may respond with a service provisioning subscription response.

[0072] Additionally, the ECS 103 may reject the service provisioning subscription request and respond with an appropriate failure reason.

[0073] Step 4: An event occurs in the ECS 103 that satisfies a trigger condition for updating the service provisioning of the subscribed EEC 111. The ECS 103 may determine information that needs to be provisioned, such as, for example, an identification of the EDN, an EDN service area, and an EES endpoint. In one embodiment, the ECS 103 may determine the EES endpoint to be provided to the EEC 111 by considering one or more EES provider identifiers in addition to other filters. For example, the ECS 103 may determine, based on the EES registration provider information, from the EESs hosted by the ECS 103, an EES provided by an EES service provider that holds valid edge subscription data for the UE.

[0074] The ECS 103 may then send a provisioning notification including the determined information to the EEC 111. For example, the ECS 103 may include the endpoint of the EES determined in step 2 in the service provisioning notification message. In one embodiment, the EEC 111 may receive only the EES corresponding to the EES provider ID sent in step 1.

[0075] In one embodiment, upon receiving service provisioning information (e.g., EES endpoints), the EEC 111 may select an EES 121 from the received EES information. The selected EES 121 may host or obtain edge subscription data for the UE and thus provide differentiated services to the UE 101.

[0076] For example, the EES 121 may obtain edge subscription data for the UE 101 after receiving the EAS discovery request from the EEC 111. The EES 121 may then operate differently in provisioning EAS candidates to the service consumer (e.g., the EEC 111) based on the edge subscription data for the UE 101 (shown in Table 2 above).

[0077] As can be seen from the above, in some embodiments, EEC111 may indicate its preferred EES provider as part of the service provisioning request filter, and ECS103 may provide a matching EES to EEC111 based on the registered EES information (i.e., EES provider).

[0078] According to embodiments herein, the EEC 111 may provide the ECS 103 with desired EES service providers, thus narrowing down the number of EES candidates in the service provisioning response (undesired EESs may be filtered by the ECS). As a result, interactions over the EDGE-4 reference point between the EEC 111 and the ECS 103 may be optimized.

[0079] Furthermore, embodiments may enable service differentiation of EELs and thus address KI#12. The EES 121 may be able to distinguish between different UEs and apply different policies to the UEs based on subscription information. The ECS 103 may be able to identify the EES 121 during the service provisioning procedure based on an EES provider identifier provided by the EEC so as to provide the correct EES with the corresponding edge subscription data for the UE 101.

[0080] 3 is a schematic flowchart illustrating an example method 300 in a UE 101 according to an embodiment of the present specification. In one embodiment, the flowchart of FIG. 3 may be implemented in a functional component that implements an enabler function (such as the EEC 111) of FIGS. 1, 2A, and 2B.

[0081] The method 300 may begin at step S301, in which a functional component (such as the EEC 111) may send a first message to a first network function (such as the ECS 103) that implements ECS to request service provisioning. The first message may include a first parameter indicating one or more edge service providers. That is, the UE 101 that implements an enabling function may send the first message to the ECS 103 to request service provisioning.

[0082] In one embodiment, the first parameter may include one or more EES provider identifiers. In one embodiment, the one or more EES provider identifiers may indicate a list of preferred EES providers. That is, the first message may include one or more EES provider identifiers that identify one or more desired (or preferred) EES providers. The one or more EES provider identifiers may correspond to a list of desired EES provider identifiers, and the list may include at least one desired EES provider identifier, as shown in Table 1.

[0083] In one embodiment, the first message may be a service provisioning request message over the EDGE-4 reference point. In another embodiment, the first message may be a service provisioning subscription request message over the EDGE-4 reference point.

[0084] The method 300 may then proceed to step S302, in which the functional component (e.g., EEC 111) may receive a second message from the first network function (e.g., ECS 103) including a second parameter indicating one or more second network functions that implement the EES. That is, the UE 101 may receive the second message indicating the one or more EES. Optionally, the one or more EESs are configured with edge subscription data for the UE 101. The one or more second network functions may be provided by at least one of one or more edge service providers. In other words, the one or more EESs may be determined based on one or more EES provider identifiers that identify the one or more edge service providers.

[0085] In one embodiment, the second parameters may include one or more endpoints of each of the one or more second network functions, i.e., the one or more EESs may be indicated by the respective one or more EES endpoints.

[0086] In one embodiment, the second message may be a Service Provisioning Response message over the EDGE-4 reference point. In another embodiment, the second message may be a Service Provisioning Notification message over the EDGE-4 reference point.

[0087] The method 300 may then proceed to optional step S303, in which a functional component (e.g., EEC111) may select a second network function from one or more second network functions to provide differentiated services to the UE 101 according to the edge subscription data.

[0088] In one embodiment, the edge subscription data may be stored in a selected second network function.

[0089] In one embodiment, the edge subscription data may include a UE ID of the UE.

[0090] In one embodiment, the edge subscription data may include at least one of an edge service level or a service policy.

[0091] The above steps are merely exemplary, and the functional components may perform any associated operations described with respect to Figures 1, 2A, and 2B.

[0092] 4 is a schematic flowchart illustrating an exemplary method 400 in a first network function according to an embodiment of the present disclosure. In one embodiment, the flowchart of FIG. 4 may be implemented in the ECS 103 of FIGS. 1, 2A, and 2B.

[0093] The method 400 may begin at step S401, in which a first network function (e.g., ECS 103) may receive a first message for requesting service provisioning from a UE 101 that includes a functional component (e.g., EEC 111) that implements an enabler function. The first message may include a first parameter indicating one or more edge service providers, i.e., EES providers. Optionally, as shown in Table 1, the first message may include one or more EES provider identifiers that identify one or more desired EES providers.

[0094] In one embodiment, the first parameter may include one or more EES provider identifiers. In one embodiment, the one or more EES provider identifiers may indicate a list of preferred EES providers. As shown in Table 1, the one or more EES provider identifiers may correspond to a list of preferred EES provider identifiers, and the list may include at least one preferred EES provider identifier.

[0095] In one embodiment, the first message may be a service provisioning request message over the EDGE-4 reference point. In another embodiment, the first message may be a service provisioning subscription request message over the EDGE-4 reference point.

[0096] Method 400 may then proceed to step S402, in which the first network function (e.g., ECS 103) may send a second message to UE 101 including a second parameter indicating one or more second network functions that implement EES. As described above, ECS 103 may consider one or more EES provider identifiers included in the first message when determining the one or more EESs and indicate the one or more EESs to UE 101 in the second message. The one or more EESs may be configured with edge subscription data for the UE. The one or more second network functions may be provided by at least one of one or more edge service providers identified by the desired EES provider identifiers in the first message.

[0097] In one embodiment, the second parameters may include one or more endpoints of each of the one or more second network functions, i.e., one or more EESs may be indicated by one or more endpoints of each of the one or more EESs.

[0098] In one embodiment, the second message may be a Service Provisioning Response message over the EDGE-4 reference point. In another embodiment, the second message may be a Service Provisioning Notification message over the EDGE-4 reference point.

[0099] The above steps are merely exemplary, and the first network function may perform any of the associated operations described with respect to Figures 1, 2A, and 2B.

[0100] 5 is a schematic block diagram illustrating an example UE 500 according to an embodiment of the present specification. In one embodiment, the example UE 500 of FIG. 5 may be implemented as the UE 101 of FIG. 1, FIG. 2A, and FIG. 2B.

[0101] In one embodiment, the UE 500 may include at least one processor 501 and a non-transitory computer-readable medium 502 coupled to the at least one processor 501. The non-transitory computer-readable medium 502 may store instructions executable by the at least one processor 501, such that the at least one processor 501 may be configured to perform steps in the exemplary method 300 shown in the schematic flowchart of Figure 3, the details of which will be omitted herein.

[0102] It should be noted that the UE 500 may be implemented as hardware, software, firmware, and any combination thereof. For example, the UE 500 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of the example method 300 or one or more steps illustrated in Figures 1, 2A, and 2B associated with the UE 101 and its functional components (e.g., the EEC 111 and / or the AC 112).

[0103] 6 is a schematic block diagram illustrating an example network function 600 according to an embodiment of the present disclosure. In one embodiment, the example network function 600 of FIG. 6 may be implemented as the ECS 103 of FIGS. 1, 2A, and 2B.

[0104] In one embodiment, the network function 600 may include at least one processor 601 and a non-transitory computer-readable medium 602 coupled to the at least one processor 601. The non-transitory computer-readable medium 602 may store instructions executable by the at least one processor 601, such that the at least one processor 601 may be configured to perform steps in the exemplary method 400 shown in the schematic flowchart of Figure 4, details of which will be omitted herein.

[0105] It should be noted that network function 600 may be implemented as hardware, software, firmware, and any combination thereof. For example, network function 600 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of example method 400 or one or more steps shown in Figures 1, 2A, and 2B associated with the first network function (e.g., ECS 103).

[0106] 7 is a schematic block diagram illustrating an example computer-implemented apparatus 700 according to embodiments herein. In one embodiment, the apparatus 700 may be configured as the above-mentioned apparatus, such as the UE 101 or its functional components (such as the EEC 111 and / or AC 112), the first network function (such as the ECS 103), or the second network function (such as the EES 121).

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

[0108] In one embodiment, computer-readable medium 702 (such as a non-transitory computer-readable medium) may be stored in memory 703. In another embodiment, the computer program may be stored at a remote location, e.g., in computer program product 704 (which may also be embodied as a computer-readable medium), and accessible by processor 701, e.g., via carrier 705.

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

[0110] Additionally, we propose the following amendments to amend the current 3GPP Technical Report 3GPP TR23.700-98V1.2.0(2022-09):

[0111] Title: EEL's Service Differentiation Introduction: This contribution proposes a novel solution to support EEL's service differentiation.

[0112] Reason for change: Agreed to consider the following key issues:

[0113] 4.12 Key Issue #12: EEL Service Differentiation Service differentiation in Rel-17 is quite general and not detailed (e.g., ECS uses local policies to determine service provisioning). Details should be specified to allow ECSPs to offer different service quality levels, such as principles based on the role of the service consumer. For example, premium users should get the closest available edge, or there should be certain applications available only to premium users.

[0114] Open issues: - What service differentiation should EEL enable? -What procedures should be strengthened to support service differentiation? - Which functional entity is responsible for defining or managing service differentiation?

[0115] Proposed changes: ***First Change*** (including the following content added to 3GPP TR23.700-98V1.2.0(2022-09))

[0116] 7.x Solution #X3: EES Policy Differentiation 7.x.1 Architecture Enhancements none. 7.x.2 Solution Description

[0117] For edge service differentiation, UE profiles and policies can be managed by the EES, and Table 7.x.2-1 gives an example of information provisioned to the UE. TIFF2025533611000004.tif49170

[0118] For example, after receiving an EAS discovery request, the EES obtains edge subscription data about the UE. Then, the EES operates differently in provisioning EAS candidates to a service consumer (e.g., an EEC) based on the edge subscription data about the UE. For example, a policy can be the maximum number of edge computing applications, e.g., the EES can only support up to five applications for a free UE. Another example is the temporal and spatial conditions for providing edge services, such as EAS discovery under different edge service levels. More detailed edge subscription data is specific to the implementation of the EES and is outside the scope of this discussion.

[0119] Because this is a contractual subscription with an EES provider and an ECS may host multiple EESs provided by different ECSPs, the EEC needs to contact the EES provided by the EES service provider that holds the UE's valid edge subscription data. This requires the EEC to provide its desired EES service provider in the service provisioning procedure, as shown in Figure 2A. With such information, the ECS can provision the EES to the EEC based on the EES registered provider information.

[0120] Figure 2A: Service Provisioning - Request / Response

[0121] Table 7.x.2-1 shows the additional impact on the information flow of a service provisioning request. TIFF2025533611000005.tif142170

[0122] The EES provider identifier is also applicable to the subscribe-notify model of the service provisioning procedure (ie, included in the service provisioning subscription request).

[0123] 7.x.3 Solution Evaluation This solution addresses KI#12, which enables service differentiation for EES. The EES can distinguish between different UEs and apply different policies to the UEs based on their subscription information. To address the correct EES with the corresponding edge subscription data for the UE, the ECS can identify the EES during the service provisioning procedure based on the EES provider identifier provided by the EEC. ***END OF CHANGE***

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

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

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

[0127] Numerous variations and modifications can be made to the embodiments without substantially departing from the principles of the inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the subject matter disclosed above should be considered illustrative and not limiting, and the accompanying examples of embodiments are intended to cover all such modifications, extensions, and other embodiments that fall within the spirit and scope of the inventive concept. Therefore, to the fullest extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of this disclosure, including subsequent examples of embodiments and their equivalents, and should not be limited or constrained by the above detailed description.

[0128] Abbreviation 3GPP 3rd Generation Partnership Project AC Application Client API Application Programming Interface EAS Edge Application Server ECS Edge Configuration Server ECSP Edge Computing Service Provider EDGEAPP: An architecture that enables edge applications EDN Edge Data Network EEC Edge Enabler Client EEL Edge Enabler Layer EES Edge Enabler Server IoT Internet of Things OTT Over-the-top SA Service and System Aspects UE User Equipment

Claims

1. A method (300) performed by a user equipment (UE) (101) implementing an enabler function, comprising: Sending a first message to an Edge Configuration Server (ECS) (103) to request service provisioning (S301), the first message including one or more Edge Enabler Server (EES) provider identifiers identifying one or more desired EES providers; receiving a second message from the ECS (103) indicating one or more EESs (121); The method (300).

2. The method (300) of claim 1, wherein the one or more EESs (121) are determined based on the one or more EES provider identifiers.

3. 3. The method (300) of claim 1 or 2, wherein the one or more EES provider identifiers correspond to a list of desired EES provider identifiers, the list including at least one desired EES provider identifier.

4. The method (300) of any one of claims 1 to 3, wherein the one or more EESs (121) are configured with edge subscription data of the UE (101).

5. The method (300) of any one of claims 1 to 4, wherein the one or more EESs (121) are represented by one or more endpoints of each of the one or more EESs (121).

6. selecting an EES (121) from the one or more EESs (121) to provide differentiated services to the UE (101) according to configured edge subscription data for the UE (101) (S303); The method (300) of any one of claims 1 to 5, further comprising:

7. The edge subscription data is stored in the selected EES (121); The edge subscription data includes a UE ID of the UE (101); or 7. The method (300) of claim 6, wherein the edge subscription data includes at least one of an edge service level or a service policy.

8. the first message is a service provisioning request message over an EDGE-4 reference point; the second message is a Service Provisioning Response message over an EDGE-4 reference point; the first message is a service provisioning subscription request message over an EDGE-4 reference point; or The method (300) of any one of claims 1 to 7, wherein the second message is a service provisioning notification message over an EDGE-4 reference point.

9. A method (400) performed by an Edge Configuration Server (ECS) (103), comprising: Receiving (S401) a first message for requesting service provisioning from a user equipment (UE) (101) implementing an enabler function, the first message including one or more Edge Enabler Server (EES) provider identifiers identifying one or more desired EES providers; sending a second message to the UE (101) indicating one or more EESs (121) taking into account the one or more EES provider identifiers included in the first message (S402); The method (400) includes:

10. 10. The method (400) of claim 9, wherein the one or more EES provider identifiers correspond to a list of desired EES provider identifiers, the list including at least one desired EES provider identifier.

11. 11. The method (400) of claim 9 or 10, wherein the one or more EESs (121) are represented by one or more endpoints of each of the one or more EESs (121).

12. The method (400) of any one of claims 9 to 11, wherein the one or more EESs (121) are configured with edge subscription data of the UE (101).

13. the first message is a service provisioning request message over an EDGE-4 reference point; the second message is a Service Provisioning Response message over an EDGE-4 reference point; the first message is a service provisioning subscription request message over an EDGE-4 reference point; or The method (400) of any one of claims 9 to 12, wherein the second message is a service provisioning notification message over an EDGE-4 reference point.

14. A user equipment (UE) (101, 500), At least one processor (501); a non-transitory computer-readable medium (502) coupled to the at least one processor (501); wherein the non-transitory computer-readable medium (502) includes instructions executable by the at least one processor (501), whereby the at least one processor (501) is configured to perform the method (300) of any one of claims 1 to 8. User Equipment (UE) (101, 500).

15. A network function (103, 600) implementing an Edge Configuration Server (ECS), comprising: At least one processor (601); a non-transitory computer-readable medium (602) coupled to the at least one processor (601); wherein the non-transitory computer-readable medium (602) includes instructions executable by the at least one processor (601), whereby the at least one processor (601) is configured to perform the method (400) of any one of claims 9 to 13. Network functions (103, 600).

16. A computer-readable medium (502, 602, 702) comprising computer-readable code that, when run on a device (101, 103, 500, 600, 700), causes the device (101, 103, 500, 600, 700) to perform a method (300, 400) according to any one of claims 1 to 13.

17. A computer program product (704) comprising computer readable code that, when run on a device (101, 103, 500, 600, 700), causes the device (101, 103, 500, 600, 700) to perform a method (300, 400) according to any one of claims 1 to 13.

Images