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

Abstract

Disclosed are a method for hosting an application by an access node and a method therefor. The method according to the invention includes the steps of: receiving a request packet for a service request from a user application of the mobile terminal; forwarding, when the destination of the request packet corresponds to an application provided in an access node, the request packet to the application in the access node; providing a service to a user application of the mobile terminal by the application; and forwarding, if the application corresponding to the destination of the request packet does not exist in the access node, the request packet to the corresponding public application on the Internet.

Description

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 the 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 normal access node in charge of wireless connection with a mobile terminal delivers the Internet service request to an application server (AS) of the Internet when an Internet service request of the terminal is received, and from the application server It is configured to perform the role of a simple bit-pipe (bit-pipe), which delivers the response of the terminal to the terminal.

The existing platform as described above has a problem in that it is difficult to host various applications, and it is difficult to provide different levels of quality of service (QoS) for differentiating applications. In addition, it is not easy to add a new value added service corresponding to a technology change, and it is not easy to utilize resources of an 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 making use of information from the access network.

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

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

A method of hosting an application at an access node according to a preferred embodiment of the present invention includes 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 A mobile node using the application running on the access node by forwarding the request packet to the application running on the access node, if a destination of the request packet is the application running on the access node And providing a service to the user application, and transmitting the request packet to the core network when the destination of the request packet is not the application running on the access node.

An access node hosting an application according to a preferred embodiment of the present invention includes a communication unit performing communication with an external device through a network, and an application hosting unit connected to the communication unit, wherein the application hosting unit is via the communication unit If a request packet is received from a user application of a mobile node, and the 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 running on the access node, the access node Provides a service to the user application of the mobile node by using the application running in, and when the destination of the request packet is not the application running in the access node, sends the request packet to the core network through the communication unit Can deliver.

1 schematically shows a system configuration for providing Internet services through an access network.
Figure 2 schematically shows a system configuration including a base station system according to an embodiment of the present invention.
3 shows a structure of an access node according to an embodiment of the present invention.
4 illustrates 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 illustrates a message flow diagram for a scenario in which a terminal receives access network information according to an embodiment of the present invention.
6 illustrates 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. And, in the description of the present invention, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to a user's or operator's intention or practice. Therefore, the definition should be made based on the contents throughout this specification.

A mobile device such as a mobile station (MS), a user equipment (UE), a smartphone, or a tablet computer equipped with a communication module is a 3GPP (3rd generation partnership project) long-term evolution (LTE). ) Is configured to be accessible to the Internet through an access network of a cellular wireless communication system.

1 schematically illustrates a system configuration for providing Internet services 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 the AS 124 on a public network such as the Internet 120. One or more applications 102 are provided. In the present specification, for convenience of description, the application 102 executed on the mobile terminal is referred to as a “user application”, and the application 122 (or application server) executed on the Internet 120 is referred to as a “public app ( public application).

The mobile terminal 100 connects to the Internet 120 through the operator network 110, and the operator network 110 includes an access network (AN) 112 and a core network (CN) 118, The access network (AN) 112 is an access node 114, such as a base station (BS) or node ratio (Node B) or an evolved node B (eNB) that provides a network access point of the mobile terminal 100. The core network 118 comprises 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 in charge of processing data and signaling signals of a mobile communication network. The service request by the user app 102 is delivered to the public app 122 of the Internet 120 through the operator network 110, and the public app 122 moves the content or information in response to the received service request. (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 policy and rules based on subscriber information. do.

The embodiments described below 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 schematically shows 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 a mobile terminal 200 with access to a mobile communication network, and may be a Node B in a 3G network and an eNB in an LTE network.

The access node 210 includes a base band unit (BBU) 212 in charge of processing normal data and signaling signals for a mobile communication network, and additionally a filter unit 214 for distinguishing and processing data of a specific application packet. And a network information handler 216 for acquiring information about the 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, which is referred to herein as an “edge application”. It is called. The edge app 218 may provide a service to the user by using the dynamically changing access network information, and may provide a service by interworking with the public app 232 of the Internet 230 through the core network, if necessary.

The user app 202 of the mobile terminal 200 may request specific access network information to the access node 210, and may also request service to the edge app 218 or the public app 232. When the user app 202 requests the direct access network information, the service request therefor is filtered by 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, the access network information is sent to the user app 202 of the mobile terminal 200. When the user app 202 of the mobile terminal 200 requests a service by the edge app 218 or a specific public app 232, the service request for the service is filtered from the filter unit 214 of the BBU 212 to the edge 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 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 delivers content or information directly 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. Backhaul is not generated by not generating service traffic to a core network of an operator network. It has the advantage of saving.

In the second scenario, the user app requests the service from the edge app, but the edge app handles the service request directly or through communication with the public app. In this case, the edge app can directly send a response to the service to the user app, but if necessary, it can also communicate with the public app to obtain desired information or content. An example of such a service scenario is a real-time game, and the edge app delivers information that can respond directly to the user without communication with the public app, and additional information that the edge app does not have is obtained by communicating with the public app on the Internet. , Use the acquired information to provide services to users.

In the third service scenario, the edge app operates transparently between the user app and the public app, and the user app is considered to receive the service by communicating with the public app without knowing that the edge app is in the middle. An example of such a service scenario is an edge cache that operates transparently, and an edge app can reduce response time and content transmission time for user requests by operating as an edge cache.

Although the above-described service scenarios are described as an example in this specification, it is of course possible to provide various types of services through an edge app in another embodiment of the present invention.

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

3 shows a structure 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, the mobile terminal 300 executing the user app (or user app execution block) 302 is connected to the access network of the operator network through the access node 310, and the access node 310 is the core The public app 352 on the Internet 350 may be accessed through the network 340.

The access node 310 is a communication unit including a base band unit (BBU) 314 in charge of 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 at least one edge app (or edge app execution block) (334,336) is configured to drive the app hosting unit 330. Here, only the packet data convergence protocol (PDCP) processing unit 316 and the general packet radio service (GPRS) tunneling protocol (GPTP) processing unit 320 among the protocol stacks of the BBU 314 are illustrated, and a lower layer of the PDCP processing unit 316 RLC (radio link control), MAC (medium access control) and PHY (physical) are omitted for convenience of explanation.

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

The filtering and forwarding unit (FAFU) 318 located between the PDCP processing unit 316 and the GTP processing unit 320 includes a mobile terminal 300, an edge app 334,336, a public app 352, and an application program The IP packets transmitted or received between the interface (application program interface: API) modules 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 requests and/or service requests transmitted from the user app 302 of the mobile terminal 300 according to a preset rule and processes the corresponding 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 corresponds to 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 app 334,336, the filtering and delivery unit 318 delivers the packet to the mobile terminal 300 through the PDCP 316. In addition, the filtering and delivery unit 318 may deliver a specific packet delivered from the terminal or a specific packet delivered from the Agile app 334,336 to the API module 324 of the network information processing unit 322, and from the API module 324 The delivered response packet is transmitted to the mobile terminal 300 through the PDCP 316, or to the corresponding edge app 334,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 delivery unit 318 may include a destination IP address included in a header of a request packet including a network information request or service request, or a universal resource locator (URL) included in the header of the request packet. Can be used to determine the entity to forward the request packet. In one embodiment, when the edge app 334 is configured on the access node 310, the destination IP address and URL destined for the edge app 334 is set as a filtering rule in the filtering and delivery unit 318. The filtering and forwarding unit 318 forwards the request packet to the edge app 334 instead of forwarding the request packet to the core network 340 when a request packet including a destination IP address and/or URL set by the filtering rule is introduced. do.

The filtering and delivery unit 318 and the edge apps 334 and 336 are connected through an IP-in-IP tunnel, or inter-process communication (IPC). Similarly, packet transmission 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 receiving the request packet for network information, the API module 324 of the network information processing unit 322 identifies the request packet and transmits it to the information retrieval unit 326. The information acquisition unit 326 collects information about the access node 310 from the BBU 314 of the access node 310, an operation and maintenance (OAM) unit, or other functional block, or for an access network. Network information is collected and stored periodically or aperiodically, and desired network information is configured and transmitted to the API module 324 according to the request of 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 (BW) usage, access subscriber channel information, 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 corresponding user app 302 via the corresponding protocol stack of the BBU 314. do. At least one edge app 334, 336 may transmit a request packet for access network information to the API module 324, if necessary, and the API module 324 obtains the requested network information from the information acquisition unit 326 and Edge apps (334,336).

The API module 324 requests the network information between the user app 302 or the edge app 334,336 so that the information of the access node 310 can be retrieved and provided to the mobile terminal 300 or the edge app 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 many 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 configured with multiple virtual machines ( virtual machine), it can run on one or multiple virtual machines. The edge apps 334 and 336 of FIG. 3 represent a case 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 application service requests and access network information requests of the terminal will be described with reference to message flows of FIGS. 4 and 5.

4 illustrates 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.

Referring to FIG. 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 through the session establishment, the core network 340 moves The IP address is assigned 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. As an example, 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.

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 in step 408, the corresponding packet is confirmed. Sent to the edge app.

In one embodiment, filtering may be based on the destination IP address included in the header of the request packet. That is, when a request packet having a predetermined destination IP address is received, the filtering and delivery unit 318 delivers 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, the edge app 334, in response to the service request of the request packet, requests preset available network information to the network information processing unit 322, and network information through the API communication with the network information processing unit 322 To receive.

As an embodiment, communication for requesting network information and delivering the request result between the edge app 334 and the network information processing unit 322 is performed through an interface in the form of a web API or SDK.

In step 412, the edge app 334 provides the network information corresponding to the request packet to the mobile terminal 300 through 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 and obtain information or content necessary for the mobile terminal 300 to provide a desired service to 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, in step 416, the edge app 334 sends the request packet. Forwarding to the filtering and delivery unit 318 of the BBU 312.

In step 418, the filtering and forwarding unit 318 of the BBU 312 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 through the core network 340 and the BBU 312 of the access node.

As an example 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 illustrates 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.

Referring to FIG. 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 is a mobile terminal 300. ) To an 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 access network information may be configured in a format similar to a typical 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. (322).

In one embodiment, the filtering and forwarding unit 318 sends 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 delivery, it is delivered to the network information processing unit 322.

Communication for requesting network information between the user app 302 of the mobile terminal 300 and the network information processing unit 522 and delivering the result of the request may be performed using an open interface. In one embodiment, a web API such as REST may be used. Or use SDK-type interface.

In step 510, the network information processing unit 322 provides 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, a load of an access network and/or an access node, a backhaul bandwidth, and location information in an area to which the access network belongs, at the request of the mobile terminal 300 And one or more IP packets.

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

Referring to FIG. 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 configured by.

The filtering rule 600 is configured by including a 5-tuple of IP, that is, a source IP address, a source port number, a destination IP address, a destination port number, and a protocol type, and a command line by a base station operator. It can be entered directly or set by a system administrator (not shown) of the operator network.

The system manager provides an interface of operator matching function so that an operator can perform operation and maintenance for an access node, and is a management node configured to provide software management, configuration management, performance management, and fault 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 about the corresponding filtering rule, delivers the information to the filtering and delivery unit 318, and the filtering and delivery unit 318 is configured according to the information. The filtering rules are stored in the rule storage unit 602 and tuples with the filtering rules and corresponding edge apps are generated.

The filtering unit 604 filters the 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 the corresponding destination according to the filtering and transmits the packets to the determined destination entity. Examples of packet filtering according to destinations are as follows.

As an example, a downlink (DL) packet received through the GTP processing unit 320 is directly sent to the PDCP processing unit 316 or is 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 network information processing unit 322 through the mapping unit 606. ).

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

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

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. A user equipment (UE) 716 includes at least one user app 718 and connects to an access node 710 using wireless access technology.

The access node 710 includes an eNB block 712 composed of a modified existing base station platform and at least one edge app 714, and the public app of the application server 702 via the 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, etc., and may further include a filtering and delivery unit. The core network 706 may be configured as an evolved packet core (EPC) of an LTE system as an example.

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

The access information to the edge app 714, for example, a destination IP address or destination URL, may be provided to a user through an offline advertisement leaflet, TV, media, etc., and the user may input the user device 716 input means. You can directly enter the destination IP address or destination URL.

As another embodiment, the access node 710 provides the user device 716 with advance information (advertisement, etc.) about a service available through the edge app 714 through a wireless channel, and the user device 716 is a display screen Display a soft button or menu key accessible to the edge app 714 through and trigger a service request for the edge app 714 by detecting a selection (touch) of the soft button or menu key from a user. can do.

As another embodiment, a user or a specific app installed in a user terminal requests and acquires access information for the edge app 704 using a preset IP address or URL, and the user uses the acquired access information to You can request services with the Edge app.

Referring to FIG. 8, the public app 804 is installed in an application server (AS) 802 located on the Internet. The 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 possible to access the public app 804 of 802.

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 delivers 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 service provision, and receive the additional information (820).

Referring to FIG. 9, the public app 904 is installed in an application server (AS) 902 located on the Internet. The user equipment (UE) 916 includes at least one user app 918 and accesses 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 sends a service request for the 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 delivered 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, the edge app 914 sends the request for the content to the public app 904, and the public app 904 through the core network 906 ) Receives and stores (cache) the content, and provides the stored content to the user app 918 (920). When the content is already stored, the edge app 910 may directly provide the pre-stored content to the user app 918 without access to the public app 904.

The embodiments of the present invention operating as described above provide access network information such as base station load, backhaul bandwidth, location information, etc. to a mobile terminal, thereby differentiating application services based on access network information, and different levels of quality of service (Quality of Service: QoS). In addition, embodiments of the present invention can obtain an effect of adding value-added services or facilitating expansion to such services according to the characteristics and technology evolution of a mobile communication network.

On the other hand, 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 should not be limited to the described embodiments, but should be determined not only by the scope of the claims to be described later, but also by the scope and equivalents of the claims.

Claims (2)

A method for 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 using an application program interface (API) associated with the application-based service; And
Transmitting information related to the application-based service to the application client of the mobile terminal using the API;
How to include.
In the edge application server providing an application-based service to a mobile terminal,
Communication department; And
And at least one processor that controls the communication unit to receive information related to the application-based service by using an application program interface (API) related to the application-based service.

Images