DNS query control device, DNS query control method and program

Abstract

To provide a DNS query control apparatus configured to achieve fine control which a user or an application does not grasp, by rewriting a DNS query generated by a terminal device in a MEC system or an intermediate node.SOLUTION: A DNS query control apparatus includes: a DNS query acquisition unit which acquires a first DNS message including a first DNS query output from a terminal device; an MEC information addition unit which adds, based on the first DNS message acquired by the DNS query acquisition unit, MEC information to the first DNS query to generate a second DNS message; and a DNS query output unit which outputs the second DNS message generated by the MEC information addition unit.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a DNS query control device, a DNS query control method, and a program. [Background technology]

[0002] MEC (Multi-access Edge Computing) technology is being developed. Additionally, DNS (Domain Name System) technology is being developed.

[0003] As shown in Non-Patent Document 1, MEC is expected to provide low-latency application (App) services to users, and therefore, in principle, devices are expected to be connected to geographically or topologically nearby edge hosts (see Non-Patent Document 1). Here, it is assumed that the application does not have knowledge of the topology of the access network or MEC system, so the DNS query is expected to resolve the appropriate IP (Internet Protocol) address for each individual user from the FQDN (Fully Qualified Domain Name) common to all users. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] ETSI White Paper NO.39, “Enhanced DNS Support towards Distributed MEC Environment”, September 2020, [Retrieved August 25, 2022], Internet <URL:https: / / www.etsi.org / images / files / ETSIWhitePapers / etsi-wp39-Enhanced-DNS-Support-towards-Distributed-MEC-Environment.pdf> [Non-patent document 2] Internet Engineering Task Force, Request for Comments: 6891 “Extension Mechanisms for DNS (EDNS(0))”, [Retrieved August 25, 2022], Internet<URL:https: / / datatracker.ietf.org / doc / html / rfc6891> Summary of the Invention [Problem to be solved by the invention]

[0005] However, it is expected that there will be frequent cases where edge hosts do not have sufficient computing and network resources, making it difficult to achieve this with the control granularity of general DNS. If a system were to be set up to resolve DNS records for each user, it would be necessary to prepare records that would resolve the appropriate IP address from the combination of FQDN and user ID (e.g., ueid.example.com), and the number of records would need to be multiplied by the number of users. Therefore, a simple system that requires the maintenance of a huge number of records would not be able to realize a system that can accommodate a large number of users.

[0006] Here, the technology of Non-Patent Document 1 makes it possible to realize control at a predetermined granularity by using EDNS0, an extended protocol of DNS. The specifications of EDNS0 are defined in Non-Patent Document 2 (see Non-Patent Document 2). However, a specific method of use is not shown in Non-Patent Document 1. For example, metrics that should be used as a control standard may include not only information that can be observed on the UE side (e.g., UE identifier, location, response time, etc.), but also information that can be observed on the MEC platform side (e.g., resource usage status and load status of the serving MEC host and surrounding MEC hosts, etc.).

[0007] FIG. 5 is a diagram illustrating an example of a communication system including an MEC host. The communication system shown in FIG. 5 includes a device 611 which is user equipment (UE), an MEC host 631 (MEC host A), and an MEC host 632 (MEC host B). When the device 611 is communicating with the MEC host 631 and the processing load of the MEC host 631 becomes heavy, the MEC host is switched so that the device 611 communicates with another MEC host 632 instead of the MEC host 631. Thus, in the example of Figure 5, an operator can dynamically select a MEC host based on operational policies other than location.

[0008] FIG. 6 is a diagram illustrating another example of a communication system including an MEC host. The communication system shown in FIG. 6 includes a device 711 (Device A) and a device 712 (Device B) 712 which are UEs, an MEC host 731 (MEC host A), an MEC host 732 (MEC host B), and a DNS 751. The device 711 sends a DNS query to the DNS 751, and when a response is received indicating that communication with the MEC host 731 will be performed, the device 711 communicates with the MEC host 731. Furthermore, the device 712 transmits a DNS query to the DNS 751, and when notified in response that communication with the MEC host 732 will be performed, the device 712 communicates with the MEC host 732. Thus, in the example of Figure 6, different devices may need to connect to different MEC hosts depending on the location of each device.

[0009] As described above, Non-Patent Document 1 assumes that detailed control can be achieved by using the EDNS0 extension field, but because DNS queries are generated by the client, the parameters stored in the extension field are limited to those known by the client UE. This makes it impossible to distribute the load on MEC hosts or improve the efficiency of facility utilization as desired by platform operators.

[0010] The present disclosure has been made in consideration of these circumstances, and aims to provide a DNS query control device, a DNS query control method, and a program that can achieve detailed control without the user or application being aware of it by rewriting DNS queries created by terminal devices in an MEC system or intermediate node. [Means for solving the problem]

[0011] As one configuration example, the DNS server includes: a DNS query acquisition unit that acquires a first DNS message including a first DNS query output from a terminal device; an MEC information addition unit that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit; and a DNS query output unit that outputs the second DNS message generated by the MEC information addition unit. The MEC information adding unit determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring unit, the information about the terminal device being information representing computing resource requirements of an application, and the MEC information being information representing a processing load of an MEC host. It is a DNS query control device. As one configuration example, the DNS query control device includes: a DNS query acquisition unit that acquires a first DNS message including a first DNS query output from a terminal device; an MEC information addition unit that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit; and a DNS query output unit that outputs the second DNS message generated by the MEC information addition unit, wherein the MEC information addition unit determines the MEC information to add to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquisition unit, the information about the terminal device being information representing the delay requirements of an application, and the MEC information being information representing a round trip time from a UPF.

[0012] As one configuration example, a DNS query acquisition unit acquires a first DNS message including a first DNS query output from a terminal device, an MEC information addition unit generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit, and a DNS query output unit outputs the second DNS message generated by the MEC information addition unit. the MEC information adding unit determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring unit, the information about the terminal device being information representing a computing resource requirement of an application, and the MEC information being information representing a processing load of an MEC host. This is a method for controlling DNS queries. As one configuration example, in a DNS query control method, a DNS query acquisition unit acquires a first DNS message including a first DNS query output from a terminal device, an MEC information addition unit generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit, a DNS query output unit outputs the second DNS message generated by the MEC information addition unit, the MEC information addition unit determines the MEC information to add to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquisition unit, the information about the terminal device is information representing the delay requirements of an application, and the MEC information is information representing a round trip time from a UPF.

[0013] As one configuration example, a computer is configured to realize a DNS query acquisition function that acquires a first DNS message including a first DNS query output from a terminal device, an MEC information addition function that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition function, and a DNS query output function that outputs the second DNS message generated by the MEC information addition function. A program, wherein the MEC information addition function determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquisition function, the information about the terminal device being information representing computing resource requirements of an application, and the MEC information being information representing a processing load of an MEC host. It is a program. As one configuration example, the program is for causing a computer to realize a DNS query acquisition function that acquires a first DNS message including a first DNS query output from a terminal device, an MEC information addition function that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition function, and a DNS query output function that outputs the second DNS message generated by the MEC information addition function, wherein the MEC information addition function determines the MEC information to add to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquisition function, the information about the terminal device is information that represents the delay requirements of an application, and the MEC information is information that represents the round trip time from a UPF. [Effects of the Invention]

[0014] According to the DNS query control device, DNS query control method, and program of the present disclosure, DNS queries created by terminal devices can be rewritten in an MEC system or an intermediate node, enabling detailed control to be achieved without the user or application being aware of it. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a diagram showing a schematic configuration of a communication system according to a first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the functional block configuration of the DNS query control device according to the first embodiment. [Figure 3] FIG. 10 is a diagram showing a schematic configuration of a communication system according to a second embodiment. [Figure 4] FIG. 11 is a diagram illustrating an example of the functional block configuration of a DNS query control device of a granting node according to the second embodiment. [Figure 5] FIG. 1 illustrates an example of a communication system including an MEC host. [Figure 6] FIG. 10 is a diagram illustrating another example of a communication system including an MEC host. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0017] (First embodiment) [Communication Systems] FIG. 1 is a diagram showing a schematic configuration of a communication system 1 according to the first embodiment. The communication system 1 includes a UE 11, a base station device 21, a base station device 22, a UPF (User Plane Function) 31, a UPF 32, an MEC system 41, and a DNS 42 (DNS server). The MEC system 41 includes a DNS query control device 51 .

[0018] In the example of FIG. 1, base station device 21 and base station device 22 are connected to UPF 31, and UPF 31 is connected to UPF 32. The UPF 31 routes communications to and from the MEC system 41 . The UPF 32 routes communication with the DNS 42 . The UE 11 communicates with the base station device 21 wirelessly.

[0019] Here, in the example of FIG. 1, for the sake of convenience of explanation, a simple configuration example is shown as the configuration of the communication system 1. The configuration of the communication system 1 is not limited to the example in FIG. 1, and for example, the communication system 1 may include other UEs, other base station devices, other UPFs, other servers, and the like.

[0020] An outline of the operations performed in the communication system 1 will now be described. The UE 11 outputs (transmits) a DNS message F1 addressed to the DNS 42. The DNS message F1 is input to the MEC system 41 via the base station device 21 and the UPF 31 (communication T1).

[0021] Here, the DNS message F1 includes a DNS query and UE information. The UE information is information related to the UE 11, and may be, for example, reception information (GPS information) of a GPS (Global Positioning System) of the UE 11. The GPS information includes, for example, information on latitude and longitude that indicates the position of the UE 11.

[0022] In the MEC system 41, the DNS query control device 51 receives the DNS message F1 and determines the MEC information to be added based on the received DNS message F1. Then, the DNS query control device 51 generates a DNS message F2 by adding (adding) the MEC information to the DNS message F1, and returns the DNS message F2 to the original communication flow. As a result, the DNS message F2 passes through UPF 31 and UPF 32 and is input to the DNS 42 (communication T2). Here, the DNS message F2 includes a DNS query, UE information, and MEC information.

[0023] Note that this embodiment complies with specifications in which the MEC host and the DNS 42 are not integrated. For example, according to GS ETSI MEC 003, DNS servers are outside the scope of the MEC system. For this reason, this embodiment does not address a configuration in which the DNS server itself is part of the MEC system and resolves destinations.

[0024] The MEC system 41 includes, for example, one or more MEC hosts. Each MEC host is, for example, configured from a physical server. When the MEC system 41 includes multiple MEC hosts, for example, the multiple MEC hosts may be located remotely from one another. The MEC system 41 may include an orchestrator. The orchestrator manages, for example, information about each MEC host. The information may be, for example, information about the location of each MEC host or load information about each MEC host.

[0025] In this embodiment, the MEC system 41 is provided with a DNS query control device 51 having the function of an application that rewrites DNS queries, and the DNS query control device 51 can assign MEC information to each DNS query. Here, the DNS query control device 51 may be, for example, one MEC host.

[0026] [DNS query control device] FIG. 2 is a diagram showing an example of the functional block configuration of the DNS query control device 51 according to the first embodiment. The DNS query control device 51 includes a DNS query acquisition unit 111, an MEC information addition unit 112, and a DNS query output unit 113.

[0027] The DNS query acquisition unit 111 acquires information included in the DNS message F1 transmitted from the UE 11. In this embodiment, the information includes a DNS query and UE information. The MEC information adding unit 112 generates a DNS message F2 by adding MEC information to the DNS query (DNS message F1) based on the information acquired by the DNS query acquiring unit 111. In this case, the MEC information adding unit 112 may determine the MEC information based on the information acquired by the DNS query acquiring unit 111. The DNS query output unit 113 returns the DNS message F2 generated by the MEC information adding unit 112 to the original communication flow (in the example of FIG. 1, it outputs it to the UPF 31).

[0028] In this embodiment, the DNS query (DNS message F1) sent from UE 11 to DNS 42 is first acquired by the DNS query control device 51, and the DNS message F2, which is the DNS query with information related to the MEC system (MEC information) added to it, is returned to the original path. When the DNS message F2 is transmitted to the original destination DNS 42, the DNS query output unit 113 may output the DNS message F2 to a communication flow other than the original communication flow.

[0029] As an example, the DNS query control device 51 can add information (MEC information) to the DNS query for querying the DNS record of the MEC host corresponding to the geography based on geographical information such as GPS information contained in the UE information. As another example, the DNS query control device 51 can directly or indirectly refer to network information such as the load status of each MEC host or the network topology, and assign parameters (MEC information) that take these into consideration.

[0030] Here, in this embodiment, the DNS query output from the UE 11 is configured to be steered so as to pass through the MEC system 41 (DNS query control device 51). In this embodiment, the DNS query control device 51 functions as an MEC host and acts as a DNS server to receive DNS queries.

[0031] [Case Study] The following cases are assumed as examples of UE information or MEC information that may be added to a DNS query:

[0032] In the first example, region selection is achieved by assigning GPS information as UE information and region information as MEC information. That is, UE 11 includes GPS information in the UE information. Furthermore, based on the GPS information included in the UE information, DNS query control device 51 includes information on regions close to the location of the GPS information in the MEC information, thereby enabling selection of an MEC host close to the location of the GPS information (that is, an MEC host close to the location of UE 11). In this case, for example, the MEC system 41 (DNS query control device 51 or other components) stores information for associating location information (GPS information) with region information, and the DNS query control device 51 uses (refers to) that information.

[0033] In the second example, information representing the computing resource requirements of the application is assigned as the UE information, and information representing the processing load of the MEC host is assigned as the MEC information. That is, the UE 11 includes information representing the computing resource requirements of the application in the UE information. Furthermore, the DNS query control device 51 includes information representing the processing load of the MEC host in the MEC information as appropriate information based on the information representing the computing resource requirements of the application included in the UE information, thereby enabling selection of an MEC host capable of executing the expected application processing. In this case, for example, the MEC system 41 (DNS query control device 51 or other components) stores information indicating the processing load of each MEC host, and the DNS query control device 51 uses (references) this information.

[0034] In the third example, information representing the delay requirements of an application is assigned as UE information, and information representing a round trip time (RTT) from the UPF is assigned as MEC information. That is, the UE 11 includes information representing the delay requirements of the application in the UE information. Furthermore, the DNS query control device 51 includes information representing the round trip time from the UPF for the MEC host in the MEC information as information appropriate for the information representing the delay requirements of the application included in the UE information, thereby enabling selection of an MEC host that satisfies the delay requirements. In this case, for example, the MEC system 41 (DNS query control device 51 or other components) stores information indicating the communication delay time (RTT) from each UPF to each MEC host, and the DNS query control device 51 uses (refers to) that information.

[0035] [Regarding the first embodiment] As described above, in the communication system 1 according to this embodiment, the DNS query control device 51 rewrites the DNS query created by the terminal device (in this embodiment, UE 11) in the MEC system 41, thereby achieving detailed control without the user or application being aware of it.

[0036] In the communication system 1 according to the present embodiment, for example, it is possible to significantly reduce the number of DNS records required when performing DNS resolution using a single FQDN, while responding with a different IP address depending on attributes of the UE 11, such as the identification information (UE ID) of the UE 11. At the same time, in the communication system 1 according to the present embodiment, it is possible to respond with a different IP address depending on information of the MEC system 41, such as the computing load of the MEC host. Here, the suppression effect of the DNS record is expressed by (number of clusters of the device / total number of UEs).

[0037] If one were to try to solve this problem directly, it would be technically possible for the UE to receive information from the MEC system and for the UE to add the MEC information to the DNS query in advance. However, it is conceivable that there may be cases where it is not permitted to disclose information relating to the topology of the MEC host within the MEC system or information relating to its performance. Therefore, in the communication system 1 of this embodiment, the problem is solved by preventing the MEC information from being notified to the UE 11.

[0038] In the communication system 1 according to this embodiment, the DNS query created by the UE 11 is rewritten by the DNS query control device 51 of the MEC system 41, thereby realizing detailed control without the user or application being aware of it. Note that rewriting DNS queries also includes adding (adding) information.

[0039] In the communication system 1 of this embodiment, for example, a DNS query control device 51 for handover of an MEC host can be provided, which makes it possible to flexibly switch the MEC host to be connected depending on the movement status (handover status) of the UE 11 or the resource usage status of the edge host, even when the MEC system 41 is deployed nationwide.

[0040] In the communication system 1 according to this embodiment, for example, when multiple users connect simultaneously in a distributed MEC environment, the DNS query control device 51 can process DNS queries to switch the appropriate connection destination (e.g., IP address) for each user depending on the user's movement or changes in resource usage. The communication system 1 according to this embodiment can solve the implementation problem of DNS resolution in a configuration in which, for example, each MEC host has a different IP address.

[0041] In the communication system 1 according to this embodiment, it is possible to use an extension function of DNS such as EDNS0 (Extension Mechanisms for DNS version 0).

[0042] <Configuration example according to the first embodiment> As an example configuration, the DNS query control device 51 includes a DNS query acquisition unit 111 that acquires a first DNS message (DNS message F1 in the example of FIG. 1) including a first DNS query output from a terminal device (UE 11 in the example of FIG. 1), an MEC information addition unit 112 that adds MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit 111 to generate a second DNS message (DNS message F2 in the example of FIG. 1), and a DNS query output unit 113 that outputs the second DNS message generated by the MEC information addition unit 112.

[0043] Here, the first DNS message may include, for example, information other than the first DNS query, or may be the same as the first DNS query. Furthermore, the second DNS message may include, for example, information other than (the first DNS query and the MEC information), or may be the same as (the first DNS query and the MEC information).

[0044] As one configuration example, in the DNS query control device 51, the MEC information adding unit 112 determines the MEC information to add to the first DNS query based on information about the terminal device (in the example of Figure 1, UE information) included in the first DNS message acquired by the DNS query acquiring unit 111.

[0045] In one configuration example, the DNS query control device 51 is provided in the MEC system 241.

[0046] Here, it is also possible to provide a method for the processing performed in the DNS query control device 51. As an example configuration, in a DNS query control method, a DNS query acquisition unit 111 acquires a first DNS message including a first DNS query output from a terminal device, a MEC information addition unit 112 adds MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit 111 to generate a second DNS message, and a DNS query output unit 113 outputs the second DNS message generated by the MEC information addition unit 112.

[0047] It is also possible to provide a program for controlling DNS queries. As one configuration example, the program is a program for causing a computer to realize a DNS query acquisition function that acquires a first DNS message including a first DNS query output from a terminal device, an MEC information addition function that adds MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition function to generate a second DNS message, and a DNS query output function that outputs the second DNS message generated by the MEC information addition function.

[0048] (Second embodiment) [Communication Systems] FIG. 3 is a diagram showing a schematic configuration of a communication system 201 according to the second embodiment. The communication system 201 includes a UE 211, a base station device 221, a base station device 222, a UPF 231, a UPF 232, an MEC system 241, an assigning node 242, and a DNS 243 (DNS server).

[0049] The granting node 242 may be, for example, a switch or a general-purpose server. The granting node 242 includes a DNS query control device 251 . The granting node 242 communicates with the MEC system 241. The MEC system 241 notifies the granting node 242 of information related to MEC information. The information may be the MEC information itself. In this embodiment, for the sake of convenience, a configuration example is shown in which the granting node 242 is equipped with the DNS query control device 251, but the granting node 242 and the DNS query control device 251 may be the same, that is, the granting node 242 itself may be the DNS query control device 251.

[0050] In the example of FIG. 3, the base station device 221 and the base station device 222 are connected to the UPF 231, and the UPF 231 and the UPF 232 are connected to each other. The UPF 231 routes communications to and from the MEC system 241 . The UPF 232 routes communication with the DNS 243. In this embodiment, a granting node 242 is provided between the UPF 232 and the DNS 243. The UE 211 communicates with the base station device 221 wirelessly.

[0051] Here, in the example of FIG. 3, for the sake of convenience of explanation, a simple configuration example is shown as the configuration of the communication system 201. The configuration of the communication system 201 is not limited to the example of FIG. 3, and the communication system 201 may include, for example, other UEs, other base station devices, other UPFs, other servers, and the like.

[0052] An outline of the operations performed in the communication system 201 will now be described. The UE 211 outputs (transmits) a DNS message F11 addressed to the DNS 243. The DNS message F11 is input to the granting node 242 located between the UPF 232 and the DNS 243 on the way to the DNS 243 via the base station device 221, the UPF 231, and the UPF 232 (communication T11).

[0053] Here, the DNS message F11 includes a DNS query and UE information. The UE information is information relating to the UE 211, and may be, for example, GPS reception information (GPS information) of the UE 11. The GPS information includes, for example, latitude and longitude information indicating the position of the UE 211.

[0054] In the providing node 242, the DNS query control device 251 receives the DNS message F11 and determines the MEC information to be provided based on the received DNS message F11. Then, the DNS query control device 251 generates a DNS message F12 by adding (adding) the MEC information to the DNS message F11, and returns the DNS message F12 to the original communication flow. As a result, the DNS message F12 is input to the DNS 243 (communication T12). Here, the DNS message F12 includes a DNS query, UE information, and MEC information.

[0055] In this embodiment, the MEC system 241 notifies the granting node 242 of information related to the MEC information at any timing. The timing may be, for example, regular timing or other timing. Such notification may be made to the granting node 242 by the MEC system 241 on its own initiative, or may be made when the granting node 242 accesses the MEC system 241, for example.

[0056] Note that this embodiment supports specifications in which the MEC host and the DNS 243 are not integrated. For example, according to GS ETSI MEC 003, the DNS server is outside the scope of the MEC system. Therefore, this embodiment does not target a configuration in which the DNS server itself is part of the MEC system and resolves destinations.

[0057] The MEC system 241 includes, for example, one or more MEC hosts. Each MEC host is, for example, a physical server. When the MEC system 241 includes multiple MEC hosts, for example, the multiple MEC hosts may be located remotely from one another. The MEC system 241 may include an orchestrator. The orchestrator manages, for example, information about each MEC host. The information may be, for example, information about the location of each MEC host or load information about each MEC host.

[0058] In this embodiment, the assigning node 242 is provided with a DNS query control device 251 having the function of an application that rewrites DNS queries, and the DNS query control device 251 can assign MEC information to each DNS query. Here, the DNS query control device 251 may be, for example, one MEC host.

[0059] [DNS query control device] FIG. 4 is a diagram showing an example of the functional block configuration of a DNS query control device 251 according to the second embodiment. The DNS query control device 251 includes a DNS query acquisition unit 311 , an MEC information addition unit 312 , and a DNS query output unit 313 .

[0060] The DNS query acquisition unit 311 acquires information included in the DNS message F11 transmitted from the UE 211. In this embodiment, the information includes a DNS query and UE information. The MEC information adding unit 312 generates a DNS message F12 by adding MEC information to the DNS query (DNS message F11) based on the information acquired by the DNS query acquiring unit 311. In this case, the MEC information adding unit 312 may determine the MEC information based on the information acquired by the DNS query acquiring unit 311. The DNS query output unit 313 returns the DNS message F12 generated by the MEC information adding unit 312 to the original communication flow (in the example of FIG. 3, it is output to the DNS 243).

[0061] In this embodiment, the DNS query sent from UE211 to DNS243 is tapped and acquired by an intermediate node (in this embodiment, assignment node 242), information related to the MEC system (MEC information) is assigned to the DNS query, and the DNS query with the assigned MEC information is returned to the original path. When the DNS message F12 is transmitted to the original destination DNS 243, the DNS query output unit 313 may output the DNS message F12 to a communication flow other than the original communication flow.

[0062] As an example, the DNS query control device 251 can add information (MEC information) to the DNS query for querying the DNS record of the MEC host corresponding to the geography based on geographical information such as GPS information included in the UE information. As another example, the DNS query control device 251 can directly or indirectly refer to network information such as the load status of each MEC host or the network topology, and assign parameters (MEC information) that take these into consideration.

[0063] Here, in this embodiment, the DNS query output from the UE 211 is configured to be steered so as to pass through the granting node 242 (DNS query control device 251). In this embodiment, the DNS query control device 251 may function as a MEC host and act as a DNS server to receive DNS queries.

[0064] [Case Study] The cases are similar to the cases (first to third cases) described in the first embodiment. In this embodiment, generally speaking, compared to the first embodiment, the difference is that the DNS query control device 251 is arranged outside the MEC system 241, but other points are similar.

[0065] In this embodiment, for example, a switch capable of processing packets at high speed, such as a p4 language compatible switch (in this embodiment, the assignment node 242) can be used, and the switch can be configured to receive information from the MEC system 241 as appropriate and assign the information as MEC information.

[0066] [Regarding the second embodiment] As described above, in the communication system 201 according to this embodiment, the DNS query control device 251 rewrites the DNS query created by the terminal device (in this embodiment, the UE 211) at the granting node 242, thereby realizing detailed control without the user or application being aware of it.

[0067] Furthermore, in the communication system 201 of this embodiment, except that the placement position of the DNS query control device 251 is different from that of the first embodiment, it is possible to obtain the same effects as those described for the communication system 1 of the first embodiment, for example.

[0068] <Configuration example according to the second embodiment> As an example configuration, the DNS query control device 251 includes a DNS query acquisition unit 311 that acquires a first DNS message (in the example of FIG. 3, DNS message F11) including a first DNS query output from a terminal device (in the example of FIG. 3, UE 211), an MEC information addition unit 312 that adds MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition unit 311 to generate a second DNS message (in the example of FIG. 3, DNS message F12), and a DNS query output unit 313 that outputs the second DNS message generated by the MEC information addition unit 312.

[0069] As one configuration example, in the DNS query control device 251, the MEC information adding unit 312 determines the MEC information to add to the first DNS query based on information about the terminal device (in the example of Figure 3, UE information) included in the first DNS message acquired by the DNS query acquiring unit 311.

[0070] In one configuration example, the DNS query control device 251 is provided outside the MEC system 241 and acquires information about MEC information from the MEC system 241. The information is information to which the DNS query control device 251 can add MEC information, and may be, for example, the MEC information itself, or other information.

[0071] Here, similarly to the first embodiment, it is also possible to provide a method of processing performed in the DNS query control device 251. Also, as in the first embodiment, it is possible to provide a program for controlling DNS queries.

[0072] [Regarding the above embodiment] As a result, it will be possible to improve the overall service quality of wireless networks, which will contribute to Goal 9 of the United Nations-led Sustainable Development Goals (SDGs), which is to "Build resilient infrastructure, promote sustainable industrialization and foster innovation."

[0073] A program for implementing the functions of any of the components of any of the above-described devices may be recorded on a computer-readable recording medium and loaded into a computer system for execution. The term "computer system" as used herein includes hardware such as an operating system or peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and compact discs (CDs) or read-only memories (ROMs), as well as storage devices such as hard disks built into computer systems. The term "computer-readable recording medium" also includes devices that retain a program for a certain period of time, such as volatile memory within a computer system that acts as a server or client when a program is transmitted over a network such as the Internet or a communication line such as a telephone line. Such volatile memory may be, for example, random access memory (RAM). The recording medium may also be, for example, a non-transitory recording medium.

[0074] The above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network such as the Internet or a communication line such as a telephone line. The above program may also be one that realizes part of the above-mentioned functions. Furthermore, the above program may be a so-called differential file that can realize the above-mentioned functions in combination with a program already recorded in a computer system. A differential file may also be called a differential program.

[0075] Furthermore, the functions of any of the components in any of the above-described devices may be implemented by a processor. For example, each process in the embodiments may be implemented by a processor operating based on information such as a program and a computer-readable recording medium storing information such as the program. Here, the functions of each unit of the processor may be implemented by, for example, individual hardware, or may be implemented by integrated hardware. For example, the processor may include hardware, and the hardware may include at least one of a circuit for processing digital signals and a circuit for processing analog signals. For example, the processor may be configured using one or more circuit devices mounted on a circuit board, or one or both of one or more circuit elements. An integrated circuit (IC) or the like may be used as the circuit device, and a resistor or a capacitor may be used as the circuit element.

[0076] Here, the processor may be, for example, a CPU. However, the processor is not limited to a CPU, and various types of processors such as a GPU (Graphics Processing Unit) or a DSP (Digital Signal Processor) may be used. The processor may also be, for example, a hardware circuit such as an ASIC (Application Specific Integrated Circuit). The processor may also be, for example, composed of multiple CPUs, or may be, for example, composed of a hardware circuit such as a multiple ASIC. The processor may also be, for example, composed of a combination of multiple CPUs and a hardware circuit such as a multiple ASIC. The processor may also include, for example, one or more of an amplifier circuit or a filter circuit that processes analog signals.

[0077] The embodiments of this disclosure have been described in detail above with reference to the drawings, but the specific configuration is not limited to this embodiment, and includes designs within the scope that do not deviate from the gist of this disclosure. [Explanation of symbols]

[0078] 1, 201...Communication system, 11, 211...UE, 21, 22, 221, 222...Base station device, 31, 32, 231, 232...UPF, 41, 241...MEC system, 42, 243...DNS, 51, 251...DNS query control device, 242...Providing node, 111, 311...DNS query acquisition unit, 112, 312...MEC information addition unit, 113, 313...DNS query output unit, 611, 711, 712...Device, 632, 731, 732...MEC host, F1, F2, F11, F12...DNS message, T1, T2, T11, T12...Communication

Claims

1. a DNS query acquisition unit that acquires a first DNS message including a first DNS query output from a terminal device; an MEC information adding unit that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquiring unit; a DNS query output unit that outputs the second DNS message generated by the MEC information adding unit; Equipped with the MEC information adding unit determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring unit; the information about the terminal device is information that represents a computing resource requirement of an application; The MEC information is information representing a processing load of an MEC host. DNS query control device.

2. a DNS query acquisition unit that acquires a first DNS message including a first DNS query output from a terminal device; an MEC information adding unit that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquiring unit; a DNS query output unit that outputs the second DNS message generated by the MEC information adding unit; Equipped with the MEC information adding unit determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring unit; the information about the terminal device is information that represents a delay requirement of an application; The MEC information is information representing a round trip time from the UPF. DNS query control device.

3. Provided in the MEC system, The DNS query control device according to claim 1 or 2.

4. Located outside the MEC system, obtaining information about the MEC information from the MEC system; The DNS query control device according to claim 1 or 2.

5. a DNS query acquisition unit that acquires a first DNS message including a first DNS query output from the terminal device; an MEC information adding unit adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquiring unit to generate a second DNS message; a DNS query output unit outputs the second DNS message generated by the MEC information adding unit; the MEC information adding unit determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring unit; the information about the terminal device is information that represents a computing resource requirement of an application; The MEC information is information representing a processing load of an MEC host. DNS query control method.

6. a DNS query acquisition unit that acquires a first DNS message including a first DNS query output from the terminal device; an MEC information adding unit adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquiring unit to generate a second DNS message; a DNS query output unit outputs the second DNS message generated by the MEC information adding unit; the MEC information adding unit determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring unit; the information about the terminal device is information representing a delay requirement of an application, The MEC information is information representing a round trip time from the UPF. DNS query control method.

7. On the computer, a DNS query acquisition function for acquiring a first DNS message including a first DNS query output from a terminal device; an MEC information addition function that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition function; a DNS query output function that outputs the second DNS message generated by the MEC information addition function; A program for realizing the above, The MEC information adding function determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring function; the information about the terminal device is information that represents a computing resource requirement of an application; The MEC information is information representing a processing load of an MEC host. program.

8. On the computer, a DNS query acquisition function for acquiring a first DNS message including a first DNS query output from a terminal device; an MEC information addition function that generates a second DNS message by adding MEC information to the first DNS query based on the first DNS message acquired by the DNS query acquisition function; a DNS query output function that outputs the second DNS message generated by the MEC information addition function; A program for realizing the above, The MEC information adding function determines the MEC information to be added to the first DNS query based on information about the terminal device included in the first DNS message acquired by the DNS query acquiring function; the information about the terminal device is information representing a delay requirement of an application, The MEC information is information representing a round trip time from the UPF. program.

Images