KR102169614B1 - Method for application hosting by access node and apparatus therefor - Google Patents

Abstract

Disclosed is a method and apparatus for hosting an application by an access node. The method according to the present invention includes the process of receiving a request packet for a service request from a user application of a mobile terminal, and when a destination of the request packet corresponds to an application provided in an access node, the request packet is sent to the access node. The process of transferring to the application, the process of providing a service to the user application of the mobile terminal by the application, and when the application corresponding to the destination of the request packet does not exist in the access node, the request packet is transmitted to the Internet. It includes the process of delivering to the corresponding public application on the image.

Description

Application hosting method and apparatus by access node {METHOD FOR APPLICATION HOSTING BY ACCESS NODE AND APPARATUS THEREFOR}

The present invention relates to a wireless communication system, and more particularly, to a method and apparatus for hosting an application service in an access node of a wireless communication system.

Due to the rapid increase in use of portable computing devices such as smartphones and tablet computers, various Internet application services are provided through cellular mobile communication networks. In a cellular mobile communication system, a typical access node in charge of wireless access to a mobile terminal transmits the Internet service request to an application server (AS) of the Internet when the Internet service request of the terminal is received, from the application server. It is configured to perform only the role of a simple bit-pipe that transmits the response of the user to the terminal.

The existing platforms as described above have problems in that it is difficult to host various applications, and it is difficult to differentiate between applications and provide different levels of quality of service (QoS). In addition, it is not easy to add new additional services corresponding to technological changes, and it is not easy to utilize the resources of the access network to provide various application services.

The present invention provides a method and apparatus for hosting applications by an access node in a cellular mobile communication network.

The present invention provides a method and apparatus for hosting various applications by an access node and utilizing information of an access network.

The present invention provides a method and apparatus for filtering a user's service request by a base station application as needed.

The present invention provides a method and apparatus for allowing a base station to directly provide an Internet service to a terminal through interworking with an access network and a base station application.

A method of hosting an application in an access node according to a preferred embodiment of the present invention includes a process of receiving a request packet from a user application of a mobile node, and identifying a destination of the request packet based on information included in the request packet. When the destination of the request packet is the application executed in the access node, the mobile node uses the application executed in the access node by transferring the request packet to the application executed in the access node. A process of providing a service to the user application of and, when the destination of the request packet is not the application executed in the access node, transferring the request packet to the core network.

An access node for hosting an application according to a preferred embodiment of the present invention includes a communication unit that performs communication with an external device through a network, and an application hosting unit connected to the communication unit, wherein the application hosting unit includes: When a request packet is received from a user application of a mobile node, a destination of the request packet is identified based on information included in the request packet, and the destination of the request packet is an application executed in the access node, the access node When a service is provided to the user application of the mobile node using the application executed in the mobile node, and the destination of the request packet is not the application executed in the access node, the request packet is transferred to the core network through the communication unit. I can deliver.

1 schematically shows a system configuration for providing an Internet service through an access network.
2 is a schematic diagram of a system configuration including a base station system according to an embodiment of the present invention.
3 shows a configuration of an access node according to an embodiment of the present invention.
4 is a diagram illustrating a message flow diagram for a scenario in which a terminal receives a service from an edge app or a public app according to an embodiment of the present invention.
5 is a flowchart illustrating a message flow diagram for a scenario in which a terminal receives access network information according to an embodiment of the present invention.
6 shows a detailed configuration of a filtering and delivery unit according to an embodiment of the present invention.
7 to 9 illustrate operations according to service scenarios according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Further, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary depending on the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

Mobile devices such as mobile stations (MS), user equipment (UE), smartphones, or tablet computers equipped with a communication module are 3GPP (3rd generation partnership project) LTE (long-term evolution). ) Is configured to be accessible to the Internet through an access network of a cellular wireless communication system.

1 schematically shows a system configuration for providing an Internet service through an access network.

Referring to FIG. 1, the mobile terminal 100 includes a communication module capable of cellular wireless communication, and requires access to an application 122 running on an AS 124 on a public network such as the Internet 120. It has one or more applications 102. In the present specification, for convenience of description, the application 102 running on the mobile terminal is referred to as "user application", and the application 122 (or application server) running on the Internet 120 is referred to as "public app ( public application)".

The mobile terminal 100 accesses the Internet 120 through the operator network 110, the operator network 110 including an access network (AN) 112 and a core network (CN) 118, and , The access network (AN) 112 is an access node 114 such as a base station (BS) or a node ratio (Node B) or eNB (Evolved Node B) providing a network access point of the mobile terminal 100 Including, the core network 118 is configured to include at least one data service node that provides access to an external network such as the Internet (120).

The access node 114 includes a baseband unit (BBU) 116 responsible for processing data and signaling signals of a mobile communication network. The service request by the user app 102 is transmitted to the public app 122 of the Internet 120 through the operator network 110, and the public app 122 transmits content or information to the mobile terminal in response to the received service request. Provided as (100). At this time, the access network 112 and the core network 118 of the operator network 110 process service requests and user traffic for the mobile terminal 100 according to a policy and rule based on subscriber information. do.

The following embodiments of the present invention relate to an access node in an access network, instead of a server on the Internet, directly providing a service by an application to a mobile terminal.

2 is a schematic diagram of a system configuration including a base station system according to an embodiment of the present invention.

Referring to FIG. 2, the mobile terminal 200 executing the user app 202 is connected to the access network of the operator network through the access node 210, and the access node 210 is connected to the Internet through the core network 220. It is connected to the public app 232 provided in the application server 234 of 230. The access node 210 refers to a base station that provides access to the mobile communication network to the mobile terminal 200, and may be a Node B in a 3G network and an eNB in an LTE network.

The access node 210 includes a baseband unit (BBU) 212 in charge of processing normal data and signaling signals for a mobile communication network, and additionally, a filter unit 214 that distinguishes and processes data of a specific application packet. And, a network information handler 216 that obtains information on an access network (hereinafter referred to as access network information) when necessary. In addition, the access node 210 may host an application 218 for user service. In this specification, the application 218 running on the access node 210 is referred to as "edge application". It is called this. The edge app 218 may provide a service to a user by utilizing dynamically changing access network information, and, if necessary, may provide a service by interworking with the public app 232 of the Internet 230 through a core network.

The user app 202 of the mobile terminal 200 may request specific access network information from the access node 210 and may also request a service from the edge app 218 or the public app 232. When the user app 202 requests direct access network information, the service request for the request is filtered in the filter unit 214 of the BBU 212 and transmitted to the network information processing unit 216, and the network information processing unit 216 In response to the service request, access network information is transmitted to the user app 202 of the mobile terminal 200. When the user app 202 of the mobile terminal 200 requests a service to the edge app 218 or a specific public app 232, the service request for that is filtered by the filter unit 214 of the BBU 212 and It is delivered to the app 218. The edge app 218 directly provides a service in response to the service request, or provides a service using information or content from the public app 232.

Various types of services may be provided through the edge app 218 hosted on the access node 210, and examples of possible service scenarios are as follows.

The first service scenario is that the user app of the terminal requests a service to the edge app of the access node, and the edge app directly delivers content or information to the mobile terminal in response to the received service request. This type of service can be used to service local information such as local weather or to provide traffic information of an access network to an authenticated mobile terminal, and does not generate service traffic to the core network of the operator's network, thereby preventing backhaul. There is an advantage that can be saved.

In the second scenario, the user app requests a service to the edge app, but the edge app handles the service request either directly or through communication with a public app. In this case, the edge app may directly transmit a response to the service to the user app, but if necessary, it may communicate with the public app to obtain desired information or content. An example of such a service scenario is a real-time game, where the edge app delivers information that can be responded directly to the user without communicating with the public app, and additional information that the edge app does not have is acquired by communicating with the public app on the Internet. , Providing services to users by using the acquired information.

In the third service scenario, the edge app operates transparently between the user app and the public app, and the user app does not know that the edge app is in the middle and is considered to receive services by communicating with the public app. An example of such a service scenario is an edge cache that operates transparently, and an edge app operates as an edge cache, thereby reducing a response time to a user request and a content transmission time.

In the present specification, the above service scenarios have been described as examples, but it is of course possible to provide various types of services through an edge app in another embodiment of the present invention.

Hereinafter, a configuration of an access node related to a service scenario for processing a request for access network information and a service request will be described in detail.

3 shows a configuration of an access node according to an embodiment of the present invention. Here, an example of an LTE base station is shown.

Referring to FIG. 3, a mobile terminal 300 executing a user app (or user app execution block) 302 is connected to the access network of the operator network through an access node 310, and the access node 310 is a core The public app 352 on the Internet 350 may be accessed through the network 340.

The access node 310 includes a baseband unit (BBU) 314 for processing normal data and signaling signals for a mobile communication network and a network information processing unit 322 for managing information on the access network ( 312) and an app hosting unit 330 configured to drive at least one edge app (or edge app execution block) 334 and 336. Here, only the packet data convergence protocol (PDCP) processing unit 316 and the GPRS (general packet radio service) tunneling protocol (GTP) processing unit 320 among the protocol stacks of the BBU 314 are shown, and the lower layer of the PDCP processing unit 316 These radio link control (RLC), medium access control (MAC), and physical (PHY) are omitted for convenience of description.

The PDCP processing unit 316 is responsible for packet communication between the mobile terminal 300 and the access node 310, and processes conversion and interpretation of an IP (internet protocol) packet. The GTP processing unit 320 transfers the IP packets from the PDCP processing unit 316 to the Internet 350 through the core network 340 or transfers the IP packets flowing from the Internet 350 through the core network 340 to the PDCP processing unit. Forward to 316.

A filtering and forwarding unit (FAFU) 318 located between the PDCP processing unit 316 and the GTP processing unit 320 is a mobile terminal 300, an edge app 334,336, a public app 352, and an application program. IP packets transmitted or received between the interface (application program interface: API) module 324 are distinguished according to a predetermined rule and transmitted to a corresponding destination.

Specifically, the filtering and delivery unit 318 distinguishes packets for network information request and/or service request transmitted from the user app 302 of the mobile terminal 300 according to a preset rule, and processes the request ( entity). The packet for requesting network information received from the user app 302 is transmitted to the network information processing unit 322 by the filtering and forwarding unit 318, and the service request received from the user app 302 is the corresponding edge app 334,336 ).

When a packet destined for the mobile terminal 300 is received from the public app 352 or the edge apps 334 and 336, the filtering and forwarding unit 318 transmits the packet to the mobile terminal 300 through the PDCP 316. In addition, the filtering and forwarding unit 318 may transmit a specific packet transmitted from the terminal or a specific packet transmitted from the AG apps 334 and 336 to the API module 324 of the network information processing unit 322, and from the API module 324 The transmitted response packet is transmitted to the mobile terminal 300 through the PDCP 316 or to the corresponding edge apps 334 and 336.

The network information processing unit 322 receives the network information request to the network information processing unit 326 by the API module 324.

As an embodiment, the filtering and forwarding unit 318 includes a destination IP address included in a header of a request packet including a network information request or a service request, or a universal resource locator (URL) included in the header of the request packet. Can be used to determine which entity will forward the request packet. As an embodiment, when the edge app 334 is configured in the access node 310, the destination IP address and URL destined for the edge app 334 are set in the filtering and forwarding unit 318 as filtering rules. When a request packet including a destination IP address and/or URL set as the filtering rule is introduced, the filtering and forwarding unit 318 forwards the request packet to the edge app 334 instead of forwarding it to the core network 340 do.

The filtering and delivery unit 318 and the edge apps 334 and 336 are connected via an IP-in-IP tunnel or inter-process communication (IPC). Similarly, packet delivery between the filtering and delivery unit 318 and the API module 324 of the network information processing unit 322 may be performed through an IP-in-IP tunnel or IPC.

When the API module 324 of the network information processing unit 322 receives a request packet for network information, it identifies the request packet and transmits it to the information retrieval unit 326. The information acquisition unit 326 collects information on the access node 310 from the BBU 314 of the access node 310, an operation and maintenance (OAM) unit, or other functional block, or Network information is periodically or aperiodically collected, stored and managed, and desired network information is configured according to the request of the API module 324 and transmitted to the API module 324. Examples of network information managed by the information acquisition unit 326 include a base station identifier (or cell identifier), a base station load (cell load or load level indicator), and radio resource usage (resource block (RB) usage). , Base station bandwidth usage (bandwidth (BW) usage), channel information of an access subscriber, and the like.

The API module 324 configures the network information obtained from the information acquisition unit 326 in an IP packet format and transmits it to the user app 302. Specifically, the IP packetized network information is transmitted from the API module 324 to the filtering and delivery unit 318 of the BBU 314, and then transmitted to the user app 302 through the corresponding protocol stack of the BBU 314. do. If necessary, at least one edge app (334,336) may transmit a request packet for access network information to the API module 324, the API module 324 obtains the requested network information from the information acquisition unit 326 It is transmitted to the edge apps (334,336).

The API module 324 requests for network information between the user app 302 or the edge apps 334 and 336 so that the information of the access node 310 can be inquired and provided to the mobile terminal 300 or edge apps 334,336. And an interface for delivering a response. The interface between the API module 324 and the edge apps 334 and 336 may be implemented as a Web API such as REST (representational state transfer) as an example, and as another example, a software development kit (SDK), It can be implemented in several different forms, such as a library.

The edge apps 334 and 336 hosted on the access node 310 are applications that can be executed on a general IT server, and are executed on one operating system (OS), or the access node 310 is logically divided into several virtual machines ( virtual machine), it can run on one or multiple virtual machines. The edge apps 334 and 336 of FIG. 3 are hosted in one virtual machine, and the edge apps 334 and 336 are connected to the BBU 314 through a virtual switch 332.

Hereinafter, service scenarios for processing an application service request and an access network information request from a terminal will be described with reference to a message flow diagram of FIGS. 4 and 5.

4 is a diagram illustrating a message flow diagram for a scenario in which a terminal receives a service from an edge app or a public app according to an embodiment of the present invention.

4, in step 402, a session is established between the mobile terminal 300 and a packet data node (not shown) in the core network 340, and the core network 340 moves through the session establishment. Allocates an IP address to the terminal 300. In step 404, the mobile terminal 300 transmits a request packet for a service request generated by the user app 302 to the access node 310. The service request by the user app 302 of the mobile terminal 300 may be configured in a format similar to a general HTTP (hyper text transfer protocol) web content request as an example.

In step 406, the request packet of the mobile terminal 300 is filtered according to a predetermined rule in the filtering and forwarding unit 318 of the BBU 312 in the access node 310, and the corresponding packet confirmed through the filtering in step 408 It is sent to the Edge app.

In one embodiment, filtering may be performed based on the destination IP address included in the header of the request packet. That is, when a request packet having a destination IP address set in advance is received, the filtering and forwarding unit 318 transmits the request packet to a corresponding edge app. As another embodiment, the filtering and forwarding unit 318 may perform filtering using the destination URL included in the header of the request packet.

In step 408, the filtered request packet is transmitted to the corresponding edge app 334 through IP-in-IP tunneling.

In step 410, in response to the service request of the request packet, the edge app 334 requests preset available network information to the network information processing unit 322, and network information through API communication with the network information processing unit 322 Receive.

As an embodiment, communication for requesting network information and transmitting a request result between the edge app 334 and the network information processing unit 322 is performed through a WEB API or an SDK type interface.

In step 412, the edge app 334 provides the network information corresponding to the request packet to the mobile terminal 300 via the BBU 312. As an example, the network information may be composed of one or more IP packets. If necessary, the edge app 334 may obtain information or content necessary for providing a desired service by the mobile terminal 300 by requesting it from the public app 352.

If the edge app 334 cannot accept the service request of the request packet, that is, if the mobile terminal 300 does not provide the requested service, the edge app 334 sends the request packet in step 416. It forwards to the filtering and forwarding unit 318 of the BBU 312.

In step 418, the filtering and forwarding unit 318 of the BBU 312 directly transmits the request packet to the corresponding public app 352 of the Internet 350 through the core network 340, and in step 420, the public app 352 ) Provides the requested service to the mobile terminal 300 via the core network 340 and the BBU 312 of the access node.

As an embodiment of a specific service, when the edge app 334 provides a caching service for the public app 352, the service content from the public app 352 is cached (ie stored) in the edge app 334, The edge app 334 provides the service content to the mobile terminal 300.

5 is a flowchart illustrating a message flow diagram for a scenario in which a terminal receives access network information from an edge app according to an embodiment of the present invention.

5, in step 502, a session is established between the mobile terminal 300 and a packet data node (not shown) in the core network 340, and through the session establishment, the core network 340 ) To the IP address.

In step 504, the mobile terminal 300 transmits a request packet for requesting access network information generated by the user app 302 to the access node 310. The request for the access network information may be configured in a format similar to a general HTTP web content request, for example.

In step 506, the request packet of the mobile terminal 300 is filtered according to a predetermined rule in the filtering and forwarding unit 318 of the BBU 312 in the access node 310, and in step 508, the network information processing unit is filtered by the filtering. It is forwarded to (322).

As an embodiment, the filtering and forwarding unit 318 transmits the request packet to the core network 340 if the destination IP address or destination URL included in the header of the request packet is a predetermined IP address or URL for requesting network information. Instead of transmitting it, it is transmitted to the network information processing unit 322.

Communication for network information request and request result transmission between the user app 302 of the mobile terminal 300 and the network information processing unit 522 may be performed using an open interface. As an embodiment, a WEB API such as REST is used. Or use the SDK type interface.

In step 510, the network information processing unit 322 provides the network information to the user app 302 of the mobile terminal 300 through the BBU 312 in response to the network information request of the request packet.

As an example, the network information may include at least one of weather of a region to which the access network belongs, load of the access network and/or access node, backhaul bandwidth, and location information according to the request of the mobile terminal 300. And can be composed of one or more IP packets.

6 shows a detailed configuration of a filtering and delivery unit according to an embodiment of the present invention.

6, the filtering and delivery unit 318 is located between the GTP processing unit 320 and the PDCP processing unit 316, and includes a rule storage unit 602, a filtering unit 604, and a mapping unit 606. It is composed by

The filtering rule 600 is composed of a 5-tuple of IP, i.e., a source IP address, a source port number, a destination IP address, a destination port number, and a protocol type, and a command line is provided by a base station operator. It may be directly input through or set by a system administrator (not shown) of the operator network.

The system manager is a management node configured to provide an interface of an operator matching function so that an operator can operate and maintain an access node, and provides software management, configuration management, performance management, and failure management functions.

Each filtering rule corresponds to each edge app, and can be set/changed/deleted when each edge app is installed/updated/deleted on the access node. When the edge app is installed on the access node, the system administrator obtains information on the corresponding filtering rule, and delivers the information to the filtering and delivery unit 318, and the filtering and delivery unit 318 The filtering rule is stored in the rule storage unit 602, and a tuple of the filtering rule and the corresponding edge app is generated.

The filtering unit 604 filters packets received from the GTP processing unit 320, the PDCP processing unit 316, the edge app 334, or the network information processing unit 322 according to the filtering rules stored in the rule storage unit 602. , The mapping unit 606 determines a corresponding destination according to the filtering and transmits the packets to the determined entity. An example of packet filtering according to the destination is as follows.

As an example, a downlink (DL) packet received through the GTP processing unit 320 is directly transmitted to the PDCP processing unit 316 or transmitted to the corresponding edge app 334 through the mapping unit 606. As another example, an uplink (UL) packet received through the PDCP processing unit 316 is directly sent to the GTP processing unit 320 or the corresponding edge app 334 or the network information processing unit 322 through the mapping unit 606 ).

As another example, a packet received from the edge app 334 is transmitted to the GTP processing unit 320 or transmitted to the PDCP processing unit 316. As another example, a packet received from the network information processing unit 322 is transmitted to the PDCP processing unit 316 or transmitted to the corresponding edge app 334.

The mapping unit 606 determines a tuple according to the edge app 334 when packets are transmitted from the filtering and forwarding unit 318 to the edge app 334, and conversely, the tuple of packets received from the edge app 334 Accordingly, it is determined whether to forward the packets to the PDCP processing unit 316 or the GTP processing unit 320. For this operation, the mapping unit 606 includes a bearer ID of a radio bearer used for packet transmission between an access node and a mobile terminal, a tunneling endpoint ID (TEID) used for GTP tunneling, and At least one of a source IP address/port number, a destination IP address/port number, and IP information for tunneling may be used.

7 to 9 illustrate operations according to service scenarios according to an embodiment of the present invention.

Referring to FIG. 7, the public app 704 is installed in an application server (AS) 702 located on the Internet. User equipment (UE) 716 includes at least one user app 718 and connects to the access node 710 using wireless access technology.

The access node 710 includes an eNB block 712 configured with a modified existing base station platform and at least one edge app 714, and a public app of the application server 702 through a core network (CN) 706 ( 704).

The eNB block 712 includes a protocol stack according to an existing base station platform, for example, PHY, MAC, RLC, PDCP, GTP, and the like, and may additionally include a filtering and forwarding unit. The core network 706 may be configured with an evolved packet core (EPC) of an LTE system as an example.

The user app 718 directly accesses a specific edge app 714 of the access node 710 related to a desired service, for example, local weather or advertisement provision, and content or content for the desired service from the edge app 714 Information is received (720).

Access information for the edge app 714, as an example, a destination IP address or destination URL may be provided to the user through an offline advertisement flyer, TV, media, etc., and the user input means of the user device 716 The destination IP address or destination URL can be directly entered.

As another embodiment, the access node 710 provides advance information (advertisement, etc.) on services that can be provided through the edge app 714 through a wireless channel to the user device 716, and the user device 716 is a display screen. A service request for the edge app 714 is triggered by displaying a soft button or menu key accessible to the edge app 714 through and detecting a selection (touch) for the soft button or menu key from the user can do.

In another embodiment, a user or a specific app installed in the user terminal requests and obtains access information for the edge app 704 using a preset IP address or URL, and the user uses the obtained access information to obtain the You can request a service with the Edge app.

Referring to FIG. 8, a public app 804 is installed in an application server (AS) 802 located on the Internet. User equipment (UE) 816 includes at least one user app 818 and connects to the access node 810 using wireless access technology. The access node 810 includes an eNB block 812 composed of a modified existing base station platform and at least one edge app 814 according to an embodiment of the present invention, and an application server through a core network (CN) 806 It is accessible to 802's public app 804.

The user app 818 transmits a service request for a desired service, for example real-time gaming or online editing, to the access node 810, and the access node 810 requests the service. If an edge app 814 capable of processing is provided, the access node 810 filters the service request and transmits it to the edge app 814.

The edge app 814 provides content or information on the desired service to the user app 818 according to the service request (822). If necessary, the edge app 814 may access the public app 804, request additional information necessary for providing a service, and receive the additional information (820).

Referring to FIG. 9, a public app 904 is installed in an application server (AS) 902 located on the Internet. User equipment (UE) 916 includes at least one user app 918 and connects to the access node 910 using wireless access technology.

The access node 910 includes an eNB block 912 configured with a modified existing base station platform and at least one edge app 914, and a public app of the application server 902 through the core network (CN) 906 ( 904).

As an example, if the edge app 914 provides a transparent caching service, the user app 918 transmits a service request for desired content to the access node 910, and the access node 910 requests the service. Instead of passing it to the public app 904, it is filtered and passed to the edge app 914 first.

When the edge app 914 does not store the content for the desired service according to the service request, it transmits the request for the content to the public app 904, and transmits the request for the content to the public app 904 through the core network 906. ), the content is received and stored (cached), and the stored content is provided to the user app 918 (920). When the content is already stored, the edge app 910 may directly provide the previously stored content to the user app 918 without access to the public app 904.

Embodiments of the present invention operating as described above provide access network information such as base station load, backhaul bandwidth, and location information to a mobile terminal to differentiate application services based on access network information, and to differentiate application services based on different levels of quality of service. of Service: QoS) can be easily supported. In addition, embodiments of the present invention can obtain an effect of adding value-added services or facilitating extension to such services according to the characteristics and technological evolution of the mobile communication network.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention is limited to the described embodiments and should not be determined, and should be determined by the scope of the claims to be described later, as well as the scope and equivalents of the claims.

Claims (2)

In the method of hosting an edge application running on an edge application server providing an application-based service to a mobile terminal,
Receiving information related to the application-based service by using an application program interface (API) related to the application-based service; And
Transmitting information related to the application-based service to an application client of the mobile terminal by using the API;
How to include.
In an edge application server providing an application-based service to a mobile terminal,
Communication department; And
Edge application server comprising; at least one processor for controlling the communication unit to receive information related to the application-based service using an application program interface (API) related to the application-based service.

Images