Data transmission system

Abstract

The issuing side simply determines whether the processing of issuing the operation information related to the operation state of the elevator is continued or not. A data transmission system (100) is provided with a first server device (4) that functions as a proxy, and a communication device (3). In a transmission mode, a distribution unit (312) of the communication device continues the transmission mode when the communication device has received a transmission continuation request from a request source device (8) before a predetermined period of time has elapsed after the communication device has received the transmission continuation request for distribution to the first server device in the second subject, and continues the transmission mode when the communication device has received the transmission continuation request for distribution to the first server device in the second subject after the communication device has received the transmission continuation request for distribution to the first server device in the second subject. When a predetermined period of time has elapsed without receiving a transmission continuation request, the mode is switched to a non-transmission mode.

Description

Technical Field

[0001] One aspect of the present invention relates to a data transmission system for transmitting motion information related to the motion status of an elevator. Background Technology

[0002] Patent Document 1 discloses an example of a system for monitoring elevators. In the system of Patent Document 1, in response to a call from an intercom inside the elevator car, the system connects to a specific monitor's mobile phone and sends image data from a surveillance camera installed in the elevator lobby to the monitor's mobile phone. In this system, the image data sent to the mobile phone is switched according to a switching command for the image data of the monitored object.

[0003] Existing technical documents Patent documents Patent Document 1: Japanese Invention Patent No. 4369253 Summary of the Invention The problem the invention aims to solve However, Patent Document 1 does not disclose any technology related to the transmission and reception of information related to elevators that use a publish / subscribe communication method.

[0004] One objective of this invention is to simply determine on the publishing side whether to continue processing the publishing of motion information related to the elevator's motion status using a publish / subscribe communication method.

[0005] Technical means adopted to solve the problem A data transmission system according to one aspect of the present invention includes: a server device that can communicate with each other using a publish / subscribe communication method and acts as a proxy, and one or more communication devices; the communication devices include: a receiving unit that receives motion information related to the motion status of an elevator controlled by an elevator control device communicatively connected to the device; a publishing unit that switches the motion mode to any of the following: a sending mode in which, whenever the receiving unit receives the motion information, the received motion information is published to the server device with a predetermined first topic; and a non-sending mode in which the publishing is not performed; and a subscribing unit that, when switching to the sending mode, subscribes to the server device. The server device includes a first sending unit that sends a request to a communication device that has subscribed to the second topic to continue sending the action information published by the requesting source device to the server device on the second topic. The publishing unit, in the sending mode, continues sending if it receives the continued sending request after a predetermined period has elapsed since the last time the communication device received it, and switches to the non-sending mode if it has not received the continued sending request after the last time the communication device received it and the predetermined period has elapsed.

[0006] Invention Effects According to one aspect of the present invention, it is possible to simply determine on the publishing side whether to continue processing of motion information related to the elevator's motion status using a publish / subscribe communication method. Attached Figure Description

[0007] Figure 1 This is a block diagram illustrating an example of the structure of a data transmission system according to an embodiment of the present invention.

[0008] Figure 2 This is a sequence diagram representing an example of a data flow based on the first use of an API.

[0009] Figure 3 This is a sequence diagram representing an example of data flow based on the API after switching to send mode for the second time or subsequent times.

[0010] Figure 4 This is a sequence diagram representing an example of data flow when the API is not used within a specified period. Detailed Implementation

[0011] The data transmission system 100 of this embodiment will be described below.

[0012] [Overview of the Data Transmission System] First, based on Figure 1 An overview of the data transmission system 100 is provided. Figure 1 This is a block diagram illustrating an example of the structure of a data transmission system 100.

[0013] The data transmission system 100 is a system capable of transmitting motion information related to the operational status of the elevator 1 controlled by the elevator control device 2 from the elevator control device 2 to the terminal device 9. By transmitting the motion information of the elevator 1 to the terminal device 9, the user of the terminal device 9 can monitor the operational status of the elevator 1.

[0014] Action information includes, for example, information about abnormal situations occurring in elevator 1 and the operational status of elevator 1. Information indicating operational status may include, for example, the position of the car, the weight inside the car, and the opening and closing status of the doors. Action information corresponds to the identification information of elevator 1. In addition to action information, the identification information of elevator 1 may also correspond to detailed information about elevator 1, such as the model name of elevator 1 and the configuration information of elevator 1.

[0015] The elevator 1 that is the object of obtaining motion information can be one or more. Preferably, the motion information of the elevator 1 specified by the user is sent to the terminal device 9.

[0016] Users of the data transmission system 100 may be, for example, users of elevator 1. Users of the data transmission system 100 may also be, for example, the administrator of elevator 1. Alternatively, users of the data transmission system 100 may be, for example, maintenance personnel performing maintenance on elevator 1. In this case, a monitoring device for monitoring the operation of elevator 1 can be used as the terminal device 9.

[0017] In this embodiment, such as Figure 1 As shown, the data transmission system 100 includes, for example, an elevator 1, an elevator control device 2, a communication device 3, a first server device 4, a second server device 5, a destination device 6, a storage device 7, a request source device 8, and a terminal device 9. The first server device 4, the second server device 5, the storage device 7, and the request source device 8 are as follows: Figure 1 As shown, it can be built on a Virtual Private Cloud (VPC), for example. Furthermore, part or all of the destination device 6 can be built on this Virtual Private Cloud.

[0018] Elevator control device 2 is communicatively connected to elevator 1 and controls the movement of elevator 1 and monitors its operational status. Elevator control device 2 is also communicatively connected to communication device 3, transmitting the movement information of elevator 1 controlled by elevator control device 2 to communication device 3. Elevator control device 2 can also transmit detailed information about elevator 1 along with its movement information to communication device 3.

[0019] Elevator control device 2 generates motion information corresponding to the identification information of elevator 1, and sends the motion information to communication device 3 using method A as shown below. Furthermore, elevator control device 2 can send motion information to communication device 3 using method B as shown below. Method B, as a communication method between elevator control device 2 and communication device 3, is a widely used method. Therefore, data transmission system 100 can be constructed by adding method A to an existing system that uses method B.

[0020] (Method A: Push-type) Whenever the operating status of elevator 1 changes, elevator control device 2 sends the operating information to communication device 3. In this case, elevator control device 2 sends the operating information to communication device 3 via the first control line 101 connecting elevator control device 2 and communication device 3 each time it generates operating information. In Method A, no request to send operating information is sent from communication device 3 to elevator control device 2.

[0021] (Method B: Pull-type) When the elevator control device 2 receives a request to send motion information from the communication device 3, it sends motion information to the communication device 3 in response to the request. In this case, the elevator control device 2 sends the motion information to the communication device 3 via the second control line 102 connecting the elevator control device 2 and the communication device 3. The sending request to the elevator control device 2 in Method B will be referred to as "each sending request" below.

[0022] The operational status of elevator 1 can change constantly. Therefore, the transmission frequency of operational information in method A is higher than that in method B. Therefore, preferably, a communication standard capable of communicating at a higher frequency than the second control line 102 is used in the first control line 101. For example, the first control line 101 can be RS422, and the second control line 102 can be RS232C. However, the second control line 102 can also use the same communication standard as the first control line 101.

[0023] The communication device 3 is communicatively connected to both the first server device 4 and the second server device 5, and is a device for sending and receiving data with both the first server device 4 and the second server device 5. In the communication between the communication device 3 and both the first server device 4 and the second server device 5, SORACOM (registered trademark) can be used, for example. Furthermore, the communication networks connecting the communication device 3 and the first server device 4, and the communication networks connecting the communication device 3 and the second server device 5, can be physically the same or physically separate.

[0024] The communication device 3 transmits the motion information received from the elevator control device 2 to the first server device 4 via method A described above. Specifically, regarding the motion information received from the elevator control device 2 via method A, the communication device 3 follows a publish / subscribe communication method, starting to send data to the first server device 4 at a predetermined time and stopping sending data to the first server device 4 at a predetermined time. In other words, the communication device 3 is a device capable of communicating with the first server device 4 via a publish / subscribe communication method. The publish / subscribe communication method will be referred to as the "first communication method" below. The protocol used in the first communication method is preferably, for example, MQTT (Message Queuing Telemetry Transport). By using the MQTT protocol, motion information can be sent from the communication device 3 to the first server device 4 at a high frequency. Therefore, the motion information sent from the elevator control device 2 to the communication device 3 at a high frequency via method A described above is then sent from the communication device 3 to the first server device 4 at a high frequency. That is, in the data transmission system 100, motion information can be transmitted from the elevator control device 2 to the first server device 4 at a high frequency.

[0025] On the other hand, the communication device 3 can send the motion information received from the elevator control device 2 to the second server device 5 via method B described above, following a second communication method different from the first communication method. The second communication method does not need to be publish / subscribe; it can use, for example, a protocol based on TCP / IP (Transmission Control Protocol / Internet Protocol), or a custom-defined protocol. Furthermore, the second communication method is a widely adopted method in existing elevator monitoring systems and communication devices 3.

[0026] Furthermore, in method B described above, the action information sent to the communication device 3 as a response of the elevator control device 2 to each transmission request can be the latest action information from the time the communication device 3 receives each transmission request, or it can be untransmitted action information accumulated up to the time the transmission request is received. In the latter case, the elevator control device 2 can generate action information each time the operating status of the elevator 1 changes and store it in the storage unit (not shown) of the elevator control device 2. In this case, the communication device 3 can send the action information stored in the storage unit (not shown) of the communication device 3 at this time as a response to each transmission request when it receives each transmission request from the second server device 5.

[0027] In addition, communication device 3 receives a "send start request" for action information from second server device 5 according to the second communication method. Taking the receipt of the send start request as an opportunity, communication device 3 sends action information to first server device 4 according to the first communication method each time it receives action information from elevator control device 2. That is, the send start request is a start request to send action information to first server device 4 in real time. Furthermore, communication device 3 receives a "send continue request" for action information from first server device 4 according to the first communication method. During the period of continuously receiving send continue requests, communication device 3 continuously sends the action information received from elevator control device 2 to first server device 4. That is, the send continue request is a continuation request to send action information to first server device 4 in real time.

[0028] Each elevator control device 2 and communication device 3 is provided for one elevator 1. As described above, the data transmission system 100 can have one elevator 1 or multiple elevators 1. When the data transmission system 100 has multiple elevators 1, each elevator 1 is provided with a set of elevator control device 2 and communication device 3.

[0029] The first server device 4 is a device that can communicate with the communication device 3 according to a first communication method and acts as an agent. The data transmission system 100 may be a system that includes at least the first server device 4 and the communication device 3, which can communicate with each other according to the first communication method and act as agents. While receiving action information from the communication device 3 according to the first communication method, the first server device 4 sends the received action information to the destination device 6 each time it receives action information.

[0030] Furthermore, the first server device 4 is a device that can be communicatively connected to the second server device 5 and the request source device 8 according to a first communication method. The first server device 4 sends a transmission continuation request received from the request source device 8 to the communication device 3 according to the first communication method; on the other hand, it sends a transmission start request received from the request source device 8 to the second server device 5 according to a second communication method.

[0031] The first server device 4 acts as a proxy. Therefore, the communication device 3 subscribes to the first server device 4 so that the first server device 4 can send the transmission continuation request received from the requesting source device 8 to the communication device 3. This subscription will be described later as an explanation of the subscription unit 313 of the communication device 3.

[0032] The second server device 5, following the second communication method, sends a request to initiate the transmission of action information received from the first server device 4 to the communication device 3. Alternatively, the second server device 5 may, upon receiving a transmission request for action information from the requesting source device 8, also follow the second communication method to send each transmission request to the communication device 3, receiving action information as a response to each transmission request. In this case, the second server device 5 performs the following process: storing the received action information in the storage device 7. In this embodiment, the second server device 5 directly stores the action information in the storage device 7, but it may also store the action information in the storage device 7 via a relay device.

[0033] The sending destination device 6 is a device that performs the process of storing the received action information in the storage device 7 each time it receives action information from the first server device 4. In this embodiment, the sending destination device 6 directly stores the action information in the storage device 7, but it may also store the action information in the storage device 7 via a relay device. The sending destination device 6 may be a device provided as a web service platform such as AWS IoT Core. The storage device 7 is a device for storing action information, and may include a database, for example. In order to store action information that is sent at a high frequency, the database included in the storage device 7 is preferably a NoSQL database, such as a key-value type, and has excellent scalability. The database and the mechanism for storing the action information in the database may also be provided as a database cloud service.

[0034] As described above, the first server device 4 acts as a proxy. Therefore, the destination device 6 subscribes to a specified first topic from the first server device 4, enabling the first server device 4 to send action information received from the communication device 3 to the destination device 6. The first topic is a topic used to receive action information and can be set to any value.

[0035] After receiving the transmission start request, communication device 3 begins sending action information to first server device 4. Therefore, destination device 6 subscribes to a first topic from first server device 4 before first server device 4 begins receiving action information, so that first server device 4 can send action information to destination device 6 each time it receives it. In this embodiment, destination device 6 subscribes to the first topic from first server device 4 before terminal device 9 utilizes (calls) API (Application Programming Interface) 813.

[0036] The request source device 8 has the following function: providing specified elevator 1 movement information available to the terminal device 9. In this embodiment, the request source device 8 is, for example, a web server, and this function is provided by API 813. API 813 is a software interface available to a web browser or APP application software (hereinafter simply referred to as "terminal-side software") running on the terminal device 9, used to obtain the elevator 1 movement information stored in the storage device 7 and send it to the terminal device 9. When the terminal device 9 is using API 813, the request source device 8 sequentially obtains the specified elevator 1 movement information from the storage device 7 and sends the obtained movement information to the terminal device 9. "The terminal device 9 is using API 813" means that in order to obtain the elevator 1 movement information specified by the user, the terminal-side software capable of using API 813 is running on the terminal device 9.

[0037] If the requesting source device 8 utilizes API 813 from the terminal device 9 again after a predetermined period has elapsed since the terminal device 9 last utilized API 813, it performs the following process: sending a start request for action information to the first server device 4. That is, when the terminal device 9 begins utilizing API 813, the requesting source device 8 sends a start request to the first server device 4. In this embodiment, the requesting source device 8 sends the start request directly to the first server device 4, but it may also send the start request to the first server device 4 via a relay device.

[0038] Additionally, at this time, the request source device 8 receives specified information (e.g., elevator 1 identification information) for the elevator 1 designated as the object of motion information acquisition. Therefore, the request source device 8 sends a transmission start request containing the received specified information to the first server device 4. As a result, the first server device 4 can send the transmission start request to the communication device 3 set up for the specified elevator 1 and can receive motion information from the communication device 3.

[0039] Additionally, while the terminal device 9 is utilizing API 813, the requesting source device 8 sends a continue request to the first server device 4. In order to also send the continue request to the communication device 3 configured for the specified elevator 1, the first server device 4 sends the specified information of the specified elevator 1 to the communication device 3 along with the continue request.

[0040] The first server device 4 communicates with the communication device 3 using a first communication method. Therefore, the requesting source device 8 creates a second topic based on the elevator 1's identification information and sends a continued transmission request to the first server device 4 using this second topic. Thus, the first server device 4 can send the continued transmission request to the communication device 3, which is configured for the specified elevator 1 and has subscribed to the second topic.

[0041] Terminal device 9 is a device capable of accepting user input operations and notifying the user of motion information sent by elevator control device 2. Terminal device 9 can also be a device capable of notifying the user of detailed information sent by elevator control device 2. In this embodiment, terminal device 9 functions as a display device for displaying various information. Furthermore, terminal device 9 also functions as an input device capable of accepting user input operations. Terminal device 9 can accept user input operations for obtaining motion information of elevator 1 that the user wishes to understand. Additionally, terminal device 9 can accept user input operations specifying elevator 1 as the target for obtaining motion information.

[0042] Terminal device 9 may be, for example, a smartphone, tablet, or laptop, but is not limited to these. Terminal device 9 only needs to have at least communication functions, the ability to display various information, and the ability to accept input operations. In addition, there may be one or multiple terminal devices 9.

[0043] Terminal device 9, by utilizing API 813, enables requesting source device 8 to issue a start request and a continue request for sending specified elevator 1 motion information, and receives the motion information from requesting source device 8. When terminal device 9 begins using API 813, it accepts input operations specifying elevator 1 as the object of motion information acquisition. Therefore, terminal device 9 can send the specified information to requesting source device 8 when using API 813. Terminal device 9 can use API 813 to enable requesting source device 8 to issue each motion information sending request, and receive specified elevator 1 motion information from requesting source device 8.

[0044] When terminal device 9 first uses API 813, requesting source device 8 sends a start request to first server device 4. Subsequently, each time terminal device 9 uses API 813, requesting source device 8 sends a continue request to first server device 4. Furthermore, after the first use of API 813, terminal device 9 receives and displays the action information obtained by requesting source device 8 from storage device 7 each time API 813 is used. For example, during the operation of the aforementioned terminal-side software, terminal device 9 uses API 813 at a predetermined frequency (e.g., once every 10 seconds).

[0045] Furthermore, API 813 is not limited to passively providing action information to terminal device 9 based on a request from terminal device 9, but can also be provided to terminal device 9 actively. For example, it can be done as follows: when terminal device 9 has subscribed to a first topic from requesting source device 8, and requesting source device 8 has subscribed to the first topic from storage device 7, and the storage state of action information in storage device 7 changes (in the case that new action information is stored in storage device 7), requesting source device 8 publishes the action information stored in storage device 7 to terminal device 9.

[0046] <Method for sending start request> As described above, in this embodiment, the first server device 4 is configured to send a start request to the communication device 3 via the second server device 5 using a second communication method. However, it may also send the request directly to the communication device 3 using a first communication method without going through the second server device 5. In this case, for example, in order to monitor the receipt of the start request from the first server device 4, the communication device 3 must maintain a continuous communication session between the communication device 3 and the first server device 4 and subscribe according to the first communication method.

[0047] Therefore, the processing performance of the first server device 4 must be able to withstand the continuous connection of the aforementioned communication session. Furthermore, the communication session must be valid according to the number of communication devices 3. Since the number of communication devices 3 connected to the first server device 4 is usually large, a high-performance first server device 4 is required to handle the continuous large number of connections in the aforementioned communication session. In addition, the time required for real-time transmission of action information is often limited, and continuous connection of the aforementioned communication session will generate additional communication load.

[0048] Therefore, in this embodiment, the start request is sent to the communication device 3 via the second server device 5 and following the second communication method, thereby suppressing the processing load and communication load of the first server device 4.

[0049] <Purpose of the data transmission system> The data transmission system 100 of this embodiment includes a first server device 4 and a communication device 3 capable of communicating with each other according to a first communication method, and a first control line 101. After the communication device 3 receives a transmission start request for motion information and continuously receives transmission continue requests, the communication device 3 sends motion information to the first server device 4 whenever the motion status of the elevator 1 changes. Furthermore, the first server device 4 stores the received motion information in the storage device 7. Thus, in the data transmission system 100, during the operation of the terminal-side software of the terminal device 9 using API 813, the motion information stored in the storage device 7 can be acquired sequentially, allowing the user to observe the constantly changing motion status of the elevator 1 in real time. The specific functions and processing of such a data transmission system 100 will be described below.

[0050] [Detailed Description of the Data Transmission System] The following is based on Figure 1 This section primarily describes an example of the specific configuration of the communication device 3, the first server device 4, and the request source device 8.

[0051] <Communication device> like Figure 1 As shown, the communication device 3 includes, for example, a first control unit 31 and a second control unit 32. The first control unit 31 includes, for example, a receiving unit 311, a publishing unit 312, and a subscription unit 313. The second control unit 32 includes, for example, a transceiver unit 321.

[0052] The receiving unit 311 receives action information from the elevator control device 2. Whenever the operation status of the elevator 1 specified by the user changes, the receiving unit 311 receives action information from the elevator control device 2 via the first control line 101.

[0053] The publishing unit 312 controls the transmission and reception of data with the first server device 4 according to the first communication method, and switches the operation mode to one of the following: a sending mode, where the receiving unit 311 publishes the received action information to the first server device 4 with a predetermined first topic whenever it receives action information; or a non-sending mode, where no publication is performed. In this embodiment, when the communication device 3 (the transceiver unit 321 of the second control unit 32) receives a request to start sending action information, the publishing unit 312 switches the operation mode to the sending mode. Therefore, the publishing unit 312 can publish the action information to the first server device 4 at the moment it receives the request to start sending.

[0054] Furthermore, in the transmission mode, if the publishing unit 312 receives a transmission continuation request before a predetermined period has elapsed since the last transmission continuation request for action information was received from the communication device 3, it continues transmission mode. On the other hand, if the publishing unit 312 does not receive a transmission continuation request after a predetermined period has elapsed since the last transmission continuation request was received from the communication device 3, it switches to non-transmission mode. The predetermined period can be longer than the interval between consecutive transmission continuation requests. This interval can be the same as the interval used by the terminal device 9 using API 813.

[0055] The publishing unit 312 switches the operation mode based on the reception status of the continued request, thereby enabling the publishing side to easily determine whether the processing of publishing action information according to the first communication method should continue. Furthermore, since the first server device 4 acts as a proxy, it cannot monitor the communication device 3 or automatically acquire action information. Therefore, the communication device 3 determines whether to send action information to the first server device 4 by monitoring the reception status of the continued request (i.e., by monitoring the first server device 4).

[0056] The subscription unit 313 controls the transmission and reception of data with the first server device 4 according to the first communication method. When the operation mode is switched to the sending mode, it subscribes to the second topic created based on the identification information of the elevator 1 from the first server device 4. The second topic can be created by the first control unit 31 in a way that can identify the elevator 1.

[0057] As described above, the requesting source device 8 sends a continued transmission request to the first server device 4 using a second topic created based on the identification information of the specified elevator 1. Therefore, by subscribing to the second topic that identifies the elevator 1 connected to the communication device 3, the first server device 4 can send a continued transmission request to the communication device 3 connected to the specified elevator 1.

[0058] The transceiver unit 321 receives a transmission start request from the second server device 5 and sends a signal indicating that the transmission start request has been received to the first control unit 31. Therefore, upon receiving the transmission start request, the publishing unit 312 switches its operation mode to transmission mode, publishes operation information to the first server device 4, and the subscription unit 313 subscribes to the second topic from the first server device 4.

[0059] <First Server Device> like Figure 1 As shown, the first server device 4, which acts as a proxy, includes, for example, a server control unit 41. The server control unit 41 controls the operation of the first server device 4 and includes, for example, a first transmission unit 411, a second transmission unit 412, and a server transmission unit 413.

[0060] The first transmitting unit 411 sends the transmission continuation request issued by the requesting source device 8 to the first server device 4 with the second topic to the communication device 3 that has subscribed to the second topic from the first server device 4. Thus, the first server device 4 is able to send the transmission continuation request to the communication device 3 connected to the designated elevator 1.

[0061] When the second sending unit 412 receives the action information published by the publishing unit 312, it sends the received action information to the sending destination device 6, which has subscribed to the first topic from the first server device 4. Thus, the sending destination device 6 can store the specified elevator 1 action information received by the first server device 4 in the storage device 7. Therefore, the requesting source device 8 can retrieve the action information from the storage device 7 and send it to the terminal device 9.

[0062] Server sending unit 413 sends the transmission start request received from request source device 8 to second server device 5. Thus, first server device 4 can send the transmission start request to communication device 3 via second server device 5 (following the second communication method).

[0063] <Request source device> like Figure 1 As shown, the request source device 8 includes, for example, a request source control unit 81. The request source control unit 81 controls the operation of the request source device 8 and includes a request source sending unit 811, a request source publishing unit 812, and an API 813.

[0064] As described above, the request source sending unit 811 sends a transmission start request to the first server device 4 when API 813 is used again from the terminal device 9 after a predetermined period has elapsed since the last use of API 813. In this embodiment, when API 813 is used after a predetermined period of non-use, the request source sending unit 811 sends a transmission start request to the first server device 4, including specified information about the elevator 1 that is the target for obtaining motion information.

[0065] The request source publishing unit 812 publishes a continuation request to the first server device 4 using a second topic created based on the identification information of the specified elevator 1. In this embodiment, after the terminal device 9 first utilizes API 813, the request source publishing unit 812 publishes a continuation request to the first server device 4 using the second topic every time the terminal device 9 utilizes API 813. That is, during the period when the terminal device 9 provides action information from the request source device 8 to the terminal device 9 at a predetermined frequency using API 813, the request source publishing unit 812 publishes a continuation request to the first server device 4 using the second topic. The second topic only needs to be created in a way that the request source control unit 81 can identify the specified elevator 1. The predetermined frequency corresponds to the utilization frequency of API 813. When API 813 actively provides action information to the terminal device 9, the predetermined frequency can also be determined corresponding to the frequency of changes in the storage device 7.

[0066] API 813, as described above, is an example of a function for providing motion information of a specified elevator 1. Using API 813 via terminal device 9, request source sending unit 811 can specify elevator 1 as the object of motion information acquisition and send a start request to first server device 4. Additionally, request source publishing unit 812 can also specify elevator 1 as the object of motion information acquisition and send a continue request to first server device 4. Based on this transmission, the motion information of the specified elevator 1 is stored in storage device 7. Therefore, while terminal device 9 is using API 813, request source device 8 can sequentially retrieve the motion information of the specified elevator 1 from storage device 7 and send the retrieved motion information to terminal device 9.

[0067] [sequence] Next, based on Figures 2 to 4 The data flow between the various devices is explained. Figure 2 This is a sequence diagram representing an example of a data stream based on the first use of API 813. Figure 3 This is a sequence diagram representing an example of data streams using API 813 after switching to transmit mode, based on the second and subsequent uses. Figure 4 This is a sequence diagram representing an example of a data flow when API 813 is not used within a specified period.

[0068] Figure 3 It shows Figure 2 An example of a sequence following the sequence. Figure 4 It shows Figure 3 An example of a sequence following a sequence. Additionally, in Figures 2-4 In this context, whenever the operating status of elevator 1 changes, the operating information is sent from elevator control device 2 to communication device 3 via first control line 101.

[0069] In this embodiment, such as Figure 2 As shown, the destination device 6 subscribes to the first topic from the first server device 4 at a time point before the terminal device 9 uses API 813 (S1). Therefore, when the communication device 3 receives the transmission start request from the second server device 5 and publishes the action information to the first server device 4, the first server device 4 can send the action information to the destination device 6.

[0070] Terminal device 9 accepts an input operation for obtaining the user's desired status information about the elevator 1. Upon receiving this input operation, terminal device 9 utilizes API 813 (S2) of requesting source device 8. At this time, terminal device 9 sends the specified information about the elevator 1 specified by the user to requesting source device 8.

[0071] In the request source device 8, the request source sending unit 811 sends a transmission start request containing specified information to the first server device 4 (S3). In the first server device 4, the server sending unit 413 sends the transmission start request received from the request source device 8 to the second server device 5 (S4). The second server device 5 sends the transmission start request received from the first server device 4 to the communication device 3 (S5).

[0072] In communication device 3, transceiver unit 321 receives a transmission start request from second server device 5. Upon receiving this request, publishing unit 312 switches the operation mode from non-transmission mode to transmission mode (S6). Then, publishing unit 312 publishes the operation information received from elevator control device 2 to first server device 4 with a first topic (S8). Publishing unit 312 publishes the operation information received from elevator control device 2 to first server device 4 with a first topic whenever it receives operation information from elevator control device 2.

[0073] In addition, in the communication device 3, the transceiver unit 321 receives a transmission start request, and the subscription unit 313 subscribes to the first server device 4 for a second topic created based on the identification information of the elevator 1 connected to the communication device 3 (S7). The processing of S7 can be performed either before or simultaneously with the processing of S6, or at or after the start of the processing of S8, as long as the communication device 3 receives the transmission start request in S5.

[0074] In S1, the destination device 6 subscribes to a first topic from the first server device 4. Therefore, in the first server device 4, the second sending unit 412 sends the specified elevator 1 movement information published by the communication device 3 to the destination device 6 (S9). The second sending unit 412 sends movement information to the destination device 6 whenever it receives it from the communication device 3. Then, the destination device 6 stores the movement information in the storage device 7 whenever it receives it from the first server device 4 (S10).

[0075] Next, as Figure 3 As shown, after the terminal device 9 uses API 813 for the first time, it continues to use API 813 (S11). In the request source device 8, the request source publishing unit 812 publishes a continuing request for transmission to the first server device 4 based on a second topic created based on the identification information of elevator 1 (S12). As a result, the first server device 4 is able to send the continuing request for transmission published by the request source device 8 to the communication device 3 that has subscribed to the same second topic as the second topic.

[0076] exist Figure 2 In S7, the communication device 3 subscribes to a second topic created based on the identification information of the elevator 1 from the first server device 4. Therefore, in the first server device 4, the first sending unit 411 sends a transmission continuation request issued by the request source device 8 to the communication device 3, which has subscribed to the second topic created based on the identification information of the specified elevator 1 (S13).

[0077] Furthermore, in the request source device 8, the request source control unit 81, based on the utilization of API 813 in S11, sequentially retrieves the specified elevator 1's motion information from the storage device 7 (S14) and sends it to the terminal device 9 (S15). In the storage device 7, from... Figure 2 After step S10, the system stores motion information generated whenever the motion status of elevator 1 changes. Therefore, by sequentially receiving motion information from the requesting source device 8, the terminal device 9 can notify the user of the motion status of elevator 1 in real time.

[0078] In communication device 3, Figure 2After receiving the transmission start request in S5, the transceiver unit 321 starts timing. Then, the publishing unit 312 determines whether a transmission continuation request has been received before the specified period has elapsed since receiving the transmission start request. If the publishing unit 312 determines that the transmission continuation request sent in S13 has been received before the specified period has elapsed, it continues the transmission mode. Therefore, whenever the publishing unit 312 receives action information from the elevator control device 2, it continuously publishes it to the first server device 4 with a first topic (S16). The timing of the first control unit 31 is reset when it receives the transmission continuation request from the publishing unit 312 or when the specified period has elapsed.

[0079] In the first server device 4, the second sending unit 412 sends the designated elevator 1 movement information to the sending destination device 6 whenever it receives it from the communication device 3 (S17). Then, whenever the sending destination device 6 receives the movement information from the first server device 4, it stores it in the storage device 7 (S18).

[0080] On the other hand, the release department 312 judged it to be from Figure 2 If a predetermined period has elapsed since the start of transmission request was received in S5, the operation mode is switched from transmission mode to non-transmission mode. In non-transmission mode, even if communication device 3 receives operation information from elevator control device 2 whenever the operation status of elevator 1 changes, it does not transmit operation information to the first server device 4. That is, communication device 3 stops sending operation information to the first server device 4 by switching to non-transmission mode.

[0081] If terminal device 9 continues to use API 813 after its previous use of API 813 (S21), requesting source device 8 publishes a continued transmission request for a second topic created based on the identification information of elevator 1 to first server device 4 (S22). First server device 4 then sends the continued transmission request published by requesting source device 8 to communication device 3 that has subscribed to the same second topic as the second topic (S23).

[0082] Furthermore, in the request source device 8, the request source control unit 81, based on the utilization of API 813 in S21, sequentially retrieves the specified elevator 1's motion information from the storage device 7 (S24) and sends it to the terminal device 9 (S25). In the storage device 7, from... Figure 2 After step S10, the system continues to store motion information generated whenever the operating status of elevator 1 changes. Therefore, the request source device 8 can continuously send motion information representing the latest operating status of elevator 1 to the terminal device 9. Thus, the terminal device 9 can notify the user of the operating status of elevator 1 in real time.

[0083] In communication device 3, after receiving the transmission continuation request in S13, the first control unit 31 starts timing again. Then, the publishing unit 312 determines whether a next transmission continuation request will be received within a specified period after receiving the transmission continuation request. That is, the publishing unit 312 determines whether a transmission continuation request has been received before the specified period has elapsed since the last transmission continuation request was received. If the publishing unit 312 determines that the transmission continuation request sent in S23 was received before the specified period has elapsed, it continues the transmission mode. Therefore, whenever the publishing unit 312 receives action information from the elevator control device 2, it continuously publishes it to the first server device 4 with a first topic (S26).

[0084] In the first server device 4, the second sending unit 412 sends the designated elevator 1 movement information to the sending destination device 6 whenever it receives it from the communication device 3 (S27). Then, whenever the sending destination device 6 receives the movement information from the first server device 4, it stores it in the storage device 7 (S28).

[0085] Similarly, when terminal device 9 utilizes API 813 (S31), the request source publishing unit 812 of request source device 8 publishes a transmission continuation request with a second topic (S32). Then, the first sending unit 411 of the first server device 4 sends the transmission continuation request to the communication device 3, which has subscribed to the same second topic as the second topic (S33). Furthermore, request source device 8 continues to retrieve action information from storage device 7 (S34) and sends it to terminal device 9 (S35).

[0086] If the publishing unit 312 determines that it received the transmission continuation request in S33 after receiving it in S23, and receives the transmission continuation request in S33 before a predetermined period has elapsed, it continues the transmission mode. Therefore, whenever the publishing unit 312 receives action information from the elevator control device 2, it continuously publishes it to the first server device 4 with a first topic (S36). Then, the second transmitting unit 412 of the first server device 4 sends the action information published from the communication device 3 to the transmission destination device 6 (S37), and the transmission destination device 6 continues to store it in the storage device 7 (S38). Figure 4 The same applies to S41-S48 shown.

[0087] Thus, during the period from receiving the continue request to receiving the next continue request (i.e., the period during which the continue request is continuously received), the publishing unit 312 continuously publishes the action information to the first server device 4. Therefore, while the terminal device 9 is continuously using API 813, the requesting source device 8 can send action information indicating the latest action status of the elevator 1 to the terminal device 9.

[0088] On the other hand, if the issuing unit 312 determines that a specified period has elapsed since the last received request to continue sending was not received, it switches the operation mode from sending mode to non-sending mode. For example... Figure 4 As shown, if the publishing unit 312 determines that it has received a transmission continuation request in S43 and has not received a next transmission continuation request before the specified period has elapsed, it switches the operation mode from transmission mode to non-transmission mode (S51).

[0089] As described above, whenever the operating status of the elevator 1 controlled by the elevator control device 2 changes, it sends the operation information to the communication device 3. However, in the communication device 3, the publishing unit 312, after switching to the non-transmitting mode, does not publish the operation information to the first server device 4 even if it receives the operation information. That is, the communication device 3 stops sending operation information to the first server device 4 by switching to the non-transmitting mode.

[0090] Therefore, communication device 3 can only send action information to the first server device 4 after receiving a send start request and while continuously receiving send continue requests. In other words, action information can only be sent to the first server device 4 while API 813 is continuously being used. Therefore, while API 813 is being used, terminal device 9 can notify the user of the elevator 1's operation status in real time. On the other hand, when API 813 is not being used, since no communication session following the first communication method is established between communication device 3 and the first server device 4, unnecessary communication load can be suppressed.

[0091] When multiple terminal devices 9 have designated the same elevator 1, when any terminal device 9 uses API 813, it requests the source device 8 to send a request to the first server device 4 to initiate the transmission of motion information about the elevator 1. Based on this transmission, the communication device 3 can switch the motion mode to the transmission mode.

[0092] As described above, if the communication device 3 receives a transmission continuation request and then receives another transmission continuation request before a predetermined period has elapsed, it maintains the transmission mode. When any terminal device 9 is using API 813, the requesting source device 8 sends a transmission continuation request to the first server device 4. Therefore, while any terminal device 9 is using API 813, the communication device 3 maintains the transmission mode and continuously publishes action information to the first server device 4.

[0093] On the other hand, when all terminal devices 9 do not utilize API 813, the request source device 8 stops sending transmission continuation requests to the first server device 4. That is, if it is determined that none of the users have viewed the specified elevator 1's movement information, the request source device 8 stops sending transmission continuation requests to the first server device 4. Therefore, since all terminal devices 9 do not utilize API 813, if the communication device 3 does not receive a transmission continuation request after a specified period since last receiving it from the first server device 4, it switches to non-transmission mode. By switching to non-transmission mode, the communication device 3 stops sending the specified movement information to the first server device 4.

[0094] Thus, when multiple users attempt to view the operational status of a specific elevator 1, the communication device 3 maintains the switched transmission mode. Consequently, at least one of the multiple terminal devices 9 can notify the users of the operational status of the elevator 1 in real time. Furthermore, the communication device 3 only switches to non-transmission mode and stops sending operational information to the first server device 4 when none of the users have viewed the operational status of the specific elevator 1.

[0095] [Summarize] The data transmission system of Embodiment 1 of the present invention includes: a server device that can communicate with each other using a publish / subscribe communication method and acts as a proxy, and one or more communication devices; the communication devices include: a receiving unit that receives motion information related to the operation status of an elevator controlled by an elevator control device communicatively connected to the device; a publishing unit that switches the operation mode to any of the following: a sending mode in which, whenever the receiving unit receives the motion information, the received motion information is published to the server device with a predetermined first topic; and a non-sending mode in which the publishing is not performed; and a subscribing unit that, when switching to the sending mode, subscribes to the server device. The server device includes a first sending unit that sends a request to a communication device that has subscribed to the second topic to continue sending the action information published by the requesting source device to the server device on the second topic. The publishing unit, in the sending mode, continues sending if it receives the continued sending request after a predetermined period has elapsed since the last time the communication device received it, and switches to the non-sending mode if it has not received the continued sending request after the last time the communication device received it and the predetermined period has elapsed.

[0096] In the data transmission system of the present invention, in Method 1, the elevator control device sends the action information to the communication device whenever the action status of the elevator controlled by the elevator control device changes.

[0097] In the data transmission system of embodiment 3 of the present invention, in embodiment 1 or 2, the requesting source device has the following functions: providing the motion information of a specified elevator that is available to the terminal device of the user of the data transmission system; and, while the terminal device is providing the motion information from the requesting source device to the terminal device at a predetermined frequency using the function, publishing the transmission continuation request to the server device based on a second topic created according to the identification information of the specified elevator.

[0098] In the data transmission system of embodiment 4 of the present invention, in any one of embodiments 1-3, the server device includes: a second transmission unit that, upon receiving the action information published from the publishing unit, sends the received action information to a destination device that has subscribed to the first topic from the server device; the destination device, each time it receives the action information from the server device, performs the following processing: storing the received action information in a storage device; the requesting source device has the following function: providing the action information of a specified elevator that is available to a terminal device of a user of the data transmission system; when the terminal device is using the function, sequentially retrieving the action information of the specified elevator from the storage device and sending the retrieved action information to the terminal device.

[0099] In the data transmission system of embodiment 5 of the present invention, in any one of embodiments 1-4, the request source device has the following functions: providing the specified elevator's operation information available to the terminal device of the user of the data transmission system; and performing the following processing when the terminal device uses the function again after the specified period has elapsed since the last use of the function: sending a transmission start request for the operation information to the communication device; and when the communication device receives the transmission start request, the publishing unit switches the operation mode to the transmission mode.

[0100] In the data transmission system of embodiment 6 of the present invention, in any one of embodiments 3-5, the function is provided by an application programming interface (API).

[0101] [Software Implementation Example] The functions of each device (except for storage device 7) (hereinafter referred to as "device") in the data transmission system 100 can be realized by a program that enables the computer to function as the device, or by a program that enables the computer to function as each control block of the device (in particular, each of the units included in the first control unit 31, the second control unit 32, the server control unit 41, and the request source control unit 81).

[0102] In this case, the aforementioned apparatus, as hardware for executing the aforementioned program, comprises a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., a memory). The aforementioned program is executed by the control device and the storage device, thereby realizing the functions described in the above embodiments.

[0103] The above-described program can also be recorded on one or more non-transitory, computer-readable recording media. The above-described device may or may not have such a recording medium. In the latter case, the above-described program can be provided to the above-described device via any wired or wireless transmission medium.

[0104] Furthermore, some or all of the functions of the aforementioned control blocks can also be implemented by logic circuits. For example, integrated circuits that form the logic circuits that function as the aforementioned control blocks are also included within the scope of this invention. In addition, the functions of the aforementioned control blocks can also be implemented by a quantum computer, for example.

[0105] Furthermore, the processes described in the above embodiments can also be performed by AI (Artificial Intelligence). In this case, the AI ​​can run in the aforementioned control device or in other devices (such as edge computers or cloud servers).

[0106] [Additional Notes] This invention is not limited to the above-described embodiments. Various modifications can be made within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of this invention.

[0107] Explanation of reference numerals in the attached figures 1 elevator 2. Elevator control device 3 communication device 4. First server device (server device) 6. Sending destination device 7 storage devices 8 Request source device 9 terminal devices 100 Data Transmission System 311 Receiving Department 312 Release Department 313 Subscription Department 411 First Sending Unit 412 Second Sending Unit 813 API (functionality).

Claims

1. A data transmission system, including: A server device that can communicate with each other using a publish / subscribe communication method and acts as a proxy, and one or more communication devices; The communication device includes: The receiving unit receives motion information related to the motion status of the elevator controlled by the elevator control device from the elevator control device that is communicatively connected to this device. The publishing unit switches the action mode to any of the following: sending mode, whenever the receiving unit receives the action information, it publishes the received action information to the server device with a predetermined first topic; And, in non-sending mode, no publication is performed; and, The subscription unit, when switching to the sending mode, subscribes to a second topic created based on the elevator's identification information from the server device; The server device includes: The first sending unit sends a request to the communication device that has subscribed to the second topic to the server device to continue sending the action information published by the requesting source device to the server device on the second topic; The publishing unit is in the sending mode. If the communication device receives the transmission continuation request again after a predetermined period has elapsed since the last time it received the transmission continuation request, the transmission mode continues. If the communication device has not received the transmission continuation request after the last time it received the transmission continuation request and the specified period has elapsed, it switches to the non-transmission mode.

2. In the data transmission system according to claim 1, the elevator control device sends the action information to the communication device whenever the action status of the elevator controlled by the elevator control device changes.

3. The data transmission system according to claim 1, wherein the request source device has the following function: providing the specified elevator's motion information that is available to the terminal device of the user of the data transmission system; While the terminal device is providing the action information from the requesting source device to the terminal device at a predetermined frequency using the function, the send continuation request is sent to the server device based on the second topic created according to the identification information of the specified elevator.

4. The data transmission system according to claim 1, wherein the server device comprises: When the second sending unit receives the action information published by the publishing unit, it sends the received action information to a sending destination device that has subscribed to the first topic from the server device. Each time the sending destination device receives the action information from the server device, it performs the following process: stores the received action information in a storage device; The request source device has the following function: providing the specified elevator's motion information that can be used by the terminal device of the user of the data transmission system; When the terminal device is using the function, it sequentially retrieves the specified elevator's motion information from the storage device and sends the retrieved motion information to the terminal device.

5. The data transmission system according to claim 1, wherein the request source device has the following function: providing the specified elevator's motion information that is available to the terminal device of the user of the data transmission system; When the terminal device uses the function again after the specified period has elapsed since the last use of the function, the following process is performed: a request to start sending the action information is sent to the communication device; When the communication device receives the transmission start request, the publishing unit switches the operation mode to the transmission mode.

6. The data transmission system according to any one of claims 3 to 5, wherein the function is provided by an application programming interface (API).

Images