Edge configuration server (ECS) and method thereof

Abstract

To provide a technique for determination of one or more preferred edge servers for an Edge Enabler Client (EEC).SOLUTION: An Edge Configuration Server (ECS) receives a Service provisioning request from the EEC, which includes the Application Client profile (AC profile) information. The ECS uses the Geographical service area information to determine or identify an Edge Enabler Server (EES) and returns a Service provisioning response to the EEC, which includes information related to the EES.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present disclosure relates to wireless communication networks, and more particularly to an apparatus and method for edge computing. [Background technology]

[0002] Edge computing aims to move applications, data, and computing power (services) from centralized points (e.g., centralized data centers) to locations closer to users (e.g., distributed data centers). The European Telecommunications Standards Institute (ETSI) Industry Specification Group called Multi-access Edge Computing (MEC) is standardizing application platforms and APIs for edge computing. For example, MEC offers application developers and content providers a cloud computing capabilities and information technology (IT) services environment in the Radio Access Network (RAN) in close proximity to mobile subscribers. This environment provides ultra-low latency and high bandwidth, as well as direct access to radio network information generation (e.g., subscriber location and cell load) that can be leveraged by applications and services.

[0003] The Third Generation Partnership Project (3GPP (registered trademark)) SA6 working group has started standardization work on an architecture for enabling Edge Applications (see, for example, Non-Patent Document 1). This architecture of 3GPP is called the EDGEAPP architecture. The EDGEAPP architecture provides a specification of an enabling layer to facilitate communication between application clients (ACs) running on a User Equipment (UE) and applications deployed at an edge. According to the EDGEAPP architecture, edge applications provided by Edge Application Servers (EASs) are provided to the ACs of a UE by an Edge Configuration Server (ECS) and an Edge Enabler Server (EES) via an Edge Enabler Client (EEC) of the UE.

[0004] An AC running on a UE needs to discover server applications (i.e., EAS in 3GPP SA6 terminology, or MEC application in ETSI ISG MEC terminology) on the edge cloud. For server application discovery, the AC can use another client on the UE, i.e., EEC. The EEC provides the ACs with discovery of available EASs in the edge data network.

[0005] A UE is initially provisioned with the necessary information to connect to an Edge Data Network (EDN) from the ECS. The EDN includes one or more EESs and one or more EASs. More specifically, the EEC of the UE communicates with the ECS for service provisioning. Service provisioning allows the EEC to configure information about available edge computing services based on the UE location, service requirements, service performances, and connectivity. The configuration includes address information required for the EEC to establish a connection with one or more EESs located in the EDN. The ECS identifies (or selects, or determines) one or more EESs based on the UE location and, for example, based on one or more Application Client profiles provided by the EEC.

[0006] For this service provisioning, the EEC makes a service provisioning request to the ECS to request resources for the service provisioning in the EDN, and connection or configuration information, including, for example, information about available edge computing services, information about servers in the EDN, their identifiers (IDs) and address information (e.g., Internet Protocol (IP) addresses, Single-Network Slice Selection Assistance Information (S-NSSAI), and service area information), EDN configuration information, and configuration information about the Edge Data Network to which the EEC will establish a connection.

[0007] Next, the EEC communicates with the EES and performs EAS discovery for the AC. EAS discovery enables the EEC to obtain information about available EASs of interest for the AC (EAS information). The EES identifies (or selects, or determines, or discovers) one or more EASs based on the UE location and, for example, based on EAS discovery filters provided by the EEC. For EAS discovery, the EEC makes an EAS discovery request to the EES to request information about the equipment, connections, or settings required to provide the service in the EDN. Such information includes, for example, information about available edge computing services and information about servers in the EDN.

[0008] Hereinafter, an entity that issues a service provisioning request and / or an EAS discovery request will be collectively referred to as a request entity. A service provisioning request and an EAS discovery request will be collectively referred to simply as a request. [Prior art documents] [Non-patent literature]

[0009] [Non-Patent Document 1] 3GPP TS 23.558 V1.2.0 (2020-11) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture for enabling Edge Applications; (Release 17)", November 2020 Summary of the Invention [Problem to be solved by the invention]

[0010] As described above, in the 3GPP EDGEAPP architecture, a server (hereinafter referred to as an edge server) located in an edge data network includes one or more EESs and one or more EASs. If the UE cannot obtain information of a preferred or suitable edge server through an enabling layer, the UE cannot use the edge application. More specifically, if the ECS cannot identify (or discover) a suitable EES for the AC, the AC cannot use the edge application. Alternatively, if the ECS can discover the EES(s) but the EES cannot identify (or discover) a suitable EAS for the AC, the AC cannot use the edge application.

[0011] These impacts may be more severe when edge application mobility (or application context relocation) for service continuity is required. Edge application mobility relocates application context or application instance or both for a user (i.e., AC) from a source EAS (or EDN or LADN) to a target EAS (or EDN or LADN). Edge application mobility is triggered by UE mobility events or non-UE mobility events. UE mobility events include, for example, intra-EDN UE mobility, inter-EDN UE mobility, and Local Area Data Network (LADN)-related UE mobility. Non-UE mobility events include, for example, EAS or EDN overload conditions, and EAS maintenance (e.g., graceful shutdown of the EAS).

[0012] One of the objectives that the embodiments disclosed in this specification aim to achieve is to provide an apparatus, a method, and a program that contribute to mitigating the impact of failure to discover one or more edge servers preferred for a UE. It should be noted that this objective is only one of the objectives that the embodiments disclosed in this specification aim to achieve. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]

[0013] In a first aspect, a first server includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to, in response to receiving a request from a requesting entity for connection to an entity providing a service in an edge data network, attempt to identify a second server located within the edge data network based on at least one selection criterion. If the at least one processor cannot identify the second server or is unavailable, identify a second alternative server different from the second server or identify a first alternative server that attempts to identify the second server in place of the first server.

[0014] In a second aspect, a method performed by a first server includes the steps of: (a) in response to receiving a request from a requesting entity for a connection to an entity providing a service in an edge data network, attempting to identify a second server located within the edge data network based on at least one selection criterion; and (b) if the second server cannot be identified or is unavailable, identifying a second alternative server different from the second server, or identifying a first alternative server that attempts to identify the second server on behalf of the first server.

[0015] In a third aspect, the requesting entity includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to send a request for connection to an entity providing a service in an edge data network to a first server and receive a response to the request from the first server. The at least one processor is configured to, if a second server located in the edge data network that is attempted to be identified based on at least one selection criterion is not identified, determine whether to accept the information of the first alternative server or the information of the second alternative server for providing the service if the response includes information of a second alternative server different from the second server or information of a first alternative server that attempts to identify the second server instead of the first server, when the second server located in the edge data network that is attempted to be identified based on at least one selection criterion is not identified.

[0016] In a fourth aspect, a method performed by a requesting entity includes the steps of: (a) sending a request to a first server for a connection to an entity providing a service in an edge data network; (b) receiving a response to the request from the first server; and (c) if a second server located within the edge data network that is attempted to be identified based on at least one selection criterion is not identified, and the response includes information of a second alternative server different from the second server or information of a first alternative server that attempts to identify the second server on behalf of the first server, determining whether to accept the information of the first alternative server or the information of the second alternative server for providing the service.

[0017] In a fifth aspect, a program includes a set of instructions (software code) for causing a computer to carry out the method according to the second or fourth aspect above when the program is loaded into the computer. Effect of the Invention

[0018] According to the above aspects, an apparatus, method, and program can be provided that contribute to mitigating the impact of failing to find one or more edge servers preferred for a UE. [Brief description of the drawings]

[0019] [Figure 1] FIG. 1 is a diagram illustrating an example of a network architecture according to an embodiment. [Diagram 2] 6 is a flowchart showing an example of an operation of the first server according to the embodiment. [Diagram 3] 11 is a flowchart illustrating an example of an operation of a request entity according to an embodiment. [Figure 4] 1 is a sequence diagram showing an example of the operation of an EEC and an ECS according to an embodiment. [Diagram 5] A sequence diagram showing an example of the operation of the EEC and EES according to the embodiment. [Figure 6] A sequence diagram showing an example of the operation of a source EES (S-EES) and an ECS according to an embodiment. [Figure 7] A sequence diagram showing an example of the operation of a source EES (S-EES) and a target EES (T-EES) according to an embodiment. [Figure 8] 6 is a flowchart showing an example of an operation of the first server according to the embodiment. [Figure 9] A sequence diagram showing an example of the operation of the EEC, ECS, and EES according to the embodiment. [Figure 10] FIG. 11 is a sequence diagram showing an example of the operation of the EEC, ECS, and EES according to the embodiment. [Figure 11] FIG. 2 is a block diagram showing an example of the configuration of a UE according to the embodiment. [Figure 12] FIG. 2 is a block diagram showing an example of the configuration of a server according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] In the following, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and duplicated descriptions will be omitted as necessary for clarity of explanation.

[0021] The multiple embodiments described below can be implemented independently or in appropriate combination. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different objects or problems and provide different effects.

[0022] The following embodiments will be described with a focus on a 3GPP system (eg, a 5G system (5GS)). However, these embodiments may be applied to other wireless communication systems.

[0023] <First embodiment> FIG. 1 shows an example of the architecture of a network according to the present embodiment. The architecture of FIG. 1 corresponds to the 3GPP EDGEAPP architecture. Each of the elements shown in FIG. 1 is a functional entity, providing functions and interfaces defined by 3GPP. Each of the elements (functional entities) shown in FIG. 1 can be implemented, for example, as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an application platform.

[0024] In the example of FIG. 1, User Equipment (UE) 1 includes an Edge Enabler Client (EEC) 2 and one or more Application Clients (ACs) 3. In other words, the EEC 2 and one or more ACs 3 are arranged in the UE 1 and operate on the UE 1. Although not explicitly shown in FIG. 1, the UE 1 communicates with a 3GPP core network 8 (eg, 5G Core (5GC)) via an access network (eg, Radio Access Network (eg, NG Radio Access Network (NG-RAN)). This allows the UE 1 to provide connectivity to a data network via the access network and the 3GPP core network 8 to the EEC 2 and AC(s) 3.

[0025] The EEC2 provides supporting functions required by the AC(s) 3. Specifically, the EEC2 provides provisioning of configuration information to enable exchange of application data traffic with an Edge Application Server (EAS). Furthermore, the EEC2 provides functionality for discovery of one or more EASs available in the Edge Data Network (EDN) 4. The EEC2 uses the EAS endpoint information obtained during EAS discovery for routing outgoing application data traffic to the EAS. Furthermore, the EEC2 provides functionality for registration (i.e., registration, update, and de-registration) of the EES 5 and EAS(s) 6.

[0026] Each AC3 is an application running on a UE1. Each AC3 connects to one or more EASs to utilize edge computing services and exchanges application data traffic with these EASs.

[0027] An Edge Data Network (EDN) 4 includes one or more Edge Enabler Servers (EES) 5 and one or more Edge Application Servers (EASs) 6. The EDN 4 may be a Local Area Data Network (LADN). The LADN allows limited access to a DN (and corresponding Data Network Name (DNN)) only in one or more specific areas. Outside the area, the UE 1 cannot access the DN (and DNN). The area in which the LADN DNN is available is called the LADN service area and is configured in the network as a set of Tracking Areas (TAs). DNNs that do not use the LADN feature do not have a LADN service area and are not restricted by the feature. The LADN service area is provided to the UE 1 by the Access and Mobility Management Function (AMF) in the 3GPP core network 8 when the UE 1 registers. This allows the UE 1 to know the area in which the LADN (or EDN) is available and not to try to access the LADN (or EDN) outside this area.

[0028] Each EES5 provides supporting functions required by the EAS(s)6 and EEC2. In particular, each EES5 provides the provisioning of configuration information to the EEC2, thereby enabling the exchange of application data traffic with the EAS(s)6. Each EES5 provides the functionality of registration (i.e., registration, update, and de-registration) with the EEC2 and EAS(s)6. Each EES5 provides the functionality of application context transfer between EESs. This functionality is required for edge application mobility (or application context relocation) for service continuity. Edge application mobility relocates application context and / or application instance for a user (i.e., AC) from a source EAS (or EDN or LADN) to a target EAS (or EDN or LADN). Edge application mobility can be triggered by UE mobility events or non-UE mobility events. UE mobility events include, for example, intra-EDN UE mobility, inter-EDN UE mobility, and LADn-related UE mobility. Non-UE mobility events include, for example, EAS or EDN overload conditions, and EAS maintenance (e.g., graceful shutdown of the EAS).

[0029] Additionally, each EES 5 supports the functionality of an Application Programming Interface (API) invoker and an API exposing function. Each EES 5 may interact directly (e.g., via a Policy Control Function (PCF)) or indirectly (e.g., via a Network Exposure Function (NEF) or Service Capability Exposure Function (SCEF)) with the 3GPP core network 8 to access the services and capabilities of network functions within the 3GPP core network 8. Each EES 5 may support external exposure of the services and capabilities of the 3GPP network functions to the EAS(s) 6.

[0030] Each EAS 6 is located in the EDN 4 and executes a server function of an application. The server function of the application may be available only at the edge. In other words, the server function of the application may be available only as an EAS. However, the server function of the application may be available both at the edge and in the cloud. In other words, the server function of the application may be available as an EAS and also as an application server in the cloud. The cloud here means a central cloud located farther from the UE 1 than the EDN 4. Thus, the application server in the cloud means a server located in a centralized location (e.g., a centralized data center). Each EAS 6 may consume or use 3GPP core network capabilities. Each EAS 6 may directly invoke a 3GPP core network function API. Alternatively, each EAS 6 may consume or use 3GPP core network capabilities via the EES 5 or via the NEF or SCEF.

[0031] The Edge Configuration Server (ECS) 7 provides supporting functions required by the EEC2 to connect to the EES(s) 5. Specifically, the ECS 7 provides provisioning of edge configuration information to the EEC2. The edge configuration information includes information for the EEC2 to connect to the EES(s) 5 (e.g., service area information applicable to the LADN) and information for establishing a connection with the EES(s) 5 (e.g., Uniform Resource Identifier (URI)). The ECS 7 provides functions for registration, update, and de-registration of the EES(s) 5. Additionally, the ECS 7 supports functions of an API invoker and an API exposing function. The ECS 7 may interact directly (e.g., via the PCF) or indirectly (e.g., via the NEF or SCEF) with the 3GPP core network 8 to access services and capabilities of network functions in the 3GPP core network 8. The ECS 7 may be located within the domain of a Mobile Network Operator (MNO) providing a 3GPP core network 8, or may be located in a third-party domain of a service provider (eg, an Edge Computing Service Provider (ECSP)).

[0032] 1 shows only representative elements for ease of explanation. For example, ECS 7 may be connected to multiple EDNs including EDN 4.

[0033] FIG. 2 is a flowchart showing an example of the operation of the first server according to the present embodiment. The first server attempts to identify (discover, select, or determine) a preferred or appropriate edge server located in the EDN4. In one example, the first server may be an ECS7 and may attempt to identify one or more EESs in response to a request from an EEC2 of the UE1. Alternatively, the first server may be an ECS7 and may attempt to identify a target EES (T-EES) in response to a request from a source EES (S-EES) during edge application mobility (or application context relocation). In another example, the first server may be an EES5 and may attempt to identify one or more EASs in response to a request from an EEC2 of the UE1. Alternatively, the first server may be an EES5 (T-EES) and may attempt to identify a target EAS (T-EAS) in response to a request from an S-EES during edge application mobility (or application context relocation).

[0034] In step 201, the first server receives a request from a requesting entity. The requesting entity may be a functional entity. In the case where the first server is an ECS7, the requesting entity may be an EEC2 or an S-EES (eg, EES5) in edge application mobility. In the case where the first server is an EES5, the requesting entity may be an EEC2 or an S-EES in edge application mobility. The request requests a connection to an entity that provides a service in an edge data network. The request may be a service provisioning request or an EAS discovery request. The request may be an EEC registration request or an EEC registration update request.

[0035] In step 202, in response to receiving the request, the first server attempts to identify a second server located in the EDN4 and that satisfies at least one selection criterion. Note that in the case of the selection (or determination, or discovery, or identification) of the EES(s) by the ECS7, the second server is an EES. Furthermore, in this case, at least one factor considered in the at least one selection criterion may include at least one of the location of the UE1, at least one Application Client profile provided by the EEC2, the operation status of the second server (i.e., EES), or the load status of the second server (i.e., EES). The ECS7 may identify the EES(s) that matches the provided Application Client profile. If multiple Application Client profiles are provided, the ECS7 may identify the EES(s) that matches all the Application Client profiles. Alternatively, the ECS7 may identify the EES(s) that matches at least one of the provided Application Client profiles.

[0036] On the other hand, in the case of the selection (or determination, or discovery, or identification) of the EAS(s) by the EES5, the second server is the EAS. Furthermore, in this case, at least one factor taken into account in the at least one selection criterion may include at least one of the location of the UE1, the EAS discovery filters provided by the EEC2, the operation status of the second server (i.e., EAS), or the load status of the second server (i.e., EAS). The List of Application Client characteristics included in the EAS discovery filters may indicate multiple Application Clients (i.e., multiple Application Client Profiles). In this case, the EES5 may identify the EAS(s) that match all the Application Client profiles. Alternatively, the EES5 may identify the EAS(s) that match at least one of the provided Application Client profiles. Additionally or alternatively, the List of Edge Application Server characteristics included in the EAS discovery filters may indicate multiple items. Each item on the list describes a set of one or more characteristics (e.g., any combination of EAS type, EAS schedule, EAS Geographical Service Area, EAS Topological Service Area, Service continuity support, and EAS status). The EES5 may identify EAS(s) that match all items on the list. Alternatively, the ECS7 may identify EES(s) that match at least one item on the list.

[0037] Upon successfully identifying a preferred or suitable second server that meets the selection criteria (YES in step 203), the procedure proceeds to step 204. In step 204, the first server (i.e., ECS7 or EES5) sends information of the identified second server (e.g., EES, EAS, T-EES, or T-EAS) to the requesting entity (i.e., EEC2 or S-EES).

[0038] On the other hand, in response to failing to identify a preferred or suitable second server that satisfies the selection criteria (NO in step 203), the procedure proceeds to step 205. In step 205, the first server (i.e., ECS7 or EES5) transmits information of an alternative server (e.g., EES, EAS, T-EES, or T-EAS) instead of the second server to the requesting entity (i.e., EEC2 or S-EES). Note that the information of the alternative server may be transmitted by being included in the information of the edge data network. Specifically, if an alternative server (or configuration information of the alternative server) is available, the first server may transmit the (configuration) information of the alternative server to the requesting entity. The alternative server (i.e., alternative EES or alternative EAS) may be referred to as a default server, a central server, or a centralized server.

[0039] The first server may transmit an identifier explicitly indicating that it is an alternative server to the requesting entity in association with the alternative server information. The requesting entity may recognize that the received server information is information of an alternative server based on the identifier. Alternatively, the requesting entity may recognize that the received server information is an alternative server when the EAS information (including characteristics of EASs, which will be described later) included in the EAS discovery filters included in the request to the first server is not included in the response to the request. The alternative server information may also include a criterion that the alternative server is unable to satisfy among at least one selection criterion for identifying the second server. The alternative server information may also include a criterion that the alternative server satisfies among at least one selection criterion for identifying the second server.

[0040] The information on the alternative server may be set (or provided) in advance to the first server. Alternatively, the first server (e.g., EES5) may dynamically or periodically obtain the information on the alternative server from the ECS7.

[0041] The alternative server may be a server that cannot fulfill some or all of at least one selection criteria for identifying the second server. For example, in case of selection (or determination, or discovery, or identification) of EES(s), if the first server (i.e., ECS7) cannot identify an EES that completely matches the Application Client profile provided by EEC2, the first server (i.e., ECS7) may respond to the request of EEC2 with information of the alternative EES. The Application Client profile may include, for example, at least one of "Application Client Schedule", "Expected Application Client Geographical Service Area", "Service Continuity Support", or "List of EASs". The Application Client Schedule indicates an expected operation schedule of AC3, e.g., a time window. The Expected Application Client Geographical Service Area indicates an expected location(s) of UE1 during the expected operation schedule of AC3, e.g., a route. The Service Continuity Support indicates whether service continuity support is required for AC3. The List of EASs includes an EAS ID and may further include Application Client Service Key Performance Indicators (KPIs). The Application Client Service KPIs indicate the service characteristics required by AC3.These service characteristics include at least one of, for example, connection bandwidth, maximum request rate to be generated by the AC, maximum response time, maximum compute resources required by the AC, maximum memory resources required by the AC, or information specific to the AC type (e.g., video, Virtual Reality (VR), etc.). The alternative EES may be an EES that cannot satisfy some or all of these service characteristics required in the Application Client profile. In other words, the alternative EES may be an EES that cannot provide the EEC2 with a connection to an EAS that satisfies all the service characteristics required in the Application Client profile. In other words, the alternative EES may be an EES that can provide the EEC2 with only a connection to an EAS(s) that cannot satisfy some or all of the service characteristics required in the Application Client profile. Note that the response to the request of the EEC2 mentioned above means a response in a service provisioning procedure based on a Request / Response model, but in a service provisioning procedure based on a Subscribe-Notify model, instead of a response to the request, the first server notifies the EEC2 of information on the alternative EES.

[0042] On the other hand, in case of EAS(s) selection (or determination, or discovery, or identification), if the first server (i.e., EES5) is unable to identify an EAS that fully matches the EAS discovery filters provided by the EEC2, the first server (i.e., EES5) may respond to the EEC2 request with information of alternative EASs. The EAS discovery filters indicate a set of characteristics required to determine the requested EAS. For example, the EAS discovery filters may include the Application Client profile described above. Additionally or alternatively, the EAS discovery filters may indicate characteristics of one or more requested EASs. Each required EAS characteristic may include, for example, at least one of EAS ID, EAS provider identifier, category or type of the EAS, required availability schedule of the EAS, location(s) (e.g. geographical area, route) where the EAS service should be available, or topological area (e.g. cell ID, Tracking Area Identity(TAI)) for which the EAS service should be available. The alternative EAS may be an EAS that cannot satisfy some or all of the characteristics required by the EAS discovery filters. Note that the response to the request of the EEC2 described above means a response in the EAS discovery procedure based on the Request / Response model, but in the EAS discovery procedure based on the Subscribe-Notify model, instead of responding to the request, the first server notifies the EEC2 of information about the alternative EAS.

[0043] Additionally or alternatively, the alternative server may be available as an application server in a cloud. Cloud here means a central cloud located farther from the UE1 than the EDN4 (edge ​​cloud). The alternative server may be a server located in a centralized location (e.g., a centralized data center). The alternative server (i.e., an alternative EES or an alternative EAS) may be an EES or an EAS located in a data network that cannot satisfy some of the service characteristics (e.g., maximum response time) required in the Application Client profile. In some implementations, the second server is a server in the LADN, whereas the alternative server may be a server located in a normal DN that is not the LADN. Alternatively, the alternative server may be a server located in a second LADN that includes a server that does not satisfy at least one of the at least one selection criteria. At least one of the at least one selection criteria may be any of a service area, a geographical area, a route, a topological area, and a maximum response time. Alternatively, the second server may be a server in the first LADN, while the alternate server may be a server located in a second LADN associated with a larger service area than the first LADN.

[0044] 3 is a flowchart showing an example of the operation of the requesting entity according to the present embodiment. In the case of selecting (or determining, or discovering, or identifying) the EES(s), the requesting entity may be the EEC2 or the S-EES (eg, EES5) in edge application mobility. In the case of selecting (or determining, or discovering, or identifying) the EAS(s), the requesting entity may be the EEC2 or the S-EES in edge application mobility.

[0045] In step 301, the requesting entity sends a request to a first server (e.g., ECS 7 or EES 5). The request requests a connection to an entity that provides a service in an edge data network. The request may be a service provisioning request or an EAS discovery request. The request may be an EEC registration request or an EEC registration update request. In step 302, the requesting entity receives a response or notification to the request from the first server (hereinafter, notification and response may be interpreted interchangeably).

[0046] If the response of step 302 includes information of a second server located in EDN4 and satisfying at least one selection criterion, the procedure proceeds to step 304. Alternatively, if the response of step 302 does not include an identifier explicitly indicating that it is an alternative server associated with the information of the second server, the procedure proceeds to step 304. Alternatively, if the response of step 302 includes EAS information included in the EAS discovery filters included in the request to the first server, the procedure proceeds to step 304. In step 304, the requesting entity (e.g., EEC2 or S-EES) uses the received information of the second server (e.g., EES, EAS, T-EES, or T-EAS) for subsequent communication. For example, if the requesting entity is EEC2 in the case of selecting (or determining, or discovering, or identifying) an EES(s), the EEC2 may use the received information of the second server (i.e., EES) in subsequent EAS discovery. Alternatively, if the requesting entity is an EEC2 in case of selecting (or determining, or discovering, or identifying) an EAS(s), the EEC2 may use the received information (eg, endpoint information) of the second server (ie, EES) for routing application data traffic to the EAS.

[0047] On the other hand, if the response of step 302 does not include the second server information but includes the alternative server information instead, the procedure proceeds to step 305. Alternatively, if the response of step 302 includes an identifier that explicitly indicates an alternative server associated with the (second or alternative) server information, the procedure proceeds to step 305. Alternatively, if the response of step 302 does not include EAS information included in the Application Client profile or EAS discovery filters included in the request to the first server, the procedure proceeds to step 305. In step 305, the requesting entity (e.g., EEC2 or S-EES) decides whether to accept the received alternative server information for use in subsequent communications. In this decision, the requesting entity (e.g., EEC2) may take into account service characteristics (e.g., Application Client Service KPIs) requested in the Application Client profile.

[0048] Specifically, the EEC2 may notify the AC3 of the received information on the alternative server. Based on a notification from the AC3 indicating that the alternative server is accepted, the EEC2 may determine that the information on the alternative server is accepted. On the other hand, based on a notification from the AC3 indicating that the alternative server is not accepted, the EEC2 may determine that the information on the alternative server is not accepted. In addition, the EEC2 may take into consideration in the acceptance decision whether an identifier that explicitly indicates that the server is an alternative server is associated with the information on the (second or alternative) server. Specifically, in a case where the EEC2 allows the acceptance of the alternative server, if an identifier that explicitly indicates that the server is an alternative server is associated with the information on the server, the EEC2 may determine that the information on the alternative server is accepted. On the other hand, in a case where the EEC2 does not allow the acceptance of the alternative server, if an identifier that explicitly indicates that the server is an alternative server is associated with the information on the server, the EEC2 may determine that the information on the alternative server is not accepted. In addition, the EEC2 may take into consideration in the acceptance decision whether the EAS information included in the Application Client profile (or EAS discovery filters) included in the request to the first server is included in the response to the request. Specifically, in a case where the EEC2 allows the acceptance of an alternative server, if the EAS information included in the Application Client profile (or EAS discovery filters) included in the request to the first server is not included in the response to the request, the EEC2 may determine that the information of the alternative server is accepted. On the other hand, in a case where the EEC2 does not allow the acceptance of an alternative server, if the EAS information included in the Application Client profile (or EAS discovery filters) included in the request to the first server is not included in the response to the request, the EEC2 may determine that the information of the alternative server is not accepted. Note that the case where the EEC2 allows / does not allow the acceptance of an alternative server may be based on a pre-set local policy, or may be based on receiving alternative server information, or on periodically checking the alternative server allow / does not allow policy of the AC3.

[0049] If the requesting entity is an EEC2 and accepts information of an alternative EES, the requesting entity (EEC2) may operate as follows: When the EEC2 initiates an EAS discovery procedure, the EEC2 does not include information about the EAS in its EAS discovery filters (e.g., List of EASs in Application Client Profile, and List of Edge Application Server characteristics).

[0050] If the requesting entity is EEC2 and does not accept the information of the alternative EES, the requesting entity (EEC2) may act as follows: The EEC2 discards the received information of the alternative EES (configuration information) and aborts the service provisioning procedure. The EEC2 may inform the AC3 of the current status. The EEC2 may map the current status information to AC-specific information (e.g., status). Alternatively, the EEC2 may transparently forward the current status information to the AC3.

[0051] Similarly, if the requesting entity is EEC2 and does not accept the information of the alternative EAS, the requesting entity (EEC2) may behave as follows: The EEC2 discards the received information of the alternative EAS (configuration information) and aborts the EAS discovery procedure. The EEC2 may inform the AC3 of the current status. The EEC2 may map the current status information to AC-specific information (e.g., status). Alternatively, the EEC2 may transparently forward the current status information to the AC3.

[0052] According to the above-mentioned operation of the first server and the requesting entity, when a preferred or suitable second server that meets the selection criteria cannot be identified, discovered, selected, or determined, the first server can provide the requesting entity with information of an alternative server. The requesting entity can decide whether to use the alternative server for subsequent communication. In other words, when a preferred or suitable second server cannot be identified, the first server can propose a work-around (Plan B) to the requesting entity. In this way, although AC3 may not enjoy all of the desired service characteristics, Plan B in which an alternative server is utilized can help ensure the provision of service and ensure service continuity. Thus, the above-mentioned operation of the first server and the requesting entity can mitigate the impact of failing to find one or more edge servers that are preferred for UE1.

[0053] The following provides some concrete examples of implementation of the above-mentioned first server and requesting entity operations with reference to Fig. 4 to Fig. 7. Fig. 4 shows an example of the operations of EEC2 and ECS7 in a service provisioning procedure based on a Request / Response model. EEC2 in Fig. 4 corresponds to the above-mentioned requesting entity, and ECS7 in Fig. 4 corresponds to the above-mentioned first server. In step 401, EEC2 sends a service provisioning request to ECS7.

[0054] In step 402, the ECS 7 attempts to identify at least one EES that satisfies at least one selection criterion. For example, the at least one selection criterion may take into account one or both of the UE location and the at least one Application Client profile provided by the EEC 2 via the request of step 401. Additionally or alternatively, the at least one selection criterion may take into account, for example, one or both of the EES operation status and the EES load status. The at least one selection criterion may take into account other factors, for example, UE-specific service information in the ECS 7, or ECSP policies. As described with reference to FIG. 2 (step 205), the ECS 7 may select an alternative EES if it cannot identify an EES that satisfies the at least one selection criterion.

[0055] In step 403, the ECS 7 responds to the EEC 2 request with a service provisioning response. The response includes EDN configuration information. The EDN configuration information includes, for example, an identification of the EDN 4, service area information (e.g., LADN service area), and information required to establish a connection to the EES (e.g., endpoint information). The information about the EES relates to the determined EES, or an alternative EES. As described with reference to FIG. 3 (step 305), if the response includes information about the alternative EES, the EEC 2 may decide whether to accept the information about the alternative EES for use in subsequent communications.

[0056] The service provisioning procedure shown in Fig. 4 may be modified accordingly. In particular, the service provisioning procedure may follow a Subscribe-Notify model instead of a Request-Response model. The signaling between the EEC2 and the ECS7 shown in Fig. 4 may be performed via a user plane connection (e.g., data radio bearers and one or more user plane tunnels) provided by the 3GPP core network 8 and the access network. Alternatively, the signaling may be performed via a control plane connection provided by the 3GPP core network 8 and the access network. The control plane connection includes a Non-Access Stratum (NAS) signaling connection between the UE1 and a control plane entity (e.g., AMF or Mobility Management Entity (MME)) in the 3GPP core network 8.

[0057] Fig. 5 shows an example of the operation of EEC2 and EES5 in an EAS discovery procedure based on a Request / Response model. EEC2 in Fig. 5 corresponds to the above-mentioned requesting entity, and EES5 in Fig. 5 corresponds to the above-mentioned first server. In step 501, EEC2 sends an Edge Application Server discovery request to EES5.

[0058] In step 502, the EES5 attempts to identify at least one EAS that satisfies at least one selection criterion. For example, the at least one selection criterion considers one or both of the UE location and the EAS discovery filters provided by the EEC2 via the request of step 501. Additionally or alternatively, the at least one selection criterion may consider, for example, one or both of the EAS operation status and the EAS load status. The at least one selection criterion may consider other factors, for example, UE-specific service information in the EES5, or ECSP policies. As described with reference to FIG. 2 (step 205), the EES5 may select an alternative EAS if it cannot identify an EAS that satisfies the at least one selection criterion.

[0059] In step 503, the EES5 responds to the EEC2 request with an Edge Application Server discovery response. The response includes information of the discovered EAS(s). For each discovered EAS, the information includes endpoint information. The information may further include additional information about the matched capabilities, such as service permissions levels, Application Client locations that the Edge Application Servers can support, and KPIs. Alternatively, the response of step 503 may include information of an alternative EAS (e.g., endpoint information). The response of step 503 may include additional information about the partially matched capabilities, such as service permissions levels, Application Client locations that the Edge Application Servers can support, and KPIs, in addition to the information of the alternative EAS. If the response includes the information of the alternative EAS, the EEC2 may decide whether to accept the information of the alternative EAS for use in subsequent communication, as described with reference to FIG. 3 (step 305).

[0060] The EAS discovery procedure shown in Fig. 5 may be modified accordingly. In particular, the EAS discovery procedure may follow a Subscribe-Notify model instead of a Request-Response model. The signaling between the EEC2 and the EES5 shown in Fig. 5 may be performed via a user plane connection (e.g., data radio bearers and one or more user plane tunnels) provided by the 3GPP core network 8 and the access network. Alternatively, the signaling may be performed via a control plane connection provided by the 3GPP core network 8 and the access network. The control plane connection includes a NAS signaling connection between the UE1 and a control plane entity (e.g., AMF or MME) in the 3GPP core network 8.

[0061] Figure 6 shows an example of the operation of the source EES (S-EES) 61 and the ECS 7 in the Retrieve Target Edge Enabler Server procedure. The S-EES 61 in Figure 6 corresponds to the requesting entity described above, and the ECS 7 in Figure 6 corresponds to the first server described above. In step 601, the S-EES 61 sends a Retrieve Edge Enabler Server request to the ECS 7.

[0062] In step 602, the ECS 7 attempts to identify at least one target EES (T-EES) that satisfies at least one selection criterion. For example, the at least one selection criterion considers one or both of the UE location and the target DNAI. Additionally or alternatively, the at least one selection criterion may consider, for example, one or both of the EES operation state and the EES load state. The at least one selection criterion may also consider other factors, for example, UE-specific service information in the ECS 7, or ECSP policies. As described with reference to FIG. 2 (step 205), the ECS 7 may select an alternative T-EES if it cannot identify a T-EES that satisfies the at least one selection criterion.

[0063] In step 603, the ECS 7 sends a Retrieve Edge Enabler Server response to the S-EES 61. The response includes a list of the determined T-EES(s) information (e.g., endpoint information). Alternatively, the response may include information of an alternative T-EES (e.g., endpoint information). As described with reference to FIG. 3 (step 305), if the response includes information of the alternative T-EES, the S-EES 61 may decide whether to accept the information of the alternative EES for use in subsequent communications.

[0064] The Retrieve Target Edge Enabler Server procedure shown in Fig. 6 may be modified accordingly. In particular, the Retrieve Target Edge Enabler Server procedure may follow a Subscribe-Notify model instead of a Request-Response model.

[0065] Figure 7 shows an example of the operation of a source EES (S-EES) 71 and a target EAS (T-EES) 72 in a Target EAS discovery procedure during application context relocation determined or triggered by the source EES (S-EES). The S-EES 71 in Figure 7 corresponds to the requesting entity described above, and the T-EES 72 in Figure 7 corresponds to the first server described above. In step 701, the S-EES 71 sends an Edge Application Server discovery request to the T-EES 72.

[0066] In step 702, the T-EES 72 attempts to identify at least one target EAS (T-EAS) that satisfies at least one selection criterion. For example, the at least one selection criterion considers one or both of an EAS discovery filter that matches the EAS profile of the S-EES 71 and a target DNAI. Additionally or alternatively, the at least one selection criterion may consider, for example, one or both of an EAS operation state and an EAS load state. The at least one selection criterion may also consider other factors, for example, UE-specific service information in the T-EES 72, or an ECSP policy. As described with reference to FIG. 2 (step 205), the T-EES 72 may select an alternative T-EAS if it cannot identify a T-EAS that satisfies the at least one selection criterion.

[0067] In step 703, the T-EES 72 responds to the S-EES 71 request with an Edge Application Server discovery response. The response includes information of the discovered T-EAS(s). For each discovered T-EAS, the information includes endpoint information. The information may further include additional information about the matched capabilities, such as service permissions levels, Application Client locations that the Edge Application Servers can support, and KPIs. Alternatively, the response of step 703 may include information of an alternative T-EAS (e.g., endpoint information). The response of step 703 may include additional information about the partially matched capabilities, such as service permissions levels, Application Client locations that the Edge Application Servers can support, and KPIs, in addition to the information of the alternative T-EAS. As described with reference to FIG. 3 (step 305), if the response includes information of the alternative T-EAS, the S-EES 71 may decide whether to accept the information of the alternative T-EAS for use in subsequent communications.

[0068] <Second embodiment> This embodiment provides a variation of the operation of the first server and the requesting entity described in the first embodiment. An example of a network architecture according to this embodiment is similar to the example described with reference to FIG.

[0069] In this embodiment, the requesting entity includes an indication in the request sent to the first server indicating whether the requesting entity desires information of an alternative server, can accept information of an alternative server, or supports the provision of a service using an alternative server (e.g., steps 301, 401, 501, 601, and 701). The requesting entity may decide whether to include the indication in the request based on the Application Client Profile. The first server receives the request including the indication (e.g., steps 201, 401, 501, 601, and 701). The first server then decides whether to send information of an alternative server in the case where the first server cannot identify a preferred second server that meets the selection criteria, taking into account the indication received from the requesting entity (e.g., steps 205, 402, 502, 602, and 702).

[0070] Such operation allows the first server to determine whether to send information of an alternative server based on the needs of the requesting entity.

[0071] <Third embodiment> This embodiment provides a variation of the operation of the first server and the requesting entity described in the first embodiment. An example of a network architecture according to this embodiment is similar to the example described with reference to FIG.

[0072] In one example of the arrangement of the ECS7 and the EES5 in this embodiment, the ECS7 may be arranged in the domain of a Mobile Network Operator (MNO) that provides a 3GPP core network 8, while the EES5 may be arranged in a third-party domain of a service provider (ECSP). In this case, the ECS7 may set EES information in the EEC2 based on the agreement between the MNO and the service provider. In other words, the ECS7 does not necessarily identify (discover, select, or determine) an EES based on the application requirements of the edge service. Therefore, in this embodiment, when the result of verifying the registration request (EEC registration request, EEC registration update request) of the EEC2 is that the source EES (or the EASs registered in the source EES) does not satisfy the verification criteria based on the registration request, the EES5 can perform EES re-allocation to another EES (target EES) that satisfies the verification criteria.

[0073] Validating the registration request includes, in the above embodiment, identifying a second server located in the EDN 4 and satisfying at least one selection criterion, and validating security requirements.

[0074] The verification criteria may include some or all of the selection criteria described in the above embodiment, or may include other requirements. Specifically, the verification criteria may include security requirements in addition to some or all of the selection criteria in the above embodiment.

[0075] In application of this embodiment, the arrangement of the ECS 7 and the EES 5 is not limited to the above-mentioned arrangement example.

[0076] 8 is a flowchart showing an example of the operation of the first server according to the present embodiment. The first server may be an EES 5, and may attempt to register the EEC 2 in response to a registration request from the EEC 2 of the UE 1, which is a requesting entity. In step 801, the first server receives a registration request (i.e., a registration request or a registration update request) from the requesting entity.

[0077] In step 802, in response to receiving the registration request, the first server attempts to verify (identify, find, select, or determine) the registration request. At least one factor considered in verifying the registration request may include at least one of security requirements, the location of UE1, the Application Client Profile(s) provided by EEC2, and the operation status of the second server (i.e., EAS). As a specific example of the verification of the registration request based on the Application Client Profile(s) provided by EEC2, the EES5 may identify the EAS(s) that match the provided Application Client profile. If multiple Application Client profiles are provided, the EES5 may identify the EAS(s) that match all the Application Client profiles. Alternatively, the EES5 may identify the EAS(s) that match at least one of the provided Application Client profiles. Alternatively, the EES5 may identify the EAS(s) on an Application Client profile basis.

[0078] Here, matching may mean that the information (e.g., characteristics, performance, status) of the EAS satisfies the information or conditions of the Application Client included in the Application Client profile. Selection criteria for the EAS(s) may be as follows. The Application Client profile includes at least one of, for example, an "Application Client Schedule", an "Expected Application Client Geographical Service Area", a "Service Continuity Support", or a "List of EASs". The Application Client Schedule indicates an expected operation schedule of the AC3, for example, a time window. The Expected Application Client Geographical Service Area indicates an expected location(s) of the UE1 during the expected operation schedule of the AC3, for example, a route. The Service Continuity Support indicates whether service continuity support is required for the AC3. The List of EASs includes an EAS ID and may further include Application Client Service Key Performance Indicators (KPIs). The Application Client Service KPIs indicates service characteristics required by the AC3.These service characteristics include at least one of, for example, connection bandwidth, maximum request rate to be generated by the AC, maximum response time, maximum compute resources required by the AC, maximum memory resources required by the AC, or information specific to the AC type (e.g., video, Virtual Reality (VR), etc.). The EES5 may specify an EAS that matches all information elements included in the Application Client profile. Alternatively, the EAS may specify an EAS that matches at least one information element included in the Application Client profile. Alternatively, the EAS5 may specify an EAS(s) that matches all information elements included in the Application Client profile except for the "List of EASs" and that matches at least one item in the "List of EASs".

[0079] The UE location may specify the position of the UE or the network to which UE1 is attached. The value of the UE location may be a Cell Identity (ID), a Tracking Area Identity (TAI), Global Positioning System (GPS) coordinates, or a civic address. The selection criteria on the UE location for the selection of EAS(s) by EES5 may require that the location of UE1 is within an EDN service area, an EES service area, or an EAS service area. The EAS service area may be a topological service area (e.g., Cell ID(s), or TAI(s)) or a geographical service area. The EAS service area may be the same as or a subset of the EDN service area. The EAS service area may be the same as or a subset of the EES service area.

[0080] If the registration request satisfies the verification criteria (YES in step 803), the procedure proceeds to step 804. In step 804, the first server (i.e., EES5) sends a registration success response message to the requesting entity (i.e., EEC2) indicating that the registration in step 801 was successful. Note that satisfying the verification criteria means identifying the second server in the above-mentioned embodiment and satisfying the security requirements.

[0081] On the other hand, if the registration request does not satisfy the verification criteria (NO in step 803), the procedure proceeds to step 805. The failure to satisfy the verification criteria refers to either or both of the following: the second server in the above-mentioned embodiment cannot be specified, or the security requirements are not satisfied (the second server cannot be used). In step 805, the first server (i.e., EES5) considers the verification result in step 802 and determines whether or not relocation of the registration is necessary. If it is determined that relocation of the registration is necessary, the first server (i.e., EES5) acquires, from the ECS7, information on an alternative server to replace the registration destination. Note that the alternative server information may be information on one or more EESs different from the EES5. In response to the acquisition of the alternative server information, the first server transmits a response message including information that explicitly indicates that relocation of the registration to an alternative server is necessary, for example, to the EEC2 as a response to the registration request (step 806). Alternatively, in response to the acquisition of the alternative server information, the first server may include the alternative server information in a registration failure response message and transmit this as a response to the registration request to the EEC2. Alternatively, in response to obtaining the alternative server information, the first server may include the alternative server information and information explicitly indicating that the registration needs to be relocated to the alternative server in a registration failure response message and send this to the EEC2 as a response to the registration request. In another example, the first server notifies the alternative server of the relocation of the registration. In response to receiving the registration relocation notification, the alternative server takes over and executes the registration procedure on behalf of the first server. At this time, the alternative server may execute the above-mentioned verification of the registration request (step 802 and thereafter). Here, if it is determined that the registration request satisfies the verification criteria (YES in step 803), the procedure proceeds to step 804. In step 804, the alternative server sends a registration success response message to the requesting entity (i.e., EEC2) on behalf of the first server.

[0082] According to the operations of the first server, the alternative server, and the requesting entity described above, when a registration request does not meet the validation criteria, the first server can prevent the registration from failing by redirecting to an alternative server.

[0083] The following provides some specific examples of implementations of the operations of the first server and the alternative server and the requesting entity described above with reference to FIGS.

[0084] Figure 9 shows the operations of EEC2, EES5 (source EES), and EES91 (target EES) as an example of registration relocation. EEC2 in Figure 9 corresponds to the requesting entity described above, EES5 in Figure 9 corresponds to the first server described above, and EES91 in Figure 9 corresponds to the alternative server described above. In step 901, EEC2 sends an EEC registration request or an EEC registration update request to EES5.

[0085] In step 902, the EES 5 initiates validation of the registration request as described with reference to Figure 8 (step 802) and, as further described with reference to Figure 8 (step 803), the EES 5 determines that relocation of the registration to an alternative server is necessary if the registration request does not meet validation criteria.

[0086] In step 903, if the EES 5 determines that it is necessary to relocate the registration to an alternative server, it sends an acquisition request (or a referral request) for alternative server information to the ECS 7. The acquisition request for alternative server information may follow the method shown in Non-Patent Document 1 (Figure 8.8.3.3-1). In addition, the acquisition request may include the Application Client Profiles that the EES 5 received from the EEC 2.

[0087] In step 904, the EES5 sends a response message including one or more alternative server information including the information of the EES91 acquired in step 903 to the EEC2 as a response to the registration request. The response message may be, for example, an EEC registration response or an EEC registration update response. The response message may include information requesting registration in a different EES for reassignment of the registration. The information requesting registration for reassignment may be attribute information "Registration requested" with the value "True" set to request EEC registration, or may be information with the value "Registration requested".

[0088] In step 905, EEC2 may abort the registration procedure started in step 901 in response to receiving the response in step 904.

[0089] In step 906, the EEC2 selects the EES91 from the one or more alternative server information received in step 904, and transmits an EEC registration request to the EES91. This initiates the registration procedure, and the registration is redirected to the alternative server.

[0090] Figure 10 shows the operation of EEC2, EES5 (source EES) and EES101 (target EES) as another example of registration relocation. EEC2 in Figure 10 corresponds to the requesting entity described above, EES5 in Figure 10 corresponds to the first server described above, and EES101 in Figure 10 corresponds to the alternative server described above. In step 1001, EEC2 sends an EEC registration request or an EEC registration update request to EES5.

[0091] In step 1002, the EES 5 initiates validation of the registration request as described with reference to Fig. 8 (step 802). Furthermore, as described with reference to Fig. 8 (step 803), the EES 5 determines that relocation of the registration to an alternative server is necessary if the registration request does not meet validation criteria.

[0092] In step 1003, if the EES 5 determines that it is necessary to relocate the registration to an alternative server, it sends an acquisition request (or a referral request) for alternative server information to the ECS 7. The acquisition request for alternative server information may follow the method shown in Non-Patent Document 1 (Figure 8.8.3.3-1). In addition, the acquisition request may include the Application Client Profiles that the EES 5 received from the EEC 2.

[0093] In step 1004, the EES5 selects the EES101 from one or more alternative server information including the information of the EES101 acquired in step 1003, and sends a registration relocation notification to the EES101. The registration relocation notification may include all information included in the registration request received by the EES5 from the EEC2 in step 1001. Alternatively, the registration relocation notification may include the registration request itself. In response to receiving the registration relocation notification, the EES101 may take over and execute the registration procedure. Specifically, the EES101 may execute the above-mentioned registration request verification (step 802 and thereafter). In response to the registration relocation notification received in step 1004, the EES101, which is the alternative server, may send a response to the EES5 indicating that the registration of the EEC2 has been successful.

[0094] In step 1005, if the EES101 determines that the registration request meets the validation criteria, the EES101 sends to the EEC2 a registration success response message including information of the EES121 instead of the EES5 (Alternative (ALT) 1 in FIG. 10). Alternatively, in step 1007, the EES5 may send to the EEC2 a registration success response message including information of the EES101 in response to receiving a registration relocation notification response including information of the EES101 from the EES101 in step 1006 (Alternative (ALT) 2 in FIG. 10).

[0095] Next, the following describes configuration examples of the UE1, EES5, EAS6, and ECS7 according to the above-mentioned embodiments. FIG. 11 is a block diagram showing a configuration example of the UE1. A Radio Frequency (RF) transceiver 1101 performs analog RF signal processing to communicate with a RAN node. The RF transceiver 1101 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 1101 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 1101 is coupled to an antenna array 1102 and a baseband processor 1103. The RF transceiver 1101 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmission RF signal, and provides the transmission RF signal to the antenna array 1102. The RF transceiver 1101 also generates a baseband reception signal based on the reception RF signal received by the antenna array 1102, and provides the baseband reception signal to the baseband processor 1103. The RF transceiver 1101 may include an analog beamformer circuit for beamforming, which may include, for example, multiple phase shifters and multiple power amplifiers.

[0096] The baseband processor 1103 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission line coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management of layer 1 (e.g., transmission power control), layer 2 (e.g., radio resource management, and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signaling related to attachment, mobility, and call management).

[0097] For example, the digital baseband signal processing by the baseband processor 1103 may include signal processing of a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. Also, the control plane processing by the baseband processor 1103 may include processing of a Non-Access Stratum (NAS) protocol, a Radio Resource Control (RRC) protocol, MAC Control Elements (CEs), and Downlink Control Information (DCIs).

[0098] The baseband processor 1103 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.

[0099] The baseband processor 1103 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1104 described later.

[0100] The application processor 1104 is also called a CPU, an MPU, a microprocessor, or a processor core. The application processor 1104 may include multiple processors (multiple processor cores). The application processor 1104 executes a system software program (operating system (OS)) and various application programs (e.g., a call application, a web browser, a mailer, a camera operation application, and a music playback application) read from the memory 1106 or a memory not shown, thereby implementing various functions of the UE1.

[0101] In some implementations, the baseband processor 1103 and the application processor 1104 may be integrated on a single chip, as shown by the dashed line (1105) in Figure 11. In other words, the baseband processor 1103 and the application processor 1104 may be implemented as a single System on Chip (SoC) device 1105. An SoC device may also be called a system Large Scale Integration (LSI) or a chipset.

[0102] The memory 1106 is a volatile memory or a non-volatile memory, or a combination thereof. The memory 1106 may include a plurality of physically independent memory devices. The volatile memory is, for example, a Static Random Access Memory (SRAM) or a Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is a Mask Read Only Memory (MROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. For example, the memory 1106 may include an external memory device accessible from the baseband processor 1103, the application processor 1104, and the SoC 1105. The memory 1106 may include an internal memory device integrated in the baseband processor 1103, the application processor 1104, or the SoC 1105. Furthermore, the memory 1106 may include a memory in a Universal Integrated Circuit Card (UICC).

[0103] The memory 1106 may store one or more software modules (computer programs) 1107 including instructions and data for performing the processes by the UE 1 described in the above-mentioned embodiments. In some implementations, the baseband processor 1103 or the application processor 1104 may be configured to read the software modules 1107 from the memory 1106 and execute them to perform the processes by the UE 1 described in the above-mentioned embodiments with reference to the drawings.

[0104] In addition, the control plane processing and operations performed by UE1 described in the above embodiment can be realized by elements other than the RF transceiver 1101 and the antenna array 1102, i.e., at least one of the baseband processor 1103 and the application processor 1104, and the memory 1106 storing the software module 1107.

[0105] Fig. 12 shows an example of the configuration of the EES5. The EAS6 and the ECS7 may also have a similar configuration to that shown in Fig. 12. Referring to Fig. 12, the EES5 (or the EAS6, or the ECS7) includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 is used, for example, to communicate with other network functions (NFs) or nodes. The network interface 1201 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series.

[0106] The processor 1202 may be, for example, a microprocessor, a Micro Processing Unit (MPU), or a Central Processing Unit (CPU). The processor 1202 may include multiple processors.

[0107] The memory 1203 is composed of a volatile memory and a non-volatile memory. The memory 1203 may include a plurality of physically independent memory devices. The volatile memory is, for example, a static random access memory (SRAM) or a dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, a mask read only memory (MROM), an electrically erasable programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. The memory 1203 may include a storage located away from the processor 1202. In this case, the processor 1202 may access the memory 1203 via the network interface 1201 or an I / O interface not shown.

[0108] The memory 1203 may store one or more software modules (computer programs) 1204 including instructions and data for performing processing by the EES5 (or EAS6, or ECS7) described in the above-mentioned embodiments. In some implementations, the processor 1202 may be configured to read the software modules 1204 from the memory 1203 and execute them to perform processing by the EES5 (or EAS6, or ECS7) described in the above-mentioned embodiments.

[0109] As described with reference to FIG. 11 and FIG. 12, each of the processors included in the UE1, EES5, EAS6, and ECS7 according to the above-described embodiment executes one or more programs including instructions for making a computer execute the algorithm described with reference to the drawings. The programs can be stored and provided to a computer using various types of non-transitory computer readable media. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, random access memory (RAM)). The programs may also be provided to a computer by various types of transitory computer readable media. Examples of the temporary computer-readable medium include an electric signal, an optical signal, and an electromagnetic wave. The temporary computer-readable medium can provide the program to the computer via a wired communication path such as an electric wire or an optical fiber, or a wireless communication path.

[0110] A wireless terminal (User Equipment (UE)) in this specification is an entity connected to a network via a radio interface. The wireless terminal (UE) in this specification is not limited to a dedicated communication device, but may be any device having the communication function of the wireless terminal (UE) described in this specification, such as:

[0111] The terms "User Equipment (UE)" (as the term is used in 3GPP), "mobile station", "mobile terminal", "mobile device" and "wireless device" are generally intended to be synonymous with each other. A UE may be a standalone mobile station such as a terminal, a mobile phone, a smartphone, a tablet, a cellular IoT terminal, an IoT device, etc. The terms "UE" and "wireless terminal" also encompass devices that are stationary for extended periods of time.

[0112] The UE may be, for example, production equipment, manufacturing equipment, and / or energy related machinery (including, by way of example only, boilers, engines, turbines, solar panels, wind power generators, hydroelectric generators, thermal power generators, nuclear generators, batteries, nuclear power systems, nuclear related equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metal processing machinery, manipulators, robots, robot application systems, tools, dies, rolls, conveying equipment, lifting equipment, cargo handling equipment, textile machinery, sewing machinery, printing presses, printing related machinery, paper converting machinery, chemical machinery, mining machinery, mining related machinery, construction machinery, construction related machinery, agricultural machinery and / or equipment, forestry machinery and / or equipment, fishing machinery and / or equipment, safety and / or environmental protection equipment, tractors, bearings, precision bearings, chains, cogwheels, power transmission equipment, lubrication equipment, valves, fittings, and / or application systems of any of the equipment or machinery mentioned above).

[0113] The UE may be, for example, a transportation device (by way of example only, a vehicle, an automobile, a motorcycle, a bicycle, a train, a bus, a handcart, a rickshaw, a ship and other watercraft, an airplane, a rocket, a satellite, a drone, a balloon, etc.).

[0114] The UE may be, for example, a device for information communication (eg, an electronic computer and related devices, a communication device and related devices, an electronic component, etc.).

[0115] The UE may be, for example, a refrigerator, a refrigerator application product and device, commercial and service equipment, a vending machine, an automatic service machine, an office machine and device, or a consumer electric or electronic machine (for example, an audio device, a speaker, a radio, a video device, a television, an oven range, a rice cooker, a coffee maker, a dishwasher, a washing machine, a dryer, an electric fan, a ventilation fan and related products, a vacuum cleaner, etc.).

[0116] The UE may be, for example, an electronic application system or device (eg, an x-ray device, a particle accelerator device, a radioactive material application device, a sonic application device, an electromagnetic application device, a power application device, etc.).

[0117] The UE may be, for example, a light bulb, a light, a weighing machine, an analytical instrument, a testing and measuring instrument (including, by way of example, a smoke alarm, an occupancy alarm sensor, a motion sensor, a radio tag, etc.), a watch or clock, a lab machine, an optical machine, a medical instrument and / or a medical system, a weapon, a sharp tool, or a hand tool.

[0118] The UE may be, for example, a personal digital assistant or device with wireless communication capabilities (e.g., an electronic device (e.g., a personal computer, electronic measuring instrument, etc.) configured to accommodate or accept a wireless card, wireless module, etc.).

[0119] The UE may be, for example, a device or part of a device that provides the following applications, services, and solutions in the "Internet of Things" (IoT) using wired and wireless communication technologies: IoT devices (or things) comprise appropriate electronics, software, sensors, network connections, etc. that enable the devices to collect and exchange data with each other and with other communication devices. IoT devices may be automated devices that follow stored software instructions in their internal memory. IoT devices may operate without the need for human supervision or attention. IoT devices may be devices that are stationary and / or remain inactive for long periods of time. IoT devices may be implemented as part of stationary devices. IoT devices may be embedded in non-stationary devices (such as vehicles) or attached to animals or people being monitored / tracked. IoT technology may be implemented on any communication device that can be connected to a communication network to send and receive data without control by human input or software instructions stored in memory. IoT devices are also sometimes called Machine Type Communication (MTC) devices, or Machine to Machine (M2M) communication devices, or Narrow Band-IoT (NB-IoT) UEs.

[0120] The UE may support one or more IoT or MTC applications.

[0121] Some examples of MTC applications are listed in the list given in 3GPP TS22.368 V13.2.0(2017-01-13) Annex B, the contents of which are incorporated herein by reference. This list is not exhaustive but shows exemplary MTC applications. In this list, the Service Areas of the MTC applications include Security, Tracking & Tracing, Payment, Health, Remote Maintenance / Control, Metering, and Consumer Devices.

[0122] Examples of MTC applications related to security include Surveillance systems, Backup for landline, Control of physical access (eg to buildings), and Car / driver security.

[0123] Examples of MTC applications related to track and trace include Fleet Management, Order Management, Telematics Insurance: Pay as you drive (PAYD), Asset Tracking, Navigation, Traffic information, Road tolling, and Road traffic optimisation / steering.

[0124] Examples of payment related MTC applications include Point of sales (POS), Vending machines, and Gaming machines.

[0125] Examples of health-related MTC applications include Monitoring vital signs, Supporting the aged or handicapped, Web Access Telemedicine points, and Remote diagnostics.

[0126] Examples of MTC applications for remote maintenance / control include Sensors, Lighting, Pumps, Valves, Elevator control, Vending machine control, and Vehicle diagnostics.

[0127] Examples of MTC applications related to metering include Power, Gas, Water, Heating, Grid control, and Industrial metering.

[0128] Examples of MTC applications for consumer devices include digital photo frames, digital cameras, and ebooks.

[0129] Examples of applications, services, and solutions include MVNO (Mobile Virtual Network Operator) services / systems, disaster prevention radio services / systems, private branch exchange (PBX) services / systems, PHS / digital cordless telephone services / systems, Point of sales (POS) systems, advertising services / systems, Multimedia Broadcast and Multicast Service (MBMS) services / systems, Vehicle to Everything (V2X: vehicle-to-vehicle, road-to-vehicle, and pedestrian-to-vehicle) services / systems, in-train mobile radio services / systems, location information related services / systems, disaster / emergency wireless communication services / systems, Internet of Things (IoT) services / systems, community services / systems, video distribution services / systems, Femto cell application services / systems, Voice over LTE (VoLTE) services / systems, and more. The service / system may be, for example, an LTE (Long Term Evolution) service / system, a wireless tag service / system, a billing service / system, a radio on-demand service / system, a roaming service / system, a user behavior monitoring service / system, a communications carrier / communication network selection service / system, a function restriction service / system, a PoC (Proof of Concept) service / system, a personal information management service / system for terminals, a display and video service / system for terminals, a non-communication service / system for terminals, an ad hoc network / DTN (Delay Tolerant Networking) service / system, etc.

[0130] The above-mentioned categories of UE are merely examples of applications of the technical ideas and embodiments described herein, and the UEs in this specification are not limited to these examples, and various modifications can be made by those skilled in the art.

[0131] Furthermore, the above-described embodiment is merely an example of application of the technical idea obtained by the inventor of the present invention. In other words, the technical idea is not limited to the above-described embodiment, and various modifications are possible.

[0132] For example, some or all of the above embodiments may be described as, but are not limited to, the following supplementary notes.

[0133] (Appendix 1) a first server, At least one memory; and coupled to the at least one memory; and In response to receiving a request from a requesting entity for connection to an entity providing a service in an edge data network, attempting to identify a second server located within the edge data network based on at least one selection criterion; if the second server cannot be identified or is unavailable, identifying a second alternative server different from the second server, or identifying a first alternative server that attempts to identify the second server on behalf of the first server; at least one processor configured to A first server comprising: (Appendix 2) The at least one processor is configured to, if the second alternate server is identified, send information of the second alternate server to the requesting entity. 2. The first server according to claim 1. (Appendix 3) the second alternative server being a server that is unable to satisfy some or all of the at least one selection criterion; 3. The first server according to claim 1 or 2. (Appendix 4) The second server is a server located in the edge data network, which is a first Local Area Data Network (LADN); the second alternative server is a server located in a second LAN that includes servers that do not satisfy at least one of the at least one selection criterion. 4. The first server according to claim 1. (Appendix 5) At least one of the at least one selection criteria that is not satisfied is one of a service area, a geographical area, a route, a topological area, and a maximum response time; 5. The first server according to claim 4. (Appendix 6) The second alternative server is a server located in the second LAN associated with a service area larger than that of the first LAN. 6. The first server according to claim 4 or 5. (Appendix 7) The second server is a server located within the edge data network, which is a local area data network (LADN); The second alternative server is a server located in a data network that is not an LADN. 4. The first server according to claim 1. (Appendix 8) the request includes an indication that the requesting entity desires, can accept, or supports the provision of the service using a second alternate server; the at least one processor is configured to determine, based on the indication, whether to send the information of the second alternative server to the requesting entity if the second server cannot be identified. The first server according to any one of appendix 1 to 7. (Appendix 9) The at least one processor is configured to, if the first alternate server is identified, transmit information of the first alternate server to the requesting entity. 3. The first server according to claim 1 or 2. (Appendix 10) The at least one processor is configured to, if it identifies the first alternate server, send information corresponding to the request to the first alternate server for an attempt to identify the second server. 3. The first server according to claim 1 or 2. (Appendix 11) The first server is an Edge Configuration Server (ECS); Each of the second server and the second alternative server is an Edge Enabler Server (EES) or a target EES; The requesting entity is an Edge Enabler Client (EEC) located in a User Equipment (UE) or a source EES; The first server according to any one of appendix 1 to 8. (Appendix 12) The at least one selection criterion includes at least one of the following: a location of the UE, at least one Application Client profile provided by the EEC, a running state of the second server, or a load state of the second server; 12. The first server according to claim 11. (Appendix 13) The first server is an Edge Enabler Server (EES), a source EES, or a target EES; Each of the second server and the second alternative server is an Edge Application Server (EAS) or a target EAS; The requesting entity is an Edge Enabler Client (EEC) located in a User Equipment (UE), a source EAS, or a source EES; The first server according to any one of appendix 1 to 8. (Appendix 14) The at least one selection criterion includes at least one of the following: a location of the UE, EAS discovery filters provided by the EEC, a running state of the second server, or a load state of the second server; 14. The first server according to claim 13. (Appendix 15) The at least one processor is configured to, when the second server cannot be identified, obtain information of the first alternative server from a third server that manages information of the first server. 2. The first server according to claim 1. (Appendix 16) each of the first server and the first alternative server is an Edge Enabler Server (EES); the second server is an Edge Application Server (EAS); The requesting entity is an Edge Enabler Client (EEC) located in a User Equipment (UE); 16. The first server according to claim 1 or 15. (Appendix 17) The at least one selection criterion includes at least one of a security requirement, a location of the UE, at least one Application Client profile provided by the EEC, EAS discovery filters provided by the EEC, a running state of the second server, or a load state of the second server; 17. The first server of claim 16. (Appendix 18) 1. A method performed by a first server, comprising: In response to receiving a request from a requesting entity for connection to an entity providing a service in an edge data network, attempting to identify a second server located within the edge data network based on at least one selection criterion; and if the second server cannot be identified or is unavailable, identifying a second alternative server different from the second server or identifying a first alternative server that attempts to identify the second server on behalf of the first server; A method for providing the above. (Appendix 19) A program for causing a computer to perform a method for a first server, comprising: The method comprises: In response to receiving a request from a requesting entity for connection to an entity providing a service in an edge data network, attempting to identify a second server located within the edge data network based on at least one selection criterion; and if the second server cannot be identified or is unavailable, identifying a second alternative server different from the second server or identifying a first alternative server that attempts to identify the second server on behalf of the first server; A program that includes: (Appendix 20) At least one memory; and coupled to the at least one memory; and Sending a request to a first server for a connection to an entity providing a service in the edge data network; receiving a response to the request from the first server; If a second server located within the edge data network that is attempted to be identified based on at least one selection criterion is not identified, if the response includes information of a second alternative server different from the second server or information of a first alternative server that attempts to identify the second server instead of the first server, determine whether to accept the information of the first alternative server or the information of the second alternative server for providing the service. at least one processor configured to A requesting entity. (Appendix 21) the second alternative server being a server that is unable to satisfy some or all of the at least one selection criterion; A request entity as described in Appendix 20. (Appendix 22) The second server is a server located in the edge data network, which is a first Local Area Data Network (LADN); the second alternative server is a server located in a second LAN that includes servers that do not satisfy at least one of the at least one selection criterion. 22. A request entity as described in Claim 20 or 21. (Appendix 23) At least one of the at least one selection criteria that is not satisfied is one of a service area, a geographical area, a route, a topological area, and a maximum response time; A request entity as described in Appendix 22. (Appendix 24) The second alternative server is a server located in the second LAN associated with a service area larger than that of the first LAN. 24. A request entity as described in Clause 22 or 23. (Appendix 25) The second server is a server located within the edge data network, which is a local area data network (LADN); The second alternative server is a server located in a data network that is not an LADN. 22. A request entity as described in Claim 20 or 21. (Appendix 26) the at least one processor is configured to include in the request an indication of whether the requesting entity desires, can accept, or supports the provision of the service using a second alternate server. A request entity according to any one of Supplementary Notes 20 to 25. (Appendix 27) The first server is an Edge Configuration Server (ECS); Each of the second server and the second alternative server is an Edge Enabler Server (EES) or a target EES; The requesting entity is an Edge Enabler Client (EEC) located in a User Equipment (UE) or a source EES; A request entity according to any one of Supplementary Notes 20 to 26. (Appendix 28) The at least one selection criterion includes at least one of the following: a location of the UE, at least one Application Client profile provided by the EEC, a running state of the second server, or a load state of the second server; A request entity as described in Appendix 27. (Appendix 29) The first server is an Edge Enabler Server (EES), a source EES, or a target EES; Each of the second server and the second alternative server is an Edge Application Server (EAS) or a target EAS; The requesting entity is an Edge Enabler Client (EEC) located in a User Equipment (UE), a source EAS, or a source EES; A request entity according to any one of Supplementary Notes 20 to 26. (Appendix 30) The at least one selection criterion includes at least one of the following: a location of the UE, EAS discovery filters provided by the EEC, a running state of the second server, or a load state of the second server; A request entity as described in Appendix 29. (Appendix 31) each of the first server and the first alternative server is an Edge Enabler Server (EES); the second server is an Edge Application Server (EAS); The requesting entity is an Edge Enabler Client (EEC) located in a User Equipment (UE); A request entity as described in Appendix 20. (Appendix 32) The at least one selection criterion includes at least one of a security requirement, a location of the UE, at least one Application Client profile provided by the EEC, EAS discovery filters provided by the EEC, a running state of the second server, or a load state of the second server; A request entity as described in Appendix 31. (Appendix 33) 1. A method performed by a requesting entity, comprising: Sending a request to a first server for connection to an entity providing a service in the edge data network; receiving a response to the request from the first server; and if a second server located within the edge data network that is attempted to be identified based on at least one selection criterion is not identified, if the response includes information of a second alternative server different from the second server or information of a first alternative server that attempts to identify the second server instead of the first server, determining whether to accept the information of the first alternative server or the information of the second alternative server for providing the service; A method for providing the above. (Appendix 34) 1. A program for causing a computer to perform a method for a requesting entity, comprising: The method comprises: Sending a request to a first server for connection to an entity providing a service in the edge data network; receiving a response to the request from the first server; and if a second server located within the edge data network that is attempted to be identified based on at least one selection criterion is not identified, if the response includes information of a second alternative server different from the second server or information of a first alternative server that attempts to identify the second server instead of the first server, determining whether to accept the information of the first alternative server or the information of the second alternative server for providing the service; A program that includes:

[0134] This application claims priority to Japanese Patent Application No. 2021-023807, filed on February 17, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0135] 1. User Equipment (UE) 2 Edge Enabler Client (EEC) 3 Application client (AC) 4. Edge Data Network (EDN) 5 Edge Enabler Server (EES) 6 Edge Application Server (EAS) 7 Edge Configuration Server (ECS) 1103 Baseband Processor 1104 Application Processor 1106 Memory 1107 Module 1202 Processor 1203 Memory 1204 Module

Claims

1. An Edge Configuration Server (ECS), means for receiving a service provisioning request from an Edge Enabler Client (EEC), the service provisioning request including Application Client profile (AC profile) information; A means for determining or locating an Edge Enabler Server (EES) using geographical service area information; means for returning a service provisioning response to the EEC, the service provisioning response including information related to the EES; ECS equipped with.

2. An Edge Configuration Server (ECS), means for receiving a service provisioning request from an Edge Enabler Client (EEC), the service provisioning request including Application Client profile (AC profile) information; A means to identify an Edge Enabler Server (EES) based on Service continuity support information; means for returning a service provisioning response to the EEC, the service provisioning response including information related to the EES; ECS equipped with.

3. 1. A method for an Edge Configuration Server (ECS), comprising: Receive a Service provisioning request including Application Client profile (AC profile) information from an Edge Enabler Client (EEC); Using the geographical service area information to determine or identify an Edge Enabler Server (EES); and returning a service provisioning response to the EEC, the service provisioning response including information related to the EES.

4. 1. A method for an Edge Configuration Server (ECS), comprising: Receive a Service provisioning request including Application Client profile (AC profile) information from an Edge Enabler Client (EEC); Identify the Edge Enabler Server (EES) based on the Service continuity support information, and returning a service provisioning response to the EEC, the service provisioning response including information related to the EES.

Images