Patent Description:
Therefore, the <NUM> or pre-<NUM> communication system is also called a "Beyond <NUM> Network" or a "Post LTE System".

In the <NUM> system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access(NOMA), and sparse code multiple access (SCMA) as an advanced access technology have also been developed.

The 3GPP, which is in charge of cellular mobile communication standards, has named a new core network structure <NUM> core (5GC) and is standardizing the 5GC in order to evolve from an existing <NUM> LTE system to a <NUM> system.

The 5GC can support the following differentiated functions compared to the evolved packet core (EPC), which is the existing <NUM> network core.

First, a network slice function is introduced in the 5GC. According to a <NUM> requirement, the 5GC needs to support various types of terminals and services, for example, enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

Each terminal/service has different requirements in a core network. For example, an eMBB service may require a high data rate, while an URLLC service may require high stability and low latency. To satisfy various service requirements, network slicing is proposed.

Network slicing is a method of producing a plurality of logical networks by virtualization of one physical network, and each network slice instance (NSI) may have a different characteristic. Thus, each NSI may have a network function (NF) suitable for the characteristic thereof, thereby satisfying various service requirements. Accordingly, an NSI suitable for the characteristic of a required service may be allocated to each terminal, thereby efficiently supporting various <NUM> services.

Second, the 5GC can easily support a network virtualization paradigm by separating a mobility management function and a session management function. In existing <NUM> LTE, all terminals can receive services from a network through signaling exchange with a single core device called a mobility management entity (MME) that is in charge of registration, authentication, mobility management, and session management functions.

However, in <NUM>, as the number of terminals is explosively increasing and mobility and traffic/session characteristics to be supported are segmented according to the types of terminals, when a single device, such as an MMF, supports all functions, scalability to add an entity for each required function is bound to decrease. Accordingly, various functions are being developed based on a structure in which a mobility management function and a session management function are separated in order to address complexity in function/implementation of a core device in charge of a control plane and to improve scalability in signaling load. Document <CIT>, relates to a method for modifying a base application resident on a terminal. Terminal-related information is transmitted from the terminal upon initial activation of the base application at the terminal. Application variant information is received from a configuration server system, which is used to modify a user interface of the base application.

In the disclosure, it may be needed to support a flexible edge computing network architecture for supporting scenarios in which an edge computing platform of a local area data network of an operator is operated and installed in various forms within the operator.

A user equipment (UE) registered in one operator network may need to be able to connect to a plurality of edge computing platforms provided by a plurality of edge computing platform service providers to receive a service.

A UE registered in one operator network may need to be able to distinguish an area where an edge computing platform is provided from an area where an edge computing platform is not provided and to discover the address of an edge computing server to be accessed by an application layer in the area where the edge computing platform is provided.

The solution is set out in the appended set of claims.

According to the disclosure, a plurality of edge computing network operators can provide edge computing services in one operator network. Further, according to the disclosure, it is possible to operate an edge computing platform for each area.

In the following description of the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.

In the following description, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In the disclosure, a downlink (DL) may refer to a radio transmission path via which a base station transmits a signal to the terminal, and an uplink (UL) may refer to a radio transmission path via which a terminal transmits a signal to a base station.

In the following description of embodiments of the disclosure, the LTE or LTE-A system will be described by way of example, but the embodiments of the disclosure may be applied to other communication systems having similar backgrounds or channel types. In addition, based on determinations by those skilled in the art, the embodiments of the disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure.

<FIG> illustrates an application network architecture for supporting edge computing.

Referring to <FIG>, a user equipment (UE) <NUM> may include at least one application client <NUM> and an edge enabler client <NUM>. The application client <NUM> may be an application-level client to provide an edge computing service for a user when provided with the edge computing service.

In addition, the UE <NUM> may include a mobile terminal (not shown in <FIG>) to communicate with a wireless communication network, for example, at least one mobile communication network or two or more mobile communication networks.

A 3GPP network <NUM> is illustrated as a representative mobile communication network and may include, for example, an EPC and/or a 5GC. The 3GPP network <NUM> may include base stations that directly communicate with the UE <NUM> over the air, and may include a core network configuration above the base stations. When the 3GPP network <NUM> includes the 5GC, the 3GPP network <NUM> may include an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a user plane function (UPF), and the like.

When the 3GPP network <NUM> includes an EPC as a core network, the 3GPP network <NUM> may include network nodes corresponding to a 5GC.

Edge data networks may be configured through network slicing, and all edge data networks A to N may be configured in the same form. For example, in the configuration of edge data network A <NUM>-A, an edge hosting platform <NUM> may be included, and an edge enabler server <NUM>, an application server <NUM>, and an orchestrator <NUM> for an edge hosting platform may be included. The edge enabler server <NUM> may include an edge enabler client manager <NUM>, an edge enabler platform <NUM>, and an edge enabler API server <NUM>.

Network functions illustrated in <FIG> may be defined as follows.

3GPP network <NUM>: May include a 3GPP radio access network and a core network.

Edge data networks <NUM>-A,. , 300N: Data network of a <NUM> core network or a packet data network of an EPC network, which may be a data network including functions of providing an edge computing service, such as the edge hosting platform <NUM> and the edge enabler server <NUM>.

UE application (Application client) <NUM>: Application program operating on a mobile operating system of the UE <NUM>, which may be identified by OSId and OSAppID in the <NUM> core network.

Application servers (or edge applications) <NUM>: Application server program operating in a VM image or a virtualization container operating on the edge hosting platform <NUM>, which may be a server program executed by instantiation of the VM image and may also be referred to as an edge application.

Edge data network configuration server <NUM>: Server providing configuration information about an edge data network to the UE <NUM>, which may be an initial access server from which the UE <NUM> can receive configuration information to use an MEC service.

Edge hosting platform <NUM>: May be platform software including a virtualization layer capable of executing a plurality of edge applications. In this document, the edge hosting platform <NUM> may be used in the same concept as an edge hosting environment.

Orchestrator <NUM> for edge hosting platform: May be a management system that manages the edge hosting platform <NUM> and manages the lifecycle of edge application programs operating on the edge hosting platform <NUM>. The orchestrator <NUM> can perform a function of an orchestrator defined in an ETSI management and network operation (MANO).

Edge enabler server <NUM>: Server for providing an edge computing service, which may serve as a server that provides the UE <NUM> with a list of application programs available on the edge hosting platform <NUM> (edge enabler client manager), manages configuration information about edge application programs operating on the edge computing hosting platform <NUM>, and provides edge applications with an API for a function provided by the 3GPP network.

Edge enabler client <NUM>: Software module of the UE <NUM>, which may be a software agent having functions for providing an edge computing service. The edge enabler client <NUM> may serve as a software agent that performs an authentication function for the UE to access an edge computing server, performs routing necessary for the UE application program <NUM> by the UE <NUM> receiving information provided from the edge hosting platform <NUM> via interworking with the edge enabler server <NUM>, and provides information to the UE application program <NUM>.

The disclosure can provide the following two scenarios enabling an operator to flexibly install an edge network and can disclose application network architectures and methods for implementing the scenarios.

The application network architecture for supporting edge computing of <FIG> may be managed by an edge computing operator separate from a mobile communication operator, and thus a plurality of separate edge computing operators may exist in one mobile communication operator network. The application network architecture for supporting edge computing of <FIG> may support this operator configuration.

The application network architecture illustrated in <FIG> may support a plurality of edge computing operators in one mobile communication network. The application network architecture enables configuration information for accessing a plurality of edge computing service operators available in one mobile communication network and edge computing networks installed by the operators to be transmitted to a UE.

The application network architecture illustrated in <FIG> enables configuration information for accessing an edge network service provider selected by a mobile communication operator from among a plurality of edge computing operators existing in one mobile communication network and an edge computing network installed by the selected edge network service provider to be transmitted to the UE <NUM>.

A description is made with reference to attached <FIG>.

<FIG> illustrates a scenario for supporting a plurality of edge computing platform operators.

Referring to <FIG>, edge service provider X <NUM> and edge service provider Y <NUM> are included. Edge service provider X <NUM> is shown to have a form including edge data network A and edge data network B therein, and edge service provider Y <NUM> is shown to have a form including one edge data network C.

All the edge data networks (edge data networks A, B, and C) have the same configuration. For example, the edge data networks may include edge enabler servers 310a, 310b, and 310c and edge application servers 320a-<NUM>, 320a-<NUM>, 320b-<NUM>, 320b-<NUM>, 320c-<NUM>, and 320c-<NUM>. The edge application servers 320a-<NUM>, 320a-<NUM>, 320b-<NUM>, 320b-<NUM>, 320c-<NUM>, and 320c-<NUM> are shown to be configured in the same form, but different application servers may be configured if necessary or depending on areas. For example, edge data network A may be configured to include a first application server, a second application server, and a third application server, and edge data network B may be configured to include only a third application server. In another example, edge data network A may be configured to include a first application server, a second application server, and a third application server, and edge data network B may be configured to include a fourth application server. In still another example, edge data network A and edge data network B may be configured to include a first application server and a second application server, and edge data network C may be configured to include a third application server and a fourth application server.

Each of the edge data networks may be connected to UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> through corresponding UPFs 221a, 221b, and 221c in the 5GC. The UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> may include the foregoing configuration of <FIG>. In addition, the UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> may further include various modules for user convenience. For example, the UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> may include a device for providing a graphical user interface to a user, a touch device for input convenience, or a voice recognition device. As widely known, the UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> are capable of wireless access through base stations <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of a mobile communication network.

As illustrated in <FIG>, a plurality of edge computing operators may exist in one mobile communication operator network. For example, a first mobile communication operator network <NUM> may include edge data network A and edge data network B. In other words, one edge computing operator may configure a plurality of edge data networks within one mobile communication operator network to provide an edge network service. One edge data network may include data infrastructures 325a, 325b, and 525c including an edge hosting platform and an edge orchestrator, and edge enabler servers 310a, 310b, and 310c may provide configuration information for providing an edge computing service to the UEs <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM>.

The application layer architecture for supporting edge computing illustrated in <FIG> may support the following edge computing service deployment scenarios of a mobile communication operator.

Edge computing is installed only in some areas of an operator network in an initial edge computing deployment, and when the operator expands an area where edge computing is installed, an edge computing service area may increase or decrease. It is also possible for the operator to reduce the area when providing an edge computing service.

A mobile communication operator can provide edge computing services differentiated by area. For example, when a business using edge computing is started only in a specific city, an edge computing service may be provided only in an area designated by the operator. The mobile communication operator may operate a separate edge computing service for each area and may provide different edge application services for respective areas.

For the foregoing various deployments of edge data networks, the application network architecture illustrated in <FIG> allows an operator to install an edge computing service platform in each area. The application layer architecture supports a structure in which a plurality of edge data networks can be deployed, one edge data network may include an edge data network service area that is a portion of the coverage of a mobile communication operator network, and the edge data network service area may include a plurality of cells or tracking areas.

The application network architecture illustrated in <FIG> may support a function of configuring information about an associated edge network service area in a UE.

The application network architecture illustrated in <FIG> may support a function enabling a UE to identify an area related to an edge network service area.

A mobile communication operator may have various network deployment scenarios for providing edge computing according to business requirements. In the disclosure, various network deployment scenarios are divided into three scenarios as follows, and each deployment scenario are described with reference to <FIG>.

The following three deployment scenarios may be broadly presented for mobile communication operators.

A first deployment scenario is an edge data network deployment scenario using an Internet DN. This scenario will be described with reference to <FIG>.

<FIG> illustrates a network deployment scenario Option 1A according to the disclosure.

Referring to <FIG>, an Internet DN includes a first edge data network and a second edge data network, and the first edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>. The second edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>.

The individual UPFs <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> may be connected to base stations <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> capable of communicating with a mobile terminal over the air. The first edge data network may include an edge hosting environment <NUM>-<NUM>, and may include an edge enabler server <NUM>-<NUM> and edge applications <NUM>-<NUM> and <NUM>-<NUM> running in the edge hosting environment <NUM>-<NUM>. The second edge data network may also include an edge hosting environment <NUM>-<NUM>, and may include an edge enabler server <NUM>-<NUM> and edge applications <NUM>-<NUM> and <NUM>-<NUM> running in the edge hosting environment <NUM>-<NUM>.

<FIG> shows a scenario in which a UE connects to an edge application using a data network used for Internet access. The deployment scenario according to <FIG> may be referred to as Option 1A. In this network deployment scenario, a separate dedicated DN for supporting edge computing does not exist, and the UE may access edge applications through the DN for Internet access (Internet DN in <FIG>). The DN for Internet access refers to a default PDN connection in an EPC architecture, and may be a DNN specified in DNN information stored in a local configuration of the UE or a USRP rule having a match-all traffic descriptor among policies received through a URSP in the 5GC.

In the scenario illustrated in <FIG>, the entire operator network area (PLMN area) may be the service areas of the edge data networks. For example, as illustrated in <FIG>, edge data network <NUM> corresponds to an area corresponding to local DN <NUM> of the Internet DN, and edge data network <NUM> corresponds to an area corresponding to local DN <NUM> of the Internet DN. In this network deployment scenario, intermediate UPFs (I-UPFs) <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> are required to distinguish traffic for the UE to access the Internet from traffic for the UE to communicate with the edge applications <NUM>-<NUM>, <NUM>-<NUM>,. , <NUM>-<NUM>, <NUM>-<NUM>, and the like installed in the edge hosting environments <NUM>-<NUM> and <NUM>-<NUM>. A solution using the I-UPFs may be a solution supporting an uplink classifier (UL-CL) or IPv6 multihoming.

The respective edge enabler servers <NUM>-<NUM> and <NUM>-<NUM> may represent the edge hosting environments <NUM>-<NUM> and <NUM>-<NUM>), and one logical edge enabler server may exist in a local data network (DN) unless specified otherwise.

<FIG> illustrates a network deployment scenario Option 1B according to the disclosure.

Referring to <FIG>, an Internet DN includes a first edge data network and a second edge data network, and the first edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>. The second edge data network may include one UPF <NUM>-<NUM>. A third UPF <NUM>-<NUM> illustrated in <FIG> may be a UPF that is not connected to an edge data network.

The network deployment scenario illustrated in <FIG> is a deployment scenario in which a UE communicates with the edge applications using an Internet DN as in the scenario illustrated in <FIG>. The scenario illustrated in <FIG> is different from that illustrated in <FIG> in that the edge data networks do not cover the entire operator network. Referring to <FIG>, there is no edge data network to which a UPF3 <NUM>-<NUM> can directly connect. Accordingly, the UE cannot access an edge data network in the service area of the UPF3 <NUM>-<NUM>. The deployment scenario according to <FIG> may be referred to as Option 1B.

A second network deployment scenario is a deployment scenario using a dedicated DN. <FIG> illustrates a network deployment scenario Option 2A according to the disclosure.

In the network deployment scenario illustrated in <FIG>, similar to the scenario shown in <FIG>, all the edge data networks may be used in the entire service area of an operator network. The difference between the first network deployment scenario (Option 1A) illustrated in <FIG> and the deployment scenario of Option 2A illustrated in <FIG> is as follows.

In the network deployment scenario according to <FIG>, the UE uses a separate DN, for example, a dedicated DN, to access the edge applications <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM>, instead of sharing the network with the Internet DN. A separate DN for distinguishing the edge data networks may be preconfigured in the UE (UE local configuration), or a specific DNN may be transmitted to the UE through the URSP and may be stored in the UE. In this network deployment scenario, when the UE moves from the area of edge data network <NUM> to the area of edge data network <NUM>, an SMF (not shown in <FIG>) of a <NUM> core network may terminate a PDU session used in edge data network <NUM> and may provide a method for the UE to access the nearest edge data network using an SSC Mode <NUM> or SSC Mode <NUM> solution of instructing the UE to reestablish a session with the same DNN in edge data network <NUM>.

<FIG> illustrates a network deployment scenario Option 2B according to the disclosure.

Referring to <FIG>, an Internet DN includes a first edge data network and a second edge data network, and the first edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>). The second edge data network may include one UPF <NUM>-<NUM>. A third UPF <NUM>-<NUM> illustrated in <FIG> may be a UPF that is not connected to an edge data network.

The network deployment scenario illustrated in <FIG> is a deployment scenario in which a UE communicates with the edge applications <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, and <NUM>-<NUM> using a dedicated DN as in the scenario illustrated in <FIG>.

The scenario illustrated in <FIG> is different from that illustrated in <FIG> in that the edge data networks do not cover the entire operator network. As illustrated in <FIG>, there is no edge data network to which a UPF3 <NUM>-<NUM> can directly connect. Accordingly, the UE cannot access an edge data network in the service area of the UPF3 <NUM>-<NUM>.

<FIG> illustrates a network deployment scenario Option 3A according to the disclosure.

Referring to <FIG>, a first edge data network and a second edge data network are illustrated. The first edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>. The second edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>.

The network deployment scenario illustrated in <FIG> is a network deployment scenario in which a connection is established through a separate DN in each area. The network deployment scenario illustrated in <FIG> may be referred to as Option 3A. The entire service area of an operator network includes a plurality of edge data networks, and the respective edge data networks have different service areas. This configuration in which a data network has a service area is specified in a description of a LADN in TS <NUM><NUM>. That is, in the network deployment scenario illustrated in <FIG>, the entire service area of the operator network is covered using a plurality of LADNs. The respective edge enabler servers <NUM>-<NUM> and <NUM>-<NUM> may represent the edge hosting environments <NUM>-<NUM> and <NUM>-<NUM> in the edge data networks.

<FIG> illustrates a network deployment scenario Option 3B according to the disclosure.

Referring to <FIG>, a first edge data network and a second edge data network are illustrated. The first edge data network may include two different UPFs <NUM>-<NUM> and <NUM>-<NUM>. The second edge data network may include one UPF <NUM>-<NUM>. A third UPF <NUM>-<NUM> illustrated in <FIG> may be a UPF that is not connected to an edge data network.

The network deployment scenario illustrated in <FIG> is a deployment scenario in which a UE communicates with the edge applications using a LADN as in the scenario illustrated in <FIG>. The network deployment scenario illustrated in <FIG> may be referred to as Option 3B. The scenario illustrated in <FIG> is different from that illustrated in <FIG> in that the edge data networks do not cover the entire operator network. Comparing <FIG> with <FIG>, there is no edge data network to which a UPF3 <NUM>-<NUM> can directly connect. Accordingly, the UE cannot access an edge data network in the service area of the UPF3 <NUM>-<NUM>.

A first embodiment relates to a method and procedure for obtaining edge data network configuration information. The first embodiment is described with reference to attached <FIG>.

<FIG> illustrates a procedure for obtaining edge data network configuration information according to the disclosure.

According to <FIG>, in operation <NUM>, a UE <NUM> determines the address of an initial access server. The address of the initial access server may be expressed as a URI as follows, and the address excluding a <domain> part is fixed.

Example of initial access URI address:
http://edgeconfiguration. <domain>/provisioning.

The domain address (<domain>) is determined by the following method.

The UE receives a PLMN code (PLMN identifier) included in system information (SIB) of a serving PLMN broadcast from a camped base station, and the PLMN code includes an MNC and an MCC. Upon obtaining the MNC and the MCC from the PLMN code, the UE may configure a domain address from the MNC and the MCC.

In operation <NUM>, the UE <NUM> transmits an initial configuration request message to an edge data network configuration server.

In operation <NUM>, the edge data network configuration server <NUM> transmits information about an edge data network to the UE <NUM>. The edge data network may be one data network or packet data network for providing an edge computing service. The edge data network may be distinguished by a DNN or an APN. One edge data network may be connected to one or a plurality of RAN nodes. One edge data network provides a service in an edge data network service area. The edge data service area may be a tracking area, a cell list, an SMF service area, or a UPF service area which can be classified as an area by an operator on a 3GPP network. The edge data network may include network functions that support edge computing.

In the 5GC, the edge data network corresponds to one data network, and the UE can access the edge data network through a PDU session connection. In the EPC, the edge data network corresponds to one packet data network, and the UE can access the edge data network through a PDN connection.

Edge data network configuration information transmitted by the edge data network configuration server <NUM> to the UE <NUM> includes the following or some thereof.

A second embodiment relates to an edge data network discovery method.

A UE may distinguish an edge data network by identifying a tracking area and a cell list from LADN information received in a registration procedure. The UE may receive the LADN information from a network through the registration procedure or a UE configuration update (UCU) procedure. When using an LADN for an edge computing service, the UE may identify whether an LADN DNN is a DNN for supporting edge computing. Further, the UE may identify LADN service area information included in the LADN information and may identify (determine) whether the UE is in the edge data network.

According to another method for the UE to identify (determine) the service area of an edge data network, the UE may identify the service area of an edge data network, based on a spatial validity condition included in a UE route selection policy (URSP) provided by a PCF of a 5GC network to the UE. When a DNN for accessing an edge computing service is configured, the UE may identify a spatial validity condition transmitted along with a related URSP policy and may identify whether a cell or tracking area on which the UE currently camps in a 3GPP network is within a spatial validity area, thereby identifying whether there is an available edge data network.

A third embodiment relates to a method for establishing an edge data network session. The third embodiment may be described with reference to <FIG>.

<FIG> illustrates an edge data network session establishment procedure according to the disclosure.

According to <FIG>, an edge data network generation procedure through a PDU session establishment procedure is performed according to the following operations.

In operation <NUM>, it may be determined to generate an edge data network of a UE <NUM>. The UE <NUM> may determine to generate the edge data network. The UE <NUM> may discover an edge data network service area by identifying whether the UE <NUM> is in the edge data network area according to the description of the second embodiment and may identify (determine) whether a base station on which the UE <NUM> camps belongs to the edge data network of the UE <NUM>. That is, it is possible to identify (determine) whether the base station on which the UE <NUM> camps is an edge data network service area described in the second embodiment. When it is determined that the UE <NUM> is in the edge data network area, the UE <NUM> may determine to establish a session for accessing the edge data network.

When the UE <NUM> determines to establish the session for accessing the edge data network, the UE <NUM> may transmit a session establishment request message to a 3GPP network <NUM>. When the 3GPP network is the 5GC, the UE <NUM> may transmit a PDU session establishment request message to an SMF <NUM>. The PDU session establishment request message may include the following information.

A DNN, an S-NSSAI, a UE identifier, an edge data network usage indicator, and edge data network operator information may be included.

The identifier of the UE may be a GPSI, and the GPSI may follow a network access identifier (NAI) format in the form of username@domainname.

The SMF <NUM> receiving the session establishment request may determine whether to perform a procedure for requesting authorization for use from a DN-AAA server <NUM> in view of the DNN, the S-NSSAI, and the UE identifier (e.g., the GPSI) in the NAI format received from the UE <NUM>.

The SMF <NUM> may identify (determine) whether a preconfigured domain name or a domain name received from a PCF (not shown in <FIG>) and configured matches a domain name included in the UE identifier in the NAI format and may identify (determine) whether a use authorization request is transmitted to the DN AAA server <NUM>.

The SMF <NUM> may identify (determine) whether the DNN is configured for edge computing, that is, may determine whether the DNN matches a preconfigured DNN or a DNN received from the PCF and configured and may identify (determine) whether the use authorization request is transmitted to the DN AAA server <NUM>. The UE identifier may be included in a use authorization request message transmitted by the SMF to the DN-AAA server <NUM>.

The UE <NUM> and the DN-AAA server <NUM> may perform an authentication procedure for session establishment. Here, the UE <NUM> and the DN-AAA server <NUM> may perform the authentication procedure according to an extensible authentication protocol (EAP: RFC <NUM>).

The DN-AAA server <NUM> may receive the use authorization request message and may determine whether to authorize use through the UE identifier and a policy and configuration information of the DN-AAA server <NUM> included in the request message. When the DN-AAA server <NUM> determines authorization for use, the DN-AAA server <NUM> may transmit a use authorization message to the SMF <NUM>. The DN-AAA server <NUM> may transmit a DN profile index.

The DN-AAA server <NUM> may transmit an application layer address (e.g., a URI) of an edge enabler server that the UE <NUM> accesses via an application layer or a domain address (FQDN) for generating an application layer address to the SMF <NUM> through the UE identifier and the policy and the configuration information of the DN-AAA server <NUM>.

The DN-AAA server <NUM> may transmit edge data network configuration information of the UE <NUM>. The edge network configuration information may be the same as that described in the first embodiment.

Operation <NUM> to operation <NUM> described above may be collectively referred to as an authentication operation. That is, reference numeral <NUM> may correspond to an operation in which the DN-AAA server <NUM> authenticates the UE <NUM> through the 3GPP network <NUM>.

The SMF <NUM> may determine whether to authorize the UE <NUM> to use a session. When a session use authorization request is transmitted to the DN-AAA server <NUM>, the SMF <NUM> may determine whether to authorize use of the session requested by the UE <NUM> in view of a result included in a use authorization response message from the DN-AAA server <NUM>.

The DN-AAA server <NUM> may transmit edge computing-related configuration information via the use authorization response message. The edge computing-related configuration information may include edge data network application layer access information and authentication information in the edge data network configuration information described in the first embodiment.

The SMF <NUM> may determine whether to authorize the use of the session, based on the DNN, the S-NSSAI, and the UE identifier transmitted by the UE, according to an autonomous configuration thereof. In this case, the SMF <NUM> has edge data network application layer access information and authentication information among locally configured edge data network configuration information.

The SMF <NUM> may receive a DN authorization profile index from the DN-AAA server <NUM>. In this case, the DN-AAA server <NUM> may receive a policy and charging control (PCC) rule related to the policy control function (PCF) and a session management-related policy. The SMF <NUM> may receive edge computing-related configuration information of the UE <NUM> from the PCF. The edge computing-related configuration information may include edge data network application layer access information and authentication information in the edge data network configuration information described in the first embodiment.

When determining to authorize the UE <NUM> to use the session, the SMF <NUM> may transmit a successful session establishment response message in operation <NUM>, and otherwise, the SMF <NUM> may transmit a session establishment response message along with an indication of rejecting the session.

When the SMF <NUM> determines to authorize the UE to use the session, the SMF may transmit a session establishment response message for authorizing session establishment to the UE. The session establishment response message may include edge data network application layer access information. As described in operation <NUM>, the edge data network application layer access information may be information received from the DN-AAA server <NUM>, information autonomously configured by the SMF <NUM>, or information received from the PCF.

A fourth embodiment relates to a procedure for accessing an edge enabler server. The fourth embodiment describes the procedure illustrated in <FIG>.

The fourth embodiment is described with reference to attached <FIG>.

<FIG> illustrates a procedure for requesting and obtaining edge application information according to the disclosure.

A UE <NUM> may identify an application level discovery trigger condition in an edge computing environment for accessing an edge enabler server <NUM> in operation <NUM>. The trigger condition for accessing the edge enabler server is as follows.

The UE <NUM> may transmit an edge application information request message to the edge enabler server <NUM>. The edge application information request message may include the following information.

When receiving the edge application information request message from the UE <NUM>, the edge enabler server <NUM> may identify access token information and may examine authentication information. The edge enabler server <NUM> may identify the authority of the UE <NUM> and may transmit information requested by the UE <NUM> to the UE <NUM>. The information transmitted to the UE <NUM> includes information necessary for the UE <NUM> to provide an edge computing service, and examples of the necessary information are as follows.

A fifth embodiment illustrates the configuration of an edge data network using an LADN. The fifth embodiment is described with reference to attached <FIG>.

<FIG> illustrates a procedure in which a UE obtains LADN information through a registration procedure in a 5GC network according to the disclosure.

An edge data network for supporting edge computing may be defined as a 5GC LADN. When the edge data network is defined as the 5GC LADN, a UE may receive LADN information in a registration procedure as in the procedure of <FIG>. The LADN information may include information about an LADN DNN and an LADN service area. The LADN service area may be designated as follows.

When performing the registration procedure in operation <NUM>, the UE <NUM> may transmit a registration request message.

In operation <NUM>, an access and mobility management function (AMF) <NUM> of a 5GC network may transmit an indicator indicating the type of the LADN area and the LADN area to the UE <NUM>. For example, when the LADN area is the same as a current registration area, the AMF <NUM> may transmit a registration accept message of the registration procedure including an indicator indicating that the LADN area is the same as the current registration area. Alternatively, the AMF <NUM> may transmit the message including an indicator that the LADN area is included in an LADN service area provided in the current registration area. When the LADN area is the same as the entire area of the current operator, the AMF <NUM> may include, in the LADN information included in the registration accept message of the registration procedure, an indicator indicating that the LADN service area is available in an area to which a current PLMN and an equivalent network (equivalent PLMN) belongs. When the LADN area is available in an area where a specific equivalent PLMN among current PLMNs is broadcast, the AMF <NUM> may transmit the registration accept message including a corresponding indicator and equivalent PLMN ID information to the UE <NUM>. When the LADN service area is configured with the cell list, the AMF <NUM> may transmit the cell list as LADN service area information.

A sixth embodiment illustrates a procedure performed in a UE, an operator network, and an application layer in the network deployment scenarios described with reference to <FIG>. The sixth embodiment is described with reference to attached <FIG>.

<FIG> illustrates a procedure performed to receive an edge computing service when a UE is powered on according to the disclosure.

This embodiment illustrates a power-on procedure commonly applied to various deployment scenarios. In each operation, actions that may vary depending on the deployment scenarios are compared in a description.

In operation <NUM> of <FIG>, a mobile terminal (MT) <NUM> performing a modem function of a UE <NUM> may perform a procedure for initial registration for a 3GPP network <NUM> and session establishment.

This procedure may include both of a case in which the UE accesses the EPC and a case in which the UE <NUM> accesses the 5GC. When the UE <NUM> accesses the EPC, the UE <NUM> and a 3GPP network may perform an initial attach procedure. When the UE <NUM> accesses the 5GC, the UE <NUM> and the 3GPP network <NUM> may perform an initial registration procedure and a PDU session establishment procedure.

Both when the UE <NUM> accesses the EPC and when the UE <NUM> accesses the 5GC, the UE <NUM> may access the Internet through the procedure <NUM>, and a connected Internet network may be referred to as an "Internet DN".

When successfully performing operation <NUM>, the UE <NUM> may perform an initial provisioning procedure with an EDN configuration server <NUM> located in the "Internet DN" in operation <NUM>. This procedure is the same as the procedure described in the first embodiment.

When receiving configuration information from the EDN configuration server in operation <NUM>, the UE <NUM> may identify whether DNN (or APN) information designated as an EDN is a currently established PDU session in operation <NUM>. That is, the UE <NUM> may determine whether the DNN (or APN) information is a PDU session established in operation <NUM>. When an operator supports edge computing in the same DN as a DN that accesses the Internet as in the network deployment scenario 1A or 1B, the EDN configuration information configured by the EDN configuration server <NUM> is DNN information the same as that of a DN configured in operation <NUM>. When a DNN (or APN) for the currently established session in the UE <NUM> is the same as the EDN configuration information, the UE <NUM> does not establish a separate session.

When the operator has a network deployment scenario, such as the network deployment scenario 2A, 2B, 3A, or 3B, the UE <NUM> may need to establish a separate session to access an edge application.

When a PDU session (or PDN connection) corresponding to a DNN (or APN) specified in the configuration information received by the UE <NUM> from the EDN configuration server <NUM> is not established, the UE <NUM> may determine that it is needed to establish a PDU session. Here, the PDU session (or PDN connection) to be established may or may not be provided depending on the area. In the network deployment scenario 2B or 3B, since it may be impossible for the UE <NUM> to currently establish a PDU session, the UE <NUM> may determine whether to establish a session by identifying service area information for each DNN specified in an EDN configuration and the current location of the UE in the network in order to determine whether it is possible to establish a DNN (or APN) specified in the EDN configuration in a current area.

When the UE <NUM> determines that the UE <NUM> is currently within an EDN service area, the UE <NUM> may transmit a request for establishment of a PDU session (or PDN connection) to the 3GPP network and may establish a PDU session (or PDN connection) in the 3GPP network.

When the initial provisioning procedure according to operation <NUM> is performed by a trigger condition rather than occurring after the initial registration procedure (operation <NUM>), a dedicated DNN (or APN) specified in the EDN configuration information may already be established by the UE. When the session corresponding to the DNN for EDN configuration specified in the EDN configuration information has already been established in the UE <NUM>, the UE <NUM> does not initiate a session procedure according to operation <NUM>.

When the UE <NUM> determines that additional session establishment is not necessary in operation <NUM> or when additional session establishment is successfully performed in operation <NUM>, the UE <NUM> may identify whether there is an edge enabler server <NUM> available in the current area. When there is an edge enabler server <NUM> available in the current area, the UE <NUM> may transmit a request to the edge enabler server <NUM> received with the EDN configuration information in operation <NUM>. A detailed procedure of operation <NUM> may follow the procedure of <FIG>.

Details of the UE <NUM> determining to initiate establishment of a PDU session (PDN connection) according to the received configuration information to access the edge enabler server <NUM> with the configuration information after receiving the configuration information and determining to access the edge enabler server <NUM> may follow <FIG>.

<FIG> is a control flowchart in a UE when the UE accesses an edge enabler server according to an embodiment of the disclosure.

According to <FIG>, in an initial start, when a network to be connected is a 5GC, a UE <NUM> may perform an initial registration procedure in operation <NUM> and may establish a PDU session for connecting to an Internet DN in operation <NUM>. However, in an initial start, when the network to be connected is an EPC, the UE <NUM> may perform an initial attach operation in operation <NUM> and may establish a PDU session for connecting to an Internet DN in operation <NUM>. Subsequently, an enabler client <NUM> of the UE <NUM> may initiate an initial provisioning procedure in operation <NUM>.

When the UE periodically receives the initial provisioning procedure, for example, in operation <NUM>, in addition to a case where the initial provisioning procedure performed in the initial start or when provisioning information is dynamically updated, for example, in operation <NUM>, the UE <NUM> may determine whether a DNN (or APN) received as part of EDN configuration information is a PDU session currently established in the UE <NUM>.

Specifically, when the UE <NUM> periodically receives the initial provisioning procedure in operation <NUM>, the UE <NUM> may perform a provisioning procedure in operation <NUM> and may then proceed to operation <NUM>.

When the provisioning information is dynamically updated in operation <NUM>, the UE <NUM> may proceed to operation <NUM>.

When the DNN (or APN) received by the UE <NUM> as part of the EDN configuration information is not currently established in the UE <NUM> (No in operation <NUM>), the UE <NUM> may determine whether a PDU session (PDN connection) is available in a current area in operation <NUM>. When a PDU session (PDN connection) is not available in the current area (No in operation <NUM>), the UE <NUM> proceeds to operation <NUM> and does not initiate a PDU session (PDN connection). When it is possible to establish a PDU session (PDN connection) in the current area (Yes in operation <NUM>), the UE <NUM> may proceed to operation <NUM> of the UE <NUM> and may initiate establishment of the PDU session. The UE <NUM> may successfully establish the PDU session (PDN connection) (Yes in operation <NUM>). When the UE <NUM> cannot successfully establish the PDU session (PDN connection) (No in operation <NUM>), the UE <NUM> proceeds to operation <NUM> and does not initiate a PDU session (PDN connection).

When the PDU session (PDN connection) is successfully established in the current UE <NUM> or the PDU session (PDN connection) is established (Yes in operation <NUM>), the UE <NUM> may determine whether an edge enabler server <NUM> is available in the current location of the UE <NUM> in operation <NUM>. When the edge enabler server <NUM> is available in the current location of the UE <NUM> (Yes in operation <NUM>), the edge enabler client <NUM> of the UE <NUM> may transmit an edge application discovery request message to the edge enabler server <NUM> in operation <NUM>. When receiving a response to the message, the UE <NUM> may receive a list of available edge applications and configuration information about the edge applications in operation <NUM>.

When the DNN (or APN) received by the UE <NUM> as part of the EDN configuration information is not currently established in the UE <NUM> (No in operation <NUM>), the UE <NUM> may determine whether a PDU session (PDN connection) is available in a current area in operation <NUM>. When a PDU session (PDN connection) is not available in the current area (No in operation <NUM>), the UE <NUM> proceeds to operation <NUM> and does not initiate a PDU session (PDN connection). When it is possible to establish a PDU session (PDN connection) in the current area (Yes in operation <NUM>), the UE <NUM> may initiate establishment of the PDU session of the UE <NUM> in operation <NUM>.

<FIG> illustrates a mobile network operator (MNO) model for providing an edge computing service.

According to the mobile network operator model, a plurality of base stations <NUM>, <NUM>, and <NUM> is included in an edge network service area, and each base station may communicate with UEs <NUM>-<NUM> and <NUM>-<NUM>. A fourth UE <NUM>-<NUM> may be connected to cloud application servers <NUM>-<NUM> and <NUM>-<NUM> connected to the Internet <NUM> through a UDM <NUM> and an edge enabler server <NUM>, in which actual data may be transmitted through a UPF <NUM>.

A first UE <NUM>-<NUM> may access an edge computing network by interworking with a mobile communication network or through a UFP <NUM> connected to an edge network located in the mobile communication network. Accordingly, the first UE <NUM>-<NUM> may be provided with a service from edge application servers <NUM>-<NUM> and <NUM>-<NUM> by interworking with the mobile communication network or through an edge computing infrastructure <NUM> of the edge network located in the mobile communication network. For this service, an edge enabler server <NUM> may interwork with the UDM <NUM>.

According to the configuration of <FIG>, subscriber-based differential services may be provided, and differentiated services may be implemented depending on whether edge computing is used and depending on each edge application or each local area.

A centralized model, a distributed model, and a hybrid model according to the disclosure are described with reference to <FIG>.

In <FIG>, an edge computing area may be defined as a subarea of a PLMN application range. The edge computing area may be a list of tracking areas of a UE <NUM> or a list of cells. An MNO needs to be able to identify the location of the UE in a network geographic area. The UE also needs to be able to identify the location thereof. There may be a plurality of edge computing areas in one PLMN, one PLMN may include a plurality of edge network service areas, and the individual edge network service areas may be configured not to overlap. The edge computing service areas may be deployed in a distributed manner, and two areas A and B may have adjacent boundaries as illustrated in <FIG>.

In this case, in a centralized model, there may be only one edge computing area in the PLMN. One central entity may be configured to manage all edge applications in one PLMN. An example of this model may be an ETSI MEC architecture.

Next, in a distributed model, each edge computing area may be configured to be managed by another edge computing area management entity.

A hybrid model may be configured in a combination of the central model and the distributed model.

Next, an edge network and configuration information are described.

An edge network may use a data network or a packet data network for connection to provide an edge computing service. An edge network may be configured to be identified by a DNN or APN. An edge network may be connected via one or more RAN nodes. That is, a wireless UE may access an edge network through an RNA node. An edge network may be supported in an edge network service area. For example, as illustrated in <FIG>, a UE <NUM> may be connected to an edge data network connected to a UPF through an RAN to which the UE <NUM> belongs. When the RAN is not connected to the edge data network, the UE <NUM> cannot be provided with an edge computing service.

An edge network service area may be identified as a tracking area, a cell list, an SMF service area, or a UPF service area. An edge network may include a set of network functions that support edge computing. In a 3GPP system, a UE may access an edge computing network through a data network (DN) or a packet data network (PDN) of an evolved packet core network. The connection of the UE to the data network may be provided by a <NUM> core network using a PDU session or by an EPC using a PDN connection.

Next, an edge network configuration is described.

An edge network configuration may be a set of configuration information needed by a UE. The edge network configuration may include information as described above with reference to <FIG>.

<FIG> illustrates an edge computing system for a centralized management MNO configuration according to the disclosure.

Referring to <FIG>, a mobile network operator (MNO) may include a plurality of base stations, and each base station may be connected to UPFs 221a and 221b. The UPFs 221a and 221b illustrated in <FIG> may be connected to an edge network A <NUM> and an edge network B <NUM>, respectively. At least one UE <NUM> among UEs <NUM>, <NUM>, and <NUM> may be a UE for receiving an edge computing service. As indicated by reference numeral <NUM>, a first UE <NUM> may access the edge network A <NUM>, thereby being provided with an edge data service. To this end, as indicated by reference numeral <NUM>, an operation for authentication/authorization discovery needs to be performed through an edge enabler server <NUM>.

<FIG> illustrates a case in which a core network <NUM> is a 5GC, and the core network may include an SMF <NUM>, a PCF <NUM>, and a UDM/authentication server function (AUSF) <NUM>. A procedure for authenticating a UE may be performed between the UDM/AUSF <NUM> and the edge enabler server <NUM> (<NUM>). List information of an edge application server may be provided between a portal orchestrator <NUM> and the edge enabler server <NUM>. The portal orchestrator <NUM> may receive the following information from the application server.

An application identifier of a UE (UE App Id), DNS Info (FQDN), an edge application, cloud resources, and geographic area information may be received.

In a method illustrated in <FIG>, one PLMN includes a single entity (edge enabler server). Thus, all providers, such as MNOs, may use a single edge application set. Further, available edge application programs may vary depending on registration. Application program authentication may use a USIM credential or may use a separate credential. When the USIM credential is used, the USIM credential may also be used for authentication.

The 5GC core network illustrated above in <FIG> may have a core network component in a similar form to that described in <FIG>. In addition, a portal orchestrator <NUM> may be further included. The configuration of <FIG> may correspond to a case including distributed enabler servers for independently operating edge computing services.

<FIG> is a signal flowchart according to an authentication, configuration, and discovery procedure according to a centralized management MNO configuration according to the disclosure.

In <FIG>, an operation may be performed under the following assumption. A bootstrapping server function (BSF), which is a central enabler, is a logical entity in charge of authentication using a 3GPP credential of a subscriber in an MNO and generation and management of a key to be used in an application layer. The central enabler possesses a database of all information available in a plurality of edge networks. The central enabler has a list of all available edge applications. For example, the central enabler possesses a list of edge applications in each edge network.

<FIG> is a signal flowchart where a UE receives a list for receiving an edge computing service according to an embodiment of the disclosure.

Specifically, in <FIG>, the UE may perform authentication through the BSF <NUM>. The UE may transmit a message for requesting configuration information to a central edge enabler server <NUM> from a generated key. In response to this message, the UE may receive information about EDNs locally distributed including the edge enabler server <NUM>. A procedure for requesting an edge application list and receiving an available edge application list when a condition for triggering an edge application discovery is satisfied through the edge enabler server <NUM> is described.

In operation <NUM>, the UE <NUM> transmits the identifier of the UE <NUM> to the BSF <NUM>. In operation <NUM>, the BSF <NUM> may request an authentication vector (AV) and a user profile together with a UE identifier from a UDM or AUSF <NUM> and may receive the AV and the user profile for authentication. In operation <NUM>, the BSF <NUM> may return a <NUM> Unauthorized as a TTP response to the request of the UE <NUM>. This message may include RAND and AUTH (information about authentication of the UE). In operation <NUM>, the UE <NUM> may perform AKA authentication, may verify an AUTH, and may generate an RES.

In operation <NUM>, the UE <NUM> may transmit an HTTP request for RES authentication to the BSF <NUM>.

In operation <NUM> and operation <NUM>, the BSF <NUM> verifies an RES value received from the UE <NUM> and generates Ks. When successfully verifying the RES, the BSF <NUM> may respond to the UE <NUM> with <NUM> OK in operation <NUM>.

In operation <NUM>, the UE <NUM> may also perform AKA authentication on Ks from a 3GPP credential, thereby generating Ks.

In operation <NUM>, the UE <NUM> may transmit a configuration request message for requesting the configuration of the UE <NUM> to a centralized EES <NUM>. In operation <NUM>, the centralized EES <NUM> may receive the UE identifier transmitted from the UE <NUM>, the identifier of client software of the UE, or a bootstriping transaction ID from the UE in order to verify the configuration request message requested by the UE <NUM> and may transmit an authentication request message including this identifier information, an edge service provider name, a server name, and the like to the BSF <NUM> that has authenticated the UE through operation <NUM> to operation <NUM>. The BSF <NUM> may identify the identifier of the UE <NUM> or the UE client stored in operation <NUM> or the bootstrapping transaction ID, may identify the profile received from the UDM <NUM> in corresponding operation <NUM>, and may determine whether to authorize an edge service of the UE. When the BSF <NUM> determines to authorize the UE to use the edge service, the BSF <NUM> may transmit a response to the authentication request to the edge configuration function (edge configuration server) <NUM> in operation <NUM>. The response message to the authentication request includes an authentication key (Ks_NAF) to be used in the edge configuration server, the profile of an authorized user, and the lifetime of the authentication key.

When the edge configuration function <NUM> receives the response message, the edge configuration function <NUM> may transmit configuration information including information about an edge network to the UE <NUM> in operation <NUM>. The network configuration information of this message includes the edge data network configuration information illustrated in the first embodiment.

After receiving the configuration information from the edge configuration function <NUM>, the UE <NUM> may identify whether a triggering condition for discovering an edge application server occurs in operation <NUM>, and may transmit a discovery request according to operation <NUM> to an EES <NUM> when the triggering condition occurs. The triggering condition is as follows.

Based on this message, the edge configuration function <NUM> may transmit a list of available edge applications to the UE <NUM>.

<FIG> is a signal flowchart according to an authentication, configuration, and discovery procedure when a distributed management MNO is configured according to the disclosure.

The procedure of <FIG> may be performed under the following assumption. One AA server may be operated by one edge computing service provider. Authentication may use a separate credential. Edge Enabler servers may be distributed or centrally located.

In operation <NUM>, a UE <NUM> performs authentication with an authentication/authorization server using a user identifier or a generic public subscription identifier (GPSI: Identifier for identifying a subscriber). After successfully performing the authentication procedure, the UE <NUM> and the AA server <NUM> issue and share an authentication.

The UE <NUM> may transmit a configuration request message to an edge configuration function <NUM> in operation <NUM>. The edge configuration function <NUM> may transmit an authentication request to the AA server <NUM> in operation <NUM>. The AA server <NUM> may identify the authentication request, may perform authentication of the UE, and may transmit a result to the AA server <NUM> in operation <NUM>.

The edge configuration function <NUM> may request and receive a user profile from a profile database (or UDM) <NUM> in operation <NUM>. The edge configuration function <NUM> may transmit edge data network configuration information to the UE <NUM> in operation <NUM>.

The UE <NUM> may transmit a discovery request to an edge enabler server <NUM> in operation <NUM>. The edge enabler server <NUM> may request and receive the user profile from the profile database <NUM> in operation <NUM>. According to the user profile, the edge enabler server <NUM> may transmit a list of available edge applications to the UE <NUM> in operation <NUM>.

The foregoing details are provided for the convenience of understanding of the disclosure, and the disclosure is not limited thereto.

Claim 1:
A method for obtaining edge data network, EDN, configuration information by a user equipment (<NUM>), UE, to receive an edge computing service in a wireless communication system, the method comprising:
transmitting, to an EDN configuration server (<NUM>), an initial provisioning request message using a URI address of the EDN configuration server; and
receiving, from the edge data network configuration server (<NUM>), an initial provisioning response message comprising the EDN configuration information,
wherein the URI address is derived from a public land mobile network, PLMN, identifier, ID,
wherein the EDN configuration information includes an EDN connection information for establishing connection with the EDN, and an edge enabler server, EES, address, wherein the EDN connection information includes information on EDN which serves the UE that is connected to a core network from one of cells included in an edge computing service area, and
wherein the EES address includes an address of the EES as a URI.