The present disclosure relates to a communication system and a communication method that control the time of a terminal.
In recent years, IoT (Internet of Things) has started to spread, and the number of terminals (IoT terminals) that perform operation and communication based on a specific schedule is increasing. Examples include periodic transmission of log information from IoT sensors or an IoT GW (gateway) (which includes both a pattern of transmission at a specific time and a pattern of transmission at a specific cycle), and utterance, operation of an IoT terminal, or guidance of human behavior by a smart speaker at a reserved time.
When many IoT terminals perform the above operations, degradation in quality occurs due to an increase in the load on the server that collects IoT data or the congestion in the network (NW). It has been reported that, when actually simulating a situation in which IoT GWs start uploading data at a specific cycle, an increase in delay occurs when the transmission timings overlap (see, e.g., Non-Patent Literature 1).
In addition, the timing of generating periodic traffic depends on the time that the IoT terminal has, and, if no special setting is made, the IoT terminal often transmits data at a cycle of several seconds, several minutes, or several hours on the basis of the time of 0:00, or transmits data at a specified time. Therefore, the transmission timings of IoT terminals are difficult to disperse in time, and traffic is likely to occur in a burst at a specific time.
As a method for alleviating such congestion in the NW, there has been disclosed a technique in which a terminal communicates with a dedicated server in the NW to appropriately determine the transmission time for uploading and the content acquisition time for downloading (see, e.g., Non-Patent Literature 2). In the technique of Non-Patent Literature 2, a dedicated server is installed in a telecommunications carrier NW, and notifies terminals subordinate to the NW when communication is possible to alleviate congestion.
However, since the technique of Non-Patent Literature 2 requires communication with the server every time communication occurs, it has a problem that it is not efficient for alleviating periodic traffic such as that of IoT terminals. Therefore, it is less effective for applications with severe delay requirements.
Here, as load balancing methods for applications with relatively severe delay requirements, there have been known the following two techniques:
(A) A technique of providing a transfer device in the NW with a large enough buffer to drop the transfer bit rate; and
(B) A technique of controlling buffers of a plurality of transfer devices to drop the transfer bit rate as the entire NW (see, e.g., Non-Patent Literature 3).
The technique (A), has a problem that introduction of a dedicated transfer device is required.
In addition, the techniques (A) and (B) also have a problem that, when a large upload traffic has occurred, the delay increases if the amount of buffer or the number of devices is increased, resulting in degradation in communication quality or retransmission associated therewith, and the traffic amount can further increase.
In addition, when both the terminal and the application server can be controlled, it is also possible to configure them to cause an event or communication to occur at a time slightly different from the set time. For example, when an alarm is set at 7:00 with a smart speaker, it is set in granularity in minutes on the GUI (Graphical User Interface), but the server that controls the smart speaker can also control the alarm generation time in seconds or milliseconds.
However, this control requires implementation of a new function in individual applications, terminals, and servers, and it is required to implement the function in many pieces of equipment in order to perform load balancing throughout the communication network. Since it is difficult to add functions to end terminals, this control has a problem that it is difficult for NW operators to apply it. In order for NW operators to eliminate communication congestion, it is desirable that the NW operators can control many applications executed on terminals.
The above-described problems are summarized as follows.
The first problem is to establish a scalable traffic alleviation approach for larger bursty server loads and NW loads arising from automatic control equipment such as IoT terminals or their associated equipment operations or actions, and the like.
Then, the second problem is to make the traffic alleviation approach easy for telecommunications carriers to implement.
In order to solve the above problems, an object of the present invention is to provide a communication system and a communication method that can avoid network congestion using a simple approach.
In order to achieve the above object, a communication system according to the present invention is configured to cause a time different from the reference time (absolute time) for each IoT terminal to be falsely recognized as the reference time to synchronize with.
Specifically, a communication system according to the present invention includes
a time distribution unit that distributes a synchronization time to a plurality of terminals that periodically generate traffic,
in which the time distribution unit distributes a time different from a reference time to at least one of the terminals as the synchronization time.
Further, in a communication method according to the present invention, in a communication system in which a synchronization time is distributed to a plurality of terminals that periodically generate traffic, a time different from a reference time is distributed to at least one of the terminals as the synchronization time.
A terminal in a network has a function of setting a time notified from a time synchronization server or the time in a time synchronization packet transferred from an upper network as a reference time and synchronizing with this. This communication system and this communication method utilize this function. The time synchronization server in the network notifies a time different for each terminal as the reference time. Further, a transfer device shifts the time in the time synchronization packet and sets it as the time different for each terminal. Thus, since the reference time is shifted for each terminal, traffic is distributed. In addition, this approach can be realized without adding a new function to all pieces of equipment. Therefore, the present invention can provide a communication system and a communication method that can avoid network congestion using a simple approach.
Preferably, the communication system according to the present invention further includes an analysis unit that collects information on the traffic from the terminals, and determines the time different from the reference time.
In the communication system according to the present invention, the reference time is a standard time notified from an upper stratum of the communication system, and the time distribution unit is a time synchronization server that generates the time different from the reference time based on the standard time.
In the communication system according to the present invention, the reference time is a time notified from a time synchronization server in an upper network of the communication system via a time synchronization packet, and the time distribution unit is a transfer device that rewrites the time in the time synchronization packet to the time different from the reference time.
Note that the above inventions can be combined as long as the combination is possible.
The present invention can provide a communication system and a communication method that can avoid network congestion using a simple approach.
Embodiments of the present invention will be described with reference to the accompanying drawings. The embodiments described below are examples of the present invention, and the present invention is not limited to the embodiments below. Note that, in the specification and the drawings, components having the same reference numeral shall indicate the same components.
(Gist of the Invention)
A communication system of the present invention includes a time distribution unit 12 that distributes a synchronization time to a plurality of terminals 11 that periodically generate traffic, in which the time distribution unit 12 distributes a time different from a reference time to at least one of the terminals as the synchronization time.
The communication system of the present invention prevents overlapping of transmission timings from a plurality of terminals by utilizing a time synchronization protocol.
In a first approach of the communication system of the present invention, the reference time is a standard time notified from an upper stratum of the communication system, and the time distribution unit 12 is a time synchronization server that generates the time different from the reference time based on the standard time. In the first approach, as shown in
In a second approach of the communication system of the present invention, the reference time is a time notified from a time synchronization server in an upper network of the communication system via a time synchronization packet, and the time distribution unit 12 is a transfer device that rewrites the time in the time synchronization packet to the time different from the reference time. In the second approach, as shown in
The analysis unit 13 acquires traffic information in a NW such as in a communication carrier network, and determines a distributed time to the terminal according to the traffic pattern of the terminal 11. Originally, the time synchronization protocol fine-tunes the distributed time based on network delay and the like. The analysis unit 13 acquires the generation cycle of traffic generated as client information, the bit rate at the time of generation of traffic, and the like from the terminal 11, and determines the distributed time. The time determined by the analysis unit 13 is notified from the time synchronization server or the transfer device to the terminal 11. That is, this communication system can smooth traffic and reduce congestion by controlling the distributed time from the time synchronization server or the transfer device to each terminal.
For example, when the analysis unit 13 detects that an event in which a traffic amount is generated in a burst has occurred periodically, it detects the IP address of the terminal 11 generating the periodic traffic. Then, the analysis unit 13 performs calculation such as increasing the shift amount for the time of distribution to the terminal 11 if the traffic amount is large, and decreasing the time shift amount if the traffic amount is small.
When the time distribution unit 12 is a time synchronization server, the time synchronization server does not distribute a time distributed from the upper stratum as it is, but determines an actual distributed time based on the time distributed from the upper stratum and client information subordinate to the time synchronization server. Further, when the time distribution unit 12 is a transfer device, the transfer device does not distribute a time synchronizing packet with the standard time transmitted from the upper network as it is, but determines a time to which the time synchronizing packet is rewritten based on the standard time and client information subordinate to the transfer device. The terminal 11 operates with an existing time synchronization protocol, and RTC (Real-Time Clock) is rewritten to the distributed time.
In addition to time synchronization that takes into account the delay of a time synchronization packet and the like, this communication system includes a function group for exchanging NW information so that a time considering the NW state and traffic pattern can be distributed to each terminal 11.
A NW 50 monitors traffic of users (terminals 11) subordinate to the NW in a NW information acquisition unit 51, and calculates statistical amounts or feature amounts to extract terminals 11 that generate a traffic pattern in a NW information processing unit 52. NW information generated by the NW information processing unit 52 is transmitted from a NW information transmission unit 53 to the time synchronization server 12 and the transfer device 12. The time synchronization server 12 and the transfer device 12 performs time control based on the information.
Further, the NW information transmitted from the NW 50 may be routed through a control server 70 before reaching the time synchronization server 12 and the transfer device 12. In that case, a control amount (the shift of a distributed time and an amount of transfer delay to be given) to be applied by the time synchronization server 12 and the transfer device 12 to each client is derived by a control information generation unit 62 in the control server 70. A control information transmission unit 63 transmits the control amount directly to the time synchronization server 12 and the transfer device 12.
Functions common to the case of
1-1. The time synchronization server (12, 70) randomly distributes a time to the terminal 11.
1-2. The analysis unit 13 controls the shifted time for each terminal 11 in accordance with a specific algorithm. (Example) The time shift is increased for clients with a high bit rate among terminals contributing to burst traffic.
The order of the width of the shifted time does not matter (examples where shifting methods with various time widths are conceivable are shown below as reference).
(Example 1) In the case of IoT traffic, a shift amount may be on the order of milliseconds.
(Example 2) In such a case that reception of video streaming is started at a specific time, a shift amount in seconds is required. This is because the bit rate tends to increase for a few seconds at the start of viewing for accumulation in a buffer.
Next, the case where the time synchronization server 12 is provided shown in
3A-1. A case to notify a shifted time as shown in
3A-2. A case of notifying both the correct time and a shifted time as shown in
3A-3. A case of notifying the correct time and a shifted time width as shown in
[4A. Correction of Shift Amount of Time]
These cases correspond to the cases in
4A-1. An OS and application basically recognize the shifted time distributed from the time synchronization server, but rewrite log information to have the standard time (correct time).
As shown in
4A-2. The time of the OS is set to the standard time, and the time is converted by an interface with the application. The time recognized by the application is shifted.
As shown in
4A-3. The standard time (so-called correct time) in the region is displayed on the UI.
As shown in
[5A. Combination of Notified Contents and Synchronization Method]
5A-1. Although the standard time is notified to the terminal on average, a time is distributed as needed so that the time with which the terminal synchronizes varies around the standard time. As shown in
5A-2. A time is distributed so that the time with which the terminal synchronizes always advances or is delayed from the standard time. As shown in
[6A. Determination of Distributed Time to Each Terminal 11 in Time Synchronization Server 12]
6A-1. The time synchronization server 12 derives it based on the correct time and client information.
6A-2. The control server 60 derives a distributed time to each terminal 11, and transmits it to the time synchronization server 12 as part of the client information.
Subsequently, the case where the transfer device 12 is provided shown in
Examples of the transfer device include the following devices:
3B-1. Switches and routers in the NW
3B-3. A firewall and a proxy server located in front of the terminal
3B-4. A firewall installed on the terminal itself
[4B. Methods of Controlling Time Synchronization Packet]
The transfer device 12 shifts the time recognized by the terminal 11 by the following approaches.
4B-1. For a time synchronization packet transferred from the time synchronization server 70 in an upper network or a packet from the terminal 11, the transfer device 12 changes the order of queuing, or holds it in a buffer for a specific time period and then transfers it, thereby giving a delay. Hereinafter, this control will be referred to as “delay giving control”.
4B-2. The transfer device 12 rewrites a message corresponding to the distributed time in a time synchronization packet transferred from the time synchronization server 70 in the upper network. Hereinafter, this control will be referred to as “time rewriting control”.
[5B. Time Synchronization Packets to Be Controlled]
The transfer device 12 can perform the delay giving control only for uplink packets as shown in
[6B. Determination of Distributed Time to Each Terminal 11 in Transfer Device 12]
6B-1. The time synchronization server 70 derives it based on the correct time and client information.
6B-2. The control server 60 derives a distributed time to each terminal 11, and transmits it to the transfer device 12 as part of the client information. The transfer device 12 uses the time written in the information as the distributed time.
The communication method of the present invention is characterized in that a time distribution server (which corresponds to a time synchronization server or the like) that transmits time information to terminals (such as IoT equipment) distributes a time different from the standard time for each terminal, and the terminal performs communication on the basis of the distributed time. Further, the communication method of the present invention is characterized in that, for a time synchronizing packet transmitted from a time distribution server on the Internet to a terminal, a node or the like in the middle of the path performs transfer control or rewrites the packet, thereby causing the terminal to recognize a different time, and the terminal performs communication on the basis of the time.
In the present invention, the above features provide the effects that, since negotiation of transmission timing for each session is not required for a terminal that generates periodic traffic, communication resources can be utilized more efficiently, so it is possible not only to alleviate NW congestion but also suppress degradation in communication quality.
[Effect 1 of the Invention]
Since negotiation of transmission timing for each session is not required for a terminal that generates periodic traffic, the present invention can more efficiently utilize communication resources than the technique of Non-Patent Literature 2.
[Effect 2 of the Invention]
The occurrence time of a reserved event can be controlled from a network operator. The communication generation timing in a plurality of applications of the terminal can also be controlled from the network operator.
[Effect 3 of the Invention]
Degradation in communication quality is less likely to occur even when the amount of data generated in association with an event is large.
[Effect 4 of the Invention]
Since major modifications to terminals and an existing time synchronization server are not required, implementation is easy compared to the techniques of Non-Patent Literatures 1 to 3 that require implementation of a new protocol, dedicated equipment, or application.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/JP2020/014760 | 3/31/2020 | WO |