WO2023162130A1 - Data collection system, method, and program - Google Patents

Data collection system, method, and program Download PDF

Info

Publication number
WO2023162130A1
WO2023162130A1 PCT/JP2022/007865 JP2022007865W WO2023162130A1 WO 2023162130 A1 WO2023162130 A1 WO 2023162130A1 JP 2022007865 W JP2022007865 W JP 2022007865W WO 2023162130 A1 WO2023162130 A1 WO 2023162130A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
communication path
server
data source
connection request
Prior art date
Application number
PCT/JP2022/007865
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/JP2022/007865 priority Critical patent/WO2023162130A1/en
Publication of WO2023162130A1 publication Critical patent/WO2023162130A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment

Definitions

  • This disclosure relates to communication control for data collection.
  • RDMA Remote Direct Memory Access
  • RDMA performs DMA transfer of data from the memory of a local computer to the memory of a different remote computer (direct data transfer between peripheral devices, main memory (RAM), etc. without CPU intervention). Therefore, since RDMA does not require CPU processing for data transfer, it is possible to avoid the aforementioned bottleneck on the receiving side.
  • Non-Patent Document 1 A remote transfer technology using this RDMA has been proposed (see, for example, Non-Patent Document 1).
  • Non-Patent Document 1 in order to transfer data by RDMA in a wide area communication network, it is necessary to set a communication path for each flow in advance. Therefore, collecting data from many data sources requires a large amount of network resources.
  • the present disclosure aims to provide a system that does not require a large amount of network resources even when collecting data from many data sources.
  • the systems and methods of the present disclosure include: A system for collecting data from multiple data sources on a server and a method performed by the system, comprising: a network device for transferring data from the plurality of data sources to the server is determined for each data source; When data to be transmitted to the server is generated, each of the plurality of data sources transmits a communication path connection request to a network device determined in the own device.
  • the data source apparatus and method of the present disclosure are A method executed by the data source device and the data source provided in a system that collects data from a plurality of data source devices on a server, the data source device When data to be transmitted to the server is generated, a communication path connection request is transmitted to the network device determined in the self-device.
  • Devices such as the controller and data source of the present disclosure can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided through a communication network.
  • the program of the present disclosure is a program for realizing a computer as each functional unit provided in the apparatus according to the present disclosure, and is a program for causing the computer to execute each step included in the method executed by the apparatus according to the present disclosure. .
  • 1 shows a system configuration example of the present disclosure
  • 1 shows a configuration example of a communication network
  • a configuration example of a server is shown.
  • a configuration example of a data source is shown.
  • An example of information stored in the requirement table of each data source is shown.
  • 4 shows a configuration example of a transmission control controller; It is an example of a transmission policy decision sequence in the present disclosure.
  • An example of the operation in the transmission policy determination function is shown.
  • 4 shows an example of information stored in a transmission policy table;
  • An example of the Attribute ID area is shown.
  • An example of a sequence for creating and releasing a communication path is shown.
  • An example of a sequence for creating and releasing a communication path is shown.
  • 4 shows an example of transmission of sensing data from data source B to the server.
  • 4 shows an example of transmission of sensing data from data source A to the server.
  • An example of transmission of sensing data from data source C to the server is shown.
  • Fig. 1 shows a system configuration example of the present disclosure.
  • the system of the present disclosure comprises multiple data sources 10 , a transmission controller 20 and a server 40 .
  • a plurality of data sources 10 , transmission controllers 20 and servers 40 are connected by a communication network 80 .
  • a data source 10 is a terminal having user-side sensing data.
  • the server 40 is a terminal that collects data from data sources.
  • the data source 10, transmission controller 20, and server 40 of the present disclosure can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided through a communication network.
  • FIG. 2 shows a configuration example of the communication network 80.
  • a communication network 80 is composed of a plurality of network devices 81 .
  • a network device 81 for transferring data from the data source 10 to the server 40 is determined for each data source 10 .
  • the data source 10A and server 40 are connected by network devices 81A and 81B
  • the data source 10B and server 40 are connected by network devices 81A and 81C
  • the data source 10C and server 40 are connected by network devices 81D and 81E.
  • each of the network devices 81A-81E When each of the network devices 81A-81E receives data addressed to the server 40 from the data sources 10A-10C, it knows to which network device it should be transferred. Therefore, even if the data sources 10A to 10C do not know which network device 81 to use, if they specify the server 40 and send data, the data will be sent to the server 40 . Thus, the present disclosure can transfer data losslessly and broadband when a communication path is being created.
  • This disclosure proposes a method of allocating lossless and broadband communication paths to required data sources 10 at required timings in order to realize data transfer by RDMA.
  • each of the plurality of data sources 10 when data to be transmitted to the server 40 is generated, transmits the network device 81 determined in the device at the transmission timing determined in the transmission policy of the device itself. to generate a communication path.
  • each data source 10 can autonomously transmit sensing data to the server 40 based on its own transmission policy.
  • Transmission policies can be exemplified by the following, for example.
  • First transmission policy Immediately after generation of data, a communication path is generated and data is transferred, and immediately after completion of data transfer, the communication path is released.
  • Second transmission policy After a certain amount of data is accumulated, a communication path is generated and data is transferred, and the communication path is released immediately after the completion of data transfer.
  • Third transmission policy A communication path is generated immediately after data is generated, data is transferred, and the communication path is maintained for a certain period of time after data transfer is completed.
  • Fourth transmission policy After a certain amount of data is accumulated, a communication path is generated and data is transferred, and the communication path is maintained for a certain period of time even after the data transfer is completed.
  • a transmission policy that meets the data transfer requirements of the data source 10 is distributed. Then, each data source 10 autonomously transmits sensing data according to a transmission policy that considers sensor characteristics and data transfer requirements for each application. As a result, the present embodiment controls the trade-off between immediacy of data transmission and shortening of communication path usage time.
  • the data source 10 directly transmits communication path connection requests to the network devices 81A to 81E.
  • the network devices 81A to 81E By reflecting the settings received by the network devices 81A to 81E, it is possible to save time and effort until the communication paths are generated. Thereby, the present disclosure can set up a communication path in a shorter time. A detailed description will be given below.
  • FIG. 3 shows a configuration example of the server 40.
  • the server 40 has a data reception function 41 , a memory 42 and an application 43 .
  • the data reception function 41 receives sensing data from each data source 10 .
  • Memory 42 stores sensing data from sensor 50 .
  • Application 43 collects sensing data from sensor 50 .
  • the application 43 is any application that collects any sensing data detected or generated by a user terminal, sensor, in-vehicle system, or the like.
  • FIG. 4 shows a configuration example of the data source 10.
  • the data source 10 includes a requirement notification function 11, a transmission policy reception function 12, a data transmission timing control function 13, a communication path setting function 14, a data transmission function 15, a communication path release function 16, a generated data storage function 17, a requirement table 18, A transmission policy table 19 is provided.
  • the generated data storage function 17 stores sensing data from the sensor 50 .
  • the requirement notification function 11 reads data transfer requirements from the requirement table 18 and notifies the transmission controller 20 of the read data transfer requirements.
  • the transmission policy reception function 12 receives transmission policies from the transmission control controller 20 .
  • Data transmission timing control function 13 controls communication path setting function 14 , data transmission function 15 and communication path release function 16 according to transmission policy table 19 .
  • the communication path setting function 14 transmits a connection request for creating a communication path with the server 40 to the network device 81 .
  • the data transmission function 15 transmits sensing data stored in the generated data storage function 17 to the server 40 .
  • the communication path release function 16 transmits a release request for releasing the communication path with the server 40 to the network device 81 .
  • the requirement table 18 stores data transfer requirements for each data source 10 .
  • the transmission policy table 19 stores policies for transmitting sensing data from the data source 10 to the server 40 .
  • FIG. 5 shows an example of information stored in the requirement table 18 of each data source.
  • the permissible delay time is the permissible delay time from when data is generated until it reaches the server.
  • the amount of data generated is the amount of data generated in the sensor 50 at one time.
  • FIG. 6 shows a configuration example of the transmission controller 20.
  • the transmission controller 20 has a requirement reception function 21 , a transmission policy determination function 22 , a transmission policy delivery function 23 and a transmission policy determination rule 24 .
  • FIG. 7 shows an example of the operation of the transmission controller 20.
  • Each data source 10 notifies the transmission controller 20 of data transfer requirements based on the information in the requirement table 18 (S101).
  • the data transfer requirements include the allowable delay time and data generation frequency of each data source 10, as shown in FIG.
  • a requirement reception function 21 of the transmission control controller 20 receives data transfer requirements from the data source 10 .
  • the transmission policy determination function 22 determines the transmission policy for each data source 10 according to the data transfer requirements according to the transmission policy determination rule 24 (S102).
  • the transmission policy distribution function 23 of the transmission controller 20 distributes the determined transmission policy to each data source 10 (S103).
  • FIG. 8 shows an example of the operation of the transmission policy determination function 22.
  • the transmission controller 20 acquires the data transfer requirements from the data source 10 (S11), it determines the allowable delay time requirements (S12). If the allowable delay time requirement is 100 ms or less (Yes in S12), a method of generating and transmitting a path immediately after data generation is determined (S13). On the other hand, if the allowable delay time requirement is more than 100 ms (No in S12), a method of storing a certain amount of sensing data and transmitting it is determined (S14). Next, the transmission controller 20 determines the data generation frequency (S15).
  • the method of releasing the path immediately after data transmission is determined (S16). On the other hand, if the data generation frequency is more than 4 times/s (No in S15), the method of waiting for a certain period of time after completion of data transmission and releasing the path is determined (S17).
  • the transmission policy determination function 22 determines as follows. ⁇ Data source A: Since the allowable delay time is set to 1000 ms and the data generation frequency is set to 4, the transmission controller 20 determines the second transmission policy as the transmission policy. ⁇ Data source B: Since the allowable delay time is set to 200 ms and the data generation frequency is set to 10 times, the transmission controller 20 determines the fourth transmission policy as the transmission policy. ⁇ Data source C: Since the set time of the allowable delay time is 100 ms and the set value of the data generation frequency is 5 times, the transmission controller 20 determines the third transmission policy as the transmission policy. As a result, transmission policies as shown in FIG. 9 are given to data sources A to C. FIG.
  • the data transfer requirements may include application information.
  • the transmission controller 20 in steps S12 and S15, sets the threshold considering the requirements contained in the application information.
  • the data source 10 When the data source 10 receives the transmission policy from the transmission controller 20, it stores it in the transmission policy table 19. As a result, the transmission policy suitable for each data source 10 is stored in the transmission policy table 19 of each data source 10, as shown in FIG.
  • the data source 10 transmits a communication path connection request to the network device 81 when sensing data is generated.
  • the received device 81 reflects the setting. For example, when the data source 10A transmits sensing data, the data source 10A transmits a communication path connection request to the network device 81B. The network device 81B then creates a communication path with the data source 10A.
  • the connection destination of the sensing data communication path is set in advance.
  • predetermined network devices 81B and 81A connecting between data source 10A and server 40 create communication paths between data source 10A and server 40.
  • the communication path can use any means capable of transmitting sensing data, and may be virtual such as VLAN or physical such as optical path.
  • Data in any format readable by the network device 81 can be used for the communication path connection request.
  • RDMA Remote Direct Memory Access
  • Fig. 10 shows an example of the Attribute ID area.
  • RoCE RDMA over Converged Ethernet
  • UDP User Datagram Protocol
  • the network device 81 can identify the negotiation based on the description of the Attribute ID field in the MAD Header.
  • the MAD Header is stored in the DATH Header in the Base Transport Header.
  • Attribute ID is determined for each negotiation. For example, if Attribute ID is 0x0010, it can be used as a trigger for path generation in network device 81B.
  • Fig. 11 shows an example of a sequence for creating and releasing a communication path.
  • the data source 10A When using RDMA, the data source 10A generates a communication path to the server 40 with ConnectRequest as a trigger. At this time, the network device 81B transfers the ConnectRequest to the next network device 81A. The network device 81A also transfers the ConnectRequest to the server 40 after completing the generation of the communication path.
  • the server 40 uses the generated communication path to send ConnectReply to the data source 10A.
  • the data source 10A transmits ReadyToUse to the server 40 upon receiving the ConnectReply from the server 40 . This enables RDMA communication from the data source 10A to the server 40.
  • FIG. 11 shows an example of a sequence for creating and releasing a communication path.
  • the data source 10A releases the communication path to the server 40 with the Disconnect Request as a trigger.
  • the network device 81B transfers the Disconnect Request to the network device 81A.
  • the server 40 receives the Disconnect Request, it sends a Disconnect Reply to the data source 10A.
  • the timing for transferring the ConnectRequest in the network devices 81B and 81A is, for example, after the completion of the generation of the communication path.
  • the present disclosure is not so limited.
  • the network devices 81B and 81A may transfer the ConnectRequest without waiting for the completion of communication path generation.
  • Fig. 12 shows an example of a sequence for creating and releasing a communication path.
  • the network devices 81B and 81A forward the ConnectRequest without waiting for the completion of communication path generation.
  • the network devices 81B and 81A have a function of transmitting a path setting completion notification to the data source 10A, which is the source of the ConnectRequest.
  • the data source 10A since the transmission route of the sensing data is determined in advance, the data source 10A counts the number of path setting completion notifications transmitted from the network devices 81B and 81A so that all the network devices 81B on the transmission route and 81A, it can be confirmed that the setting of the communication path has been completed. After this confirmation, the data source 10A transmits ReadyToUse to the server 40 . This enables RDMA communication from the data source 10A to the server 40.
  • the data source 10A When releasing the communication path, the data source 10A sends a Disconnect Request to the server 40. Server 40 releases the communication path and sends a DisconnectReply to data source 10A. Since the communication paths are released in the server 40, the communication paths are also released in the network devices 81A and 81B.
  • FIG. 13 shows an example of transmission of sensing data from the data source 10B to the server 40.
  • the data source 10B transmits sensing data according to the fourth transmission policy.
  • the data source 10B accumulates the sensing data generated by the sensor 50, and when the data reaches 20 MB, it creates a communication path with the server 40 (S202).
  • the data source 10B transmits sensing data to the server 40 (S204-1, S204-2).
  • the data source 10B waits for the next 50 ms before transmitting a communication path release request.
  • the sensing data is generated during that time, the sensing data is transmitted each time (S204-3).
  • the data source 10B releases the communication path (S205) when 50 ms have passed since the last data transmission (step S204-3).
  • FIG. 14 shows an example of transmission of sensing data from the data source 10A to the server 40.
  • the data source 10A transmits sensing data according to the second transmission policy.
  • the data source 10A accumulates sensing data generated by the sensor 50, and when the data reaches 15 MB, it creates a communication path with the server 40 (S302).
  • the data source 10A collectively transmits the accumulated sensing data to the server 40 (S304-1, S304-2, S304-3).
  • the data source 10A releases the communication path (S305).
  • FIG. 15 shows an example of transmission of sensing data from the data source 10C to the server 40.
  • the data source 10C transmits sensing data according to the third transmission policy.
  • the data source 10C creates a communication path with the server 40 (S402).
  • the data source 10C transmits sensing data to the server 40 (S404-1), and then waits for transmission of a communication path release request for 20 ms.
  • the sensing data is transmitted each time (S404-2, S404-3).
  • the data source 10C releases the communication path (S405) when 20 ms have passed since the last data transmission (step S404-3).
  • this embodiment prevents exhaustion of network resources and realizes RDMA communication with a large amount of data sources by time-divisionally allocating communication paths at necessary timings. Since a communication path is allocated to the data source 10 to which sensing data is to be transmitted only for the required period, the utilization rate of the path can be improved and network resources can be reduced.
  • the present disclosure determines a transmission policy for each data source 10 and generates communication paths for each data source 10 according to the transmission policy, so communication paths can be allocated in a time division manner at required timings. . For this reason, the present disclosure shortens the communication path utilization time from each data source 10 to the server 40, facilitates reuse of the communication path, and reduces the trade-off between data transmission immediacy and communication path utilization time reduction. It can be controlled to reduce the number of required communication paths for the communication network 80 as a whole.
  • the present disclosure can realize a lossless and broadband communication network 80 with communication paths, and enable RDMA communication with multiple data sources without requiring a large amount of network resources. Furthermore, the present disclosure can prevent data loss in the communication network 80, so that data transfer using reliable RDMA can be realized.
  • the data collected by the server 40 is sensing data
  • the present disclosure can be applied to any data that is required to be collected, such as user terminals, sensors, and in-vehicle systems.
  • This disclosure can be applied to the information and communications industry.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The purpose of this disclosure is to provide a system that does not require a large amount of network resources even when collecting data from a large number of data sources.　This disclosure provides a system for collecting, in a server, data from multiple data sources, wherein the respective data sources transmit a data transfer requirement to a controller, the controller determines a transmission policy for each data source on the basis of the data transfer requirement, a data source autonomously transmits a communication path connection request on the basis of the transmission policy, the controller generates a communication path on the basis of the communication path connection request from the data source, and the data source transmits data using the generated communication path.

Description

データを収集するシステム、方法及びプログラムSystems, methods and programs for collecting data
　本開示は、データ収集のための通信制御に関する。 This disclosure relates to communication control for data collection.
　ユーザ端末やセンサ、車載システムが発展しており、センサの数や各センサから生成されるデータ量が大幅に増している。それらデータを収集する際に従来の通信方法では、受信側の通信の処理がボトルネックとなる可能性がある。 With the development of user terminals, sensors, and in-vehicle systems, the number of sensors and the amount of data generated from each sensor has increased significantly. When collecting such data, in the conventional communication method, communication processing on the receiving side may become a bottleneck.
　高速なデータ転送手法として、ＲＤＭＡ（Ｒｅｍｏｔｅ　Ｄｉｒｅｃｔ　Ｍｅｍｏｒｙ　Ａｃｃｅｓｓ）が検討されている。ＲＤＭＡでは、ローカルのコンピュータのメモリから、異なるリモートのコンピュータのメモリへ、データのＤＭＡ転送（ＣＰＵを介さずに周辺機器やメインメモリ（ＲＡＭ）などの間で直接データ転送）を行う。このため、ＲＤＭＡは、データ転送にＣＰＵ処理を必要としないため、受信側での前記ボトルネックを回避することができる。 RDMA (Remote Direct Memory Access) is being considered as a high-speed data transfer method. RDMA performs DMA transfer of data from the memory of a local computer to the memory of a different remote computer (direct data transfer between peripheral devices, main memory (RAM), etc. without CPU intervention). Therefore, since RDMA does not require CPU processing for data transfer, it is possible to avoid the aforementioned bottleneck on the receiving side.
　このＲＤＭＡを用いた遠隔転送技術が提案されている（例えば、非特許文献１参照。）。しかし、非特許文献１では、広域な通信ネットワークにおいてＲＤＭＡでデータ転送するには、あらかじめフロー毎に通信パスを設定する必要がある。そのため、多数のデータソースからデータを収集する場合、大量のネットワークリソースが必要となる。 A remote transfer technology using this RDMA has been proposed (see, for example, Non-Patent Document 1). However, according to Non-Patent Document 1, in order to transfer data by RDMA in a wide area communication network, it is necessary to set a communication path for each flow in advance. Therefore, collecting data from many data sources requires a large amount of network resources.
　本開示は、多数のデータソースからデータを収集する場合であっても、大量のネットワークリソースが必要とならないシステムの提供を目的とする。 The present disclosure aims to provide a system that does not require a large amount of network resources even when collecting data from many data sources.
　本開示のシステム及び方法は、
　複数のデータソースからのデータをサーバに収集するシステム及び当該システムが実行する方法であって、
　前記複数のデータソースから前記サーバにデータを転送するネットワーク機器が、データソースごとに定められており、
　前記複数のデータソースは、それぞれ、前記サーバに送信すべきデータが発生すると、自装置に定められているネットワーク機器に対して通信パスの接続要求を送信する。 The systems and methods of the present disclosure include:
A system for collecting data from multiple data sources on a server and a method performed by the system, comprising:
a network device for transferring data from the plurality of data sources to the server is determined for each data source;
When data to be transmitted to the server is generated, each of the plurality of data sources transmits a communication path connection request to a network device determined in the own device.
　本開示のデータソース装置及び方法は、
　複数のデータソース装置からのデータをサーバに収集するシステムに備わる前記データソース装置及び当該データソースが実行する方法であって、
　前記データソース装置が、
　前記サーバに送信すべきデータが発生すると、自装置に定められている前記ネットワーク機器に対して通信パスの接続要求を送信する。 The data source apparatus and method of the present disclosure are
A method executed by the data source device and the data source provided in a system that collects data from a plurality of data source devices on a server,
the data source device
When data to be transmitted to the server is generated, a communication path connection request is transmitted to the network device determined in the self-device.
　本開示のコントローラ及びデータソースなどの装置はコンピュータとプログラムによっても実現でき、プログラムを記録媒体に記録することも、通信ネットワークを通して提供することも可能である。本開示のプログラムは、本開示に係る装置に備わる各機能部としてコンピュータを実現させるためのプログラムであり、本開示に係る装置が実行する方法に備わる各ステップをコンピュータに実行させるためのプログラムである。 Devices such as the controller and data source of the present disclosure can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided through a communication network. The program of the present disclosure is a program for realizing a computer as each functional unit provided in the apparatus according to the present disclosure, and is a program for causing the computer to execute each step included in the method executed by the apparatus according to the present disclosure. .
　本開示によれば、多数のデータソースからデータを収集する場合であっても、大量のネットワークリソースが必要とならないシステムを提供することができる。 According to the present disclosure, it is possible to provide a system that does not require a large amount of network resources even when collecting data from many data sources.
本開示のシステム構成例を示す。1 shows a system configuration example of the present disclosure; 通信ネットワークの構成例を示す。1 shows a configuration example of a communication network; サーバの構成例を示す。A configuration example of a server is shown. データソースの構成例を示す。A configuration example of a data source is shown. 各データソースの要件テーブルに格納されている情報の一例を示す。An example of information stored in the requirement table of each data source is shown. 送信制御コントローラの構成例を示す。4 shows a configuration example of a transmission control controller; 本開示における送信ポリシー決定シーケンスの一例である。It is an example of a transmission policy decision sequence in the present disclosure. 送信ポリシー決定機能における動作の一例を示す。An example of the operation in the transmission policy determination function is shown. 送信ポリシーテーブルに格納される情報の一例を示す。4 shows an example of information stored in a transmission policy table; Ａｔｔｒｉｂｕｔｅ　ＩＤ領域の一例を示す。An example of the Attribute ID area is shown. 通信パスを生成及び解放する際のシーケンスの一例を示す。An example of a sequence for creating and releasing a communication path is shown. 通信パスを生成及び解放する際のシーケンスの一例を示す。An example of a sequence for creating and releasing a communication path is shown. データソースＢからサーバへのセンシングデータの送信例を示す。4 shows an example of transmission of sensing data from data source B to the server. データソースＡからサーバへのセンシングデータの送信例を示す。4 shows an example of transmission of sensing data from data source A to the server. データソースＣからサーバへのセンシングデータの送信例を示す。An example of transmission of sensing data from data source C to the server is shown.
　以下、本開示の実施形態について、図面を参照しながら詳細に説明する。なお、本開示は、以下に示す実施形態に限定されるものではない。これらの実施の例は例示に過ぎず、本開示は当業者の知識に基づいて種々の変更、改良を施した形態で実施することができる。なお、本明細書及び図面において符号が同じ構成要素は、相互に同一のものを示すものとする。 Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that the present disclosure is not limited to the embodiments shown below. These implementation examples are merely illustrative, and the present disclosure can be implemented in various modified and improved forms based on the knowledge of those skilled in the art. In addition, in this specification and the drawings, constituent elements having the same reference numerals are the same as each other.
　図１に、本開示のシステム構成例を示す。本開示のシステムは、複数のデータソース１０、送信制御コントローラ２０、及びサーバ４０を備える。複数のデータソース１０、送信制御コントローラ２０、及びサーバ４０は、通信ネットワーク８０で接続されている。データソース１０は、ユーザ側のセンシングデータを持つ端末である。サーバ４０は、データソースからのデータを収集する端末である。 Fig. 1 shows a system configuration example of the present disclosure. The system of the present disclosure comprises multiple data sources 10 , a transmission controller 20 and a server 40 . A plurality of data sources 10 , transmission controllers 20 and servers 40 are connected by a communication network 80 . A data source 10 is a terminal having user-side sensing data. The server 40 is a terminal that collects data from data sources.
　本開示のデータソース１０、送信制御コントローラ２０、及びサーバ４０は、コンピュータとプログラムによっても実現でき、プログラムを記録媒体に記録することも、通信ネットワークを通して提供することも可能である。 The data source 10, transmission controller 20, and server 40 of the present disclosure can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided through a communication network.
　図２に、通信ネットワーク８０の構成例を示す。通信ネットワーク８０は、複数のネットワーク機器８１で構成されている。本実施形態では、データソース１０からサーバ４０にデータを転送するネットワーク機器８１が、データソース１０ごとに定められている。例えば、データソース１０Ａとサーバ４０がネットワーク機器８１Ａ及び８１Ｂで接続され、データソース１０Ｂとサーバ４０がネットワーク機器８１Ａ及び８１Ｃで接続され、データソース１０Ｃとサーバ４０がネットワーク機器８１Ｄ及び８１Ｅで接続されている。 FIG. 2 shows a configuration example of the communication network 80. A communication network 80 is composed of a plurality of network devices 81 . In this embodiment, a network device 81 for transferring data from the data source 10 to the server 40 is determined for each data source 10 . For example, the data source 10A and server 40 are connected by network devices 81A and 81B, the data source 10B and server 40 are connected by network devices 81A and 81C, and the data source 10C and server 40 are connected by network devices 81D and 81E. there is
　各ネットワーク機器８１Ａ～８１Ｅは、データソース１０Ａ～１０Ｃからサーバ４０宛のデータを受信すると、どのネットワーク機器へ転送したらよいか知っている。そのため、データソース１０Ａ～１０Ｃは、どのネットワーク機器８１を利用するかをわからなくても、サーバ４０を指定してデータ送信すれば、データはサーバ４０へ送られる。これより、本開示は、通信パスが生成されているときは、ロスレスかつ広帯域でデータを転送することができる。 When each of the network devices 81A-81E receives data addressed to the server 40 from the data sources 10A-10C, it knows to which network device it should be transferred. Therefore, even if the data sources 10A to 10C do not know which network device 81 to use, if they specify the server 40 and send data, the data will be sent to the server 40 . Thus, the present disclosure can transfer data losslessly and broadband when a communication path is being created.
　本開示では、ＲＤＭＡによるデータ転送を実現するため、ロスレスかつ広帯域な通信パスを、必要なデータソース１０に必要なタイミングで割り当てる方式を提案する。本開示のシステムでは、複数のデータソース１０は、それぞれ、サーバ４０に送信すべきデータが発生すると、自装置の送信ポリシーで定められた送信タイミングに、自装置に定められているネットワーク機器８１を用いて通信パスを生成する。これにより、各データソース１０は、自装置の送信ポリシーに基づいて、自律的に、センシングデータをサーバ４０へ送信することができる。 This disclosure proposes a method of allocating lossless and broadband communication paths to required data sources 10 at required timings in order to realize data transfer by RDMA. In the system of the present disclosure, each of the plurality of data sources 10, when data to be transmitted to the server 40 is generated, transmits the network device 81 determined in the device at the transmission timing determined in the transmission policy of the device itself. to generate a communication path. Thereby, each data source 10 can autonomously transmit sensing data to the server 40 based on its own transmission policy.
　送信ポリシーは、例えば、以下が例示できる。
　第１の送信ポリシー：データ発生後即座に通信パスを生成してデータ転送を行い、データ転送完了後即座に通信パスを解放する。
　第２の送信ポリシー：データが一定量蓄積してから通信パスを生成してデータ転送を行い、データ転送完了後即座に通信パスを解放する。
　第３の送信ポリシー：データ発生後即座に通信パスを生成してデータ転送を行い、データ転送完了後も一定時間通信パスを保持し続ける。
　第４の送信ポリシー：データが一定量蓄積してから通信パスを生成してデータ転送を行い、データ転送完了後も一定時間通信パスを保持し続ける。 Transmission policies can be exemplified by the following, for example.
First transmission policy: Immediately after generation of data, a communication path is generated and data is transferred, and immediately after completion of data transfer, the communication path is released.
Second transmission policy: After a certain amount of data is accumulated, a communication path is generated and data is transferred, and the communication path is released immediately after the completion of data transfer.
Third transmission policy: A communication path is generated immediately after data is generated, data is transferred, and the communication path is maintained for a certain period of time after data transfer is completed.
Fourth transmission policy: After a certain amount of data is accumulated, a communication path is generated and data is transferred, and the communication path is maintained for a certain period of time even after the data transfer is completed.
　本実施形態では、送信制御コントローラ２０を備えることで、データソース１０のデータ転送要件に合った送信ポリシーを配布する。そして、センサ特性及びアプリ毎のデータ転送要件を考慮した送信ポリシーに従って、各データソース１０が自律的にセンシングデータを送信する。これにより、本実施形態は、データ送信の即時性と通信パス利用時間短縮のトレードオフを制御する。 In this embodiment, by providing the transmission controller 20, a transmission policy that meets the data transfer requirements of the data source 10 is distributed. Then, each data source 10 autonomously transmits sensing data according to a transmission policy that considers sensor characteristics and data transfer requirements for each application. As a result, the present embodiment controls the trade-off between immediacy of data transmission and shortening of communication path usage time.
　ここで、パスの生成についてもコントローラで一括制御すると、パス生成が大量にリクエストされた場合、コントローラの負荷が高くなり、通信パス生成ができなくなる、または、生成に通常よりも時間がかかる可能性がある。そこで、本開示では、データソース１０は、直接、ネットワーク機器８１Ａ～８１Ｅへ通信パスの接続要求を送信する。ネットワーク機器８１Ａ～８１Ｅが受け取った設定を反映することで、通信パスを生成するまでの手間を省略することができる。これにより、本開示は、より短時間で通信パスの設定することができる。以下、詳細に説明する。 Here, if the path generation is also collectively controlled by the controller, if a large number of path generation requests are received, the load on the controller will increase and communication path generation may not be possible or generation may take longer than usual. There is Therefore, in the present disclosure, the data source 10 directly transmits communication path connection requests to the network devices 81A to 81E. By reflecting the settings received by the network devices 81A to 81E, it is possible to save time and effort until the communication paths are generated. Thereby, the present disclosure can set up a communication path in a shorter time. A detailed description will be given below.
　図３に、サーバ４０の構成例を示す。サーバ４０は、データ受信機能４１、メモリ４２、アプリケーション４３を備える。
　データ受信機能４１は、各データソース１０からセンシングデータを受信する。
　メモリ４２は、センサ５０からのセンシングデータを格納する。
　アプリケーション４３は、センサ５０からのセンシングデータを収集する。アプリケーション４３は、ユーザ端末やセンサ、車載システムなどで検出又は発生した任意のセンシングデータを収集する任意のアプリケーションである。 FIG. 3 shows a configuration example of the server 40. As shown in FIG. The server 40 has a data reception function 41 , a memory 42 and an application 43 .
The data reception function 41 receives sensing data from each data source 10 .
Memory 42 stores sensing data from sensor 50 .
Application 43 collects sensing data from sensor 50 . The application 43 is any application that collects any sensing data detected or generated by a user terminal, sensor, in-vehicle system, or the like.
　図４に、データソース１０の構成例を示す。データソース１０は、要件通知機能１１、送信ポリシー受信機能１２、データ送信タイミング制御機能１３、通信パス設定機能１４、データ送信機能１５、通信パス解放機能１６、発生データ格納機能１７、要件テーブル１８、送信ポリシーテーブル１９を備える。 FIG. 4 shows a configuration example of the data source 10. The data source 10 includes a requirement notification function 11, a transmission policy reception function 12, a data transmission timing control function 13, a communication path setting function 14, a data transmission function 15, a communication path release function 16, a generated data storage function 17, a requirement table 18, A transmission policy table 19 is provided.
　発生データ格納機能１７は、センサ５０からのセンシングデータを格納する。
　要件通知機能１１は、要件テーブル１８からデータ転送要件を読み出し、読み出したデータ転送要件を送信制御コントローラ２０に通知する。
　送信ポリシー受信機能１２は、送信制御コントローラ２０から送信ポリシーを受信する。
　データ送信タイミング制御機能１３は、送信ポリシーテーブル１９に従い、通信パス設定機能１４、データ送信機能１５及び通信パス解放機能１６を制御する。
　通信パス設定機能１４は、サーバ４０との通信パスを生成するための接続要求をネットワーク機器８１に送信する。
　データ送信機能１５は、発生データ格納機能１７に格納されているセンシングデータを、サーバ４０に送信する。
　通信パス解放機能１６は、サーバ４０との通信パスを解放するための解放要求をネットワーク機器８１に送信する。
　要件テーブル１８は、データソース１０ごとのデータ転送要件を格納する。
　送信ポリシーテーブル１９は、データソース１０からサーバ４０へセンシングデータを送信する際のポリシーを格納する。 The generated data storage function 17 stores sensing data from the sensor 50 .
The requirement notification function 11 reads data transfer requirements from the requirement table 18 and notifies the transmission controller 20 of the read data transfer requirements.
The transmission policy reception function 12 receives transmission policies from the transmission control controller 20 .
Data transmission timing control function 13 controls communication path setting function 14 , data transmission function 15 and communication path release function 16 according to transmission policy table 19 .
The communication path setting function 14 transmits a connection request for creating a communication path with the server 40 to the network device 81 .
The data transmission function 15 transmits sensing data stored in the generated data storage function 17 to the server 40 .
The communication path release function 16 transmits a release request for releasing the communication path with the server 40 to the network device 81 .
The requirement table 18 stores data transfer requirements for each data source 10 .
The transmission policy table 19 stores policies for transmitting sensing data from the data source 10 to the server 40 .
　図５に、各データソースの要件テーブル１８に格納されている情報の一例を示す。要件テーブルには、データ転送要件として、各データソース１０の許容遅延時間、データ発生頻度、データ発生量が、アプリケーションに紐づけて格納されている。許容遅延時間は、データが発生してから前記サーバに到達するまでの許容遅延時間である。データ発生量は、センサ５０において一度に発生するデータ量である。 FIG. 5 shows an example of information stored in the requirement table 18 of each data source. In the requirement table, as data transfer requirements, the permissible delay time, data generation frequency, and data generation amount of each data source 10 are stored in association with the application. The permissible delay time is the permissible delay time from when data is generated until it reaches the server. The amount of data generated is the amount of data generated in the sensor 50 at one time.
　図６に、送信制御コントローラ２０の構成例を示す。送信制御コントローラ２０は、要件受信機能２１、送信ポリシー決定機能２２、送信ポリシー配信機能２３、送信ポリシー決定ルール２４を備える。 FIG. 6 shows a configuration example of the transmission controller 20. As shown in FIG. The transmission controller 20 has a requirement reception function 21 , a transmission policy determination function 22 , a transmission policy delivery function 23 and a transmission policy determination rule 24 .
　図７に、送信制御コントローラ２０における動作の一例を示す。
　各データソース１０が、要件テーブル１８の情報に基づいて、送信制御コントローラ２０に、データ転送要件を通知する（Ｓ１０１）。データ転送要件には、図５に示すような、各データソース１０の許容遅延時間及びデータ発生頻度が含まれる。
　送信制御コントローラ２０の要件受信機能２１は、データソース１０からのデータ転送要件を受信する。送信ポリシー決定機能２２は、送信ポリシー決定ルール２４に従い、データ転送要件に応じてデータソース１０ごとに送信ポリシーを決定する（Ｓ１０２）。
　送信制御コントローラ２０の送信ポリシー配信機能２３は、決定した送信ポリシーを、各データソース１０に配信する（Ｓ１０３）。 FIG. 7 shows an example of the operation of the transmission controller 20. As shown in FIG.
Each data source 10 notifies the transmission controller 20 of data transfer requirements based on the information in the requirement table 18 (S101). The data transfer requirements include the allowable delay time and data generation frequency of each data source 10, as shown in FIG.
A requirement reception function 21 of the transmission control controller 20 receives data transfer requirements from the data source 10 . The transmission policy determination function 22 determines the transmission policy for each data source 10 according to the data transfer requirements according to the transmission policy determination rule 24 (S102).
The transmission policy distribution function 23 of the transmission controller 20 distributes the determined transmission policy to each data source 10 (S103).
　図８に、送信ポリシー決定機能２２における動作の一例を示す。
　送信制御コントローラ２０は、データソース１０からデータ転送要件を取得すると（Ｓ１１）、許容遅延時間の要件を判定する（Ｓ１２）。許容遅延時間の要件が１００ｍｓ以下である場合（Ｓ１２においてＹｅｓ）、データ発生後即座にパスを生成し、送信する方式に決定する（Ｓ１３）。一方、許容遅延時間の要件が１００ｍｓ超である場合（Ｓ１２においてＮｏ）、センシングデータを一定量溜めて送信する方式に決定する（Ｓ１４）。
　次に、送信制御コントローラ２０は、データ発生頻度を判定する（Ｓ１５）。データ発生頻度が４回／ｓ以下である場合（Ｓ１５においてＹｅｓ）、データ送信後即座にパス解放する方式に決定する（Ｓ１６）。一方、データ発生頻度が４回／ｓ超である場合（Ｓ１５においてＮｏ）、データ送信完了後一定時間待機してパス解放する方式に決定する（Ｓ１７）。 FIG. 8 shows an example of the operation of the transmission policy determination function 22. As shown in FIG.
When the transmission controller 20 acquires the data transfer requirements from the data source 10 (S11), it determines the allowable delay time requirements (S12). If the allowable delay time requirement is 100 ms or less (Yes in S12), a method of generating and transmitting a path immediately after data generation is determined (S13). On the other hand, if the allowable delay time requirement is more than 100 ms (No in S12), a method of storing a certain amount of sensing data and transmitting it is determined (S14).
Next, the transmission controller 20 determines the data generation frequency (S15). If the data generation frequency is 4 times/s or less (Yes in S15), the method of releasing the path immediately after data transmission is determined (S16). On the other hand, if the data generation frequency is more than 4 times/s (No in S15), the method of waiting for a certain period of time after completion of data transmission and releasing the path is determined (S17).
　例えば、図５に示すデータ転送要件の場合、送信ポリシー決定機能２２は以下のように決定する。
・データソースＡ：
　許容遅延時間の設定時間が１０００ｍｓであり、データ発生頻度の設定値が４回であるため、送信制御コントローラ２０は送信ポリシーを第２の送信ポリシーに決定する。
・データソースＢ：
　許容遅延時間の設定時間が２００ｍｓであり、データ発生頻度の設定値が１０回であるため、送信制御コントローラ２０は送信ポリシーを第４の送信ポリシーに決定する。
・データソースＣ：
　許容遅延時間の設定時間が１００ｍｓであり、データ発生頻度の設定値が５回であるため、送信制御コントローラ２０は送信ポリシーを第３の送信ポリシーに決定する。
　これにより、図９に示すような送信ポリシーがデータソースＡ～Ｃに与えられる。 For example, for the data transfer requirements shown in FIG. 5, the transmission policy determination function 22 determines as follows.
・Data source A:
Since the allowable delay time is set to 1000 ms and the data generation frequency is set to 4, the transmission controller 20 determines the second transmission policy as the transmission policy.
・Data source B:
Since the allowable delay time is set to 200 ms and the data generation frequency is set to 10 times, the transmission controller 20 determines the fourth transmission policy as the transmission policy.
・Data source C:
Since the set time of the allowable delay time is 100 ms and the set value of the data generation frequency is 5 times, the transmission controller 20 determines the third transmission policy as the transmission policy.
As a result, transmission policies as shown in FIG. 9 are given to data sources A to C. FIG.
　ここで、データ転送要件は、アプリケーションの情報が含まれていてもよい。この場合、送信制御コントローラ２０は、ステップＳ１２及びＳ１５において、アプリケーションの情報に含まれる要件を考慮してしきい値を設定する。 Here, the data transfer requirements may include application information. In this case, the transmission controller 20, in steps S12 and S15, sets the threshold considering the requirements contained in the application information.
　データソース１０は、送信制御コントローラ２０から送信ポリシーを受信すると、送信ポリシーテーブル１９に格納する。これにより、図９に示すように、各データソース１０の送信ポリシーテーブル１９に、各データソース１０に適した送信ポリシーが格納される。 When the data source 10 receives the transmission policy from the transmission controller 20, it stores it in the transmission policy table 19. As a result, the transmission policy suitable for each data source 10 is stored in the transmission policy table 19 of each data source 10, as shown in FIG.
　データソース１０は、センシングデータが発生すると、ネットワーク機器８１へ通信パスの接続要求を送信する。受け取った機器８１は、設定を反映する。例えば、データソース１０Ａがセンシングデータを送信する場合、データソース１０Ａが通信パスの接続要求をネットワーク機器８１Ｂに送信する。すると、ネットワーク機器８１Ｂは、データソース１０Ａとの通信パスを生成する。 The data source 10 transmits a communication path connection request to the network device 81 when sensing data is generated. The received device 81 reflects the setting. For example, when the data source 10A transmits sensing data, the data source 10A transmits a communication path connection request to the network device 81B. The network device 81B then creates a communication path with the data source 10A.
　センシングデータの送信ルートに設定されている各ネットワーク機器８１には、予めセンシングデータの通信パスの接続先が設定されている。これにより、本開示では、データソース１０Ａとサーバ４０との間を接続する予め定められたネットワーク機器８１Ｂ及び８１Ａが、データソース１０Ａとサーバ４０の間の通信パスを生成する。通信パスは、センシングデータを伝送可能な任意の手段を用いることが可能であり、ＶＬＡＮ等の仮想的なものであってもよいし、光パス等の物理的なものであってもよい。 For each network device 81 that is set as a sensing data transmission route, the connection destination of the sensing data communication path is set in advance. Thus, in the present disclosure, predetermined network devices 81B and 81A connecting between data source 10A and server 40 create communication paths between data source 10A and server 40. FIG. The communication path can use any means capable of transmitting sensing data, and may be virtual such as VLAN or physical such as optical path.
　通信パスの接続要求は、ネットワーク機器８１で読み取り可能な任意のフォーマットのデータを用いることができる。例えば、ＲＤＭＡ（Ｒｅｍｏｔｅ　Ｄｉｒｅｃｔ　Ｍｅｍｏｒｙ　Ａｃｃｅｓｓ）のパケットのヘッダに備わるＡｔｔｒｉｂｕｔｅ　ＩＤ領域を用いることができる。 Data in any format readable by the network device 81 can be used for the communication path connection request. For example, it is possible to use the Attribute ID area provided in the RDMA (Remote Direct Memory Access) packet header.
　図１０に、Ａｔｔｒｉｂｕｔｅ　ＩＤ領域の一例を示す。ＵＤＰ（Ｕｓｅｒ　Ｄａｔａｇｒａｍ　Ｐｒｏｔｏｃｏｌ）プロトコルで用いられるＲｏＣＥ（ＲＤＭＡ　ｏｖｅｒ　Ｃｏｎｖｅｒｇｅｄ　Ｅｔｈｅｒｎｅｔ）　ｖ２を利用する場合、ネットワーク機器８１は、ＭＡＤ　Ｈｅａｄｅｒ内のＡｔｔｒｉｂｕｔｅ　ＩＤフィールドの記載に基づいて、ネゴシエーションを識別することができる。ＭＡＤ　Ｈｅａｄｅｒは、Ｂａｓｅ　Ｔｒａｎｓｐｏｒｔ　Ｈｅａｄｅｒにおける、ＤＡＴＨ　Ｈｅａｄｅｒ内に格納されている。 Fig. 10 shows an example of the Attribute ID area. When using RoCE (RDMA over Converged Ethernet) v2 used in the UDP (User Datagram Protocol) protocol, the network device 81 can identify the negotiation based on the description of the Attribute ID field in the MAD Header. The MAD Header is stored in the DATH Header in the Base Transport Header.
　ネゴシエーションは、例えば、ＲＤＭＡの接続要求を行うＣｏｎｎｅｃｔＲｅｑｕｅｓｔ、ＲＤＭＡの接続応答を示すＣｏｎｎｅｃｔＲｅｐｌｙ、使用可能な状態であることを示すＲｅａｄｙＴｏＵｓｅ、ＲＤＭＡの解放要求を行うＤｉｓｃｏｎｎｅｃｔＲｅｑｕｅｓｔ、ＲＤＭＡの解放応答を示すＤｉｓｃｏｎｎｅｃｔＲｅｐｌｙが含まれる。ネゴシエーションごとにＡｔｔｒｉｂｕｔｅ　ＩＤの値が定められており、例えば、Ａｔｔｒｉｂｕｔｅ　ＩＤが０ｘ００１０であれば、ネットワーク機器８１Ｂにおけるパス生成のトリガーとすることができる。 Negotiation includes, for example, ConnectRequest for requesting RDMA connection, ConnectReply for indicating RDMA connection response, ReadyToUse for indicating a usable state, DisconnectRequest for requesting RDMA release, and DisconnectReply for indicating RDMA release response. . The value of Attribute ID is determined for each negotiation. For example, if Attribute ID is 0x0010, it can be used as a trigger for path generation in network device 81B.
　図１１に、通信パスを生成及び解放する際のシーケンスの一例を示す。ＲＤＭＡを用いる場合、データソース１０Ａは、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔをトリガーとして、サーバ４０までの通信パスの生成を行う。このとき、ネットワーク機器８１Ｂは、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔを次のネットワーク機器８１Ａへ転送する。ネットワーク機器８１Ａも、通信パスの生成完了後、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔをサーバ４０へ転送する。サーバ４０は、生成された通信パスを用いて、ＣｏｎｎｅｃｔＲｅｐｌｙをデータソース１０Ａに送信する。データソース１０Ａは、サーバ４０からＣｏｎｎｅｃｔＲｅｐｌｙを受信すると、ＲｅａｄｙＴｏＵｓｅをサーバ４０に送信する。これにより、データソース１０Ａからサーバ４０へのＲＤＭＡ通信が可能になる。 　Fig. 11 shows an example of a sequence for creating and releasing a communication path. When using RDMA, the data source 10A generates a communication path to the server 40 with ConnectRequest as a trigger. At this time, the network device 81B transfers the ConnectRequest to the next network device 81A. The network device 81A also transfers the ConnectRequest to the server 40 after completing the generation of the communication path. The server 40 uses the generated communication path to send ConnectReply to the data source 10A. The data source 10A transmits ReadyToUse to the server 40 upon receiving the ConnectReply from the server 40 . This enables RDMA communication from the data source 10A to the server 40. FIG.
　通信パスを解放する際も、通信パスを生成する際と同様である。具体的には、データソース１０Ａは、Ｄｉｓｃｏｎｎｅｃｔ　Ｒｅｑｕｅｓｔをトリガーとして、サーバ４０までの通信パスの解放を行う。このとき、ネットワーク機器８１Ｂは、通信パスの解放が完了すると、Ｄｉｓｃｏｎｎｅｃｔ　Ｒｅｑｕｅｓｔをネットワーク機器８１Ａに転送する。ネットワーク機器８１Ａも同様である。サーバ４０は、Ｄｉｓｃｏｎｎｅｃｔ　Ｒｅｑｕｅｓｔを受信すると、ＤｉｓｃｏｎｎｅｃｔＲｅｐｌｙをデータソース１０Ａに送信する。 　When releasing a communication path, it is the same as when creating a communication path. Specifically, the data source 10A releases the communication path to the server 40 with the Disconnect Request as a trigger. At this time, when the release of the communication path is completed, the network device 81B transfers the Disconnect Request to the network device 81A. The same applies to the network device 81A. When the server 40 receives the Disconnect Request, it sends a Disconnect Reply to the data source 10A.
　ネットワーク機器８１Ｂ及び８１Ａにおいて、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔを転送するタイミングは、例えば、通信パスの生成完了後である。しかし、本開示は、これに限定されない。例えば、ネットワーク機器８１Ｂ及び８１Ａは、通信パスの生成の完了を待たずに、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔを転送してもよい。 The timing for transferring the ConnectRequest in the network devices 81B and 81A is, for example, after the completion of the generation of the communication path. However, the present disclosure is not so limited. For example, the network devices 81B and 81A may transfer the ConnectRequest without waiting for the completion of communication path generation.
　図１２に、通信パスを生成及び解放する際のシーケンスの一例を示す。この例では、ネットワーク機器８１Ｂ及び８１Ａは、通信パスの生成の完了を待たずに、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔを転送する。この場合、ネットワーク機器８１Ｂ及び８１Ａは、ＣｏｎｎｅｃｔＲｅｑｕｅｓｔの送信元であるデータソース１０Ａに、パス設定完了通知を送信する機能を備える。本開示では、センシングデータの送信ルートは予め定められているため、データソース１０Ａはネットワーク機器８１Ｂ及び８１Ａから送信されるパス設定完了通知の数をカウントすることで、送信ルートの全てのネットワーク機器８１Ｂ及び８１Ａにおいて通信パスの設定が完了したことを確認することができる。この確認ができたら、データソース１０Ａは、ＲｅａｄｙＴｏＵｓｅをサーバ４０に送信する。これにより、データソース１０Ａからサーバ４０へのＲＤＭＡ通信が可能になる。 　Fig. 12 shows an example of a sequence for creating and releasing a communication path. In this example, the network devices 81B and 81A forward the ConnectRequest without waiting for the completion of communication path generation. In this case, the network devices 81B and 81A have a function of transmitting a path setting completion notification to the data source 10A, which is the source of the ConnectRequest. In the present disclosure, since the transmission route of the sensing data is determined in advance, the data source 10A counts the number of path setting completion notifications transmitted from the network devices 81B and 81A so that all the network devices 81B on the transmission route and 81A, it can be confirmed that the setting of the communication path has been completed. After this confirmation, the data source 10A transmits ReadyToUse to the server 40 . This enables RDMA communication from the data source 10A to the server 40. FIG.
　通信パスを解放する際、データソース１０Ａは、Ｄｉｓｃｏｎｎｅｃｔ　Ｒｅｑｕｅｓｔをサーバ４０に送信する。サーバ４０は、通信パスを解放し、ＤｉｓｃｏｎｎｅｃｔＲｅｐｌｙをデータソース１０Ａに送信する。サーバ４０で通信パスが解放されるため、ネットワーク機器８１Ａ及び８１Ｂにおいても通信パスが解放される。 When releasing the communication path, the data source 10A sends a Disconnect Request to the server 40. Server 40 releases the communication path and sends a DisconnectReply to data source 10A. Since the communication paths are released in the server 40, the communication paths are also released in the network devices 81A and 81B.
　図１３に、データソース１０Ｂからサーバ４０へのセンシングデータの送信例を示す。データソース１０Ｂは、第４の送信ポリシーに従い、センシングデータを送信する。
　データソース１０Ｂは、センサ５０で発生したセンシングデータを蓄積し、データが２０ＭＢに達すると、サーバ４０との間で通信パスを生成する（Ｓ２０２）。
　データソース１０Ｂは、通信パスの生成が完了すると、サーバ４０へセンシングデータを送信する（Ｓ２０４－１、Ｓ２０４－２）。データソース１０Ｂは、サーバ４０へのセンシングデータの送信が完了すると、その後の５０ｍｓの間、通信パスの解放要求の送信を待機する。その間にセンシングデータが発生した場合、その都度センシングデータを送信する（Ｓ２０４－３）。
　データソース１０Ｂは、最後のデータ送信（ステップＳ２０４－３）から５０ｍｓが経過すると、通信パスを解放する（Ｓ２０５）。 FIG. 13 shows an example of transmission of sensing data from the data source 10B to the server 40. As shown in FIG. The data source 10B transmits sensing data according to the fourth transmission policy.
The data source 10B accumulates the sensing data generated by the sensor 50, and when the data reaches 20 MB, it creates a communication path with the server 40 (S202).
When the communication path generation is completed, the data source 10B transmits sensing data to the server 40 (S204-1, S204-2). After completing the transmission of the sensing data to the server 40, the data source 10B waits for the next 50 ms before transmitting a communication path release request. When sensing data is generated during that time, the sensing data is transmitted each time (S204-3).
The data source 10B releases the communication path (S205) when 50 ms have passed since the last data transmission (step S204-3).
　図１４に、データソース１０Ａからサーバ４０へのセンシングデータの送信例を示す。データソース１０Ａは、第２の送信ポリシーに従い、センシングデータを送信する。
　データソース１０Ａは、センサ５０で発生したセンシングデータを蓄積し、データが１５ＭＢに達すると、サーバ４０との間で通信パスを生成する（Ｓ３０２）。そして、データソース１０Ａは、通信パスの生成が完了すると、蓄積したセンシングデータをまとめてサーバ４０へ送信する（Ｓ３０４－１、Ｓ３０４－２、Ｓ３０４－３）。
　データソース１０Ａは、サーバ４０へのセンシングデータの送信が完了すると、通信パスを解放する（Ｓ３０５）。 FIG. 14 shows an example of transmission of sensing data from the data source 10A to the server 40. As shown in FIG. The data source 10A transmits sensing data according to the second transmission policy.
The data source 10A accumulates sensing data generated by the sensor 50, and when the data reaches 15 MB, it creates a communication path with the server 40 (S302). When the communication path generation is completed, the data source 10A collectively transmits the accumulated sensing data to the server 40 (S304-1, S304-2, S304-3).
When the transmission of the sensing data to the server 40 is completed, the data source 10A releases the communication path (S305).
　図１５に、データソース１０Ｃからサーバ４０へのセンシングデータの送信例を示す。データソース１０Ｃは、第３の送信ポリシーに従い、センシングデータを送信する。
　データソース１０Ｃは、センシングデータが発生すると、サーバ４０との間で通信パスを生成する（Ｓ４０２）。データソース１０Ｃは、通信パスの生成が完了すると、サーバ４０へセンシングデータを送信し（Ｓ４０４－１）、その後の２０ｍｓの間、通信パスの解放要求の送信を待機する。その間にセンシングデータが発生した場合、その都度センシングデータを送信する（Ｓ４０４－２、Ｓ４０４－３）。データソース１０Ｃは、最後のデータ送信（ステップＳ４０４－３）から２０ｍｓが経過すると、通信パスを解放する（Ｓ４０５）。 FIG. 15 shows an example of transmission of sensing data from the data source 10C to the server 40. As shown in FIG. The data source 10C transmits sensing data according to the third transmission policy.
When sensing data is generated, the data source 10C creates a communication path with the server 40 (S402). When the communication path generation is completed, the data source 10C transmits sensing data to the server 40 (S404-1), and then waits for transmission of a communication path release request for 20 ms. When sensing data is generated during that time, the sensing data is transmitted each time (S404-2, S404-3). The data source 10C releases the communication path (S405) when 20 ms have passed since the last data transmission (step S404-3).
　図１３から図１５に示すように、本実施形態は、通信パスを必要なタイミングで時分割に割り当てることで、ネットワークリソースの枯渇を防ぎ、大量のデータソースとのＲＤＭＡ通信を実現する。センシングデータを送信したいデータソース１０に必要な期間だけ通信パスを割り当てるため、パスの利用率を向上できるとともに、ネットワークリソースを削減できる。 As shown in FIGS. 13 to 15, this embodiment prevents exhaustion of network resources and realizes RDMA communication with a large amount of data sources by time-divisionally allocating communication paths at necessary timings. Since a communication path is allocated to the data source 10 to which sensing data is to be transmitted only for the required period, the utilization rate of the path can be improved and network resources can be reduced.
（本開示の効果）
　以上説明したように、本開示は、送信ポリシーをデータソース１０ごとに決定し、送信ポリシーに従って各データソース１０の通信パスを生成するため、通信パスを必要なタイミングで時分割に割り当てることができる。このため、本開示は、データ送信の即時性と通信パス利用時間短縮のトレードオフに対し、各データソース１０からサーバ４０への通信パス利用時間を短縮し、通信パスの使いまわしを容易にし、通信ネットワーク８０の全体としての通信パス必要数を削減するよう、制御することができる。 (Effect of the present disclosure)
As described above, the present disclosure determines a transmission policy for each data source 10 and generates communication paths for each data source 10 according to the transmission policy, so communication paths can be allocated in a time division manner at required timings. . For this reason, the present disclosure shortens the communication path utilization time from each data source 10 to the server 40, facilitates reuse of the communication path, and reduces the trade-off between data transmission immediacy and communication path utilization time reduction. It can be controlled to reduce the number of required communication paths for the communication network 80 as a whole.
　したがって、本開示は、ロスレスかつ広帯域な通信ネットワーク８０を通信パスで実現し、大量のネットワークリソースを要せず、多数のデータソースとのＲＤＭＡ通信を可能にすることができる。さらに、本開示は、通信ネットワーク８０でのデータのロスを防ぐことができるため、確実なＲＤＭＡを用いたデータ転送を実現することができる。 Therefore, the present disclosure can realize a lossless and broadband communication network 80 with communication paths, and enable RDMA communication with multiple data sources without requiring a large amount of network resources. Furthermore, the present disclosure can prevent data loss in the communication network 80, so that data transfer using reliable RDMA can be realized.
　なお、本実施形態では、サーバ４０の収集するデータがセンシングデータである例を示したが、ユーザ端末やセンサ、車載システムなど、本開示は収集の要求される任意のデータに適用可能である。 In this embodiment, an example in which the data collected by the server 40 is sensing data is shown, but the present disclosure can be applied to any data that is required to be collected, such as user terminals, sensors, and in-vehicle systems.
　また、上述の実施形態ではデータソース１０とサーバ４０との間でロスレスかつ広帯域の通信パスを設定する例を示したが、品質が保証されていないデータの転送経路を通信パスとして設定してもよい。 Further, in the above-described embodiment, an example of setting a lossless and broadband communication path between the data source 10 and the server 40 has been shown. good.
　本開示は情報通信産業に適用することができる。 This disclosure can be applied to the information and communications industry.
１０、１０Ａ、１０Ｂ、１０Ｃ：データソース
２０：送信制御コントローラ
４０：サーバ
５０：センサ
１１：要件通知機能
１２：送信ポリシー受信機能
１３：データ送信タイミング制御機能
１４：通信パス設定機能
１５：データ送信機能
１６：通信パス解放機能
１７：発生データ格納機能
１８：要件テーブル
１９：送信ポリシーテーブル
２１：要件受信機能
２２：送信ポリシー決定機能
２３：送信ポリシー配信機能
２４：送信ポリシー決定ルール
４１：データ受信機能
４２：メモリ
４３：アプリケーション
８０：通信ネットワーク
８１Ａ、８１Ｂ、８１Ｃ、８１Ｄ、８１Ｅ：ネットワーク機器 10, 10A, 10B, 10C: data source 20: transmission control controller 40: server 50: sensor 11: requirement notification function 12: transmission policy reception function 13: data transmission timing control function 14: communication path setting function 15: data transmission function 16: Communication path release function 17: Generated data storage function 18: Requirement table 19: Transmission policy table 21: Requirement reception function 22: Transmission policy determination function 23: Transmission policy distribution function 24: Transmission policy determination rule 41: Data reception function 42 : memory 43: application 80: communication network 81A, 81B, 81C, 81D, 81E: network equipment

Claims (8)

  1. 　複数のデータソースからのデータをサーバに収集するシステムにおいて、
    　前記複数のデータソースから前記サーバにデータを転送するネットワーク機器が、前記データソースごとに定められており、
    　前記複数のデータソースは、それぞれ、前記サーバに送信すべきデータが発生すると、自装置に定められている前記ネットワーク機器に対して通信パスの接続要求を送信する、
    　システム。     In a system that collects data from multiple data sources into a server,
    a network device for transferring data from the plurality of data sources to the server is determined for each data source;
    When data to be transmitted to the server is generated, each of the plurality of data sources transmits a communication path connection request to the network device determined in the device itself.
    system.
  2. 　前記ネットワーク機器は、
    　予め定められたデータソース又はネットワーク機器から通信パスの接続要求を受信すると、
    　前記通信パスの接続要求の送信元との間で通信パスを生成し、
    　前記通信パスの接続要求の送信元に応じて定められたネットワーク機器又はサーバに通信パスの接続要求を送信し、当該通信パスの接続要求の送信先との間で通信パスを生成する、
    　請求項１に記載のシステム。     The network equipment is
    Upon receiving a communication path connection request from a predetermined data source or network device,
    generating a communication path with a source of a connection request for the communication path;
    transmitting a communication path connection request to a network device or server determined according to the source of the communication path connection request, and generating a communication path with the transmission destination of the communication path connection request;
    The system of claim 1.
  3. 　前記通信パスの接続要求は、ＲＤＭＡ（Ｒｅｍｏｔｅ　Ｄｉｒｅｃｔ　Ｍｅｍｏｒｙ　Ａｃｃｅｓｓ）のパケットのヘッダを用いて送信され、
    　前記データソースと前記サーバとの間でＲＤＭＡを用いたデータの転送が可能な通信パスが生成される、
    　請求項１又は２に記載のシステム。     The communication path connection request is transmitted using a RDMA (Remote Direct Memory Access) packet header,
    A communication path is created between the data source and the server that allows data to be transferred using RDMA.
    3. A system according to claim 1 or 2.
  4. 　前記通信パスの接続要求は、ＲＤＭＡのパケットのヘッダに備わるＡｔｔｒｉｂｕｔｅ　ＩＤ領域を用いて、ネットワーク機器に送信される、
    　請求項３に記載のシステム。     The communication path connection request is transmitted to the network device using an Attribute ID area provided in the RDMA packet header,
    4. The system of claim 3.
  5. 　複数のデータソースからのデータをサーバに収集するシステムが実行する方法であって、
    　前記システムは、前記複数のデータソースから前記サーバにデータを転送するネットワーク機器が、前記データソースごとに定められており、
    　前記複数のデータソースは、それぞれ、前記サーバに送信すべきデータが発生すると、自装置に定められている前記ネットワーク機器に対して通信パスの接続要求を送信する、
    　方法。     A method performed by a system for collecting data from multiple data sources on a server, comprising:
    In the system, a network device for transferring data from the plurality of data sources to the server is defined for each data source,
    When data to be transmitted to the server is generated, each of the plurality of data sources transmits a communication path connection request to the network device determined in the device itself.
    Method.
  6. 　複数のデータソース装置からのデータをサーバに収集するシステムに備わる前記データソース装置であって、
    　前記サーバにデータを転送するネットワーク機器が予め定められており、
    　前記サーバに送信すべきデータが発生すると、自装置に定められている前記ネットワーク機器に対して通信パスの接続要求を送信する、
    　データソース装置。     The data source device provided in a system that collects data from a plurality of data source devices to a server,
    A network device for transferring data to the server is predetermined,
    When data to be transmitted to the server is generated, a communication path connection request is transmitted to the network device defined in the device itself;
    Data source device.
  7. 　複数のデータソース装置からのデータをサーバに収集するシステムに備わる前記データソース装置が実行する方法であって、
    　前記データソース装置は、
    　前記サーバに送信すべきデータが発生すると、自装置に定められているネットワーク機器に対して通信パスの接続要求を送信する、
    　方法。     A method executed by a data source device provided in a system for collecting data from a plurality of data source devices on a server,
    The data source device
    When data to be transmitted to the server is generated, a communication path connection request is transmitted to a network device determined in the own device.
    Method.
  8. 　請求項１から４のいずれかに記載のシステムに備わる前記データソースとしてコンピュータを実現させるためのプログラム。 A program for implementing a computer as the data source provided in the system according to any one of claims 1 to 4.
PCT/JP2022/007865 2022-02-25 2022-02-25 Data collection system, method, and program WO2023162130A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/007865 WO2023162130A1 (en) 2022-02-25 2022-02-25 Data collection system, method, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/007865 WO2023162130A1 (en) 2022-02-25 2022-02-25 Data collection system, method, and program

Publications (1)

Publication Number Publication Date
WO2023162130A1 true WO2023162130A1 (en) 2023-08-31

Family

ID=87765027

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/007865 WO2023162130A1 (en) 2022-02-25 2022-02-25 Data collection system, method, and program

Country Status (1)

Country Link
WO (1) WO2023162130A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020017821A (en) * 2018-07-24 2020-01-30 富士通フロンテック株式会社 External information reception and distribution device, data transmission method, and program

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020017821A (en) * 2018-07-24 2020-01-30 富士通フロンテック株式会社 External information reception and distribution device, data transmission method, and program

Similar Documents

Publication Publication Date Title
US7930446B2 (en) Methods and apparatuses for wireless network communication wherein a universal serial bus request block (URB) is generated that will vary parameters that controls wireless transmission commands between devices
EP3547580B1 (en) Data sending method and apparatus, and data receiving method and apparatus
CN106411767B (en) Pass through method, system and the medium of the transmission operation that Remote Direct Memory accesses
KR101021566B1 (en) Mechanism for providing quality of service in a network utilizing priority and reserved bandwidth protocols
EP2193634B1 (en) Bandwidth reservation for data flows in interconnection networks
US10484472B2 (en) Methods and systems for efficiently moving data between nodes in a cluster
US11513985B2 (en) RoCE over wireless
KR101426217B1 (en) Reducing the maximum latency of reserved streams
JP2023511889A (en) Service level configuration method and apparatus
US7580410B2 (en) Extensible protocol processing system
US11177969B2 (en) Interface device and data communication method
CN112398754B (en) Data transmission method, device, medium, electronic equipment and network access equipment
WO2023162130A1 (en) Data collection system, method, and program
WO2014010189A1 (en) Proxy device, communication system, program
WO2023162128A1 (en) System, method, and program for collecting data
WO2023162127A1 (en) System, method, and program for collecting data
WO2018142866A1 (en) Transfer device, transfer method and program
WO2023012878A1 (en) System, method, and program for collecting data
WO2024150299A1 (en) Device and method for preliminarily predicting and executing establishment of communication path
WO2023162134A1 (en) Data collecting system, method and program
WO2024150298A1 (en) Device and method for predicting release of communication path in advance and performing same
WO2024150300A1 (en) Device and method for transferring data by method according to situation of communication network
JP6488557B2 (en) Communication control system, communication system, communication control method, and communication control program
JPH10190734A (en) Packet transfer device/method
EP3955115B1 (en) Flexible link level retry for shared memory switches

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: 22928657

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2024502363

Country of ref document: JP

Kind code of ref document: A