WO2023162128A1 - System, method, and program for collecting data - Google Patents

System, method, and program for collecting data Download PDF

Info

Publication number
WO2023162128A1
WO2023162128A1 PCT/JP2022/007859 JP2022007859W WO2023162128A1 WO 2023162128 A1 WO2023162128 A1 WO 2023162128A1 JP 2022007859 W JP2022007859 W JP 2022007859W WO 2023162128 A1 WO2023162128 A1 WO 2023162128A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
communication path
transmission policy
transmission
data source
Prior art date
Application number
PCT/JP2022/007859
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/007859 priority Critical patent/WO2023162128A1/en
Publication of WO2023162128A1 publication Critical patent/WO2023162128A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation

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: the plurality of data sources, Get the rules that determine the outbound policy from the outside, Based on the rules, determine a transmission policy according to the data transfer requirements of the device, Data is transmitted autonomously based on the transmission policy.
  • the present disclosure provides a data source device for transmitting data to a server and a method performed by the data source device, comprising: the data source device Get the rules that determine the outbound policy from the outside, Based on the rules, determine a transmission policy according to the data transfer requirements of the device, Data is transmitted autonomously based on the transmission policy.
  • 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;
  • 4 shows a configuration example of a path management controller;
  • An example of a path setting location table 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.
  • 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.
  • Fig. 1 shows a system configuration example of the present disclosure.
  • the system of the present disclosure comprises multiple data sources 10, a transmission control controller 20, a path management controller 30, and a server 40.
  • FIG. A plurality of data sources 10 , transmission controllers 20 , path management controllers 30 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.
  • This embodiment shows an example in which the transmission control controller 20 and the path management controller 30 are arranged separately, but these controllers may be provided in a common device or distributed. It may consist of a plurality of devices.
  • the device of the present invention can also be implemented 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 .
  • the network device 81 used between the data source 10 and the server 40 is predetermined.
  • 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 data transfer is completed, 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.
  • each data source 10 when the transmission control controller 20 distributes the transmission policy of each data source 10, each data source 10 simultaneously receives the transmission policy from the transmission control controller 20 when the transmission policy determination flow that defines the rule for determining the transmission policy is changed. will receive At this time, access from the data source 10 to the transmission control controller 20 is concentrated, the load on the transmission control controller 20 is increased, and there is a possibility that the transmission policy cannot be distributed or takes time to be distributed.
  • the transmission control controller 20 distributes the transmission policy determination flow.
  • Each data source 10 determines a transmission policy that matches the data transfer requirements of its own device according to the transmission policy determination flow. Thereby, each data source 10 can acquire a transmission policy that meets the data transfer requirements of its own device.
  • Each data source 10 notifies the path management controller 30 of a communication path connection request or release request according to the transmission policy, and controls the timing of communication path creation or release. As a result, the present embodiment controls the trade-off between immediacy of data transmission and shortening of communication path usage 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 transmission policy determination 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, and a transmission policy table 19. Prepare.
  • the generated data storage function 17 stores sensing data from the sensor 50 .
  • the transmission policy determination function 12 receives a transmission policy determination flow from the transmission control controller 20, reads data transfer requirements from the requirement table 18, determines a transmission policy according to the read data transfer requirements, and stores it in the transmission policy table 19. do.
  • 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 communication path connection request to the path management controller 30 .
  • 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 communication path release request to the path management controller 30 .
  • 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. As shown in FIG.
  • the transmission controller 20 has a transmission policy determination flow generation function 26 and a transmission policy determination flow delivery function 23 .
  • Fig. 7 shows an example of the flow for determining the transmission policy.
  • the transmission policy determination flow generation function 26 generates a transmission policy determination flow (S101).
  • the transmission policy determination flow distribution function 23 distributes to each data source 10 (S102).
  • Each data source 10 receives the transmission policy determination flow transmitted from the transmission control controller 20 .
  • the data source 10 refers to the requirement table 18 provided in its own device and determines its own transmission policy according to the received transmission policy determination flow (S103).
  • FIG. 8 shows an example of the operation of the transmission policy determination function 12 provided in each data source 10.
  • the transmission policy determination function 12 acquires the data transfer requirements (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 a communication path immediately after data generation and transmitting 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 policy determination function 12 determines the data generation frequency (S15).
  • the method of releasing the communication 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 communication 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 policy decision function 12 sets the thresholds in steps S12 and S15, taking into consideration the requirements contained in the application information.
  • the data source 10 determines the transmission policy, it stores it in the transmission policy table 19.
  • 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.
  • FIG. 10 shows a configuration example of the path management controller 30.
  • the path management controller 30 has a path setting request reception function 31 , a path setting function 32 and a path setting location table 33 .
  • the path setup request reception function 31 receives a communication path connection request or release request from each data source 10 .
  • the path setting function 32 creates or releases a communication path according to a communication path connection request or release request from each data source 10 .
  • the path setting location table 33 manages communication path setting information (creation/release) from each data source 10 to the server 40 .
  • the path setting location table 33 stores information on the network device 81 that transfers sensing data from each data source 10 .
  • the information of the network device 81 includes identification information of the network devices 81A and 81B connecting the data source 10A and the server 40, and communication path setting information (creation/release) in the network devices 81A and 81B. include.
  • FIG. 12 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 sensing data generated by the sensor 50, and when the data reaches 20 MB, it transmits a communication path connection request to the path management controller 30 (S201).
  • the path management controller 30 sets the communication paths of the network devices 81A and 81C and generates the communication paths (S202).
  • the path management controller 30 transmits a communication path generation completion notification to the data source 10B (S203).
  • the data source 10B When the data source 10B receives the communication path generation completion notification, it transmits sensing data to the server 40 (S204-1 and S204-2). It waits for the next 50ms to send a communication path release request. When sensing data is generated during that time, the sensing data is transmitted each time (S204-3). When 50 ms have passed since the last data transmission (step S204-3), the data source 10B transmits a communication path release request to the path management controller 30 (S205). When the path management controller 30 receives the communication path release request, the path management controller 30 releases the communication paths of the network devices 81A and 81C, and transmits a communication path release completion notification to the data source 10B indicating that the communication path release has been completed (S206). ).
  • FIG. 13 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 transmits a communication path connection request to the path management controller 30 (S301).
  • the path management controller 30 Upon receiving the communication path connection request, the path management controller 30 generates a communication path from the network device 81E to the server 40 (S302).
  • the path management controller 30 transmits a communication path generation completion notification to the data source 10A (S303).
  • the data source 10A When the data source 10A receives the communication path generation completion notification (S303), it collectively transmits the accumulated sensing data to the server 40 (S304-1, S304-2, S304-3). After that, the data source 10A immediately transmits a communication path release request to the path management controller 30 (S305).
  • FIG. 14 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 transmits a communication path connection request to the path management controller 30 (S401).
  • the data source 10C receives the communication path generation completion notification (S403), it 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 transmits a communication path release request to the path management controller 30 when 20 ms have passed since the last data transmission (step S404-3) (S405).
  • 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 communication path can be improved and network resources can be reduced.
  • the transmission control controller 20 distributes the transmission policy determination flow, and each data source 10 follows the transmission policy determination flow to determine a transmission policy that meets the data transfer requirements of its own device. Thereby, each data source 10 can acquire a transmission policy that meets the data transfer requirements of its own device according to the transmission policy determination flow.
  • the present disclosure can reduce the load due to access concentration on the transmission controller 20 .
  • each data source 10 determines a transmission policy and generates a communication path for each data source 10 according to the transmission policy, it is possible to time-divisionally allocate the communication path at the required timing. 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 system of this embodiment does not include the path management controller 30 shown in FIG.
  • the data source 10 directly transmits a communication path connection request to the network devices 81A to 81E.
  • the data source 10 directly transmits a communication path connection request to the network devices 81A to 81E.
  • the communication path setting function 14 transmits a connection request for generating a communication path with the server 40 to the network device 81 .
  • the communication path release function 16 also transmits a release request for releasing the communication path with the server 40 to the network device 81 .
  • 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. 15 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. 16 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.
  • 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. 17 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 predetermined, 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.
  • This embodiment realizes a lossless and broadband communication network 80 with communication paths, does not require a large amount of network resources, and enables RDMA communication with many data sources. Furthermore, the present disclosure can prevent data loss in the communication network 80, so that data transfer using reliable RDMA can be realized.
  • the present disclosure can provide a lossless and high-bandwidth communication network 80 with communication paths to 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The purpose of this disclosure is to provide a system which does not require large amounts of network resources even when data is collected from a large number of data sources.　This disclosure relates to a system for collecting data from a plurality of data sources in a server, and a method. In the system, the plurality of data sources each acquire a rule for determining a transmission policy from outside, on the basis of the rule, determine a transmission policy corresponding to a data transfer requirement therefor, and on the basis of the transmission policy, autonomously transmit the data.

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:
the plurality of data sources,
Get the rules that determine the outbound policy from the outside,
Based on the rules, determine a transmission policy according to the data transfer requirements of the device,
Data is transmitted autonomously based on the transmission policy.
　本開示は、データをサーバに送信するデータソース装置及び当該データソース装置が実行する方法であって、
　データソース装置が、
　送信ポリシーを決定するルールを外部から取得し、
　前記ルールに基づき、自装置のデータ転送要件に応じた送信ポリシーを決定し、
　前記送信ポリシーに基づいて、自律的に、データを送信する。 The present disclosure provides a data source device for transmitting data to a server and a method performed by the data source device, comprising:
the data source device
Get the rules that determine the outbound policy from the outside,
Based on the rules, determine a transmission policy according to the data transfer requirements of the device,
Data is transmitted autonomously based on the transmission policy.
　本開示のコントローラ及びデータソースなどの装置はコンピュータとプログラムによっても実現でき、プログラムを記録媒体に記録することも、通信ネットワークを通して提供することも可能である。本開示のプログラムは、本開示に係る装置に備わる各機能部としてコンピュータを実現させるためのプログラムであり、本開示に係る装置が実行する方法に備わる各ステップをコンピュータに実行させるためのプログラムである。 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; パス管理コントローラの構成例を示す。4 shows a configuration example of a path management controller; パス設定箇所テーブルの一例を示す。An example of a path setting location table 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. Ａｔｔｒｉｂｕｔｅ　ＩＤ領域の一例を示す。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.
　以下、本開示の実施形態について、図面を参照しながら詳細に説明する。なお、本開示は、以下に示す実施形態に限定されるものではない。これらの実施の例は例示に過ぎず、本開示は当業者の知識に基づいて種々の変更、改良を施した形態で実施することができる。なお、本明細書及び図面において符号が同じ構成要素は、相互に同一のものを示すものとする。 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 control controller 20, a path management controller 30, and a server 40. FIG. A plurality of data sources 10 , transmission controllers 20 , path management controllers 30 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.
　本実施形態では、送信制御コントローラ２０及びパス管理コントローラ３０が分離して配置されている例を示すが、これらのコントローラは、共通の装置に備わっていてもよいし、分散して配置されている複数の装置で構成されていてもよい。本発明の装置はコンピュータとプログラムによっても実現でき、プログラムを記録媒体に記録することも、通信ネットワークを通して提供することも可能である。 This embodiment shows an example in which the transmission control controller 20 and the path management controller 30 are arranged separately, but these controllers may be provided in a common device or distributed. It may consist of a plurality of devices. The device of the present invention can also be implemented 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, the network device 81 used between the data source 10 and the server 40 is predetermined. 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 data transfer is completed, 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.
　ここで、送信制御コントローラ２０が各データソース１０の送信ポリシーを配布する場合、送信ポリシーを決定するルールを定める送信ポリシー決定フローの変更時に、各データソース１０が一斉に送信制御コントローラ２０から送信ポリシーを受信することになる。このとき、データソース１０から送信制御コントローラ２０へのアクセスが集中し、送信制御コントローラ２０の負荷が高くなり、送信ポリシーを配布できなくなる、または、配布に時間がかかる可能性がある。 Here, when the transmission control controller 20 distributes the transmission policy of each data source 10, each data source 10 simultaneously receives the transmission policy from the transmission control controller 20 when the transmission policy determination flow that defines the rule for determining the transmission policy is changed. will receive At this time, access from the data source 10 to the transmission control controller 20 is concentrated, the load on the transmission control controller 20 is increased, and there is a possibility that the transmission policy cannot be distributed or takes time to be distributed.
　そこで、本開示のシステムは、送信制御コントローラ２０が送信ポリシー決定フローを配布する。各データソース１０は、送信ポリシー決定フローに従い、自装置のデータ転送要件に合った送信ポリシーを決定する。これにより、各データソース１０は、自装置のデータ転送要件に合った送信ポリシーを取得することができる。 Therefore, in the system of the present disclosure, the transmission control controller 20 distributes the transmission policy determination flow. Each data source 10 determines a transmission policy that matches the data transfer requirements of its own device according to the transmission policy determination flow. Thereby, each data source 10 can acquire a transmission policy that meets the data transfer requirements of its own device.
　各データソース１０は、送信ポリシーに従い、通信パスの接続要求又は解放要求をパス管理コントローラ３０へ通知し、通信パスの生成又は解放のタイミング制御を行う。これにより、本実施形態は、データ送信の即時性と通信パス利用時間短縮のトレードオフを制御する。以下、詳細に説明する。 Each data source 10 notifies the path management controller 30 of a communication path connection request or release request according to the transmission policy, and controls the timing of communication path creation or release. As a result, the present embodiment controls the trade-off between immediacy of data transmission and shortening of communication path usage time. A detailed description will be given below.
（第１の実施形態）
　図３に、サーバ４０の構成例を示す。サーバ４０は、データ受信機能４１、メモリ４２、アプリケーション４３を備える。
　データ受信機能４１は、各データソース１０からセンシングデータを受信する。
　メモリ４２は、センサ５０からのセンシングデータを格納する。
　アプリケーション４３は、センサ５０からのセンシングデータを収集する。アプリケーション４３は、ユーザ端末やセンサ、車載システムなどで検出又は発生した任意のセンシングデータを収集する任意のアプリケーションである。 (First embodiment)
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 transmission policy determination 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, and a transmission policy table 19. Prepare.
　発生データ格納機能１７は、センサ５０からのセンシングデータを格納する。
　送信ポリシー決定機能１２は、送信制御コントローラ２０から送信ポリシー決定フローを受信し、要件テーブル１８からデータ転送要件を読み出し、読み出したデータ転送要件に応じた送信ポリシーを決定し、送信ポリシーテーブル１９に格納する。
　データ送信タイミング制御機能１３は、送信ポリシーテーブル１９に従い、通信パス設定機能１４、データ送信機能１５及び通信パス解放機能１６を制御する。
　通信パス設定機能１４は、通信パスの接続要求をパス管理コントローラ３０に送信する。
　データ送信機能１５は、発生データ格納機能１７に格納されているセンシングデータを、サーバ４０に送信する。
　通信パス解放機能１６は、通信パスの解放要求をパス管理コントローラ３０に送信する。
　要件テーブル１８は、データソース１０ごとのデータ転送要件を格納する。
　送信ポリシーテーブル１９は、データソース１０からサーバ４０へセンシングデータを送信する際のポリシーを格納する。 The generated data storage function 17 stores sensing data from the sensor 50 .
The transmission policy determination function 12 receives a transmission policy determination flow from the transmission control controller 20, reads data transfer requirements from the requirement table 18, determines a transmission policy according to the read data transfer requirements, and stores it in the transmission policy table 19. do.
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 communication path connection request to the path management controller 30 .
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 communication path release request to the path management controller 30 .
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 transmission policy determination flow generation function 26 and a transmission policy determination flow delivery function 23 .
　図７に、送信ポリシーを決定するフローの一例を示す。送信ポリシー決定フロー生成機能２６が送信ポリシー決定フローを生成する（Ｓ１０１）。送信ポリシー決定フロー配信機能２３が、各データソース１０に配信する（Ｓ１０２）。各データソース１０は、送信制御コントローラ２０から送信された送信ポリシーの決定フローを受信する。データソース１０は、自装置に備わる要件テーブル１８を参照し、受信した送信ポリシーの決定フローに従い、自装置の送信ポリシーを決定する（Ｓ１０３）。 　Fig. 7 shows an example of the flow for determining the transmission policy. The transmission policy determination flow generation function 26 generates a transmission policy determination flow (S101). The transmission policy determination flow distribution function 23 distributes to each data source 10 (S102). Each data source 10 receives the transmission policy determination flow transmitted from the transmission control controller 20 . The data source 10 refers to the requirement table 18 provided in its own device and determines its own transmission policy according to the received transmission policy determination flow (S103).
　図８に、各データソース１０に備わる送信ポリシー決定機能１２の動作の一例を示す。
　送信ポリシー決定機能１２は、データ転送要件を取得すると（Ｓ１１）、許容遅延時間の要件を判定する（Ｓ１２）。許容遅延時間の要件が１００ｍｓ以下である場合（Ｓ１２においてＹｅｓ）、データ発生後即座に通信パスを生成し、送信する方式に決定する（Ｓ１３）。一方、許容遅延時間の要件が１００ｍｓ超である場合（Ｓ１２においてＮｏ）、センシングデータを一定量溜めて送信する方式に決定する（Ｓ１４）。
　次に、送信ポリシー決定機能１２は、データ発生頻度を判定する（Ｓ１５）。データ発生頻度が４回／ｓ以下である場合（Ｓ１５においてＹｅｓ）、データ送信後即座に通信パスを解放する方式に決定する（Ｓ１６）。一方、データ発生頻度が４回／ｓ超である場合（Ｓ１５においてＮｏ）、データ送信完了後一定時間待機して通信パスを解放する方式に決定する（Ｓ１７）。 FIG. 8 shows an example of the operation of the transmission policy determination function 12 provided in each data source 10. As shown in FIG.
When the transmission policy determination function 12 acquires the data transfer requirements (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 a communication path immediately after data generation and transmitting 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 policy determination function 12 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 communication 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 communication 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 policy decision function 12 sets the thresholds in steps S12 and S15, taking into consideration the requirements contained in the application information.
　データソース１０は、送信ポリシーを決定すると、送信ポリシーテーブル１９に格納する。これにより、図９に示すように、各データソース１０の送信ポリシーテーブル１９に、各データソース１０に適した送信ポリシーが格納される。 When the data source 10 determines the transmission policy, 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.
　図１０に、パス管理コントローラ３０の構成例を示す。パス管理コントローラ３０は、パス設定要求受信機能３１、パス設定機能３２、パス設定箇所テーブル３３を備える。 10 shows a configuration example of the path management controller 30. FIG. The path management controller 30 has a path setting request reception function 31 , a path setting function 32 and a path setting location table 33 .
　パス設定要求受信機能３１は、通信パスの接続要求又は解放要求を、各データソース１０から受信する。
　パス設定機能３２は、各データソース１０からの通信パスの接続要求又は解放要求に従い、通信パスの生成又は解放を行う。
　パス設定箇所テーブル３３は、各データソース１０からサーバ４０までの通信パスの設定情報（生成／解放）を管理する。 The path setup request reception function 31 receives a communication path connection request or release request from each data source 10 .
The path setting function 32 creates or releases a communication path according to a communication path connection request or release request from each data source 10 .
The path setting location table 33 manages communication path setting information (creation/release) from each data source 10 to the server 40 .
　図１１に、パス設定箇所テーブル３３の一例を示す。パス設定箇所テーブル３３は、各データソース１０からのセンシングデータを転送するネットワーク機器８１の情報を格納する。例えば、データソース１０Ａの場合、ネットワーク機器８１の情報は、データソース１０Ａとサーバ４０を接続するネットワーク機器８１Ａ及び８１Ｂの識別情報、ネットワーク機器８１Ａ及び８１Ｂにおける通信パスの設定情報（生成／解放）を含む。 An example of the path setting location table 33 is shown in FIG. The path setting location table 33 stores information on the network device 81 that transfers sensing data from each data source 10 . For example, in the case of the data source 10A, the information of the network device 81 includes identification information of the network devices 81A and 81B connecting the data source 10A and the server 40, and communication path setting information (creation/release) in the network devices 81A and 81B. include.
　図１２に、データソース１０Ｂからサーバ４０へのセンシングデータの送信例を示す。データソース１０Ｂは、第４の送信ポリシーに従い、センシングデータを送信する。
　データソース１０Ｂは、センサ５０で発生したセンシングデータを蓄積し、データが２０ＭＢに達すると、通信パスの接続要求をパス管理コントローラ３０に送信する（Ｓ２０１）。
　パス管理コントローラ３０は、通信パスの接続要求を受信すると、ネットワーク機器８１Ａ及び８１Ｃの通信パスを設定し、通信パスを生成する（Ｓ２０２）。パス管理コントローラ３０は、通信パスの生成が完了すると、通信パス生成完了通知をデータソース１０Ｂに送信する（Ｓ２０３）。
　データソース１０Ｂは、通信パス生成完了通知を受信すると、サーバ４０へセンシングデータを送信する（Ｓ２０４－１及びＳ２０４－２）。その後の５０ｍｓの間、通信パスの解放要求の送信を待機する。その間にセンシングデータが発生した場合、その都度センシングデータを送信する（Ｓ２０４－３）。
　データソース１０Ｂは、最後のデータ送信（ステップＳ２０４－３）から５０ｍｓが経過すると、通信パスの解放要求をパス管理コントローラ３０に送信する（Ｓ２０５）。
　パス管理コントローラ３０は、通信パスの解放要求を受信すると、ネットワーク機器８１Ａ及び８１Ｃの通信パスを解放し、通信パスの解放が完了した旨の通信パス解放完了通知をデータソース１０Ｂに送信する（Ｓ２０６）。 FIG. 12 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 sensing data generated by the sensor 50, and when the data reaches 20 MB, it transmits a communication path connection request to the path management controller 30 (S201).
Upon receiving the communication path connection request, the path management controller 30 sets the communication paths of the network devices 81A and 81C and generates the communication paths (S202). When the communication path generation is completed, the path management controller 30 transmits a communication path generation completion notification to the data source 10B (S203).
When the data source 10B receives the communication path generation completion notification, it transmits sensing data to the server 40 (S204-1 and S204-2). It waits for the next 50ms to send a communication path release request. When sensing data is generated during that time, the sensing data is transmitted each time (S204-3).
When 50 ms have passed since the last data transmission (step S204-3), the data source 10B transmits a communication path release request to the path management controller 30 (S205).
When the path management controller 30 receives the communication path release request, the path management controller 30 releases the communication paths of the network devices 81A and 81C, and transmits a communication path release completion notification to the data source 10B indicating that the communication path release has been completed (S206). ).
　図１３に、データソース１０Ａからサーバ４０へのセンシングデータの送信例を示す。データソース１０Ａは、第２の送信ポリシーに従い、センシングデータを送信する。
　データソース１０Ａは、センサ５０で発生したセンシングデータを蓄積し、データが１５ＭＢに達すると、通信パスの接続要求をパス管理コントローラ３０に送信する（Ｓ３０１）。
　パス管理コントローラ３０は、通信パスの接続要求を受信すると、ネットワーク機器８１Ｅからサーバ４０までの通信パスを生成する（Ｓ３０２）。パス管理コントローラ３０は、通信パスの生成が完了すると、通信パス生成完了通知をデータソース１０Ａに送信する（Ｓ３０３）。
　そして、データソース１０Ａは、通信パス生成完了通知を受信すると（Ｓ３０３）、蓄積したセンシングデータをまとめてサーバ４０へ送信する（Ｓ３０４－１、Ｓ３０４－２、Ｓ３０４－３）。その後、データソース１０Ａは、即座に通信パスの解放要求をパス管理コントローラ３０に送信する（Ｓ３０５）。 FIG. 13 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 transmits a communication path connection request to the path management controller 30 (S301).
Upon receiving the communication path connection request, the path management controller 30 generates a communication path from the network device 81E to the server 40 (S302). When the communication path generation is completed, the path management controller 30 transmits a communication path generation completion notification to the data source 10A (S303).
When the data source 10A receives the communication path generation completion notification (S303), it collectively transmits the accumulated sensing data to the server 40 (S304-1, S304-2, S304-3). After that, the data source 10A immediately transmits a communication path release request to the path management controller 30 (S305).
　図１４に、データソース１０Ｃからサーバ４０へのセンシングデータの送信例を示す。データソース１０Ｃは、第３の送信ポリシーに従い、センシングデータを送信する。
　データソース１０Ｃは、センサ５０でデータが発生すると、通信パスの接続要求をパス管理コントローラ３０に送信する（Ｓ４０１）。
　データソース１０Ｃは、通信パス生成完了通知を受信すると（Ｓ４０３）、サーバ４０へセンシングデータを送信し（Ｓ４０４－１）、その後の２０ｍｓの間、通信パスの解放要求の送信を待機する。その間にセンシングデータが発生した場合、その都度センシングデータを送信する（Ｓ４０４－２、Ｓ４０４－３）。
　データソース１０Ｃは、最後のデータ送信（ステップＳ４０４－３）から２０ｍｓが経過すると、通信パスの解放要求をパス管理コントローラ３０に送信する（Ｓ４０５）。 FIG. 14 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 the sensor 50 generates data, the data source 10C transmits a communication path connection request to the path management controller 30 (S401).
When the data source 10C receives the communication path generation completion notification (S403), it 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 transmits a communication path release request to the path management controller 30 when 20 ms have passed since the last data transmission (step S404-3) (S405).
　図１２から図１４に示すように、本実施形態は、通信パスを必要なタイミングで時分割に割り当てることで、ネットワークリソースの枯渇を防ぎ、大量のデータソースとのＲＤＭＡ通信を実現する。センシングデータを送信したいデータソース１０に必要な期間だけ通信パスを割り当てるため、通信パスの利用率を向上できるとともに、ネットワークリソースを削減できる。 As shown in FIGS. 12 to 14, 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 communication path can be improved and network resources can be reduced.
　以上説明したように、本開示は、送信制御コントローラ２０が送信ポリシー決定フローを配布し、各データソース１０が送信ポリシー決定フローに従い、自装置のデータ転送要件に合った送信ポリシーを決定する。これにより、各データソース１０は、送信ポリシー決定フローに従い、自装置のデータ転送要件に合った送信ポリシーを取得することができる。 As described above, according to the present disclosure, the transmission control controller 20 distributes the transmission policy determination flow, and each data source 10 follows the transmission policy determination flow to determine a transmission policy that meets the data transfer requirements of its own device. Thereby, each data source 10 can acquire a transmission policy that meets the data transfer requirements of its own device according to the transmission policy determination flow.
　本開示では、送信ポリシー決定フローをデータソース１０へ配布するため、送信ポリシー決定フローに変更がある場合であっても、送信制御コントローラ２０にアクセスが集中することはない。このため、本開示は、送信制御コントローラ２０へのアクセス集中による負荷を低減することができる。 In the present disclosure, since the transmission policy determination flow is distributed to the data source 10, even if there is a change in the transmission policy determination flow, accesses do not concentrate on the transmission control controller 20. Therefore, the present disclosure can reduce the load due to access concentration on the transmission controller 20 .
　各データソース１０が送信ポリシーを決定し、送信ポリシーに従って各データソース１０の通信パスを生成するため、通信パスを必要なタイミングで時分割に割り当てることができる。このため、本開示は、データ送信の即時性と通信パス利用時間短縮のトレードオフに対し、各データソース１０からサーバ４０への通信パス利用時間を短縮し、通信パスの使いまわしを容易にし、通信ネットワーク８０の全体としての通信パス必要数を削減するよう、制御することができる。 Since each data source 10 determines a transmission policy and generates a communication path for each data source 10 according to the transmission policy, it is possible to time-divisionally allocate the communication path at the required timing. 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.
（第２の実施形態）
　本実施形態のシステムは、図１に示すパス管理コントローラ３０を備えない。本実施形態では、データソース１０は、直接、ネットワーク機器８１Ａ～８１Ｅへ通信パスの接続要求を送信する。ネットワーク機器８１Ａ～８１Ｅが受け取った設定を反映することで、通信パスを生成するまでの手間を省略することができる。これにより、本実施形態は、より短時間で通信パスの設定することができる。 (Second embodiment)
The system of this embodiment does not include the path management controller 30 shown in FIG. In this embodiment, the data source 10 directly transmits a communication path connection request 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, this embodiment can set a communication path in a shorter time.
　本実施形態では、通信パス設定機能１４は、サーバ４０との通信パスを生成するための接続要求をネットワーク機器８１に送信する。また通信パス解放機能１６は、サーバ４０との通信パスを解放するための解放要求をネットワーク機器８１に送信する。 In this embodiment, the communication path setting function 14 transmits a connection request for generating a communication path with the server 40 to the network device 81 . The communication path release function 16 also transmits a release request for releasing the communication path with the server 40 to the network device 81 .
　データソース１０は、センシングデータが発生すると、ネットワーク機器８１へ通信パスの接続要求を送信する。受け取った機器８１は、設定を反映する。例えば、データソース１０Ａがセンシングデータを送信する場合、データソース１０Ａが通信パスの接続要求をネットワーク機器８１Ｂに送信する。すると、ネットワーク機器８１Ｂは、データソース１０Ａとの通信パスを生成する。 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. 15 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. 16 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. 17 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 predetermined, 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.
　本実施形態は、ロスレスかつ広帯域な通信ネットワーク８０を通信パスで実現し、大量のネットワークリソースを要せず、多数のデータソースとのＲＤＭＡ通信を可能にすることができる。さらに、本開示は、通信ネットワーク８０でのデータのロスを防ぐことができるため、確実なＲＤＭＡを用いたデータ転送を実現することができる。 This embodiment realizes a lossless and broadband communication network 80 with communication paths, does not require a large amount of network resources, and enables RDMA communication with many data sources. Furthermore, the present disclosure can prevent data loss in the communication network 80, so that data transfer using reliable RDMA can be realized.
（本開示の効果）
　したがって、本開示は、ロスレスかつ広帯域な通信ネットワーク８０を通信パスで実現し、大量のネットワークリソースを要せず、多数のデータソースとのＲＤＭＡ通信を可能にすることができる。さらに、本開示は、通信ネットワーク８０でのデータのロスを防ぐことができるため、確実なＲＤＭＡを用いたデータ転送を実現することができる。 (Effect of the present disclosure)
Accordingly, the present disclosure can provide a lossless and high-bandwidth communication network 80 with communication paths to 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 30: path management controller 40: server 50: sensor 12: transmission policy determination 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 determination flow distribution function 24: Transmission policy determination flow 31: Path setting Request reception function 32: Path setting function 33: Path setting location table 41: Data reception function 42: Memory 43: Application 80: Communication networks 81A, 81B, 81C, 81D, 81E: Network equipment

Claims (8)

  1. 　複数のデータソースからのデータをサーバに収集するシステムにおいて、
    　前記複数のデータソースが、
    　送信ポリシーを決定するルールを外部から取得し、
    　前記ルールに基づき、自装置のデータ転送要件に応じた送信ポリシーを決定し、
    　前記送信ポリシーに基づいて、自律的に、データを送信する、
    　システム。     In a system that collects data from multiple data sources into a server,
    the plurality of data sources,
    Get the rules that determine the outbound policy from the outside,
    Based on the rules, determine a transmission policy according to the data transfer requirements of the device,
    autonomously transmitting data based on the transmission policy;
    system.
  2. 　前記送信ポリシーは、
    　データ発生後即座に通信パスを生成してデータ転送を行い、データ転送完了後即座に通信パス解放するもの、
    　データが一定量蓄積してから通信パスを生成してデータ転送を行い、データ転送完了後即座に通信パスを解放するもの、及び
    　データ発生後即座に通信パスを生成してデータ転送を行い、データ転送完了後も一定時間通信パスを保持し続けるもの、
    　データが一定量蓄積してから通信パスを生成してデータ転送を行い、データ転送完了後も一定時間通信パスを保持し続けるもの、
    　を含む、
    　請求項１に記載のシステム。     The transmission policy is
    Immediately after data generation, a communication path is generated and data is transferred, and the communication path is released immediately after data transfer is completed.
    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 data transfer is completed. Those that keep the communication path for a certain period of time even after the transfer is completed,
    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.
    including,
    The system of claim 1.
  3. 　前記データ転送要件は、許容遅延時間及びデータ発生頻度を含み、
    　前記送信ポリシーは、許容遅延時間及びデータ発生頻度を基に決定される、
    　請求項１又は２に記載のシステム。     the data transfer requirements include allowable delay time and data occurrence frequency;
    The transmission policy is determined based on an allowable delay time and data occurrence frequency,
    3. A system according to claim 1 or 2.
  4. 　前記ルールを決定し、前記複数のデータソースに配布するコントローラをさらに備える、
    　請求項１から３のいずれかに記載のシステム。     further comprising a controller that determines and distributes the rules to the plurality of data sources;
    A system according to any of claims 1-3.
  5. 　複数のデータソースからのデータをサーバに収集するシステムが実行する方法であって、
    　前記データソースが、
    　送信ポリシーを決定するルールを外部から取得し、
    　前記ルールに基づき、自装置のデータ転送要件に応じた送信ポリシーを決定し、
    　前記送信ポリシーに基づいて、自律的に、データを送信する、
    　方法。     A method performed by a system for collecting data from multiple data sources on a server, comprising:
    the data source is
    Get the rules that determine the outbound policy from the outside,
    Based on the rules, determine a transmission policy according to the data transfer requirements of the device,
    autonomously transmitting data based on the transmission policy;
    Method.
  6. 　送信ポリシーを決定するルールを外部から取得し、
    　前記ルールに基づき、自装置のデータ転送要件に応じた送信ポリシーを決定し、
    　前記送信ポリシーに基づいて、自律的に、データを送信する、
    　データソース装置。     Get the rules that determine the outbound policy from the outside,
    Based on the rules, determine a transmission policy according to the data transfer requirements of the device,
    autonomously transmitting data based on the transmission policy;
    Data source device.
  7. 　データをサーバに送信するデータソース装置が実行する方法であって、
    　前記データソース装置が、
    　送信ポリシーを決定するルールを外部から取得し、
    　前記ルールに基づき、自装置のデータ転送要件に応じた送信ポリシーを決定し、
    　前記送信ポリシーに基づいて、自律的に、データを送信する、
    　方法。     A method performed by a data source device that transmits data to a server, comprising:
    the data source device
    Get the rules that determine the outbound policy from the outside,
    Based on the rules, determine a transmission policy according to the data transfer requirements of the device,
    autonomously transmitting data based on the transmission policy;
    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/007859 2022-02-25 2022-02-25 System, method, and program for collecting data WO2023162128A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/007859 WO2023162128A1 (en) 2022-02-25 2022-02-25 System, method, and program for collecting data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/007859 WO2023162128A1 (en) 2022-02-25 2022-02-25 System, method, and program for collecting data

Publications (1)

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

Family

ID=87765067

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/007859 WO2023162128A1 (en) 2022-02-25 2022-02-25 System, method, and program for collecting data

Country Status (1)

Country Link
WO (1) WO2023162128A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003110605A (en) * 2001-09-28 2003-04-11 Mitsubishi Electric Corp Policy control system, policy control method and program for allowing computer to execute the method
JP2003224598A (en) * 2002-01-31 2003-08-08 Mitsubishi Electric Corp Method for setting policy definition and policy server
JP2006319902A (en) * 2005-05-16 2006-11-24 Nippon Telegr & Teleph Corp <Ntt> Vpn service providing method and establishment method of optical path
WO2020145182A1 (en) * 2019-01-09 2020-07-16 ソニー株式会社 Communication device and communication method
US20200288212A1 (en) * 2017-11-10 2020-09-10 Telefonaktiebolaget Lm Ericsson (Publ) Multipath policy decisions for encrypted video streams

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003110605A (en) * 2001-09-28 2003-04-11 Mitsubishi Electric Corp Policy control system, policy control method and program for allowing computer to execute the method
JP2003224598A (en) * 2002-01-31 2003-08-08 Mitsubishi Electric Corp Method for setting policy definition and policy server
JP2006319902A (en) * 2005-05-16 2006-11-24 Nippon Telegr & Teleph Corp <Ntt> Vpn service providing method and establishment method of optical path
US20200288212A1 (en) * 2017-11-10 2020-09-10 Telefonaktiebolaget Lm Ericsson (Publ) Multipath policy decisions for encrypted video streams
WO2020145182A1 (en) * 2019-01-09 2020-07-16 ソニー株式会社 Communication device and communication method

Similar Documents

Publication Publication Date Title
CN108536543B (en) Receive queue with stride-based data dispersal
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
US20100306365A1 (en) Push-back mechanism for pub/sub brokers
RU2007148416A (en) UNITED ARCHITECTURE FOR REMOTE NETWORK ACCESS
JPH11143655A (en) Printing system, printing method and printer
US9014211B2 (en) Reducing the maximum latency of reserved streams
US11177969B2 (en) Interface device and data communication method
WO2023162128A1 (en) System, method, and program for collecting data
WO2023162130A1 (en) Data collection system, method, and program
CN112398754A (en) Data transmission method, device, medium, electronic equipment and network access equipment
JP2010093370A (en) Edge node and band control method
JP2009188655A (en) Communication control method, information processing system, information processor, and program
WO2023162127A1 (en) System, method, and program for collecting data
WO2014010189A1 (en) Proxy device, communication system, program
WO2023012878A1 (en) System, method, and program for collecting data
WO2023162134A1 (en) Data collecting system, method and program
JP6620760B2 (en) Management node, terminal, communication system, communication method, and program
JP6488557B2 (en) Communication control system, communication system, communication control method, and communication control program
WO2018142866A1 (en) Transfer device, transfer method and program
JP2002163185A (en) Method and device for contents distribution
EP3955115B1 (en) Flexible link level retry for shared memory switches
JP6656099B2 (en) Control device and its operation method, communication relay device and its operation method, and communication system and its control method
JP2002183014A (en) Contents distribution system and method
KR102066591B1 (en) Apparatus and method for optimizing resource of system based on self-adaptive for natwork application

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

Country of ref document: EP

Kind code of ref document: A1