METHOD FOR EDGE COMPUTING SERVICES AND ELECTRONIC DEVICE THEREOF

The electronic device's MEC service module optimizes authentication and discovery for edge computing services, addressing inefficiencies and power consumption issues in existing technologies by integrating these processes, resulting in faster and more stable service delivery.

JP7590058B2Active Publication Date: 2024-11-26SAMSUNG ELECTRONICS CO LTD
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
JP2021558600
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-03-29
Filing Date
2020-03-27
Publication Date
2024-11-26
Estimated Expiration
2040-03-27

AI Technical Summary

Technical Problem

Existing edge computing technologies for electronic devices face challenges in providing secure and efficient authentication, authorization, and discovery procedures for multi-access edge computing (MEC) services, leading to suboptimal performance and increased power consumption.

Method used

An electronic device equipped with a multi-access edge computing service module performs integrated authentication and discovery operations, utilizing methods like AKA and connection tokens to streamline MEC service access, reducing the need for separate applications and optimizing host selection.

Benefits of technology

This approach enables faster, more efficient, and stable edge computing services by integrating authentication and discovery processes, reducing power consumption and improving overall service quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007590058000001
    Figure 0007590058000001
  • Figure 0007590058000002
    Figure 0007590058000002
  • Figure 0007590058000003
    Figure 0007590058000003
Patent Text Reader

Abstract

Various embodiments of the present disclosure provide a method for supporting an edge computing service and an electronic device thereof. The present disclosure relates to a 5G or pre-5G communication system provided to support a higher data transmission rate after a 4G communication system such as LTE. A method according to an embodiment of the present disclosure is an authentication method for an electronic device for which an edge computing service is provided by an authentication server of a mobile communication system, and includes the steps of: performing a first authentication of the electronic device using an authentication and key agreement (AKA) method with the electronic device (403), and providing first authentication information from the electronic device when the first authentication is successful; and performing a second authentication for the edge computing service of the electronic device (411), and providing second authentication information including a connection token for authentication of the edge computing service from the electronic device when the second authentication is successful.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Various embodiments of the present disclosure relate to a method and an electronic device for supporting edge computing services (e.g., multi-access edge computing (MEC) services). [Background technology]

[0002] In order to meet the increasing demand for wireless data traffic since the commercialization of the 4G communication system, efforts are being made to develop improved 5G or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are referred to as Beyond 4G Network or Post-LTE systems.

[0003] To achieve high data transmission rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (such as the 60 GHz band). To mitigate radio wave propagation loss and increase transmission distances in ultra-high frequency bands, beamforming, massive MIMO (multiple-input multiple-output), full dimensional MIMO (FD-MIMO), array antennas, analog beam-forming, and large scale antenna technologies are being discussed for 5G communication systems.

[0004] Furthermore, to improve the system's network, technologies being developed for the 5G communication system include advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device to device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation.

[0005] In addition, the 5G system includes advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced connection technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access).

[0006] Due to this technological trend, a technology using a channel bonding method for high-speed data transmission is emerging in the WiFi wireless communication system, one of the various wireless communication systems. In the WiFi wireless communication system, the channel bonding technology is used to increase the data transmission rate by bonding an additional band to the basic band. For example, the IEEE802.11ac standard supports a maximum bandwidth of 160MHz by bonding eight 20MHz channels, and the channel bonding technology is also expected to be applied to the IEEE802.11ay standard. When using the channel bonding technology, it is inevitable that the power consumption of electronic devices will increase.

[0007] In recent years, edge computing technology that transmits data using an edge server has been discussed. The edge computing technology may include, for example, multi-access edge computing (MEC) or fog computing. The edge computing technology may refer to a technology that provides data to an electronic device through a separate server (hereinafter, edge server or MEC server) installed in a location geographically close to the electronic device, for example, inside or near a base station. For example, an application that requires low latency among at least one application installed in an electronic device may transmit and receive data through an edge server installed in a geographically close location, rather than through a server located in an external data network (DN) (e.g., the Internet).

[0008] In recent years, services using edge computing technology (hereinafter referred to as "MEC-based services" or "MEC services") have been discussed, and research and development of electronic devices to support MEC-based services is progressing. For example, an application of a mobile communication electronic device can transmit and receive edge computing-based data to and from an edge server (or an application of an edge server) on the application layer. Summary of the Invention [Problem to be solved by the invention]

[0009] In an MEC-based service, for example, a secure environment must be provided between an electronic device (or user), a network, an operator, or an application provider to execute a service. For example, for an MEC service, an edge server (or MEC application) must provide a service (or access) to an electronic device (or client application) that has been authenticated and granted access authorization. For example, an application of the electronic device can communicate with an application of the edge server, and the edge server can authenticate the application of the electronic device and grant authorization according to the authentication result. For example, in an MEC-based service, authorized applications between an electronic device and an edge server can communicate with each other. For example, when authentication between the electronic device and the edge server is completed, a discovery (e.g., MEC discovery) procedure (or MEC service discovery procedure) can be performed.

[0010] On the other hand, when multiple applications are installed in an electronic device, each application can individually communicate with an edge server on an application layer to transmit data based on edge computing. For example, in the past, applications in an electronic device could individually perform authentication, authorization, and discovery procedures for using MEC services.

[0011] In various embodiments, methods and apparatuses are disclosed that can perform MEC applications and provide services based on a more optimal MEC host for an electronic device.

[0012] In various embodiments, methods and apparatuses are disclosed that can perform MEC applications and provide services based on a more optimal MEC host for an electronic device.

[0013] In various embodiments, methods and apparatus are disclosed for performing service discovery operations by an electronic device (eg, a MEC service module) rather than by a separate application.

[0014] In various embodiments, methods and apparatus are disclosed that allow MEC discovery to be performed by an electronic device (e.g., an MEC service module) rather than by an individual application, thereby enabling faster and more efficient discovery and selecting an MEC host that can provide optimal quality.

[0015] In various embodiments, a method and apparatus are disclosed that can provide a stable edge computing service by managing the state of an application and the state of an electronic device in an integrated manner via an MEC service module installed in an electronic device. [Means for solving the problem]

[0016] A method according to one embodiment of the present disclosure is an authentication method for an electronic device to which an edge computing service is provided by an authentication server of a mobile communication system, and includes a step of performing a first authentication of the electronic device using an authentication and key agreement (AKA) method with the electronic device (403) and providing first authentication information from the electronic device when the first authentication is successful, and a step of performing a second authentication for the edge computing service of the electronic device (411) and providing second authentication information from the electronic device including a connection token for authentication of the edge computing service from the electronic device when the second authentication is successful.

[0017] A method according to another embodiment of the present disclosure is an authentication method for an edge computing service in a mobile communication system in which an electronic device of the mobile communication system provides an edge computing service, the method including: performing a first authentication with an authentication server of the mobile communication system using an Authentication and Key Agreement (AKA) method (403) and receiving first authentication information; and performing a second authentication for the edge computing service with the authentication server (411) and receiving second authentication information including a connection token for authentication of the edge computing service.

[0018] A method according to another embodiment of the present disclosure is a method for providing edge computing service information in an electronic device in which an edge computing service is provided by a multi-access edge computing management proxy (MMP) server of a mobile communication system, comprising: receiving a query message of at least one edge computing server including a fully qualified domain name (FQDN) for the MMP from the electronic device; and sending a response message from the electronic device in response to the query, wherein the response message may include a list of applications that can provide edge computing services via the MMP.

[0019] Another method according to the present disclosure is a method for an electronic device to acquire edge computing service information in a mobile communication system providing edge computing services via a multi-access edge computing management proxy (MMP) server, comprising: sending a query message of at least one edge computing server to the MMP, the query message including a fully qualified domain name (FQDN) for the MMP; and receiving a response message from the MMP in response to the query.

[0020] The response message may include a list of applications that can provide edge computing services via the MMP.

[0021] An electronic device according to one embodiment of the present disclosure may include a network interface, at least one application for edge computing services (MEC), a multi-access service agent (MSA) that performs authentication of the electronic device, authentication of the MEC, policy of the MEC, and control by setting a data path for the MEC via the network interface, and a multi-access service enabler (MSE) that sets a session and a path for data transmission with a MEC management proxy server (MMP) of a mobile communication system via the network interface, sends query information and receives response signals, and discovers an MEC application server via the MMP. Effect of the Invention

[0022] According to various embodiments of an electronic device and an operating method thereof, a service can be provided by performing an MEC application based on a more optimal MEC host for the electronic device. According to various embodiments, a service discovery operation can be performed by the electronic device (e.g., a service enabler) rather than an individual application. According to various embodiments, MEC discovery is not handled by an individual application but is performed by the electronic device (e.g., a service enabler), so that discovery can be performed more quickly and efficiently and an MEC host that can provide optimal quality can be selected. According to various embodiments, a stable edge computing service can be provided by integrally managing the state of an application and the state of the electronic device through an MEC service module installed in the electronic device.

[0023] In addition, various advantages may be provided that can be understood directly or indirectly through this document. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 is a block diagram of an electronic device 101 in a network environment 100 according to various embodiments. [Diagram 2] 2 is a block diagram 200 of an electronic device 101 for supporting legacy network communication and 5G network communication according to various embodiments. [Diagram 3] 1 illustrates an electronic device 101 and an external server 300 for supporting an MEC-based service in a network environment according to various embodiments of the present disclosure. [Figure 4] 1 illustrates an example of an authentication procedure according to various embodiments of the present disclosure. [Diagram 5] 1 illustrates an example of an authentication procedure according to various embodiments of the present disclosure. [Figure 6] 1 illustrates an example of an authentication procedure according to various embodiments of the present disclosure. [Figure 7] 1 illustrates an example of an authentication procedure according to various embodiments of the present disclosure. [Figure 8] 4 is a diagram illustrating an example of a policy update operation in an electronic device 101 according to various embodiments of the present disclosure. [Figure 9] 1 is a diagram showing an example of a PDU session setting operation in an electronic device 101 according to various embodiments of the present disclosure. [Figure 10] 1 illustrates an example of a discovery procedure according to various embodiments of the present disclosure. [Figure 11] 1 illustrates an example of a discovery procedure according to various embodiments of the present disclosure. [Figure 12] 11 is a diagram illustrating an example of an operation for acquiring an app list in a discovery procedure according to various embodiments of the present disclosure. [Figure 13] 1 is a diagram illustrating an example in which an application list is provided according to various embodiments of the present disclosure. [Figure 14] 1 is a diagram illustrating an example of a context generation procedure in a discovery procedure according to various embodiments of the present disclosure. [Figure 15] 1 is a diagram illustrating an example of a MEC host selection procedure in a discovery procedure according to various embodiments of the present disclosure. [Figure 16] 11 is a diagram illustrating an example of separately operating a local DNS cache for MEC in an electronic device 101 according to various embodiments of the present disclosure. [Figure 17] 11 is a diagram illustrating an example of operating a local DNS cache for MEC in an MSE 330 in an electronic device 101 according to various embodiments of the present disclosure. [Figure 18] 1 is a diagram illustrating an example of a DNS resolving operation in a discovery procedure according to various embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] FIG. 1 is a block diagram of an electronic device 101 in a network environment 100 according to various embodiments.

[0026] 1, in a network environment 100, an electronic device 101 may communicate with an electronic device 102 via a first network 198 (e.g., a short-range wireless communication network) or with an electronic device 104 or a server 108 via a second network 199 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 via the server 108. According to an embodiment, the electronic device 101 may include a processor 120, a memory 130, an input device 150, an audio output device 155, a display device 160, an audio module 170, a sensor module 176, an interface 177, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a subscriber identity module 196, or an antenna module 197. In some embodiments, the electronic device 101 may omit at least one of these components (e.g., the display device 160 or the camera module 180) or may include one or more other components. In some embodiments, some of these components may be implemented as a single integrated circuit, for example, the sensor module 176 (e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be implemented as embedded in the display device 160 (e.g., a display).

[44] The processor 120 may, for example, execute software (e.g., program 140) to control at least one other component (e.g., hardware or software component) of the electronic device 101 connected to the processor 120, and may perform various data processing or calculations. According to an embodiment, as at least a part of the data processing or calculation, the processor 120 may load instructions or data received from other components (e.g., the sensor module 176 or the communication module 190) into a volatile memory 132, process the instructions or data stored in the volatile memory 132, and store the result data in a non-volatile memory 134. According to an embodiment, the processor 120 may include a main processor 121 (e.g., a central processing unit (CPU) or an application processor (AP)), and an auxiliary processor 123 (e.g., a graphic processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that may operate independently or together with the main processor 121. Additionally or generally, the auxiliary processor 123 may be configured to use less power than the main processor 121 or to be dedicated to designated functions. The auxiliary processor 123 may be embodied separately from the main processor 121 or as part of it.

[0027] The auxiliary processor 123 may, for example, control at least a portion of the functions or states of at least one of the components of the electronic device 101 (e.g., the display device 160, the sensor module 176, or the communication module 190) in place of the main processor 121 while the main processor 121 is in an inactive (e.g., sleep) state, or together with the main processor 121 while the main processor 121 is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor 123 (e.g., an image signal processor or a communication processor) may be embodied as part of another functionally related component (e.g., the camera module 180 or the communication module 190).

[0028] The memory 130 can store various data used by at least one component (e.g., the processor 120 or the sensor module 176) of the electronic device 101. The data can include, for example, software (e.g., the program 140) and input or output data for instructions therefor. The memory 130 can include a volatile memory 132 or a non-volatile memory 134.

[0029] The programs 140 may be stored in the memory 130 as software and may include, for example, an operating system (OS) 142 , middleware 144 , or applications 146 .

[0030] The input device 150 can receive instructions or data from outside (e.g., a user) of the electronic device 101 for use by a component (e.g., the processor 120) of the electronic device 101. The input device 150 can include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus pen).

[0031] The audio output device 155 can output an audio signal to the outside of the electronic device 101. The audio output device 155 can include, for example, a speaker or a receiver. The speaker is used for general purposes such as multimedia playback or recording and playback, and the receiver is used to receive incoming calls. According to an embodiment, the receiver can be embodied separately from the speaker or as a part of the speaker.

[0032] The display device 160 may visually present information to an external (e.g., user) of the electronic device 101. The display device 160 may include, for example, a display, a holographic device, or a projector, and control circuitry for controlling the device. According to one embodiment, the display device 160 may include touch circuitry configured to detect a touch, or sensor circuitry (e.g., a pressure sensor) configured to measure the strength of a force generated by the touch.

[0033] The audio module 170 can convert sound into an electrical signal or vice versa. According to one embodiment, the audio module 170 can obtain sound via the input device 150 or output sound via the audio output device 155 or an external electronic device (e.g., the electronic device 102 (e.g., a speaker or headphones)) connected directly or wirelessly to the electronic device 101.

[0034] The sensor module 176 may detect an operating state (e.g., power or temperature) of the electronic device 101 or an external environmental state (e.g., a user state) and generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, a barometer sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor (e.g., an RGB (red, green, blue) sensor), an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0035] Interface 177 may support one or more specified protocols used to directly or wirelessly connect with external electronic devices (e.g., electronic device 102) of electronic device 101. According to one embodiment, interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0036] The connection terminal 178 may include a connector through which the electronic device 101 may be physically connected to an external electronic device (e.g., the electronic device 102). According to one embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0037] The haptic module 179 can convert the electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive via touch or kinesthetic sensation. According to one embodiment, the haptic module 179 can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0038] The camera module 180 can capture still and video images and, according to one embodiment, can include one or more lenses, an image sensor, an image signal processor, or a flash.

[0039] The power management module 188 may manage the power provided to the electronic device 101. According to one embodiment, the power management module 188 may be embodied, for example, as at least a part of a power management integrated circuit (PMIC).

[0040] The battery 189 can provide power to at least one component of the electronic device 101. According to one embodiment, the battery 189 can include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0041] The communication module 190 can support establishing a direct (e.g., wired) or wireless communication channel between the electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108) and performing communication through the established communication channel. The communication module 190 can include one or more communication processors that operate independently of the processor 120 (e.g., an application processor) and support the direct (e.g., wired) or wireless communication. According to one embodiment, the communication module 190 can include a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (e.g., a local area network (LAN) communication module, or a power line communication module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 198 (e.g., a short-range communication network such as Bluetooth, Wi-Fi direct, or IrDA (infrared data association)) or a second network 199 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or WAN (wide area network))). These various types of communication modules can be integrated into one component (e.g., a single chip) or embodied as multiple separate components (e.g., multiple chips).

[0042] The wireless communication module 192 can use subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identity module 196 to identify and authenticate the electronic device 101 within a communication network, such as a first network 198 or a second network 199.

[0043] The antenna module 197 can transmit or receive signals or power to or from an external device (e.g., an external electronic device). According to an embodiment, the antenna module 197 can include one antenna including a radiator made of a conductor or conductive pattern formed on a substrate (e.g., a PCB). According to an embodiment, the antenna module 197 can include multiple antennas. In this case, at least one antenna compatible with a communication method used in a communication network such as a first network 198 or a second network 199 can be selected from the multiple antennas by, for example, the communication module 190. Signals or power can be transmitted or received between the communication module 190 and an external electronic device via the selected at least one antenna. According to an embodiment, other components (e.g., an RFIC) other than the radiator can be formed as part of the antenna module 197.

[0044] At least some of the components are connected to each other via a peripheral communication method (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and can exchange signals (e.g., commands or data) between each other.

[0045] According to one embodiment, commands or data can be sent or received between electronic device 101 and external electronic device 104 via a server 108 connected to a second network 199. Each of electronic devices 102, 104 can be the same type of device as electronic device 101 or a different type of device.

[0046] According to an embodiment, all or part of the operations performed by the electronic device 101 may be performed by one or more external devices among the external electronic devices 102, 104, or 108. For example, if the electronic device 101 has to perform any function or service automatically or in response to a request from a user or another device, the electronic device 101 may request one or more external electronic devices 102, 104 to perform at least a part of the function or service instead of or in addition to performing the function or service itself. The one or more external electronic devices 102, 104 receiving the request may perform at least a part of the requested function or service, or an additional function or service related to the request, and may transmit the result of the execution to the electronic device 101. The electronic device 101 may process the result as it is or additionally and provide it as at least a part of a response to the request. For this purpose, for example, cloud computing, distributed computing, or client-server computing technologies may be used.

[0047] The electronic device 101 according to various embodiments disclosed herein may be a device of various types. The electronic device 101 may include, for example, a portable communication device (e.g., a smartphone), a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronic device. The electronic device 101 according to the embodiments disclosed herein is not limited to the above devices.

[0048] The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to a specific embodiment, but should be understood to include various modifications, equivalents, or alternatives of the embodiment. In connection with the description of the drawings, similar reference numerals are used for similar or related components. The singular form of a noun corresponding to an item can include one or more of the item, unless otherwise clearly indicated otherwise in the relevant context.

[0049] In this document, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B, or C" may include any one of the items listed in the corresponding phrase, or all possible combinations thereof. Terms such as "first", "second", "first", or "second" are used simply to distinguish the component from other components, and do not limit the component in other aspects (e.g., importance or procedure). When any (e.g., first) component is referred to as "coupled" or "connected" to a different (e.g., second) component, with or without the terms "functional" or "communicative", it means that the component can be connected to the other component directly (e.g., by wire), wirelessly, or via a third component.

[0050] The term "module" as used herein may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integrated component or the smallest unit or part of such a component that performs one or more functions. According to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0051] Various embodiments of this document may be embodied as software (e.g., program 140) including one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) readable by a machine (e.g., electronic device 101). For example, a processor (e.g., processor 120) of the machine (e.g., electronic device 101) may call up and execute at least one of the one or more instructions stored in the storage medium. This allows the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves); the term does not distinguish between data being stored semi-permanently on the storage medium and data being stored temporarily.

[0052] According to an embodiment, the method according to the various embodiments disclosed herein may be provided in a computer program product. The computer program product may be traded between sellers and buyers as a commodity. The computer program product may be distributed in the form of a device-readable storage medium (e.g., CD-ROM, compact disc read only memory) or may be distributed in the form of an application store (e.g., Play Store). TM ) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a part of the computer program product can be at least temporarily stored or temporarily generated on a machine-readable storage medium, such as the memory of a manufacturer's server, an application store server, or an intermediary server.

[0053] According to various embodiments, each of the components (e.g., modules or programs) may include one or more entities. According to various embodiments, one or more of the components or operations may be omitted or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., modules or programs) may be integrated into one component. In such a case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the multiple components prior to the integration. According to various embodiments, operations performed by a module, program, or other component may be performed sequentially, in parallel, iteratively, or heuristically, one or more of the operations may be performed in a different order, omitted, or one or more other operations may be added.

[0054] Before describing various embodiments of the present invention, an electronic device 101 to which an embodiment of the present invention can be applied will be described.

[0055] FIG. 2 is a block diagram 200 of an electronic device 101 for supporting legacy network communications and 5G network communications according to various embodiments.

[0056] 2, the electronic device 101 may include a first communication processor 212, a second communication processor 214, a first RFIC 222, a second RFIC 224, a third RFIC 226, a fourth RFIC 228, a first RFFE (radio frequency front end) 232, a second RFFE 234, a first antenna module 242, a second antenna module 244, and an antenna 248. The electronic device 101 may further include a processor 120 and a memory 130.

[0057] 1, and the network 199 can further include at least one other network. According to one embodiment, the first communication processor 212, the second communication processor 214, the first RFIC 222, the second RFIC 224, the fourth RFIC 228, the first RFFE 232, and the second RFFE 234 can form at least a portion of the wireless communication module 192. According to another embodiment, the fourth RFIC 228 can be omitted or included as part of the third RFIC 226.

[0058] The first communications processor 212 can support establishment of a communications channel in a band used for wireless communications with a first network 292, and legacy network communications over the established communications channel. According to various embodiments, the first network 292 can be a legacy network, including a second generation (2G), 3G, 4G, or long term evolution (LTE) network.

[0059] The second communication processor 214 may support establishment of a communication channel corresponding to a specified band (e.g., about 6 GHz to about 60 GHz) among bands used for wireless communication with the second network 294, and 5G network communication through the established communication channel. According to various embodiments, the second network 294 may be a 5G network defined by 3GPP.

[0060] Additionally, according to an embodiment, the first communication processor 212 or the second communication processor 214 may support establishment of a communication channel corresponding to another specified band (e.g., about 6 GHz or less) among the bands used for wireless communication with the second network 294, and 5G network communication through the established communication channel. According to an embodiment, the first communication processor 212 and the second communication processor 214 may be embodied in a single chip or a single package. According to various embodiments, the first communication processor 212 or the second communication processor 214 may be formed in a single chip or a single package with the processor 120, the auxiliary processor 123, or the communication module 190.

[0061] The first RFIC 222 can convert a baseband signal generated by the first communication processor 212 to a radio frequency (RF) signal of about 700 MHz to about 3 GHz for use in the first network 292 (e.g., a legacy network) during transmission. During reception, an RF signal can be acquired from the first network 292 (e.g., a legacy network) via an antenna (e.g., the first antenna module 242) and preprocessed via an RFFE (e.g., the first RFFE 232). The first RFIC 222 can convert the preprocessed RF signal to a baseband signal so that it can be processed by the first communication processor 212.

[0062] The second RFIC 224 can convert the baseband signal generated by the first communication processor 212 or the second communication processor 214 into an RF signal (hereinafter, 5G Sub6 RF signal) in the Sub6 band (e.g., about 6 GHz or less) used in the second network 294) (e.g., a 5G network) during transmission. During reception, the 5G Sub6 RF signal can be acquired from the second network 294) (e.g., a 5G network) via an antenna (e.g., the second antenna module 244) and pre-processed via an RFFE (e.g., the second RFFE 234). The second RFIC 224 can convert the pre-processed 5G Sub6 RF signal into a baseband signal so that it can be processed by the corresponding communication processor of the first communication processor 212 or the second communication processor 214.

[0063] The third RFIC 226 may convert the baseband signal generated by the second communication processor 214 into an RF signal (hereinafter, 5G Above 6 RF signal) of a 5G Above 6 band (e.g., about 6 GHz to about 60 GHz) used in the second network 294 (e.g., a 5G network). Upon reception, the 5G Above 6 RF signal may be acquired from an antenna (e.g., the second network 294 via the antenna 248) (e.g., a 5G network) and pre-processed via the third RFFE 236. The third RFIC 226 may convert the pre-processed 5G Above 6 RF signal into a baseband signal so that it can be processed by the second communication processor 214. According to an embodiment, the third RFFE 236 may be formed as a part of the third RFIC 22.

[0064] According to one embodiment, the electronic device 101 may include a fourth RFIC 228, either separately from or at least as a part of the third RFIC 226. In such a case, the fourth RFIC 228 may convert the baseband signal generated by the second communication processor 214 to an RF signal (hereinafter, IF signal) in an intermediate frequency band (e.g., about 9 GHz to about 11 GHz) and then transmit the IF signal to the third RFIC 226. The third RFIC 226 may convert the IF signal to a 5G Above 6 RF signal. On reception, the 5G Above 6 RF signal may be received from a second network 294 (e.g., a 5G network) via an antenna (e.g., antenna 248) and converted to an IF signal by the third RFIC 226. The fourth RFIC 228 may convert the IF signal to a baseband signal for processing by the second communication processor 214.

[0065] According to an embodiment, the first RFIC 222 and the second RFIC 224 may be implemented as at least a portion of a single chip or a single package. According to an embodiment, the first RFFE 232 and the second RFFE 234 may be implemented as at least a portion of a single chip or a single package. According to an embodiment, at least one of the first antenna module 242 or the second antenna module 244 may be omitted or combined with another antenna module to process RF signals of corresponding multiple bands.

[0066] According to an embodiment, the third RFIC 226 and the antenna 248 may be disposed on the same substrate to form the third antenna module 246. For example, the wireless communication module 192 or the processor 120 may be disposed on a first substrate (e.g., a main PCB). In this case, the third RFIC 226 may be disposed on a portion (e.g., a lower surface) of a second substrate (e.g., a sub PCB) separate from the first substrate, and the antenna 248 may be disposed on another portion (e.g., an upper surface) to form the third antenna module 246. By disposing the third RFIC 226 and the antenna 248 on the same substrate, the length of the transmission line therebetween may be reduced. This may reduce the loss (e.g., attenuation) of a signal in a high frequency band (e.g., about 6 GHz to about 60 GHz) used in 5G network communication due to the transmission line. As a result, the electronic device 101 may improve the quality or speed of communication with the second network 294 (e.g., a 5G network).

[0067] According to an embodiment, the antenna 248 may be formed as an antenna array including a plurality of antenna elements that may be used for beamforming. In this case, the third RFIC 226 may include a plurality of phase shifters 238 corresponding to the plurality of antenna elements, for example as part of the third RFFE 236. During transmission, each of the plurality of phase shifters 238 may shift the phase of a 5G Above 6 RF signal transmitted to an external (e.g., a base station of a 5G network) of the electronic device 101 via a corresponding antenna element. During reception, each of the plurality of phase shifters 238 may shift the phase of a 5G Above 6 RF signal received from the external via a corresponding antenna element to the same or substantially the same phase. This allows transmission or reception through beamforming between the electronic device 101 and the external.

[0068] The second network 294 (e.g., a 5G network) can be operated independently (e.g., Stand-Alone (SA)) or connected (e.g., Non-Stand Alone (NSA)) to the first network 292 (e.g., a legacy network). For example, the 5G network may only have an access network (e.g., a 5G radio access network (RAN) or a next generation RAN (NG RAN)) and no core network (e.g., a next generation core (NGC)). In such a case, the electronic device 101 can access an external network (e.g., the Internet) under the control of the core network (e.g., evolved packed core (EPC)) of the legacy network after accessing the access network of the 5G network. Protocol information for communication with legacy networks (e.g., LTE protocol information) or protocol information for communication with 5G networks (e.g., New Radio (NR) protocol information) can be stored in memory 230 and accessed by other components (e.g., processor 120, first communication processor 212, or second communication processor 214).

[0069] Hereinafter, the 5G network technology described in the drawings and description may refer to standards defined by the international telecommunication union (ITU) or 3GPP (e.g., technical specification (TS) 23.501), and the MEC technology may refer to standards defined by the European telecommunication standards institute (ETSI) (e.g., MEC001 to MEC016). Hereinafter, the content will be described based on MEC technology, but the same or similar principles may be applied to fog computing technology defined by the openfog consortium.

[0070] FIG. 3 illustrates an electronic device 101 and an external server 300 for supporting an MEC-based service in a network environment according to various embodiments of the present disclosure.

[0071] As shown in FIG. 3, the electronic device 101 of FIG. 3 may represent an example of a software architecture for a MEC AA (MEC Authentication / Authorization) procedure and a MEC discovery procedure.

[0072] According to an embodiment, the electronic device 101 may include an application (hereinafter referred to as a client application (application)) 310 for edge computing services (hereinafter referred to as MEC services), a service agent (e.g., MSA) 320 (hereinafter referred to as MSA 320), and a service enabler (e.g., MSE) 330 (hereinafter referred to as MSE 330). According to an embodiment, the electronic device 101 may include a network interface 340 (e.g., wireless communication module 192 in FIG. 1 or FIG. 2) for establishing a protocol data unit (PDU) session related to data transmission, and may include a network driver (e.g., software driver) that controls the operation of the network interface 340, although not shown. According to an embodiment, the client application 310, the MSA 320, and the MSE 330 may be configured to be installed in the electronic device 101 as software or to have a physical configuration. According to one embodiment, MSA 320 and MSE 330 may be operated as part of a processor (e.g., processor 120 in FIG. 1). According to one embodiment, MSA 320 and MSE 330 may be separate hardware components operated independently of processor 120. According to another embodiment, MSA 320 and MSE 340 may be software (e.g., program 140 in FIG. 1). For example, software-based MSA 320 and MSE 340 may be stored in a memory (e.g., memory 130 in FIG. 1 or FIG. 2) in the form of instructions, and the operations of MSA 320 and MSE 330 may be executed by processor 120.

[0073] According to one embodiment, the client application 310 may include a third party application installed by a user on the electronic device 101. According to one embodiment, the client application 310 may be an application that uses MEC services, such as MEC or fog computing. According to one embodiment, the client application 310 may include an application that uses differentiated services, such as free of charge (FOC) services.

[0074] According to an embodiment, the client application 310 for MEC may refer to an application of the electronic device 101 that connects to an MEC application operated by an MEC host. According to an embodiment, the MEC application may refer to an application that is installed and executed in an MEC host adjacent to a user and communicates with the client application 310. According to an embodiment, the client application 310 may receive authentication through the MSA 320 (e.g., a service agent) that acts as a separate authentication client. According to an embodiment, the client application 310 may connect to a network based on a specific PDU session (e.g., a MEC dedicated PDU session) through the network interface 340, or may connect to the MEC application with an existing PDU session (e.g., a default PDU session) through a DNS proxy function of the MSE 330 (e.g., a service enabler).

[0075] According to an embodiment, the client application 310 for the charge-free service may refer to an application of the electronic device 101 that applies a data charge-free policy. According to an embodiment, when the client application 310 is authenticated through the charge-free authentication MSA 320, a routing rule for the unique identifier (UID) is registered through a client application routing policy (CARP) or a UE route selection policy (URSP), and traffic generated by the UID can be transmitted and received through a non-chargeable dedicated PDU session. According to an embodiment, the URSP indicates a route selection (or setting) policy of the electronic device 101 (e.g., user terminal) defined in the 3GPP standard, and can be included in a non-access stratum (NAS) message and received from the AMF via a modem (or communication processor (CP)) of the electronic device 101. In one embodiment, CARP can be received as an electronic device 101 routing (or configuration) policy defined in various embodiments via an application layer (e.g., MSA 320 or MSE 330) of the electronic device 101, for example in an environment where 3GPP URSP is not available.

[0076] According to an embodiment, the MSA 320 (e.g., a service agent) may process an authentication procedure (e.g., an authentication and authorization (AA) procedure) related to the MEC service with the AA (Authentication / Authorization) server 380 (e.g., an authentication server) of the external server 300. For example, the MSA 320 may include a role of delivering URSP rules and / or MEC connection tokens received as a result of the AA to the MSE 330. According to an embodiment, the MSA 320 may include a role of detecting application events (e.g., launch, termination) or delivering a specific event to an application. According to various embodiments, the MSA 320 of the electronic device 101 may include an AA client 325. According to an embodiment, the AA client 325 may be provided by a manufacturer (or a company) that produces the electronic device 101 or an operator (e.g., a service provider). According to an embodiment, the MSA 320 may perform authentication / authorization (AA) based on the subscriber identity of the electronic device 101 through the AA client 325. The subscriber identity may include, for example, a subscriber identity module (SIM), a universal SIM (USIM), an international mobile equipment identity (IMEI), or a generic public subscription identifier (GPSI). For example, the MSA 320 may be an application (or software) that provides authentication and authorization functions for using a service (e.g., an MSE service) by the MSE 330 through communication with the AA server 380 based on the subscriber identity. According to an embodiment, the MSE service may be a service such as MEC, FOC, MMS, or URLLC (ultra-reliable and low latency communications) that is provided through the MSE 330.

[0077] According to an embodiment, when the MSA 320 receives MSE service authentication and authorization through communication with the AA server 380, it can activate / disable the MSE 330 (e.g., activate / deactivate the MSE service) for the authorized service type using an MSE application programming interface (API), register the UID and rules (e.g., ApnSettings) of the client application 310 available for each service type, and request routing settings. According to an embodiment, the MSE API can include an API provided at an upper application layer in the electronic device 101 for activation / deactivation and routing rule setting for each MSE service type. According to an embodiment, the MSE API can include an API for setting at least one policy, such as a policy for an MEC discovery procedure or a context monitoring policy. According to an embodiment, the client application 310 can access the corresponding service (e.g., MEC, FOC) through the authentication and authorization procedure with the MSA 320.

[0078] According to an embodiment, when the MSA 320 is implemented by an operator (e.g., a service provider), for example, when the operator directly develops an MSA (e.g., an operator MSA) that uses an MSE service, the MSA 320 can directly perform an authentication and authorization procedure for using the MSE service through the AA server 380. According to an embodiment, the MSA 320 can receive a routing rule for each application (e.g., DNN (data network name (=APN in LTE)) information when using a dedicated PDU session) from the AA server 380 in the authentication and authorization procedure. According to an embodiment, the MSA 320 can perform an authentication and authorization procedure between the MSA 320 and the electronic device 101 in order to use the MSE API. For example, when the MSA 320 is installed in the electronic device 101 in advance, it can be authenticated with a platform key through signing of the MSA app APK. According to an embodiment, when the electronic device 101 includes (or supports) an authentication module, the MSA 320 may obtain the right to use the MSE API through a separate authentication procedure with the authentication module in the electronic device 101 after the MSA 320 is installed. According to an embodiment, when the MSE service authentication procedure is completed, the MSA 320 may call the MSE API based on the received policy to create / terminate a PDU session and set routing rules.

[0079] According to an embodiment, the electronic device 101 may set a data path (e.g., path A, path B, or path C) to pass through at least one of various entities (e.g., MEC enabling layer (MEL) 331, URSP handling layer (UHL) 333, or domain name system (DNS) handling layer (DHL) 335)) of the MSE 330 when setting a data path for an MEC application. According to an embodiment, the electronic device 101 may set a data path differently depending on whether a default PDU session is used (e.g., path A) or a separate dedicated PDU session is used (e.g., path B or path C) when setting a data path for an MEC application. According to an embodiment, when a separate dedicated PDU session is used, the data path of path B or path C may be determined depending on whether an MEC discovery procedure is performed via the MEL 331 of the MSE 330.

[0080] According to an embodiment, the MSA 320 can directly request the UHL 333 of the MSE 330 to configure a dedicated PDU session (e.g., set the service path to path C) without going through the MEL 331 of the MSE 330. For example, when a sponsored application is executed in the electronic device 101, if a specific server or network is previously reserved, the MSA 320 can request the UHL 333 to provide the corresponding service through a dedicated PDU session. According to an embodiment, the MSA 320 can further generate separate information for identifying the service in the UHL 333 or receive and provide the separate information from an external server.

[0081] According to various embodiments, the electronic device 101 can include an MSE 330 (eg, a service enabler) at a layer below the MSA 320 .

[0082] According to an embodiment, the MSE 330 may provide an MSE API to the MSA 320 so that the client application 310 can use the MEC service (or MSE service) via the MSA 320, thereby allowing a routing table for a PDU session used by each application to be set. According to an embodiment, the MSE 330 may set a routing table for a PDU session path used by each application ID or URI, and store it in a memory (e.g., the memory 130 of FIG. 1 or FIG. 2). According to an embodiment, the MSE 330 may set at least one of the application ID and the URI as a setting target for the PDU session path. The URI may include a domain name or an IP address format. For example, the PDU session path setting by the application ID may be set as, for example, "AppID 1: PDU session 1, AppID 2: PDU session 1, AppID 3: PDU session 2". For example, the PDU session path setting by the URI may be set as, for example, "URI 1: PDU session 1, URI 2: PDU session 2". For example, PDU session path setting for each application ID and URI can be set as, for example, "AppID 1 & URI 1: PDU session 3, AppID 2 & URI 1: PDU session 1."

[0083] In one embodiment, MEC services may refer to procedures required to use MEC applications (or mobile edge (ME) applications), services provided through MEC applications, and information-related services provided to MEC applications. In one embodiment, the MSE 330 may support additional functions for MEC services, such as MEC service discovery, location verification, route selection, performance verification, or mobility support.

[0084] According to various embodiments, the MSE 330 may be configured with a dedicated PDU session or a basic PDU session to provide a specific service while connected to at least one MEC host (or MEC application). According to one embodiment, information required for configuring a dedicated PDU session or a basic PDU session may be received from the AMF / PCF server 390 via non-access stratum (NAS) information, for example, by a modem (or a communication processor, CP) of the electronic device 101.

[0085] According to one embodiment, the MSE 330 may include a MEL 331, a UHL 333, and a DHL 335.

[0086] According to one embodiment, the MEL 331 may perform operations necessary for using MEC services among the MSE services. For example, the MEL 331 may handle operations such as MEC service registration, MEC service discovery, route selection (e.g., DNN handling), performance pre-measurement, location services, and / or mobility handling.

[0087] According to one embodiment, MEC service registration may be performed by authenticating whether to subscribe to an MEC service from the MMP server 370 (or LCM proxy server) or MEC solution provider server based on the USIM or account (e.g., log-in) information of the electronic device 101, receiving a token (e.g., a cookie) corresponding to an MEC service authorization level and storing it in a memory (e.g., memory 130 of FIG. 1 or FIG. 2). Subsequent MEC services may make service requests using the token during the validity period of the token.

[0088] According to one embodiment, when the electronic device 101 enters an area where the MEC service is available (e.g., when connecting to a specific cell ID or entering a LAN area), the MEL 331 detects this, receives at least one of an app list (e.g., an MEC App (name) list) or a domain name (e.g., a domain name for each MEC application) available in the area, and can perform various functions according to user settings. For example, the MEL 331 can provide available MEC application notification, DNS proxying, and / or MEC application activation according to user settings. According to one embodiment, the MEL 331 can provide notification of available MEC applications. For example, currently available MEC applications can be displayed in a notification window or an application icon (e.g., an app icon). According to one embodiment, the electronic device 101 can also be notified of the installation of a client application corresponding to the MEC application.

[0089] According to an embodiment, the MEL 331 can provide DNS proxying. For example, when a DNS query occurs for a domain name in order for a client application to connect to an MEC application, if at least one of the application name or the DNS query matches the MEC application list, the MEL 331 can send the DNS query to a DNS server for MEC, receive a connection IP address for the MEC application, and return it to the client application 310. According to an embodiment, the IP address can be stored in a DNS cache for MEC in the electronic device 101, for example, for a valid period. MEC DNS resolving for a domain name on the MEC application list can be performed by the MEL 331 itself, separately from the DNS query of the client application, and stored in the DNS cache for MEC.

[0090] According to one embodiment, the MEL 331 can provide MEC application activation. For example, if an MEC client application installed in the electronic device 101 is in use or is expected to be used, activation (e.g., instantiation) of an associated MEC application can be requested. According to one embodiment, if the MEC application is not installed in the MEC host in the region where the electronic device 101 is connected, installation can be requested (e.g., including a package URI).

[0091] According to one embodiment, the route selection (e.g., DNN handling) can set a routing rule for the UID of the client application when it is desired to use a dedicated PDU session for the MEC service or MEC application instead of using a basic PDU session. According to one embodiment, the MSE 330 can receive dedicated DNN information for the MEC service or MEC application from a predefined profile or the AA server 380 and request the creation of a MEC dedicated PDU session using a UHL API (not shown).

[0092] According to one embodiment, the performance pre-measurement may include, for example, the MEL 331 performing a pre-performance test on a plurality of candidate MEC hosts. For example, the MEL 331 may select an optimal MEC host through a pre-performance (e.g., ping probing, bandwidth estimation) test.

[0093] According to one embodiment, location services may include, for example, providing services based on a region in which electronic device 101 is located. According to one embodiment, MEL 331 may provide information regarding service availability (or location accuracy) at the location of electronic device 101. For example, information regarding service availability may include information such as location confirmed, location not found, or location spoofed.

[0094] According to one embodiment, the mobility handling may provide handling for service continuity in an area where a handover occurs, for example, the MEL 331 may handle a handover from a MEC host to another MEC host or a handover from a MEC host to a remote host.

[0095] According to one embodiment, the MEL 331 can identify the type of service and control for discovery of MEC applications of the MEC host through communication with the MMP server. For example, the MEL 331 can identify the service by a predefined MSE API call. For another example, the MEL 331 can identify the service by a policy received from an operator server (e.g., the AA server 380) or the MMP server 370.

[0096] According to an embodiment, the MEL 331 sets a service path (e.g., path A) via the DHL 335 in response to a service identification result, for example, in the case of a service using a basic PDU session, so that the MEL 331 and the DHL 335 can provide the MEC service. According to an embodiment, in the case of data path A for an MEC application, the MEL 331 can be configured to provide the service via a basic PDU session. According to another embodiment, the MEL 331 sets a service path (e.g., path B) via the MEL 331, the UHL 333, and the DHL 335 in response to a service identification result, for example, in the case of a service using a dedicated PDU session, so that the service can be provided by the MEL 331, the UHL 333, and the DHL 335. According to an embodiment, in the case of data path B for an MEC application, the MEL 331 can be configured to request the UHL 333 to provide the service via a dedicated PDU session. According to one embodiment, the MSA 320 may provide additional information to the MEL 331 to identify the various services described above, or the MEL 331 may receive (or obtain) relevant information from the MMP server 370 .

[0097] According to one embodiment, the UHL 333 can request a dedicated PDU session for each service type by calling an API and bind to the dedicated PDU session set for the corresponding application.

[0098] According to one embodiment, the DHL 335 can support DNS pre-resolving or DNS proxy functions for third-party applications. For example, when a client application for MEC generates a DNS query for a specific service connection while connected to data through an existing basic PDU session, the DNS proxy intercepts the DNS query and transmits the query to a DNS server using the MEC domain name, or returns the MEC domain IP address by performing a lookup in the DNS cache. This allows third-party applications to provide MEC services without additional software modifications and without the operator having to perform additional traffic filtering (or steering).

[0099] According to an embodiment, the AA server 380 can provide authentication and authorization for use of the MSE service. According to an embodiment, the MSA 320 of the electronic device 101 can receive authorization for each service type according to authentication and subscriber information through the AA server 380. According to an embodiment, the MSA 320 can also authenticate an MSE service-enabled client application. According to an embodiment, the authentication procedure between the AA server 380 and the MSA 320 of the electronic device 101 does not go through a separate PDU session, but can use a basic PDU session currently connected to the Internet via a communication such as LTE or Wi-Fi.

[0100] According to an embodiment, the MMP server 370 may refer to a proxy server that communicates with the electronic device 101 for authentication or MEC control of the electronic device 101. According to an embodiment, the MMP server 370 may exchange request / response messages based on, for example, HTTP (hypertext transfer protocol). According to an embodiment, if the electronic device 101 can directly communicate with the AA server 380 or the MEC solution providing server, the LCM proxy may not be necessary. For example, when using a server API provided by the LCM proxy, the authentication request message of the MSA 320 may be forwarded to the AA server 380 for authentication, and the MEC control message may be transmitted to the MEC solution providing server. In various embodiments, the interface API between the MSA 320 and the MMP server 370 or the entitlement server may be omitted, and information required for the AA procedure (e.g., authentication and authorization procedure) may be received in advance.

[0101] According to one embodiment, when MEC is supported in the 5G NR (new radio) standard, for example, MMP information and URPS rules are registered in the PCF, and the AMF (access and mobility function) / PCF (policy control function) server 390 can receive the information from the AMF via NAS signaling.

[0102] As described above, according to various embodiments, the MSA 320 can communicate with the AA server 380 to perform authentication and request desired information (e.g., authentication and authorization), and can receive and acquire the requested information from the AA server 380. According to various embodiments, the MSE 330 can communicate with the MMP server 330 to request desired information and can receive and acquire the requested information from the MMP server 330. For example, the MSE 330 can communicate with the MMP server 370 to obtain an MEC app list, or can perform an MEC service discovery procedure and establish a connection with at least one specific MEC host (or MEC application).

[0103] According to various embodiments, based on the electronic device 101 including the MSA 320 and the MSE 330 as described in the description section with reference to FIG. 3, when setting up a data path for an MEC application, various service scenarios can be provided as follows:

[0104] 1. First data path (e.g., path A) scenario (e.g., MSE on Single PDU Session)

[0105] A scenario of a first data path (e.g., path A) according to an embodiment may represent a scenario in which a client application connects to an MEC application using a basic PDU session (or public data network (PDN) connection) currently being used for internet data. According to an embodiment, the MEL 331 may perform an MEC discovery procedure, request an MEC application to be run and connected to an MEC host close to the electronic device 101, and receive a URI of the MEC application. When the client application 310 requests to connect to the MEC application, the connection may be made using an MEC application IP address obtained through DNS resolving for the URI. According to an embodiment, in the scenario of the first data path (e.g., MSE on Single PDU Session), a separate PDU session for the MEC service is not used, so the UHL 333 that controls the URSP rules may not be involved in the operation.

[0106] 2. Scenario B (e.g., MSE on Multiple PDU Sessions with MEL) for the second data path (e.g., path B)

[0107] A scenario of a second data path (e.g., path B) according to one embodiment may represent a scenario in which a client application generates a separate MEC-dedicated PDU session in addition to an existing Internet basic PDU session (or PDN connection) and connects to an MEC application. In one embodiment, the MEC dedicated PDU session can be generated by the MSA 320 or an authorized client application 310 via the UHL 333 using the MSE API according to the policy of an operator (e.g., a mobile network operator (MNO)) or the MMP server 370). In one embodiment, the MEC dedicated PDU session can be one or more PDU sessions that are always open in addition to the basic PDU session, and can be dynamically generated or released at a request of the MEL 331 as needed at a specific time. In one embodiment, the UHL 333 of the MSE 330 can support traffic for the client application (or UID) or connection URI to be routed to the MEC dedicated PDU session according to a predefined rule (e.g., a CARP or URSP rule) or a routing rule received from an external server (e.g., the MMP server 370, the AA server 380, or the AMF / PCF server 390).

[0108] 3. Third Data Path (e.g., Path C) Scenarios (e.g., MSE on Multiple PDU Sessions without MEL)

[0109] The third data path scenario according to an embodiment may represent a scenario in which only a dedicated PDU session is generated and used for a specific service without the function of the MEL 331. According to an embodiment, a separate dedicated PDU session may be generated in the MSA 320 or the authenticated client application 310 using the MSE API, and an application (e.g., UID) rule using the PDU session may be registered so that traffic of the application may be routed through the PDU session. According to an embodiment, a third data path scenario (e.g., MSE on Multiple PDU Sessions without MEL) may be used not only for MEC but also for various types of services (e.g., FOC, MMS, or URLLC) that require a dedicated PDU session.

[0110] According to various embodiments of the present invention, the electronic device 101 includes a network interface 420 and a processor 120, and the processor 120 can use the network interface to obtain information about applications that can be provided by at least one external server that can be connected to a base station or via the base station, select an external server including an application corresponding to specified conditions based on the information about the application, and transmit data to the selected external server.

[0111] According to various embodiments, the processor 120 can send a request message to the at least one external server requesting information about the application, receive a response message from the at least one external server including information about the application, and obtain information about the application from the response message.

[0112] According to various embodiments, the processor 120 may specify conditions regarding information about the application in the request message and transmit the request message to the at least one external server.

[0113] According to various embodiments, the request message may include at least one of a clientappName, a locationInfo, a device Type, a service Type, a context Type, or a URI Request.

[0114] According to various embodiments, the response message may include at least one of a reference URI, a client App Name, a client App Package URL, a uri TTL, a uri LOC, a carp Rule, a DNN, an S-NSSAI, an accessType, a sessionType, an mptcp, or an fqdnList.

[0115] According to various embodiments of the present invention, the electronic device 101 includes a network interface 420 and a processor 120, and the processor 120 can obtain an app list of applications that can be served from a designated external server based on a discovery policy, obtain information related to an application to be associated with and connected to a client application of the electronic device from the designated external server based on the app list, determine a host for data transmission based on the obtained information, and transmit data to the host.

[0116] According to various embodiments, the processor 120 may include a service agent that communicates with the external server to perform operations related to authentication and authorization, and a service enabler that communicates with the external server to obtain an app list and perform operations related to discovery.

[0117] According to various embodiments, the processor 120 may activate the service enabler via an API between the service agent and the service enabler, and perform a discovery procedure with the external server via the service enabler.

[0118] According to various embodiments, the processor 120 may include setting the discovery policy in the service enabler in the service agent, the discovery policy including a client application name (client App Name) and a discovery policy (discoveryPolicy), and the discovery policy (discoveryPolicy) may include at least one of whether to use a dynamic DNN (dynamicDnn), location information (locationInfo), a device type (deviceType), a service type (serviceType), or a context type (contextType).

[0119] According to various embodiments, the processor 120 can activate the service enabler based on receiving the discovery policy from the service agent and can constantly request a list of apps that satisfy the conditions specified by the discovery policy from a proxy server via the service enabler.

[0120] According to various embodiments, if there is no application related to the client application in the app list, the processor 120 may request a URI of the application from a proxy server via the service enabler, and if there is an application related to the client application in the app list, the processor 120 may send the URI of the application to the proxy server including the application name of the application.

[0121] According to various embodiments, the processor 120 can obtain an application package URI for downloading or installing the application from the proxy server if the application is not present on the proxy server.

[0122] According to various embodiments, the processor 120 may perform a DNS query with a URI for the application via the service enabler and store an IP address obtained in a DNS response corresponding to the DNS query in a local DNS cache.

[0123] According to various embodiments, the processor 120 may be configured to select a host based on additional information when a candidate IP list for multiple hosts is received from the external server, and the additional information may include information regarding host location, user current location, user speed, or host performance.

[0124] The electronic device 101 according to various embodiments of the present invention includes a network interface 420 and a processor 120, and the processor 120 can obtain an app list of applications that can be served from a designated external server based on a discovery policy, obtain information related to an application to be associated with and connected to the client application from the designated external server based on an event related to context generation by a client application, select a host for data transmission based on the obtained information, and transmit data to the host.

[0125] According to various embodiments, the event related to the context generation may include at least one of execution of the client application, a context generation request by the client application, or a DNS query being generated by the client application.

[0126] According to various embodiments, the discovery policy may include a client application name (clientAppName) and a discovery policy (discoveryPolicy), and the discovery policy (discoveryPolicy) may include at least one of whether to use a dynamic DNN (dynamicDnn), location information (locationInfo), a device type (deviceType), a service type (serviceType), or a context type (contextType).

[0127] According to various embodiments, the processor 120 can request a proxy server for a list of apps that meet the conditions specified by the discovery policy.

[0128] According to various embodiments, the processor 120 can be configured to request a URI of the application from the proxy server if the application related to the client application is not present in the app list, and to send the application to the proxy server including the application name of the application if the application related to the client application is present in the app list, and to obtain an application package URI for downloading or installing the application from the proxy server if the application is not present in the proxy server.

[0129] According to various embodiments, the processor 120 may perform a DNS query on a URI for the application and store the IP address obtained in the DNS response corresponding to the DNS query in a local DNS cache.

[0130] The following describes various exemplary embodiments of the electronic device 101. For example, the following describes various operations of receiving authentication and authorization (e.g., AA (authentication / authorization)) and policies (e.g., app routing policy, discovery policy, or monitoring policy) according to various exemplary embodiments of the electronic device 101 including the MSA 320 and the MSE 330, and performing route setup and MEC discovery procedures based on the received policies.

[0131] The operations performed by electronic device 101 described below may be performed by at least one processor (e.g., at least one processor including processing circuitry, such as processor 120 of FIG. 1) of electronic device 101. According to one embodiment, the operations performed by electronic device 101 may be performed by instructions that are stored in a memory (e.g., memory 130 of FIG. 1) and that, when executed, cause processor 120 to operate.

[0132] According to various embodiments, the electronic device 101 may perform wireless communication via an access node (not shown in the drawings) disposed between the MMP (MEC Management Proxy) server 430 and the electronic device 101 .

[0133] For example, a network entity may be shown that interacts with a MEC service module (not shown in the drawing) including a service agent 320 (e.g., MSA, multi-access service agent) and a service enabler 330 (e.g., MSE, multi-access service enabler) in the electronic device 101 for an edge computing service (e.g., MEC service).

[0134] According to various embodiments, in the example of FIG. 3, authentication, authorization, and discovery procedures may be performed in a control path (e.g., MEC control plane) interoperating between the service agent (e.g., MSA) 320 and the service enabler (e.g., MSE) 330 and the MMP server 370. According to one embodiment, after the discovery procedure, an MEC data service may be provided through a data path (e.g., MEC user plane) between the application (e.g., App 1, App 2) of the electronic device 101 and the MEC application (e.g., MEC App 1, MEC App 2 - not shown in the drawings) connected to the MMP server 370. Although not shown in FIG. 3, the electronic device 101 may perform data communication with a DNS server through a domain name system (DNS) query / response data path.

[0135] According to one embodiment, the MMP server 370 can provide a user application interface (see ETSI MEC 016 standard) for an edge computing system (e.g., MEC system) to a user equipment (UE) (e.g., electronic device 101). For example, the electronic device 101 can request information about applications that can be provided by the MEC system (e.g., available application list) from the MMP server 370, and can transmit a request to execute (e.g., context creation) and a request to terminate (e.g., context termination) a specific application to the MEC system. For example, the MMP server 370 can manage the life cycle of an application installed in the MEC system. For example, the MMP server 370 can receive a request from the electronic device 101, transmit the received request to the MEC system, and manage the life cycle of an application installed in the MEC system.

[0136] According to one embodiment, the MEC service module may include a service agent (e.g., MSA) 320 and a service enabler (e.g., MSE) 330. According to various embodiments, the MEC service module may receive and process authentication and authorization (e.g., AA) and policies (e.g., app routing policy, discovery policy (or monitoring policy) (e.g., monitoring information list)) according to various embodiments. According to one embodiment, the MEC service module may receive the AA and policies (e.g., monitoring information list) using the service agent (e.g., MSA) 320, and perform route setup and MEC discovery procedures based on the received policies using the service enabler (e.g., MSE) 330.

[0137] According to various embodiments, the MEC service module may operate such that at least one of an entity (e.g., a service agent (MSA) 320 or a service enabler (MSE) 330) within the MEC service module monitors MEC discovery conditions and transmits the results of the monitoring by the entity to the service enabler (MSE) 330. According to one embodiment, the MEC service module may obtain (or receive) AA and discovery related policies via the service agent (MSA) 320. According to one embodiment, when the service agent 320 performs monitoring, the service agent 320 may monitor MEC discovery conditions, and when the conditions are met, an MEC discovery request may be transmitted to the service enabler (MSE) 330, and an MEC discovery procedure may be performed via the service enabler 330. In another embodiment, when the service enabler 330 performs monitoring, the service agent 320 transmits a policy to the service enabler 330, and the service enabler 330 monitors the MEC discovery conditions according to the transmitted policy and performs the MEC discovery procedure when the conditions are met.

[0138] According to an embodiment, the service agent 320 may monitor context information of the electronic device 101. The context information may refer to at least one of, for example, information on an application that supports data transmission based on MEC among applications installed in the electronic device 101, information on the mobility of the electronic device 101, application life cycle information, information on the state of the electronic device 101, information acquired by a sensor, or network performance. The information on the mobility of the electronic device 101 may include, for example, at least one of information indicating the movement of the electronic device 101, information on a change in a base station connected to the electronic device 101, or information on whether the electronic device 101 enters a specified area. The specified area may refer to, for example, at least one of a local area data network (LADN), a tracking area (TA), a cell of a base station, an area where a handover between base stations occurs, or an area determined by a location-based service (e.g., a location measurement technology based on cellular, satellite, or wireless fidelity (Wi-Fi)). The application life cycle information may indicate, for example, a state (e.g., a life cycle) of an application having a series of periods. The information on the status of the electronic device 101 may refer to at least one of, for example, an on / off status of a display (e.g., the display device 160 in FIG. 1), a battery (e.g., the battery 189 in FIG. 1) status, a memory (e.g., the memory 130 in FIG. 1) usage status, a received signal strength, time-out information, or a CPU (e.g., the processor 120 in FIG. 1) usage status. The information acquired by the sensor may refer to, for example, information acquired by the sensor module 176 illustrated in FIG. 1. The network performance may refer to, for example, at least one of a frequency bandwidth or a latency of a network to which the electronic device 101 is connected. The service agent 412 according to various embodiments will be described in detail with reference to the drawings below.

[0139] According to one embodiment, the service enabler 330 can manage (or process) the MEC-based data transmission of the application based on the monitored context information.

[0140] For example, instead of multiple applications individually requesting information from the MMP server 370, the service enabler 330 in various embodiments can reduce the load on the electronic device 101 by requesting or receiving information related to applications (e.g., MEC applications) that the MEC system can provide from the MMP server 370 when an event related to the mobility of the electronic device 101 is detected.

[0141] For another example, the service enabler 330 may determine whether at least one of the MEC applications or applications included in the electronic device 101 satisfies a specified condition for enabling MEC-based data transmission, and may notify the at least one application that satisfies the specified condition to perform MEC-based data transmission. If at least one application that satisfies the specified condition is not installed in the electronic device 101, the service enabler 330 may guide the application layer 446 and / or a framework (e.g., middleware 144 and / or OS 142) to install the application. For example, a new application may be installed in the electronic device 101 at the request of the application layer 310. In various embodiments, the electronic device 101 may receive (or obtain) information for the new application (e.g., a URI or IP address, an application name) from the MEC system.

[0142] For example, when a specified condition (hereinafter, a second condition) related to life cycle synchronization is detected, the service enabler 330 may request life cycle synchronization from the MMP server 370 (e.g., an LCM proxy server) or the edge server (or MEC server), thereby reducing resource consumption of the edge server. For example, the service enabler 330 may notify the MMP server 370 whether an application is to be used. According to one embodiment, the MEC application may operate (e.g., transmit data) only when the application is in use, and may stop operating (e.g., transmit data) when the application is unused (e.g., at least one of screen off, change in client application background state, and user movement speed being equal to or greater than a certain level is satisfied). According to one embodiment, the service enabler 330 may efficiently manage resources of the MEC host (or edge server) by notifying the MMP server 370 whether an application is to be used as described above. According to one embodiment, the resource allocation of the MEC application may be released for unused applications, thereby reducing resource consumption of the MEC host.

[0143] For example, unlike a method in which multiple applications individually perform authentication procedures for MEC-based data transmission, the service enabler 330 can reduce network load by performing authentication procedures for the electronic device 101 in an integrated manner with the MMP server 370 (or edge server).

[0144] FIG. 4 is a diagram illustrating an example of an authentication procedure according to various embodiments of the present disclosure.

[0145] As shown in FIG. 4, the electronic device 101 may include an MSA (or service agent) 320 (including, for example, an AA client 325) and an MSE (or service enabler) 330 (including, for example, an MEL 331, a UHL 333).

[0146] 4, in operation 401, the MSA 320 of the electronic device 101 may send a message (e.g., a first request message) for an authentication (e.g., first authentication) request to the AA server 380 based on at least one specified authentication method (e.g., first authentication). According to one embodiment, the MSA 320 may request authentication with the AA server 380 using a generic public subscription identifier (GPSI)-based Application-layer AKA method, an ID / password-based Login method, or a GBA method.

[0147] In operation 403, MSA 320 may perform authentication with AA server 380. According to one embodiment, MSA 320 may perform GPSI-based user authentication with AA server 380.

[0148] In operation 405, when the AA server 380 receives an authentication request from the electronic device 101, it performs authentication with the electronic device 101, and when the authentication is completed (e.g., the authentication procedure is completed), it can provide (or transmit) authentication information (e.g., first authentication information) according to the authentication result to the electronic device 101 (e.g., MSA 320). According to one embodiment, the authentication information can include, for example, MMP related information (hereinafter, MMP Info) and an authorization code (hereinafter, Auth Code). According to one embodiment, the MMP server 370 can provide the authentication information by further including at least one of additional (or selective) required information, for example, an ID_token for authentication or CARP or URSP rules for MEC data service, in addition to the above information.

[0149] According to an embodiment, the MMP Info may include information related to the connection of the MMP server 370 (e.g., MMP connection address). For example, the MMP Info may include address information of the new MMP server 370 to be connected (e.g., URI (uniform resource identifier) ​​or IP address) and information related to the validity time and / or location of the information. According to an embodiment, the Auth Code may include a code (e.g., OAuth2.0-based) required to request a connection token (e.g., MAT, MEC access token) from the MMP server 370. According to an embodiment, the CARP or URSP rule may include, for example, related information (e.g., DNN) for PDU session setup, information related to an application (or application group) available for each DNN, or information related to a DNN list that can be set later or the maximum number of DNNs that can be set.

[0150] In operation 407, once the authentication procedure with the AA server 380 is completed, the MSA 320 can perform a policy update with the MSE 330 (e.g., PDU session setup). According to one embodiment, the MSA 320 can perform PDU session setup according to a CARP rule or a URSP rule (e.g., DNN). For example, the MSA 320 can identify a policy for whether to perform PDU session setup according to a CARP rule or a URSP rule, and can transmit a PDU session setup request to the MSE 330 via the MSE API according to the CARP rule or the URSP rule. The MSE 330 can respond to the PDU session setup request of the MSA 320 and perform PDU session setup. According to one embodiment, the MSA 320 can modify a basic PDU session or establish a new dedicated PDU session.

[0151] According to one embodiment, the policy update operation of MSA 320 and MSE 330 in operation 407 can be performed, for example, when MSA 320 is provided with CARP or URSP rules from AA server 380. According to one embodiment, MSA 320 may not perform policy update with MSE 330 if CARP or URSP rules are not provided from AA server 380. According to another embodiment, MSA 320 may not perform policy update through its own judgment or information exchange with MSE 330 even if CARP or URSP rules are provided from AA server 380.

[0152] In operation 409, after completing authentication (or after performing or abbreviating a policy update with MSE 330), MSA 320 can send a message (e.g., a second request message) for an authorization (e.g., second authentication) request to MMP server 370. According to one embodiment, MSA 320 can request authorization from MMP server 370 based on authentication information (e.g., including an Auth Code or additionally an ID_token) obtained from AA server 380.

[0153] In operation 411, the MSA 320 can perform authentication (e.g., authorization procedure) with the AA server 380 via the MMP server 370. According to one embodiment, the MSA 320 can perform service authorization for service usage based on the Auth Code with the AA server 380.

[0154] In operation 413, the MMP server 370 may respond to the authentication request (e.g., the second request message) of the MSA 320 and provide (or send) authentication information (e.g., the second authentication information) according to the authentication result to the electronic device 101 (e.g., the MSA 320). According to one embodiment, the authentication information may include, for example, a connection token (e.g., a MAT, MEC access token) and MMP Info. According to one embodiment, the MMP server 370 may send a response to the MSA 320 including the connection token during or after authentication of the MSA 320.

[0155] In operation 415, the MSA 320 can activate the MSE 330. According to an embodiment, when the MSA 320 receives authentication information (e.g., a connection token (MAT)) according to the authentication result from the MMP server 370 during or after the authentication with the AA server 380, the MSA 320 can transmit the received authentication information (e.g., a connection token (MAT)) to the MSE 330 to activate the MSE 330. According to an embodiment, the MSA 320 can transmit at least one additional information, such as a connection address (e.g., a URI or IP address) of the new MMP server 370 to be connected to for performing the MEC discovery procedure, a DNS server address, or a DNN to be used, together with the authentication information (e.g., a connection token (MAT)) to the MSE 330. According to an embodiment, the MSA 320 can activate the MSE 330 based on the received connection token (MAT) and / or other additional information. According to one embodiment, when MSA 320 authenticates (e.g., authorizes) with MMP server 370, MSA 320 can receive a connection token (e.g., MAT) from MMP server 370 as an authentication result, and can communicate the MMP connection information (MMP Info) and connection token (MAT) to MSE 330, for example, by calling MSE API enableMecEnablingLayer(true, MMP Info, MAT).

[0156] In operation 417, the MSE 330 may receive the authentication information (e.g., MAT) and / or other additional information (e.g., MMP Info, DNS server address, or DNN to be used) and may perform a MEC discovery procedure based at least on the authentication information and / or the additional information. According to one embodiment, the MSE 330 may use the MMP Info and MAT to perform a MEC discovery procedure after connecting to the MMP server 370.

[0157] Although not shown in FIG. 4, according to another embodiment, MSE 330 can perform authentication with MMP server 370 (e.g., service authorization in operation 411). According to one embodiment, when MSE 330 performs authentication (e.g., authorization) with MMP server 380, MSA 320 that has completed priority authentication can receive MMP Info and Auth Code and / or other additional information (e.g., identification token (ID_token)) from MMP server 370 as an authentication result, and can transmit it to MSE 330 by calling enableMecEnablingLayer(true, MMP Info, Auth Code, [ID-Token]) of MSE API for activating MSE 330. MSE 330 can directly perform authorization with MMP server 370 from the information transmitted from MSA 320, and receive (or acquire) MAT as a result. For example, in comparison with the operation of FIG. 4, the entity that performs the service authentication procedure for authorization among the internal components of the electronic device 101 may be classified into the MSA 320 and the MSE 330.

[0158] FIG. 5 is a diagram illustrating an example of an authentication procedure according to various embodiments of the present disclosure.

[0159] As shown in FIG. 5, FIG. 5 may illustrate an example of a signal flow for an authentication procedure (e.g., scenario A for AA (authentication / authorization) and policy update) according to various embodiments. For example, FIG. 5 illustrates an example of an MEC service authentication flow for scenario A of the authentication procedure according to various embodiments, and may include an operation according to an embodiment of User Authentication (or Subscriber Authentication) (e.g., operation 510) and an operation according to an embodiment of MEC Service Authorization (e.g., operation 520). According to one embodiment, scenario A for MEC AA and policy update may illustrate an example scenario in which MEC Service Authorization (e.g., operation 520) is performed after User Authentication (e.g., operation 510) as shown in FIG. 5.

[0160] Referring to FIG. 5, in operation 501, the MSA 320 of the electronic device 101 may send a message to an entitlement server 500 for an authentication request.

[0161] In operation 503, the entitlement server 500 may determine an authentication method. According to an embodiment, the entitlement server 500 may determine an authentication method corresponding to the authentication request of the electronic device 101 from at least one specified authentication method. According to an embodiment, the at least one authentication method may include, for example, an Application-layer AKA using GPSI or a Login (e.g., ID / password) authentication method. According to an embodiment, the MSA 320 may request an authorization code while transmitting subscriber identity information (or terminal identity information) (e.g., GPSI or IMSI) to the entitlement server 500. According to an embodiment, the MSA 320 and the entitlement server 500 may perform user authentication in the Application-layer AKA or Logging method as in operation 510.

[0162] According to one embodiment, in operation 505, the MSA 320 performs an authentication procedure (e.g., MEC subscriber authentication) based on an application-layer AKA method between the MSA 320 and the AA server 380 via the entitlement server 500, and can obtain an authentication response including authentication information according to the authentication result from the AA server 380. According to another embodiment, in operation 507, the MSA 320 performs an authentication procedure with the entitlement server 500 based on an ID / password-based Login method, and can obtain an authentication response including authentication information according to the authentication result from the entitlement server 500 based on a Login Success to the entitlement server 500, in operation 509.

[0163] In operation 511, the MSA 320 may receive an authentication response corresponding to the authentication request. For example, in operation 511, the MSA 320 may obtain authentication information (e.g., MMP Info, Auth Code, ID_token, CARP rule, or URSP rule) according to the authentication result from the entitlement server 500 or the AA server 380 via the entitlement server 500. For example, the MSA 320 may receive MMP-related information (e.g., MMP connection address) for performing the MEC discovery procedure and an authorization code (e.g., Auth code) and ID_token for authorization according to the authentication result. According to an embodiment, the MSA 320 may also receive information related to the CARP or URSP rule for the MEC data service based on whether the AA server 380 supports it.

[0164] According to one embodiment, the MSA 320 can perform MEC Service Authorization as in operation 520 after User Authentication as in operation 510 .

[0165] According to one embodiment, in operation 513, after completing authentication, MSA 320 can send a message for an authorization request to MMP server 370. For example, MSA 320 can transmit the acquired authentication information (e.g., including Auth Code or additionally ID_token) to MMP server 370 to request authorization from MMP server 370. For example, after completing authentication, MSA 320 can connect to MMP server 370 using the MMP connection address to perform the authorization procedure.

[0166] In operation 515, the MMP server 370 may request an access token from the entitlement server 500, and in operation 517, may obtain the access token from the entitlement server 500. According to one embodiment, the MMP server 370 may communicate with the entitlement server 500 or communicate with the AA server 380 via the entitlement server 500 to verify whether the electronic device 101 is an MEC service subscriber. According to one embodiment, if the MMP server 370 verifies via the AA server 380 that the electronic device 101 is an MEC service subscriber, the MMP server 370 may issue (e.g., authorize) an access token (e.g., MAT) to the MSA 320.

[0167] In operation 519, the MMP server 370 can transmit the MMP information and the authorization code to the entitlement server 500 (or the AA server 380) and request and obtain a connection token for accessing user profile information.

[0168] In operation 521, the MMP server 370 can send an authorization response corresponding to the authorization request to the MSA 320. According to one embodiment, the MMP server 370 can use the connection token to verify the user profile and transmit an authorization response including MMP Info, MAT, or CARP rules to the MSA 320 if it is determined that the MEC service is available based on the user profile.

[0169] According to one embodiment, in operation 521, MSA 320 may obtain a connection token (e.g., MAT) as a result of the authorization procedure. According to one embodiment, when MSA 320 performs an authorization procedure with MMP server 370, MSA 320 may receive a connection token as a result of the authorization procedure and transfer MMP information and the connection token to MSE 330 via MSE API. According to another embodiment, when MSE 330 performs an authorization procedure with MMP server 370, MSA 320 that has completed the priority authentication may transfer MMP information and an authorization code (Auth code) received from entitlement server 500, and optionally an ID_token, to MSE 330 via MSE API. MSE 330 may directly perform an authorization procedure with MMP server 370 based on the information transferred from MSA 320, and receive a connection token as a result.

[0170] In operation 523, the MSA 320, via the MSE 330, may perform a MEC discovery procedure using the MMP Info and the connection token.

[0171] FIG. 6 is a diagram illustrating an example of an authentication procedure according to various embodiments of the present disclosure.

[0172] As shown in FIG. 6, the electronic device 101 may include an MSA (or service agent) 320 (including, for example, an AA client 325) and an MSE (or service enabler) 330 (including, for example, an MEL 331, a UHL 333).

[0173] 6, in operation 601, the MSA 320 of the electronic device 101 may send a message (e.g., an authorization request message) for an authorization request for service use to the MMP server 370 based on at least one specified authentication method. According to one embodiment, when the MSA 320 requests authorization for service use from the MMP server 370, it may provide (or send) at least one or both of MNO (mobile network operator) (e.g., entitlement server 500) information and a Device ID (e.g., IMSI, IMEI, GPSI, or a separately assigned unique identifier) ​​to the MMP server 370. According to one embodiment, the Device ID may include an identifier that allows the MMP server 370 to identify the electronic device 101 uniquely.

[0174] In operation 603, the MSA 320 may perform an authentication and authorization (e.g., AA, authentication & authorization) procedure with the MMP server 370 or the AA server 380 via the MMP server 370. For example, when the MSA 320 transmits an authorization request to the MMP server 370, a message exchange may be performed among the MSA 320, the MMP server 370, and the AA server 380. According to an embodiment, the MSA 320 may perform user authentication and service authorization (or authorization) with the MMP server 370. For example, the MSA 320 may perform a procedure to identify whether the electronic device 101 is a registered user and to identify whether the corresponding service can be provided. According to an embodiment, the MMP server 370 may use different AA methods depending on the MNO information, and may perform AA using the corresponding method depending on the MNO information.

[0175] In operation 605, when the MMP server 370 receives an authentication request from the electronic device 101, it performs authentication with the electronic device 101, and when the authentication is completed (e.g., the authentication procedure is completed), it can provide (or transmit) authentication information according to the authentication result to the electronic device 101 (e.g., MSA 320). According to one embodiment, the authentication information can include, for example, MMP Info and a connection token (e.g., MAT). According to one embodiment, the MMP server 370 can provide the authentication information by further including, in addition to the above information, additional (or selective) necessary information, for example, at least one of CARP or URSP rules for MEC data services. According to one embodiment, in operation 605, the MSA 320 can receive all of the authentication information according to the authentication result (e.g., MMP Info, MAT, and CARP or URSP rules) from the MMP server 370. According to another embodiment, in operation 605, the MSA 320 may receive part of the authentication information (e.g., MMP Info for discovery, MAT) from the MMP server 370 and the CARP rules (or URSP rules) from the AA server 380 as a result of user authentication.

[0176] According to one embodiment, the MMP Info may include, for example, information related to the connection of the MMP server 370 (e.g., MMP connection address). For example, the MMP Info may include address information of the new MMP server 370 to be connected (e.g., a uniform resource identifier (URI) or IP address) and information related to the validity time and / or location of the information. According to one embodiment, the connection token (e.g., MAT) may include, for example, a connection token for confirming MEC discovery authority. According to one embodiment, the CARP or URSP rule may include, for example, information related to DNN configuration, information related to an application (or application group) available for each DNN, or information related to a DNN list that can be set later or the maximum number of DNNs that can be set.

[0177] In operation 607, once the authentication procedure is complete, the MSA 320 can perform a policy update (e.g., PDU session setup) with the MSE 330. In one embodiment, the MSA 320 can perform the initial PDU session setup according to CARP or URSP rules (e.g., DNN). For example, the MSA 320 can update the URSP rules using the MSE API if the URSP rules are present in the information received from the MMP server 370.

[0178] According to one embodiment, the policy update operation of MSA 320 and MSE 330 in operation 607 can be performed, for example, when MSA 320 is provided with CARP or URSP rules from AA server 380. According to one embodiment, MSA 320 may not perform a policy update with MSE 330 if CARP or URSP rules are not provided from AA server 380. According to another embodiment, MSA 320 may not perform a policy update through its own judgment or through information exchange with MSE 330 even if CARP or URSP rules are provided from AA server 380.

[0179] In operation 609, the MSA 320 can activate the MSE 330. According to an embodiment, when the MSA 320 receives authentication information (e.g., a connection token (MAT)) according to the authentication result from the MMP server 370 during or after the authentication with the AA server 380, the MSA 320 can transmit the received authentication information (e.g., a connection token (MAT)) to the MSE 330 to activate the MES 330. According to an embodiment, the MSA 320 can transmit at least one additional information, such as a connection address (e.g., a URI or IP address) of the new MMP server 370 to be connected to for performing the MEC discovery procedure, a DNS server address, or a DNN to be used, together with the authentication information (e.g., a connection token (MAT)) to the MSE 330. According to an embodiment, the MSA 320 can activate the MSE 330 based on the received connection token (MAT) and / or other additional information. According to one embodiment, when MSA 320 authenticates with MMP server 370, MSA 320 can receive a connection token (e.g., MAT) from MMP server 370 as an authentication result, and can transmit the MMP connection information (MMP Info) and the connection token (MAT) to MSE 330, for example, by calling MSE API enableMecEnablingLayer(true, MMP Info, MAT).

[0180] In operation 611, the MSE 330 may receive authentication information (e.g., MAT) and / or other additional information (e.g., MMP Info, DNS server address, or DNN to be used) and may perform a MEC discovery procedure based at least on the authentication information and / or the additional information. According to one embodiment, the MSE 330 may perform a MEC discovery procedure after connecting to the MMP server 370 using the MMP Info and MAT.

[0181] FIG. 7 is a diagram illustrating an example of an authentication procedure according to various embodiments of the present disclosure.

[0182] 7, the electronic device 101 may include an MSA (or service agent) 320 (including, for example, an AA client 325) and an MSE (or service enabler) 330 (including, for example, an MEL 331 and a UHL 333). According to an embodiment, the PCF of the AMF / PCF server 390 may add an URSP to manage information required for MMP connection (for example, MMP Info, Auth Code, or ID_token).

[0183] 7, in operation 701, the MSE 330 of the electronic device 101 may perform a NAS signaling procedure with the AMF / PCF server 390 (e.g., AMF). According to one embodiment, the AMF / PCF server 390 may provide MMP Info, Auth Code, and may additionally provide ID_token and / or CARP or URSP rules to the electronic device 101. According to one embodiment, the MSE 330 may receive a NAS signaling message that a modem (or communication processor) of the electronic device 101 receives from the AMF 390 via the UHL 333 of the MSE 330. For example, the modem of the electronic device 101 may obtain at least one of MMP Info and Auth Code, ID_token, or CARP or URSP rules from the NAS signaling message received from the AMF, and transmit the obtained information to the MSA 320 via the UHL 333.

[0184] In operation 703, the MSE 330 may acquire at least one of MMP Info, Auth Code, and / or ID_token from the NAS signaling message and transmit the acquired information to the MSA 320. According to an embodiment, the MMP Info may include, for example, information related to the connection of the MMP server 370 (e.g., MMP connection address). For example, the MMP Info may include address information (e.g., URI (uniform resource identifier) ​​or IP address) of the new MMP server 370 to be connected and information related to the valid time and / or location of the address information. According to an embodiment, the CARP or URSP rule may include, for example, information related to DNN configuration, information related to an application (or application group) available for each DNN, or information related to a future configurable DNN list or a maximum number of configurable DNNs.

[0185] According to one embodiment, at least one of MMP Info, Auth Code, ID_token, or CARP or URSP rules provided by the AMF / PCF server 390 can also be obtained from the MSA 320 via the MSE 330.

[0186] In operation 705, MSA 320 may perform a policy update with MSE 330 (e.g., PDU session setup). According to one embodiment, MSA 320 may perform a PDU session setup according to a CARP or URSP rule (e.g., DNN). For example, MSA 320 may update the URSP rule using the MSE API if the URSP rule is included in the information received from MMP server 370. According to one embodiment, MSA 320 may perform a policy update with MSE 330 if the CARP or URSP rule is included in the information acquired via the NAS signaling message. According to one embodiment, MSA 320 may not perform a policy update with MSE 330 if the CARP or URSP rule is not provided in the information acquired via the NAS signaling message. According to another embodiment, MSA 320 may not perform a policy update even if the CARP or URSP rule is provided, based on its own judgment or through information exchange with MSE 330. According to one embodiment, PDU session setup can be performed during policy update between MSA 320 and MSE 330 .

[0187] In operation 707, after receiving the NAS signaling message (or after performing or omitting a policy update with MSE 330), MSA 320 can send a message (e.g., an authorization request message) for an authorization request (e.g., a service usage authorization request) to MMP server 370. According to one embodiment, MSA 320 can request authorization for service usage from MMP server 370 based on authentication information (e.g., including an Auth Code or additionally an ID_token) obtained from the NAS signaling message.

[0188] In operation 709, the MSA 320 can perform authentication (e.g., authorization procedure) with the AA server 380 via the MMP server 370. According to one embodiment, the MSA 320 can provide (or send) at least one or both of an Auth Code and an ID_token to the AA server 380 and request service authorization for service usage.

[0189] In operation 711, MMP server 370 may respond to MSA 320's authorization request (e.g., an authorization request message) and provide (or send) authentication information to electronic device 101 (e.g., MSA 320). According to one embodiment, the authentication information may include, for example, a connection token (e.g., MAT) and MMP Info. According to one embodiment, MMP server 370 may send a response to MSA 320 including the connection token and MMP Info during or after authentication of MSA 320.

[0190] In operation 713, the MSA 320 can activate the MSE 330. According to an embodiment, when the MSA 320 receives authentication information (e.g., a connection token (MAT), MMP Info) from the MMP server 370, the MSA 320 can transmit the received authentication information (e.g., a connection token (MAT), MMP Info) to the MSE 330 to activate the MSE 330. According to an embodiment, the MSA 320 can transmit at least one additional information, such as a connection address (e.g., a URI or IP address) of the new MMP server 370 to which to connect to perform the MEC discovery procedure, a DNS server address, or a DNN to be used, together with the connection token (MAT) to the MSE 330. According to an embodiment, the MSA 320 can activate the MSE 330 based on the received connection token (MAT) and / or other additional information. According to one embodiment, when MSA 320 performs an authorization procedure with MMP server 370, MSA 320 can receive a connection token (e.g., MAT) from MMP server 370 and can communicate the MMP connection information (MMP Info) and the connection token (MAT) to MSE 330, for example, by calling MSE API enableMecEnablingLayer(true, MMP Info, MAT).

[0191] In operation 715, the MSE 330 may receive authentication information (e.g., MAT) and / or other additional information (e.g., MMP Info, DNS server address, or DNN to be used) and may perform a MEC discovery procedure based at least on the authentication information and / or the additional information. According to one embodiment, the MSE 330 may use the MMP Info and MAT to perform a MEC discovery procedure after connecting to the MMP server 370.

[0192] FIG. 8 illustrates an example of a policy update operation in the electronic device 101 according to various embodiments of the present disclosure.

[0193] As shown in FIG. 8, FIG. 8 may show an example of PDU session establishment among policy updates (e.g., PDU session setup), and may show an example of an operation for dedicated DNN activation in PDU session setup (or PDN connection establishment). According to one embodiment, PDU session setup may include new PDU session establishment, existing PDU session release, and existing PDU session update (e.g., changing settings for characteristics of each PDU session (e.g., QoS information such as bandwidth or latency)), and FIG. 8 shows an example of PDU session establishment. According to one embodiment, the electronic device 101 may include an MSA (or service agent) 320, an MSE (or service enabler) 330, and a modem (or CP, communication processor) 800.

[0194] Referring to FIG. 8, in operation 801, when MSA320 acquires (or receives) information for DNN configuration, it may provide (or transmit) a first message (e.g., setUrspDNN) to MSE330 instructing it to configure a DNN.

[0195] At operation 803, the MSE 330 may update the DNN information (e.g., update DNN Info) based on the first message (e.g., setUrspDNN) provided from the MSA 320.

[0196] At operation 805, the MSA 320 may provide a second message (e.g., requestPduSession) to the MSE 330 instructing it to create a PDU session (or PDN connection).

[0197] At operation 807, if the MSE 330 receives the second message (e.g., requestPduSession), it may provide a third message (e.g., setup data call) to the modem 800 instructing it to set up a data call.

[0198] In operation 809, upon receiving a third message (e.g., setup data call) from the MSE 330, the modem 800 may set up a data call based on preconfigured information for processing a service (e.g., MEC service) or set up a data call based on indicated information, and provide a fourth message (e.g., a response message) corresponding to the third message at the MSE 320. According to one embodiment, a PDU session may be generated based on the modem 800 requesting PDU session generation from a core network (e.g., SMF - not shown in the drawing) via the third message (e.g., setup data call).

[0199] At operation 811, if the MSE 330 receives a fourth message (e.g., a response corresponding to a data call setup request) from the modem 800, it may provide a fifth message (e.g., onAvaible) to the MSA 320 notifying that the PDU session has been established.

[0200] In operation 813, the MSA 320 may provide a sixth message (e.g., setUrspRules) to the MSE 330 to instruct the MSE 330 to set the URSP rules if the URSP rules are received using any one of the above-mentioned methods or via another method. According to one embodiment, in operation 815, the MSA 320 may provide a seventh message (e.g., setMaServiceEnableMode(true)) to the MSE 330 to instruct the MEC service activation mode (e.g., MSE activation) to be performed (true).

[0201] In operation 817, the MSE 330 may generate (or add) a routing table based on the sixth message (e.g., setUrspRules) and the seventh message (e.g., setMaServiceEnableMode(true)) received from the MSA 320. According to an embodiment, the URSP rule may include PDU session information to be used per application or per URI, and the electronic device 101 (e.g., MSE 330) may generate a PDU session via the setUrspDNN API if a PDU session on the URSP rule has not been generated. According to an embodiment, the electronic device 101 (e.g., MSE 330) may set the routing table via the setUrspRules API when generating a PDU session so that a data path for the application ID (AppID) or URI is set in the PDU session on the URSP rule.

[0202] FIG. 9 is a diagram showing an example of a PDU session setup operation in an electronic device 101 according to various embodiments of the present disclosure.

[0203] As shown in FIG. 9, FIG. 9 may show an example of a PDU session release during a policy update (e.g., PDU session setup), and may show an example of an operation for releasing a PDU session (or PDN connection). According to one embodiment, PDU session setup may include a new PDU session establishment, an existing PDU session release, and an existing PDU session update (e.g., changing settings for characteristics of each PDU session (e.g., QoS information such as bandwidth or latency)), and FIG. 8 shows an example of a PDU session release. According to one embodiment, the electronic device 101 may include an MSA (or service agent) 320, an MSE (or service enabler) 330, and a modem (or CP, communication processor) 800.

[0204] Referring to FIG. 9, in operation 901, if the MSA 320 needs to unset information for a DNN setting, it can provide (or transmit) a first message (e.g., setUrspDNN) to the MSE 330 instructing it to unset the corresponding DNN.

[0205] At operation 903, the MSE 330 may provide a second message (e.g., Release data call) to the modem 1300 instructing it to release the data call based on the first message (e.g., setUrspDNN) provided from the MSA 320.

[0206] In operation 905, when the modem 800 receives a third message (e.g., Release data call) from the MSE 330, the modem 800 may release the configuration set for processing the corresponding service (e.g., MEC service) and provide a fourth message (e.g., a Response message) corresponding to the third message at the MSE 330. According to one embodiment, the PDU session may be released based on the modem 800 requesting the core network (e.g., SMF) to release the PDU session by the third message (e.g., Release data call).

[0207] At operation 907, the MSA 320 may provide a fifth message (e.g., setMaServiceEnableMode(false)) to the MSE 330 instructing it to perform (false) an MEC service deactivation mode (e.g., MSE deactivation).

[0208] At operation 909, MSE330 may delete the routing table stored (or generated) in memory (e.g., memory 130 of FIG. 1 or FIG. 2) based on the fifth message (e.g., setMaServiceEnableMode(false)) received from MSA320.

[0209] FIG. 10 is a diagram illustrating an example of a discovery procedure according to various embodiments of the present disclosure.

[0210] As shown in FIG 10, an example of an application state-based MEC discovery procedure may be illustrated. According to one embodiment, the electronic device 101 may include a client application (or Client App) 310, an MSA (or Service Agent) 320, an MSE (or Service Enabler) 330 (including, for example, an MEL 331, a UHL 333), and a DNS cache 1010.

[0211] Referring to FIG. 10, in operation 1001, the MSA 320 of the electronic device 101 may set an MEC discovery policy in the MSE 330. According to an embodiment, the MEC discovery policy may be provided including client application names (e.g., clientAppNames) and a discovery policy (e.g., discoveryPolicy). According to an embodiment, the discoveryPolicy may include whether a dynamic DNN (e.g., dynamicDnn) is used, and may include at least one of information such as a location (e.g., locationInfo), a device type (e.g., deviceType), a service type (e.g., serviceType), or a context type (e.g., contextType). According to an embodiment, the MSA 320 may include the location (e.g., locationInfo), device type (e.g., deviceType), and service type (e.g., serviceType) in the discoveryPolicy to limit the application list to only those that meet the conditions. According to an embodiment, the MSA 320 may include information on whether an application context is required by including a context type (e.g., contextType) in the discoveryPolicy. According to an embodiment, the MSA 320 may include a URI Request Flag in the discoveryPolicy to request that the URI be included in the application list if the URI of the MEC application is available. According to an embodiment, the client application name (clientAppNames) may be information for requesting an application list to check whether MEC is available, the location (locationInfo) may be information for requesting a location-based application list according to the current location of the electronic device 101, and the dynamic DNN (dynamicDnn) may be information for checking whether a dynamic DNN update is used.

[0212] In operation 1003, the MSE 330 may perform an acquisition procedure (e.g., MEC Application Look-up) to acquire an application list (e.g., AppList) based on information (e.g., MEC discovery policy) received from the MSA 320. According to an embodiment, an acquisition procedure (e.g., MEC Application Look-up) to acquire an application list according to the MEC discovery policy setting may be initiated between the MSA 320 and the MSE 330. According to an embodiment, the MSE 330 may activate the MEC Application Look-up when it receives the MEC discovery policy from the MSA 320 via the MSE API, and may execute (or start) the MEC Application Look-up when a specific condition of the electronic device 101 (e.g., a change in the connection base station Cell ID while the electronic device 101 is moving) is satisfied. According to an embodiment, the MSE 330 may request and receive an application list (e.g., MEC AppList) related to MEC applications (e.g., MEP App) that can be serviced according to the MEC discovery policy from the MMP server 370. According to one embodiment, the MSE 330 can request the MEC discovery policy to the MMP server 370 by filling in the MEC AppList request message parameters as shown in Table 1, and the MMP server 370 can provide the corresponding service-enabled app list to the MSE 330 and respond to the request from the MSE 330.

[0213] In operation 1005, the client application 310 may provide (or convey) an App Launch Detected or an API (Context Create) call to the MSA 320. According to one embodiment, the App Launch Detected case may indicate a case where the client application 310 is executed. According to one embodiment, the API (Context Create) call may indicate a case where a URI for the MEC application name (e.g., MEC App Name) to be connected is requested.

[0214] In operation 1007, when the MSA 320 receives an App Launch Detected or API (Context Create) call, it can provide a notification message (e.g., notifyClientAppState) to the MSE 330 to notify the state of the client application 310. According to one embodiment, the notification message (e.g., notifyClientAppState) can be provided including, for example, the state of the client application (e.g., START) and the name (e.g., clientAppName) (and / or UID) of the client application (e.g., notifyClientAppState(START, clientAppName)).

[0215] In operation 1009, the MSE 330 may receive a notification message (e.g., notifyClientAppState) from the MSA 320 and perform a procedure (e.g., application context create) to discover (or search, confirm) an MEC application (or an MEC host (e.g., an edge server or MEC server) including the MEC application) based on the received notification message. According to an embodiment, the MSE 330 may activate application context create when it receives an event related to the execution of the client application 310 from the MSA 320. According to an embodiment, the MSE 330 may perform an application context create operation to search for an MEC host including a desired MEC application via the MMP server 370 based on information in the received notification message (e.g., notifyClientAppState). According to an embodiment, the application context create may be activated (or performed) by an MSE API call when the MSA 320 detects the execution of the client application 310. According to an embodiment, the application context create may be activated (or performed) when the client application 310 calls a context create API. According to one embodiment, the MSE 330 may request and receive a URI for an MEC application name (e.g., MEC App Name) to be connected from the MMP server 370. According to one embodiment, the MSE 330 may also request and receive information for a dedicated DNN from the MMP server 370 as necessary. According to one embodiment, the MMP server 370 may also transmit an MEC application package URI to the MSE 330 if the corresponding MEC application does not exist. The application context generation procedure according to various embodiments will be described in detail with reference to the drawings below.

[0216] In operation 1011, the MSE 330 may perform a host selection procedure (e.g., MEC Host Selection) for selecting a MEC host together with the DNS server 1020. According to an embodiment, when there are at least two MEC hosts acquired via the MMP server 370, the MSE 330 may perform a host selection procedure (e.g., MEC Host Selection) for selecting one of the MEC hosts together with the DNS server 1020. According to an embodiment, when there are two or more MEC hosts, the host selection procedure for selecting one MEC host may be determined using preset information and / or information queried by the DNS server 1020, or a specific MEC host may be selected (or set) by querying the information queried by the DNS server 1020 and / or a user. According to an embodiment, the preset information for the MSE 330 to set a specific MEC host when there are two or more MEC hosts may include priority information. According to an embodiment, the host selection procedure may include a DNS pre-resolving operation and a MEC host prioritization operation. According to an embodiment, DNS pre-resolving may include, for example, the MSE 330 itself performing DNS resolution on a fully qualified domain name (FQDN) for MEC regardless of a DNS query of the client application 310. According to an embodiment, DNS resolution may be performed using a URI or a domain name received via a Get App List step of operation 1003 or a Find Cloudlet step of operation 1009. According to an embodiment, MEC host prioritization may include, for example, setting IP priority when multiple IP addresses are received in a DNS query response. A host selection procedure (e.g., MEC host selection) according to various embodiments will be described in detail with reference to the following drawings.

[0217] In operation 1013, the client application 310 may perform a DNS resolving operation using the information acquired through the above operations. According to one embodiment, the DNS resolving may be performed, for example, when a DNS query is generated by the client application 310. According to one embodiment, the DNS resolving may include, for example, client-driven normal DNS resolving or DNS proxying (hooking DNS query). DNS resolving according to various embodiments will be described in detail with reference to the following drawings.

[0218] FIG. 11 is a diagram illustrating an example of a discovery procedure according to various embodiments of the present disclosure.

[0219] 11, an example of a DNS Query-based MEC discovery procedure may be illustrated. According to an embodiment, the electronic device 101 may include a client application (or Client App) 310, an MSA (or Service Agent) 320, an MSE (or Service Enabler) 330 (including, for example, an MEL 331 and a UHL 333), and a DNS cache 1010.

[0220] Referring to FIG. 11, in operation 1101, the MSA 320 of the electronic device 101 may set an MEC discovery policy in the MSE 330. According to an embodiment, the MEC discovery policy may be provided including client application names (e.g., clientAppNames) and a discovery policy (e.g., discovery Policy). According to an embodiment, the discovery policy may include whether to use a dynamic DNN (e.g., dynamicDnn), and may include at least one of information such as a location (e.g., locationInfo), a device type (e.g., deviceType), a service type (e.g., serviceType), or a context type (e.g., contextType). According to an embodiment, the MSA 320 may include a location (e.g., locationInfo), a device type (e.g., deviceType), and a service type (e.g., serviceType) in the discoveryPolicy to limit the application list to only those that meet the conditions. According to one embodiment, the MSA 320 can include information on whether an application context is required by including a context type (e.g., contextType) in the discoveryPolicy. According to one embodiment, the MSA 320 can include a URI Request Flag in the discoveryPolicy to request that the URI be included in the app list if the URI of the MEC application is available.

[0221] In operation 1103, the MSE 330 may perform an acquisition procedure (e.g., MEC Application Look-up, Get App List) to acquire an application list (e.g., AppList) based on information (e.g., MEC discovery policy) received from the MSA 320. According to an embodiment, an acquisition procedure (e.g., MEC Application Look-up, Get App List) to acquire an application list according to the MEC discovery policy setting may be initiated between the MSA 320 and the MSE 330. According to an embodiment, when the MSE 330 receives the MEC discovery policy from the MSA 320 via the MSE API, the MEC Application Look-up may be activated and executed (or started) when a specific condition of the electronic device 101 (e.g., a change in the connected base station Cell ID while the electronic device 101 is in operation) is satisfied. According to an embodiment, the MSE 330 may request and receive an application list (e.g., MEC AppList) related to MEC applications (e.g., MEP App) that can be serviced according to the MEC discovery policy from the MMP server 370. According to one embodiment, the MSE 330 can request the MEC discovery policy from the MMP server 370 by filling in the MEC AppList request message Parameter, and the MMP server 370 can provide the corresponding service-enabled app list to the MSE 330 and respond to the MSE 330 request.

[0222] At operation 1105, the client application 310 may transmit a message for a DNS query (e.g., a DNS query message) to the MSE 330.

[0223] In operation 1107, the MSE 330 may perform a Find Cloudlet operation with the MMP server 370 in response to a DNS query from the client application 310. According to an embodiment, when a DNS query (with FQDN) message is generated in the client application 310, the MSE 330 may perform Find Cloudlet for the MEC application (e.g., MEC App) when detecting the FQDN for MEC through FQDN filtering. According to an embodiment, the MSE 330 may request and receive a URI for the MEC application name (e.g., MEC App Name) to be connected from the MMP server 370. According to an embodiment, the MSE 330 may request and receive information on a dedicated DNN from the MMP server 370 as necessary. According to an embodiment, the MMP server 370 may transmit a MEC application package URI to the MSE 330 if the MEC application does not exist.

[0224] In operation 1109, the MSE 330 may perform a host selection procedure (e.g., MEC Host Selection) for selecting an MEC host with the DNS server 1020 in response to the DNS query from the client application 310. According to an embodiment, when there are at least two MEC hosts acquired via the MMP server 370, the MSE 330 may perform a host selection procedure (e.g., MEC Host Selection) for selecting one MEC host with the DNS server 1020. According to an embodiment, when there are two or more MEC hosts. The host selection procedure for selecting one MEC host may be determined using preset information and / or information (e.g., IP address, location information by IP) received by requesting the DNS server 1020, or a specific MEC host may be selected (or set) by the user via information received by requesting the DNS server 1020 and / or a user interface (UI) (e.g., a selection button). According to an embodiment, when there are two or more MEC hosts, the preset information for setting a specific MEC host may include priority information. According to an embodiment, the priority information may include, for example, information in which the host priority is determined by URI, or, when there are multiple IP addresses resulting from DNS resolving one URI, may include information in which the priority is determined by the IP addresses. According to an embodiment, the host selection procedure may include a DNS resolving operation and a MEC host prioritization operation. According to an embodiment, the DNS resolving may include, for example, the MSE 330 itself performing DNS resolution on the MEC FQDN regardless of a DNS query of the client application 310. According to an embodiment, the MEC host prioritization may include, for example, setting IP priority when multiple IP addresses are received in a DNS query response.According to one embodiment, the priority is predefined for each URI or IP, and when multiple IP addresses are received, the IP priority can be dynamically determined according to the results of a performance test for each of the received IP addresses. A host selection procedure (e.g., MEC Host Selection) according to various embodiments will be described in detail with reference to the following drawings.

[0225] In operation 1111, when the above procedures are completed, the MSE 330 may provide the information acquired through the above procedures to the client application 310 as a DNS response. According to one embodiment, after selecting an MEC host (e.g., DNS resolving), the MSE 330 may deliver a DNS response corresponding to the DNS query to the client application 310 that provided the DNS query. DNS responses according to various embodiments will be described with reference to the drawings below.

[0226] FIG. 12 is a diagram illustrating an example of an operation for acquiring an application list in a discovery procedure according to various embodiments of the present disclosure.

[0227] As shown in FIG. 12, FIG. 12 may show an example of an operation regarding application list generation and acquisition (e.g., MEC Application Look-up) in an MEC discovery procedure according to one embodiment.

[0228] 12, in operation 1201, the MSA 320 of the electronic device 101 may transmit an MEC discovery policy to the MSE 330. According to an embodiment, the MEC service module 410 may obtain the MEC discovery policy using the MSA 320 and perform a discovery procedure based on the received MEC discovery policy using the MSE 330. According to an embodiment, the MEC discovery policy may be provided including at least one of a client application name (e.g., clientAppNames), a location (locationInfo), a device type (e.g., deviceType), a service type (e.g., serviceType), a context type (e.g., contextType), a URI request flag (e.g., URI Request), or a dynamic DNN (e.g., dynamicDnn).

[0229] In operation 1203, the MSE 330 may perform an acquisition procedure (e.g., MEC Application Look-up) to acquire an application list (e.g., AppList) based on information (e.g., MEC discovery policy) received from the MSA 320. According to one embodiment, the operation of acquiring the application list may be initiated by an MEC discovery policy setting between the MSA 320 and the MSE 330. According to one embodiment, the application list acquisition procedure may be activated upon an MEC discovery policy API call in the MSA 320, and the MEC application list and / or URIs corresponding to the MEC discovery policy may be requested and received from the MMP server 370. According to one embodiment, the application list acquisition procedure may include operations 1210 and 1220.

[0230] At operation 1210, the MSE 330 may send a request message (e.g., HTTP Get AppList Request Parameters) requesting an app list to the MMP server 370. According to one embodiment, the MSE 330 may provide the MEC discovery policy to the MMP server 370 by including it in the request message (e.g., HTTP Get AppList Request Parameters). For example, the MSE 330 may provide the MMP server 370 by including the app list request parameters.

[0231] According to an embodiment, field information that can be supported in the Request Parameter can be defined in MMP Info in the Authorization Response in the authentication (AA) phase. According to an embodiment, parameters (or information) related to the app list request (e.g., AppList Request Parameters) can be included in a parameter field of a request message (e.g., HTTP GET). According to an embodiment, the application list request parameters include application names (e.g., clientAppNames) transmitted from the MSA 320 (e.g., setMecDiscoveryPolicy(clientAppNames, discoveryPolicy) in operation 1201), location information (Location Info) related to the location of the electronic device 101 including at least one of a connected Cell ID, a tracking area (TA) ID, area information (e.g., city, district, dong, building), or preferred location information designated by a user, a device type (Device Type) (e.g., Smartphone, Tablet, Wearable, IoT, Car, Drone) that can identify the type of the electronic device 101, a service type (Service Type) (e.g., Game, V2X, AR / VR, LBO, Enterprise, Web) that can identify the type of service, and a context type (Context Info) that can identify whether context information is required. The response may include at least one of the following: Type (e.g., whether user or application context information is required to run the MEC application); or a Flag (e.g., URI Request Flag) that requests that the URI of the MEC application be included in the response if it is available for activation.According to one embodiment, the context type is information for identifying the service application type of the electronic device 101, and may include, for example, at least one of an application installed on the electronic device 101 (e.g., a specific launcher or a specified application), the name of the running application, and a domain.

[0232] According to an embodiment, the electronic device 101 may transmit information about applications installed in the electronic device 101 (e.g., a specific launcher or a specified application) to the MMP server 370 by requesting an app list. According to an embodiment, when there is a change (e.g., an update) in the information about the applications installed in the electronic device 101, the electronic device 101 may also transmit the information about the applications installed in the electronic device 101 to the MMP server 370 by requesting an app list.

[0233] At operation 1220, the MMP server 370 may provide the MSE 330 with a response message (e.g., HTTP 200 OK AppList response Data) including the app list (e.g., MEC AppList) in response to the request message received from the MSE 330. According to one embodiment, the MMP server 370 may search for MEC applications based on the received client application name, and provide the MSE 330 with the app list including the searched MEC applications in the response message.

[0234] According to one embodiment, data (or information) related to the app list response (eg, AppList Response Data) may be included in a message body of a response message (eg, HTTP 200 OK).

[0235] According to one embodiment, when the MMP server 370 provides an app list, it can provide a serviceable MEC App List based on at least one of the available overall MEC App List or the Request Parameters. According to one embodiment, it can include a connectable MEC App Name for each client application, and the MEC App Name can be used (or required) in a subsequent Application Context Create operation.

[0236] According to an embodiment, when an operator's location API is available, the MMP server 370 may provide a notification by including it in the application list. According to an embodiment, when a URI Request Flag is true in a request message and the MEC app is running in an available MEC host near the electronic device 101 (e.g., a user terminal), the MMP server 370 may provide the URI of the MEC app by including it in the application list. According to an embodiment, even if there is no URI Request Flag in the request message, the MMP server 370 may provide the URI of the MEC app by including it in the application list if the MEC app is running in the MEC host. According to an embodiment, when the MMP server 370 receives an application list request from the electronic device 101, if the MEC app can be immediately run according to the context type in the request message, the MMP server 370 may provide the URI after running the MEC app by including it in the application list. According to an embodiment, the MMP server 370 may provide the valid time / valid place information of the URI by further including it in the application list. According to an embodiment, information regarding the validity period of the URI may be determined by the electronic device 101 or may be variably determined according to the MEC App operating state by the MMP server 370. According to an embodiment, the MMP server 370 may provide a dedicated DNN rule for each application, if such a rule exists.

[0237] According to one embodiment, the URIs included in the app list may be differentiated by being hyperlinked and / or highlighted, and the electronic device 101 may display MEC Apps that do not include URIs in the app list by distinguishing them based on the hyperlink and / or highlight. According to another embodiment, the electronic device 101 may display MEC Apps that include URIs and MEC Apps that do not include URIs in the same way in the app list without distinguishing them. According to one embodiment, the electronic device 101 may provide location and / or time information in which a service is available for each application in the app list.

[0238] According to an embodiment, the MMP server 370 may include application-specific (or app-specific) DNN information in the application list in the procedure of responding with the application list if DNN setting is possible on an application-by-application basis. According to an embodiment, the DNN server may be a DNN included in the DNN list received in the authentication (AA) procedure.

[0239] According to one embodiment, the electronic device 101 may obtain (or receive) the app list and information (e.g., a URI) for a MEC host (e.g., an edge server or MEC server) for a corresponding application in the app list by requesting the app list from the MMP server 370 and receiving a response thereto. According to one embodiment, if the electronic device 101 does not receive information (e.g., a URI) for a MEC host, for example, the electronic device 101 may further perform an Application Context Create procedure for the corresponding application to obtain information (e.g., a URI) for a MEC host for the corresponding application from an external server. According to one embodiment, if the electronic device 101 receives information (e.g., a URI) for a MEC host, for example, the electronic device 101 may immediately connect to the MEC host (e.g., using the URI) for the corresponding application without performing an Application Context Create procedure for the corresponding application.

[0240] According to an embodiment, the electronic device 101 may receive the app list and information (e.g., DNN) on a designated networking path for the application in the app list by requesting an app list from the MMP server 370 and receiving a response thereto. According to an embodiment, when the electronic device 101 receives information (e.g., DNN) on the designated networking path, the electronic device 101 may perform a procedure of setting up a network and the designated networking path. According to an embodiment, the electronic device 101 may set up a DNN path to communicate with a designated (or dedicated) DNN only for the application that received the DNN information. According to an embodiment, the electronic device 101 may set up a designated DNN path for the application that received the DNN information by a procedure of requesting the MEC host to create a context (e.g., Application Context Create).

[0241] FIG. 13 is a diagram illustrating an example in which an app list is provided according to various embodiments of the present disclosure.

[0242] As shown in FIG. 13, FIG. 13 may illustrate a Location-based Service Area.

[0243] 13, in one embodiment, it may be assumed that the MMP server 370 obtains first information (e.g., A(+URI), B, C) on available applications from a first server (Server1) 1310 (or a first MEC host adjacent to the user). In one embodiment, it may be assumed that the MMP server 370 obtains second information (e.g., A, C(+URI), D) on available applications from a second server (Server2) 1320 (or a second MEC host adjacent to the user).

[0244] According to various embodiments, the MMP server 370 can collect information (e.g., first information, second information) for each application obtained from the first server 1310 and the second server 1320, and generate (or obtain) information such as A(+URI), B, C(+URI), and D. According to one embodiment, the MMP server 370 can generate an application list including A(+URI), B, C(+URI), and D generated from the first server 1310 and the second server 1320, and provide the generated application list to the user 1330 (e.g., the electronic device 101).

[0245] FIG. 14 is a diagram illustrating an example of a context generation procedure in a discovery procedure according to various embodiments of the present disclosure.

[0246] As shown in FIG. 14, FIG. 14 may show an example of an operation related to application context creation (e.g., Application Context Create) in an MEC discovery procedure according to an embodiment. According to an embodiment, the application context creation procedure may be performed, for example, when a client application 310 is executed, by the MSA 320 transmitting application start information to the MSE 330 via the MSE API together with information related to the client application (e.g., package name or UID). According to various embodiments, the application context creation may be performed when an application on an app list is executed (launched) (first case), when an application requests context creation (contextcreate) via the MSE API (e.g., context create API call) (second case), or when an application sends a DNS query and is matched with an application name and / or URI (e.g., FQDN) included in a previously received app list (third case). According to one embodiment, the application context may be generated when the location information transferred via the MEC discovery policy (e.g., setDiscoveryPolicy(discoveryPolicy)) or the available location (e.g., uriLOC) for each application included in the app list transferred via the application lookup response matches the location of the current user (or electronic device 101) (e.g., fourth case). According to various embodiments, the application context may be generated when at least one of the conditions according to the first, second, third, or fourth case is satisfied. FIG. 14 shows an example of an operation of generating an application context according to the first case.

[0247] 14, in operation 1401, when a particular client application 310 is launched, the client application 310 may provide information notifying the execution of the application (e.g., App Launched) to the MSA 320. According to an embodiment, operation 1401 may not be performed. For example, when the client application 310 is launched, the MSA 320 (e.g., Framework level) may detect the execution of the client application 310 by itself, without an operation of notifying the execution by the client application 310.

[0248] In operation 1403, when the MSA 320 receives information (e.g., App Launched) notifying the execution of the client application 310, the MSA 320 may provide a notification message (e.g., notifyClientAppState) to the MSE 330 to notify the state of the client application 310. According to one embodiment, the notification message (e.g., notifyClientAppState) may include, for example, the state of the client application (e.g., START) and the name (e.g., clientAppName) (and / or UID) of the client application (e.g., notifyClientAppState(START, clientAppName)).

[0249] In operation 1405, the MSE 330 may receive a notification message (e.g., notifyClientAppState) from the MSA 320 and perform an application context creation procedure based on information in the received notification message. According to one embodiment, the application context creation procedure (operation 1405) may include operations 1410, 1420, and 1430.

[0250] In operation 1410, the MSE 330 may send a request message (e.g., HTTP POST AppContext Data) to the MMP server 370 requesting the creation of an application context. According to one embodiment, if MEC application context creation is required (e.g., if the URI is not present in the app list), the MSE 330 may send a request message to the MMP server 370 requesting a URI. According to one embodiment, if the MMP server 370 has an MEC application, the MSE 330 may send the request message to the MMP server 370 including an MEC application name (MEC App Name). According to another embodiment, if the MMP server 370 does not have an MEC application, the MSE 330 may send the request message to the MMP server 370 including only an URI (e.g., an App package download URI) at which the MEC application can be downloaded.

[0251] In operation 1420, the MMP server 370 may provide a response message (e.g., HTTP OK 200 Response AppContext Data) including a URI of an MEC application to the MSE 330 in response to the request message received from the MSE 330. According to an embodiment, the response message may include a URI (FQDN) of a corresponding application (e.g., MEC application). According to an embodiment, the response message may include information regarding the URI of the MEC application and a validity time and / or a validity location of the URI. According to an embodiment, the MSE 330 may perform application context re-execution or handover triggering when the validity time expires or the validity location changes. According to an embodiment, the response message may include DNN information.

[0252] In operation 1430, the MSE 330 may perform a policy update. According to an embodiment, the MSE 330 may additionally (or alternatively) include a policy update operation in the application context creation procedure (operation 1405). According to an embodiment, the MSE 330 may receive a URSP rule (e.g., DNN) when a dedicated PDU session is required (or when a new dedicated DNN rule is set), and may set up a PDU session per application or per URI according to the URSP rule. For example, the URSP rule (or CARP rule) may be received as a result of an authentication procedure (e.g., received by the MSA 320 and transmitted to the MSE 330), or as a result of an application lookup (e.g., App lookup) or a result of a context create (Context Create), and if a new DNN rule is set in the URSP rule, a PDU session setup may be performed. According to one embodiment, PDU session setting (e.g., PDU session creation in FIG. 8, PDU session release in FIG. 9) can be generated / released by modem 800 via a request from MSE330 to modem 800 as described above in the description section referring to FIG. 8 or FIG. 9, by modem 800 making a request to the SMF of the 5G network (or core network).

[0253] According to various embodiments, the application context generation procedure (operation 1405) may be omitted, for example, if the MEC application to which the client application 310 should connect is already running and a URI has been received in an application list acquisition procedure (e.g., MEC Application Look-up).

[0254] FIG. 15 is a diagram illustrating an example of a MEC host selection procedure in a discovery procedure according to various embodiments of the present disclosure.

[0255] As shown in FIG 15, FIG 15 may show a MEC host selection operation (MEC Host selection) 1501 for the MSE 330 to select a DNS server 1020 and a MEC host. According to one embodiment, the MEC host selection operation (operation 1501) may include a DNS (pre)resolving operation (e.g., operation 1510), a MEC Host Prioritization operation (e.g., operation 1520), and a DNS caching operation (e.g., operation 1530).

[0256] 15, the MSE 330 may perform DNS resolving (resolving or pre-resolving) in operation 1510. According to one embodiment, DNS resolution may be performed by the MSE 330 itself for the MEC FQDN, regardless of a DNS query from the client application 310. According to one embodiment, the DNS resolution (operation 1510) may include operations 1511 and 1513.

[0257] According to one embodiment, in operation 1511, the MSE 330 may perform a DNS resolving operation with the DHL 335. According to one embodiment, the MSE 330 may send a DNS query to the DNS server 1020 with the URI (FQDN) for the MEC application.

[0258] According to one embodiment, in operation 1513, the DNS server 1020 may receive the DNS query from the MSE 330 and send a DNS response to the MSE 330 in response to the DNS query. According to one embodiment, the DNS response may include at least one address information (e.g., a URI or IP address) associated with the MEC host.

[0259] At operation 1520, the MSE 330 may perform a MEC Host Prioritization operation. According to one embodiment, the MEC Host Prioritization may include setting IP prioritization, for example, when multiple IP addresses are received in a DNS query response. For example, the MSE 330 may set priorities for the MEC hosts.

[0260] According to one embodiment, the MSE 330 can obtain (or receive) a candidate IP list for a plurality of MEC hosts from the MMP server 370, and can specify a connection IP selection or priority among the MEC host candidate IPs and the IP addresses of a remote server (e.g., the remote server 306 in FIG. 3) based on additional information of the candidate IP list (e.g., at least one of the MEC host location, the user's current location, the user speed, or the MEC host performance (e.g., RTT (round trip time), throughput)). According to one embodiment, when selecting a connection IP from the candidate IP list, either the MEC host IP or the IP of the remote server can be selected. For example, if all MEC host locations are at a certain distance or more from the user location, or the RTT value is at a certain value or more, or the user movement speed is at a certain value or more, the remote server IP can be selected instead of the MEC host IP. According to an embodiment, the MSE 330 (e.g., the MEL 331) may select an optimal MEC host through a pre-performance measurement (or test) (e.g., ping probing or bandwidth estimation) for a plurality of candidate MEC hosts. According to an embodiment, the DNS server 1020 may record location information of the MEC host together with the IP address of the MEC host in a DNS response message. For example, if location information of the MEC host is included for a location record type (e.g., LOC record type) among DNS types in a received DNS response message after a DNS query during DNS resolution, the MSE 330 may select a neighboring MEC host using the location information. According to an embodiment, the MSE 330 may acquire location information of the MEC host (e.g., latitude, altitude, serving cell ID, display information, or ID) from the DNS server 1020 in a DNS query operation for acquiring the IP address of the MEC host. For example, the location information of the MEC host may be included in the DNS type field.

[0261] In operation 1530, the MSE 330 may perform DNS caching in the DNS cache 1010. According to an embodiment, when the MSE 330 receives a DNS response including address information in response to the DNS query from the DNS server 1020, the MSE 330 may store the address information included in the DNS response (e.g., an IP address corresponding to a URI (FQDN) related to an MEC host) in a local DNS cache for MEC (e.g., DNS Cache 2). According to an embodiment, when address information (e.g., a URI or IP address) for an MEC application is requested from the client application 310, the MSE 330 may transmit the address information stored in the local DNS cache for MEC. According to various embodiments, in relation to the operation of the local DNS cache for MEC (e.g., DNS Cache 2), a method of separately operating a local DNS cache for MEC (e.g., DNS Cache 2) of FIG. 16 described below or a method of including and operating a local DNS cache for MEC (e.g., DNS Cache 2) in the MSE 330 of FIG. 17 described below may be used. The operation of operating the local DNS cache for MEC according to one embodiment will be described in detail with reference to the drawings below.

[0262] According to various embodiments, the electronic device 101 may receive information (e.g., URI or IP address) of a plurality of MEC hosts on which the MEC application can operate, in a communication procedure (e.g., discovery / application context generation) with the MMP server 370 based on the MEC host selection operation. According to one embodiment, the electronic device 101 may select and communicate with any one of a plurality of MEC hosts that are selected at any time. According to various embodiments, the electronic device 101 may select a plurality of MEC hosts on which the MEC application can operate based on a priority order. According to one embodiment, the priority order may be determined based at least on latency measurement information between the electronic device 101 and the MEC host or location information of the MEC host.

[0263] Hereinafter, in accordance with various embodiments, an operation of maintaining and / or managing DNS caching data for MEC client applications in the electronic device 101 separately from DNS caching data for general client applications will be described.

[0264] FIG. 16 is a diagram illustrating an example of separately operating a local DNS cache for MEC in an electronic device 101 according to various embodiments of the present disclosure.

[0265] 16, an example in which a local DNS cache for MEC is configured separately from the MSE 330 of the electronic device 101 may be illustrated. According to an embodiment, general client applications 1610 may perform DNS caching in a first DNS cache 1620, and MEC client applications 310 may perform DNS caching in a second DNS cache 1630. For example, the general client applications 1610 may use the first DNS cache 1620, and the MEC client applications 310 may use the second DNS cache 1630.

[0266] According to one embodiment, a request can be made using a DNS resolving API for a URI that a client application wishes to access, and an IP address for the URI can be received. For example, the MSE 330 (e.g., the DHL 335) (or a DNS processing module on the OS or framework of the electronic device 101) can change the request of the client application to a DNS query (e.g., FQDN) message, make a request to the DNS server 1020, receive a DNS response (e.g., an IP address corresponding to the FQDN), cache the response, and transmit it to the client application. According to one embodiment, the MSE 330 can determine which DNS cache to use for each client application or URI (FQDN), and a separate DNS processing module (e.g., FIG. 16 or the DHL of the MSE (FIG. 17) can then refer to the first DNS cache 1620 or the second DNS cache 1630 and deliver the IP address to the client application. According to one embodiment, the DNS processing module or DHL can first refer to the DNS cache for the requested URI (FQDN) and deliver the IP corresponding to the URI if there is one, and if not in the cache, perform a DNS query to the DNS server 1020.

[0267] FIG. 17 is a diagram illustrating an example of operating a local DNS cache for MEC in an MSE 330 in an electronic device 101 according to various embodiments of the present disclosure.

[0268] 17, an example of configuring a local DNS cache for MEC (e.g., second DNS cache 1630) in the MSE 330 of the electronic device 101 may be shown. According to one embodiment, the general client application 1610 may perform DNS caching in the first DNS cache 1620, and the MEC client application 310 may perform DNS caching in the second DNS cache 1630. For example, the general client application 1610 may use the first DNS cache 1620, and the MEC client application 310 may use the second DNS cache 1630.

[0269] According to one embodiment, a request can be made using a DNS resolving API for a URI that a client application wishes to access, and an IP address corresponding to the URI can be received. For example, a DNS processing module on an OS or framework of the MSE 330 (e.g., the DHL 335) (or the electronic device 101) can change the request of the client application to a DNS query (e.g., FQDN) message, make a request to the DNS server 1020, receive a DNS response (e.g., an IP address corresponding to the FQDN), cache the message, and transmit the response to the client application. According to one embodiment, the MSE 330 can determine which DNS cache to use for each client application or URI (FQDN), and a separate DNS processing module (e.g., FIG. 16 or the DHL of the MSE (FIG. 17) can then refer to the first DNS cache 1620 or the second DNS cache 1630 and deliver the IP address to the client application. According to one embodiment, the DNS processing module or DHL can first refer to the DNS cache for the requested URI (FQDN) and deliver the IP corresponding to the URI if there is one, and if not in the cache, perform a DNS query to the DNS server 1020.

[0270] According to various embodiments, the division of the general client application 1610 and the MEC client application 310 and the DNS caching will be described in detail with reference to the following drawings (eg, FIG. 36).

[0271] FIG. 18 is a diagram illustrating an example of a DNS resolving operation in a discovery procedure according to various embodiments of the present disclosure.

[0272] As shown in Figure 18, Figure 18 may illustrate a DNS resolving operation for a DNS query of the client application 310. According to one embodiment, the DNS resolving operation may include an operation when the DNS server 1020 is in a deactivated state (e.g., operation 1810) and an operation when the DNS server 1020 is in an activated state (e.g., operation 1830).

[0273] According to one embodiment, the DNS resolving operation of operation 1810 may represent an example of an operation in a state where a local DNS cache for MEC (e.g., second DNS cache 1630) is deactivated in the DNS cache 1010. Referring to FIG 18, the client application 310 may transmit a DNS query for a URI to the DNS cache 1010 (operation 1811), and the DNS cache 1010 may transmit a response (e.g., DNS Cache Response) to the DNS query of the client application 310 to the client application 310 (operation 1813). According to one embodiment, the DNS cache 1010 may store at least one of an application name, a domain name, or an IP address for a domain name of the MEC application. In one embodiment, when a DNS query for a URI of a client application 310 is made and the IP address of the MEC application for that URI is not present in the DNS cache 1010 (e.g., a DNS cache miss), the client application 310 transmits the DNS query to the DNS server 1020 (operation 1815) and can obtain the IP address from the DNS server 1020 based on a response 1817 corresponding to the DNS query.

[0274] According to one embodiment, the DNS resolving operation of operation 1830 may represent an example of an operation in a state where a local DNS cache for MEC (e.g., second DNS cache 1630) is activated in DNS cache 1010. Referring to FIG 18, client application 310 may transmit a DNS query for a URI to DNS cache 1010 via MSE 330 (operations 1831 and 1833). According to one embodiment, DNS cache 1010 may transmit a DNS response for the DNS query to MSE 330 (operation 1835). In one embodiment, when a DNS query is made for a URI of a client application 310, if the IP address of the MEC application for that URI is not present in the DNS cache 1010 (e.g., a DNS cache miss), the MSE 330 can transmit the DNS query to the DNS server 1020 (operation 1837), receive a response corresponding to the DNS query from the DNS server 1020 (operation 1839), and forward the received response to the client application 310 (operation 1841).

[0275] According to one embodiment, if the IP address of the MEC application for the URI is found in the DNS cache 1010 at the time of a DNS query for the URI of the client application 310, the MEC application can be connected to the address. According to one embodiment, in the case of a DNS cache miss in DNS resolution, a remote server (e.g., the remote server 306 in FIG. 3) or a Client App-driven MEC application can be connected to through DNS resolution. According to one embodiment, in the case of DNS resolution, if there is a DNS proxy, the DNS proxy can hook the DNS query of the client application and perform DNS resolution according to the MEC app list.

[0276] According to one embodiment, the MSE 330 can support DNS pre-resolving or DNS proxy functionality for a third party application. For example, when the MEC client application 310 makes a DNS query for a specific service connection while connected to data via an existing basic PDU session, the DNS proxy can intercept the DNS query and query the DNS server 1020 for the MEC domain name or return the MEC domain IP address by looking up the DNS cache 1010. Through this, the third party application can provide MEC services without additional software modifications and without additional traffic filtering (or steering) by the operator.

[0277] Meanwhile, each of the signaling flowcharts described above may be connected to other signaling flowcharts as necessary, for example, after an authentication operation (e.g., at least one of FIGs. 4 to 6), the operation of FIG. 7 for performing NAS signaling may be performed.

[0278] In addition, each of the signal flow charts described above may be replaced with a part of another signal flow chart as necessary. For example, the authentication operations of Figures 4 to 6 may be replaced with operations used in other figures.

[0279] The various embodiments of the present disclosure disclosed in the specification and drawings are presented as specific examples to easily explain the contents of the present disclosure and to facilitate understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. Therefore, the scope of the present disclosure should be interpreted as including all modifications or alterations derived based on the technical ideas of the present disclosure in addition to the embodiments disclosed herein. [Industrial Applicability]

[0280] The present disclosure can be used in cases for providing edge computing services in wireless communication systems.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, comprising: transmitting a discovery request message to a server to obtain information related to an application server, the discovery request message including location information and an application client profile of the terminal; receiving, from the server, a discovery response message in response to the discovery request message, the discovery response message including the location information of the terminal and the information associated with the application server based on the application client profile; The information associated with the application servers includes a list of the application servers and uniform resource identifiers (URIs); The method, wherein the location information of the terminal includes a cell identifier (ID) or a tracking area ID (TAI).

2. The method of claim 1 , wherein the discovery request message further includes at least one of a discovery policy or a service type.

3. 2. The method of claim 1, wherein the information associated with the application server further includes lifetimes of the URIs.

4. The method of claim 1, wherein the discovery request message further includes at least one of a device type, a context type, or a dynamic network name (DNN).

5. In a terminal (user equipment, UE) in a wireless communication system, A transmitting / receiving unit; a control unit coupled to the transceiver unit, The control unit is transmit a discovery request message to a server to obtain information related to an application server, the discovery request message including location information of the terminal and an application client profile; receiving from the server a discovery response message in response to the discovery request message, the discovery response message including the location information of the terminal and the information associated with the application server based on the application client profile; The information associated with the application servers includes a list of the application servers and uniform resource identifiers (URIs); The terminal, wherein the location information of the terminal includes a cell identifier (ID) or a tracking area ID (TAI).

6. The terminal of claim 5, wherein the discovery request message further includes at least one of a discovery policy or a service type.

7. The terminal of claim 5, wherein the information associated with the application server further includes lifetimes of the URIs.

8. The terminal of claim 5, wherein the discovery request message further includes at least one of a device type, a context type, or a dynamic network name (DNN).

9. 1. A method performed by a server in a wireless communication system, comprising: receiving a discovery request message from a terminal for obtaining information related to an application server, the discovery request message including location information and an application client profile of the terminal; obtaining the information associated with the application server based on the location information of the terminal and the application client profile; transmitting a discovery response message to the terminal in response to the discovery request message, the discovery response message including the information associated with the application server; The information associated with the application servers includes a list of the application servers and uniform resource identifiers (URIs); The method, wherein the location information of the terminal includes a cell identifier (ID) or a tracking area ID (TAI).

10. The method of claim 9 , wherein the discovery request message further includes at least one of a discovery policy or a service type.

11. 10. The method of claim 9, wherein the information associated with the application server further includes lifetimes of the URIs.

12. The method of claim 9, wherein the discovery request message further includes at least one of a device type, a context type, or a dynamic network name (DNN).

13. In a server in a wireless communication system, A transmitting / receiving unit; a control unit coupled to the transceiver unit, The control unit is receiving a discovery request message from a terminal for obtaining information related to an application server, the discovery request message including location information and an application client profile of the terminal; obtaining the information associated with the application server based on the location information of the terminal and the application client profile; transmitting a discovery response message to the terminal in response to the discovery request message, the discovery response message including the information associated with the application server; The information associated with the application servers includes a list of the application servers and uniform resource identifiers (URIs); The server, wherein the location information of the terminal includes a cell identifier (ID) or a tracking area ID (TAI).

14. The server of claim 13, wherein the discovery request message further includes at least one of a discovery policy or a service type.

15. 14. The server of claim 13, wherein the information associated with the application server further includes lifetimes of the URIs.

16. The server of claim 13, wherein the discovery request message further includes at least one of a device type, a context type, or a dynamic network name (DNN).

Citation Information

Patent Citations

  • Web server and program for collecting sensing data

    JP2009145989A

  • Management device for local device access in mobile communication systems

    JP2012524424A

  • Information relay device and on-vehicle information terminal

    JP2013115680A

  • Method and apparatus for accessing localized applications

    JP2016208548A

  • Proximity service search method and apparatus for providing proximity service

    JP2016523044A