WO2022038789A1 - Database selection device, database selection method, and program - Google Patents

Database selection device, database selection method, and program Download PDF

Info

Publication number
WO2022038789A1
WO2022038789A1 PCT/JP2020/031727 JP2020031727W WO2022038789A1 WO 2022038789 A1 WO2022038789 A1 WO 2022038789A1 JP 2020031727 W JP2020031727 W JP 2020031727W WO 2022038789 A1 WO2022038789 A1 WO 2022038789A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
delay requirement
storage request
request
delay
Prior art date
Application number
PCT/JP2020/031727
Other languages
French (fr)
Japanese (ja)
Inventor
明寛 木村
Original Assignee
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電信電話株式会社 filed Critical 日本電信電話株式会社
Priority to PCT/JP2020/031727 priority Critical patent/WO2022038789A1/en
Priority to JP2022543260A priority patent/JPWO2022038789A1/ja
Publication of WO2022038789A1 publication Critical patent/WO2022038789A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • the present invention relates to a database selection device, a database selection method and a program.
  • the time required for the response of the database management system (hereinafter referred to as "DBM") mainly consists of the data search algorithm and the access time to the storage device.
  • DBM database management system
  • the on-disk database is a method in which data is managed by a disk storage mechanism such as an HDD, and while the device cost can be suppressed compared to an in-memory database, the access time is long (several milliseconds to several tens of milliseconds). Has.
  • the in-memory database is a method of managing data on memory such as main memory, and has the characteristic that the access time is shorter (several nanoseconds) than the on-disk database, but the equipment cost is high.
  • the hybrid database is a method of managing data by using both an on-disk database and an in-memory database.
  • MySQL Non-Patent Document 1
  • SQLite Non-Patent Document 2
  • the on-disk database and the in-memory database are stored in table units. Can be selected.
  • the term hybrid database is sometimes used to mean that different types of DBM (SQL or NoSQL) can be used together, but the hybrid database here is slow like the above-mentioned on-disk and in-memory. It is limited to the meaning of using DB and high-speed DB together.
  • MySQL "16.3 The MEMORY Storage Engine”, [online], Internet ⁇ URL: https://dev.mysql.com/doc/refman/8.0/en/memory-storage-engine.html> SQLite, "In-Memory Databases", [online], Internet ⁇ URL: https://www.sqlite.org/inmemorydb.html>
  • the present invention has been made in view of the above points, and an object of the present invention is to increase the possibility of accessing an appropriate database in response to a request from a terminal.
  • the database selection device is provided with a determination unit that determines a delay requirement based on network information related to the storage request for a data storage request in a database transmitted from a terminal, and a determination unit. It has a selection unit for selecting a database as a storage destination of the data from a plurality of databases based on the determined delay requirement.
  • FIG. 1 is a diagram showing an example of a basic system configuration according to each embodiment of the present invention.
  • the system shown in FIG. 1 includes a plurality of terminals 20 on an IP network, an application server 10, a DBM 30 (database management system), and the like.
  • the terminal 20 is an information processing device that transmits a data storage request or a data acquisition request to the application server 10.
  • the application server 10 is one or more computers that perform application processing, data storage in the DBM 30, and data acquisition from the DBM 30 in response to a request from the terminal 20.
  • the DBM 30 is one or more computers that manage a high-speed DB 31 which is a database having a relatively short access time and a low-speed DB 32 which is a database having a relatively long access time.
  • the DBM30 may be constructed using hybrid database technology.
  • the difference in access time is not limited to the difference in device type. Specifically, each embodiment can be applied even in a case where a database located near the network topology and a database located far away are used properly.
  • the application server 10 and the DBM 30 are represented by different figures, but the theory structure is not limited to this. Specifically, there are cases where the application server 10 and the DBM 30 exist as physically separate devices, and cases where the application server 10 and the DBM 30 exist logically separately in the physically same device.
  • the delay requirement for the request from the terminal 20 may differ depending on the request, and a method for the application server 10 to determine the delay requirement for each request is disclosed.
  • network information regarding the request from the terminal 20 is used in determining the delay requirement.
  • the system for satisfying the delay requirement for accessing the database is not only an effort to reduce the delay for the application server 10 and the DB, but also the overall low delay including the network to reach it. It is conceivable to make efforts for the conversion. For example, by dividing the network into multiple logical planes (slices) and using a technology (network slice technology) that uses communication quality properly, applications with low-latency network slices are used for requests with low-latency requirements. It is conceivable that the packet is transferred to the server 10, and the application server 10 selects a low-delay DB (high-speed DB 31) to store and acquire data.
  • a low-delay DB high-speed DB 31
  • FIG. 2 is a diagram showing an example of a system configuration according to the first embodiment.
  • the same parts as those in FIG. 1 are designated by the same reference numerals, and the description thereof will be omitted.
  • the application server 10 can communicate with the network controller 40.
  • a system administrator or the like uses a network controller to create a low-latency NW and a normal NW as a network connecting each terminal 20 and the application server 10.
  • a low-delay NW is a network with a relatively small delay (high speed).
  • the NW is a network with a relatively large delay (slow speed).
  • the method of realizing the low delay NW and the normal NW is not limited to a specific method.
  • the application server 10 has an interface for connecting to the low-delay NW or the normal NW for each low-delay NW and the normal NW.
  • FIG. 3 is a diagram showing a hardware configuration example of the application server 10 according to the first embodiment.
  • the application server 10 of FIG. 3 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other by a bus B, respectively.
  • the program that realizes the processing in the application server 10 is provided by a recording medium 101 such as a CD-ROM.
  • a recording medium 101 such as a CD-ROM.
  • the program is installed in the auxiliary storage device 102 from the recording medium 101 via the drive device 100.
  • the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network.
  • the auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.
  • the memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program.
  • the CPU 104 executes the function related to the application server 10 according to the program stored in the memory device 103.
  • the interface device 105 is used as an interface for connecting to a network.
  • FIG. 4 is a diagram showing a functional configuration example of the application server 10 in the first embodiment.
  • the application server 10 includes a storage request receiving unit 11, a delay requirement determination unit 12, a storage destination DB selection unit 13, a data storage unit 14, and the like. Each of these parts is realized by a process of causing the CPU 104 to execute one or more programs installed in the application server 10.
  • FIG. 5 is a flowchart for explaining an example of the processing procedure of the data storage processing in the first embodiment.
  • step S101 the storage request receiving unit 11 receives the data storage request transmitted from any terminal 20 (hereinafter referred to as "target terminal 20") (S101).
  • the target terminal 20 or the NW device on the communication path of the data storage request selects the network used for transferring the data storage request based on the delay requirement of the data storage request. Specifically, when the low-delay NW and the normal NW are directly connected to the target terminal 20, the target terminal 20 connects to one of the networks according to the application that uses the data related to the data storage request. Select and send a data storage request to the selected network.
  • the NW device when the low-delay NW and the normal NW are not connected to the target terminal 20, and the low-delay NW and the normal NW are connected to a NW device such as a switch or a router, the NW device is connected.
  • the application is judged based on the network information of the data storage request, and one of the networks is selected based on the judgment result.
  • L2 header information, L3 header information (IP header information), and the like are assumed as the network information of the data storage request.
  • the NW device identifies the target terminal 20 from the source MAC address of the L2 header of the data storage request and the source IP address of the L3 header, and corresponds to the application associated with the target terminal 20 in advance. Transfer the data storage request to the network.
  • the NW device can determine the delay requirement by this method.
  • the NW device may identify the application server 10 from the destination IP address or destination port number of the L3 header of the data storage request, and transfer the data storage request to the network associated with the application server 10 in advance. .. This method is effective when the delay requirement of the application handled by the application server 10 is constant for each IP address or each port number.
  • the NW device may select the transfer destination network based on the TOS value of the L3 header of the data storage request.
  • the target terminal 20 may set a TOS value in the data storage request according to the application to which the data storage request is transmitted.
  • step S101 the data storage request whose delay requirement is "low delay” is received via the low delay NW.
  • a data storage request whose delay requirement is "non-low delay” is usually received via the NW.
  • “non-low delay” means that low delay is not required.
  • the delay requirement determination unit 12 determines the delay requirement of the received data storage request (hereinafter, referred to as “target request”) (S102).
  • target request the delay requirement determination unit 12 inquires in advance of the network controller 40, and acquires correspondence information between the low delay NW and the normal NW and each network interface of the application server 10. Further, the delay requirement determination unit 12 stores information for associating each network interface with the delay requirement in the auxiliary storage device 102 or the like based on the corresponding information.
  • the delay requirement determination unit 12 determines the delay requirement of the target request based on the network interface in which the target request is received and the information. That is, when the target request is received via the low delay NW, the delay requirement determination unit 12 determines that the delay requirement of the target request is "low delay”. On the other hand, when the target request is normally received via the NW, the delay requirement determination unit 12 determines that the delay requirement of the target request is "non-low delay”.
  • the storage destination DB selection unit 13 selects the database of the storage destination of the data related to the target request based on the delay requirement determined by the delay requirement determination unit 12 (S103). For example, the storage destination DB selection unit 13 selects the high-speed DB 31 as the storage destination if the delay requirement is "low delay”, and the low-speed DB 32 as the storage destination if the delay requirement is "non-low delay”. select.
  • the data storage unit 14 transmits the data related to the target request to the database selected by the storage destination DB selection unit 13 (S104).
  • the data for which low delay is required is stored in the high-speed DB 31, the delay time is suppressed, and the data for which low delay is not required is stored in the low-speed DB 32, and the device cost is suppressed.
  • the second embodiment will explain the differences from the first embodiment.
  • the points not particularly mentioned in the second embodiment may be the same as those in the first embodiment.
  • FIG. 6 is a diagram showing a system configuration example in the second embodiment.
  • the same parts as those in FIG. 1 are designated by the same reference numerals, and the description thereof will be omitted.
  • the application server 10 can communicate with the authentication system 50.
  • the authentication system 50 is a system for authenticating the terminal 20, authorizing the use of services, and accounting.
  • a system using IEEE 802.1X and a RADIUS server can be mentioned as an example of the authentication system 50.
  • the authentication system 50 is preset with a delay requirement for each terminal 20.
  • the authentication system 50 is preset with information that associates the MAC address, which is the identification information on the physical layer of each terminal 20, with the delay requirement.
  • the terminal 20 executes an authentication sequence by the authentication system 50, and after communication becomes possible, sends a data storage request to the application server 10 using the L2 network (data link layer network). do. Therefore, in step S101 of FIG. 5, the storage request receiving unit 11 receives the data storage request of the physical layer.
  • step S102 the delay requirement determination unit 12 sets the delay requirement associated with the source MAC address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11 from the authentication system 50. Acquire and determine the delay requirement as the delay requirement for the target request.
  • target request the data storage request
  • the third embodiment will explain the differences from the second embodiment.
  • the points not particularly mentioned in the third embodiment may be the same as those in the second embodiment.
  • the authentication system 50 is preset with information for associating an IP address, which is identification information on the network layer of each terminal 20, with a delay requirement.
  • the terminal 20 executes an authentication sequence by the authentication system 50, and after communication becomes possible, transmits a data storage request to the application server 10 using an IP network (network of the network layer). .. Therefore, in step S101 of FIG. 5, the storage request receiving unit 11 receives the data storage request of the network layer.
  • step S102 the delay requirement determination unit 12 sets the delay requirement associated with the source IP address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11 from the authentication system 50. Acquire and determine the delay requirement as the delay requirement for the target request.
  • target request the delay requirement associated with the source IP address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11 from the authentication system 50. Acquire and determine the delay requirement as the delay requirement for the target request.
  • the fourth embodiment will explain the differences from the first embodiment.
  • the points not particularly mentioned in the fourth embodiment may be the same as those in the first embodiment.
  • the system configuration of the fourth embodiment may be as shown in FIG. Therefore, unlike the first embodiment, there is no distinction between a low latency NW and a normal NW in the network between the terminal 20 and the application server 10.
  • a delay requirement corresponding to the IP address is set for each of the plurality of IP addresses for the application server 10. That is, the correspondence information between the IP address and the delay requirement is set for the application server 10.
  • the corresponding information is stored in, for example, the auxiliary storage device 102. Further, the corresponding information is also shared with each terminal 20.
  • the terminal 20 transmits a data storage request with an IP address corresponding to a desired delay requirement as a destination IP address to the application server 10.
  • step S102 of FIG. 5 the delay requirement determination unit 12 targets the delay requirement associated with the destination IP address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11. Determined as a delay requirement for the request.
  • the fifth embodiment will explain the differences from the fourth embodiment.
  • the points not particularly mentioned in the fifth embodiment may be the same as those in the fourth embodiment.
  • a delay requirement corresponding to the port number is set for each of the plurality of port numbers for the application server 10. That is, the correspondence information between the port number and the delay requirement is set for the application server 10.
  • the corresponding information is stored in, for example, the auxiliary storage device 102. Further, the corresponding information is also shared with each terminal 20. In the fifth embodiment, the correspondence information between the IP address and the delay requirement is unnecessary.
  • the terminal 20 transmits a data storage request with the port number corresponding to the desired delay requirement as the destination port number to the application server 10.
  • step S102 of FIG. 5 the delay requirement determination unit 12 targets the delay requirement associated with the destination port number of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11. Determined as a delay requirement for the request.
  • the sixth embodiment will explain the differences from the fifth embodiment.
  • the points not particularly mentioned in the sixth embodiment may be the same as those in the fifth embodiment.
  • the delay requirement corresponding to the TOS value is set for each of the plurality of TOS values in the application server 10. That is, the correspondence information between the TOS value and the delay requirement is set for the application server 10.
  • the corresponding information is stored in, for example, the auxiliary storage device 102. Further, the corresponding information is also shared with each terminal 20. In the sixth embodiment, the correspondence information between the port number and the delay requirement is unnecessary.
  • the terminal 20 transmits a data storage request including the TOS value corresponding to the desired delay requirement in the IP header to the application server 10.
  • the delay requirement determination unit 12 is associated with the TOS value included in the IP header of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11.
  • the delay requirement is determined as the delay requirement for the target request.
  • the application server 10 is an example of the database selection device in the present embodiment.
  • the delay requirement determination unit 12 is an example of the determination unit.
  • the storage destination DB selection unit 13 is an example of the selection unit.
  • Application server 11 Storage request receiving unit 12 Delay requirement determination unit 13 Storage destination DB selection unit 14 Data storage unit 20 Terminal 30 DBM 31 High-speed DB 32 Low speed DB 40 Network controller 50 Authentication system 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU 105 Interface device B Bus

Abstract

A database selection device has a determination unit for determining, for a storing request of data into a database, which is transmitted from a terminal, a delay requirement on the basis of network information relating to the storing request and a selection unit for selecting, on the basis of the delay requirement determined by the determination unit, a database as a storing destination of the data from among a plurality of databases, thereby increasing a possibility of access to an appropriate database in response to the request from the terminal.

Description

データベース選択装置、データベース選択方法及びプログラムDatabase selection device, database selection method and program
　本発明は、データベース選択装置、データベース選択方法及びプログラムに関する。 The present invention relates to a database selection device, a database selection method and a program.
　データベースマネジメントシステム（以下「ＤＢＭ」という。）の応答にかかる時間は、主にデータの検索アルゴリズムとストレージデバイスへのアクセス時間からなる。ここではストレージデバイスへのアクセス時間について考える。 The time required for the response of the database management system (hereinafter referred to as "DBM") mainly consists of the data search algorithm and the access time to the storage device. Here, consider the access time to the storage device.
　既存技術として、ストレージデバイスのアクセス時間を考慮した方式として、オンディスクデータベース、インメモリデータベース及びハイブリッドデータベースが存在する。 As an existing technology, there are on-disk database, in-memory database and hybrid database as a method considering the access time of the storage device.
　オンディスクデータベースとは、データをＨＤＤ等のディスクストレージ機構で管理する方式であり、インメモリデータベースに比べて装置コストを抑制できる一方、アクセス時間が長い（数ミリ秒～数十ミリ秒）という特性を有する。 The on-disk database is a method in which data is managed by a disk storage mechanism such as an HDD, and while the device cost can be suppressed compared to an in-memory database, the access time is long (several milliseconds to several tens of milliseconds). Has.
　インメモリデータベースは、データをメインメモリ等のメモリ上で管理する方式であり、オンディスクデータベースに比べてアクセス時間が短い（数ナノ秒）一方、装置コストが高いという特性を有する。 The in-memory database is a method of managing data on memory such as main memory, and has the characteristic that the access time is shorter (several nanoseconds) than the on-disk database, but the equipment cost is high.
　ハイブリッドデータベースは、オンディスクデータベースとインメモリデータベースを併用してデータを管理する方式であり、ＭｙＳＱＬ（非特許文献１）やＳＱＬｉｔｅ（非特許文献２）では、テーブル単位でオンディスクデータベースとインメモリデータベースを選択可能である。なお、ハイブリッドデータベースという用語は、異なる種類のＤＢＭ（ＳＱＬやＮｏＳＱＬ）を併用可能という意味で使われることもあるが、ここでのハイブリッドデータベースは、上述のオンディスクとインメモリのように、低速なＤＢと高速なＤＢの併用という意味に限定される。 The hybrid database is a method of managing data by using both an on-disk database and an in-memory database. In MySQL (Non-Patent Document 1) and SQLite (Non-Patent Document 2), the on-disk database and the in-memory database are stored in table units. Can be selected. The term hybrid database is sometimes used to mean that different types of DBM (SQL or NoSQL) can be used together, but the hybrid database here is slow like the above-mentioned on-disk and in-memory. It is limited to the meaning of using DB and high-speed DB together.
　従来技術のハイブリットＤＢにおいては、データを扱うアプリケーション、すなわちＤＢＭにクエリを送信するクライアント（データベースクライアント）がデータ格納に使用する方式（データベース）を選択する必要があった。この場合、ＩＰネットワークの端末からのクエリでは、アクセス先のデータベースとして、ネットワークによる遅延や、分散ＤＢによるハードウェア性能による差なども考慮した適切なデータベースの選択が困難であるという問題が有った。 In the hybrid DB of the prior art, it was necessary to select a method (database) used for data storage by an application that handles data, that is, a client (database client) that sends a query to DBM. In this case, in the query from the terminal of the IP network, there is a problem that it is difficult to select an appropriate database as the access destination database in consideration of the delay due to the network and the difference due to the hardware performance due to the distributed DB. ..
　本発明は、上記の点に鑑みてなされたものであって、端末からの要求に対して適切なデータベースへのアクセスの可能性を高めることを目的とする。 The present invention has been made in view of the above points, and an object of the present invention is to increase the possibility of accessing an appropriate database in response to a request from a terminal.
　そこで上記課題を解決するため、データベース選択装置は、端末から送信される、データベースへのデータの格納要求について、前記格納要求に関するネットワーク情報に基づいて遅延要件を判定する判定部と、前記判定部によって判定された遅延要件に基づいて、複数のデータベースの中から前記データの格納先とするデータベースを選択する選択部と、を有する。 Therefore, in order to solve the above problem, the database selection device is provided with a determination unit that determines a delay requirement based on network information related to the storage request for a data storage request in a database transmitted from a terminal, and a determination unit. It has a selection unit for selecting a database as a storage destination of the data from a plurality of databases based on the determined delay requirement.
　端末からの要求に対して適切なデータベースへのアクセスの可能性を高めることができる。 It is possible to increase the possibility of accessing an appropriate database in response to a request from the terminal.
本発明の各実施の形態における基本的なシステム構成例を示す図である。It is a figure which shows the example of the basic system configuration in each embodiment of this invention. 第１の実施の形態におけるシステム構成例を示す図である。It is a figure which shows the system configuration example in 1st Embodiment. 第１の実施の形態におけるアプリケーションサーバ１０のハードウェア構成例を示す図である。It is a figure which shows the hardware configuration example of the application server 10 in 1st Embodiment. 第１の実施の形態におけるアプリケーションサーバ１０の機能構成例を示す図である。It is a figure which shows the functional configuration example of the application server 10 in 1st Embodiment. 第１の実施の形態におけるデータ格納処理の処理手順の一例を説明するためのフローチャートである。It is a flowchart for demonstrating an example of the processing procedure of the data storage process in 1st Embodiment. 第２の実施の形態におけるシステム構成例を示す図である。It is a figure which shows the system configuration example in 2nd Embodiment.
　以下、図面に基づいて本発明の実施の形態を説明する。図１は、本発明の各実施の形態における基本的なシステム構成例を示す図である。図１に示されるシステムは、ＩＰネットワーク上の複数の端末２０、アプリケーションサーバ１０、及びＤＢＭ３０（データベースマネジメントシステム）等を含む。 Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of a basic system configuration according to each embodiment of the present invention. The system shown in FIG. 1 includes a plurality of terminals 20 on an IP network, an application server 10, a DBM 30 (database management system), and the like.
　端末２０は、アプリケーションサーバ１０に対して、データ格納要求又はデータ取得要求を送信する情報処理装置である。 The terminal 20 is an information processing device that transmits a data storage request or a data acquisition request to the application server 10.
　アプリケーションサーバ１０は、端末２０からの要求に応じて、アプリケーション処理やＤＢＭ３０へのデータ格納やＤＢＭ３０からのデータ取得を行う１以上のコンピュータである。 The application server 10 is one or more computers that perform application processing, data storage in the DBM 30, and data acquisition from the DBM 30 in response to a request from the terminal 20.
　ＤＢＭ３０は、アクセス時間が相対的に短いデータベースである高速ＤＢ３１と、アクセス時間が相対的に長いデータベースである低速ＤＢ３２とを管理する１以上のコンピュータである。ＤＢＭ３０は、ハイブリッドデータベースの技術を用いて構築されてもよい。 The DBM 30 is one or more computers that manage a high-speed DB 31 which is a database having a relatively short access time and a low-speed DB 32 which is a database having a relatively long access time. The DBM30 may be constructed using hybrid database technology.
　なお、各実施の形態では、アクセス時間の違いをデバイス種別の違いだけに限定しない。具体的には、ネットワークトポロジ的に近傍にあるデータベースと遠方にあるデータベースを使い分けるようなケースにおいても、各実施の形態は適用できる。 In each embodiment, the difference in access time is not limited to the difference in device type. Specifically, each embodiment can be applied even in a case where a database located near the network topology and a database located far away are used properly.
　また、図１では、アプリケーションサーバ１０とＤＢＭ３０とが別の図形で表現されているが、論物構成はこれに限定されない。具体的にはアプリケーションサーバ１０及びＤＢＭ３０が物理的に別の装置として存在する場合と、物理的に同一な装置内でそれぞれが論理的に分かれて存在する場合とが考えられる。 Further, in FIG. 1, the application server 10 and the DBM 30 are represented by different figures, but the theory structure is not limited to this. Specifically, there are cases where the application server 10 and the DBM 30 exist as physically separate devices, and cases where the application server 10 and the DBM 30 exist logically separately in the physically same device.
　各実施の形態では、端末２０からの要求に対する遅延要件が、要求によって異なりうる場合が想定され、アプリケーションサーバ１０が要求ごとに遅延要件を判定する方法が開示される。各実施の形態では、遅延要件の判定において、端末２０からの要求に関するネットワーク情報が用いられる。 In each embodiment, it is assumed that the delay requirement for the request from the terminal 20 may differ depending on the request, and a method for the application server 10 to determine the delay requirement for each request is disclosed. In each embodiment, network information regarding the request from the terminal 20 is used in determining the delay requirement.
　この背景として、データベース（ＤＢ）へのアクセスに関する遅延要件を満たすためのシステムは、アプリケーションサーバ１０とＤＢに対する低遅延化の取り組みだけではなく、そこに至るまでのネットワークも含めて総合的に低遅延化の取り組みを行うことが考えられる。例えば、ネットワークを複数の論理面（スライス）に分割し、通信品質を使い分ける技術（ネットワークスライス技術）を用いることで、低遅延要件のある要求に対しては、低遅延なネットワークスライスを用いてアプリケーションサーバ１０までパケットを転送し、さらにアプリケーションサーバ１０では低遅延ＤＢ（高速ＤＢ３１）を選択してデータを格納・取得する、ということが考えられる。 As a background to this, the system for satisfying the delay requirement for accessing the database (DB) is not only an effort to reduce the delay for the application server 10 and the DB, but also the overall low delay including the network to reach it. It is conceivable to make efforts for the conversion. For example, by dividing the network into multiple logical planes (slices) and using a technology (network slice technology) that uses communication quality properly, applications with low-latency network slices are used for requests with low-latency requirements. It is conceivable that the packet is transferred to the server 10, and the application server 10 selects a low-delay DB (high-speed DB 31) to store and acquire data.
　これを実現するため、アプリケーションサーバ１０がＤＢを選択する際に、ネットワーク情報と連携するための方法が必要となる。各実施の形態では、斯かる方法について説明する。 In order to realize this, a method for linking with network information is required when the application server 10 selects a DB. In each embodiment, such a method will be described.
　図２は、第１の実施の形態におけるシステム構成例を示す図である。図２中、図１と同一部分には同一符号を付し、その説明は省略する。図２において、アプリケーションサーバ１０は、ネットワークコントローラ４０と通信可能である。また、システム管理者等によって、ネットワークのコントローラが用いられて、各端末２０とアプリケーションサーバ１０とを接続するネットワークとして低遅延ＮＷと通常ＮＷが作成される。低遅延ＮＷは、相対的に遅延が小さい（高速な）ネットワークである。通常ＮＷは、相対的に遅延が大きい（低速な）ネットワークである。なお、低遅延ＮＷと通常ＮＷの実現方法は特定の方法に限定されない。アプリケーションサーバ１０は、低遅延ＮＷ及び通常ＮＷごとに、低遅延ＮＷ又は通常ＮＷに接続するインタフェースを有する。 FIG. 2 is a diagram showing an example of a system configuration according to the first embodiment. In FIG. 2, the same parts as those in FIG. 1 are designated by the same reference numerals, and the description thereof will be omitted. In FIG. 2, the application server 10 can communicate with the network controller 40. Further, a system administrator or the like uses a network controller to create a low-latency NW and a normal NW as a network connecting each terminal 20 and the application server 10. A low-delay NW is a network with a relatively small delay (high speed). Normally, the NW is a network with a relatively large delay (slow speed). The method of realizing the low delay NW and the normal NW is not limited to a specific method. The application server 10 has an interface for connecting to the low-delay NW or the normal NW for each low-delay NW and the normal NW.
　図３は、第１の実施の形態におけるアプリケーションサーバ１０のハードウェア構成例を示す図である。図３のアプリケーションサーバ１０は、それぞれバスＢで相互に接続されているドライブ装置１００、補助記憶装置１０２、メモリ装置１０３、ＣＰＵ１０４、及びインタフェース装置１０５等を有する。 FIG. 3 is a diagram showing a hardware configuration example of the application server 10 according to the first embodiment. The application server 10 of FIG. 3 has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other by a bus B, respectively.
　アプリケーションサーバ１０での処理を実現するプログラムは、ＣＤ－ＲＯＭ等の記録媒体１０１によって提供される。プログラムを記憶した記録媒体１０１がドライブ装置１００にセットされると、プログラムが記録媒体１０１からドライブ装置１００を介して補助記憶装置１０２にインストールされる。但し、プログラムのインストールは必ずしも記録媒体１０１より行う必要はなく、ネットワークを介して他のコンピュータよりダウンロードするようにしてもよい。補助記憶装置１０２は、インストールされたプログラムを格納すると共に、必要なファイルやデータ等を格納する。 The program that realizes the processing in the application server 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed in the auxiliary storage device 102 from the recording medium 101 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.
　メモリ装置１０３は、プログラムの起動指示があった場合に、補助記憶装置１０２からプログラムを読み出して格納する。ＣＰＵ１０４は、メモリ装置１０３に格納されたプログラムに従ってアプリケーションサーバ１０に係る機能を実行する。インタフェース装置１０５は、ネットワークに接続するためのインタフェースとして用いられる。 The memory device 103 reads the program from the auxiliary storage device 102 and stores it when there is an instruction to start the program. The CPU 104 executes the function related to the application server 10 according to the program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.
　図４は、第１の実施の形態におけるアプリケーションサーバ１０の機能構成例を示す図である。図４において、アプリケーションサーバ１０は、格納要求受信部１１、遅延要件判定部１２、格納先ＤＢ選択部１３及びデータ格納部１４等を有する。これら各部は、アプリケーションサーバ１０にインストールされた１以上のプログラムが、ＣＰＵ１０４に実行させる処理により実現される。 FIG. 4 is a diagram showing a functional configuration example of the application server 10 in the first embodiment. In FIG. 4, the application server 10 includes a storage request receiving unit 11, a delay requirement determination unit 12, a storage destination DB selection unit 13, a data storage unit 14, and the like. Each of these parts is realized by a process of causing the CPU 104 to execute one or more programs installed in the application server 10.
　以下、アプリケーションサーバ１０が実行する処理手順について説明する。図５は、第１の実施の形態におけるデータ格納処理の処理手順の一例を説明するためのフローチャートである。 Hereinafter, the processing procedure executed by the application server 10 will be described. FIG. 5 is a flowchart for explaining an example of the processing procedure of the data storage processing in the first embodiment.
　ステップＳ１０１において、格納要求受信部１１は、いずれかの端末２０（以下、「対象端末２０」という。）から送信されたデータ格納要求を受信する（Ｓ１０１）。 In step S101, the storage request receiving unit 11 receives the data storage request transmitted from any terminal 20 (hereinafter referred to as "target terminal 20") (S101).
　第１の実施の形態において、対象端末２０、又はデータ格納要求の通信経路上のＮＷ装置は、データ格納要求の遅延要件に基づき、データ格納要求の転送に用いるネットワークを選択する。具体的には、低遅延ＮＷ及び通常ＮＷが直接的に対象端末２０に接続されている場合には、対象端末２０が、データ格納要求に係るデータを利用するアプリケーションに応じていずれかのネットワークを選択し、選択したネットワークにデータ格納要求を送信する。 In the first embodiment, the target terminal 20 or the NW device on the communication path of the data storage request selects the network used for transferring the data storage request based on the delay requirement of the data storage request. Specifically, when the low-delay NW and the normal NW are directly connected to the target terminal 20, the target terminal 20 connects to one of the networks according to the application that uses the data related to the data storage request. Select and send a data storage request to the selected network.
　一方、対象端末２０には低遅延ＮＷと通常ＮＷが接続されておらず、その先のスイッチ又はルータ等のＮＷ装置に低遅延ＮＷ及び通常ＮＷが接続されている場合には、当該ＮＷ装置が、データ格納要求のネットワーク情報を基に基づいてアプリケーションを判定し、この判定結果に基づきいずれかのネットワークを選択する。なお、ここで、データ格納要求のネットワーク情報としては、Ｌ２ヘッダ情報やＬ３ヘッダ情報（ＩＰヘッダ情報）等が想定される。 On the other hand, when the low-delay NW and the normal NW are not connected to the target terminal 20, and the low-delay NW and the normal NW are connected to a NW device such as a switch or a router, the NW device is connected. , The application is judged based on the network information of the data storage request, and one of the networks is selected based on the judgment result. Here, as the network information of the data storage request, L2 header information, L3 header information (IP header information), and the like are assumed.
　具体的には、ＮＷ装置は、データ格納要求のＬ２ヘッダの送信元ＭＡＣアドレスやＬ３ヘッダの送信元ＩＰアドレスから対象端末２０を識別し、対象端末２０に予め紐付けられているアプリケーションに対応するネットワークに当該データ格納要求を転送する。一部のＩｏＴ端末ように、対象端末２０とアプリケーションとが一意に紐づく場合にはこの方法でＮＷ装置は遅延要件を判定することが可能となります。 Specifically, the NW device identifies the target terminal 20 from the source MAC address of the L2 header of the data storage request and the source IP address of the L3 header, and corresponds to the application associated with the target terminal 20 in advance. Transfer the data storage request to the network. When the target terminal 20 and the application are uniquely linked like some IoT terminals, the NW device can determine the delay requirement by this method.
　又は、ＮＷ装置は、データ格納要求のＬ３ヘッダの宛先ＩＰアドレス又は宛先ポート番号からアプリケーションサーバ１０を識別し、予めアプリケーションサーバ１０に紐付けられているネットワークに当該データ格納要求を転送してもよい。この方法は、アプリケーションサーバ１０が扱うアプリケーションの遅延要件がＩＰアドレス単位、又はポート番号単位で一定の場合に有効である。 Alternatively, the NW device may identify the application server 10 from the destination IP address or destination port number of the L3 header of the data storage request, and transfer the data storage request to the network associated with the application server 10 in advance. .. This method is effective when the delay requirement of the application handled by the application server 10 is constant for each IP address or each port number.
　又は、ＮＷ装置は、データ格納要求のＬ３ヘッダのＴＯＳ値に基づいて、転送先のネットワークを選択してもよい。この場合、対象端末２０が、データ格納要求の送信先のアプリケーションに応じて、当該データ格納要求にＴＯＳ値を設定してもよい。 Alternatively, the NW device may select the transfer destination network based on the TOS value of the L3 header of the data storage request. In this case, the target terminal 20 may set a TOS value in the data storage request according to the application to which the data storage request is transmitted.
　したがって、ステップＳ１０１では、遅延要件が「低遅延」であるデータ格納要求は、低遅延ＮＷを介して受信される。一方、遅延要件が「非低遅延」であるデータ格納要求は、通常ＮＷを介して受信される。なお、「非低遅延」は、低遅延を求めないことをいう。 Therefore, in step S101, the data storage request whose delay requirement is "low delay" is received via the low delay NW. On the other hand, a data storage request whose delay requirement is "non-low delay" is usually received via the NW. In addition, "non-low delay" means that low delay is not required.
　続いて、遅延要件判定部１２は、受信されたデータ格納要求（以下、「対象要求」という。）の遅延要件を判定する（Ｓ１０２）
　第１の実施の形態において、遅延要件判定部１２は、予めネットワークコントローラ４０に問い合わせ、低遅延ＮＷ及び通常ＮＷと、アプリケーションサーバ１０の各ネットワークインタフェースとの対応情報を取得しておく。また、遅延要件判定部１２は、当該対応情報に基づいて、各ネットワークインタフェースと遅延要件とを対応付ける情報を補助記憶装置１０２等に記憶しておく。遅延要件判定部１２は、対象要求が受信されたネットワークインタフェースと当該情報とに基づいて、対象要求の遅延要件を判定する。すなわち、対象要求が低遅延ＮＷを介して受信された場合、遅延要件判定部１２は、対象要求の遅延要件は「低遅延」であると判定する。一方、対象要求が通常ＮＷを介して受信された場合、遅延要件判定部１２は、対象要求の遅延要件は「非低遅延」であると判定する。 Subsequently, the delay requirement determination unit 12 determines the delay requirement of the received data storage request (hereinafter, referred to as “target request”) (S102).
In the first embodiment, the delay requirement determination unit 12 inquires in advance of the network controller 40, and acquires correspondence information between the low delay NW and the normal NW and each network interface of the application server 10. Further, the delay requirement determination unit 12 stores information for associating each network interface with the delay requirement in the auxiliary storage device 102 or the like based on the corresponding information. The delay requirement determination unit 12 determines the delay requirement of the target request based on the network interface in which the target request is received and the information. That is, when the target request is received via the low delay NW, the delay requirement determination unit 12 determines that the delay requirement of the target request is "low delay". On the other hand, when the target request is normally received via the NW, the delay requirement determination unit 12 determines that the delay requirement of the target request is "non-low delay".
　続いて、格納先ＤＢ選択部１３は、遅延要件判定部１２によって判定された遅延要件に基づいて、対象要求に係るデータの格納先のデータベースを選択する（Ｓ１０３）。例えば、格納先ＤＢ選択部１３は、当該遅延要件が「低遅延」であれば、高速ＤＢ３１を格納先として選択し、当該遅延要件が「非低遅延」であれば、低速ＤＢ３２を格納先として選択する。 Subsequently, the storage destination DB selection unit 13 selects the database of the storage destination of the data related to the target request based on the delay requirement determined by the delay requirement determination unit 12 (S103). For example, the storage destination DB selection unit 13 selects the high-speed DB 31 as the storage destination if the delay requirement is "low delay", and the low-speed DB 32 as the storage destination if the delay requirement is "non-low delay". select.
　続いて、データ格納部１４は、格納先ＤＢ選択部１３が選択したデータベースに対して対象要求に係るデータを送信する（Ｓ１０４）。その結果、低遅延性が求められるデータは高速ＤＢ３１に格納されて、遅延時間が抑制され、低遅延性が求められないデータは低速ＤＢ３２に格納されて、装置コストが抑制される。 Subsequently, the data storage unit 14 transmits the data related to the target request to the database selected by the storage destination DB selection unit 13 (S104). As a result, the data for which low delay is required is stored in the high-speed DB 31, the delay time is suppressed, and the data for which low delay is not required is stored in the low-speed DB 32, and the device cost is suppressed.
　次に、第２の実施の形態について説明する。第２の実施の形態では第１の実施の形態と異なる点について説明する。第２の実施の形態において特に言及されない点については、第１の実施の形態と同様でもよい。 Next, the second embodiment will be described. The second embodiment will explain the differences from the first embodiment. The points not particularly mentioned in the second embodiment may be the same as those in the first embodiment.
　図６は、第２の実施の形態におけるシステム構成例を示す図である。図６中、図１と同一部分には同一符号を付し、その説明は省略する。図６において、アプリケーションサーバ１０は、認証システム５０と通信可能である。認証システム５０は、端末２０の認証、サービス利用の認可、およびアカウンティングを行うシステムであり、例えば、ＩＥＥＥ８０２．１ＸとＲａｄｉｕｓサーバを用いるシステムなどが認証システム５０の一例として挙げられる。第２の実施の形態において、認証システム５０には、端末２０ごとの遅延要件が予め設定される。具体的には、各端末２０の物理層上の識別情報であるＭＡＣアドレスと遅延要件とを対応付ける情報が認証システム５０に予め設定されている。 FIG. 6 is a diagram showing a system configuration example in the second embodiment. In FIG. 6, the same parts as those in FIG. 1 are designated by the same reference numerals, and the description thereof will be omitted. In FIG. 6, the application server 10 can communicate with the authentication system 50. The authentication system 50 is a system for authenticating the terminal 20, authorizing the use of services, and accounting. For example, a system using IEEE 802.1X and a RADIUS server can be mentioned as an example of the authentication system 50. In the second embodiment, the authentication system 50 is preset with a delay requirement for each terminal 20. Specifically, the authentication system 50 is preset with information that associates the MAC address, which is the identification information on the physical layer of each terminal 20, with the delay requirement.
　なお、第１の実施の形態と異なり、端末２０とアプリケーションサーバ１０との間のネットワークには、低遅延ＮＷ及び通常ＮＷの区別は無い。 Note that, unlike the first embodiment, there is no distinction between a low-latency NW and a normal NW in the network between the terminal 20 and the application server 10.
　第２の実施の形態において、端末２０は、認証システム５０による認証シーケンスを実行し、通信可能となった後、データ格納要求をＬ２ネットワーク（データリンク層のネットワーク）を用いてアプリケーションサーバ１０に送信する。したがって、図５のステップＳ１０１において、格納要求受信部１１は、物理層のデータ格納要求を受信する。 In the second embodiment, the terminal 20 executes an authentication sequence by the authentication system 50, and after communication becomes possible, sends a data storage request to the application server 10 using the L2 network (data link layer network). do. Therefore, in step S101 of FIG. 5, the storage request receiving unit 11 receives the data storage request of the physical layer.
　ステップＳ１０２において、遅延要件判定部１２は、格納要求受信部１１が受信したデータ格納要求（以下、「対象要求」という。）の送信元ＭＡＣアドレスに対応付けられている遅延要件を認証システム５０から取得し、当該遅延要件を対象要求に対する遅延要件として判定する。 In step S102, the delay requirement determination unit 12 sets the delay requirement associated with the source MAC address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11 from the authentication system 50. Acquire and determine the delay requirement as the delay requirement for the target request.
　その他は、第１の実施の形態と同様でよい。 Others may be the same as in the first embodiment.
　次に、第３の実施の形態について説明する。第３の実施の形態では第２の実施の形態と異なる点について説明する。第３の実施の形態において特に言及されない点については、第２の実施の形態と同様でもよい。 Next, the third embodiment will be described. The third embodiment will explain the differences from the second embodiment. The points not particularly mentioned in the third embodiment may be the same as those in the second embodiment.
　第３の実施の形態において、認証システム５０には、各端末２０のネットワーク層上の識別情報であるＩＰアドレスと遅延要件とを対応付ける情報が予め設定されている。 In the third embodiment, the authentication system 50 is preset with information for associating an IP address, which is identification information on the network layer of each terminal 20, with a delay requirement.
　第３の実施の形態において、端末２０は、認証システム５０による認証シーケンスを実行し、通信可能となった後、データ格納要求をＩＰネットワーク（ネットワーク層のネットワーク）を用いてアプリケーションサーバ１０に送信する。したがって、図５のステップＳ１０１において、格納要求受信部１１は、ネットワーク層のデータ格納要求を受信する。 In the third embodiment, the terminal 20 executes an authentication sequence by the authentication system 50, and after communication becomes possible, transmits a data storage request to the application server 10 using an IP network (network of the network layer). .. Therefore, in step S101 of FIG. 5, the storage request receiving unit 11 receives the data storage request of the network layer.
　ステップＳ１０２において、遅延要件判定部１２は、格納要求受信部１１が受信したデータ格納要求（以下、「対象要求」という。）の送信元ＩＰアドレスに対応付けられている遅延要件を認証システム５０から取得し、当該遅延要件を対象要求に対する遅延要件として判定する。 In step S102, the delay requirement determination unit 12 sets the delay requirement associated with the source IP address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11 from the authentication system 50. Acquire and determine the delay requirement as the delay requirement for the target request.
　その他は、第２の実施の形態と同様でよい。 Others may be the same as in the second embodiment.
　次に、第４の実施の形態について説明する。第４の実施の形態では第１の実施の形態と異なる点について説明する。第４の実施の形態において特に言及されない点については、第１の実施の形態と同様でもよい。第４の実施の形態のシステム構成は、図１に示した通りでよい。したがって、第１の実施の形態と異なり、端末２０とアプリケーションサーバ１０との間のネットワークには、低遅延ＮＷ及び通常ＮＷの区別は無い。 Next, the fourth embodiment will be described. The fourth embodiment will explain the differences from the first embodiment. The points not particularly mentioned in the fourth embodiment may be the same as those in the first embodiment. The system configuration of the fourth embodiment may be as shown in FIG. Therefore, unlike the first embodiment, there is no distinction between a low latency NW and a normal NW in the network between the terminal 20 and the application server 10.
　第４の実施の形態では、アプリケーションサーバ１０に対して、複数のＩＰアドレスのそれぞれごとに、当該ＩＰアドレスに対応する遅延要件が設定される。すなわち、ＩＰアドレスと遅延要件との対応情報がアプリケーションサーバ１０に対して設定される。当該対応情報は、例えば、補助記憶装置１０２に記憶される。また、当該対応情報は、各端末２０にも共有される。 In the fourth embodiment, a delay requirement corresponding to the IP address is set for each of the plurality of IP addresses for the application server 10. That is, the correspondence information between the IP address and the delay requirement is set for the application server 10. The corresponding information is stored in, for example, the auxiliary storage device 102. Further, the corresponding information is also shared with each terminal 20.
　端末２０は、所望の遅延要件に対応したＩＰアドレスを宛先ＩＰアドレスとするデータ格納要求をアプリケーションサーバ１０へ送信する。 The terminal 20 transmits a data storage request with an IP address corresponding to a desired delay requirement as a destination IP address to the application server 10.
　図５のステップＳ１０２において、遅延要件判定部１２は、格納要求受信部１１が受信したデータ格納要求（以下、「対象要求」という。）の宛先ＩＰアドレスに対応付けられている遅延要件を、対象要求に対する遅延要件として判定する。 In step S102 of FIG. 5, the delay requirement determination unit 12 targets the delay requirement associated with the destination IP address of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11. Determined as a delay requirement for the request.
　その他は、第１の実施の形態と同様でよい。 Others may be the same as in the first embodiment.
　次に、第５の実施の形態について説明する。第５の実施の形態では第４の実施の形態と異なる点について説明する。第５の実施の形態において特に言及されない点については、第４の実施の形態と同様でもよい。 Next, the fifth embodiment will be described. The fifth embodiment will explain the differences from the fourth embodiment. The points not particularly mentioned in the fifth embodiment may be the same as those in the fourth embodiment.
　第５の実施の形態では、アプリケーションサーバ１０に対して、複数のポート番号のそれぞれごとに、当該ポート番号に対応する遅延要件が設定される。すなわち、ポート番号と遅延要件との対応情報がアプリケーションサーバ１０に対して設定される。当該対応情報は、例えば、補助記憶装置１０２に記憶される。また、当該対応情報は、各端末２０にも共有される。なお、第５の実施の形態において、ＩＰアドレスと遅延要件との対応情報は不要である。 In the fifth embodiment, a delay requirement corresponding to the port number is set for each of the plurality of port numbers for the application server 10. That is, the correspondence information between the port number and the delay requirement is set for the application server 10. The corresponding information is stored in, for example, the auxiliary storage device 102. Further, the corresponding information is also shared with each terminal 20. In the fifth embodiment, the correspondence information between the IP address and the delay requirement is unnecessary.
　端末２０は、所望の遅延要件に対応したポート番号を宛先ポート番号とするデータ格納要求をアプリケーションサーバ１０へ送信する。 The terminal 20 transmits a data storage request with the port number corresponding to the desired delay requirement as the destination port number to the application server 10.
　図５のステップＳ１０２において、遅延要件判定部１２は、格納要求受信部１１が受信したデータ格納要求（以下、「対象要求」という。）の宛先ポート番号に対応付けられている遅延要件を、対象要求に対する遅延要件として判定する。 In step S102 of FIG. 5, the delay requirement determination unit 12 targets the delay requirement associated with the destination port number of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11. Determined as a delay requirement for the request.
　その他は、第４の実施の形態と同様でよい。 Others may be the same as in the fourth embodiment.
　次に、第６の実施の形態について説明する。第６の実施の形態では第５の実施の形態と異なる点について説明する。第６の実施の形態において特に言及されない点については、第５の実施の形態と同様でもよい。 Next, the sixth embodiment will be described. The sixth embodiment will explain the differences from the fifth embodiment. The points not particularly mentioned in the sixth embodiment may be the same as those in the fifth embodiment.
　第６の実施の形態では、アプリケーションサーバ１０に対して、複数のＴＯＳ値のそれぞれごとに、当該ＴＯＳ値に対応する遅延要件が設定される。すなわち、ＴＯＳ値と遅延要件との対応情報がアプリケーションサーバ１０に対して設定される。当該対応情報は、例えば、補助記憶装置１０２に記憶される。また、当該対応情報は、各端末２０にも共有される。なお、第６の実施の形態において、ポート番号と遅延要件との対応情報は不要である。 In the sixth embodiment, the delay requirement corresponding to the TOS value is set for each of the plurality of TOS values in the application server 10. That is, the correspondence information between the TOS value and the delay requirement is set for the application server 10. The corresponding information is stored in, for example, the auxiliary storage device 102. Further, the corresponding information is also shared with each terminal 20. In the sixth embodiment, the correspondence information between the port number and the delay requirement is unnecessary.
　端末２０は、所望の遅延要件に対応したＴＯＳ値をＩＰヘッダに含むデータ格納要求をアプリケーションサーバ１０へ送信する。 The terminal 20 transmits a data storage request including the TOS value corresponding to the desired delay requirement in the IP header to the application server 10.
　図５のステップＳ１０２において、遅延要件判定部１２は、格納要求受信部１１が受信したデータ格納要求（以下、「対象要求」という。）のＩＰヘッダに含まれているＴＯＳ値に対応付けられている遅延要件を、対象要求に対する遅延要件として判定する。 In step S102 of FIG. 5, the delay requirement determination unit 12 is associated with the TOS value included in the IP header of the data storage request (hereinafter referred to as “target request”) received by the storage request receiving unit 11. The delay requirement is determined as the delay requirement for the target request.
　その他は、第５の実施の形態と同様でよい。 Others may be the same as in the fifth embodiment.
　上述したように、上記各形態によれば、端末２０２０からの要求に対して適切なデータベースへのアクセスの可能性を高めることができる。 As described above, according to each of the above forms, it is possible to increase the possibility of accessing an appropriate database in response to a request from the terminal 2020.
　なお、上記各実施の形態において、本実施の形態において、アプリケーションサーバ１０は、データベース選択装置の一例である。遅延要件判定部１２は、判定部の一例である。格納先ＤＢ選択部１３は、選択部の一例である。 In each of the above embodiments, the application server 10 is an example of the database selection device in the present embodiment. The delay requirement determination unit 12 is an example of the determination unit. The storage destination DB selection unit 13 is an example of the selection unit.
　以上、本発明の実施の形態について詳述したが、本発明は斯かる特定の実施形態に限定されるものではなく、請求の範囲に記載された本発明の要旨の範囲内において、種々の変形・変更が可能である。 Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.
１０　　　　　アプリケーションサーバ
１１　　　　　格納要求受信部
１２　　　　　遅延要件判定部
１３　　　　　格納先ＤＢ選択部
１４　　　　　データ格納部
２０　　　　　端末
３０　　　　　ＤＢＭ
３１　　　　　高速ＤＢ
３２　　　　　低速ＤＢ
４０　　　　　ネットワークコントローラ
５０　　　　　認証システム
１００　　　　ドライブ装置
１０１　　　　記録媒体
１０２　　　　補助記憶装置
１０３　　　　メモリ装置
１０４　　　　ＣＰＵ
１０５　　　　インタフェース装置
Ｂ　　　　　　バス 10 Application server 11 Storage request receiving unit 12 Delay requirement determination unit 13 Storage destination DB selection unit 14 Data storage unit 20 Terminal 30 DBM
31 High-speed DB
32 Low speed DB
40 Network controller 50 Authentication system 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface device B Bus

Claims (7)

  1. 　端末から送信される、データベースへのデータの格納要求について、前記格納要求に関するネットワーク情報に基づいて遅延要件を判定する判定部と、
    　前記判定部によって判定された遅延要件に基づいて、複数のデータベースの中から前記データの格納先とするデータベースを選択する選択部と、
    を有することを特徴とするデータベース選択装置。     A determination unit that determines the delay requirement based on the network information related to the storage request for the data storage request in the database transmitted from the terminal.
    A selection unit that selects a database to store the data from a plurality of databases based on the delay requirement determined by the determination unit.
    A database selection device characterized by having.
  2. 　前記データベース選択装置は、複数のネットワークに接続し、
    　前記判定部は、前記格納要求がいずれのネットワークを介して受信されたのかに基づいて前記遅延要件を判定する、
    ことを特徴とする請求項１記載のデータベース選択装置。     The database selection device is connected to a plurality of networks and is connected to a plurality of networks.
    The determination unit determines the delay requirement based on which network the storage request was received through.
    The database selection device according to claim 1.
  3. 　前記判定部は、前記格納要求の送信元の識別情報に基づいて前記遅延要件を判定する、
    ことを特徴とする請求項１記載のデータベース選択装置。     The determination unit determines the delay requirement based on the identification information of the source of the storage request.
    The database selection device according to claim 1.
  4. 　前記判定部は、前記格納要求の宛先の識別情報に基づいて前記遅延要件を判定する、
    ことを特徴とする請求項１記載のデータベース選択装置。     The determination unit determines the delay requirement based on the identification information of the destination of the storage request.
    The database selection device according to claim 1.
  5. 　前記判定部は、前記格納要求のＴＯＳ値に基づいて前記遅延要件を判定する、
    ことを特徴とする請求項１記載のデータベース選択装置。     The determination unit determines the delay requirement based on the TOS value of the storage request.
    The database selection device according to claim 1.
  6. 　端末から送信される、データベースへのデータの格納要求について、前記格納要求に関するネットワーク情報に基づいて遅延要件を判定する判定手順と、
    　前記判定手順において判定された遅延要件に基づいて、複数のデータベースの中から前記データの格納先とするデータベースを選択する選択手順と、
    をコンプータが実行することを特徴とするデータベース選択方法。     A determination procedure for determining a delay requirement based on network information related to the storage request for a data storage request sent from a terminal to a database, and a determination procedure.
    A selection procedure for selecting a database to store the data from a plurality of databases based on the delay requirement determined in the determination procedure, and a selection procedure.
    A database selection method characterized by the computer performing.
  7. 　請求項１乃至５いずれか一項記載のデータベース選択装置としてコンピュータを機能させることを特徴とするプログラム。 A program characterized by operating a computer as the database selection device according to any one of claims 1 to 5.
PCT/JP2020/031727 2020-08-21 2020-08-21 Database selection device, database selection method, and program WO2022038789A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2020/031727 WO2022038789A1 (en) 2020-08-21 2020-08-21 Database selection device, database selection method, and program
JP2022543260A JPWO2022038789A1 (en) 2020-08-21 2020-08-21

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/031727 WO2022038789A1 (en) 2020-08-21 2020-08-21 Database selection device, database selection method, and program

Publications (1)

Publication Number Publication Date
WO2022038789A1 true WO2022038789A1 (en) 2022-02-24

Family

ID=80322607

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/031727 WO2022038789A1 (en) 2020-08-21 2020-08-21 Database selection device, database selection method, and program

Country Status (2)

Country Link
JP (1) JPWO2022038789A1 (en)
WO (1) WO2022038789A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003258871A (en) * 2002-03-02 2003-09-12 At & T Corp Automatic router constitution based on traffic and service level agreement
JP2006332825A (en) * 2005-05-24 2006-12-07 Fujitsu Ltd Program, method, and device for dispersing load
JP2015041938A (en) * 2013-08-23 2015-03-02 学校法人東京電機大学 Network control method
CN111371857A (en) * 2012-10-05 2020-07-03 甲骨文国际公司 Load balancing access to replicated databases

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003258871A (en) * 2002-03-02 2003-09-12 At & T Corp Automatic router constitution based on traffic and service level agreement
JP2006332825A (en) * 2005-05-24 2006-12-07 Fujitsu Ltd Program, method, and device for dispersing load
CN111371857A (en) * 2012-10-05 2020-07-03 甲骨文国际公司 Load balancing access to replicated databases
JP2015041938A (en) * 2013-08-23 2015-03-02 学校法人東京電機大学 Network control method

Also Published As

Publication number Publication date
JPWO2022038789A1 (en) 2022-02-24

Similar Documents

Publication Publication Date Title
US9923958B1 (en) Highly available network filer with automatic load balancing and performance adjustment
US10084746B2 (en) High performance DNS traffic management
US10530745B2 (en) Network address and hostname mapping in policy service
EP2666281B1 (en) Domain name system server
US11818209B2 (en) State management and object storage in a distributed cloud computing network
JP2004192305A (en) METHOD AND SYSTEM FOR MANAGING iSCSI STORAGE
JP2003030079A (en) Contents sharing set and software program to be performed by devices constituting the same
WO2019006775A1 (en) Data transmission method and system thereof
US8250176B2 (en) File sharing method and file sharing system
US9565276B2 (en) Transparent redirection of clients to a surrogate payload server through the use of a proxy location server
US11444998B2 (en) Bit rate reduction processing method for data file, and server
US11755541B2 (en) Distributed file system and method for accessing a file in such a system
US20080270483A1 (en) Storage Management System
US11562030B2 (en) Applying filter expressions to requests at an edge server
WO2022038789A1 (en) Database selection device, database selection method, and program
US20080307045A1 (en) Method, system and apparatus for managing directory information
US20050240609A1 (en) Method and apparatus for setting storage groups
JP6607044B2 (en) Server device, distributed file system, distributed file system control method, and program
WO2012046585A1 (en) Distributed storage system, method of controlling same, and program
WO2022143751A1 (en) Method for managing storage system, and storage system and computing program product
JP2000250918A (en) Distributed data base system, retrieval method and recording medium recording processing program of the method
JP4492569B2 (en) File operation control device, file operation control system, file operation control method, and file operation control program
WO2022038790A1 (en) Database selection device, database selection method, and program
US10275155B2 (en) Methods for autonomous disk ownership assignment of nodes in a storage network with a multi-path configuration and devices thereof
JP2002024191A (en) Www system, traffic relief method for www server and www server

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20950354

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022543260

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20950354

Country of ref document: EP

Kind code of ref document: A1