JP5887231B2 - COMMUNICATION TERMINAL DEVICE, MESSAGE DISTRIBUTION SYSTEM, AND COMMUNICATION METHOD - Google Patents

Description

  The present invention relates to a communication terminal device, a message distribution system, and a communication method, for example, push distribution using a WebSocket protocol.

  As a method for push-distributing a message from a server to a client terminal, there are an SMS method, a WebSocket method, and the like. The SMS method is disclosed in, for example, Patent Document 1 and Non-Patent Document 1.

  On the other hand, the WebSocket method is disclosed in NPL 2 as RFC 6455 by IETF. The standard development time for the WebSocket method is relatively new as of December 2011.

  Generally, SMS is provided by a telecommunications carrier, as described in Non-Patent Document 1, and generally requires a telephone line contract, so the fee is high. On the other hand, the WebSocket method is less expensive than SMS because it does not require a telephone line contract and only costs packet communication. In this respect, the WebSocket method has attracted attention. WebSocket is a method characterized by maintaining a connection between two parties performing communication. For example, in the WebSocket method, a connection is established with a server in response to a connection request from the client terminal side, and then push distribution from the server becomes possible.

  In the push delivery system, immediacy is not necessarily guaranteed. For this reason, immediate message transmission is desired from the server side to the client terminal installed in the mobile body. In order to send an immediate message, it is necessary to first maintain the connection, and secondly, to detect the disconnection immediately even if an unexpected disconnection occurs, and to connect again.

  Regarding the first requirement, some of the network devices that are used for message transmission, as shown in Non-Patent Document 3, have an idle disconnection that disconnects when a non-communication state reaches a certain time for reducing the load. Some have a function. In order to prevent such disconnection due to continuation of the no-communication state, a connection maintenance signal for maintaining the connection is sent when the no-communication state elapses for a fixed time even if there is no message to be sent.

  Regarding the second requirement, when used on a mobile phone line, it is conceivable that the notification of disconnection of the network device is not received because the radio wave is poor, and the client does not notice the disconnection. In addition, it is conceivable that the client is not aware of the disconnection associated with the network type change such as the mobile line or the WiFi. As a solution to the problem, there is a method of providing a retransmission timer that disconnects the connection when there is no response to the connection maintenance signal for a certain period.

JP 2002-111790 A

http://www.jpo.go.jp/shiryou/s_sonota/hyoujun_gijutsu/keitai/3-1-1.pdf http://tools.ietf.org/html/rfc6455 http://www.hitachi.co.jp/Prod/comp/soft1/manual/cosmi/v0870/APKC/EU070179.HTM

  However, a very large amount of work is required to develop a push communication system that provides an immediate message service as described above. In particular, the amount of work related to the following three items is an issue.

(I) Connection maintenance interval survey In a system used between customers or by the same customer, any one of network components such as a client terminal direct connection network such as a mobile line or a WiFi line and a cloud infrastructure network is changed. Then, the system developer needs to reexamine the connection maintenance interval of the entire system each time. Here, regarding the backbone network (backbone), since information that sets an idle timeout shorter than the above elements is not disclosed, it is assumed that there is no information. An Internet service provider network for publishing the cloud infrastructure is also one of the network components. However, in the following description of the embodiments, it will be omitted for simplicity.

  In addition, when the customer's immediacy (maximum downtime) desired value is changed, the developer needs to reexamine the connection maintenance interval of the entire system each time.

(Ii) Response to dynamic change In an environment where multiple network types are mixed, network type dynamic change cannot be supported.

(Iii) Investigation of connection maintenance interval In particular, it takes time and effort to find a connection maintenance interval that matches the maximum interruption time (immediateness) required by the customer.

  The present invention has been made in view of such circumstances, and provides a technique for reducing the work involved in the development of a push communication system that provides an immediate service.

  In order to solve the above-described problem, in the present invention, message push delivery using the WebSocket protocol is performed between a server device (distribution device) and a communication terminal device (client terminal device). In this communication, a signal for maintaining the WebSocket connection is periodically transmitted from the communication terminal device to the server device. Here, the communication terminal device stores, in the memory, at least connection maintenance interval information for each mobile phone communication carrier, connection maintenance interval information for each cloud platform, and use network configuration information indicating network components used by the user. And hold. Then, the communication terminal device, based on the use network configuration information, the connection maintenance interval specifying process for specifying the connection maintenance interval of the mobile phone communication carrier currently used by the user and the connection maintenance interval of the cloud infrastructure, and the specification The minimum connection maintenance interval determination processing for determining which of the connection maintenance interval of the mobile phone communication carrier and the connection maintenance interval of the cloud infrastructure is the minimum, and the connection for establishing the communication connection with the server device using the minimum connection maintenance interval The establishment process is executed. Here, the connection maintenance interval information for each mobile phone communication carrier and the connection maintenance interval information for each cloud platform are fixed information that does not need to be rewritten, and the use network configuration information is information set for each user.

  According to the present invention, it is possible to reduce the work involved in developing a push communication system that provides an immediate service.

  Further features related to the present invention will become apparent from the description of the present specification and the accompanying drawings. The embodiments of the present invention can be achieved and realized by elements and combinations of various elements and the following detailed description and appended claims.

  It should be understood that the description herein is merely exemplary and is not intended to limit the scope of the claims or the application of the invention in any way.

It is a figure which shows the scene where the 1st Embodiment of this invention is applied. It is a figure which shows schematic structure of the delivery system by the 1st Embodiment of this invention. It is a figure which shows the function structure of 23C of WebSocket server side communication parts. It is a figure which shows the function structure of the WebSocket client side communication part 33B. It is a figure which shows the structural example of portable line connection destination table 33B100. It is a figure which shows the structural example of WiFi connection destination table 33B101. It is a figure which shows the structural example of the connection maintenance space | interval table 33B202 classified by mobile carrier. It is a figure which shows the structural example of WiFi connection maintenance space | interval table 33B203. It is a figure which shows the structural example of the connection maintenance space | interval table 33B204 classified by cloud infrastructure. It is a figure which shows the structural example of the largest connection maintenance space | interval table 33B205. It is a figure which shows the structural example of the connection maintenance retransmission interval table 33B206. It is a figure which shows the structural example of the connection maintenance retransmission frequency table 33B207. It is an example of a structure of utilization network component designation | designated table 33B208. It is a flowchart for demonstrating the connection process of the client terminal device 3 by 1st Embodiment. It is a flowchart for demonstrating the connection signal sending process in connection by 1st Embodiment. It is a flowchart for demonstrating the reconnection process when a disconnection occurs during the connection by 1st Embodiment. It is a figure which shows the element which needs development in the system in embodiment of this invention. It is a flowchart for demonstrating the message transmission process performed by the server (distribution apparatus 2) side. 4 is a diagram illustrating an example of a setting screen (GUI) displayed on a display unit of the administrator terminal device 1. FIG. It is a schematic diagram for showing the application scene of 2nd Embodiment. It is a figure which shows schematic structure of the delivery system by the 2nd Embodiment of this invention. It is a flowchart for demonstrating the connection process which the client terminal device 3 performs by 2nd Embodiment. It is a figure which shows the internal structure of the websocket client side communication part 33B by 3rd Embodiment. It is a flowchart for demonstrating the connection process which a client terminal device performs by 3rd Embodiment.

  The present invention provides a technique for reducing the amount of work required for development of a push delivery system using, for example, a WebSocket protocol.

  Each embodiment of the present invention eliminates the need to reexamine the connection maintenance interval of the entire system for all system components even when the system components change in a network environment between customers or used by the same customer. To do. In addition, each embodiment is to reduce the amount of work for ensuring immediacy within the time requested by the customer including an environment where radio waves are not good.

  Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the accompanying drawings, functionally identical elements may be denoted by the same numbers. The attached drawings show specific embodiments and implementation examples based on the principle of the present invention, but these are for understanding the present invention and are not intended to limit the present invention. Not used.

  This embodiment has been described in sufficient detail for those skilled in the art to practice the present invention, but other implementations and configurations are possible without departing from the scope and spirit of the technical idea of the present invention. It is necessary to understand that the configuration and structure can be changed and various elements can be replaced. Therefore, the following description should not be interpreted as being limited to this.

  Furthermore, as will be described later, the embodiment of the present invention may be implemented by software running on a general-purpose computer, or may be implemented by dedicated hardware or a combination of software and hardware.

  In the following explanation, each information of the present invention will be explained by “table”. However, these information may not necessarily be represented by a data structure of a table, but may be represented by a data structure such as a list, a DB, a queue, or the like. May be. Therefore, “table”, “list”, “DB”, “queue”, etc. may be simply referred to as “information” to indicate that they do not depend on the data structure.

  In addition, when explaining the contents of each information, the expressions “identification information”, “identifier”, “name”, “name”, “ID” can be used, and these can be replaced with each other. It is.

  In the following, each process in the embodiment of the present invention will be described with “... Part” as a subject (operation subject), but each “... Part” may be configured by a program. In this case, since the program performs processing determined by being executed by the processor using the memory and the communication port (communication control device), the processor may be described as the operation subject. Further, the processing disclosed with the program as the subject may be processing performed by a computer such as a management server or an information processing apparatus. Part or all of the program may be realized by dedicated hardware, or may be modularized. Various programs may be installed in each computer by a program distribution server or a storage medium.

(1) 1st Embodiment 1st Embodiment is for reducing the response | compatibility to the static change of a network component.

<Application scene>
FIG. 1 is a diagram illustrating a scene in which the first embodiment is applied. FIGS. 1A to 1C are schematic diagrams respectively when only the mobile carrier A is used, when only the mobile carrier B is used, and only the WiFi network is used on the customer premises. As mentioned above, in a system that is utilized between customers or by the same customer, such network components may change.

  In the scene according to FIG. 1A, the administrator terminal device 1 is connected to the distribution device 2 via the Internet 4. The distribution apparatus 2 is connected to the client terminal apparatus 3 in the mobile body 101 via the Internet 4 and the mobile carrier A network 102. The client terminal device 3 in the mobile body 101 is located in the customer α premises 103 or the customer α premises 104 and communicates with the distribution device 2 using the mobile carrier A network 102.

  In the scene according to FIG. 1B, the administrator terminal device 1 is connected to the distribution device 2 via the Internet 4. The distribution device 2 is connected to the client terminal device 3 in the mobile body 101 via the Internet 4 and the mobile carrier B network 105. The client terminal device 3 in the mobile body 101 is in the customer β premises 106 or the customer β premises 107 and communicates with the distribution device 2 using the mobile carrier B network 105.

  In the scene according to FIG. 1C, the administrator terminal device 1 is connected to the distribution device 2 via the Internet 4. The distribution apparatus 2 is connected to the Internet 4 and a WiFi network 6 including a LAN in the customer's home. Then, the client terminal device 3 in the moving body 101 in the customer γ premises 108 communicates with the distribution device 2 through the WiFi network 6. The customer γ off-premise 109 has no communication means.

  As described above, in order to be able to operate the system operating in FIG. 1A in the scene of FIG. 1B, it is necessary to change the system (static change of network components). When implementing this system change, the connection maintenance interval of the entire system must be examined by every means.

  However, there is a case where the amount of work increases in the investigation of the connection maintenance interval, and a device that can reduce the amount of work is necessary.

  Therefore, the first embodiment provides a configuration for reducing the amount of work when statically changing such network components.

<Configuration of distribution system>
FIG. 2 is a diagram showing a schematic configuration of a distribution system according to the first embodiment of the present invention.
The distribution system according to the first embodiment includes at least one administrator terminal device 1, at least one distribution device 2, and at least one client terminal device 3, and the administrator terminal device 1 and the distribution device 2. Are connected via the Internet 4, and the distribution device 2 and the client terminal device 3 are connected via a mobile phone network 5 and a WiFi network 6.

  The administrator terminal device 1 includes a terminal device 11 including a CPU 11A and a memory 11B, a communication port 12, and an external storage device 13. The external storage device 13 includes an administrator operation transmission unit 13A for instructing the distribution device 2 to perform an operation such as transmission of a message from the administrator, and a display processing unit 13B for displaying a transmission result and the like. Have. Note that the administrator operation transmission unit 13A and the display processing unit 13B are stored as programs, and the CPU 11A executes these programs to realize the respective functions.

  The distribution device 2 includes a terminal device 21 including a CPU 21A and a memory 21B, a communication port 22, and an external storage device 23. The external storage device 23 includes an administrator operation response unit 23A for returning an administrator operation response to the administrator terminal device, a server management unit 23B that collects processing in the device, and a WebSocket server for sending a message by WebSocket. Side communication unit 23C. The server management unit 23B includes a transmission content list table 23B1 that stores frequently sent content and a transmission destination terminal list table 23B2 that stores information of the client terminal device 3. Note that the administrator operation response unit 23A, the server management unit 23B, and the WebSocket server side communication unit 23C are stored as programs, and the CPU 21A executes these programs to realize the respective functions.

  The client terminal device 3 includes a terminal device 31 including a CPU 31A and a memory 31B, a communication port 32, and an external storage device 33. The external storage device 33 includes a client management unit 33A that organizes processing in the client terminal device, a WebSocket client side communication unit 33B for performing communication using WebSocket, and a display processing unit for displaying a message distributed from the distribution device 33C, a mobile line connection unit 33D for connection when the network used by the client terminal device 3 is a cellular phone network, and a WiFi network when the network used by the client terminal device 3 is WiFi and further connecting And a WiFi search / connecting unit 33E to perform. The client management unit 33A, the WebSocket client side communication unit 33B, the display processing unit 33C, the mobile line connection unit 33D, and the WiFi search / connection unit 33E are stored as programs, and the CPU 31A executes these programs. Each function is realized.

<Function of WebSocket server side communication unit>
FIG. 3 is a diagram illustrating a functional configuration of the WebSocket server side communication unit 23C.
The WebSocket server side communication unit 23C includes a connection / disconnection response unit 23C1 for responding to a connection / disconnection request from the WebSocket client side communication unit 33B, and a packet for maintaining the WebSocket connection from the WebSocket client side communication unit 33B. A connection maintenance signal response unit 23C2 for transmitting a response to the message, and a message transmission unit 23C3 that performs message transmission.

<Functions of the WebSocket client side communication unit>
FIG. 4 is a diagram illustrating a functional configuration of the WebSocket client side communication unit 33B.
The WebSocket client side communication unit 33B includes a connection / disconnection unit 33B1 that requests connection / disconnection to the WebSocket server side communication unit 23C, a WebSocket connection maintaining unit 33B2, and a message reception unit 33B3.

  The connection / disconnection unit 33B1 includes a mobile line connection destination table 33B100 for storing connection destination information when the network used by the client terminal device 3 is a mobile phone network, and a network used by the client terminal device 3 is a WiFi network. In this case, a WiFi connection destination table 33B101 for storing connection destination information is stored. Here, the mobile line connection destination table 33B100 may describe not only the connection destination address but also other information necessary for connection such as authentication information.

  The WebSocket connection maintaining unit 33B2 includes a connection maintaining signal transmitting unit 33B200 for transmitting a connection maintaining signal to the WebSocket server side communication unit 23C, and a disconnection for disconnecting the connection when there is no response of the connection maintaining signal Detection unit 33B201, connection maintenance interval table for each mobile carrier 33B202, and WiFi connection maintenance interval table for storing in advance connection maintenance intervals necessary for each network type such as a mobile carrier network, WiFi network, and cloud-based network 33B203, the connection maintenance interval table 33B204 for each cloud platform, the maximum connection maintenance interval table 33B205 for recording the maximum connection maintenance interval that satisfies the maximum disconnection time requested by the customer, and the disconnection detection unit 33B201 responding to the connection maintenance signal. If there is no re Intervals, a retransmission upper limit number of connection wrote respectively maintained retransmission interval table 33B206, the connection maintaining retransmission count tables 33B207, contain, and use network components specified table 33B208 for designating the network component utilized.

  Regarding the message transmission unit 23C3 and the message reception unit 33B3, the WebSocket is a protocol characterized not only in one-way communication from the server to the client side but also in the bidirectional direction including the reverse direction. Although it is a communication means that can be used, it is described here as if it is only one direction from the server to the client side for the sake of simplicity of explanation.

<Mobile line connection table>
FIG. 5 is a diagram illustrating a configuration example of the mobile line connection destination table 33B100.
The mobile line connection destination table 33B100 includes a connection destination URL 501, an authentication user name 502, and an authentication password 503 as configuration items. In the example of FIG. 5, address_a, usr_a, and pw_a are set for each item.

<WiFi connection destination table>
FIG. 6 is a diagram illustrating a configuration example of the WiFi connection destination table 33B101.
The WiFi connection destination table 33B101 includes a connection destination URL 601, an authentication user name 602, and an authentication password 603 as configuration items. In the example of FIG. 6, address_wifi_a, usr_wifi_a, and pw_wifi_a are set for each item.

<Connection maintenance interval table by mobile carrier>
FIG. 7 is a diagram illustrating a configuration example of the connection maintenance interval table 33B202 for each mobile carrier.
The mobile carrier connection maintenance interval table 33B202 includes a mobile carrier 701 and a necessary connection maintenance interval 702 as configuration items. Here, the connection maintenance interval is information indicating a time interval necessary for avoiding the start of the measurement timer operation for no communication time.

  In FIG. 7, for example, the necessary connection maintenance interval 702 is set to 1800 seconds, 2400 seconds, and 3000 seconds for Company A, Company B, and Company C, respectively.

<WiFi connection maintenance interval table>
FIG. 8 is a diagram illustrating a configuration example of the WiFi connection maintenance interval table 33B203.
The WiFi connection maintenance interval table 33B203 holds information on the WiFi connection maintenance interval 801, and the value is set to 30 seconds, for example.

<Connection maintenance interval table by cloud platform>
FIG. 9 is a diagram illustrating a configuration example of the cloud platform-specific connection maintenance interval table 33B204.
The cloud infrastructure connection maintenance interval table 33B204 includes a cloud infrastructure 901 and a necessary connection maintenance interval 902 as configuration items. In the example of FIG. 9, for example, 600 seconds, 1200 seconds, and 1800 seconds are set for company a, company b, and company c, respectively.

<Maximum connection maintenance interval table>
FIG. 10 is a diagram illustrating a configuration example of the maximum connection maintenance interval table 33B205.
The maximum connection maintenance interval table 33B205 holds information of the maximum connection maintenance interval 1001, and the value is set to 900 seconds, for example. The maximum connection maintenance interval 1001 is a desired value set by the user of the client terminal device 3.

<Connection maintenance retransmission interval table>
FIG. 11 is a diagram illustrating a configuration example of the connection maintenance retransmission interval table 33B206.
The connection maintenance retransmission interval table 33B206 holds information of the connection maintenance retransmission interval 1101, and the value is set to 4 seconds, for example.

<Connection maintenance retransmission count table>
FIG. 12 is a diagram illustrating a configuration example of the connection maintenance retransmission number table 33B207.
The connection maintenance retransmission count table 33B207 holds information of the connection maintenance retransmission count 1201, and the value is set to 2 times, for example. In the present specification, it is assumed that the connection is not disconnected when a response of the connection maintenance signal is not returned even after waiting for the retransmission interval shown in FIG.

<Used network component specification table>
FIG. 13 shows a configuration example of the use network component specification table 33B208.
The usage network component designation table 33B208 includes a usage component item name 1301 and a usage component content 1302 as configuration items. The item name 1301 of the usage component is composed of network type, mobile carrier, and cloud-based information. In the example of FIG. 13, mobile line, company A, and company a are set.

<Client terminal device connection processing>
FIG. 14 is a flowchart for explaining connection processing of the client terminal device 3 according to the first embodiment. This process is a process executed when the client terminal device 3 is activated or after detecting an unintended disconnection described below.

  First, the WebSocket client side communication unit 33B reads the mobile line connection destination table 33B100 and the WiFi connection destination table 33B101 (step 200).

  Next, the WebSocket client side communication unit 33B reads the mobile carrier-specific connection maintenance interval table 33B202, the WiFi connection maintenance interval table 33B203, the cloud infrastructure-specific connection maintenance interval table 33B204, and the maximum connection maintenance interval table 33B205 ( Step 201).

  In addition, the WebSocket client side communication unit 33B reads the network type, the mobile carrier in the case of a mobile line, and cloud-based information specified in the use network component specification table 33B208 (step 202). That is, information about the currently used environment is acquired.

  The WebSocket client side communication unit 33B obtains the connection maintenance interval 702 or the WiFi connection maintenance interval 801 of the designated mobile carrier and the cloud-based connection maintenance interval 902 from each table (step 203).

  Then, the WebSocket client side communication unit 33B reads the connection maintenance retransmission interval table 33B206 and the connection maintenance retransmission number table 33B207 (step 204).

  Subsequently, the WebSocket client side communication unit 33B refers to the use network component designation table 33B208 and checks whether the network type is a mobile line (step 205). If the network being used is a mobile line, the process proceeds to step 206. If the network being used is not a mobile line, the process proceeds to step 212.

  In step 206, the WebSocket client side communication unit 33B adopts the mobile line connection destination as the connection destination. (Step 206).

  Then, the WebSocket client side communication unit 33B compares the mobile carrier connection maintenance interval 702, the cloud-based connection maintenance interval 902, and the maximum connection maintenance interval 1001, and checks whether the mobile carrier connection maintenance interval 702 is the minimum (step) 207). If the mobile carrier connection maintenance interval 702 is the minimum, the process proceeds to step 211, and if not, the process proceeds to step 208.

  In step 211, the WebSocket client side communication unit 33B adopts the mobile carrier connection maintenance interval 702 as the connection maintenance interval (step 211).

  On the other hand, in step 208, the WebSocket client side communication unit 33B checks whether the cloud-based connection maintenance interval 902 is the minimum (step 208). If the cloud-based connection maintenance interval 902 is the minimum, the process proceeds to step 209, and if not, the process proceeds to step 210.

  In Step 209, the WebSocket client side communication unit 33B adopts the cloud-based connection maintenance interval 902 as the connection maintenance interval (Step 209).

  In step 210, the WebSocket client side communication unit 33B adopts the maximum connection maintenance interval 1001 as the connection maintenance interval.

  On the other hand, in step 212, the WebSocket client side communication unit 33B adopts the WiFi connection destination as the connection destination. (Step 212).

  Then, the WebSocket client side communication unit 33B compares the WiFi connection maintenance interval 801, the cloud-based connection maintenance interval 902, and the maximum connection maintenance interval 1001, and checks whether the WiFi connection maintenance interval 801 is the minimum (step 213). . If the WiFi connection maintenance interval 801 is minimum, the process proceeds to step 217, and if not, the process proceeds to step 214.

  In Step 217, the WebSocket client side communication unit 33B adopts the WiFi connection maintenance interval 801 as the connection maintenance interval (Step 217).

  In step 214, the WebSocket client side communication unit 33B checks whether the cloud-based connection maintenance interval 902 is the minimum (step 214). If the cloud-based connection maintenance interval 902 is the minimum, the process proceeds to step 215, and if not, the process proceeds to step 216.

  In step 215, the WebSocket client side communication unit 33B employs the cloud-based connection maintenance interval 902 as the connection maintenance interval (step 215).

  In step 216, the WebSocket client side communication unit 33B adopts the maximum connection maintenance interval 1001 as the connection maintenance interval.

  In step 218, the connection / disconnection unit 33B1 of the WebSocket client side communication unit 33B connects to the distribution apparatus 2 using the connection destination and the connection maintenance interval employed in the processing so far (step 218).

<Connection signal sending process during connection>
FIG. 15 is a flowchart for explaining connection signal sending processing during connection according to the first embodiment.

  First, the WebSocket client side communication unit 33B determines whether or not there is a no-communication state for a certain time (step 301). If the communication state does not correspond to a certain period of time, the process proceeds to step 303; otherwise, the process proceeds to step 302.

  In step 302, the WebSocket client side communication unit 33B resets the no-communication time measurement variable, and again determines in step 301 whether or not the communication state is in the no-communication state.

  In step 303, the WebSocket client side communication unit 33B increments the no-communication time measurement variable (step 303).

  Further, the WebSocket client side communication unit 33B determines whether or not the no-communication time measurement variable has reached the connection maintenance interval (702 or 801) (step 304). If the connection maintenance interval has not been reached, the process proceeds to step 301. If the connection maintenance interval has been reached, the process proceeds to step 305.

  In step 305, the WebSocket client side communication unit 33B (connection maintenance signal transmission unit 33B200) sends a connection maintenance signal to the distribution apparatus 2 (step 305).

  Further, the WebSocket client side communication unit 33B determines whether the connection maintenance retransmission interval (retransmission time interval) 1101 described in the connection maintenance retransmission interval table 33B206 has elapsed before receiving the response signal from the distribution apparatus 2 ( Step 306). If the connection maintenance retransmission interval (retransmission time interval) 1101 has not elapsed, the process proceeds to step 307. If the connection maintenance retransmission interval (retransmission time interval) 1101 has elapsed, the process proceeds to step 308. Migrate to

  In step 307, the WebSocket client side communication unit 33B resets the number of retransmissions (step 307), resets the no-communication time measurement variable (step 302), and shifts the processing to step 301.

  In step 308, the WebSocket client side communication unit 33B retransmits the connection maintenance signal (step 308), and adds 1 to the number of retransmissions (step 309).

  Then, the WebSocket client side communication unit 33B determines whether or not the upper limit 1201 of the number of retransmissions described in the connection maintenance retransmission number table 33B207 has been reached (step 310). If the upper limit has been reached, the process proceeds to step 311, and if the upper limit has not been reached, the process proceeds to step 306.

  In step 311, the WebSocket client side communication unit 33 </ b> B determines that the disconnection of the connection is unintentional disconnection, sets a flag indicating the disconnection, and disconnects the connection (step 311).

<Reconnection processing>
FIG. 16 is a flowchart for explaining reconnection processing when disconnection occurs during connection according to the first embodiment.

  The connection / disconnection unit 33B1 of the WebSocket client side communication unit 33B constantly monitors the connection established with the distribution apparatus 2, and performs this processing when a disconnection occurs.

  First, the connection / disconnection unit 33B1 determines whether or not the generated disconnection is an unintended disconnection (step 351). Here, if it is the cutting | disconnection which generate | occur | produced by step 311, the flag showing that it is an unintentional cutting | disconnection is set, and if this is not normal cutting | disconnection, this flag will not be set.

  If the disconnection is not intended, the connection / disconnection unit 33B1 executes the connection process of FIG. 14 again (step 352). Here, when the connection process of FIG. 14 is performed again, reading of the already read table may be omitted.

  If it is not intended disconnection but normal disconnection (when no flag is set), the process ends.

<Elements that need to be developed>
FIG. 17 is a diagram showing elements that need to be developed in the system according to the embodiment of the present invention.
(I) FIG. 17A is a schematic diagram showing a development part necessary for responding to a change in network configuration requirements for each customer or the same customer on the server side. Without the present invention, if there is a change in the network configuration, it is necessary to design and develop the entire system on the server (distribution apparatus 2) side. According to the present invention, the hatched portion, that is, the transmission content list table 23B1 and If only the transmission destination list table 23B2 is changed, the server (distribution apparatus 2) side can cope with a change in network configuration requirements.

(Ii) FIG. 17B is a schematic diagram showing a development part necessary for responding to a change in network configuration requirements for each customer or the same customer on the client side. As described above, if the present invention is not present and the network configuration is changed, it is necessary to design and develop the entire system on the client side. By changing the connection destination table 33B101, the WiFi connection maintenance interval table 33B203, the maximum connection maintenance interval table 33B205, and the use network component designation table 33B208, the client side can cope with changes in network configuration requirements. In FIG. 17B, elements such as 33B200 that need not be developed each time are omitted in the WebSocket client side communication unit 33B.

<Message transmission processing on the server side>
FIG. 18 is a flowchart for explaining message transmission processing executed on the server (distribution apparatus 2) side.

  The WebSocket server side communication unit 23C determines whether or not the client status is OK even if a message is transmitted (step 401). Here, the client status is a variable that is “OK” if the connection between the distribution device 2 and the client terminal device 3 is established and maintained, and “NG” if the connection is disconnected. If the state is NG, the process proceeds to step 402, and if the state is OK, the process proceeds to step 403.

  In step 402, the WebSocket server side communication unit 23 </ b> C returns a transmission failure to the administrator terminal device 1 (step 402).

  In step 403, the WebSocket server side communication unit 23C transmits a message to the client terminal device 3.

<Send setting screen example>
FIG. 19 is a diagram illustrating an example of a setting screen (GUI) displayed on the display unit of the administrator terminal device 1. FIG. 19A shows a transmission destination terminal list screen example, and FIG. 19B shows a transmission content list screen example. FIG. 19C shows an example of a transmission setting screen.

(I) As illustrated in FIG. 19A, the transmission destination terminal list screen includes a terminal ID 1901 for uniquely identifying and identifying the client terminal device 3, and a user 1902 indicating a user of the corresponding client terminal device 3. And a state 1903 indicating the state of the corresponding client terminal device 3 as a component.

  The administrator can display this screen on the display unit, select the client terminal apparatus 3 whose state 1903 is OK, select the one to send a message, and instruct the distribution apparatus 2 to transmit the message. It can be done.

(Ii) As shown in FIG. 19B, the transmission content list screen has a transmission content ID 1904 for uniquely identifying and identifying a transmission message and a transmission content 1905 indicating the content of the message as components. Yes.

  The administrator can select a desired one from transmission contents 1905 prepared in advance and instruct the client terminal device 3 selected by the distribution device 2 to transmit the selected message. The transmission content 1905 is fixed here for the sake of simplicity, but this is not a limitation. Therefore, when the desired message is not on the transmission content list screen, a message creation screen (not shown) may be displayed so that the administrator can create the desired message.

(Iii) In the transmission setting screen shown in FIG. 19C, the transmission terminal setting and the transmission content setting can be performed by a selection operation in one screen. As in FIG. 19B, the transmission content (transmission content) does not have to be fixed in advance.

(2) Second Embodiment The second embodiment provides a technique for easily dealing with a case where the network type is dynamically changed in an environment where a plurality of types of networks are mixed.

<Application scene>
FIG. 20 is a schematic diagram for illustrating an application scene of the second embodiment.
FIG. 20 shows a scene in which the WiFi network is used on the customer premises and the mobile line network is used outside the customer premises. In this application situation, the network component changes dynamically when moving from the customer premises to the customer premises. The second embodiment provides a system that can cope with this dynamic network configuration change.

  In FIG. 20, the administrator terminal device 1 is connected to the distribution device 2 via the Internet 4. The distribution apparatus 2 is connected to a WiFi network 6 including a mobile carrier C network 113 and a customer premises LAN via the Internet 4. When the mobile unit 101 is in the customer δ premises 111, the client terminal device 3 therein communicates with the distribution device 2 via the WiFi network 6. On the other hand, when the mobile unit 101 is outside the customer δ, the client terminal device 3 communicates with the distribution device 2 via the mobile carrier C network 113.

<Configuration of distribution system>
FIG. 21 is a diagram showing a schematic configuration of a distribution system according to the second embodiment of the present invention.
In addition to the configuration according to the first embodiment, the distribution system according to the second embodiment further includes a network type automatic determination unit 33F and a mobile carrier automatic determination unit 33G.

  The network type automatic determination unit 33F refers to information held by the OS of the client terminal device 3 and performs processing for determining which network is used. The mobile carrier automatic determination unit 33G determines which carrier is used from the information of the OS when the network type automatic determination unit 33F determines that the mobile carrier network is used. Execute. Other configurations are the same as those in FIG.

<Connection process>
FIG. 22 is a flowchart for explaining connection processing executed by the client terminal device 3 according to the second embodiment. In the connection processing according to the second embodiment, when the client terminal device 3 is activated or when an unintentional disconnection occurs, the network type automatic processing is performed when the processing for establishing a connection with the distribution device 2 is executed. When the determination and the network type are mobile lines, mobile carrier automatic determination is performed.

  The difference from FIG. 14 is that steps 202 and 203 are changed to become steps 901 and 902, and steps 903 to 906 are newly added. Therefore, only these steps will be described below.

  In step 901 and step 902, the reading target and the acquisition target are changed to only the cloud platform, respectively. This is because in the second embodiment, the network to be used is automatically determined, so that the necessary information is only information about the cloud platform.

  In step 903, the network type automatic determination unit 33F refers to the information held by the OS of the client terminal device 3 and automatically determines the network type.

  In step 904, the mobile carrier automatic determination unit 33G similarly refers to the information held by the OS of the client terminal device 3 and performs automatic mobile carrier determination.

  In step 905, the WebSocket client side communication unit 33B acquires the corresponding mobile carrier connection maintenance interval 702 (see FIG. 7).

  In step 906, the WebSocket client side communication unit 33B acquires the corresponding WiFi connection maintenance interval 801 (see FIG. 8).

  By executing the processing as described above, connection processing can be executed in response to a dynamic network configuration change.

(3) Third Embodiment The third embodiment provides means for directly determining the connection maintenance interval from the customer's immediacy (maximum downtime) desired value.

  In the first and second embodiments, the user of the client terminal device 3 needs to set and input the maximum connection maintenance interval 1001 (FIG. 10) as a desired connection maintenance interval. This maximum connection maintenance interval is a concept that is difficult for a user to understand, and an unfamiliar user may set it incorrectly.

  Therefore, the third embodiment of the present invention is characterized in that the process of determining the connection maintenance interval is performed from the viewpoint of “maximum downtime” that is easy to understand from the customer. The configuration of the distribution system is the same as that in FIG. 2 except for the internal configuration of the WebSocket client side communication unit 33B, and thus the description thereof is omitted.

<Internal configuration of WebSocket client side communication unit>
FIG. 23 is a diagram illustrating an internal configuration of the WebSocket client side communication unit 33B according to the third embodiment.

  The difference from the first embodiment is that the maximum disconnection time, which is a concept that is easier to understand from the customer's perspective, is used as an input value. Therefore, the WebSocket client side communication unit 33B uses the maximum disconnection interval instead of the maximum connection maintenance interval table 33B205 This is a point having a time table 33B209.

  The maximum disconnection time is a value obtained by adding “retransmission timeout time from the last transmission time” to “maximum connection maintenance interval”. The retransmission timeout time is a value represented by the interval of retransmission processing (retransmission interval) executed after the connection maintenance interval × (connection maintenance retransmission upper limit count + 1).

<Connection process>
FIG. 24 is a flowchart for explaining connection processing executed by the client terminal device according to the third embodiment. The difference from the connection processing (FIG. 14) according to the first embodiment is that step 201 is changed to step 1101 and step 1102 is added.

  In Step 1101, the WebSocket client side communication unit 33B reads the mobile carrier connection maintenance interval table 33B202, the WiFi connection maintenance interval table 33B203, the cloud infrastructure connection maintenance interval table 33B204, and the maximum non-communication time table 33B209. In the maximum non-communication time table, a maximum non-communication time request value set by the user is described.

  In step 1102, the WebSocket client side communication unit 33 </ b> B derives the maximum connection maintenance interval request value from the maximum non-communication time request value. Here, the disconnection time is maximized when disconnection occurs immediately after successful transmission of the periodic connection maintenance signal. In this case, as described above, the maximum disconnection time is represented by the sum of the connection maintenance signal transmission interval and the “retransmission timeout value from the last transmission time”. Therefore, in Step 1102, the “retransmission timeout value from the last transmission time” obtained by multiplying the connection maintenance retransmission interval and the connection maintenance retransmission upper limit number by 1 is subtracted from the “maximum unavailable time requested value”. Thus, the maximum connection maintenance interval is calculated.

  As described above, since the client terminal device 3 automatically converts the “maximum disconnection time” into the “maximum connection maintenance interval”, the user inputs a desired value of the “maximum disconnection time” that is easier to understand. The connection process can be appropriately executed.

(4) Modification (i) Instead of the WebSocket protocol, a protocol called COMET may be used.

(Ii) In each of the above-described embodiments, there is no response to the connection maintenance signal for a certain period as a solution to the problem that the client is not aware of the disconnection due to a radio wave failure and cannot receive an idle disconnection notification of each network device. In this case, a solution is provided by providing a retransmission timer for disconnecting the connection. However, instead of this, a method may be employed in which disconnection is determined by monitoring the radio wave condition, or disconnection is determined by monitoring a change in the network type.

(Iii) You may use 2nd Embodiment for the use of the static change of a network component.

(Iv) In the second embodiment, when it is known that there is no further change, in order to omit automatic discrimination processing, either “network type” or “mobile carrier” to be automatically discriminated is fixed. It may be a value.

(V) In the third embodiment, instead of WebSocket, a polling method may be adopted for any one of network types that are dynamically changed.

(5) Summary (i) The present invention relates to a message push delivery system that pushes a message from a server device (distribution device) to a communication terminal device (client terminal device) using the WebSocket protocol. In the system, the client terminal device maintains a connection maintenance interval (connection maintenance interval for each carrier of mobile communication, connection maintenance interval for each cloud platform, WiFi communication) necessary for avoiding a network non-communication timer for each network component. Connection maintenance interval) information (fixed information that does not need to be changed even when the system is modified) in advance, and the connection maintenance interval can be avoided so that the no-communication timer can be avoided by simply specifying the components to be used. Is used as the connection maintenance interval. In this way, in the network configuration used between customers or by the same customer, even if the system components are statically changed, the connection maintenance interval of the entire system can be reviewed for all the system components. It becomes unnecessary. Also, by configuring the information necessary for connection separately for each network type, the amount of work for changing the connection destination accompanying the static change of the network type is reduced. In this system, it is assumed that the client terminal device is installed and used on a vehicle such as an automobile.

  In addition, the client terminal device retransmits a signal for maintaining the connection to the distribution device for a certain period of time after the absence of communication, but reconnects with the retransmission timer means for disconnecting when there is no response from the distribution device. Reconnect means to perform. This makes it possible to ensure a certain level of immediacy including an environment where radio waves are not good.

  When acquiring the minimum value of the connection maintenance interval, the client terminal device specifies in addition to the connection maintenance interval for each carrier of mobile communication, the connection maintenance interval for each cloud platform, and the connection maintenance interval for WiFi communication. The minimum value is determined including the maximum connection maintenance time interval (the user's desired value that this connection maintenance interval should satisfy at least). Thereby, the immediacy requested by the customer can be ensured including the environment where the radio wave is not good.

  In the present invention (second embodiment), the client terminal device automatically determines the network type such as the mobile communication line or the WiFi by referring to the OS holding information held by the client terminal device. In the case of a mobile communication line, the communication carrier is automatically determined. By doing so, when the network type and the mobile carrier are dynamically changed, the change can be detected and reconnected, and the network configuration can be automatically switched. In this case, information necessary for connection such as a connection destination address and authentication information, and information necessary for connection maintenance such as a connection maintenance interval suitable for the network environment are automatically set.

  Further, in the present invention (third embodiment), the user sets, as an input value, the maximum off time, which is a concept that is easier to understand from the customer, instead of the maximum connection maintenance interval. Then, the maximum connection maintenance interval is calculated from the maximum interruption time, the connection maintenance signal retransmission interval, and the connection maintenance signal retransmission count. By doing so, it is possible to provide a user-friendly system.

(Ii) The present invention can also be realized by software program codes that implement the functions of the embodiments. In this case, a storage medium in which the program code is recorded is provided to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention. As a storage medium for supplying such program code, for example, a flexible disk, CD-ROM, DVD-ROM, hard disk, optical disk, magneto-optical disk, CD-R, magnetic tape, nonvolatile memory card, ROM Etc. are used.

  Also, based on the instruction of the program code, an OS (operating system) running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing. May be. Further, after the program code read from the storage medium is written in the memory on the computer, the computer CPU or the like performs part or all of the actual processing based on the instruction of the program code. Thus, the functions of the above-described embodiments may be realized.

  Further, by distributing the program code of the software that realizes the functions of the embodiment via a network, it is stored in a storage means such as a hard disk or memory of a system or apparatus, or a storage medium such as a CD-RW or CD-R And the computer (or CPU or MPU) of the system or apparatus may read and execute the program code stored in the storage means or the storage medium when used.

  Finally, it should be understood that the processes and techniques described herein are not inherently related to any particular apparatus, and can be implemented by any suitable combination of components. In addition, various types of devices for general purpose can be used in accordance with the teachings described herein. It may prove useful to build a dedicated device to perform the method steps described herein. Various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiments. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined. Although the present invention has been described with reference to specific examples, these are in all respects illustrative rather than restrictive. Those skilled in the art will appreciate that there are numerous combinations of hardware, software, and firmware that are suitable for implementing the present invention. For example, the described software can be implemented in a wide range of programs or script languages such as assembler, C / C ++, perl, shell, PHP, Java (registered trademark).

  Furthermore, in the above-described embodiment, control lines and information lines are those that are considered necessary for explanation, and not all control lines and information lines on the product are necessarily shown. All the components may be connected to each other.

  In addition, other implementations of the invention will be apparent to those skilled in the art from consideration of the specification and embodiments of the invention disclosed herein. Various aspects and / or components of the described embodiments can be used singly or in any combination in a computerized storage system capable of managing data. The specification and specific examples are merely exemplary, and the scope and spirit of the invention are indicated in the following claims.

1 ... Administrator terminal device 11A, 21A, 31A ... CPU
11B, 21B, 31B ... Memory 13, 23, 33 ... External storage device 2 ... Distribution device 3 ... Client terminal device 4 ... Internet 5 ... Mobile phone network 6 ... WiFi Network 13A: administrator operation transmission unit 13B, 33C, display processing unit 23A, administrator operation response unit 23B, server management unit 23C, WebSocket server side communication unit 23B1, transmission content list Table 23B2 ... Destination terminal list table 33A ... Client management unit 33B ... WebSocket client side communication unit 33D ... Mobile line connection unit 33E ... WiFi search / connection unit

Claims (15)

A communication terminal device that receives a message that the server device pushes,
A processor for receiving a message from the server device using a WebSocket protocol according to a program and transmitting a signal for maintaining a WebSocket connection to the server device;
A memory for storing at least connection maintenance interval information for each mobile phone communication carrier, connection maintenance interval information for each cloud platform, and use network configuration information indicating a network component used by a user ;
The communication terminal device is connected to the server device and the cloud infrastructure via a mobile phone communication carrier or a wifi network and the Internet, respectively.
Based on the use network configuration information, the processor specifies a connection maintenance interval specifying process for specifying a connection maintenance interval and a cloud-based connection maintenance interval of a mobile phone communication carrier currently used by the user, and the specified Using the minimum connection maintenance interval determination processing for determining which of the connection maintenance interval of the mobile phone communication carrier and the connection maintenance interval of the cloud infrastructure is minimum, and the minimum connection maintenance interval determined by the minimum connection maintenance interval determination processing A connection establishment process for establishing a communication connection with the server device,
The connection maintenance interval information for each mobile phone communication carrier and the connection maintenance interval information for each cloud platform are fixed information that does not need to be rewritten, and the use network configuration information is information set for each user. A communication terminal device. In claim 1,
The memory further stores information on a maximum connection maintenance interval indicating a connection maintenance interval that the user should satisfy at least,
In the connection maintenance interval specifying process, the processor determines which of the specified mobile phone communication carrier connection maintenance interval, the specified cloud-based connection maintenance interval, and the maximum connection maintenance interval is the smallest. A communication terminal device. In claim 2,
The memory further stores changeable Wifi communication connection maintenance interval information,
The processor further refers to the use network configuration information to determine whether the network currently used by the user is a cellular phone communication network or a WiFi communication network, and when the use network is a WiFi communication network. The process of specifying the connection maintenance interval of the WiFi communication and the connection maintenance interval of the cloud infrastructure, and the connection maintenance interval of the specified WiFi communication, the connection maintenance interval of the cloud infrastructure, and the maximum connection maintenance interval are And a process for determining whether or not the communication terminal device is minimum. In claim 2,
The memory further stores retransmission processing related information defining a retransmission interval and the number of retransmissions of the signal for maintaining the WebSocket connection,
The retransmission processing related information is fixed information that does not require rewriting,
When the processor further detects a no-communication state for a certain period of time, the processing for retransmitting the signal for maintaining the WebSocket connection according to the retransmission interval and the number of retransmissions, and when the upper limit of the number of retransmissions is reached In the communication terminal apparatus, flag information indicating that disconnection of WebSocket communication not intended by the user is set in the communication terminal apparatus. In claim 4,
The processor executes a process of determining that the latest communication disconnection is a disconnection unintended by the user with reference to the flag information,
The processor performs the connection maintenance interval identification processing, the minimum connection maintenance interval determination processing, and the connection establishment processing when the communication disconnection is disconnection that is not intended by the user. apparatus. In claim 2,
The memory further stores changeable Wifi communication connection maintenance interval information,
The processor further refers to the OS of the communication terminal device to determine whether the network currently used by the user is a cellular phone communication network or a WiFi communication network, and when the use network is a WiFi communication network The connection maintenance interval of the WiFi communication and the connection maintenance interval of the cloud infrastructure, and the connection maintenance interval of the specified WiFi communication, the connection maintenance interval of the cloud infrastructure, and the maximum connection maintenance interval And a process for determining whether or not the communication terminal is minimum. In claim 1,
The memory further stores information on a maximum communication interruption time set by the user,
The processor further executes a process of calculating a maximum connection maintenance interval requested by the user from the maximum interruption time,
In the connection maintenance interval specifying process, the processor determines which is the minimum of the specified mobile phone communication carrier connection maintenance interval, the specified cloud-based connection maintenance interval, and the calculated maximum connection maintenance interval. A communication terminal device characterized by determining. A communication terminal device according to claim 1;
A server device that pushes a message to the communication terminal device using WebSocket communication;
An administrator terminal device that instructs the server device to indicate the content of the message to be transmitted and the communication terminal device to which the message is to be transmitted;
A message delivery system comprising: A communication method executed between a server device that pushes a message and a communication terminal device that receives the message,
The communication terminal device receives a message from the server device using a WebSocket protocol according to a program, transmits a signal for maintaining a WebSocket connection to the server device, and at least for each mobile phone communication carrier A memory for storing connection maintenance interval information, connection maintenance interval information for each cloud platform, and use network configuration information indicating network components used by a user;
The communication terminal device is connected to the server device and the cloud platform via a mobile phone communication carrier or wifi network and the Internet, respectively.
The communication method is:
A connection maintenance interval specifying step in which the processor specifies a connection maintenance interval of a mobile phone communication carrier currently used by the user and a cloud-based connection maintenance interval based on the use network configuration information;
A minimum connection maintenance interval determination step for determining which of the connection maintenance interval of the identified mobile phone communication carrier and the cloud-based connection maintenance interval is the processor is minimum;
The processor has a connection establishment step of establishing a communication connection with the server device using the minimum connection maintenance interval determined in the minimum connection maintenance interval determination step ;
The connection maintenance interval information for each mobile phone communication carrier and the connection maintenance interval information for each cloud platform are fixed information that does not need to be rewritten, and the use network configuration information is information set for each user. Communication method. In claim 9,
The memory further stores information on a maximum connection maintenance interval indicating a connection maintenance interval that the user should satisfy at least,
In the connection maintenance interval specifying step, the processor determines which of the specified mobile phone communication carrier connection maintenance interval, the specified cloud-based connection maintenance interval, and the maximum connection maintenance interval is minimum. A communication method characterized by the above. In claim 10,
The memory further stores changeable Wifi communication connection maintenance interval information,
The communication method further includes:
The processor refers to the use network configuration information to determine whether the network currently used by the user is a cellular phone communication network or a WiFi communication network;
The processor specifying a connection maintenance interval of the WiFi communication and a connection maintenance interval of the cloud infrastructure when a use network is a WiFi communication network; and
The processor determining which of the specified WiFi communication connection maintenance interval, the cloud-based connection maintenance interval, and the maximum connection maintenance interval is minimum;
A communication method characterized by comprising: In claim 10,
The memory further stores retransmission processing related information defining a retransmission interval and the number of retransmissions of the signal for maintaining the WebSocket connection,
The retransmission processing related information is fixed information that does not require rewriting,
The communication method further includes:
Retransmitting the signal for maintaining the WebSocket connection according to the retransmission interval and the number of retransmissions when the processor detects a no-communication state for a predetermined time;
When the processor reaches the upper limit of the number of retransmissions, setting flag information indicating disconnection of WebSocket communication unintended by the user in the communication terminal device;
A communication method characterized by comprising: The claim 12, further comprising:
The processor refers to the flag information to determine that the latest communication disconnection is a disconnection unintended by the user;
The communication method, wherein the processor executes the connection maintenance interval specifying step, the minimum connection maintenance interval determination step, and the connection establishment step when the communication disconnection is a disconnection unintended by the user. . In claim 10,
The memory further stores changeable Wifi communication connection maintenance interval information,
The communication method further includes:
The processor refers to the OS of the communication terminal device to determine whether the network currently used by the user is a cellular phone communication network or a WiFi communication network;
The processor specifying a connection maintenance interval of the WiFi communication and a connection maintenance interval of the cloud infrastructure when a use network is a WiFi communication network; and
The processor determining which of the specified WiFi communication connection maintenance interval, the cloud-based connection maintenance interval, and the maximum connection maintenance interval is minimum;
A communication method characterized by comprising: In claim 9,
The memory further stores information on a maximum communication interruption time set by the user,
The communication method further includes:
The processor calculates a maximum connection maintenance interval requested by the user from the maximum outage time;
In the connection maintenance interval specifying step, the processor determines which is the minimum of the specified mobile phone communication carrier connection maintenance interval, the specified cloud-based connection maintenance interval, and the calculated maximum connection maintenance interval. A communication method characterized by determining.

Images