System, method and program for collecting data

Abstract

A purpose of the present disclosure is to provide a system in which even when data is collected from multiple data sources, no large amounts of network resource is necessary.　The present disclosure relates to a system for collecting data from multiple data sources into a serve, said system comprising a path management controller that manages communication paths between the server and the multiple data sources. The path management controller adjusts the sectional length of the communication path from each of the multiple data sources to the server so as to reduce the times required for generating the communication paths along which to transmit the data from the multiple data sources to the server.

Description

[Technical field]

[0001] The present disclosure relates to communication control for data collection. [Background technology]

[0002] With the development of user terminals, sensors, and in-vehicle systems, the number of sensors and the amount of data generated by each sensor are increasing dramatically. When collecting such data, the communication processing on the receiving side can become a bottleneck in conventional communication methods.

[0003] RDMA (Remote Direct Memory Access) is being considered as a high-speed data transfer method. With RDMA, data is transferred from the memory of a local computer to the memory of a different remote computer using DMA (direct data transfer between peripheral devices and main memory (RAM) without going through the CPU). Because of this, RDMA does not require CPU processing for data transfer, and can avoid the bottleneck on the receiving side.

[0004] A remote transfer technology using this RDMA has been proposed (for example, see Non-Patent Document 1). However, Non-Patent Document 1 states that in order to transfer data using RDMA in a wide-area communication network, it is necessary to set a communication path for each flow in advance. Therefore, when collecting data from multiple data sources, a large amount of network resources is required. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "One person, one wavelength" for ultra-low latency at 100Gbps, moving away from TCP / IP, Nikkei Electronics, 2021-03, P40-47 Summary of the Invention [Problem to be solved by the invention]

[0006] The present disclosure aims to provide a system that does not require a large amount of network resources even when collecting data from multiple data sources. [Means for solving the problem]

[0007] The disclosed system and method include: A system for collecting data from multiple data sources into a server and a method executed by the system, comprising: a path management controller for managing communication paths between the plurality of data sources and the server; The path management controller adjusts the section length of a communication path from each of the multiple data sources to the server so as to shorten the time required to generate a communication path for transmitting data from the multiple data sources to the server.

[0008] The path management controller device and method disclosed herein include A path management controller device provided in a system that collects data from a plurality of data sources into a server, and a method executed by the path management controller device, comprising: The path management controller device managing communication paths between the plurality of data sources and the server; The section length of a communication path generated when transmitting data from each of the plurality of data sources to the server is adjusted so as to reduce the time required to generate the communication path when transmitting data from the plurality of data sources to the server.

[0009] The controller, data source, and other devices of the present disclosure may be realized by a computer and a program, and the program may be recorded on a recording medium or provided through a communication network. The program of the present disclosure is a program for causing a computer to realize each functional unit of the device according to the present disclosure, and is a program for causing a computer to execute each step of a method executed by the device according to the present disclosure. Effect of the Invention

[0010] 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 a large number of data sources. [Brief description of the drawings]

[0011] [Figure 1] 1 illustrates an example system configuration of the present disclosure. [Diagram 2] 1 shows an example of the configuration of a communication network. [Diagram 3] An example of a server configuration is shown. [Figure 4] An example of a data source configuration is shown below. [Diagram 5] An example of information stored in a requirements table of each data source is shown below. [Figure 6] 2 shows an example of the configuration of a transmission controller. [Figure 7] 13 is an example of a transmission policy decision sequence. [Figure 8] 13 shows an example of an operation of a transmission policy decision function. [Figure 9] 13 illustrates an example of information stored in a transmission policy table. [Figure 10] 1 shows an example of the configuration of a path management controller. [Figure 11] 1 shows an example of a communication path management table. [Figure 12] 13 shows an example of the operation of the path design function. [Figure 13] An example of a communication path design is shown below. [Figure 14] An example of transmitting sensing data from data source B to a server is shown. [Figure 15] An example of sending sensing data from a data source A to a server is shown. [Figure 16] An example of transmitting sensing data from a data source C to a server is shown. [Figure 17] An example of a communication path design is shown below. [Figure 18]13 shows an example of an operation of a transmission policy decision function. [Figure 19] 13 shows an example of information stored in the adjusted transmission policy table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, the 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 forms with various modifications and improvements based on the knowledge of those skilled in the art. Note that components with the same reference numerals in this specification and drawings are assumed to indicate the same components.

[0013] (First embodiment) 1 shows an example of a system configuration of the present disclosure. The system of the present disclosure includes a plurality of data sources 10, a transmission control controller 20, a path management controller 30, and a server 40. The plurality of data sources 10, the transmission control controller 20, the path management controller 30, and the server 40 are connected via a communication network 80. The data sources 10 are terminals having user-side sensing data. The server 40 is a terminal that collects data from the data sources.

[0014] In this embodiment, an example is shown in which the transmission control controller 20 and the path management controller 30 are separately arranged, but these controllers may be provided in a common device, or may be composed of multiple devices arranged in a distributed manner. The device of the present invention 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.

[0015] 2 shows an example of the configuration of a communication network 80. The communication network 80 is composed of a plurality of network devices 81. In this embodiment, the network devices 81 used between the data source 10 and the server 40 are determined in advance. For example, the data source 10A and the server 40 are connected by network devices 81A and 81B, the data source 10B and the server 40 are connected by network devices 81A and 81C, and the data source 10C and the server 40 are connected by network devices 81D and 81E.

[0016] When each of network devices 81A-81E receives data addressed to server 40 from data sources 10A-10C, it knows which network device to transfer the data to. Therefore, even if data sources 10A-10C do not know which network device 81 to use, if they specify server 40 and transmit data, the data is sent to server 40. Thus, the present disclosure makes it possible to transfer data losslessly and at a wide bandwidth when a communication path is generated.

[0017] In this disclosure, in order to realize data transfer by RDMA, a method is proposed for allocating a lossless and wideband communication path to a necessary data source 10 at a necessary timing. In the system of this disclosure, when data to be transmitted to the server 40 occurs, each of the multiple data sources 10 generates a communication path at a transmission timing determined by the transmission policy of the own device, using a network device 81 determined for the own device. This allows each data source 10 to autonomously transmit sensing data to the server 40 based on the transmission policy of the own device.

[0018] The transmission policy can be exemplified as follows. First transmission policy: A communication path is generated immediately after data is generated, data is transferred, and the communication path is released immediately after the data transfer is completed. Second transmission policy: A communication path is generated after a certain amount of data has accumulated, and data transfer is performed, and the communication path is immediately released after the data transfer is completed. Third transmission policy: A communication path is created immediately after data is generated, data is transferred, and the communication path is maintained for a certain period of time even after the data transfer is completed. Fourth transmission policy: A communication path is generated and data is transferred after a certain amount of data has accumulated, and the communication path is maintained for a certain period of time even after the data transfer is complete.

[0019] In this embodiment, by providing the transmission control controller 20, a transmission policy that matches the data transfer requirements of the data source 10 is distributed. Then, each data source 10 autonomously transmits sensing data according to the transmission policy that takes into account the sensor characteristics and the data transfer requirements for each application. In this way, this embodiment controls the trade-off between the immediacy of data transmission and the reduction in the communication path usage time.

[0020] When a communication path is established between the data source 10 and the server 40, communication quality is ensured and highly reliable data transfer is possible, but it takes time to generate the communication path. Therefore, in this disclosure, the path management controller 30 adjusts the length of each communication path so as to shorten the time required to generate the communication path. This will be described in detail below.

[0021] 3 shows an example of the configuration of the server 40. The server 40 includes a data receiving function 41, a memory 42, and an application 43. The data receiving function 41 receives the sensing data from each data source 10 . The memory 42 stores the sensing data from the sensor 50 . The application 43 collects sensing data from the sensor 50. The application 43 is any application that collects any sensing data detected or generated by a user terminal, a sensor, an in-vehicle system, or the like.

[0022] 4 shows an example of the configuration of the data source 10. The data source 10 includes a requirement notification function 11, a transmission policy receiving 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.

[0023] The generated data storage function 17 stores the sensing data from the sensor 50 . The requirement notification function 11 reads out the data transfer requirements from the requirement table 18, and notifies the transmission controller 20 of the read out data transfer requirements. The transmission policy receiving function 12 receives a transmission policy from the transmission controller 20 . The data transmission timing control function 13 controls the communication path setting function 14 , the data transmission function 15 and the communication path release function 16 in accordance with the transmission policy table 19 . The communication path setting function 14 transmits a path connection request to the path management controller 30 . The data transmission function 15 transmits the sensing data stored in the generated data storage function 17 to the server 40 . The communication path release function 16 sends a path release request to the path management controller 30 . The requirements table 18 stores the data transfer requirements for each data source 10 . The transmission policy table 19 stores the policy for transmitting the sensing data from the data source 10 to the server 40 .

[0024] 5 shows an example of information stored in the requirement table 18 for each data source. In the requirement table, the allowable delay time, data generation frequency, and data generation amount of each data source 10 are stored as data transfer requirements, linked to the application. The allowable delay time is the allowable delay time from when data is generated until it reaches the server. The data generation amount is the amount of data generated at one time in the sensor 50. The data generation frequency and data generation amount in the sensor 50 are not limited to being constant. In that case, the average data generation frequency and average data generation amount, which are average values ​​for each sensor 50, can be used.

[0025] 6 shows an example of the configuration of the transmission controller 20. The transmission controller 20 includes a requirement receiving function 21, a transmission policy determining function 22, a transmission policy distribution function 23, and a transmission policy determining rule 24.

[0026] 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 requirements 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. The requirement receiving function 21 of the transmission controller 20 receives the data transfer requirement from the data source 10. The transmission policy determining function 22 determines a transmission policy for each data source 10 in accordance with the data transfer requirement, in accordance with the transmission policy determining rules 24 (S102). The transmission policy distribution function 23 of the transmission controller 20 distributes the determined transmission policy to each data source 10 (S103).

[0027] FIG. 8 shows an example of the operation of the transmission policy decision function 22. In FIG. When the transmission controller 20 acquires data transfer requirements from the data source 10 (S11), it determines the requirements for the allowable delay time (S12). If the allowable delay time requirement is 100 ms or less (Yes in S12), it decides on a method of generating a path immediately after data generation and transmitting the data (S13). On the other hand, if the allowable delay time requirement is more than 100 ms (No in S12), it decides on a method of accumulating a certain amount of sensing data and transmitting it (S14). Next, the transmission controller 20 judges the data generation frequency (S15). If the data generation frequency is 4 times / s or less (Yes in S15), a method is decided to release the path immediately after data transmission (S16). On the other hand, if the data generation frequency is more than 4 times / s (No in S15), a method is decided to wait a certain time after data transmission is completed and then release the path (S17).

[0028] For example, in the case of the data transfer requirements shown in FIG. 5, the transmission policy decision function 22 makes the decision as follows. Data Source A: Since the set value of the allowable delay time is 1000 ms and the set value of the data occurrence frequency is 4 times, 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 occurrence frequency is set to 10 times, the transmission controller 20 determines the fourth transmission policy as the transmission policy. Data Source C: Since the allowable delay time is set to 100 ms and the data occurrence frequency is set to 5 times, the transmission controller 20 determines the transmission policy to be the third transmission policy. As a result, the transmission policy as shown in FIG.

[0029] 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, a 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.

[0030] Here, the data transfer requirements may include application information. In this case, the transmission controller 20 sets the threshold value in consideration of the requirements included in the application information in steps S12 and S15. In addition, the transmission policy determined by the transmission policy determination function 22 is transmitted to the path management controller 30.

[0031] 10 shows an example of the configuration of the path management controller 30. The path management controller 30 comprises a path setting request receiving function 31, a path setting function 32, a path setting location table 33, a path design function , and a path management table .

[0032] The path setting request receiving 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 in response to a request from each data source 10 to connect or release the communication path. The path setting location table 33 manages setting information (creation / release) of the communication paths from each data source 10 to the server 40 . The path design function 34 designs each communication path so that the time required to generate the communication path is shortened when the transmission policy from the transmission controller 20 is executed. The design here is reflected in the path setting location table 33. The path management table 35 manages the amount of data required to execute the transmission policy from the transmission controller 20 for each path.

[0033] In this embodiment, according to the transmission policy of the data source 10A, data is transmitted after 15 MB of data has accumulated. Since the data generation frequency of the data source 10A is 4 times / s, 15 MB of data is transmitted once / s. Therefore, the path design function 34 organizes the creation frequency and release frequency of each communication path and the data communication volume in the path management table 35, as shown in FIG.

[0034] The path design function 34 designs communication paths based on the information in the path management table 35. For example, the path design function 34 determines resources to be allocated to each communication path. Here, if the section length of a communication path is short, the time required to generate the communication path is short. Therefore, for sections where communication paths are frequently generated, the section length is shortened. This shortens the path generation time, making it possible to transmit data immediately when the data is generated.

[0035] The path design function 34 lengthens the section length for a section where the frequency of generation of a communication path is low. Since data is generated infrequently for this communication path and there is a low possibility of contention, the communication path may be used exclusively by multiple flows. This reduces the need to generate new paths and shortens the time it takes to generate a communication path. In addition, depending on the communication path, the amount of data on the communication path may be adjusted. In such a case, the path design function 34 may allocate more resources to the communication path that passes through a flow that generates a large amount of data.

[0036] FIG. 12 shows an example of the operation of the path design function 34. As shown in FIG. The communication path generation frequency and data volume are read from the path management table 35 (S31), and it is determined whether the communication path generation frequency is equal to or greater than a predetermined threshold (6 times / s in this embodiment) (S32). If the generation frequency is equal to or greater than 6 times / s, the section length is maintained (S33). On the other hand, if the generation frequency is less than 6 times / s, the communication path is extended by one to the next section (S34). It is determined whether the amount of data of the communication path added in step S33 or S34 is equal to or greater than a predetermined threshold (1 Gbps in this embodiment) (S35). Then, if the amount of data is equal to or greater than 1 Gbps (Yes in S35), the allocated resources of the added communication path are increased (S36).

[0037] For example, since the communication path of data source 10B is generated 10 times / s, step S33 is executed to separate the communication path between network devices 81C and 81A. On the other hand, since the communication path of data source 10C is generated 5 times / s, step S34 is executed to extend the communication path from network device 81E to network device 81D to a communication path from network device 81E to server 40. Also, at this point, there is no communication path with a data volume of 1 Gbps or more. As a result, a communication path as shown in FIG. 13 is designed.

[0038] In this embodiment, sensing data from data sources 10A and 10B join together at network device 81A. In this case, the communication path is separated at network device 81A. For the communication path from network device 81A to server 40, data sources 10A and 10B may generate a communication path individually, or may generate a communication path to be used jointly in advance. In this case, when a data source that uses that communication path appears, that communication path is assigned to that data source.

[0039] An example of setting a communication path when the data sources 10A to 10C transmit sensing data will be described with reference to Fig. 14 to Fig. 16. In this embodiment, a communication path as shown in Fig. 13 is designed. Therefore, a communication path from the data source 10A to the server 40 can be generated simply by generating a communication path from the network device 81B to 81A, and the time required to generate the communication path can be reduced. The same applies to the data source 10B.

[0040] 14 shows an example of transmission of sensor data from the data source 10B to the server 40. The data source 10B transmits the sensor data in accordance with 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). When the path management controller 30 receives the communication path connection request, it sets the communication path between the network devices 81A and 81C and creates the communication path (S202). When the communication path creation is completed, the path management controller 30 transmits a communication path creation completion notification to the data source 10B (S203). When the data source 10B receives the communication path creation completion notification, it transmits sensing data to the server 40 (S204-1 and S204-2). Then, for 50 ms, it waits for the transmission of a communication path release request. If sensing data is generated during that time, it transmits the sensing data each time (S204-3). When 50 ms has elapsed 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, it 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).

[0041] 15 shows an example of transmission of sensor data from the data source 10A to the server 40. The data source 10A transmits the sensor data in accordance with 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). When the path management controller 30 receives the communication path creation request, it creates a communication path from the network device 81E to the server 40 (S302). When the communication path creation is completed, the path management controller 30 transmits a communication path creation completion notification to the data source 10A (S303). Then, when the data source 10A receives a communication path creation 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). When the path management controller 30 receives the communication path release request, it releases the communication paths of the network devices 81A and 81B, and transmits a communication path release completion notification to the data source 10A indicating that the communication path has been released (S306).

[0042] 16 shows an example of transmission of sensor data from the data source 10C to the server 40. The data source 10C transmits the sensor data in accordance with the third transmission policy. When data is generated by the sensor 50, the data source 10C transmits a communication path creation 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 waits for the next 20 ms for transmission of a communication path release request. If sensing data is generated during that time, it transmits the sensing data each time (S404-2, S404-3). When 20 ms has elapsed since the last data transmission (step S404-3), the data source 10C transmits a communication path release request to the path management controller 30 (S405). Upon receiving the communication path release request, the path management controller 30 releases the communication paths of the network devices 81D and 81E, and transmits a communication path release completion notification to the data source 10C indicating that the communication path has been released (S406).

[0043] 14 to 16, in this embodiment, a communication path is allocated in a time-sharing manner at the required timing, thereby preventing the exhaustion of network resources and realizing RDMA communication with a large number of data sources. Since a communication path is allocated to the data source 10 that wishes to transmit sensing data only for the period required, the utilization rate of the path can be improved and network resources can be reduced.

[0044] The path management controller 30 has a function for monitoring the amount of data generated by each data source 10 and the creation status of the communication path, and may change the design of the communication path according to the monitoring result. In this case, when the path management controller 30 acquires the data amount of each communication path, it executes steps S31 to S36 again. The monitoring method is arbitrary, and an example is to provide a counter for recording the data amount in the network devices 81A to 81E and read the counter value.

[0045] For example, when the frequency of generating a communication path of the data source 10C increases from 5 times / s to 10 times / s, the communication path is divided from the network device 81E to 81D as shown in FIG. 17. The path from the data source 10B to the server 40 may be a path that passes through the network device 81A, or may be a path that passes through the network device 81D. Therefore, the path management controller 30 sets the path from the data source 10B to the server 40 as a path that passes through the network device 81D. Then, the path between the server 40 and the network device 81D is always maintained, and when data of the data source 10B is generated, only a communication path between the network devices 81C-81D is generated, and when data of the data source 10C is generated, only a path between the network devices 81D-81E is generated. When data of the data source A is generated, only a path between the server 40 and the network device 81A is generated.

[0046] Second Embodiment In this embodiment, the transmission controller 20 determines the transmission policy in consideration of the entire NW resources. When the transmission policy is determined, the resource usage amount when each of the data sources A to C executes the transmission policy can be calculated. Any method for calculating the resource usage amount can be used, but for example, the following formula can be used. Resource usage = (path creation overhead + transfer time + path release waiting time) * path creation frequency Transfer time = Amount of data transferred / Communication bandwidth Path generation frequency = Data generation frequency * Data generation amount / Accumulation amount Here, the path creation overhead is a leading portion indicating a connection request for a communication path, and can be any value. In this embodiment, an example of 0.03 seconds is shown. The path release waiting time corresponds to the path release timing in the transmission policy.

[0047] Data Source A The data generation frequency is 4 times / s, the data generation amount is 5MB / time, and the transmission policy is to generate a communication path only after 15MB has accumulated. Path generation frequency: 1.3 times / s = (5[MB / times] x 4[times / s]) / 15[MB] Transfer time: 0.012s = 15[MB] / (10[Gb / s] / 8) Resource usage: 0.056=(0.03+0.012+0)*1.3

[0048] Data source B The data generation frequency is 10 times / s, the data generation amount is 10 MB / time, and the transmission policy is to generate a communication path after 20 MB has accumulated and to wait 0.05 seconds for the communication path to be released. Path generation frequency: 5 times / s = (10[MB / time] x 10[times / s]) / 20[MB] Transfer time: 0.016s = 20[MB] / (10[Gb / s] / 8) Resource usage: 0.48=(0.03+0.016+0.05)*5

[0049] Data Source C The data generation frequency is 5 times / s, the data generation amount is 10 MB / time, and the transmission policy is to immediately generate a communication path and wait 0.02 seconds for the communication path to be released. Path generation frequency: 5 times / s Transfer time: 0.008s = 10[MB] / (10[Gb / s] / 8) Resource usage: 0.29=(0.03+0.008+0.02)*5

[0050] If the resource usage of each data source is 0.056, 0.48, and 0.29, the total resource usage when data sources A, B, and C execute the sending policy is 0.826.

[0051] The transmission policy decision function 22 adjusts the transmission policy by referring to the network resource DB 25. An example of the operation of the transmission policy decision function 22 is shown in FIG. The resource usage is calculated using the set transmission policy (S21). Next, the network resources are read from the network resource DB 25, and the total resource usage amount is calculated (S22). Next, it is determined whether the total resource usage amount is within a set threshold value (S23). If the total resource usage falls within the set threshold (Yes in S23), determination of the set transmission policy is completed.

[0052] On the other hand, if the total resource usage is not within the set threshold (No in S23), the transmission policy of each data source is adjusted so that the total resource usage is equal to or less than the set threshold. Specifically, in order of the loosest transmission policy (S24), the path release timing is advanced (S25) or the accumulation amount at the path creation timing is increased (S26). This makes it possible to shorten the time that a data source 10 with a loosest transmission policy consumes network resources, and reduce the total resource usage.

[0053] 5, the allowable delay time of data source A (1000 ms) > the allowable delay time of data source B (200 ms) > the allowable delay time of data source C (100 ms). In this case, in step S24, the transmission policies are adjusted in the order of data sources A, B, and C. If the result of step S23 is Yes with the adjustment of the transmission policy of data source A alone, the process ends at that point, and if adjustment of the transmission policy of data source B is also required, the transmission policy of data source B is also adjusted. In this way, the present disclosure adjusts the transmission policies in order of the longest allowable delay time.

[0054] A detailed description will be given of a case where the set threshold is 0.8, the path release waiting time of the transmission policy is reduced by 10% in step S25, and the data accumulation amount is increased by the amount of data generated at one time in step S26.

[0055] The path release timing for data source A is after data transmission is completed, and the path release waiting time is 0, so step S26 is executed. In step S26, the data accumulation amount is increased by 5 MB, which corresponds to the amount of data generated at one time. As a result, the transmission policy is adjusted so that data is transmitted only after 20 MB has accumulated, as shown in FIG.

[0056] The sending policy of data source A is set to generate a communication path after 20MB has accumulated. The resource usage of data source A in this case can be calculated as follows: Path generation frequency: 1.0 times / s = (5[MB / time] x 4[times / s]) / 20[MB] Transfer time: 0.016s = 20[MB] / (10[Gb / s] / 8) Resource usage: 0.046=(0.03+0.016+0)*1.0

[0057] The transmission policy decision function 22 calculates the total resource usage when data sources A, B, and C execute the transmission policy based on the adjusted transmission policy of data source A, and compares it with the threshold. For example, the resource usage of data source A after adjustment is 0.046, so the total resource usage when data sources A, B, and C execute the transmission policy is 0.816. Since the set threshold is 0.8, the transmission policy of data source B, which has the next longest allowable delay time, is adjusted.

[0058] Since the path release timing for data source B is to release the path if no data is generated for 50 ms, step S25 is executed. In step S25, 5 ms, which is 10% of 50 ms, is shortened. As a result, the transmission policy is adjusted so that the path will be released if no data is generated for 45 ms, as shown in FIG.

[0059] The transmission policy of data source B is set to release if no data is generated for 45 ms. In this case, the resource usage of data source B is 0.455 = (0.03 + 0.016 + 0.455) * 5.

[0060] The transmission policy determination function 22 calculates the total resource usage when data sources A, B, and C execute the transmission policy based on the adjusted transmission policy of data source B, and compares it with the threshold. For example, the resource usage of data source B after adjustment is 0.455, so the total resource usage when data sources A, B, and C execute the transmission policy is 0.719. The set threshold is 0.8, which is below the threshold, so the adjustment is completed.

[0061] In this way, the transmission policy decision function 22 repeats steps S24 to S26 until the total resource usage falls within the set threshold. Here, the process of step S25 may be executed for a transmission policy in which the path generation timing is immediately after data generation, and step S26 may be executed for other transmission policies. Also, step S25 may be further executed for the transmission policy for which step S26 has been executed.

[0062] When the total resource usage falls within the set threshold (Yes in S23), the transmission policy determination function 22 ends the determination of the set transmission policy. When the determination of the transmission policy in the transmission policy determination function 22 ends, the transmission policy distribution function 23 distributes the transmission policy to each data source 10.

[0063] 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, a 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.

[0064] (Effects of the present disclosure) As described above, the present disclosure determines a transmission policy for each data source 10 and generates a communication path for each data source 10 according to the transmission policy, so that the communication paths can be allocated in a time-sharing manner at the required timing. Therefore, the present disclosure can reduce the communication path usage time from each data source 10 to the server 40, facilitate the reuse of communication paths, and reduce the number of communication paths required for the entire communication network 80, in response to the trade-off between the immediacy of data transmission and the reduction in the communication path usage time.

[0065] Therefore, the present disclosure can realize a lossless and wideband communication network 80 with a communication path, and can enable RDMA communication with a large number of data sources without requiring a large amount of network resources. Furthermore, the present disclosure can prevent data loss in the communication network 80, and can realize reliable data transfer using RDMA.

[0066] In the present embodiment, an example has been shown in which the data collected by the server 40 is sensing data, but the present disclosure is applicable to any data that is required to be collected, such as data from user terminals, sensors, and in-vehicle systems.

[0067] In addition, in the above embodiment, an example of setting a lossless and broadband communication path between the data source 10 and the server 40 has been shown, but a transfer path for data whose quality is not guaranteed may also be set as the communication path. [Industrial Applicability]

[0068] The present disclosure can be applied to the information and communications industry. [Explanation of symbols]

[0069] 10, 10A, 10B, 10C: Data Source 20: Transmission control controller 30: Path management controller 40: Server 50: Sensor 11: Requirement notification function 12: Sending policy receiving 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: Requirements table 19: Sending policy table 21: Requirement reception function 22: Transmission policy decision function 23: Sending policy distribution function 24: Transmission policy decision rule 31: Path setting request receiving function 32: Path setting function 33: Path setting location table 34: Path design function 35: Path management table 41: Data reception function 42: Memory 43: Application 80: Communication Network 81A, 81B, 81C, 81D, 81E: Network equipment

Claims

1. In a system that collects data from multiple data sources into a server, a path management controller for managing communication paths between the plurality of data sources and the server; the path management controller adjusts section lengths of communication paths from each of the plurality of data sources to the server so as to reduce a time required for generating communication paths for transmitting data from the plurality of data sources to the server; system.

2. The path management controller, For a section where the frequency of communication path generation is less than a threshold, the section length is increased; By maintaining the section length for sections where the frequency of communication path generation is above a threshold, determining a section length of a communication path from each of the plurality of data sources to the server; The system of claim 1 .

3. the path management controller, when there is a network device at which data from two or more data sources among the plurality of data sources joins, divides the section length at the network device; 3. A system according to claim 1 or 2.

4. The path management controller A communication path for transferring data from two or more data sources among the plurality of data sources is generated in advance; assigning the communication path to a data source when the data source using the communication path appears; A system according to any one of claims 1 to 3.

5. The path management controller acquires a frequency of communication path creation in each network device, If there is a section in which the frequency of communication path generation has changed from less than the threshold to equal to or greater than the threshold, the section length of the communication path in that section is adjusted. A system according to any one of claims 1 to 4.

6. A method performed by a system for collecting data from multiple data sources into a server, comprising: The system includes a path management controller that manages communication paths between the plurality of data sources and the server; the path management controller adjusts section lengths of communication paths generated when transmitting data from each of the plurality of data sources to the server so as to shorten a time required for generating the communication paths when transmitting data from the plurality of data sources to the server; method.

7. A path management controller device provided in a system for collecting data from a plurality of data sources into a server, comprising: managing communication paths between the plurality of data sources and the server; adjusting a section length of a communication path generated when transmitting data from each of the plurality of data sources to the server so as to reduce a time required for generating the communication path when transmitting data from the plurality of data sources to the server; Path management controller device.

8. A method executed by a path management controller device included in a system that collects data from a plurality of data sources into a server, comprising: The path management controller device managing communication paths between the plurality of data sources and the server; adjusting a section length of a communication path generated when transmitting data from each of the plurality of data sources to the server so as to reduce a time required for generating the communication path when transmitting data from the plurality of data sources to the server; method.

9. 6. A program for causing a computer to function as the path management controller provided in the system according to claim 1.

Images