Data Transmission System
The data transmission system for elevators uses a publish/subscribe method with a broker server and communication devices to manage transmission modes, addressing the inefficiencies in existing systems and ensuring real-time information delivery to terminal devices.
Patent Information
- Application Number
- JP2024027620
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-02-27
- Publication Date
- 2025-01-17
- Estimated Expiration
- 2044-02-27
AI Technical Summary
Existing systems for monitoring elevators do not utilize a publish/subscribe type communication method to efficiently transmit and receive operating information, lacking the ability for the publishing side to determine whether to continue the process of publishing such information.
A data transmission system employing a server device as a broker and communication devices that use a publish/subscribe communication method, with a receiving unit, publishing unit, and subscribing unit to manage transmission modes based on request intervals, allowing for efficient control of information flow.
Enables the publishing side to easily determine whether to continue publishing elevator operating information, optimizing communication load and ensuring real-time information delivery to terminal devices.
Smart Images

Figure 0007616450000001_ABST
Abstract
Description
[Technical field]
[0001] One aspect of the present invention relates to a data transmission system for transmitting operational information regarding the operating 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, a connection is made to a specific monitor's mobile phone, and video data from a surveillance camera installed at the elevator hall is transmitted to the monitor's mobile phone. In this system, the video data to be transmitted to the mobile phone is switched in response to a command to switch the video data of the monitored object. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 4369253 Summary of the Invention [Problem to be solved by the invention]
[0004] However, Patent Document 1 does not disclose any technology related to sending and receiving information about elevators using a publish / subscribe type communication method.
[0005] One aspect of the present invention aims to enable a publishing side to easily determine whether or not to continue a process of publishing operation information regarding the operating status of an elevator using a publish / subscribe type communication method. [Means for solving the problem]
[0006] A data transmission system according to one embodiment of the present invention is a data transmission system including a server device functioning as a broker and one or more communication devices capable of communicating with each other using a publish / subscribe type communication method, wherein the communication device includes a receiving unit that receives operation information relating to the operating status of an elevator controlled by an elevator control device connected to the communication device, a publishing unit that switches an operation mode between a sending mode in which the receiving unit publishes the received operation information to the server device using a predetermined first topic each time the receiving unit receives the operation information, and a non-transmission mode in which the publishing is not performed, and a publishing unit that, when switching to the sending mode, publishes the received operation information to the server device using a predetermined first topic, and a non-transmission mode in which the publishing is not performed. and a subscribing unit that subscribes to a second topic created based on the identification information of the communication device, and the server device comprises a first transmitting unit that transmits a request for continuation of transmission of the operation information, published to the server device by a request source device using the second topic, to the communication device that has subscribed to the second topic for the server device, and the publishing unit continues the transmission mode if, during the transmission mode, the communication device receives the continuation of transmission request within a predetermined period of time since the communication device last received the continuation of transmission request, and switches to the non-transmission mode if the predetermined period of time has elapsed since the communication device last received the continuation of transmission request without receiving the continuation of transmission request. Effect of the Invention
[0007] According to one aspect of the present invention, the publisher can easily determine whether to continue the process of publishing operation information regarding the operating status of an elevator using a publish / subscribe communication method. [Brief description of the drawings]
[0008] [Figure 1] 1 is a block diagram showing an example of a configuration of a data transmission system according to an embodiment of the present invention. [Diagram 2] 13 is a sequence illustrating an example of a data flow based on an initial use of an API. [Diagram 3] 13 is a sequence showing an example of a data flow based on the second or subsequent use of the API after switching to a transmission mode. [Figure 4] 13 is a sequence showing an example of a data flow when an API has not been used for a predetermined period of time. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] The data transmission system 100 of this embodiment will be described below.
[0010] [Outline of the data transmission system] First, an overview of a data transmission system 100 will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the data transmission system 100.
[0011] The data transmission system 100 is a system capable of transmitting operation information relating to the operation status of the elevator 1 controlled by the elevator control device 2 from the elevator control device 2 to a terminal device 9. The data transmission system 100 transmits the operation information of the elevator 1 to the terminal device 9, thereby enabling a user of the terminal device 9 to grasp the operation status of the elevator 1.
[0012] The operation information includes, for example, information on the occurrence of an abnormality in the elevator 1 and the operation status of the elevator 1. The information indicating the operation status may include, for example, information on the position of the car, the weight inside the car, and the opening and closing status of the doors. The operation information is associated with the identification information of the elevator 1. In addition to the operation information, the identification information of the elevator 1 may be associated with detailed information on the elevator 1, such as the model name of the elevator 1 and installation information of the elevator 1.
[0013] The elevator 1 from which operation information is to be acquired may be one or more. However, it is preferable that the operation information of the elevator 1 designated by the user is transmitted to the terminal device 9.
[0014] A user of the data transmission system 100 is, for example, a user who gets on and off the elevator 1. A user of the data transmission system 100 may be, for example, a manager of the elevator 1. A user of the data transmission system 100 may also be, for example, a maintenance worker who performs maintenance on the elevator 1. In this case, a monitoring device that monitors the operating status of the elevator 1 may be used as the terminal device 9.
[0015] In this embodiment, as shown in Fig. 1, 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. As shown in the figure, the first server device 4, the second server device 5, the storage device 7, and the request source device 8 may be built on, for example, a virtual private cloud (VPC). Furthermore, a part or the whole of the destination device 6 may be built on the virtual private cloud.
[0016] The elevator control device 2 is communicatively connected to the elevator 1, and is a device that controls the operation of the elevator 1 and monitors the operation status of the elevator 1. The elevator control device 2 is communicatively connected to a communication device 3, and transmits operation information of the elevator 1 controlled by the elevator control device 2 to the communication device 3. The elevator control device 2 may transmit detailed information of the elevator 1 to the communication device 3 together with the operation information.
[0017] The elevator control device 2 generates operation information in association with the identification information of the elevator 1, and transmits the operation information to the communication device 3 by method A described below. Furthermore, the elevator control device 2 may be capable of transmitting the operation information to the communication device 3 by method B described below. Note that method B is a method that has traditionally been adopted in many cases as a communication method between the elevator control device 2 and the communication device 3. Therefore, the data transmission system 100 may be constructed by adding method A to an existing system that adopts method B.
[0018] (Method A: Push type) The elevator control device 2 transmits operation information to the communication device 3 every time a change occurs in the operating status of the elevator 1. In this case, the elevator control device 2 transmits operation information to the communication device 3 every time it generates the operation information, via the first control line 101 connecting the elevator control device 2 and the communication device 3. In method A, the communication device 3 does not request the elevator control device 2 to transmit the operation information.
[0019] (Method B: Pull type) Upon receiving a transmission request for operation information from the communication device 3, the elevator control device 2 transmits the operation information to the communication device 3 as a response to the transmission request. In this case, the elevator control device 2 transmits the operation information to the communication device 3 via the second control line 102 connecting the elevator control device 2 and the communication device 3. A transmission request to the elevator control device 2 by method B is hereinafter referred to as a "transmission request each time."
[0020] The operating status of the elevator 1 may change from moment to moment. Therefore, the frequency of transmitting the operating information by the above method A is higher than the frequency of transmitting the operating information by the above method B. Therefore, it is preferable to adopt a communication standard for the first control line 101 that allows more frequent communication than the second control line 102. For example, the first control line 101 may be RS422, and the second control line 102 may be RS232C. However, the same communication standard as that of the first control line 101 may be adopted for the second control line 102.
[0021] The communication device 3 is communicatively connected to each of the first server device 4 and the second server device 5, and transmits and receives data between the first server device 4 and the second server device 5. For example, Soracom (registered trademark) can be used for communication between the communication device 3 and each of the first server device 4 and the second server device 5. Note that the communication network connecting the communication device 3 and the first server device 4 and the communication network connecting the communication device 3 and the second server device 5 may be physically the same or may be physically separate.
[0022] The communication device 3 transmits the operation information received from the elevator control device 2 by the above method A to the first server device 4. Specifically, the communication device 3 starts transmitting the operation information received from the elevator control device 2 by the above method A to the first server device 4 at a predetermined timing according to a publish / subscribe communication method, and stops transmitting the information to the first server device 4 at a predetermined timing. That is, the communication device 3 is a device capable of communicating with the first server device 4 according to the publish / subscribe communication method. The publish / subscribe communication method is hereinafter referred to as the "first communication method." A protocol used in the first communication method is preferably, for example, MQTT (Message Queuing Telemetry Transport). By using the MQTT protocol, the operation information can be transmitted from the communication device 3 to the first server device 4 at a high frequency. Therefore, the operation information transmitted from the elevator control device 2 to the communication device 3 at a high frequency according to the above method A is subsequently transmitted from the communication device 3 to the first server device 4 at a high frequency. That is, in the data transmission system 100, the operation information can be transmitted from the elevator control device 2 to the first server device 4 at a high frequency.
[0023] On the other hand, the communication device 3 may transmit the operation information received from the elevator control device 2 by the above method B to the second server device 5 in accordance with a second communication method different from the first communication method. The second communication method does not need to be a publish / subscribe type, and may use, for example, a protocol based on TCP / IP (Transmission Control Protocol / Internet Protocol), or may use an independently defined protocol. The second communication method is a method that is often adopted as a communication method between existing elevator monitoring systems and the communication device 3.
[0024] In the above method B, the operation information to be transmitted by the elevator control device 2 to the communication device 3 as a response to the each-time transmission request may be the latest operation information at the time when the each-time transmission request is received from the communication device 3, or may be untransmitted operation information accumulated up to the time when the each-time transmission request is received. In the latter case, the elevator control device 2 may generate operation information every time a change occurs in the operation status of the elevator 1 and store the information in a storage unit (not shown) of the elevator control device 2. In this case, when the communication device 3 receives the each-time transmission request from the second server device 5, the communication device 3 may transmit the operation information stored in the storage unit (not shown) of the communication device 3 at that time to the second server device 5 as a response to the each-time transmission request.
[0025] The communication device 3 also receives a "transmission start request" of the operation information from the second server device 5 according to the second communication method. Upon receiving the transmission start request, the communication device 3 transmits the operation information to the first server device 4 according to the first communication method every time the communication device 3 receives operation information from the elevator control device 2. In other words, the transmission start request is a request to start real-time transmission of the operation information to the first server device 4. The communication device 3 also receives a "continue transmission request" of the operation information from the first server device 4 according to the first communication method. While the communication device 3 continues to receive the transmission continuation request, the communication device 3 continues to transmit the operation information received from the elevator control device 2 to the first server device 4. In other words, the transmission continuation request is a request to continue real-time transmission of the operation information to the first server device 4.
[0026] One elevator control device 2 and one communication device 3 are provided for each elevator 1. As described above, the data transmission system 100 may include one elevator 1 or multiple elevators 1. When the data transmission system 100 includes multiple elevators 1, one set of the elevator control device 2 and the communication device 3 is provided for each elevator 1.
[0027] The first server device 4 is a device that functions as a broker and is capable of communicating with the communication device 3 according to the first communication method. The data transmission system 100 may be a system that includes at least the first server device 4 as a broker and the communication device 3, which are capable of communicating with each other according to the first communication method. While receiving operation information from the communication device 3 according to the first communication method, the first server device 4 transmits the received operation information to the destination device 6 every time it receives operation information.
[0028] Moreover, the first server device 4 is a device that is communicatively connected to the second server device 5 and the request originating device 8 according to the first communication method. The first server device 4 transmits a transmission continuation request received from the request originating device 8 to the communication device 3 according to the first communication method, while transmitting a transmission start request received from the request originating device 8 to the second server device 5 according to the second communication method.
[0029] The first server device 4 functions as a broker. Therefore, the communication device 3 subscribes to the first server device 4 so that the first server device 4 can transmit the transmission continuation request received from the request source device 8 to the communication device 3. This subscription will be described later as an explanation of a subscribing unit 313 of the communication device 3.
[0030] The second server device 5 transmits the transmission start request for the operation information received from the first server device 4 to the communication device 3 according to the second communication method. Furthermore, when the second server device 5 receives a transmission request for the operation information from the request source device 8, it may transmit the transmission request for the operation information to the communication device 3 according to the second communication method and receive the operation information as a response to the transmission request for the operation information. In this case, the second server device 5 executes a process for storing the received operation information in the storage device 7. In this embodiment, the second server device 5 directly stores the operation information in the storage device 7, but the operation information may be stored in the storage device 7 via a relay device.
[0031] The destination device 6 is a device that executes a process for storing the received operation information in the storage device 7 every time the destination device 6 receives operation information from the first server device 4. In this embodiment, the destination device 6 directly stores the operation information in the storage device 7, but may store the operation information in the storage device 7 via a relay device. The 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 that stores the operation information, and includes, for example, a database. The database included in the storage device 7 is preferably a NoSQL such as a key-value type database that has excellent scalability in order to store the operation information transmitted at a high frequency. The database and the mechanism for storing the operation information in the database may be provided as a database cloud service.
[0032] As described above, the first server device 4 functions as a broker. Therefore, the destination device 6 subscribes to a predetermined first topic for the first server device 4 so that the first server device 4 can transmit the operation information received from the communication device 3 to the destination device 6. The first topic is a topic for receiving the operation information, and may be set to any value.
[0033] After receiving the transmission start request, the communication device 3 starts transmitting the operation information to the first server device 4. Therefore, in order for the first server device 4 to be able to transmit the operation information to the destination device 6 every time it receives it, the destination device 6 subscribes to the first topic for the first server device 4 before the first server device 4 starts receiving the operation information. In this embodiment, the destination device 6 subscribes to the first topic for the first server device 4 before the terminal device 9 uses (calls) an API (Application Programming Interface) 813.
[0034] The requesting device 8 has a function for providing operation information of the specified elevator 1 that is available to the terminal device 9. In this embodiment, the requesting device 8 is, for example, a Web server, and the function is provided by the API 813. The API 813 is a software interface that is available to a Web browser or application software (hereinafter, these will be simply referred to as "terminal side software") executed in the terminal device 9, and is used to acquire operation information of the elevator 1 stored in the storage device 7 and transmit the acquired operation information to the terminal device 9. While the terminal device 9 is using the API 813, the requesting device 8 sequentially acquires operation information of the specified elevator 1 from the storage device 7 and transmits the acquired operation information to the terminal device 9. "The terminal device 9 is using the API 813" refers to a state in which the terminal device 9 is executing terminal side software that can use the API 813 in order to acquire operation information of the elevator 1 specified by the user.
[0035] When the API 813 is used from the terminal device 9 after a predetermined period of time has elapsed since the API 813 was last used from the terminal device 9, the request sending device 8 executes processing for transmitting a transmission start request for operation information to the first server device 4. That is, the request sending device 8 transmits a transmission start request to the first server device 4 when the terminal device 9 starts using the API 813. In this embodiment, the request sending device 8 transmits the transmission start request directly to the first server device 4, but may transmit the transmission start request to the first server device 4 via a relay device.
[0036] At this time, the request sending device 8 also receives designation information (e.g., identification information of the elevator 1) designating the elevator 1 from which operation information is to be acquired. Therefore, the request sending device 8 transmits a transmission start request including the received designation information to the first server device 4. This enables the first server device 4 to transmit the transmission start request to the communication device 3 provided for the designated elevator 1, and to receive operation information from the communication device 3.
[0037] Furthermore, while the terminal device 9 is using the API 813, the request sending device 8 transmits a transmission continuation request to the first server device 4. The first server device 4 transmits the transmission continuation request to the communication device 3 provided for the specified elevator 1, and therefore transmits elevator 1 designation information together with the transmission continuation request to the communication device 3.
[0038] The first server device 4 transmits and receives data to and from the communication device 3 according to the first communication method. To this end, the request source device 8 creates a second topic based on the identification information of the elevator 1, and publishes a continuation transmission request to the first server device 4 using the created second topic. This enables the first server device 4 to transmit the continuation transmission request to the communication device 3 provided for the specified elevator 1 and subscribes to the second topic.
[0039] The terminal device 9 is a device capable of accepting input operations from a user and notifying the user of operation information transmitted by the elevator control device 2. The terminal device 9 may be a device capable of notifying the user of detailed information transmitted by the elevator control device 2. In this embodiment, the terminal device 9 functions as a display device that displays various information. The terminal device 9 also functions as an input device that can accept input operations from a user. The terminal device 9 can accept, as an input operation from a user, an operation for acquiring operation information of the elevator 1 whose operating status the user wishes to know. The terminal device 9 can also accept, as an input operation from a user, an operation for designating the elevator 1 from which operation information is to be acquired.
[0040] The terminal device 9 may be, for example, a smartphone, a tablet terminal, a notebook computer, etc., but is not limited thereto. The terminal device 9 may have at least a communication function, a function for displaying various information, and a function for accepting input operations. The terminal device 9 may be one or more.
[0041] By utilizing the API 813, the terminal device 9 can cause the request sending device 8 to issue a request to start transmitting and a request to continue transmitting operation information of the specified elevator 1, and can also receive the operation information from the request sending device 8. When starting to use the API 813, the terminal device 9 accepts an input operation for specifying the elevator 1 from which operation information is to be acquired. This allows the terminal device 9 to transmit the specified information to the request sending device 8 when using the API 813. By utilizing the API 813, the terminal device 9 can cause the request sending device 8 to issue a request to transmit operation information each time, and can also receive operation information of the specified elevator 1 from the request sending device 8.
[0042] When the terminal device 9 uses the API 813 for the first time, the request source device 8 transmits a transmission start request to the first server device 4, and thereafter, each time the terminal device 9 uses the API 813, the request source device 8 transmits a transmission continuation request to the first server device 4. Furthermore, after the first use of the API 813, the terminal device 9 receives and displays the operation information acquired by the request source device 8 from the storage device 7 each time the API 813 is used. The terminal device 9 uses the API 813 at a predetermined frequency (e.g., once every 10 seconds) while the above-mentioned terminal side software is running, for example.
[0043] The API 813 is not limited to a form in which it passively provides the operation information to the terminal device 9 in response to a request from the terminal device 9, and may be a form in which it actively provides the operation information to the terminal device 9. For example, in a situation in which the terminal device 9 subscribes to a first topic to the requesting device 8 and the requesting device 8 subscribes to the first topic to the storage device 7, if a change occurs in the storage device 7's storage state of the operation information (if new operation information is stored in the storage device 7), the requesting device 8 may publish the operation information stored in the storage device 7 to the terminal device 9.
[0044] <How to send a request to start sending> As described above, in the present embodiment, the first server device 4 is configured to transmit the transmission start request to the communication device 3 in the second communication method via the second server device 5, but the request may be transmitted directly to the communication device 3 in the first communication method without going through the second server device 5. In this case, however, for example, in order for the communication device 3 to monitor the reception of the transmission start request from the first server device 4, it becomes necessary to constantly connect the communication session between the communication device 3 and the first server device 4 and subscribe according to the first communication method.
[0045] Therefore, the first server device 4 is required to have a processing performance capable of withstanding the constant connection of the communication session. Moreover, the communication sessions must be kept valid for the number of communication devices 3, and since a large number of communication devices 3 are generally connected to the first server device 4, a high-performance first server device 4 is required to keep the communication sessions constantly connected. Furthermore, while the time during which real-time transmission of operation information is required is often limited, keeping the communication sessions constantly connected generates an extra communication load.
[0046] Therefore, in this embodiment, the transmission start request is transmitted to the communication device 3 via the second server device 5 in accordance with the second communication method, thereby realizing suppression of the processing load and communication load on the first server device 4.
[0047] <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 that can communicate with each other according to a first communication method, and a first control line 101. After the communication device 3 receives a request to start transmitting operation information, while the communication device 3 is continuously receiving a request to continue transmitting, the communication device 3 transmits operation information to the first server device 4 every time the operation status of the elevator 1 changes. Then, the first server device 4 stores the operation information in the storage device 7 every time it receives the operation information. As a result, in the data transmission system 100, the terminal device 9 can sequentially obtain the operation information stored in the storage device 7 during the period in which the terminal side software using the API 813 is being executed, and the user can visually check the operation status of the elevator 1, which may change from moment to moment, in real time. An example of specific functions and processes that realize such a data transmission system 100 will be described below.
[0048] [Details of the data transmission system] In the following, referring to FIG. 1, an example of a specific configuration of the communication device 3, the first server device 4, and the request sending device 8 will be mainly described.
[0049] <Communication Device> 1, 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 subscribing unit 313. The second control unit 32 includes, for example, a transmitting / receiving unit 321.
[0050] The receiving unit 311 receives operation information from the elevator control device 2. The receiving unit 311 receives the operation information from the elevator control device 2 via the first control line 101 every time the operational status of the elevator 1 specified by the user changes.
[0051] The publishing unit 312 controls transmission and reception of data with the first server device 4 in accordance with the first communication method, and switches the operation mode between a transmission mode in which the received operation information is published to the first server device 4 using a predetermined first topic every time the receiving unit 311 receives operation information, and a non-transmission mode in which the publishing is not performed. In this embodiment, the publishing unit 312 switches the operation mode to the transmission mode when the communication device 3 (the transmitting / receiving unit 321 of the second control unit 32) receives a request to start transmitting operation information. This allows the publishing unit 312 to publish the operation information to the first server device 4 at the timing when the transmitting / receiving unit 312 receives the request to start transmitting operation information.
[0052] Furthermore, if the publishing unit 312 receives a transmission continuation request before a predetermined period has elapsed since the communication device 3 last received a transmission continuation request for operation information during the transmission mode, the publishing unit 312 continues the transmission mode. On the other hand, if a predetermined period has elapsed since the communication device 3 last received a transmission continuation request without receiving a transmission continuation request, the publishing unit 312 switches to the non-transmission mode. The predetermined period may be longer than the reception interval of continuous transmission continuation requests. The reception interval may be equal to the interval at which the terminal device 9 uses the API 813.
[0053] The publishing unit 312 switches the operation mode depending on the reception status of the transmission continuation request, so that the publishing side can easily determine whether or not to continue the process of publishing the operation information according to the first communication method. Also, since the first server device 4 functions as a broker, it cannot actively obtain the operation information by monitoring the communication device 3. Therefore, the communication device 3 determines whether or not to transmit the operation information to the first server device 4 by monitoring the reception status of the transmission continuation request (i.e., by monitoring the first server device 4).
[0054] The subscribing unit 313 controls transmission and reception of data with the first server device 4 in accordance with the first communication method, and when the operation mode switches to the transmission mode, subscribes to a second topic created based on the identification information of the elevator 1 for the first server device 4. The second topic only needs to be created by the first control unit 31 so that the elevator 1 can be identified.
[0055] As described above, the request sending device 8 publishes the transmission continuation request to the first server device 4 in the second topic created based on the identification information of the specified elevator 1. Therefore, by subscribing to the second topic that can identify the elevator 1 to which the communication device 3 is connected to the first server device 4, the first server device 4 can transmit the transmission continuation request to the communication device 3 connected to the specified elevator 1.
[0056] The transmitting / receiving unit 321 receives the transmission start request from the second server device 5, and transmits a signal indicating that the transmission start request has been received, to the first control unit 31. As a result, at the timing when the transmitting / receiving unit 321 receives the transmission start request, the publishing unit 312 switches the operation mode to the transmission mode and publishes the operation information to the first server device 4, and the subscribing unit 313 subscribes to the second topic for the first server device 4.
[0057] <First server device> 1, the first server device 4 functioning as a broker 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.
[0058] The first transmitting unit 411 transmits the transmission continuation request published by the request source device 8 to the first server device 4 using the second topic to the communication device 3 that has subscribed to the second topic for the first server device 4. This enables the first server device 4 to transmit the transmission continuation request to the communication device 3 connected to the specified elevator 1.
[0059] When the second transmitting unit 412 receives the operation information published from the publishing unit 312, it transmits the received operation information to the destination device 6 that has subscribed to the first topic for the first server device 4. This allows the destination device 6 to store the operation information of the specified elevator 1 received by the first server device 4 in the storage device 7. Therefore, the requesting device 8 can obtain the operation information from the storage device 7 and transmit it to the terminal device 9.
[0060] The server transmitting unit 413 transmits the transmission start request received from the request source device 8 to the second server device 5. This allows the first server device 4 to transmit the transmission start request to the communication device 3 via the second server device 5 (in accordance with the second communication method).
[0061] <Requesting device> 1, the request sending device 8 includes, for example, a request sending control unit 81. The request sending control unit 81 controls the operation of the request sending device 8, and includes a request sending transmission unit 811, a request sending publishing unit 812, and an API 813.
[0062] As described above, when the API 813 is used from the terminal device 9 after a predetermined period of time has elapsed since the API 813 was last used from the terminal device 9, the request source sending unit 811 sends a transmission start request to the first server device 4. In this embodiment, when the API 813 is used in a state in which the API 813 has not been used for a predetermined period of time, the request source sending unit 811 sends a transmission start request to the first server device 4, including designation information that designates the elevator 1 from which operation information is to be acquired.
[0063] The request source publishing unit 812 publishes the transmission continuation request to the first server device 4 in the second topic created based on the identification information of the specified elevator 1. In this embodiment, after the terminal device 9 uses the API 813 for the first time, the request source publishing unit 812 publishes the transmission continuation request to the first server device 4 in the second topic every time the terminal device 9 uses the API 813. That is, the request source publishing unit 812 publishes the transmission continuation request to the first server device 4 in the second topic while the operation information is provided from the request source device 8 to the terminal device 9 at a predetermined frequency by the terminal device 9 using the API 813. The second topic may be created so that the specified elevator 1 can be identified by the request source control unit 81. The predetermined frequency corresponds to the frequency of use of the API 813. When the API 813 actively provides the operation information to the terminal device 9, the predetermined frequency may be determined corresponding to the frequency at which a change occurs in the storage device 7.
[0064] As described above, the API 813 is an example of a function for providing operation information of the specified elevator 1. When the terminal device 9 uses the API 813, the request source sending unit 811 can send a transmission start request to the first server device 4 by specifying the elevator 1 from which operation information is to be acquired. The request source publishing unit 812 can also send a transmission continuation request to the first server device 4 by specifying the elevator 1 from which operation information is to be acquired. Based on this transmission, the operation information of the specified elevator 1 is stored in the storage device 7. Therefore, while the terminal device 9 is using the API 813, the request source device 8 can sequentially acquire operation information of the specified elevator 1 from the storage device 7 and transmit the acquired operation information to the terminal device 9.
[0065] [Sequence] Next, the data flow between each device will be described with reference to Fig. 2 to Fig. 4. Fig. 2 is a sequence showing an example of the data flow based on the first use of API 813. Fig. 3 is a sequence showing an example of the data flow based on the second or subsequent use of API 813 after switching to the transmission mode. Fig. 4 is a sequence showing an example of the data flow when API 813 has not been used for a predetermined period of time.
[0066] Fig. 3 shows an example of a sequence after the sequence of Fig. 2, and Fig. 4 shows an example of a sequence after the sequence of Fig. 3. In addition, in Fig. 2 to Fig. 4, it is assumed that the operation information is transmitted from the elevator control device 2 to the communication device 3 via the first control line 101 every time a change occurs in the operation status of the elevator 1.
[0067] 2, the destination device 6 subscribes to the first topic for the first server device 4 (S1) before the terminal device 9 uses the API 813. This allows the first server device 4 to transmit the operation information to the destination device 6 at the timing when the communication device 3 receives a transmission start request from the second server device 5 and publishes the operation information to the first server device 4.
[0068] The terminal device 9 accepts an input operation for acquiring operation information of the elevator 1 whose operation status the user wishes to know. Upon accepting this input operation, the terminal device 9 uses the API 813 of the request sending device 8 (S2). At this time, the terminal device 9 also transmits to the request sending device 8 designation information of the elevator 1 designated by the user.
[0069] In the request source device 8, the request source transmitting unit 811 transmits a transmission start request including the designation information to the first server device 4 (S3). In the first server device 4, the server transmitting unit 413 transmits the transmission start request received from the request source device 8 to the second server device 5 (S4). The second server device 5 transmits the transmission start request received from the first server device 4 to the communication device 3 (S5).
[0070] In the communication device 3, the transmitting / receiving unit 321 receives a transmission start request from the second server device 5. Upon receiving this request, the publishing unit 312 switches the operation mode from the non-transmission mode to the transmission mode (S6). Then, the publishing unit 312 publishes the operation information received from the elevator control device 2 to the first server device 4 on the first topic (S8). Every time the publishing unit 312 receives operation information from the elevator control device 2, it publishes the operation information to the first server device 4 on the first topic.
[0071] Furthermore, in the communication device 3, when the transmitting / receiving unit 321 receives the transmission start request, the subscribing unit 313 subscribes to the second topic created based on the identification information of the elevator 1 to which the communication device 3 is connected, for the first server device 4 (S7). The process of S7 may be performed before or simultaneously with the process of S6, or may be performed at the start of or after the start of the process of S8, as long as it is performed after the communication device 3 receives the transmission start request in S5.
[0072] In S1, the destination device 6 subscribes to the first topic for the first server device 4. Therefore, in the first server device 4, the second transmitting unit 412 transmits the operation information of the specified elevator 1 published from the communication device 3 to the destination device 6 (S9). Every time the second transmitting unit 412 receives operation information from the communication device 3, it transmits the operation information to the destination device 6. Then, every time the destination device 6 receives operation information from the first server device 4, it stores the operation information in the storage device 7 (S10).
[0073] 3, the terminal device 9 uses the API 813 following the initial use of the API 813 (S11). In the request source device 8, the request source publishing unit 812 publishes a transmission continuation request to the first server device 4 using a second topic created based on the identification information of the elevator 1 (S12). This allows the first server device 4 to transmit the transmission continuation request published by the request source device 8 to the communication devices 3 that have subscribed to the same second topic as the second topic.
[0074] 2, the second topic created based on the identification information of the elevator 1 is subscribed to from the communication device 3 to the first server device 4. Therefore, in the first server device 4, the first transmission unit 411 transmits the transmission continuation request published by the request sending device 8 to the communication device 3 that has subscribed to the second topic created based on the identification information of the specified elevator 1 (S13).
[0075] Furthermore, in the request sending device 8, the request sending control unit 81 sequentially acquires operation information of the specified elevator 1 from the storage device 7 in response to the use of the API 813 in S11 (S14), and transmits it to the terminal device 9 (S15). The storage device 7 stores operation information that is generated every time a change occurs in the operation status of the elevator 1 after S10 in Fig. 2. Therefore, the terminal device 9 can notify the user of the operation status of the elevator 1 in real time by sequentially receiving the operation information from the request sending device 8.
[0076] In the communication device 3, after the transmitting / receiving unit 321 receives the transmission start request in S5 of Fig. 2, the first control unit 31 starts clocking. Then, the publishing unit 312 judges whether or not a transmission continuation request is received before a predetermined period of time has elapsed after receiving the transmission start request. If the publishing unit 312 judges that the transmission continuation request transmitted in S13 has been received before the predetermined period of time has elapsed, the publishing unit 312 continues the transmission mode. Therefore, every time the publishing unit 312 receives operation information from the elevator control device 2, it continues publishing to the first server device 4 in the first topic (S16). The clocking by the first control unit 31 is reset when the publishing unit 312 receives a transmission continuation request or when a predetermined period of time has elapsed.
[0077] In the first server device 4, the second transmitting unit 412 transmits the operation information of the specified elevator 1 to the destination device 6 every time the operation information is received from the communication device 3 (S17). Then, the destination device 6 stores the operation information in the storage device 7 every time the operation information is received from the first server device 4 (S18).
[0078] On the other hand, when the publishing unit 312 determines that a predetermined period of time has elapsed since receiving the transmission start request in S5 of Fig. 2, it switches the operation mode from the transmission mode to the non-transmission mode. During the non-transmission mode, the communication device 3 does not publish the operation information to the first server device 4 even if it receives the operation information from the elevator control device 2 every time the operation status of the elevator 1 changes. In other words, the communication device 3 stops transmitting the operation information to the first server device 4 by switching to the non-transmission mode.
[0079] When the terminal device 9 uses the API 813 following the previous use of the API 813 (S21), the request sending device 8 publishes a transmission continuation request to the first server device 4 in a second topic created based on the identification information of the elevator 1 (S22). The first server device 4 transmits the transmission continuation request published by the request sending device 8 to the communication devices 3 that have subscribed to the same second topic as the second topic (S23).
[0080] Furthermore, in the request sending device 8, the request sending control unit 81 sequentially acquires operation information of the specified elevator 1 from the storage device 7 in response to the use of the API 813 in S21 (S24), and transmits it to the terminal device 9 (S25). The storage device 7 continues to store operation information that is generated every time a change occurs in the operation status of the elevator 1 after S10 in FIG. 2. Therefore, the request sending device 8 can continue to transmit operation information indicating the latest operation status of the elevator 1 to the terminal device 9. Therefore, the terminal device 9 can notify the user of the operation status of the elevator 1 in real time.
[0081] In the communication device 3, after receiving the transmission continuation request in S13, the first control unit 31 starts counting time again. Then, the publishing unit 312 judges whether or not the next transmission continuation request will be received within a predetermined period after receiving this transmission continuation request. That is, the publishing unit 312 judges whether or not the next transmission continuation request will be received before a predetermined period has elapsed since the last transmission continuation request was received. If the publishing unit 312 judges that the transmission continuation request transmitted in S23 has been received before the predetermined period has elapsed, the publishing unit 312 continues the transmission mode. Therefore, the publishing unit 312 continues publishing to the first server device 4 in the first topic every time it receives operation information from the elevator control device 2 (S26).
[0082] In the first server device 4, the second transmitting unit 412 transmits the operation information of the specified elevator 1 to the destination device 6 every time the operation information is received from the communication device 3 (S27). Then, the destination device 6 stores the operation information in the storage device 7 every time the operation information is received from the first server device 4 (S28).
[0083] Similarly, when the API 813 is used by the terminal device 9 thereafter (S31), the request source publishing unit 812 of the request source device 8 publishes a transmission continuation request in the second topic (S32). After that, the first transmitting unit 411 of the first server device 4 transmits the transmission continuation request to the communication device 3 that has subscribed to the same second topic as the second topic (S33). In addition, the request source device 8 continues to obtain operation information from the storage device 7 (S34) and transmits it to the terminal device 9 (S35).
[0084] After receiving the transmission continuation request in S23, if the publishing unit 312 determines that the transmission continuation request transmitted in S33 has been received before the predetermined period has elapsed, the publishing unit 312 continues the transmission mode. Therefore, every time the publishing unit 312 receives operation information from the elevator control device 2, the publishing unit 312 continues publishing to the first server device 4 in the first topic (S36). Then, the second transmitting unit 412 of the first server device 4 transmits the operation information published from the communication device 3 to the transmission destination device 6 (S37), and the transmission destination device 6 continues to store the operation information in the storage device 7 (S38). The same applies to S41 to S48 shown in FIG. 4.
[0085] In this way, the publishing unit 312 continues to publish the operation information to the first server device 4 while the next continuation transmission request is received within a predetermined period of time after receiving the previous continuation transmission request (i.e., while the next continuation transmission request is continuously received). Therefore, the request source device 8 can transmit the operation information indicating the latest operation status of the elevator 1 to the terminal device 9 while the terminal device 9 is continuously using the API 813.
[0086] On the other hand, if the publishing unit 312 determines that a predetermined period has passed since the last time it received a continuation transmission request without receiving another continuation transmission request, it switches the operation mode from the transmission mode to the non-transmission mode. As shown in Fig. 4, if the publishing unit 312 determines that it has not received a next continuation transmission request before the predetermined period has passed after receiving a continuation transmission request in S43, it switches the operation mode from the transmission mode to the non-transmission mode (S51).
[0087] As described above, the elevator control device 2 transmits operation information to the communication device 3 every time a change occurs in the operation status of the elevator 1 controlled by the elevator control device 2. However, in the communication device 3, after switching to the non-transmission mode, the publishing unit 312 does not publish the operation information to the first server device 4 even if the operation information is received. In other words, the communication device 3 stops transmitting the operation information to the first server device 4 by switching to the non-transmission mode.
[0088] Therefore, after receiving a transmission start request, the communication device 3 can transmit operation information to the first server device 4 only while the communication device 3 is continuously receiving a transmission continuation request. In other words, the communication device 3 can transmit operation information to the first server device 4 only while the API 813 is continuously used. Therefore, while the API 813 is being used, the terminal device 9 can notify the user of the operation status of the elevator 1 in real time. On the other hand, in a situation where the API 813 is not being used, a communication session according to the first communication method is not established between the communication device 3 and the first server device 4, and therefore unnecessary communication load can be suppressed.
[0089] In the case where a common elevator 1 is specified in a plurality of terminal devices 9, when any of the terminal devices 9 uses the API 813, the request sending device 8 transmits a transmission start request for the operation information of the elevator 1 to the first server device 4. Based on this transmission, the communication device 3 can switch the operation mode to the transmission mode.
[0090] As described above, when the communication device 3 receives a next transmission continuation request before a predetermined period of time has elapsed since receiving the previous transmission continuation request, the communication device 3 continues the transmission mode. When any of the terminal devices 9 is using the API 813, the request source device 8 transmits a transmission continuation request to the first server device 4. Therefore, while any of the terminal devices 9 is using the API 813, the communication device 3 continues the transmission mode and continues publishing the operation information to the first server device 4.
[0091] On the other hand, when none of the terminal devices 9 use the API 813, the request source device 8 stops transmitting a continuation transmission request to the first server device 4. In other words, when it is determined that none of the users have viewed the operation information of the specified elevator 1, the request source device 8 stops transmitting a continuation transmission request to the first server device 4. Therefore, when the communication device 3 does not receive a continuation transmission request from the first server device 4 until a predetermined period has elapsed since the last time the communication device 3 received a continuation transmission request from the first server device 4 due to none of the terminal devices 9 using the API 813, the communication device 3 switches to the non-transmission mode. By switching to the non-transmission mode, the communication device 3 stops transmitting the specified operation information to the first server device 4.
[0092] In this way, when multiple users are attempting to view the operation status of the specified elevator 1, the communication device 3 continues the switched transmission mode. This allows at least one of the multiple terminal devices 9 to notify the users of the operation status of the elevator 1 in real time. Then, only when none of the users are viewing the operation status of the specified elevator 1, does the communication device 3 switch to the non-transmission mode and stop transmitting the operation information to the first server device 4.
[0093] 〔summary〕 A data transmission system according to a first aspect of the present invention is a data transmission system including a server device functioning as a broker and capable of communicating with each other using a publish / subscribe type communication method, and one or more communication devices, wherein the communication device includes a receiving unit that receives operation information relating to the operating status of an elevator controlled by an elevator control device that is communicatively connected to the communication device, a publishing unit that switches an operation mode between a sending mode in which the receiving unit publishes the received operation information to the server device using a predetermined first topic each time the receiving unit receives the operation information, and a non-transmission mode in which the publishing is not performed, and a publishing unit that, when switching to the sending mode, publishes the received operation information to the server device using a predetermined first topic, and a non-transmission mode in which the publishing is not performed, and and a subscribing unit that subscribes to a second topic created based on the identification information of the communication device, and the server device comprises a first transmitting unit that transmits a request for continuation of transmission of the operation information, published to the server device by a request source device using the second topic, to the communication device that has subscribed to the second topic for the server device, and the publishing unit continues the transmission mode if, during the transmission mode, the communication device receives the continuation of transmission request within a predetermined period of time since the communication device last received the continuation of transmission request, and switches to the non-transmission mode if the predetermined period of time has elapsed since the communication device last received the continuation of transmission request without receiving the continuation of transmission request.
[0094] A data transmission system according to a second aspect of the present invention is in accordance with the first aspect, wherein the elevator control device transmits the operation information to the communication device every time a change occurs in the operating status of the elevator controlled by the elevator control device.
[0095] A data transmission system according to aspect 3 of the present invention is, in aspect 1 or 2, characterized in that the requesting device has a function for providing the operation information of a specified elevator that is available to a terminal device of a user of the data transmission system, and while the operation information is provided from the requesting device to the terminal device at a predetermined frequency by the terminal device utilizing the function, the data transmission system publishes the transmission continuation request to the server device on the second topic created based on the identification information of the specified elevator.
[0096] A data transmission system according to aspect 4 of the present invention, in any of aspects 1 to 3, is characterized in that the server device is provided with a second transmission unit that, when it receives the operation information published from the publishing unit, transmits the received operation information to a destination device that has subscribed to the first topic for the server device, and the destination device executes a process for storing the received operation information in a storage device each time it receives the operation information from the server device, and the requesting device has a function for providing the operation information of a specified elevator that is available to a terminal device of a user of the data transmission system, and while the terminal device is using the function, it sequentially obtains the operation information of the specified elevator from the storage device and transmits the obtained operation information to the terminal device.
[0097] A data transmission system according to aspect 5 of the present invention, in any of aspects 1 to 4, has a function for providing the operation information of a specified elevator that is available to a terminal device of a user of the data transmission system, and when the function is used from the terminal device after the specified period of time has elapsed since the function was last used from the terminal device, executes processing for sending a request to start transmitting the operation information to the communication device, and when the communication device receives the request to start transmitting, the publishing unit switches the operation mode to the transmission mode.
[0098] A data transmission system according to a sixth aspect of the present invention is in any one of the third to fifth aspects, wherein the function is provided by an API (Application Programming Interface).
[0099] [Software implementation example] The functions of each device (excluding the memory device 7) (hereinafter referred to as the "device") of the data transmission system 100 can be realized by a program for causing a computer to function as the device, and a program for causing a computer to function as each control block of the device (in particular, each unit included in the first control unit 31, the second control unit 32, the server control unit 41 and the request source control unit 81).
[0100] In this case, the device includes a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., a memory) as hardware for executing the program. The control device and storage device execute the program to realize each function described in each of the above embodiments.
[0101] The program may be non-transitory and may be recorded in one or more computer-readable recording media. The recording media may or may not be included in the device. In the latter case, the program may be provided to the device via any wired or wireless transmission medium.
[0102] In addition, some or all of the functions of each of the control blocks can be realized by a logic circuit. For example, an integrated circuit in which a logic circuit that functions as each of the control blocks is formed is also included in the scope of the present invention. In addition, the functions of each of the control blocks can be realized by, for example, a quantum computer.
[0103] Furthermore, each process described in each of the above embodiments may be executed by AI (Artificial Intelligence). In this case, the AI may be executed by the control device or another device (for example, an edge computer or a cloud server).
[0104] [Additional Notes] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. [Explanation of symbols]
[0105] 1. Elevator 2 Elevator control device 3. Communications equipment 4. First server device (server device) 6 Destination device 7 Storage device 8 Requesting device 9 Terminal Equipment 100 Data Transmission System 311 Receiving unit 312 Publishing Department 313 Subscriber Department 411 First Transmission Unit 412 Second Transmission Unit 813 API (Function)
Claims
1. A data transmission system including a server device functioning as a broker and one or more communication devices capable of communicating with each other using a publish / subscribe type communication method, The communication device includes: A receiving unit that receives operation information related to an operation status of an elevator controlled by an elevator control device from the elevator control device that is communicably connected to the device itself; a publishing unit that switches an operation mode between a sending mode in which the received operation information is published to the server device using a predetermined first topic each time the receiving unit receives the operation information, and a non-transmission mode in which the publishing is not performed; a subscribing unit that, when switching to the transmission mode, subscribes to a second topic created based on the identification information of the elevator to the server device; The server device includes: a first transmission unit that transmits a request for continuing transmission of the operation information, the request being published to the server device by a request source device using the second topic, to the communication device that has subscribed to the second topic with respect to the server device; The publishing unit, during the transmission mode, if the communication device receives the transmission continuation request within a predetermined period of time since the communication device last received the transmission continuation request, the communication device continues the transmission mode; if the predetermined period has elapsed since the communication device last received the transmission continuation request without receiving the transmission continuation request, switching to the non-transmission mode; Data transmission system.
2. The elevator control device transmits the operation information to the communication device every time a change occurs in the operation status of the elevator controlled by the elevator control device.
2. The data transmission system according to claim 1.
3. The requesting device a function for providing the operation information of a designated elevator available to a terminal device of a user of the data transmission system; While the operation information is provided from the request source device to the terminal device at a predetermined frequency by the terminal device utilizing the function, the transmission continuation request is published to the server device using the second topic created based on identification information of a designated elevator.
2. The data transmission system according to claim 1.
4. The server device includes: a second transmission unit that, upon receiving the operation information published by the publishing unit, transmits the received operation information to a destination device that has subscribed to the first topic with respect to the server device; The destination device is Each time the operation information is received from the server device, a process is executed for storing the received operation information in a storage device; The requesting device a function for providing the operation information of a designated elevator available to a terminal device of a user of the data transmission system; While the terminal device is using the function, the operation information of the designated elevator is sequentially acquired from the storage device, and the acquired operation information is transmitted to the terminal device.
2. The data transmission system according to claim 1.
5. The requesting device a function for providing the operation information of a designated elevator available to a terminal device of a user of the data transmission system; executes a process for transmitting a request to start transmitting the operation information to the communication device when the function is used from the terminal device after the predetermined period has elapsed since the function was last used from the terminal device; When the communication device receives the transmission start request, the publishing unit switches the operation mode to the transmission mode.
2. The data transmission system according to claim 1.
6. The function is provided by an API (Application Programming Interface), 6. A data transmission system according to claim 3.
Citation Information
Patent Citations
elevator monitoring system
JP4369253B2
JPP4369253B
Elevator device, remote monitoring device for elevator, and remote monitoring system for elevator
WO2018220781A1