Device and method for providing edge computing services in a wireless communication system

Abstract

The present disclosure relates to a communication technology and system thereof that combines a 5G communication system for supporting a higher data transmission rate than a 4G system with an Internet of Things technology. The present disclosure relates to a wireless communication system, and more specifically, the present disclosure relates to: an application layer network structure and method thereof for providing edge computing services in a cellular wireless communication system (5G system). The method according to an embodiment of the present disclosure is a method for a terminal to obtain edge data network setting information to receive edge computing services in a wireless communication system, and includes: a step for sending an initial provisioning request message to an edge data network configuration server; and a step for receiving an initial provisioning response message including information about an edge data network from an edge data network configuration server, wherein the initial provisioning request message may include a URI address of the edge data network configuration server.

Description

Technical Field

[0001] The present disclosure relates to an apparatus and method for providing edge computing services, and more particularly, to an apparatus and method for providing edge computing services in a wireless communication system. Background Art

[0002] In order to meet the demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also called "super 4G networks" or "post-LTE systems."

[0003] 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60 GHz band, in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems.

[0004] In addition, in the 5G communication system, system network improvement development based on advanced small cells, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-point (CoMP), receiving-end interference elimination, etc. is underway. In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) are also developed, as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0005] The Internet is a human-centered connected network in which humans generate and consume information, and is now evolving into the Internet of Things (IoT), in which distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) is the product of the combination of IoT technology and big data processing technology by connecting cloud servers. Since IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently.

[0006] This IoT environment can provide intelligent Internet technology services and create new value for human life by collecting and analyzing data generated between connected objects. IoT can be applied to a variety of fields including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances and advanced medical services through the integration and combination of existing information technology (IT) and various industrial applications.

[0007] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RANs), which are the above-mentioned big data processing technologies, can also be regarded as an example of the fusion of 5G technology and IoT technology.

[0008] 3GPP, which is responsible for cellular mobile communication standards, has named a new core network structure 5G Core (5GC) and is standardizing 5GC to enable the evolution from the existing 4G LTE system to the 5G system.

[0009] Compared with the Evolved Packet Core (EPC) of the existing 4G network core, 5GC can support the following different functions.

[0010] First, the network slicing function is introduced in 5GC. According to 5G requirements, 5GC needs to support various types of terminals and services, such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC).

[0011] Each terminal / service has different requirements in the core network. For example, eMBB services may require high data rates, while URLLC services may require high stability and low latency. In order to meet various business needs, network slicing technology is proposed.

[0012] Network slicing is a method of generating multiple logical networks by virtualizing a physical network, and each network slice instance (NSI) can have different characteristics. Therefore, each NSI can have a network function (NF) suitable for its characteristics, thereby meeting various service requirements. Therefore, an NSI suitable for the characteristics of the required service can be assigned to each terminal, thereby effectively supporting various 5G services.

[0013] Secondly, by separating mobility management functions and session management functions, 5GC can easily support network virtualization mode. In the existing 4G LTE, all terminals can receive services from the network through signaling exchanges with a single core device called the Mobility Management Entity (MME), which is responsible for registration, authentication, mobility management and session management functions.

[0014] However, in 5G, as the number of terminals explodes, and the mobility and traffic / session characteristics to be supported are segmented according to the terminal type, when a single device (such as MMF) supports all functions, the scalability of adding an entity for each required function is bound to decrease. Therefore, various functions are being developed based on a structure in which the mobility management function and the session management function are separated to resolve the complexity in the function / implementation of the core device responsible for the control plane and to improve the scalability in the signaling load. Summary of the invention

[0015] Technical issues

[0016] In the present disclosure, it may be necessary to support a flexible edge computing network architecture to support scenarios in which edge computing platforms of operator local area networks are operated and installed in various forms within operators.

[0017] A user equipment (UE) registered in one operator network may need to be able to connect to multiple edge computing platforms provided by multiple edge computing platform service providers to receive services.

[0018] A UE registered in an operator network may need to be able to distinguish between areas where edge computing platforms are provided and areas where edge computing platforms are not provided, and be able to discover the address of the edge computing server to be accessed by the application layer in the area where the edge computing platform is located.

[0019] Technical Solution

[0020] A method according to an embodiment of the present disclosure is a method for obtaining edge data network configuration information by a user equipment (UE) to receive edge computing services in a wireless communication system, the method comprising: sending an initial provisioning request message to an edge data network configuration server; and receiving an initial provisioning response message including information about an edge data network from the edge data network configuration server.

[0021] The initial provisioning request message may include a URI address of the edge data network configuration server.

[0022] A method according to another embodiment of the present disclosure is a method for providing edge data network configuration information to a UE by an edge data network configuration server through a wireless communication system, the method comprising: receiving an initial provisioning request message from the UE; and receiving an initial provisioning response message including information about an edge data network,

[0023] The initial provisioning request message may include a URI address of the edge data network configuration server.

[0024] The device according to an embodiment of the present disclosure is a user device for obtaining edge data network configuration information to receive edge computing services in a wireless communication system, the user device comprising: an application client configured to have edge computing services and provide edge computing services to users; an edge enabling client configured to perform control of accessing an edge computing server to provide edge computing services; and a mobile terminal configured to perform modem operations to access the wireless communication system,

[0025] Among them, edge-enabled clients

[0026] The mobile terminal may be controlled to send an initial provisioning request message to the edge data network configuration server, and the mobile terminal may be controlled to receive an initial provisioning response message including information about the edge data network from the edge data network configuration server, and

[0027] The initial provisioning request message includes the URI address of the edge data network configuration server.

[0028] Beneficial Effects

[0029] According to the present disclosure, multiple edge computing network operators can provide edge computing services in one operator network. In addition, according to the present disclosure, an edge computing platform can be operated for each region. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 An application network architecture and interface for supporting edge computing according to an embodiment of the present disclosure are shown;

[0031] Figure 2 A scenario for supporting multiple edge computing platform operators according to an embodiment of the present disclosure is shown;

[0032] Figure 3 illustrates a local edge data network deployment according to an embodiment of the present disclosure;

[0033] Figure 4 A process for obtaining edge data network configuration information according to an embodiment of the present disclosure is shown;

[0034] Figure 5 The edge data network session establishment process according to an embodiment of the present disclosure is shown;

[0035] Figure 6 A process for requesting and obtaining edge application information according to an embodiment of the present disclosure is shown;

[0036] Figure 7 A process in which a UE obtains LADN information through a registration process in a 5GC network according to an embodiment of the present disclosure is shown;

[0037] Figure 8 Showing a network deployment scenario option 1A according to an embodiment of the present disclosure;

[0038] Fig. 9 Showing a network deployment scenario option 1B according to an embodiment of the present disclosure;

[0039] Fig.10 Showing a network deployment scenario option 2A according to an embodiment of the present disclosure;

[0040] Fig.11 Showing a network deployment scenario option 2B according to an embodiment of the present disclosure;

[0041] Fig.12 Showing a network deployment scenario option 3A according to an embodiment of the present disclosure;

[0042] Fig.13 Showing a network deployment scenario option 3B according to an embodiment of the present disclosure;

[0043] Fig.14 Showing a process performed when a UE is powered on according to an embodiment of the present disclosure;

[0044] Fig.15 is a control flow chart in a UE when the UE accesses an edge enabling server according to an embodiment of the present disclosure;

[0045] Fig.16 A Mobile Network Operator (MNO) model for providing edge computing services is shown;

[0046] Fig.17 An edge computing system for centrally managing MNO configurations according to the present disclosure is shown;

[0047] Fig.18 is a signal flow diagram according to an authentication, configuration and discovery process, which is configured according to a centrally managed MNO according to the present disclosure; and

[0048] Fig.19 is a signal flow diagram according to authentication, configuration and discovery processes when a distributed management MNO is configured according to the present disclosure. DETAILED DESCRIPTION

[0049] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, detailed descriptions of known functions or configurations contained herein will be omitted when it may make the subject matter of the present invention unnecessarily unclear. The terms to be described below are terms defined in consideration of the functions in the present disclosure, and may differ depending on the user, user intention or custom. Therefore, the definition of the terms should be based on the content of the entire specification.

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

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

[0052] Figure 1 An application network architecture for supporting edge computing is shown.

[0053] refer to Figure 1 , a user equipment (UE) 100 may include at least one application client 101 and an edge enabling client 102. The application client 101 may be an application-level client to provide edge computing services for users when edge computing services are provided.

[0054] In addition, the UE 100 may include a mobile terminal ( Figure 1 not shown).

[0055] The 3GPP network 200 is illustrated as a representative mobile communication network, and may include, for example, EPC and / or 5GC. The 3GPP network 200 may include a base station that directly communicates with the UE 100 in the air, and may include a core network configuration above the base station. When the 3GPP network 200 includes a 5GC, the 3GPP network 200 may include an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), a user plane function (UPF), etc.

[0056] When the 3GPP network 200 includes the EPC as a core network, the 3GPP network 200 may include a network node corresponding to the 5GC.

[0057] The edge data network can be configured by network slicing, and all edge data networks A to N can be configured in the same form. For example, in the configuration of the edge data network A300-A, an edge hosting platform 301 can be included, and an edge enabling server 310, an application server 320, and an orchestrator 330 for the edge hosting platform can be included. The edge enabling server 310 can include an edge enabling client manager 311, an edge enabling platform 312, and an edge enabling API server 313.

[0058] Figure 1 The network function shown can be defined as follows.

[0059] 3GPP network 300: may include a 3GPP radio access network and a core network.

[0060] Edge data network 300 -A, ..., 300N: a data network of a 5G core network or a packet data network of an EPC network, which may be a data network including functions for providing edge computing services, such as an edge hosting platform 301 and an edge enabling server 310 .

[0061] UE application (application client) 101: An application running on the mobile operating system of UE 100, which can be identified by OSId and OSAppID in the 5G core network.

[0062] Application server (or edge application) 320: An application server program running in a VM image or a virtualized container running on the edge hosting platform 301, which may be a server program executed by instantiating a VM image, may also be referred to as an edge application.

[0063] Edge data network configuration server 400: A server that provides configuration information about the edge data network to the UE 100, which may be an initial access server, from which the UE 100 can receive configuration information to use the MEC service.

[0064] Edge hosting platform 301: may be platform software including a virtualization layer capable of executing multiple edge applications. In this document, edge hosting platform 301 may be used in the same concept as edge hosting environment.

[0065] The edge hosting platform's orchestrator 330 may be a management system that manages the edge hosting platform 301 and manages the lifecycle of edge applications running on the edge hosting platform 301. The orchestrator 330 may perform the functions of an orchestrator defined in ETSI Management and Network Operations (MANO).

[0066] Edge enabling server 310: A server for providing edge computing services, which can be used as a server for providing a list of applications available on the edge hosting platform 301 (edge ​​enabling client manager) to UE100, managing configuration information about edge applications operating on the edge computing hosting platform 301, and providing APIs to edge applications for functions provided by the 3GPP network.

[0067] Edge-enabled client 102: A software module of UE 100, which may be a software agent with the function of providing edge computing services. Edge-enabled client 102 may be used as a software agent, which performs an authentication function for UE to access the edge computing server, performs routing required by UE application 101 by receiving information provided from edge hosting platform 301 by UE 100 via interaction with edge-enabled server 310, and provides information to UE application 101.

[0068] The present disclosure can provide the following two scenarios, enabling operators to flexibly install edge networks, and can disclose application network architectures and methods for implementing these scenarios.

[0069] Scenario 1. Supporting multiple edge computing platform operators

[0070] Figure 1 The application network architecture for supporting edge computing can be managed by an edge computing operator that is separate from the mobile communication operator, and therefore, multiple independent edge computing operators can exist in one mobile communication operator network. Figure 1 The edge computing application network architecture can support this operator configuration.

[0071] Figure 1 The application network architecture shown can support multiple edge computing operators in one mobile communication network. The application network architecture enables configuration information for accessing multiple edge computing service operators available in one mobile communication network and edge computing networks installed by operators to be sent to the UE.

[0072] Figure 1 The illustrated application network architecture 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 mobile communication operator to be transmitted to the UE 100 .

[0073] Reference Figure 2 Provide explanation.

[0074] Figure 2 A scenario of supporting multiple edge computing platform operators is shown.

[0075] refer to Figure 2 , including an edge service provider X11 and an edge service provider Y12. The edge service provider x11 is shown to have a form including an edge data network A and an edge data network B, and the edge service provider y12 is shown to have a form including one edge data network C.

[0076] All edge data networks (edge ​​data networks A, B, and C) have the same configuration. For example, the edge data network may include edge enabling servers 310a, 310b, and 310c and edge application servers 320a-1, 320a-2, 320b-1, 320b-2, 320c-1, and 320c-2. Edge application servers 320a-1, 320a-2, 320b-1, 320b-2, 320c-1, and 320c-2 are shown as being configured in the same form, but different application servers may be configured if necessary or depending on the region. 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 yet 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.

[0077] Each edge data network may be connected to UE 100-1, 100-2, and 100-3 through corresponding UPF 221a, 221b, and 221c in 5GC. UE 100-1, 100-2, and 100-3 may include Figure 1 In addition, UE 100-1, 100-2 and 100-3 may also include various modules for user convenience. For example, UE 100-1, 100-2 and 100-3 may include a device for providing a graphical user interface to the user, a touch device for convenient input, or a voice recognition device. As is known to all, UE 100-1, 100-2 and 100-3 can be wirelessly accessed through base stations 201, 202, 203, 204, 205, 206, 207 and 208 of a mobile communication network.

[0078] like Figure 2As shown, there may be multiple edge computing operators in a mobile communication operator network. For example, the first mobile communication operator network 11 may include edge data network A and edge data network B. In other words, an edge computing operator may configure multiple edge data networks within a mobile communication operator network to provide edge network services. An edge data network may include data infrastructure 325a, 325b, and 525c, including an edge hosting platform and an edge orchestrator, and edge enabling servers 310a, 310b, and 310c may provide configuration information for providing edge computing services to UEs 100-1, 100-2, and 100-3.

[0079] Scenario 2: Deploy edge data networks by region

[0080] Figure 1 The application layer architecture shown for supporting edge computing can support the following edge computing service deployment scenarios of mobile communication operators.

[0081] 1) Progressive edge computing service scenario installation

[0082] In the initial edge computing deployment, edge computing is only installed in some areas of the operator's network, and when the operator expands the area where edge computing is installed, the edge computing service area may increase or decrease. When providing edge computing services, the operator may also reduce the area.

[0083] 2) Local differentiation of edge computing services and local edge computing professional services

[0084] Mobile communication operators can provide edge computing services differentiated by region. For example, when a service using edge computing is only available in a specific city, the edge computing service can be provided only in the region specified by the operator. Mobile communication operators can run separate edge computing services for each region and can provide different edge application services for the corresponding region.

[0085] 3) Mobile communication operators can operate using multiple edge computing service providers or solutions.

[0086] 4) Edge computing services may be provided only in an area smaller than the service area of ​​a mobile communication operator.

[0087] For the aforementioned edge data network deployments, Figure 1 The application network architecture shown allows operators to install edge computing service platforms in each area. The application layer architecture supports a structure in which multiple edge data networks can be deployed, and one edge data network can include an edge data network service area that is part of the mobile communication operator's network coverage, and the edge data network service area can include multiple cells or tracking areas.

[0088] Figure 1The illustrated application network architecture may support functionality for configuring information about an associated edge network service area in a UE.

[0089] Figure 1 The illustrated application network architecture may support functionality that enables a UE to identify an area associated with an edge network service area.

[0090] Mobile communication operators may have various network deployment scenarios to provide edge computing according to business needs. In this disclosure, various network deployment scenarios are divided into the following three scenarios, and reference is made to Figures 8 to 12 Describe each deployment scenario.

[0091] The following three deployment scenarios can be widely used by mobile communication operators.

[0092] (1) Edge data network deployment scenario using Internet data network (DN) (refer to Figure 8 and Fig. 9 describe)

[0093] (2) Edge data network deployment scenario using dedicated DN (refer to Fig.10 and Fig.11 describe)

[0094] (3) Edge data network deployment scenario using local dedicated DN (refer to Fig.12 and Fig.13 describe)

[0095] (1) Internet data network

[0096] The first deployment scenario is to use the edge data network deployment scenario of the Internet DN. Figure 8 Describe the scenario.

[0097] Figure 8 A network deployment scenario option 1A according to the present disclosure is shown.

[0098] refer to Figure 8 , the 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 221-1 and 221-2. The second edge data network may include two different UPFs 221-3 and 221-4.

[0099] The individual UPFs 221-1, 221-2, 221-3, and 221-4 may be connected to base stations 201, 202, 203, 204, 205, 206, 207, and 208 that are capable of communicating with mobile terminals over the air. The first edge data network may include an edge hosting environment 325-1, and may include an edge enabling server 310-1 and edge applications 320-11 and 320-12 running in the edge hosting environment 325-1. The second edge data network may also include an edge hosting environment 325-2, and may include an edge enabling server 310-2 and edge applications 320-21 and 320-22 running in the edge hosting environment 325-2.

[0100] Figure 8 A scenario is shown in which a UE is connected to an edge application using a data network for Internet access. Figure 8 The deployment scenario of can be referred to as option 1A. In this network deployment scenario, there is no separate dedicated DN for supporting edge computing, and the UE can access the Internet through the DN ( Figure 8 The DN for Internet access refers to the default PDN connection in the EPC architecture and can be a DNN specified in the DNN information stored in the local configuration of the UE, or a USRP rule that matches all service descriptors in the policy received through the URSP in the 5GC.

[0101] exist Figure 8 In the scenario shown, the entire operator network area (PLMN area) can be the service area of ​​the edge data network. Figure 8 As shown, edge data network 1 corresponds to an area corresponding to local DN 1 of the Internet DN, and edge data network 2 corresponds to an area corresponding to local DN 2 of the Internet DN. In this network deployment scenario, intermediate UPFs (I-UPFs) 221-1, 221-2, 221-3, and 221-4 are required to distinguish traffic for UE access to the Internet from traffic for UE communication with edge applications 320-11, 320-12, ..., 320-21, 320-22, etc. installed in edge hosting environments 325-1 and 325-2. A solution using I-UPF may be a solution that supports an uplink classifier (UL-CL) or IPv6 multi-homing.

[0102] Unless otherwise specified, the respective edge enabling servers 310-1 and 310-2 may represent edge hosting environments 325-1 and 325-2, and one logical edge enabling server may exist in a local data network (DN).

[0103] Fig. 9A network deployment solution option 1B according to the present invention is shown.

[0104] refer to Fig. 9 , the 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 221-1 and 221-2. The second edge data network may include one UPF 221-4. Fig. 9 The third UPF 222-3 shown in FIG. 2 may be a UPF that is not connected to the edge data network.

[0105] The individual UPFs 221-1, 221-2, 221-3, and 221-4 may be connected to base stations 201, 202, 203, 204, 205, 206, 207, and 208 that are capable of communicating with mobile terminals over the air. The first edge data network may include an edge hosting environment 325-1, and may include an edge enabling server 310-1 and edge applications 320-11 and 320-12 running in the edge hosting environment 325-1. The second edge data network may also include an edge hosting environment 325-2, and may include an edge enabling server 310-2 and edge applications 320-21 and 320-22 running in the edge hosting environment 325-2.

[0106] Fig. 9 The network deployment scenario shown is one in which the UE uses Figure 8 The deployment scenario of the Internet DN communicating with the edge application in the scenario shown. Fig. 9 The scenario shown is different from Figure 8 The scenario shown here is because the edge data network does not cover the entire carrier network. Fig. 9 , there is no edge data network that UPF3 221-3 can directly connect to. Therefore, the UE cannot access the edge data network in the service area of ​​UPF3 221-3. Fig. 9 The deployment scenario can be referred to as Option 1B.

[0107] (2) Edge data network deployment solution using dedicated DN

[0108] The second network deployment scenario is the deployment scenario using a dedicated DN. Fig.10 A network deployment scenario option 2A according to the present invention is shown.

[0109] refer to Fig.10 , the 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 221-1 and 221-2. The second edge data network may include two different UPFs 221-3 and 221-4.

[0110] The individual UPFs 221-1, 221-2, 221-3, and 221-4 may be connected to base stations 201, 202, 203, 204, 205, 206, 207, and 208 that are capable of communicating with mobile terminals over the air. The first edge data network may include an edge hosting environment 325-1, and may include an edge enabling server 310-1 and edge applications 320-11 and 320-12 running in the edge hosting environment 325-1. The second edge data network may also include an edge hosting environment 325-2, and may include an edge enabling server 310-2 and edge applications 320-21 and 320-22 running in the edge hosting environment 325-2.

[0111] exist Fig.10 In the network deployment scenario shown, Figure 8 The scenario shown is similar, with all edge data networks being available throughout the service area of ​​the operator network. Figure 8 The first network deployment scenario (option 1A) shown is similar to Fig.10 The differences between the deployment scenarios shown for Option 2A are as follows.

[0112] In accordance with Fig.10 In the network deployment scenario, the UE uses a separate DN, for example, a dedicated DN, to access edge applications 320-11, 320-12, 320-21, and 320-22 instead of sharing the network with the Internet DN. The separate DN for distinguishing edge data networks can be pre-configured in the UE (UE local configuration), or a specific DNN can be sent to the UE via the URSP and can be stored in the UE. In this network deployment scenario, when the UE moves from the area of ​​edge data network 1 to the area of ​​edge data network 2, the SMF ( Fig.10 (not shown) can terminate the PDU session used in edge data network 1, and can provide a method for the UE to access the nearest edge data network using an SSC mode 2 or SSC mode 3 solution that instructs the UE to re-establish a session in edge data network 2 using the same DNN.

[0113] Fig.11 A network deployment solution option 2B according to the present disclosure is shown.

[0114] refer to Fig.11 , the 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 221-1 and 221-2. The second edge data network may include one UPF 221-4. Fig.11 The third UPF 222-3 shown in FIG. 2 may be a UPF that is not connected to the edge data network.

[0115] The individual UPFs 221-1, 221-2, 221-3, and 221-4 may be connected to base stations 201, 202, 203, 204, 205, 206, 207, and 208 that are capable of communicating with mobile terminals over the air. The first edge data network may include an edge hosting environment 325-1, and may include an edge enabling server 310-1 and edge applications 320-11 and 320-12 running in the edge hosting environment 325-1. The second edge data network may also include an edge hosting environment 325-2, and may include an edge enabling server 310-2 and edge applications 320-21 and 320-22 running in the edge hosting environment 325-2.

[0116] Fig.11 The network deployment scenario shown is that the UE uses Fig.10 The deployment scenario in which the dedicated DN in the scenario shown communicates with edge applications 320-11, 320-12, 320-21 and 320-22.

[0117] Fig.11 The scene shown is similar to Figure 8 The scenario shown is different because the edge data network does not cover the entire operator network. Fig.11 As shown, there is no edge data network to which UPF3 221-3 can be directly connected. Therefore, the UE cannot access the edge data network in the service area of ​​UPF3 221-3.

[0118] (3) Edge data network deployment solution using local dedicated DN

[0119] Fig.12 A network deployment solution option 3A according to the present invention is shown.

[0120] refer to Fig.12 , showing a first edge data network and a second edge data network. The first edge data network may include two different UPFs 221-1 and 221-2. The second edge data network may include two different UPFs 221-3 and 221-4.

[0121] The individual UPFs 221-1, 221-2, 221-3, and 221-4 may be connected to base stations 201, 202, 203, 204, 205, 206, 207, and 208 that are capable of communicating with mobile terminals over the air. The first edge data network may include an edge hosting environment 325-1, and may include an edge enabling server 310-1 and edge applications 320-11 and 320-12 running in the edge hosting environment 325-1. The second edge data network may also include an edge hosting environment 325-2, and may include an edge enabling server 310-2 and edge applications 320-21 and 320-22 running in the edge hosting environment 325-2.

[0122] Fig.12 The network deployment scenario shown is a network deployment scenario in which connections are established through separate DNs in each zone. Fig.12 The network deployment scenario shown in can be referred to as Option 3A. The entire service area of ​​the operator network includes multiple edge data networks, and the respective edge data networks have different service areas. The description of LADN in TS 23.501 5.6.5 specifies such a configuration that the data network has a service area. That is, in Fig.12 In the illustrated network deployment scenario, multiple LADNs are used to cover the entire service area of ​​the operator network. The corresponding edge enablement servers 310-1 and 310-2 may represent edge hosting environments 325-1 and 325-2 in the edge data network.

[0123] Fig.13 A network deployment solution option 3B according to the present invention is shown.

[0124] refer to Fig.13 , showing a first edge data network and a second edge data network. The first edge data network may include two different UPFs 221-1 and 221-2. The second edge data network may include one UPF 221-4. Fig.13 The third UPF 222-3 shown in FIG. 2 may be a UPF that is not connected to the edge data network.

[0125] The individual UPFs 221-1, 221-2, 221-3, and 221-4 may be connected to base stations 201, 202, 203, 204, 205, 206, 207, and 208 that are capable of communicating with mobile terminals over the air. The first edge data network may include an edge hosting environment 325-1, and may include an edge enabling server 310-1 and edge applications 320-11 and 320-12 running in the edge hosting environment 325-1. The second edge data network may also include an edge hosting environment 325-2, and may include an edge enabling server 310-2 and edge applications 320-21 and 320-22 running in the edge hosting environment 325-2.

[0126] Fig.13 The network deployment scenario shown is that the UE uses Fig.12 Deployment scenario of LADN communicating with edge applications in the scenario shown. Fig.13 The network deployment scenario shown in may be referred to as Option 3B. Fig.13 The scene shown is similar to Fig.12 The scenario shown is different because the edge data network does not cover the entire carrier network. Fig.13 and Fig.12 , there is no edge data network to which UPF3 221-3 can directly connect. Therefore, the UE cannot access the edge data network in the service area of ​​UPF3 221-3.

[0127] <First Embodiment>

[0128] The first embodiment relates to a method and process for obtaining edge data network configuration information. Figure 4 A first embodiment is described.

[0129] Figure 4 The process for obtaining edge data network configuration information according to the present invention is shown.

[0130] according to Figure 4 In operation 0, the UE 100 may determine the address of the initial access server. The address of the initial access server may be expressed as a URI as follows, and excludes <domain>Some addresses are fixed.

[0131] Initial access URI address example:

[0132] http: / / edgeconfiguration. <domain> / provisioning

[0133] Domain Address( <domain>) is determined by the following method.

[0134] 1) An example of a method for configuring a domain address according to a mobile network code (MNC) and a mobile country code (MCC) is as follows.

[0135] (Example) mnc015.mcc234.pub.3gppnetworks.org

[0136] The UE receives a PLMN code (PLMN identifier) ​​included in the system information (SIB) broadcast by the serving PLMN from the camped base station, and the PLMN code includes MNC and MCC. When the MNC and MCC are obtained from the PLMN code, the UE can configure the domain address according to the MNC and MCC.

[0137] 2) A method using an operator domain address: The domain address can be determined using an already determined operator domain address. A domain address mapped with the operator's MNC and MCC is used for this domain address, and this information is pre-configured in the UE. An example of a domain address can be, for example, a domain address on the Internet, such as sktelecom.com.

[0138] 3) Access Point Name (APN) / Data Network Name (DNN) can be used as <domain>The UE can use the APN / DNN previously configured for each operator.

[0139] In operation 1, the UE 100 may send an initial configuration request message to the edge data network configuration server.

[0140] In operation 2, the edge data network configuration server 400 may send information about the edge data network to the UE 100. The edge data network may be a data network or a packet data network for providing edge computing services. The edge data network may be distinguished by a DNN or an APN. An edge data network may be connected to one or more RAN nodes. An edge data network provides services 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 areas by an operator on a 3GPP network. The edge data network may include network functions that support edge computing.

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

[0142] The edge data network configuration information sent by the edge data network configuration server 400 to the UE 100 includes the following or some of the following information.

[0143] 1) Information used to establish edge data network sessions

[0144] -Data Network Name (DNN) or Access Point Name (APN)

[0145] - Single Network Slice Assistance Information (S-NSSAI) and Dedicated Core Network Identifier (DCN ID)

[0146] - UE identifier (GPSI or NAI including username and domain name) used to represent the UE when accessing edge data network sessions

[0147] 2) Edge data network service area configuration information

[0148] - Network topology information: For example, it may include a tracking area, a cell ID list or set, and at least one of a broadcasted PLMN ID, NPN ID, and CAG ID.

[0149] -Service area defined by the 5G core network: for example, UPF service area or SMF service area

[0150] - Information used by the UE to identify the network via a message broadcast from the base station: for example, CSG ID, CAG ID, PLMN ID or NPN ID

[0151] 3) Edge data network application layer access information and authentication information

[0152] -Edge computing enablement server address (URI)

[0153] -Use authorization information: Ex) OAUTH access token

[0154] -Authentication method for application layer authentication

[0155] - Identifier of the service provider operating the edge data network

[0156] <Second Embodiment>

[0157] The second embodiment relates to an edge data network discovery method.

[0158] The UE can distinguish the edge data network by identifying the tracking area and cell list from the LADN information received during the registration process. The UE can receive LADN information from the network through a registration process or a UE configuration update (UCU) process. When LADN is used for edge computing services, the UE can identify whether the LADN DNN is a DNN for supporting edge computing. In addition, the UE can identify the LADN service area information included in the LADN information, and can identify (determine) whether the UE is in an edge data network.

[0159] According to another method for UE to identify (determine) the service area of ​​the edge data network, the UE can identify the service area of ​​the edge data network based on the spatial validity condition included in the UE routing selection policy (URSP) provided to the UE by the PCF of the 5GC network. When configuring a DNN for accessing edge computing services, the UE can identify the spatial validity condition sent together with the relevant URSP policy, and can identify whether the cell or tracking area where the UE currently resides in the 3GPP network is within the spatial validity area, thereby determining whether there is an available edge data network.

[0160] <Third Embodiment>

[0161] The third embodiment relates to a method for establishing an edge data network session. Figure 5 A third embodiment is described.

[0162] Figure 5 The edge data network session establishment process according to the present disclosure is shown.

[0163] according to Figure 5 , the edge data network generation process through the PDU session establishment process is performed according to the following operations.

[0164] In operation 0, it may be determined to generate an edge data network for UE 100. UE 100 may determine to generate an edge data network. UE 100 may discover an edge data network service area by identifying whether UE 100 is in an edge data network area according to the description of the second embodiment, and may identify (determine) whether a base station where UE 100 resides belongs to the edge data network of UE 100. That is, it may be identified (determined) whether a base station where UE 100 resides is in the edge data network service area described in the second embodiment. When it is determined that UE 100 is in an edge data network area, UE 100 may determine to establish a session for accessing the edge data network.

[0165] Operation 1. Transmission of session establishment request message

[0166] When the UE 100 determines to establish a session for accessing the edge data network, the UE 100 may send a session establishment request message to the 3GPP network 200. When the 3GPP network is a 5GC, the UE 100 may send a PDU session establishment request message to the SMF 200. The PDU session establishment request message may include the following information.

[0167] May include DNN, S-NSSAI, UE identifier, edge data network usage indicator, and edge data network operator information.

[0168] 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.

[0169] Operation 2. DN-AAA uses the authorization request to establish a session

[0170] The SMF 200 receiving the session establishment request may determine whether to perform a process of requesting use authorization from the DN-AAA server 500, considering the DNN in the NAI format, the S-NSSAI, and the UE identifier (eg, GPSI) received from the UE 100.

[0171] The SMF 200 may identify (determine) a pre-configured domain name or obtain a domain name from the PCF ( Figure 5 Whether the domain name received and configured by the UE (not shown) matches the domain name included in the UE identifier in the NAI format, and whether the use authorization request is sent to the DN AAA server 500 can be identified (determined).

[0172] The SMF 200 may identify (determine) whether the DNN is configured for edge computing, that is, may determine whether the DNN matches a pre-configured DNN or a DNN received and configured from the PCF, and may identify (determine) whether a usage authorization request is sent to the DN-AAA server 500. The UE identifier may be included in the usage authorization request message sent by the SMF to the DN-AAA server 500.

[0173] Operation 3. Authentication process for session establishment

[0174] The UE 100 and the DN-AAA server 500 may perform an authentication process for session establishment. Here, the UE 100 and the DN-AAA server 500 may perform an authentication process according to the Extensible Authentication Protocol (EAP: RFC 3748).

[0175] Operation 4. DN-AAA uses the authorization response to establish a session

[0176] The DN-AAA server 500 may receive the use authorization request message and may determine whether the use is authorized by the UE identifier included in the request message and the policy and configuration information of the DN-AAA server 500. When the DN-AAA server 500 determines that the use is authorized, the DN-AAA server 500 may send a use authorization message to the SMF 200. The DN-AAA server 500 may send a DN file index.

[0177] The DN-AAA server 500 may send the application layer address (e.g., URI) of the edge enablement server to the SMF 200 through the UE identifier and the policy and configuration information of the DN-AAA server 500, and the UE 100 accesses the edge enablement server via the application layer or domain address (FQDN).

[0178] The DN-AAA server 500 may send edge data network configuration information of the UE 100. The edge network configuration information may be the same as the information described in the first embodiment.

[0179] The above operations 2 to 4 may be collectively referred to as an authentication operation. That is, reference numeral 520 may correspond to an operation of the DN-AAA server 500 authenticating the UE 100 through the 3GPP network 200.

[0180] Operation 5. Authorization to establish session by SMF 200

[0181] SMF 200 may determine whether to authorize UE 100 to use the session. When a session use authorization request is sent to DN-AAA server 500, SMF 200 may determine whether to authorize use of the session requested by UE 100 based on a result included in a use authorization response message from DN-AAA server 500.

[0182] The DN-AAA server 500 may send edge computing related configuration information by using the authorization response message. The edge computing related configuration information may include the edge data network application layer access information and authentication information in the edge data network configuration information described in the first embodiment.

[0183] SMF 200 can determine whether to authorize the use of the session based on the DNN, S-NSSAI and the UE identifier sent by the UE according to the autonomous configuration of the session. In this case, SMF 200 has the edge data network application layer access information and authentication information among the edge data network configuration information configured locally.

[0184] The SMF 200 may receive a DN authorization profile index from the DN-AAA server 500. In this case, the DN-AAA server 500 may receive a policy and charging control (PCC) rule related to a policy control function (PCF) and a policy related to session management. The SMF 200 may receive edge computing related configuration information of the UE 100 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.

[0185] When it is determined that UE 100 is authorized to use the session, SMF 200 may send a successful session establishment response message in operation 6, otherwise, SMF 200 may send a session establishment response message together with an indication of rejecting the session.

[0186] Operation 6. Transmission of session establishment response message

[0187] When SMF 200 determines that the UE is authorized to use the session, SMF may send a session establishment response message to the UE for authorizing the session establishment. The session establishment response message may include edge data network application layer access information. As described in operation 5, the edge data network application layer access information may be information received from the DN-AAA server 500, information autonomously configured by SMF 200, or information received from the PCF.

[0188] <Fourth Embodiment>

[0189] The fourth embodiment relates to the process of accessing the edge activation server. Figure 6 The process shown in .

[0190] Reference Figure 6 A fourth embodiment is described.

[0191] Figure 6 A process for requesting and obtaining edge application information according to the present disclosure is shown.

[0192] In operation 0, the UE 100 may identify an application-level discovery trigger condition in an edge computing environment for accessing the edge enablement server 310. The trigger condition for accessing the edge enablement server is as follows.

[0193] 1) When the following conditions are met, the UE 100 may send a request message to the edge enabling server 310 via an application layer message.

[0194] 2) Transmission may be performed periodically according to the autonomous strategy of the UE 100 .

[0195] 3) When the edge data network is fully established

[0196] 4) When UE 100 detects that it has entered the edge data network service area

[0197] 5) When the information required by the application layer is requested from the UE 100 through the edge enabling layer (or the API provided by the proxy to the upper application layer)

[0198] 6) When it is determined that the information required by the URSP processing layer needs to be received

[0199] Operation 1. Edge application information request message

[0200] The UE 100 may send an edge application information request message to the edge enabling server 310. The edge application information request message may include the following information.

[0201] 1) Operating system installed in UE 100 and application programs requested by UE 100

[0202] 2) Identifier and version information about the software responsible for enabling functions of the UE 100

[0203] 3) Access token, including authorization and authentication information that allows UE 100 to access edge computing resources owned by the UE 100's enabling agent

[0204] 4) Information about the edge application requested by the UE 100, for example, a list of edge applications currently available or installed in the edge hosting platform.

[0205] Operation 2. Edge application information response message

[0206] When receiving the edge application information request message from the UE 100, the edge enabling server 310 may identify the access token information and may check the authentication information. The edge enabling server 310 may identify the authorization of the UE 100 and may send the information requested by the UE 100 to the UE 100. The information sent to the UE 100 includes information required for the UE 100 to provide edge computing services, and an example of the required information is as follows.

[0207] 1) A list of available edge applications and the configuration information in the edge applications required by the UE 100. For example, it may include the DNS server address, the IP address of the edge application, and the FQDN or URL.

[0208] 2) It may include protocols for efficient network transmission with edge applications and their configuration information, such as TCP or UDP preferences, IP version information, and HTTP protocol version information. In addition, it may also include configuration information for transport protocol optimization, such as initial TCP CWND size information.

[0209] 3) List of UE applications that edge computing operators recommend to install on UE

[0210] <Fifth Embodiment>

[0211] The fifth embodiment shows the configuration of an edge data network using LADN. Figure 7 A fifth embodiment is described.

[0212] Figure 7 A process in which a UE obtains LADN information through a registration process in a 5GC network according to the present disclosure is shown.

[0213] The edge data network used to support edge computing can be defined as a 5GC LADN. When the edge data network is defined as a 5GC LADN, the UE can Figure 7 The LADN information may be received during the registration process. The LADN information may include information about the LADN DNN and the LADN service area. The LADN service area may be specified as follows.

[0214] 1) LADN area is specified using the tracking area list

[0215] 2) The LADN area is the same as the entire area of ​​the current operator

[0216] 3) The LADN area is the same as the current registration area

[0217] 4) LADN area is the same as the allowed area

[0218] 5) LADN area is a specific PLMN ID

[0219] 6) LADN service area configuration using cell list

[0220] 7) LADN area is configured using a specific CAG-ID or its list

[0221] 8) LADN area is RAN Notification Area (RNA)

[0222] When performing the registration procedure in operation 1, the UE 100 may send a registration request message.

[0223] In operation 2, the access and mobility management function (AMF) 222 of the 5GC network may send an indicator indicating the LADN area and the type of the LADN area to the UE 100. For example, when the LADN area is the same as the current registration area, the AMF 222 may send a registration acceptance message of the registration process, including an indicator indicating that the LADN area is the same as the current registration area. Optionally, the AMF 222 may send a message including an indicator that the LADN area is included in the 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 222 may include an indicator indicating that the LADN service area is available in the area to which the current PLMN and the equivalent network (equivalent PLMN) belong in the LADN information included in the registration acceptance message of the registration process. When the LADN area is available in an area where a specific equivalent PLMN among the current PLMN is broadcast, the AMF 222 may send a registration acceptance message including the corresponding indicator and equivalent PLMN ID information to the UE 100. When the LADN service area is configured using a cell list, AMF 222 may send the cell list as LADN service area information.

[0224] <Sixth Embodiment>

[0225] The sixth embodiment is shown in reference Figures 8 to 13 The procedures performed in the UE, operator network and application layers in the network deployment scenario described in this document. Fig.14 A sixth embodiment is described.

[0226] Fig.14 The process performed to receive edge computing services when a UE is powered on according to the present disclosure is shown.

[0227] This embodiment shows a power-on process that is generally applied to various deployment scenarios. In each operation, operations that may vary depending on the deployment scenario are compared in the description.

[0228] exist Fig.14 In operation 1 of the present invention, a mobile terminal (MT) 103 performing a modem function of a UE 100 may perform a procedure for initial registration and session establishment of a 3GPP network 200 .

[0229] This process may include both the case where the UE accesses the EPC and the case where the UE 100 accesses the 5GC. When the UE 100 accesses the EPC, the UE 100 and the 3GPP network may perform an initial connection process. When the UE 100 accesses the 5GC, the UE 100 and the 3GPP network 200 may perform an initial registration process and a PDU session establishment process.

[0230] When UE 100 accesses EPC and when UE 100 accesses 5GC, UE 100 can access the Internet through process 1, and the connected Internet network can be called "Internet DN".

[0231] When operation 1 is successfully performed, UE 100 may perform an initial provisioning process using EDN configuration server 340 located in the "Internet DN" in operation 2. This process is the same as the process described in the first embodiment.

[0232] When receiving the configuration information from the EDN configuration server in operation 2, the UE 100 may identify in operation 3 whether the DNN (or APN) information designated as the EDN is the currently established PDU session. That is, the UE 100 may determine whether the DNN (or APN) information is the PDU session established in operation 1. When the operator supports edge computing in the same DN as the DN accessing the Internet in the network deployment scenario 1A or 1B, the EDN configuration information configured by the EDN configuration server 340 is the same DNN information as the DN configured in operation 1. When the DNN (or APN) of the currently established session in the UE 100 is the same as the EDN configuration information, the UE 100 does not establish a separate session.

[0233] When an operator has a network deployment scenario, such as network deployment scenario 2A, 2B, 3A, or 3B, UE 100 may need to establish a separate session to access edge applications.

[0234] When a PDU session (or PDN connection) corresponding to a DNN (or APN) specified in the configuration information received by the UE 100 from the EDN configuration server 340 is not established, the UE 100 may determine that a PDU session needs to be established. Here, depending on the area, the PDU session (or PDN connection) to be established may or may not be provided. In network deployment scenarios 2B or 3B, since it is currently impossible for the UE 100 to establish a PDU session, the UE 100 may determine whether to establish a session by identifying the service area information of each DNN specified in the EDN configuration and the current location of the UE in the network, so as to determine whether it is possible to establish the DNN (or APN) specified in the EDN configuration in the current area.

[0235] When the UE 100 determines that the UE 100 is currently within the EDN service area, the UE 100 may send a request to establish a PDU session (or PDN connection) to the 3GPP network, and the PDU session (or PDN connection) may be established in the 3GPP network.

[0236] When the initial provisioning process according to operation 2 is performed by a trigger condition instead of occurring after the initial registration process (operation 1), the UE may have already established a dedicated DNN (or APN) specified in the EDN configuration information. When a session corresponding to the DNN for EDN configuration specified in the EDN configuration information has been established in the UE 100, the UE 100 does not initiate a session process according to operation 4.

[0237] When the UE 100 determines that no additional session establishment is required in operation 3, or when the additional session establishment is successfully performed in operation 4, the UE 100 may identify whether there is an available edge enabling server 310 in the current area. When there is an available edge enabling server 310 in the current area, the UE 100 may send the received request with the EDN configuration information to the edge enabling server 310 in operation 5. The detailed process of operation 5 may follow Figure 6 process.

[0238] The UE 100 determines to initiate the establishment of a PDU session (PDN connection) according to the received configuration information, so that after receiving the configuration information and determining to access the edge enabling server 310, the details of using the configuration information to access the edge enabling server 310 can be as follows: Fig.15 .

[0239] Fig.15 is a control flow chart in a UE when the UE accesses an edge enabling server according to an embodiment of the present disclosure.

[0240] according to Fig.15 In the initial startup, when the network to be connected is 5GC, the UE 100 may perform an initial registration process in operation 600, and may establish a PDU session for connecting to the Internet DN in operation 602. However, in the initial startup, when the network to be connected is EPC, the UE 100 may perform an initial connection operation in operation 600, and may establish a PDU session for connecting to the Internet DN in operation 602. Subsequently, the enabling client 102 of the UE 100 may start an initial provisioning process in operation 608.

[0241] When the UE periodically receives an initial provisioning procedure, for example, in operation 604, in addition to the initial provisioning procedure performed in the initial startup or when the provisioning information is dynamically updated, for example, in operation 606, the UE 100 can also determine whether the DNN (or APN) received as part of the EDN configuration information is a PDU session currently established in the UE 100.

[0242] Specifically, when the UE 100 periodically receives the initial provisioning procedure in operation 604 , the UE 100 may perform the provisioning procedure in operation 608 , and may then proceed to operation 610 .

[0243] When the provisioning information is dynamically updated in operation 606 , the UE 100 may proceed to operation 610 .

[0244] When the DNN (or APN) received by the UE 100 as part of the EDN configuration information is not currently established in the UE 100 (No in operation 610), the UE 100 may determine whether a PDU session (PDN connection) is available in the current area in operation 612. When the PDU session (PDN connection) is not available in the current area (No in operation 612), the UE 100 proceeds to operation 624 and does not initiate the PDU session (PDN connection). When the PDU session (PDN connection) can be established in the current area (Yes in operation 612), the UE 100 may continue to operation 614 of the UE 100 and may initiate establishment of the PDU session. The UE 100 may successfully establish the PDU session (PDN connection) (Yes in operation 616). When the UE 100 cannot successfully establish the PDU session (PDN connection) (No in operation 616), the UE 100 proceeds to operation 624 and does not initiate the PDU session (PDN connection).

[0245] When a PDU session (PDN connection) is successfully established in the current UE 100 or a PDU session (PDN connection) is established (yes in operation 616), in operation 618, the UE 100 may determine whether the edge enabling server 310 is available at the current location of the UE 100. When the edge enabling server 310 is available at the current location of the UE 100 (yes in operation 618), in operation 620, the edge enabling client 102 of the UE 100 may send an edge application discovery request message to the edge enabling server 310. When a response to the message is received, in operation 622, the UE 100 may receive a list of available edge applications and configuration information about the edge applications.

[0246] When the DNN (or APN) received by the UE 100 as part of the EDN configuration information is not currently established in the UE 100 (No in operation 610), the UE 100 may determine whether a PDU session (PDN connection) is available in the current area in operation 612. When the PDU session (PDN connection) is not available in the current area (No in operation 612), the UE 100 proceeds to operation 624 and does not initiate the PDU session (PDN connection). When the PDU session (PDN connection) can be established in the current area (Yes in operation 612), the UE 100 may initiate establishment of the PDU session of the UE 100 in operation 614.

[0247] Fig.16 A mobile network operator (MNO) model for providing edge computing services is shown.

[0248] According to the mobile network operator model, multiple base stations 201, 202 and 203 are included in the edge network service area, and each base station can communicate with UEs 101-4 and 101-1. The fourth UE 101-4 can be connected to cloud application servers 711-1 and 711-2 connected to the Internet 10 through UDM 723 and edge enabling server 710, where actual data can be sent through UPF 721.

[0249] The first UE 101-1 can access the edge computing network by interworking with the mobile communication network or by connecting to the UFP 722 of the edge network located in the mobile communication network. Therefore, the first UE 101-1 can be provided with services from the edge application servers 320-1 and 320-2 by interacting with the mobile communication network or through the edge computing infrastructure 325 of the edge network located in the mobile communication network. For this service, the edge enabling server 310 can interact with the UDM 723.

[0250] according to Figure 1 The configuration can provide differentiated services based on subscribers, and can implement differentiated services depending on whether edge computing is used and on each edge application or each local area.

[0251] refer to Figure 3 A centralized model, a distributed model, and a hybrid model according to the present invention are described.

[0252] exist Figure 3 In the , edge computing area can be defined as a sub-area of ​​the PLMN application scope. The edge computing area can be a tracking area list or a cell list of the UE 100. The MNO needs to be able to identify the location of the UE in the network geographic area. The UE also needs to be able to identify its location. There can be multiple edge computing areas in a PLMN. A PLMN can include multiple edge network service areas, and each edge network service area can be configured to be non-overlapping. The edge computing service area can be deployed in a distributed manner, and two areas A and B can have Figure 3 Adjacent boundaries shown.

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

[0254] Next, in a distributed model, each edge computing region can be configured to be managed by another edge computing region management entity.

[0255] A hybrid model can be configured as a combination of a centralized model and a distributed model.

[0256] Next, the edge network and configuration information are described.

[0257] The edge network can be connected using a data network or a packet data network to provide edge computing services. The edge network can be configured to be identified by a DNN or an APN. The edge network can be connected through one or more RAN nodes. That is, a wireless UE can access the edge network through an RNA node. The edge network can be supported in the edge network service area. For example, Figure 2 As shown, the UE 100 can be connected to an edge data network connected to the UPF through the RAN to which the UE 100 belongs. When the RAN is not connected to the edge data network, the edge computing service cannot be provided to the UE 100.

[0258] The edge network service area can be identified as a tracking area, a cell list, an SMF service area, or a UPF service area. The edge network may include a collection of network functions that support edge computing. In a 3GPP system, a UE can access an edge computing network through a data network (DN) or a packet data network (PDN) of an evolved packet core network. The UE's connection to the data network can be provided by a 5G core network using a PDU session or an EPC using a PDN connection.

[0259] Next, the edge network configuration is described.

[0260] The edge network configuration may be a collection of configuration information required by the UE. The edge network configuration may include the above reference Figure 4 The information described.

[0261] Fig.17 An edge computing system for centrally managing MNO configurations according to the present disclosure is shown.

[0262] refer to Fig.17 , a mobile network operator (MNO) may include multiple base stations, and each base station may be connected to UPF 221a and 221b. Fig.17 The UPFs 221a and 221b shown in the figure can be connected to edge network A 810 and edge network B 820 respectively. At least one UE 101 among UEs 101, 102 and 103 can be a UE for receiving edge computing services. As shown in reference numeral 701, the first UE 101 can access edge network A 810, thereby being provided with edge data services. To this end, as shown in reference numeral 702, it is necessary to perform operations for authentication / authorization discovery through the edge enabling server 920.

[0263] Fig.17 A case where the core network 930 is a 5GC is shown, and the core network may include an SMF 931, a PCF 932, and a UDM / Authentication Server Function (AUSF) 933. A process for authenticating a UE may be performed between the UDM / AUSF 933 and the edge enablement server 920 (903). List information of edge application servers may be provided between the portal orchestrator 940 and the edge enablement server 920. The portal orchestrator 940 may receive the following information from the application server.

[0264] The UE's application identifier (UE Application Id), DNS information (FQDN), edge application, cloud resources, and geographic area information can be received.

[0265] exist Fig.17 In the method shown, a PLMN includes a single entity (edge ​​enabling server). Therefore, all providers, such as MNOs, can use a single set of edge applications. In addition, the available edge applications may vary depending on the registration. Application authentication can use the USIM certificate or a separate certificate. When using the USIM certificate, the USIM certificate can also be used for authentication.

[0266] Figure 2 The 5GC core network shown in FIG. Fig.17 In addition, a portal orchestrator 940 may also be included. Figure 2 The configuration may correspond to a case including a distributed enabling server for independently operating edge computing services.

[0267] Fig.18 is a signal flow diagram according to an authentication, configuration and discovery process, which is based on a centrally managed MNO configuration according to the present disclosure.

[0268] exist Fig.18 In the example, operations can be performed under the following assumptions. The Bootstrapping Server Function (BSF) as a central enabler is a logical entity responsible for authentication using the 3GPP certificates of the subscribers in the MNO and generating and managing the keys used in the application layer. The central enabler has a database of all the information available in multiple edge networks. The central enabler has a list of all the available edge applications. For example, the central enabler has a list of edge applications in each edge network.

[0269] Fig.18 It is a signal flow chart of a UE receiving a list for receiving edge computing services according to an embodiment of the present disclosure.

[0270] Specifically, in Fig.18 In the embodiment of the present invention, the UE may perform authentication through the BSF 1002. The UE may send a message for requesting configuration information to the central edge enabling server 1001 according to the generated key. In response to the message, the UE may receive information about the locally distributed EDN, including the edge enabling server 1001. The process for requesting an edge application list and receiving an available edge application list when a condition for triggering edge application discovery is met through the edge enabling server 1001 is described.

[0271] In operation 1, UE 101 sends an identifier of UE 101 to BSF 1002. In operation 2, BSF 1002 may request an authentication vector (AV) and a user profile from UDM or AUSF 1003 using the UE identifier, and may receive the AV and user profile for authentication. In operation 3, BSF 1002 may return 401 Unauthorized as a TTP response to the request of UE 101. The message may include RAND and AUTH (information about the authentication of the UE). In operation 4, UE 101 may perform AKA authentication, may verify AUTH, and may generate RES.

[0272] In operation 5, UE 101 may send an HTTP request for RES authentication to BSF 1002.

[0273] In operation 6 and operation 7, the BSF 1002 verifies the RES value received from the UE 101 and generates Ks. When the RES is successfully verified, in operation 8, the BSF 1002 may respond to the UE 101 with 200 OK.

[0274] In operation 9, UE 101 may also perform AKA authentication on Ks according to the 3GPP certificate, thereby generating Ks.

[0275] In operation 10, the UE 101 may send a configuration request message for requesting configuration of the UE 101 to the centralized EES 1004. In operation 11, the centralized EES 1004 may receive a UE identifier sent from the UE 101, that is, an identifier of the client software of the UE, or a bootstrap transaction ID from the UE, so as to verify the configuration request message requested by the UE 101, and may send an authentication request message including the identifier information, an edge service provider name, a server name, etc. to the BSF 1002 having authenticated the UE through operations 1 to 6. The BSF 1002 may identify the identifier or the bootstrap transaction ID of the UE 101 or the UE client stored in operation 7, may identify the configuration file received from the UDM 1003 in the corresponding operation 2, and may determine whether to authorize the edge service of the UE. When the BSF 1002 determines that the UE is authorized to use the edge service, in operation 12, the BSF 1002 may send a response to the authentication request to the edge configuration function (edge ​​configuration server) 1004. The response message to the authentication request includes the authentication key (Ks_NAF) to be used in the edge configuration server, the profile of the authorized user, and the validity period of the authentication key.

[0276] When the edge configuration function 1004 receives the response message, in operation 12, the edge configuration function 1004 may send configuration information including information about the edge network to the UE 101. The network configuration information of the message includes the edge data network configuration information shown in the first embodiment.

[0277] After receiving the configuration information from the edge configuration function 1004, in operation 13, the UE 101 may identify whether a trigger condition for discovering an edge application server occurs, and may send a discovery request to the EES 1005 according to operation 14 when the trigger condition occurs. The trigger condition is as follows.

[0278] 1) When installing a new application on the UE

[0279] 2) When the UE enters the area corresponding to the edge data network configuration information

[0280] 3) When the application installed in the UE generates new traffic

[0281] 4) When the UE is newly powered on

[0282] Based on the message, the edge configuration function 1004 may send a list of available edge applications to the UE 101 .

[0283] Fig.19 is a signal flow diagram according to authentication, configuration and discovery processes when a distributed management MNO is configured according to the present disclosure.

[0284] Fig.19 The process can be performed under the following assumptions. An AA server can be operated by an edge computing service provider. Authentication can use a separate certificate. The edge enabling server can be distributed or located in a central location.

[0285] In operation 1110, the UE 101 performs authentication with the authentication / authorization server using a user identifier or a general public subscription identifier (GPSI: an identifier for identifying a subscriber). After successfully performing the authentication process, the UE 101 and the AA server 1101 issue and share the certificate.

[0286] In operation 6, UE 101 may send a configuration request message to edge configuration function 1103. In operation 7, edge configuration function 1103 may send an authentication request to AA server 1101. In operation 8, AA server 1101 may identify the authentication request, may perform authentication of the UE, and may send a result to edge configuration function 1103.

[0287] In operation 9, the edge configuration function 1103 may request and receive a user profile from a profile database (or UDM) 1102. In operation 10, the edge configuration function 1103 may send edge data network configuration information to the UE 101.

[0288] In operation 14, UE 101 may send a discovery request to edge enabling server 1104. In operation 15, edge enabling server 1104 may request and receive a user profile from profile database 1102. Based on the user profile, in operation 16, edge enabling server 1104 may send a list of available edge applications to UE 101.

[0289] The above details are provided to facilitate understanding of the present disclosure, and the present disclosure is not limited thereto.

[0290] Industrial Applicability

[0291] The present disclosure may be used to provide edge computing services in a wireless communication system.< / domain> < / domain> < / domain> < / domain>

Claims

1. A method for obtaining edge data network (EDN) configuration information by a user equipment (UE) to receive edge computing services in a wireless communication system, the method comprising: Sending an initial configuration request message to the edge data network configuration server using a uniform resource identifier (URI) address of the edge data network configuration server; as well as receiving edge data network configuration information from an edge data network configuration server, The URI address is derived from a public land mobile network PLMN identifier ID. Among them, the edge data network configuration information includes information for establishing an edge data network session, edge data network service area configuration information, and edge computing enabled server address information.

2. The method according to claim 1, wherein: The information for establishing the edge data network session includes at least one of a data network name DNN and an access point name APN.

3. The method according to claim 1, wherein: The edge computing service is provided through an edge data network, which includes a data network or a packet data network for providing edge computing services.

4. The method according to claim 1, wherein: The information used to establish an edge data network session also includes single network slice auxiliary information S-NSSAI.

5. The method according to claim 1, wherein: The edge data network service area configuration information includes network topology information, and The network topology information includes at least one of a tracking area, a cell ID list and a PLMN ID.

6. The method according to claim 1, wherein: The information of the edge computing enabling server address is the URI address of the edge computing enabling server.

7. A user equipment UE for obtaining edge data network EDN configuration information to receive edge computing services in a wireless communication system, the UE comprising: An application client is configured to have an edge computing service and provide edge computing services to users; an edge enabling client configured to perform control of accessing an edge computing server to provide edge computing services; as well as A mobile terminal configured to perform a modem operation to access a wireless communication system, Wherein, the edge-enabled client Controlling the mobile terminal to send an initial configuration request message to the edge data network configuration server using a uniform resource identifier (URI) address of the edge data network configuration server; and Controlling the mobile terminal to receive edge data network configuration information from the edge data network configuration server, The URI address is derived from a public land mobile network PLMN identifier ID. Among them, the edge data network configuration information includes information for establishing an edge data network session, edge data network service area configuration information, and edge computing enabled server address information.

8. The UE according to claim 7, wherein: The information for establishing the edge data network session includes at least one of a data network name DNN and an access point name APN.

9. The UE according to claim 7, wherein: The edge computing service is provided through an edge data network, which includes a data network or a packet data network for providing edge computing services.

10. The UE according to claim 7, wherein: The information used to establish an edge data network session also includes single network slice auxiliary information S-NSSAI.

11. The UE according to claim 7, wherein: The edge data network service area configuration information includes network topology information, and The network topology information includes at least one of a tracking area, a cell ID list and a PLMN ID.

12. The UE according to claim 7, wherein: The information of the edge computing enabling server address is the URI address of the edge computing enabling server.

13. A method for providing edge data network configuration information to a user equipment UE by an edge data network EDN configuration server through a wireless communication system, the method comprising: receiving, from the UE, an initial configuration request message including a uniform resource identifier (URI) address of an edge data network configuration server; as well as Send edge data network configuration information, The URI address is derived from a public land mobile network PLMN identifier ID, and Among them, the edge data network configuration information includes information for establishing an edge data network session, edge data network service area configuration information, and edge computing enabled server addresses.

14. The method according to claim 13, wherein: The information used to establish an edge data network session includes at least one of a data network name DNN, an access point name APN, and single network slice auxiliary information S-NSSAI.

15. The method according to claim 11, wherein: The edge data network service area configuration information includes network topology information, and The network topology information includes at least one of a tracking area, a cell ID list and a PLMN ID.

16. The method according to claim 13, wherein: The information of the edge computing enabling server address is the URI address of the edge computing enabling server.

Images