KR20220039027A - Edge enable server, and control method thereof - Google Patents

Abstract

The present invention relates to an edge enable server and an operating method of the edge enable server that enable service use through an edge cloud site (MEC site) closest to a network access location in an edge computing (MEC, multi-access edge computing) service environment.

Description

Edge Enable Server and Operation Method of Edge Enable Server {EDGE ENABLE SERVER, AND CONTROL METHOD THEREOF}

The present invention relates to a method for enabling service use through an edge cloud site closest to a network access location in an edge computing (MEC, Multi-Access Edge Computing) service environment.

In the existing mobile communication network, a method in which all traffic generated from a terminal device is delivered to a central SP-GW (SGW, PGW) for reasons of mobility management, billing, etc. has been common.

In such a centralized network structure, services such as telephony (IMS), Internet access, and messaging/video through various portals/OTTs, which are mainly used in terminal devices (eg, smartphones), are not very sensitive to delay and have low capacity. At most, it was small, about several tens of Mbps, so there was no big problem in using it.

However, in recent years, terminal devices connected to mobile communication networks are being diversified into objects such as cars, drones, sensors, VR headsets, cameras, and robots as well as existing smartphones (humans), and services required by each terminal device. requires ultra-low latency (RTT) within a few ms to 10 ms, and has reached a level of demanding large-capacity bandwidth from hundreds of Mbps to several Gbps per stream.

In this regard, as a technology to meet these needs, edge computing (MEC Site) that can accommodate ultra-low latency and large-capacity applications by placing computing for application services on an edge cloud site (MEC Site) that exists close to the terminal device MEC (Multi-Access Edge Computing) technology is attracting attention.

However, in such an edge computing service environment, a plurality of edge cloud sites may exist around the terminal device depending on the location of the terminal device. In this case, depending on the distance between the terminal device and each edge cloud site, each edge cloud site may provide The performance of the available services may vary significantly.

Accordingly, the present invention intends to propose a new method for enabling a terminal device to use a service through an edge cloud site closest to it.

The present invention was created in view of the above circumstances, and the object to be reached in the present invention is through an edge cloud site closest to the network access location in an edge computing (MEC, Multi-Access Edge Computing) service environment. It is to enable the use of the service.

The edge enable server according to an embodiment of the present invention for achieving the above object, according to the induction of access to the edge cloud site closest to the network access location performed for the terminal device accessing the network through the base station, a confirmation unit for confirming the connection of the terminal device to the edge cloud site; and a generator configured to generate a list of edge applications managed by the edge cloud site in order to support edge communication between the terminal device and the edge application according to the connection confirmation of the terminal device.

Specifically, in the connection induction, matching with the first connection information in an Edge Configuration Server (ECS) that confirms the first connection information, which is the connection information allocated to the terminal device when connecting to the network, from the terminal device According to the information, the Edge Enable server located at the edge cloud site closest to the network connection location is identified, and the second connection information, which is the connection information of the Edge Enable server, is transmitted to the terminal device. can

Specifically, the first access information may include access information allocated to the terminal device according to the service area in which the edge gateway device is located by the edge gateway device (MEC-GW) that has confirmed the network connection of the terminal device. can

Specifically, the matching information may include information obtained by matching access information of an edge enable server disposed in each edge cloud site for each service area of the edge gateway device to which the first access information is allocated.

Specifically, the generating unit generates a list such that edge communication with at least one edge application matching an edge enable client (EEC) installed in the terminal device among edge applications managed by the edge cloud site is processed. can do.

Specifically, the generator includes a domain name (FQDN, Fully Qualified Domain Name) for each application identified as a package name (App PKG Name), and third access information required to be converted from the domain name during edge communication. You can create a list.

In order to achieve the above object, an operating method of an edge enable server according to an embodiment of the present invention is provided for inducing access to an edge cloud site closest to a network access location performed for a terminal device accessing a network through a base station. Accordingly, a confirmation step of confirming the connection of the terminal device to the edge cloud site; and a generating step of generating a list of edge applications managed by the edge cloud site in order to support edge communication between the terminal device and the edge application according to the connection confirmation of the terminal device.

Specifically, in the connection induction, matching with the first connection information in an Edge Configuration Server (ECS) that confirms the first connection information, which is the connection information allocated to the terminal device when connecting to the network, from the terminal device According to the information, the Edge Enable server located at the edge cloud site closest to the network connection location is identified, and the second connection information, which is the connection information of the Edge Enable server, is transmitted to the terminal device. can

Specifically, the first access information may include access information allocated to the terminal device according to the service area in which the edge gateway device is located by the edge gateway device (MEC-GW) that has confirmed the network connection of the terminal device. can

Specifically, the matching information may include information obtained by matching access information of an edge enable server disposed in each edge cloud site for each service area of the edge gateway device to which the first access information is allocated.

Specifically, the generating step includes creating a list so that edge communication with at least one edge application matching an edge enable client (EEC) installed in the terminal device among edge applications managed by the edge cloud site is processed. can create

Specifically, the generating step includes a domain name (FQDN, Fully Qualified Domain Name) for each application identified as a package name (App PKG Name), and third access information required to be converted from the domain name during edge communication. You can create a list to do that.

Accordingly, according to the edge enable server and the operating method of the edge enable server of the present invention, the edge cloud site closest to the network connection location of the terminal device in the edge computing (MEC, Multi-Access Edge Computing) service environment (MEC Site) Since the service can be used through the

1 is an exemplary diagram for explaining an edge computing service environment according to an embodiment of the present invention.
2 is a schematic configuration diagram for explaining the configuration of an edge-enabled server according to an embodiment of the present invention;
3 is an exemplary diagram for explaining a signal flow in an edge computing service environment according to an embodiment of the present invention.
4 is a schematic flowchart for explaining a method of operating an Edge Enable Server according to an embodiment of the present invention;

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings.

In one embodiment of the present invention, edge computing (MEC, Multi-Access Edge Computing) technology is dealt with.

In the edge computing service environment, as computing for application services is deployed at the edge cloud site (MEC Site) close to the terminal device, service performance improvement such as ultra-low latency and large-capacity applications can be expected.

However, in such an edge computing service environment, a plurality of edge cloud sites that can be serviced may exist around the terminal device due to the nature of the environment in which the edge cloud is disposed close to the terminal device.

In this case, for the same service to be used by the terminal device, the performance of the service that can be provided by each edge cloud site may vary greatly depending on the distance between the terminal device and each edge cloud site.

Accordingly, in one embodiment of the present invention, it is intended to propose a new method for enabling service use through the edge cloud site closest to the network connection location of the terminal device.

In this regard, FIG. 1 exemplarily shows an edge computing service environment according to an embodiment of the present invention.

1, in the edge computing service environment according to an embodiment of the present invention, an edge gateway device (MEC-) that allocates access information to a terminal device 100 connected to a network through a base station 200 GW: 300), Edge Configuration Server (ECS, Edge Configuration Server: 400) deployed at the central office to interwork with Edge Enable Client (EEC, Edge Enable Client) installed in the terminal device 100 and the edge cloud site The deployed Edge Enable Server (EES, Edge Enable Server: 500) may be included.

In addition, in the edge cloud site according to an embodiment of the present invention, an edge router (MEC Router) for steering traffic for an edge application (ME App) installed on an edge host (MEH) or a public platform (AWS/Azure): 600) may be further disposed.

Here, the edge gateway device 300 refers to a device for allocating access information (IP) related to edge cloud site access to the network-connected terminal device 100, and for example, corresponds to a Packet Gateway (PGW) in a 4G network. In a 5G network, it can be understood as a configuration corresponding to a User Plane Function (UPF).

On the other hand, in the case of an edge enable client (EEC) in the terminal device 100 , it is possible to search for an edge application existing in an edge cloud site and to provision configuration data.

In this regard, the edge setting server 400 disposed in the central office may be understood as a configuration that provides edge data network configuration information to the edge enable client (EEC), and is also disposed in the edge cloud site In the case of the edge enable server 500, which provides information related to edge applications such as activation and related configuration, it can be understood as a configuration that supports the function of exposing the functions of the 3GPP network to the edge applications.

Above, in the edge computing service environment according to an embodiment of the present invention, through the above configuration, it is possible to use the service through the edge cloud site closest to the network connection location of the terminal device 100, which is realized below. The configuration of the edge enable server 500 for this purpose will be described in more detail.

2 schematically shows the configuration of an edge enable server 500 according to an embodiment of the present invention.

As shown in FIG. 2 , the edge enable server 500 according to an embodiment of the present invention includes a confirmation unit 510 for confirming the connection of the terminal device 100 induced to access the edge cloud site, and an edge application. It may have a configuration including a generating unit 520 that generates a list related to .

In addition, the edge enable server 500 according to an embodiment of the present invention may further include a providing unit 530 that provides a list of edge applications in addition to the above-described configuration.

The entire configuration or at least a part of the configuration of the Edge Enable Server 500 may be implemented in the form of a hardware module or a software module, or a combination of a hardware module and a software module may be implemented.

Here, the software module may be understood as, for example, an instruction executed by a processor that processes operations in the Edge Enable Server 500 , and in particular, these instructions are mounted in a separate memory in the Edge Enable Server 500 . may have a given form.

On the other hand, the edge enable server 500 according to an embodiment of the present invention further includes, in addition to the above-described configuration, a communication unit 540 that is an RF module responsible for actual communication with other components in the edge computing service environment. can have

Here, the communication unit 540 includes, but is not limited to, for example, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec (CODEC) chipset, and a memory, etc. All known circuits to be performed may be included.

Above, the edge enable server 500 according to an embodiment of the present invention enables service use through the edge cloud site closest to the network connection location of the terminal device 100 through the above-described configuration, which is realized below. A more detailed description of each configuration in the Edge Enable Server 500 will be continued.

The confirmation unit 510 performs a function of confirming the connection of the terminal device 100 according to the induction of the connection to the edge cloud.

More specifically, the check unit 510 is configured to access the edge cloud site according to the induction of access to the edge cloud site closest to the network access location performed for the terminal device 100 accessing the network through the base station 200 . The connection of the terminal device 100 to the terminal device 100 is checked.

Here, the connection induction to the terminal device 100 is an edge at which the terminal device 100 confirms access information (hereinafter, first access information) allocated from the edge gateway device 300 to the terminal device 100 during network connection. The setting server 400 identifies the edge enable server 500 disposed at the edge cloud site closest to the network connection location according to the matching information with the first access information, and the identified edge enable server 500 This may be performed in a manner of transmitting access information (hereinafter, second access information) to the terminal device 100 .

In this regard, the terminal device 100 is an edge disposed at the edge cloud site closest to the network access location based on the first access information allocated from the edge gateway device 300 according to the network access through the base station 200 . By acquiring the second access information of the enable server 500 , it is possible to connect to the edge enable server 500 to which the second access information is given.

To this end, the terminal device 100 transmits the first connection information allocated from the edge gateway device 300 in the provisioning process with the edge setting server 400 according to the network connection through the base station 200 to the edge setting server ( 400), and accordingly, the second connection information of the edge enable server 500 disposed in the edge cloud site closest to the edge gateway device 300 identified from the first connection information is transferred to the edge setting server 400 can be received from

In this regard, in the edge setting server 400, for example, a pool for the first access information that can be allocated from the edge gateway device 300 divided by station or service area, and edge information for each edge cloud site. Manages matching information that matches the second access information of the Able server 500, and through this, the corresponding edge gateway device 300 and You can check the edge enable server 500 deployed at the closest edge cloud site.

To summarize, in one embodiment of the present invention, for example, as shown in FIG. 3 , the edge gateway device 300 transmits the first connection information to the terminal device according to the network connection through the base station 200 of the terminal device 100 . (100) is allocated (①), and accordingly, the terminal device 100 transmits the first connection information to the edge setting server 400 through provisioning with the edge setting server 400 disposed in the central office. Accordingly, the second connection information of the edge enable server 500 disposed in the edge cloud site closest to the edge gateway device 300 is received from the edge setting server 400 (②, ③), and through this, the edge The enable server 500 can check the terminal device 100 connected to the edge enable server 500 through the second connection information according to the above-described connection induction (③).

The generator 520 performs a function of generating a list of edge applications.

More specifically, in order to support edge communication between the terminal device and the edge application according to the connection confirmation of the terminal device 100 , the generator 520 generates a list of edge applications managed by the edge cloud site.

At this time, the generation unit 520 is an edge that matches the package name (App PKG Name) and domain name (FQDN, Fully Qualified Domain Name) for each edge application managed by the edge cloud site and each domain name (FQDN). A list may be created to include application connection information (hereinafter, third connection information).

For reference, the generation of such an edge application list may be performed in a terminal registration process based on a REGISTER message performed for the terminal device 100 connected to the edge enable server 500 .

The providing unit 530 performs a function of providing a list of edge applications.

More specifically, when a list of edge applications managed by the cloud site is generated, the providing unit 530 provides the generated list to the terminal device 100 to provide edge applications installed in the terminal device 100 among edge applications on the list. Enables edge communication with at least one edge application matching the client to be processed.

In this regard, when a list of edge applications existing in the edge crowd site is obtained, the terminal device 100 processes edge communication with at least one edge application existing on the corresponding list.

At this time, the terminal device 100 checks whether an edge application matching the edge application client installed in the terminal device 100 exists on the list, and if at least one matched edge application exists as a result of the check, the corresponding edge It can handle edge communication with the application.

In particular, before processing the edge communication as described above, the terminal device 100 checks the domain name (FQDN, Fully Qualified Domain Name) of the edge application during edge communication with the edge application identified by the package name (App PKG Name). In this case, it is possible to enable edge communication with the edge application existing in the edge cloud site through a method of converting the verified domain name (FQDN) into the third access information confirmed from the list.

On the other hand, in the process of checking whether the edge application matching the edge application client installed in the terminal device 100 exists on the list, the terminal device 100 determines that the matched edge application does not exist on the list. In this case, the terminal registration process based on the REGISTER message in the edge enable server 500 may be interrupted. In this case, the edge application client is newly installed in the terminal device 100, or the terminal registration process may be restarted at every setting period. there is.

To summarize, in an embodiment of the present invention, as shown in FIG. 3 exemplified above, the edge enable server 500 displays a list of edge applications managed by its edge cloud site on the terminal device 100 . When provided as (④), the terminal device 100 has at least one edge application matching a pre-installed edge application client on the edge application list existing in the edge cloud site, and among them, When edge communication is required, by converting the domain name (FQDN, Fully Qualified Domain Name) of the corresponding edge application into third access information, edge communication with the edge application existing in the edge cloud site can be performed (⑤ ).

As described above, according to the configuration of the edge enable server 500 according to an embodiment of the present invention, the edge gateway device 300 and By connecting to the edge enable server 500 disposed at the nearest edge cloud site and performing edge communication with the edge application managed by the edge enable server 500, the network of the terminal device 100 As it becomes possible to use the service at the edge cloud site closest to the access location, it is possible to expect optimal service performance according to the access in a short distance.

Hereinafter, an operation method of the Edge Enable Server 500 according to an embodiment of the present invention will be described with reference to FIG. 4 .

First, the check unit 510 is a terminal for the edge cloud site according to the induction of access to the edge cloud site closest to the network access location performed for the terminal device 100 accessing the network through the base station 200 . The connection of the device 100 is checked (S10).

Here, the connection induction to the terminal device 100 is an edge at which the terminal device 100 confirms access information (hereinafter, first access information) allocated from the edge gateway device 300 to the terminal device 100 during network connection. The setting server 400 identifies the edge enable server 500 disposed at the edge cloud site closest to the network connection location according to the matching information with the first access information, and the identified edge enable server 500 This may be performed in a manner of transmitting access information (hereinafter, second access information) to the terminal device 100 .

In this regard, the terminal device 100 is an edge disposed at the edge cloud site closest to the network access location based on the first access information allocated from the edge gateway device 300 according to the network access through the base station 200 . By acquiring the second access information of the enable server 500 , it is possible to connect to the edge enable server 500 to which the second access information is given.

To this end, the terminal device 100 transmits the first connection information allocated from the edge gateway device 300 in the provisioning process with the edge setting server 400 according to the network connection through the base station 200 to the edge setting server ( 400), and accordingly, the second connection information of the edge enable server 500 disposed in the edge cloud site closest to the edge gateway device 300 identified from the first connection information is transferred to the edge setting server 400 can be received from

In this regard, in the edge setting server 400, for example, a pool for the first access information that can be allocated from the edge gateway device 300 divided by station or service area, and edge information for each edge cloud site. Manages matching information that matches the second access information of the Able server 500, and through this, the corresponding edge gateway device 300 and You can check the edge enable server 500 deployed at the closest edge cloud site.

In summary, in an embodiment of the present invention, the edge gateway device 300 allocates the first connection information to the terminal device 100 according to the network connection through the base station 200 of the terminal device 100, and accordingly The terminal device 100 transmits the first connection information to the edge setting server 400 through provisioning with the edge setting server 400 disposed at the central office, and the edge cloud closest to the edge gateway device 300 . The second connection information of the edge enable server 500 disposed on the site is received from the edge setting server 400, and through this, the edge enable server 500 receives the second connection information according to the above-mentioned connection induction. Through this, it is possible to check the terminal device 100 connected to the edge enable server 500 .

Next, the generator 520 generates a list of edge applications managed by the edge cloud site to support edge communication between the terminal device and the edge application according to the connection confirmation of the terminal device 100 ( S20 ).

At this time, the generation unit 520 is an edge that matches the package name (App PKG Name) and domain name (FQDN, Fully Qualified Domain Name) for each edge application managed by the edge cloud site and each domain name (FQDN). A list may be created to include application connection information (hereinafter, third connection information).

For reference, the generation of such an edge application list may be performed in a terminal registration process based on a REGISTER message performed for the terminal device 100 connected to the edge enable server 500 .

Thereafter, when a list of edge applications managed by the cloud site is generated, the providing unit 530 provides the generated list to the terminal device 100, and among edge applications on the list, the edge application client installed in the terminal device 100 and Edge communication with at least one matching edge application can be processed (S30).

In this regard, when a list of edge applications existing in the edge crowd site is obtained, the terminal device 100 processes edge communication with at least one edge application existing on the corresponding list.

At this time, the terminal device 100 checks whether an edge application matching the edge application client installed in the terminal device 100 exists on the list, and if at least one matched edge application exists as a result of the check, the corresponding edge It can handle edge communication with the application.

In particular, before processing the edge communication as described above, the terminal device 100 checks the domain name (FQDN, Fully Qualified Domain Name) of the edge application during edge communication with the edge application identified by the package name (App PKG Name). In this case, it is possible to enable edge communication with the edge application existing in the edge cloud site through a method of converting the verified domain name (FQDN) into the third access information confirmed from the list.

On the other hand, in the process of checking whether the edge application matching the edge application client installed in the terminal device 100 exists on the list, the terminal device 100 determines that the matched edge application does not exist on the list. In this case, the terminal registration process based on the REGISTER message in the edge enable server 500 may be interrupted. In this case, the edge application client is newly installed in the terminal device 100, or the terminal registration process may be restarted at every setting period. there is.

To summarize, in an embodiment of the present invention, as shown in FIG. 3 exemplified above, the edge enable server 500 displays a list of edge applications managed by its edge cloud site on the terminal device 100 . In this case, the terminal device 100 has at least one edge application matching a pre-installed edge application client on the edge application list existing in the edge cloud site, and edge communication with a specific edge application among them exists. If required, by converting the domain name (FQDN, Fully Qualified Domain Name) of the corresponding edge application into the third access information, edge communication with the edge application existing in the edge cloud site can be performed.

As described above, according to the operation method of the edge enable server 500 according to an embodiment of the present invention, the edge gateway device 300 is a network connection location in connection with the edge setting server 400 disposed in the central office. By connecting to the edge enable server 500 disposed at the edge cloud site closest to As it becomes possible to use the service at the edge cloud site closest to the network connection location, it can be expected to guarantee optimal service performance according to access in a short distance.

On the other hand, the operating method of the edge enable server 500 according to an embodiment of the present invention may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floppy disks. - includes magneto-optical media, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

Although the present invention has been described in detail with reference to preferred embodiments so far, the present invention is not limited to the above-described embodiments, and without departing from the gist of the present invention as claimed in the following claims, the technical field to which the present invention pertains It will be said that the technical spirit of the present invention extends to a range where various modifications or modifications can be made by anyone with ordinary knowledge in the present invention.

According to the edge enable server and the operating method of the edge enable server according to the present invention, in an edge computing (MEC, Multi-Access Edge Computing) service environment, service use through the edge cloud site closest to the network connection location (MEC Site) In terms of making it possible, as it goes beyond the limits of existing technologies, the possibility of marketing or sales of the applied device, not just the use of the related technology, is sufficient, and industrial applicability is high because it can be clearly implemented in reality. there is an invention

100: terminal device (edge enable client)
200: base station device
300: edge gateway device
400: Edge setting server
500: Edge enable server
510: confirmation unit 520: generation unit
530: provider
600: edge router

Claims (12)

a confirmation unit for confirming the connection of the terminal device to the edge cloud site according to the induction of access to the edge cloud site closest to the network access location performed for the terminal device accessing the network through the base station; and
Edge enable server comprising a generator for generating a list of edge applications managed by the edge cloud site in order to support edge communication between the terminal device and the edge application according to the connection confirmation of the terminal device. The method of claim 1,
The connection induction is
When connecting to the network, the network access location and the first access information, which is access information allocated to the terminal device, are matched according to matching information with the first access information in an Edge Configuration Server (ECS) that has been checked from the terminal device. Edge enable server, characterized in that it is performed by identifying the edge enable server disposed at the closest edge cloud site, and transmitting the second connection information, which is access information of the edge enable server, to the terminal device . 3. The method of claim 2,
The first connection information is
The edge enable server, characterized in that it includes access information allocated to the terminal device according to the service area in which the edge gateway device is located in the edge gateway device (MEC-GW) that has confirmed the network connection of the terminal device. 4. The method of claim 3,
The matching information is
Edge enable server, characterized in that it includes information that matches the connection information of the edge enable server arranged in each edge cloud site for each service area of the edge gateway device to which the first connection information is allocated. The method of claim 1,
The generating unit,
Edge, characterized in that the list is generated so that edge communication with at least one edge application matching an edge application client (EEC, Edge Enable Client) installed in the terminal device among edge applications managed by the edge cloud site is processed Able Server. The method of claim 1,
The generating unit,
It is characterized in that the list is generated to include the domain name (FQDN, Fully Qualified Domain Name) for each application identified by the package name (App PKG Name), and third access information required to be converted from the domain name during edge communication. Edge Enable Server. a confirmation step of confirming the connection of the terminal device to the edge cloud site according to the induction of access to the edge cloud site closest to the network access location performed for the terminal device accessing the network through the base station; and
Edge enable server comprising a generating step of generating a list of edge applications managed by the edge cloud site in order to support edge communication between the terminal device and the edge application according to the connection confirmation of the terminal device how it works. 8. The method of claim 7,
The connection induction is,
When connecting to the network, the network access location and the first access information, which is the access information allocated to the terminal device, are matched according to matching information with the first access information in an Edge Configuration Server (ECS) that has been checked from the terminal device. Edge enable server, characterized in that by identifying the edge enable server disposed at the nearest edge cloud site, and transmitting the second connection information, which is the connection information of the edge enable server, to the terminal device how it works. 9. The method of claim 8,
The first connection information is
Edge enable server operation, characterized in that it includes access information allocated to the terminal device according to the service area in which the edge gateway device is located in the edge gateway device (MEC-GW) that has confirmed the network connection of the terminal device method. 10. The method of claim 9,
The matching information is
The method of operating an edge enable server, characterized in that it includes information obtained by matching the access information of the edge enable server disposed in each edge cloud site for each service area of the edge gateway device to which the first access information is allocated. 8. The method of claim 7,
The creation step is
Edge, characterized in that the list is generated so that edge communication with at least one edge application matching an edge application client (EEC, Edge Enable Client) installed in the terminal device among edge applications managed by the edge cloud site is processed Able Server. 8. The method of claim 7,
The creation step is
It is characterized in that the list is generated to include the domain name (FQDN, Fully Qualified Domain Name) for each application identified by the package name (App PKG Name), and third access information required to be converted from the domain name during edge communication. Edge Enable Server.

Images