CN115210164A

CN115210164A - Device server, machine server, communication system, and data structure

Info

Publication number: CN115210164A
Application number: CN202180009807.XA
Authority: CN
Inventors: 釜坂等; 铃木悠太; 根岸启吾; 五明清司
Original assignee: Mitsubishi Electric Corp
Current assignee: Mitsubishi Electric Corp
Priority date: 2020-03-06
Filing date: 2021-03-03
Publication date: 2022-10-18
Also published as: JP2022095723A; JP7168103B2; JP7168111B2; CN115352975A; CN115348290A; WO2021177377A1; JP2022095724A; US20230050011A1; EP4116248A4; JPWO2021177377A1; US20230040980A1; US20230046391A1; JP7168112B2; EP4116248A1

Abstract

A communication system in which devices in a facility and machines operating in the facility easily cooperate, a device server and a machine server in the communication system, and a data structure for performing communication in the communication system are provided. In a communication system (1), messages are communicated in a common manner between respective device servers (7) and respective target servers (9) and are thereby used for control of a control object. The control target is a building device (3) as a device or a target (4) operating in a building (2) as a facility. The message contains the 1 st, 2 nd and 3 rd information. The 1 st information is information for specifying each target (4) as a machine. The 2 nd information is information indicating the transmission direction of the message. The 3 rd information is information indicating a process to be executed by the control target.

Description

Device server, machine server, communication system, and data structure

Technical Field

The invention relates to a device server, a machine server, a communication system, and a data structure.

Background

Patent document 1 discloses an example of a system for performing communication between an autonomous traveling vehicle and an elevator. In this system, an autonomous traveling vehicle transmits a hall call signal to a relay device controlled by a control panel of an elevator. The control panel drives the car of the elevator to a floor on which the autonomous traveling vehicle stands by, based on a signal of a hall call transmitted from the autonomous traveling vehicle.

Documents of the prior art

Patent literature

Patent document 1: japanese laid-open patent publication No. 2010-23959

Disclosure of Invention

Problems to be solved by the invention

However, in the system of patent document 1, the devices such as the elevator are controlled based on signals transmitted to the devices by a target such as an autonomous traveling vehicle. Here, in this system, in the case where a facility such as a building is provided with a plurality of devices, when a plurality of machines operate in the facility, it is necessary to determine the form of communication for each combination of device and machine. Therefore, cooperation of the apparatus and the machine is not easy.

The present invention relates to the solution of such problems. The present invention provides a communication system in which devices in a facility and machines operating in the facility easily cooperate, a device server and a machine server in the communication system, and a data structure for performing communication in the communication system.

Means for solving the problems

The device server of the present invention comprises: a 1 st communication unit that transmits and receives a message in a common data format to and from a plurality of machine servers that communicate with and control machines in a facility; and an equipment control unit that controls the equipment in the facility based on a message received by the 1 st communication unit, wherein the message includes 1 st information identifying the equipment, 2 nd information indicating a transmission direction of the message, and 3 rd information indicating a process related to the message.

The machine server of the present invention includes: a 2 nd communication unit that transmits and receives a message based on a common data format to and from an equipment server that controls equipment in a facility; and a device control unit that controls the devices in the facility based on the message received by the 2 nd communication unit, wherein the message includes 1 st information identifying the device, 2 nd information indicating a transmission direction of the message, and 3 rd information indicating a process related to the message.

The communication system of the present invention includes an equipment server and a plurality of machine servers, wherein the equipment server includes: a 1 st communication unit that transmits and receives a message based on a common data format to and from a plurality of machine servers; and a device control unit that controls devices in the facility based on the message received by the 1 st communication unit, each of the plurality of device servers including: a 2 nd communication unit which transmits and receives a message based on a common data format to and from the device server; and a device control unit that controls the devices in the facility based on the message received by the 2 nd communication unit, the message including 1 st information for specifying the device, 2 nd information indicating a transmission direction of the message, and 3 rd information indicating a process related to the message.

A data structure of the present invention is a data structure for transmitting a received message in a common data format between a plurality of device servers which communicate with and control devices in a facility and a device server which controls the devices in the facility, wherein the data structure includes 1 st information for specifying the devices in the facility, 2 nd information indicating a transmission direction of the message, and 3 rd information indicating a process to be executed by a control target of the message.

Effects of the invention

According to the device server or the machine server or the communication system of the present invention, the device in the facility and the machine operating in the facility easily cooperate. Furthermore, according to the data structure of the present invention, the devices in the facility and the machines operating in the facility easily cooperate.

Drawings

Fig. 1 is a configuration diagram of a communication system according to embodiment 1.

Fig. 2 is a diagram showing an example of a structure of a subject name of a message in the communication system according to embodiment 1.

Fig. 3 is a sequence diagram showing an example of the operation of the communication system according to embodiment 1.

Fig. 4 is a sequence diagram showing an example of the operation of the communication system according to embodiment 1.

Fig. 5 is a sequence diagram showing an example of the operation of the communication system according to embodiment 1.

Fig. 6 is a sequence diagram showing an example of the operation of the communication system according to embodiment 1.

Fig. 7 is a sequence diagram showing an example of the operation of the communication system according to embodiment 1.

Fig. 8 is a sequence diagram showing an example of the operation of the communication system according to embodiment 1.

Fig. 9 is a hardware configuration diagram of a main part of the communication system according to embodiment 1.

Fig. 10 is a configuration diagram of a communication system according to embodiment 2.

Fig. 11 is a flowchart showing an example of the operation of the communication system according to embodiment 2.

Fig. 12 is a flowchart showing an example of the operation of the communication system according to embodiment 2.

Fig. 13 is a flowchart showing an example of the operation of the communication system according to embodiment 2.

Fig. 14 is a flowchart showing an example of the operation of the communication system according to embodiment 2.

Fig. 15 is a configuration diagram of a communication system according to embodiment 3.

Detailed Description

A mode for carrying out the present invention will be described with reference to the accompanying drawings. In the drawings, the same or corresponding portions are denoted by the same reference numerals, and the redundant description is simplified or omitted as appropriate.

Embodiment mode 1

The communication system 1 is a system applied to communication related to cooperation between a plurality of devices in a facility and a plurality of targets as machines.

In this example, the facility is a building such as a building 2a or a building 2 b. Here, the building 2 is a table in which the building 2a and the building 2b are not distinguished from each other.

In the building 2a, a plurality of building devices 3a are provided as devices. In the building 2b, a plurality of building devices 3b are provided. Here, the building device 3 is a table in which the building device 3a and the building device 3b are not distinguished from each other.

The plurality of targets includes a plurality of targets 4p, for example, manufactured by manufacturer p, and a plurality of targets 4q, for example, manufactured by manufacturer q. Here, the target 4 is a table for not distinguishing between the target 4p and the target 4q, and the like.

The building equipment 3 and the target 4 operate in the facility. The building device 3 and the target 4 are, for example, a robot that moves autonomously through the building 2, a mobile device that moves autonomously or by operation of a user, or the like. Alternatively, the building device 3 and the object 4 are, for example, a wireless tag or a mobile terminal held by a user moving through the building 2. Alternatively, the building equipment 3 and the target 4 may be equipment such as an elevator, a passenger conveyor, an entrance and exit management device, a lighting device, or an air conditioner.

In this example, a part of the plurality of targets 4p moves in the building 2 a. Another portion of the plurality of targets 4p moves within the building 2 b. Further, a part of the plurality of targets 4q moves in the building 2 a. Another part of the plurality of targets 4q moves in the building 2 b. The target 4 is connected to the network 5 by wireless communication. The network 5 is, for example, the internet or the like. The target 4 is connected to the network 5 by a wireless communication standard such as LTE (Long Term Evolution). The target 4 may also be connected to the network 5 via a base station 6, for example.

The communication system 1 has 1 or more device servers 7. In this example, the device server 7 includes a device server 7a provided in the building 2a and a device server 7b provided in the building 2 b. Here, the device server 7 is a table for not distinguishing between the device server 7a and the device server 7b. The plurality of device servers 7 are connected to the network 5, respectively. The device server 7a controls each of the plurality of building devices 3a in the building 2 a. The device server 7a is connected to the network 5 via the firewall 8 of the building 2 a. The device server 7b controls each of the plurality of building devices 3b in the building 2 b. The device server 7b is connected to the network 5 via the firewall 8 of the building 2 b. The device server 7 is, for example, an edge server in the corresponding building 2. Alternatively, a part or all of the structure of the device server 7 may be provided on the cloud. In this case, the device server 7 is connected to the building device 3 via the network 5. Alternatively, the device server 7 is connected to the building device 3 via the base station 6. Alternatively, the device server 7 is connected to the building device 3 through the firewall 8.

The communication system 1 has a plurality of target servers 9 as machine servers. In this example, the plurality of target servers 9 include a target server 9p and a target server 9q managed by different managers from each other. Here, the destination server 9 is a table for not distinguishing between the destination server 9p and the destination server 9q. The administrator of the target server 9 is, for example, a manufacturer of the target 4, an administrator of the target 4, or the like. The administrator of the target server 9p is, for example, the manufacturer p. The administrator of the target server 9q is, for example, the manufacturer q. The same administrator may manage a plurality of target servers 9. The plurality of target servers 9 are connected to the network 5, respectively. The target server 9 is a server device that controls each of the plurality of targets 4 via the network 5. The target server 9p controls each of the plurality of targets 4 p. The target server 9q controls each of the plurality of targets 4q.

In the communication system 1, communication of messages is performed between the device server 7 and the target server 9. In this example, the messages are communicated via the MQTT (Message Queuing Telemetry Transport) protocol. In the MQTT protocol, messages are communicated between an MQTT proxy and an MQTT client. The MQTT agent receives a message that the MQTT client specifies a topic and issues (Publish). The MQTT proxy, in a case of publishing a message of a topic to which an MQTT client subscribes (Subscribe), transmits the message to the MQTT client.

The device server 7 and the target server 9 communicate with each other in a common data format described later. The target server 9 and the target 4 controlled by the target server 9 communicate by a data format different from the common data format. The device server 7 and the building devices 3 controlled by the device server 7 may communicate in a common data format or in a data format different from the common data format. The building devices 3 communicate directly with the device server 7. On the other hand, the target cannot directly communicate with the device server 7. Communication between the building devices 3 and the targets 4 takes place via the target server 9.

When the target 4 is a moving body such as a robot or a mobile device, various kinds of moving bodies corresponding to the applications of the moving body may be manufactured by a plurality of different manufacturers. Due to the difference in data format used for communication between various types of mobile objects, the mobile objects and the device server 7 may not easily cooperate with each other.

In the case where the target 4 is an elevator such as an elevator, a plurality of elevators may be manufactured by a plurality of different manufacturers in the same facility. Due to the difference in the data format used in the communication between the individual elevators manufactured by the individual manufacturers, cooperation of the elevators and the equipment server 7 is sometimes not easy.

The messages communicated in the communication system 1 comprise a header and a payload. The header is a portion that contains control information for the communication, such as the keep-alive timer and the subject name. The keep-alive timer represents the maximum time of interval of messages received from the MQTT client. In this example, the keep alive timer is set to, for example, 2 hours as an upper limit. When the keep-alive timer is not specified in a message at the time of connection from the MQTT client, or when the specified keep-alive timer exceeds the upper limit, the MQTT proxy sets the keep-alive timer to, for example, the time of the upper limit. The payload is a part containing information used in the cooperation of the building device 3 and the target 4. The message is used for controlling the control object such as the building device 3 or the target 4 as the control object. The message has a data structure of a common form regardless of the kind of the control object.

The device server 7 includes a 1 st communication unit 10, a device control unit 11, and a target management unit 12.

The 1 st communication unit 10 is a part that performs communication of messages. The 1 st communication unit 10 is connected to each of the plurality of target servers 9 via the network 5. The 1 st communication unit 10 is connected to each of the plurality of building devices 3 in the building 2 corresponding to the device server 7 via a LAN (Local Area Network), for example. In this example, the 1 st communication unit 10 is equipped with the MQTT proxy function. At this time, each target server 9 mounts the function of the MQTT client. When receiving a message issued by an arbitrary destination server 9, the 1 st communication unit 10 outputs information included in the message to the device control unit 11. The 1 st communication unit 10 transmits and receives a message based on a common data format to and from the plurality of target servers 9.

The device control unit 11 is a unit that controls the building device 3 based on the message when the 1 st communication unit 10 receives the message. The device control unit 11 may be provided in plural for each type of the building device 3, for example. The device control unit 11 may be equipped with the function of the MQTT client. The device control unit 11 issues a message to the target 4 according to the status of the building device 3. The 1 st communication unit 10 transmits the message to the target server 9 which has subscribed to the subject of the message issued by the device control unit 11.

The object management unit 12 is a part that manages the objects 4 that operate in the building 2 corresponding to the device server 7. The target management unit 12 may be equipped with the function of the MQTT client. The target management unit 12 may manage a topic to which the target server 9 can subscribe, for example.

The target server 9 includes a 2 nd communication unit 13 and a target control unit 14.

The 2 nd communication unit 13 is a part that performs communication of messages. The 2 nd communication unit 13 is connected to each of the plurality of device servers 7 via the network 5. The 2 nd communication unit 13 is connected to each of the plurality of targets 4 controlled by the target server 9 via the network 5. In this example, the 2 nd communication unit 13 is equipped with the function of an MQTT client. When receiving a message of a subscribed topic from any of the device servers 7, the 2 nd communication unit 13 outputs information included in the message to the target control unit 14. The 2 nd communication unit 13 communicates with the target 4 in a data format different from the common data format.

The target control unit 14 is a part that controls the target 4 based on the message when the 2 nd communication unit 13 receives the message. The target control unit 14 is an example of an apparatus control unit. The target control unit 14 may be provided in plural for each type of target 4. The target control unit 14 causes the 2 nd communication unit 13 to issue a message for the building device 3 according to the status of the target 4. The 2 nd communication unit 13 issues the message to the 1 st communication unit 10 of the device server 7 that controls the building device 3.

An example of message communication in the communication system 1 will be described taking as an example a case where the building device 3a is used by the target 4q in the building 2 a. The target 4q requests the target server 9q to issue a message for the building device 3a to be utilized. The 2 nd communication unit 13 of the target server 9q issues the requested message to the 1 st communication unit 10 of the device server 7 a.

The device control unit 11 of the device server 7a acquires the message received by the 1 st communication unit 10, for example, based on the subject name. The device control unit 11 controls the building device 3a based on the acquired message. When controlling the plurality of building devices 3a, the device control unit 11 may select the building device 3a to be controlled from the plurality of building devices 3a based on the 3 rd information of the acquired message. When controlling the plurality of building devices 3a, the device control unit 11 may select the building device 3a to be controlled from the plurality of building devices 3a based on the position information of the target 4 requesting the issuance of the acquired message in the building 2 a. The location information is determined by the 1 st information of the message. The building device 3a to be controlled operates under the control of the device control unit 11.

Further, the building device 3a operating under the control of the device server 7a may respond to the target 4q using the building device 3a. At this time, the building device 3a requests the device server 7a to issue a message for the target 4q. The 1 st communication unit 10 of the device server 7a issues a message of the theme to which the target server 9q has subscribed, in response to the request of the building device 3a.

The 2 nd communication part 13 of the target server 9q receives the message of the subscribed topic. The target control unit 14 of the target server 9q acquires the message received by the 2 nd communication unit 13. The target control unit 14 controls the target 4q based on the acquired message. The target 4q to be controlled operates under the control of the target control unit 14.

Next, a data structure of a message communicated in the communication system 1 will be described with reference to fig. 2.

As shown in fig. 2, the subject name has a hierarchical structure. In this example, the title is composed of 4 layers from the uppermost 1 st layer to the lowermost 4 th layer.

Layer 1 represents object classes. The object type is information indicating the type of the object 4, such as a robot, a mobile device, a person, or an elevator. Here, the object 4 whose object category is a person is, for example, an object that a person holds and moves.

Layer 2 represents the object ID. The object ID is information for specifying the object 4. The value of the object ID is, for example, "O001" or another number specific to the object 4. The target ID is an example of the 1 st information.

Layer 3 represents the message category. The message category includes information indicating a transmission direction of the message. The sender of the message is, for example, either from the destination side to the device side or from the device side to the destination side. In this example, the sender of the message is not individually determining the sender and recipient of the message. The transmission direction from the destination side to the device side is, for example, a transmission direction in which a message is transmitted from any one of the plurality of destination servers 9 to any one of the plurality of device servers 7. The transmission direction from the device side to the destination side is, for example, a transmission direction in which a message is transmitted from any one of the plurality of device servers 7 to any one of the plurality of destination servers 9. The message class may also contain information indicating the QoS level (QoS) of the message in the MQTT. A message with QoS level 0 is a non-guaranteed delivery message sent from the MQTT proxy up to 1 time. A message with QoS level 1 is a guaranteed delivery message sent a minimum of 1 time from the MQTT proxy. The value of the message class is a character string such as "O2B _ Q0" that combines information indicating the transmission direction and QoS class. Here, the message class "O2B _ Q0" represents a message of QoS class 0 from the target side toward the device side. The message category is an example of the 2 nd information.

Layer 4 indicates the functional class. The function type is information indicating a type of a function to be executed by the control target. The value of the function category is, for example, a character string such as "user management", "MovingObjectLocalization", "eleventinterface", or "ObjectInterface". In this example, the function type "user management" indicates a type of a management function for registering information of the object 4 operating in the building 2 in the object management unit 12 of the device server 7. Further, the function category "MovingObjectLocalization" indicates a category of functions such as synchronization of the position state of the object 4. The function type includes, for example, updating of location information stored in the memory of the device server 7. Here, the information of the position state of the target 4 includes, for example, information of the position and state of the target 4. Further, the function category "eleventinterface" indicates a category of a function requested for an elevator as the building equipment 3. The function category "ObjectInterface" indicates a category of a function requested for the target 4 operating in the building 2.

The information contained in the payload of the message is described in JSON format, for example.

A message requesting registration is sent from the target server 9. In this example, a message requesting registration as a target 4 of a mobile device moving in the building 2 is shown. For example, when the target server 9 first communicates with the device server 7 of the building 2, a message requesting registration is transmitted from the target server 9 to the device server 7.

The data in JSON form contained in the payload of this message contains "api" or the like as a key.

The value of the key "API" represents the name of the API to be utilized. The 3 rd information is information indicating a process related to the message. The 3 rd information contains the value of the key "api". The value of the keyword "api" is, for example, a character string "Registration" indicating that Registration is requested. The value of the keyword "api" is, for example, a character string "registry result" indicating that the registration result is notified. The value of the keyword "api" is, for example, a character string "PositionSynchronization" indicating the notification location state. The value of the keyword "api" is, for example, a string "positionsynchronizationofromff" indicating that correction of the position state is requested. The value of the keyword "api" is for example the string "CallElevator" indicating that an elevator is called. The value of the keyword "api" is, for example, a character string "requestfrommerleviator" indicating the result of a call to notify an elevator. The value of the keyword "api" is, for example, a character string "usedstusoffelevator" indicating the usage status of the elevator. The value of the keyword "api" is, for example, a character string "RequestMovement" representing a request from the device server 7 for the target 4. The value of the keyword "api" is, for example, a character string "RequestMovementResult" indicating a result of notifying a response to a request from the device server 7.

Next, an example of the operation of the communication system 1 will be described with reference to fig. 3 to 8.

Fig. 3 to 8 are sequence diagrams showing an example of the operation of the communication system according to embodiment 1.

Fig. 3 shows a timing chart in the initial registration and the subsequent steady operation. In this example, an example of an operation of registering the target 4 in the target management unit 12 of the facility server 7 is shown.

In order to register a target 4 operating in a building 2, the target server 9 is connected to the device server 7 corresponding to the building 2. For example, the connection with the device server 7 is made in accordance with the operation of the target server 9 by the administrator of the target 4. Alternatively, for example, the connection with the device server 7 may be made via the destination server 9 in accordance with an operation of the destination 4 by the administrator of the destination 4.

The 2 nd communication unit 13 of the target server 9 transmits a CONNECT message of MQTT to the 1 st communication unit 10 of the device server 7. The 1 st communication unit 10 of the facility server 7 sends back a CONNACK message of MQTT to the 2 nd communication unit 13 of the target server 9. The target server 9 thus confirms that an MQTT-based connection has been established with the device server 7. Here, authentication based on a user name and a password may be performed in communication between the target server 9 and the device server 7.

The 2 nd communication unit 13 of the target server 9 transmits a SUBSCRIBE message of MQTT to the 1 st communication unit 10 of the device server 7 at QoS level 1 to SUBSCRIBE to a topic for registration of the target 4. The 1 st communication unit 10 of the device server 7 returns a back message of MQTT to the 2 nd communication unit 13 of the target server 9. Thus, the target server 9 confirms that the subscription for the topic has been granted.

The 2 nd communication section 13 of the target server 9 transmits a PUBLISH message containing MQTT of information of the target 4 to be registered in the payload to the 1 st communication section 10 of the device server 7 at QoS level 1. In this message, "Registration" is specified as an API. This message is issued, for example, as the following message: the message is configured to include layer 1: NULL, layer 2 (information 1): NULL, layer 3 (information 2): O2B and layer 4: userManagement, including API (information No. 3) in the payload: registration. The 1 st communication unit 10 of the device server 7 returns a heartbeat message of MQTT to the 2 nd communication unit 13 of the target server 9. Thereby, the destination server 9 confirms that the issuance of the message has been accepted.

The object management unit 12 of the device server 7 performs registration processing of the object 4 such as giving of an object ID and generation of a subject header, based on the message received from the object server 9 by the 1 st communication unit 10. The target management unit 12 notifies the 1 st communication unit 10 of the registration result. In this example, the target managing unit 12 issues a PUBLISH message of MQTT containing the generated information of the theme header in the payload as a message of QoS class 1 to the 1 st communication unit 10. In this message, "registration result" is designated as the API. The message is, for example, a message configured as follows: the topic name includes layer 1: NULL, layer 2 (information 1): NULL, layer 3 (information 2): O2B and layer 4: userManagement, including API (information No. 3) in the payload: registrationResult.

The 2 nd communication part 13 of the target server 9 has subscribed to the topic, and therefore, receives the registration result as a PUBLISH message of MQTT from the 1 st communication part 10 of the device server 7. The 2 nd communication unit 13 of the target server 9 sends back a heartbeat message of MQTT to the 1 st communication unit 10 of the device server 7. Thereby, the device server 7 confirms that the registration result has been notified to the target server 9.

The communication part 213 of the target server 9 transmits a SUBSCRIBE message of MQTT to the communication part 110 of the device server 7 to SUBSCRIBE to the topic containing the topic header notified in the registration result. The 2 nd communication part 13 transmits a SUBSCRIBE message related to the topic to the 1 st communication part 10 to SUBSCRIBE to a message having a QoS level of 0. Further, the 2 nd communication part 13 transmits a SUBSCRIBE message related to the topic to the 1 st communication part 10 to SUBSCRIBE a message having a QoS level of 1. That is, the 2 nd communication unit 13 applies for subscribing to a message for the target side indicating an arbitrary function type in the designated version. The 1 st communication unit 10 of the device server 7 returns a back message of MQTT to the 2 nd communication unit 13 of the target server 9. Thereby, the target server 9 confirms that the subscription of the subject of the application has been permitted.

After registration as described above, the communication between the target server 9 and the device server 7 shifts to a stable operation. Messages from the target server 9 towards the device server 7 are communicated as PUBLISH messages from MQTT clients as issuers towards MQTT proxies. Messages from the device server 7 towards the target server 9 are communicated as PUBLISH messages from the MQTT proxy towards the MQTT client as the topic subscriber. The destination server 9 determines the destination 4 to which the message is to be directed from the subject header of the message.

When the communication between the destination server 9 and the device server 7 is disconnected, the destination server 9 transmits the CONNECT message to the device server 7 again, and the communication is restarted. At this time, the destination server 9 designates the same temporary ID for the same destination 4 and reconnects. Thus, the device server 7 sets the same target ID as that before the disconnection of communication to the same target 4.

Here, the difference between the position state of the object 4 recognized by the object 4 itself and the position information of the object 4 recognized by the device server 7 may become an obstacle to the cooperation of the object 4 and the building device 3. Therefore, in the steady operation, the positional state of the target 4 is synchronized between the target side and the moving body side. For example, the synchronization of the position states is performed by a periodic notification of the position state from the destination side to the device side, a request for correction of the position state from the device side to the destination side, and the like. In addition, for example, as shown in the composite segment PAR, a plurality of communications in a steady operation including notification of a position state, a request for correction of a position state, and the like are performed by parallel processing.

In the steady action, a message is sent from the target server 9 to the device server 7 so that the position status of the target 4 can be notified. The message is sent periodically, for example, at a predetermined period. For example, the target control unit 14 acquires information on the position state of the target 4 from the target 4.

The message notifying of the position status contains information of the position status of the target 4 in the payload as data in the form of JSON, for example. The position information of the target 4 may include information on the orientation of the target 4, for example. The data included in the payload includes, for example, an API name specifying a function on the device side related to synchronization of the location status, a target ID specifying the target 4 to be synchronized, information specifying a data expression of the location of the target 4, and the like. An API name is, for example, "PositionSynchronization". The message for notifying the location status is configured to include, for example, layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): O2B and layer 4: movingObjectLocalization, including API in the payload (information No. 3): positionsyncronization. The data representation of the position of the target 4 is specified by a combination of a coordinate system, a unit system such as a length and an angle, a data type such as an integer type, a real type, or a character string type, and the like. The coordinate system may be, for example, an absolute coordinate system in which the absolute position of the target 4 is represented by a set of latitude, longitude, and altitude, and the orientation of the target 4 is represented by azimuth. Alternatively, the coordinate system may be a building coordinate system in which, for example, a building 2-specific position of the object 4 in the building is represented by a group of rectangular coordinates (x, y) and a floor, and the direction of the object 4 is represented by an angle in the rectangular coordinates specific to the building 2. In this case, the origin in the building coordinate system may be designated together. The position state notified from the target 4 is managed by the target management unit 12, for example.

The information of the position state of the target 4 may also include information identifying an identifier of a base point specifying the correction position of the target 4 in the correction request when the correction of the position state of the target 4 is requested by the device server 7. At this time, the destination server 9 transmits the identifier of the last received correction request to the device server 7 in a message, thereby preventing the base point from being shifted from the device server 7.

The information on the position state of the target 4 may include information indicating the remaining charge amount of a battery that drives the target 4, for example. The information on the position state of the target 4 may include information on the operation state of the target 4, for example. The operation state of the target 4 includes, for example, a moving state or a standby state. The state information of the target 4 may include information on the operation content of the target 4, for example. The information of the operation content includes, for example, a state of operation or no operation.

Further, in the steady operation, a message is transmitted from the device server 7 to the target server 9 so that the correction of the position state of the target 4 can be requested. The equipment server 7 acquires information on the position state of the target 4 by an observation device such as a camera installed in the building 2. For example, when the difference between the position information of the target 4 recognized by the device server 7 and the position state notified from the target 4 itself is larger than a preset range, a request for correcting the position state is made.

The message of the correction request of the position status contains information such as a base point in the payload as data in the form of JSON, for example. The information of the base point may include information for correcting the orientation of the target 4, for example. The data included in the payload includes, for example, an API name for specifying a function on the destination side related to synchronization of the position status, a destination ID for specifying the destination 4 to be synchronized, information for specifying data expression of the base point, and the like. An API name is, for example, "PositionSynchronicationFrompF". The message of the location state correction request is configured to include, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): O2B and layer 4: movingObjectLocalization, including API in the payload (information No. 3): positionsyncronizationfrompf. For example, the data representation of the base point is specified in the same manner as the data representation of the position of the target 4. The message of the correction request of the position status may also contain information identifying the identifier of the base point.

In response to the message of the correction request received from the facility server 7, the target control unit 14 of the target server 9 corrects the position state of the target 4 specified in the message.

Here, the message transmitted from the device server 7 to the destination server 9 in connection with the synchronization of the position status may also contain information indicating whether the position status needs to be corrected. The message may not contain information of the base point in case that the position state does not need to be corrected. The message may be periodically transmitted at a predetermined cycle.

Fig. 4 shows a time chart in the case where the target 4 moves using an elevator as the building device 3.

In this example, the elevator has a plurality of cars and a group management device. Each car is the following device: the user, the destination 4, and the like are transported by traveling in the vertical direction between a plurality of floors in the building 2 in response to the call. The group management device manages calls assigned to each car.

When the destination 4 uses an elevator, the communication system 1 performs the call processing of the elevator shown in fig. 6 when the destination 4 arrives at the call position. The call location is e.g. the position of a landing of the elevator. In the call processing, communication of messages is performed between the destination server 9 and the device server 7. In the call processing, the elevator registers a hall call in which the floor where the destination 4 is located is set as a departure floor. A group management device of an elevator assigns a registered landing call to any one of a plurality of cars. In the call processing, the destination 4 is notified of which car of the plurality of cars the responding car to which the hall call is assigned. Here, the target 4 using an elevator is an example of the 1 st machine moving within the facility. The destination server 9 that controls the destination 4 using the elevator is an example of the 1 st machine server. Also, the responding car responding to the hall call of the target 4 is an example of the 1 st car.

After the call processing is performed, the destination 4 moves to the notified elevator riding standby position of the responding car. The boarding waiting position is set in advance in accordance with the response car. The boarding waiting position is, for example, a position before a landing entrance corresponding to a hoistway in which the car travels. After the call processing is performed, the response car moves to the departure floor.

When the response car reaches the departure floor, the communication system 1 performs an elevator boarding process for the elevator shown in fig. 7. In the boarding process, communication of messages is performed between the target server 9 and the facility server 7. In the boarding process, the target 4 boards the responding car.

After the boarding process is performed, the responding car moves to the destination floor of the destination 4.

When the response car reaches the destination floor, the communication system 1 performs an elevator getting-off process of getting off from the elevator as shown in fig. 8. In the pull-down process, communication of messages is performed between the target server 9 and the device server 7. In the alighting process, the target 4 is alighted from the responding car.

Fig. 5 shows a sequence of call processing of an elevator.

The destination 4 using the elevator requests the destination server 9 to use the elevator. Here, the destination 4 may not determine the car to be used. In addition, when a plurality of elevators are installed in the building 2, the destination 4 may not be able to determine the elevator to be used.

The destination server 9 that accepts the request sends a message to the appliance server 7 indicating that an elevator is called. The message indicating the call includes, for example, an API name specifying the call function, a destination ID identifying the destination 4 using the elevator, and information specifying the destination floor of the destination 4. The API name is for example "calleleventor". The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): O2B and layer 4: elevtorinterface, including API (information No. 3) in the payload: callseviator.

The appliance control unit 11 of the appliance server 7 that received the message selects an elevator as a control target from the plurality of building appliances 3 according to the function type of the message. Alternatively, when the equipment control unit 11 dedicated to an elevator to be controlled is provided, the equipment control unit 11 may acquire the message as a message of a subscribed topic. In addition, when a plurality of elevators are installed in the building 2, the device control unit 11 may select an elevator to be controlled from the plurality of elevators according to the position of the target 4. At this time, the device control unit 11 may select an elevator to be controlled by comparing the call position corresponding to each elevator with the position of the target 4, for example.

The equipment control unit 11 requests the exclusive operation of the target 4 to the elevator to be controlled. At this time, the device control unit 11 transmits information of the message transmitted from the destination server 9 together.

The elevator receiving the request registers a hall call in which the floor where the destination 4 is located is the starting floor as a hall call in which the destination floor is designated. For example, the floor where the target 4 is located is acquired based on the synchronized position information of the target 4. The destination floor is specified based on the information received from the device control unit 11. The group management device assigns the registered hall call to any one of the plurality of cars. The responding car to which the hall call is assigned shifts to the exclusive operation. The elevator transmits a dedicated operation start notification to the device server 7. Here, the dedicated operation start notification includes information of the boarding waiting position of the responding car.

When receiving the dedicated operation start notification from the elevator, the device server 7 transmits a message notifying the call result to the destination server 9. The message for notifying the call result includes, for example, an API name for specifying a function for notifying the call result, information indicating whether or not the call is successful, and information of the boarding waiting position of the responding car. The message may not include information for specifying the number of the responding car itself. The API name is for example "calleleventresult". The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): B2O and layer 4: elevtorenterface, including API (information No. 3) in the payload: callleviatorresult.

The target control unit 14 transmits the notified information of the call result to the target 4. Then, the target 4 moves to the boarding waiting position based on the received information of the call result.

On the other hand, in a case where the dedicated operation start notification is not received until the timeout time elapses since the request of the dedicated operation, the facility server 7 transmits a message notifying the call result to the destination server 9. The timeout time is a preset time such as 20 minutes. This message is sent as a message specifying the same subject of the API as in the case where the dedicated operation start notification is received. At this time, the message contains information indicating that the call failed. The message may not include information of the boarding waiting position.

The target control unit 14 transmits the notified information of the call result to the target 4. The communication system 1 ends the sequence in the case where the destination 4 is moving by an elevator. Then, the destination 4 moves to an operation in the case where the call to the elevator fails, based on the information of the received call result.

Fig. 6 shows a sequence of the boarding process for the elevator.

When the departure floor of the destination 4 is reached, the door of the car is opened in response to the car. The elevator sends an open door notification to the appliance server 7.

In the case of receiving a door open notification from the elevator, the appliance server 7 transmits a message indicating a request from the elevator to the destination server 9. The message indicating the request from the elevator includes, for example, an API name for specifying a function on the destination 4 side in response to the request from the elevator, information indicating the type of the request, and the like. The request type is, for example, an elevator boarding request. The message may also contain information in response to the boarding position inside the car. The API name is, for example, "requestfromlevelor". The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): B2O and layer 4: elevtorinterface, including API (information No. 3) in the payload: requestFromElevator.

The destination control unit 14 transmits request information from the elevator received from the device server 7 to the destination 4. The destination 4 rides on the responding car in accordance with the boarding request from the elevator. When the elevator-taking position inside the response car is reached, the destination 4 transmits an elevator-taking completion notification to the destination server 9.

When receiving the boarding completion notification from the destination 4, the destination server 9 transmits a message indicating the use state of the elevator to the facility server 7. The message indicating the use status of the elevator includes, for example, an API name for specifying a function on the device side corresponding to the status of the target 4, a target ID for identifying the target 4 using the elevator, a status code for specifying the use status, and the like. The state code of the usage status is, for example, a numerical value such as "1" indicating completion of elevator boarding. The API name is "usedstusofelevator", for example. The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): O2B and layer 4: elevtorinterface, including API (information No. 3) in the payload: usedstusoffelevator.

When receiving the notification of completion of elevator boarding from the destination server 9, the device control unit 11 transmits an instruction to close the doors of the responding car to the elevator. The elevator closes the doors of the responding car in accordance with the received indication.

On the other hand, when the boarding completion notification is not received until the timeout period elapses after the door opening notification is received, the facility server 7 transmits a message indicating a request from the elevator to the destination server 9. The timeout time is a preset time such as 800 seconds, for example. The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): B2O and layer 4: elevator interface. The request type in the message is, for example, a boarding suspension request.

The destination control unit 14 transmits request information from the elevator received from the device server 7 to the destination 4. The destination 4 stops the elevator car from being taken in the response car in response to an elevator car stop request. In the boarding completion processing, the destination 4 is returned to the landing of the elevator so that the elevator can be returned to normal operation.

When the boarding completion process is completed, the destination 4 may transmit a boarding completion notification to the destination server 9. The destination server 9 may also transmit a message of completion of the elevator boarding suspension to the facility server 7 through the same API as the elevator boarding completion notification.

The device control unit 11 waits until the door opening maintenance time elapses from the door opening of the responding car. The door opening maintaining time is a predetermined time such as 300 seconds. After the elapse of the door opening maintaining time, the device control unit 11 sends an instruction to the elevator to close the doors of the responding car. Alternatively, when receiving the message of completion of the boarding suspension from the destination server 9, the device control unit 11 may transmit an instruction to close the doors of the response car to the elevator without waiting for the elapse of the door opening maintenance time. The elevator closes the doors of the responding car in accordance with the received indication. The communication system 1 ends the sequence when the destination 4 is moving by an elevator.

Fig. 7 shows a sequence of the descending process from the elevator.

In the elevator getting-off process, the communication system 1 operates in the same manner as the elevator boarding process until the doors of the responding car are closed at the destination floors of the destinations 4. That is, when the destination floor is reached, the door of the car is opened in response to the car. The elevator sends an open door notification to the appliance server 7. The facility server 7 sends a message indicating a landing request to the target server 9. The target server 9 takes the target 4 off the response car according to the received message. Upon completion of the descent of the target 4, the target server 9 transmits a message indicating completion of the descent to the device server 7. The appliance server 7 sends an indication to the elevator to close the door of the responding car. When the destination 4 on the destination floor times out during the elevator trip, the facility server 7 transmits a message indicating an elevator trip stop request to the destination server 9. After the door opening maintenance time has elapsed, the appliance server 7 transmits an instruction to close the door of the responding car to the elevator.

After the door of the responding car is closed, the elevator ends the exclusive operation. Then, the elevator transmits a dedicated operation end notification to the device server 7.

Further, in a case where a message of the getting-off completion notification is not received from the target server 9 until an instruction to close the door of the response car is transmitted, trapping of the target 4 may occur in the response car. At this time, the device server 7 transmits a message indicating a request from the device server 7 to the target server 9 for the target 4. The message indicating the request from the device server 7 includes, for example, an API name specifying a function on the destination side in response to the request, information indicating the type of the request, and the like. The request type is, for example, a stop request. The API name is, for example, "requestmove".

The target control unit 14 transmits the request information received from the device server 7 to the target 4. The target 4 stops inside the response car in response to a stop request from the device server 7. Then, the target 4 sends a stop completion notification to the target server 9.

Upon receiving the stop completion notification from the target 4, the target server 9 transmits a message indicating a response result to the request from the device server 7 to the device server 7. The message indicating the response result to the request includes, for example, an API name indicating a notification of the response result, information indicating the type of the request from the device server 7, and a status code of the response result. The status code of the response result is, for example, a numerical value such as "101" indicating that the response is successful. The API name is, for example, "RequestMovementResult". The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): O2B and layer 4: objectInterface, the payload includes API (information No. 3): requestMovementResult.

When the destination server 9 receives the notification of the response result, the device control unit 11 determines whether or not the car can travel in response. When the traveling of the response car is possible, the elevator carries the trapped target 4 and causes the response car to travel to the emergency floor. The emergency floor is a floor set in advance, for example, in which a disaster prevention center or the like is installed. At the emergency-handling floor, the elevator opens the door of the response car. The device server 7 transmits a message to the destination server 9, for example, thereby moving the destination 4 to the standby place.

Fig. 8 shows a sequence diagram in the case where the device server 7 requests movement to the target 4.

Upon detecting the occurrence of the movement request event, the device server 7 requests the target 4 to move according to the type of the movement request event. The move request event is an event that requires the request target 4 to move. The movement request event is an event in an emergency including a disaster such as an earthquake detected by an earthquake detector provided in the building 2 or a fire detected by a fire detector, for example. Alternatively, the movement request event may be an event detected by the target management unit 12 according to the position state of the target 4. The movement request event may be an event at the time of abnormality such as failure or malfunction of the target 4. The movement request event may be an event that affects the operation of the target 4, such as a decrease in the remaining charge level of the battery that drives the target 4. The movement request event may be an event related to the security of the building 2, such as entry of the target 4 into an area that is not permitted to enter.

Upon detecting the occurrence of a move request event, the device server 7 sends a message to the target server 9 indicating a request from the device server 7 for the target 4. This message specifies, for example, the API "RequestMovement". The request category in the message is for example a mobile request. The message may also contain information informing of the type of disaster that occurred. In addition, the message may also contain information of the location of the requested movement. The position where the movement is requested is, for example, the position of the standby place of the target 4 in an emergency or an abnormality. Alternatively, the position to which the movement is requested may be, for example, the position of the charging station. Alternatively, the position where the movement is requested may be a position of an area where the target 4 is permitted to enter, or the like.

The target control unit 14 transmits information of the request received from the device server 7 to the target 4. The target 4 determines whether to approve the move request from the device server 7. The target 4 transmits the determination result of whether to approve to the target server 9.

Upon receiving the determination result from the target 4, the target server 9 transmits a message indicating a response to the request from the device server 7 to the device server 7. This message specifies, for example, the API "RequestMovementResult". The message is configured such that, for example, the layer 1: mobility, layer 2 (information 1): 001. layer 3 (information 2): O2B and layer 4: objectInterface, an API (information No. 3) is included in the payload: requestMovementResult. The status code of the response result in the message is, for example, a numerical value of "1" indicating approval of the request or "2" indicating rejection, or the like.

The target 4 moves to the requested position in accordance with the movement request from the device server 7, in the case where the movement request from the device server 7 is granted. Then, the target 4 transmits a movement completion notification to the target server 9.

Upon receiving the movement completion notification from the target 4, the target server 9 transmits a message indicating a response result to the request from the device server 7 to the device server 7. The message is, for example, a message specifying the same subject of the same API as the message representing the correspondence for the request. The status code of the response result in the message is, for example, a numerical value such as "101" indicating success of the response or "102" indicating failure of the response.

As described above, the communication system 1 according to embodiment 1 includes the plurality of facility servers 7 and the plurality of destination servers 9. In the communication system 1, communication of messages is performed in a common form between each of a plurality of device servers 7 and each of a plurality of destination servers 9, 9. The message contains the 1 st, 2 nd and 3 rd information. The 1 st information is information for specifying a plurality of targets 4 as machines, respectively. Each target 4 operates in the facility. Each target 4 uses at least one of a plurality of devices of the facility. The 2 nd information is information indicating the transmission direction of the message. The 3 rd information is information indicating a process to be executed by a device or equipment to be controlled. The 3 rd information represents, for example, an API. Each of the plurality of device servers 7 includes a device control unit 11 and a 1 st communication unit 10. When the device server 7 receives the message, the device control unit 11 controls at least one of the plurality of devices as a control target based on the message. The 1 st communication unit 10 performs communication of messages in a common format with each of the plurality of target servers 9. The plurality of destination servers 9 each include a destination control unit 14 and a 2 nd communication unit 13. When the target server 9 receives the message, the target control unit 14 controls at least one of the targets 4 as a control target based on the message. The 2 nd communication unit 13 performs communication of messages in a common format with each of the plurality of device servers 7. Messages are communicated in a common format between each of the plurality of appliance servers 7 and each of the plurality of destination servers 9, whereby the messages are used for control of at least one of the plurality of appliances and the plurality of destinations 4.

In the communication system 1, a plurality of devices and a plurality of targets 4 cooperate by communication via the device server 7 and the target server 9. The device server 7 and the target server 9 communicate through a common form of message. In this way, the plurality of devices and the plurality of targets 4 become loosely coupled with respect to the communication related to the cooperation. The targets 4 to be coordinated are determined by the 1 st information, and therefore, it is clear which target 4 is the message concerned. In the 2 nd information, it is not necessary to individually determine the combination of the sender and the receiver of the message, and therefore, even if the devices to cooperate and the targets 4 are plural, the amount of communication is not easily increased. Since the 3 rd information specifies the devices and the like that cooperate according to the function type in the cooperation, the target 4 does not need to have information of each device installed in the facility. Therefore, the device and the target 4 can easily operate in cooperation with each other regardless of the combination of the type of the device and the type of the target 4. Thus, even when a plurality of different targets 4 such as manufacturers and management workers move in a facility, the targets 4 can freely move in the facility regardless of the protocol of each device.

The device control unit 11 selects which device among the plurality of devices the message-based control object is to be set to, based on the 3 rd information. Thus, the target 4 does not have information of each device to be used, and can use the function by specifying the function of the device. For example, when the dedicated device control unit 11 is provided for each device to be controlled, the device control unit 11 may select a message to be acquired based on the 3 rd information.

The device control unit 11 selects which device among the plurality of devices the message-based control object is to be made to correspond to the position information of the target 4 stored in association with the information of the target 4 specified by the 1 st information. Thus, the device control unit 11 can select a device to be used by the target 4 without specifying each device from the target 4. Therefore, the target 4 does not have information of each device to be utilized, and the function of the device can be utilized by specifying the function. The device control unit 11 may select a device to be controlled based on a combination of the position of the target 4 and the 3 rd information.

When the 3 rd information of the message indicates a hall call, the device control portion 11 specifies the floor where the target 4 is located, based on the position information of the target 4 stored in association with the information of the target 4 specified by the 1 st information. The device control unit 11 registers the hall call for the specified floor as an elevator of the building device 3. Further, in the case where the elevator has a plurality of cars, the 1 st communication part 10 transmits information specifying a car responding to a hall call of the destination 4 among the plurality of cars to the destination server 9 controlling the destination 4, including the information in a message. Thereby, the destination 4 using the elevator as equipment easily calls the car of the elevator. The destination 4 does not need to select an elevator to utilize. The destination 4 can use the elevator without information such as the number of elevators to be used. Furthermore, the target 4 does not need to select the car of the elevator to be utilized. In addition, the target 4 does not need to determine the cars of the usable elevators. Thus, the target 4 is easily moved in the facility with the elevator.

When the doors of the car of the elevator are opened at the specified floor, the 1 st communication unit 10 transmits a message including the 3 rd information indicating the boarding request for the car to the destination server 9 that controls the destination 4. Further, after transmitting a message including the 3 rd information indicating the elevator boarding request for the car of the elevator to the destination server 9 and receiving a message including the 3 rd information indicating the completion of the elevator boarding for the car of the elevator from the destination server 9, the device control section 11 causes the elevator to close the door of the car. Thus, the target 4 using the elevator as the equipment can easily get on the car regardless of the model of the elevator or the like. In addition, the device server 7 can easily get the target 4 on the car regardless of the model of the target 4 or the like.

When the door of the car of the elevator is opened at the specified floor, the 1 st communication unit 10 transmits a message including the 3 rd information indicating the getting-off request from the car to the destination server 9 that controls the destination 4. Further, after transmitting a message including the 3 rd information indicating the request for getting off the elevator from the car of the elevator to the destination server 9 and receiving a message including the 3 rd information indicating completion of getting off the elevator from the destination server 9, the device control section 11 causes the elevator to close the door of the car. Thus, the target 4 using the elevator as the equipment can be easily lifted from the car regardless of the model of the elevator or the like. The facility server 7 also easily takes the target 4 off the car regardless of the model of the target 4 or the like.

When detecting the occurrence of a movement request event that is an event requiring the movement of the target 4, the 1 st communication unit 10 transmits a message including the 3 rd information indicating the movement request of the target 4 corresponding to the type of the movement request event to the target server 9 that controls the target 4. Thus, the device server 7 can make the target 4 support the corresponding situation of the facility, the device, the target 4, and the like regardless of the model and the like.

The 3 rd information of the message transmitted from the target server 9 may be data indicating a request for starting the operation of the control target device. At this time, the device control unit 11 starts the operation of the device to be controlled based on the message. The 3 rd information of the message transmitted from the target server 9 may be data indicating a stop request for the operation of the control target device. At this time, the device control unit 11 stops the operation of the device to be controlled based on the message. This facilitates the cooperation between the target 4 and the device in the facility.

The control target of the message may be, for example, a passenger conveyor, an air conditioner, a ventilator, a lighting device, or the like. When the control target is the passenger conveyor, the apparatus control unit 11 starts or stops the operation of the passenger conveyor, for example. When the control target is an air conditioner, the equipment control unit 11 starts or stops the operation of the air conditioner, for example. When the control target is a ventilator, the device control unit 11 starts or stops, for example, air blowing or air discharging of the ventilator. When the control target is an illumination device, the device control unit 11 turns on or off the illumination device, for example.

The 3 rd information of the message transmitted from the target server 9 may be data indicating a request for changing the operating state of the control target device. At this time, the device control unit 11 changes the operation state of the device to be controlled based on the message. This facilitates the cooperation between the target 4 and the device in the facility.

The change of the operating state may be, for example, switching of an operating mode. When the control target is a passenger conveyor, the switching of the operation mode is, for example, switching between an ascending operation and a descending operation, switching between a high-speed operation and a low-speed operation, or the like. The change of the operating state may be, for example, a change of an operating parameter. When the control target is a passenger conveyor, the operation parameter is, for example, an operation speed or the like. When the control target is an air conditioner, the operation parameter is, for example, a set temperature or an air volume. When the control target is a lighting device, the change of the operation parameter is, for example, dimming or color adjustment.

The device control unit 11 may authenticate the target 4 specified by the 1 st information as the entry and exit management device of the building device 3. When the authentication of the target 4 is successful, for example, the electronic lock managed by the entry/exit management device is unlocked. This enables smooth movement of the target 4 even in facilities having areas whose entry and exit are managed. The message transmitted from the destination server 9 may include authentication information of the destination 4.

Further, the message transmitted from the target server 9 may contain information indicating that the target 4 has lost its own current position. At this time, the device server 7 may transmit a message requesting correction of the position information, a message requesting movement, or the like to the destination server 9 controlling the destination 4.

In addition, when the control target device rejects execution of the function based on the message transmitted from the target server 9, the device server 7 may return a message including information indicating the reason for rejection to the target server 9. For example, when the elevator rejects the call processing, the device server 7 may return the control operation in an earthquake or another destination 4 already riding on the car as a rejection reason to the destination server 9. Thus, the target 4 can determine the possibility of agreement in the case where the execution of the function is requested again. At this time, the target 4 may determine whether or not to make a request again, based on the reason for the return.

Further, the device server 7 may not be an edge server. A plurality of device servers 7 may be provided for one facility. The device server 7 may be, for example, a server computer. The device server 7 may be constituted by a plurality of server computers or the like. The device server 7 may be a virtual server configured by a cloud service or the like, for example. A part or all of the functions of the device server 7 such as the 1 st communication unit 10, the device control unit 11, and the object management unit 12 may be mounted on separate hardware. The device control unit 11 may be provided in the control target device.

The target server 9 may be, for example, one server computer. The target server 9 may be constituted by a plurality of server computers or the like. The target server 9 may be a virtual server configured by a cloud service or the like, for example. The target server 9 may set a plurality of targets 4 manufactured by different manufacturers as control targets. The administrator of the target server 9 may also be different from the administrator of the target 4. Part or all of the functions of the object server 9 such as the 2 nd communication unit 13 and the object control unit 14 may be mounted on separate hardware. The target server 9 may be a dedicated server device or dedicated server software for each control target object 4. The target control unit 14 may be provided in the control target 4. The destination server 9 may be set for each facility where the destination 4 moves. The target server 9 may have a function of MQTT proxy in relation to the control target 4. At this time, a part or all of the control target 4 mounts the function of the MQTT client. The device server 7 may be equipped with the function of an MQTT client that serves as an interface with the target server 9 serving as an MQTT proxy.

Further, the communication between the device server 7 and the target server 9 may be performed by a protocol suitable for many-to-many communication other than MQTT. The data communicated in the payload of the message may be in any common format, and may be in a format other than JSON, such as a YAML format (YAML: YAML Ain't a Markup Language) or a binary format.

Further, the facility may not be a single building. The facility may also be a complex facility with multiple buildings. Alternatively, the facility may be an outdoor facility, for example.

The 3 rd information may include, for example, a function type as the 4 th layer shown in fig. 2.

The device control unit 11 that requests elevator use such as exclusive operation of the destination 4 may register an elevator with a hall call of a floor that does not correspond to the position information of the destination 4. For example, the device control section 11 may cause the elevator to register a hall call for floor 1 when the current position information of the object 4 moving to floor 1 is floor 2.

Next, an example of the hardware configuration of the main part of the communication system 1 will be described with reference to fig. 9.

Fig. 9 is a hardware configuration diagram of a main part of the communication system according to embodiment 1. The main components of the communication system 1 are, for example, the device server 7 and the destination server 9.

The functions of the communication system 1 can be implemented by a processing circuit. The processing circuit has at least 1 processor 1b and at least 1 memory 1c. The processing circuit may also have at least 1 dedicated hardware 1a together with or instead of the processor 1b and the memory 1c.

In the case of a processing circuit having a processor 1b and a memory 1c, the functions of the communication system 1 are implemented by software, firmware or a combination of software and firmware. At least one of the software and the firmware is described as a program. The program is stored in the memory 1c. The processor 1b reads out and executes the program stored in the memory 1c, thereby realizing each function of the communication system 1.

The processor 1b is also called a CPU (Central Processing Unit), a Processing device, an arithmetic device, a microprocessor, a microcomputer, or a DSP. The memory 1c is constituted by a nonvolatile or volatile semiconductor memory such as a RAM, a ROM, a flash memory, an EPROM, or an EEPROM.

In case the processing circuit has dedicated hardware 1a, the processing circuit is for example realized by a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA or a combination thereof.

The respective functions of the communication system 1 can be realized by the processing circuit, respectively. Alternatively, the functions of the communication system 1 may be realized by a processing circuit in a unified manner. The functions of the communication system 1 may be partially implemented by dedicated hardware 1a and partially implemented by software or firmware. In this way, the processing circuit implements the respective functions of the communication system 1 by hardware 1a, software, firmware, or a combination thereof.

Embodiment mode 2

Embodiment 2 will be described in detail with respect to differences from the example disclosed in embodiment 1, in particular. Any feature of the example disclosed in embodiment 1 can be adopted as the feature not described in embodiment 2.

In embodiment 2, an example of cooperation between an elevator as a building device 3 and an object 4 moving in the building 2 will be described.

A hoistway 15 is provided in the building 2. The hoistway 15 is a space extending over a plurality of floors of the building 2. A landing 16 adjacent to the hoistway 15 is provided on each floor of the building 2. A landing door 17 is provided in the landing 16. The landing door 17 is a door that divides the hoistway 15 and the landing 16.

The elevator has a car 18. The car 18 travels in the vertical direction in the hoistway 15 in response to a call, and conveys users, the moving destination 4, and the like between a plurality of floors of the building 2. Car 18 has car doors 19. The car door 19 opens and closes the door 17 provided at a landing on the floor in a linked manner, so that a user, a moving destination 4, and the like can get on and off when the car 18 stops at any floor.

The elevator has a control panel 20. The control panel 20 is a device for controlling the operation of the elevator. The operation of the elevator controlled by the control panel 20 includes, for example, traveling of the car 18 and opening and closing of the car door 19. The elevator as the building equipment 3 communicates with the equipment server 7 through, for example, a control panel 20.

In this example, a management room 21 of the building 2 is provided. The management room 21 is, for example, one room of the building 2. Alternatively, the management room 21 may be installed in a building outside the building 2. The management room 21 is a place where management work of the building 2 and the like are performed. A management terminal 22 is provided in the management room 21. The management terminal 22 is a device that performs management work and the like of the building 2. The management terminal 22 is a general-purpose information terminal such as a personal computer. The management terminal 22 may be connected to an alarm such as a buzzer or a lamp. Alternatively, the management terminal 22 may be a mobile information terminal such as a smartphone. The management terminal 22 is used by a manager of the building 2.

The device server 7 has a notification unit 23. The notification unit 23 is a unit that notifies the manager of the building 2. The notification unit 23 notifies the administrator by, for example, sending an electronic mail or the like that can be viewed by the management terminal 22. When the management terminal 22 is connected to an alarm, for example, the notification unit 23 may notify the administrator by an alarm sound or an alarm display of the alarm.

Next, an example of the operation of the communication system 1 will be described with reference to fig. 11 to 14.

Fig. 11 to 14 are flowcharts showing an example of the operation of the communication system according to embodiment 2.

Fig. 11 and 12 show an example of the operation flow of the facility server 7 in the elevator boarding process for the elevator.

The car 18 to which the hall call of the destination 4 is assigned performs the exclusive operation for the destination 4. When the car 18 opens the car door 19 at the departure floor of the destination 4, the device server 7 receives a door open notification from, for example, a control panel 20 of the elevator. At this time, the device server 7 starts the operation from step S101 in fig. 11.

In step S101, the facility server 7 transmits a message indicating an elevator boarding request to the target server 9. The boarding request is information expressed as API (information No. 3) in the payload of the message, for example. The facility server 7 may transmit a message indicating a boarding request to the destination 4 by, for example, wireless communication or the like. Then, the operation of the device server 7 proceeds to step S102.

The destination server 9 transmits information of the boarding request received from the facility server 7 to the destination 4. The destination 4 gets on the car 18 in response to the received boarding request. When the elevator car reaches the elevator boarding position inside the car 18, the destination 4 transmits an elevator boarding completion notification to the destination server 9. Upon receiving the boarding completion notification from the target 4, the target server 9 transmits a message indicating the boarding completion notification to the facility server 7. The boarding completion notification is, for example, information expressed as API (information No. 3) in the payload of the message. In addition, the destination 4 may transmit an elevator boarding completion notification to the facility server 7.

In step S102, the facility server 7 determines whether or not the boarding completion notification is received from the destination server 9 or the destination 4. If the determination result is yes, the operation of the device server 7 proceeds to step S103. On the other hand, if the determination result is "no", the operation of the device server 7 proceeds to step S104.

In step S103, the device server 7 transmits an instruction to close the door 19 of the car to the elevator. Then, the operation of the facility server 7 in the boarding process is ended.

The elevator closes the doors 19 of the car in accordance with the instruction received from the equipment server 7.

In step S104, the device server 7 determines whether or not to normally connect with the target server 9. When the device server 7 communicates with the target 4, the device server 7 may determine whether or not to connect to the target 4 normally. If the determination result in step S104 is yes, the operation of the device server 7 proceeds to step S106. On the other hand, when the connection with the destination server 9 or the destination 4 is not normal, the destination 4 may not receive the boarding completion notification even when the boarding of the car 18 by the destination 4 is completed. Therefore, when the determination result in step S104 is "no", the operation of the device server 7 proceeds to step S105.

In step S105, the device server 7 determines whether the position information of the target 4 immediately before being normally connected to the target 4 is inside the car 18 or outside the car 18. If the determination result in step S105 is yes, the operation of the device server 7 proceeds to step S103. On the other hand, in a case where the position information of the target 4 immediately before being normally connected to the target 4 is not either the inside of the car 18 or the outside of the car 18, the target 4 may be located between the inside of the car 18 and the outside of the car 18. At this time, in the case where the door 19 of the car is closed in step S103, the target 4 may be caught by the door 19 of the car. Therefore, when the determination result in step S105 is "no", the operation of the device server 7 proceeds to step S106.

In step S106, the device server 7 determines whether or not a timeout occurs, that is, whether or not a predetermined time has elapsed since the door open notification was received. If the determination result is "no", the operation of the device server 7 proceeds to step S102. On the other hand, if the determination result is yes, the operation of the device server 7 proceeds to step S107 in fig. 12.

In step S107, the device server 7 determines that the car 18 has failed to be taken in the target 4. At this time, the facility server 7 transmits a message indicating a boarding completion request to the destination server 9. The boarding completion request is, for example, information expressed as API (information No. 3) in the payload of the message. The facility server 7 may transmit a message indicating a boarding completion request to the destination 4. When it is determined that the destination 4 fails to take the car 18, the device server 7 transmits a cancel instruction of the exclusive operation for the destination 4 to the elevator. Then, the operation of the device server 7 proceeds to step S108.

The destination server 9 transmits information of the boarding completion request received from the facility server 7 to the destination 4. The destination 4 stops the boarding of the car 18 in response to the received boarding stop request. In the boarding completion process, the destination 4 is returned to the landing 16 so that the elevator can be returned to the normal operation. When the boarding completion processing is completed, the destination 4 transmits a boarding completion notification to the destination server 9. When receiving the boarding completion notification from the target 4, the target server 9 transmits a message indicating the boarding completion notification to the facility server 7. The boarding completion notification is, for example, information expressed as API (information No. 3) in the payload of the message. The destination 4 may transmit a boarding completion notification to the facility server 7.

In addition, the device server 7 may transmit a message indicating a movement request to a preset position outside the car 18 to the destination server 9 when it is determined that the destination 4 has failed to take the car 18. The position outside the car 18 is, for example, a position in the landing 16. The move request is represented as information of API (3 rd information), for example, in the payload of the message. In the boarding completion process, the target 4 may be moved outside the car 18 in accordance with a movement request. Upon completion of the movement based on the movement request, the target 4 transmits a movement completion notification to the target server 9. Upon receiving the movement completion notification from the target 4, the target server 9 transmits a message indicating the movement completion notification to the device server 7. The movement completion notification is, for example, information expressed as API (3 rd information) in the payload of the message. In addition, the target 4 may also transmit a movement completion notification to the device server 7. The movement completion notification may be communicated together with the boarding completion notification.

In step S108, the facility server 7 determines whether or not the boarding completion notification is received from the destination server 9 or the destination 4. If the determination result in step S108 is "no", the operation of the device server 7 proceeds to step S109. On the other hand, if the time-out occurs in step S106 in fig. 11, the boarding of the destination 4 to the car 18 may be completed during the processing of the communication of the boarding completion request and the like. Therefore, if the determination result in step S108 is yes, the operation of the device server 7 proceeds to step S103 in fig. 11.

In step S109, the facility server 7 determines whether or not a boarding completion notification is received from the destination server 9 or the destination 4. If the determination result is yes, the operation of the device server 7 proceeds to step S103 in fig. 11. On the other hand, if the determination result is "no", the operation of the device server 7 proceeds to step S110.

In step S110, the device server 7 determines whether or not to normally connect with the target server 9. When the device server 7 communicates with the target 4, the device server 7 may determine whether or not to connect to the target 4 normally. If the determination result in step S110 is yes, the operation of the device server 7 proceeds to step S112. On the other hand, when the destination server 9 or the destination 4 is not normally connected, the boarding completion notification may not be received even when the boarding completion processing for the car 18 by the destination 4 is completed. Therefore, if the determination result in step S110 is "no", the operation of the device server 7 proceeds to step S111.

In step S111, the device server 7 determines whether the position information of the target 4 immediately before being normally connected to the target 4 is inside the car 18 or outside the car 18. If the determination result in step S111 is yes, the operation of the device server 7 proceeds to step S103 in fig. 11. On the other hand, in a case where the position information of the target 4 immediately before being normally connected to the target 4 is not either the inside of the car 18 or the outside of the car 18, the target 4 may be located between the inside of the car 18 and the outside of the car 18. At this time, in the case where the door 19 of the car is closed in step S103, the target 4 may be caught by the door 19 of the car. Therefore, when the determination result in step S111 is "no", the operation of the device server 7 proceeds to step S112.

In step S112, the facility server 7 determines whether or not a timeout occurs, that is, whether or not a predetermined time has elapsed since the transmission of the boarding completion request. If the determination result is "no", the operation of the device server 7 proceeds to step S108. On the other hand, if the determination result is yes, the operation of the device server 7 proceeds to step S113.

In step S113, the notification unit 23 of the facility server 7 notifies the manager of the failure of the car 18 to be taken by the target 4. Then, the operation of the facility server 7 in the boarding process is ended.

In addition, the control panel 20 may close the car door 19 when the car door 19 can be closed after the notification portion 23 of the facility server 7 notifies the car.

When the boarding completion notification is received in step S108, the facility server 7 may transmit the instruction of the exclusive operation for the destination 4 to the elevator again. Alternatively, in step S107, the facility server 7 may transmit a message of the boarding completion request without transmitting a cancel instruction for the exclusive operation of the destination 4 to the elevator. In this case, the facility server 7 transmits a cancel instruction of the exclusive operation for the target 4 to the elevator in, for example, step S113 or the like. Alternatively, for example, when the boarding completion notification is received in step S109 or the like, the device server 7 may transmit a release instruction for the exclusive operation of the destination 4 to the elevator. Alternatively, the facility server 7 may transmit a cancel instruction of the exclusive operation for the destination 4 to the elevator when receiving the movement completion notification based on the movement requested by the movement request accompanied by the boarding stop request.

If it is determined in step S104 or step S110 that the connection to the destination server 9 is not normal, the facility server 7 may determine that the destination 4 has failed to take the car 18.

Note that, the notification unit 23 may omit notification to the manager when the elevator can be returned to the normal operation.

Fig. 13 and 14 show an example of the operation flow of the facility server 7 in the descending process from the elevator.

When the car 18 on which the destination 4 boards opens the door 19 of the car at the destination floor of the destination 4, the device server 7 receives a door opening notification from, for example, a control panel 20 of the elevator. At this time, the device server 7 starts the operation from step S201 in fig. 13.

In step S201, the facility server 7 transmits a message indicating a landing request to the target server 9. The landing request for information is for example represented as API (information No. 3) in the payload of the message. In addition, the facility server 7 may transmit a message indicating a landing request to the target 4. Then, the operation of the device server 7 proceeds to step S202.

The target server 9 transmits information of the landing request received from the facility server 7 to the target 4. Destination 4 disembarks from car 18 in response to the received disembarkation request. When the landing of the target 4 is completed, the target 4 transmits a landing completion notification to the target server 9. Upon receiving the departure completion notification from the target 4, the target server 9 transmits a message indicating the departure completion notification to the apparatus server 7. The down completion notification is, for example, information expressed as API (information No. 3) in the payload of the message. In addition, the target 4 may also transmit a landing completion notification to the facility server 7.

In step S202, the device server 7 determines whether or not a going-off completion notification is received from the target server 9 or the target 4. If the determination result is yes, the operation of the device server 7 proceeds to step S203. On the other hand, if the determination result is "no", the operation of the device server 7 proceeds to step S204.

In step S203, the device server 7 transmits an instruction to close the door 19 of the car to the elevator. Then, the operation of the facility server 7 in the downward processing is ended.

In step S204, the device server 7 determines whether or not to normally connect with the target server 9. When the device server 7 communicates with the target 4, the device server 7 may determine whether or not to connect to the target 4 normally. If the determination result in step S204 is yes, the operation of the device server 7 proceeds to step S206. On the other hand, when the connection with the destination server 9 or the destination 4 is not normal, the departure completion notification may not be received even when the destination 4 completes the departure of the car 18. Therefore, if the determination result in step S204 is "no", the operation of the device server 7 proceeds to step S205.

In step S205, the device server 7 determines whether the position information of the target 4 immediately before the target 4 is normally connected is inside the car 18 or outside the car 18. If the determination result in step S205 is yes, the operation of the device server 7 proceeds to step S203. On the other hand, in a case where the position information of the target 4 immediately before being not normally connected to the target 4 is not either of the inside of the car 18 and the outside of the car 18, the target 4 may be located between the inside of the car 18 and the outside of the car 18. At this time, in the case where the door 19 of the car is closed in step S203, the target 4 may be caught by the door 19 of the car. Therefore, when the determination result in step S205 is "no", the operation of the device server 7 proceeds to step S206.

In step S206, the device server 7 determines whether or not a timeout occurs, that is, whether or not a predetermined time has elapsed since the door open notification was received. If the determination result is "no", the operation of the device server 7 proceeds to step S202. On the other hand, if the determination result is yes, the operation of the device server 7 proceeds to step S207 in fig. 14.

In step S207, the device server 7 determines that the destination 4 has failed to get off the car 18. At this time, the facility server 7 transmits a message indicating a landing termination request to the destination server 9. The landing suspension request is, for example, information expressed as API (information No. 3) in the payload of the message. The facility server 7 may transmit a message indicating a landing termination request to the target 4. Then, the operation of the device server 7 proceeds to step S208.

The destination server 9 transmits information of the landing termination request received from the facility server 7 to the destination 4. The destination 4 stops the descent from the car 18 in response to the received descent stop request. Upon completion of the suspension of the boarding process, the target 4 transmits a boarding suspension completion notification to the target server 9. Upon receiving the departure suspension completion notification from the target 4, the target server 9 transmits a message indicating the departure suspension completion notification to the facility server 7. The down termination completion notification is, for example, information expressed as API (information No. 3) in the payload of the message. In addition, the target 4 may transmit a descent termination completion notification to the facility server 7.

In step S208, the device server 7 determines whether a departure completion notification is received from the destination server 9 or the destination 4. If the determination result in step S208 is "no", the operation of the device server 7 proceeds to step S209. On the other hand, if the time-out occurs in step S206, the destination 4 may be completely removed from the car 18 during the processing of the communication of the removal stop request and the like. Therefore, if the determination result in step S208 is yes, the operation of the device server 7 proceeds to step S203 in fig. 13.

In step S209, the device server 7 determines whether or not a departure completion notification is received from the destination server 9 or the destination 4. If the determination result is yes, the operation of the device server 7 proceeds to step S203 in fig. 13. On the other hand, if the determination result is "no", the operation of the device server 7 proceeds to step S210.

In step S210, the device server 7 determines whether or not to connect normally with the target server 9. When the device server 7 communicates with the target 4, the device server 7 may determine whether or not to connect to the target 4 normally. If the determination result in step S210 is yes, the operation of the device server 7 proceeds to step S212. On the other hand, when the connection with the destination server 9 or the destination 4 is not normal, the departure completion notification may not be received even when the departure completion processing for the destination 4 to depart from the car 18 is completed. Therefore, when the determination result in step S210 is "no", the operation of the device server 7 proceeds to step S211.

In step S211, the device server 7 determines whether the position information of the target 4 immediately before the target 4 is normally connected is inside the car 18 or outside the car 18. If the determination result in step S211 is yes, the operation of the device server 7 proceeds to step S203 in fig. 13. On the other hand, in a case where the position information of the target 4 immediately before being not normally connected to the target 4 is not either of the inside of the car 18 and the outside of the car 18, the target 4 may be located between the inside of the car 18 and the outside of the car 18. At this time, in the case where the door 19 of the car is closed in step S203, the target 4 may be caught by the door 19 of the car. Therefore, when the determination result in step S211 is "no", the operation of the device server 7 proceeds to step S212.

In step S212, the facility server 7 determines whether or not a timeout, that is, whether or not a predetermined time has elapsed since the transmission of the landing termination request. If the determination result is "no", the operation of the device server 7 proceeds to step S208. On the other hand, if the determination result is yes, the operation of the device server 7 proceeds to step S213.

In step S213, the notification unit 23 of the device server 7 notifies the manager that the destination 4 has failed to get off the car 18. Then, the operation of the facility server 7 in the downward processing is ended.

When it is determined in step S204 or step S210 that the connection to the destination server 9 is not normal, the facility server 7 may determine that the destination 4 has failed to get off the car 18.

As described above, in the communication system 1 according to embodiment 2, the car 18 responds to the hall call of the destination 4 controlled by the destination server 9. The equipment control unit 11 of the equipment server 7 determines whether or not a message including the 3 rd information indicating that the boarding for the car 18 is completed is received from the destination server 9 until a predetermined time elapses from the transmission of the message including the 3 rd information indicating the boarding request to the destination server 9. If the message is not received, the equipment control unit 11 determines that the car 18 has failed to be taken by the target 4. At this time, the device control unit 11 transmits a message including the 3 rd information indicating the request for stopping the boarding of the car 18 to the destination server 9.

Further, the device control portion 11 determines whether or not the message including the 3 rd information indicating the completion of the alighting from the car 18 is received from the destination server 9 until a predetermined time elapses from the transmission of the message including the 3 rd information indicating the request to alight from the destination server 9. If the message is not received, the device control unit 11 determines that the target 4 has failed to get off the car 18. At this time, the device control unit 11 transmits a message including the 3 rd information indicating the getting-off stop request for getting off from the car 18 to the destination server 9.

With this configuration, when the target 4 cannot be mounted on the car 18, the mounting of the target 4 is stopped, and therefore the elevator can be quickly returned to the normal operation. In addition, when the destination 4 cannot be taken off from the car 18, the taking off of the destination 4 is stopped, and therefore, the elevator can be quickly returned to the normal operation. Therefore, the operation efficiency of the elevator is not easily lowered. Further, the abnormality on the target 4 side is determined in a state where the communication between the device server 7 and the target server 9 is established, and therefore, the abnormality of the robot can be determined more accurately. Further, for example, when the destination 4 itself determines that the door 19 of the car is open at the landing 16 on the starting floor, the destination 4 may start boarding with respect to the car 18 regardless of the boarding request. In this way, when the message including the boarding request is not transmitted, the facility control unit 11 may transmit the message including the boarding suspension request to the destination server 9 when it is determined that the boarding has failed. Similarly, when the message including the elevator leaving request is not transmitted, the device control unit 11 may transmit the message including the elevator leaving request to the destination server 9 when it is determined that the elevator leaving has failed.

When the car 18 is caused to respond to a hall call, the device control unit 11 causes the car 18 to perform an exclusive operation for the target 4. When it is determined that the target 4 fails to take the car 18, the device control unit 11 cancels the exclusive operation of the car 18.

With this configuration, the exclusive operation is canceled when the destination 4 fails to take the car 18, and therefore the elevator can be quickly returned to the normal operation. Therefore, the operation efficiency of the elevator is not easily lowered.

When it is determined that the target 4 has failed to take the car 18, the device control unit 11 transmits a message including the 3 rd information indicating a request for moving the target 4 to a preset position outside the car 18 to the target server 9.

According to this configuration, when the target 4 fails to ride on the car 18, the target 4 is retracted to a position outside the car 18, and therefore the elevator can be quickly returned to the normal operation. Therefore, the operation efficiency of the elevator is not easily lowered.

When the car 18 is caused to respond to a hall call, the device control unit 11 causes the car 18 to perform an exclusive operation for the target 4. When it is determined that the taking of the car 18 by the target 4 has failed, the device control unit 11 transmits a message including the 3 rd information indicating a request for moving the target 4 to a preset position outside the car 18 to the target server 9. Then, upon receiving a message including the 3 rd information indicating completion of movement based on the movement request from the destination server 9, the device control unit 11 releases the exclusive operation of the car 18.

According to this configuration, since the exclusive operation is canceled after the confirmation of the retreat of the target 4 to the position outside the car 18, it is not easy to perform the resetting of the exclusive operation or the like due to an error message or the like. Therefore, the operation efficiency of the elevator is not easily lowered.

The device server 7 also has a notification unit 23. When the equipment control unit 11 determines that the target 4 has failed to get off the car 18, the notification unit 23 notifies the failure of getting off the car.

With this configuration, when the destination 4 fails to get off the car 18, the notification is given to the manager. Since the manager can quickly recognize the abnormality or the like occurring on the destination 4 side, the elevator can be quickly returned to the normal operation. Therefore, the operation efficiency of the elevator is not easily lowered.

Embodiment 3

Embodiment 3 will be described in detail with respect to differences from the examples disclosed in embodiment 1 or embodiment 2, in particular. Any feature of the examples disclosed in embodiment 1 or embodiment 2 can be adopted as the feature not described in embodiment 3.

In embodiment 3, an example of cooperation between an elevator as a building device 3 and an object 4 moving in a building 2 will be described.

The elevator is provided with 1 or more landing cameras 24. Each landing camera 24 is provided at any landing 16. The landing camera 24 is a device that takes images. The images captured by the landing cameras 24 are still images, moving images, or the like. The landing camera 24 is an example of a camera provided in an elevator.

The car 18 of the elevator has a scale 25, a car camera 26 and a traffic detector 27. The scale 25 is a device for measuring the load of the car 18. The scale 25 is provided, for example, on a lower portion or an upper portion of the car 18. A car camera 26 is disposed inside the car 18. The car camera 26 is a device that captures images. The image captured by the car camera 26 is a still image, a moving image, or the like. The car camera 26 is an example of a camera provided in an elevator. The traffic detector 27 is provided at the doorway of the car 18. The traffic detector 27 is disposed, for example, near the door 19 of the car. The traffic detector 27 is a device that detects a user, a target 4, or the like passing through the doorway of the car 18. The traffic detector 27 has, for example, a photosensor. The traffic detector 27 may have 1 or more light projector and light receiver sets. The traffic detector 27 may be provided to the car door 19.

The facility control unit 11 of the facility server 7 includes an entrance/exit observation unit 28. The boarding/alighting observation unit 28 is a part for observing the boarding/alighting state of the machine such as the target 4 with respect to the car 18. The boarding/alighting observation unit 28 is an example of an boarding observation unit that observes a boarding situation for the car 18. The boarding/alighting observation unit 28 is an example of an alighting observation unit that observes the state of alighting from the car 18. The facility server 7 may have an elevator boarding observation unit and an elevator disembarkation observation unit, respectively.

The device server 7 determines whether or not the cage 18 is successfully raised or lowered by the target 4 based on the observation result of the raising/lowering observation unit 28. The facility server 7 may determine whether the destination 4 has successfully transferred to the car 18 based on the observation result of the boarding/alighting observation unit 28 and whether a message such as an boarding completion notification or an alighting completion notification has been received or not until a predetermined time has elapsed since the door 19 of the car was opened. When determining that boarding or alighting has failed, the facility server 7 transmits a message indicating a boarding completion request, or a movement request, transmits a release instruction for the dedicated operation, notifies the administrator, and the like, as in embodiment 2.

The boarding/alighting observation unit 28 acquires the position information of the target 4, for example, based on a message periodically received from the target server 9. The equipment control unit 11 determines whether the entry and the exit of the target 4 to and from the car 18 are successful, for example, as follows, based on the position information of the target 4 observed by the entry and exit observation unit 28. When the position of the target 4 moves from the landing 16 to the inside of the car 18, the equipment control unit 11 determines that the boarding of the target 4 to the car 18 has succeeded. The device control unit 11 determines that the boarding of the car 18 by the target 4 has failed when the position of the target 4 has not moved into the car 18 until a predetermined time has elapsed since the door 19 of the car was opened. When the position of the target 4 moves from the inside of the car 18 to the landing 16, the device control unit 11 determines that the target 4 has successfully descended from the car 18. The equipment control unit 11 determines that the target 4 has failed to get off the car 18 when the position of the target 4 has not moved to the landing 16 after a predetermined time has elapsed since the door 19 of the car was opened.

The boarding/alighting observation unit 28 acquires an image of the target 4 captured by a camera provided in the elevator, for example, through the control panel 20. The equipment control unit 11 determines whether or not the entry and exit of the target 4 to and from the car 18 is successful, for example, as follows, based on the image of the target 4 acquired by the entry and exit observation unit 28. When acquiring an image of the target 4 moving inside the car 18, the equipment control unit 11 determines that the boarding of the target 4 to the car 18 has succeeded. The equipment control unit 11 determines that the taking of the car 18 by the target 4 has failed when the image of the target 4 moving inside the car 18 is not acquired until a predetermined time has elapsed since the door 19 of the car was opened. When acquiring an image of the target 4 moving to the landing 16, the equipment control unit 11 determines that the target 4 has successfully left the car 18. The equipment control unit 11 determines that the target 4 has failed to get off the car 18 when the image of the target 4 moving to the landing 16 is not acquired until a predetermined time elapses after the door 19 of the car is opened.

The boarding/alighting observation unit 28 obtains a measured value of the load of the scale 25 on the car 18, for example, through the control panel 20. The equipment control unit 11 determines whether or not the taking in and out of the car 18 by the target 4 is successful, for example, as follows, based on the measurement value of the load by the scale 25 acquired by the taking in and out observation unit 28. The equipment control unit 11 determines that the taking of the car 18 by the target 4 has succeeded when a predetermined weight is added to the load of the car 18 while the doors 19 of the car are open. The equipment control unit 11 determines that the elevator taking of the car 18 by the target 4 has failed when a predetermined weight is not added to the load of the car 18 until a predetermined time elapses after the door 19 of the car is opened. The device control unit 11 determines that the target 4 has successfully left the car 18 when the weight of the car 18 decreases by a predetermined amount while the car door 19 is open. The equipment control unit 11 determines that the target 4 has failed to get off the car 18 when the preset weight is not reduced by the load of the car 18 until a preset time elapses after the door 19 of the car is opened.

The boarding/alighting observation unit 28 acquires information on whether or not the traffic detector 27 detects traffic, for example, via the control panel 20. The equipment control unit 11 determines whether or not the entry and the descent of the target 4 to the car 18 have succeeded, for example, as follows, based on the presence or absence of detection by the traffic detector 27 acquired by the entry and descent observation unit 28. When the device control unit 11 detects that the target 4 passes from the landing 16 to the car 18 while the doors 19 of the car are open, it determines that the boarding of the target 4 to the car 18 has succeeded. The device control unit 11 determines that the riding of the target 4 on the car 18 has failed when the passage of the target 4 from the landing 16 to the car 18 is not detected until a preset time elapses after the door 19 of the car is opened. When detecting that the target 4 passes from the car 18 to the landing 16 while the doors 19 of the car are open, the device control unit 11 determines that the target 4 has successfully left the car 18. The device control unit 11 determines that the target 4 has failed to get off the car 18 when the passage of the target 4 from the car 18 to the landing 16 is not detected until a predetermined time elapses after the door 19 of the car is opened.

The device control unit 11 may determine whether or not the entry and the exit of the target 4 to and from the car 18 are successful by combining or switching a plurality of conditions. The equipment control unit 11 determines whether the boarding and alighting are successful or not, for example, based on at least one of position information of the target 4, an image of the target 4 captured by a camera provided in the elevator, a measurement value of the scale 25, and a passage detection result by the passage detector 27.

As described above, in the communication system 1 according to embodiment 3, the car 18 responds to the hall call of the destination 4 controlled by the destination server 9. The facility control unit 11 of the facility server 7 includes an ascending/descending observation unit 28. The boarding/alighting observation unit 28 observes the state of the target 4 with respect to the boarding and alighting of the car 18 of the elevator. The equipment control unit 11 determines whether the boarding of the target 4 to the car 18 has failed based on the boarding status of the target 4 to the car 18 observed by the boarding/alighting observation unit 28. When it is determined that the destination 4 has failed to take the car in the car 18, the device control unit 11 transmits a message including the 3 rd information indicating a request to stop taking the car in the car 18 to the destination server 9.

The device control unit 11 also determines whether or not the target 4 has failed to get off the car 18 based on the state of the target 4 getting off the car 18 observed by the boarding/alighting observation unit 28. When it is determined that the destination 4 has failed to get off from the car 18, the device control unit 11 transmits a message including the 3 rd information indicating a request to get off from the car 18 to the destination server 9.

The boarding/alighting observation unit 28 observes the boarding/alighting of the target 4 based on the position information of the target 4, the presence or absence of traffic detection by the traffic detector 27, the measurement value of the scale 25, and at least one of the images of the target 4. The position information of the target 4 is stored in association with the information of the target 4 specified by the 1 st information. The traffic detector 27 is provided at the doorway of the car 18. The traffic detector 27 detects traffic at the entrance/exit of the car 18. The scale 25 measures the load of the car 18. The image of the target 4 is taken by a camera provided in the elevator.

With this configuration, it is determined whether or not the cage 18 is successfully raised or lowered by the target 4 based on the observation result of the raising/lowering observation unit 28. Therefore, the accuracy of determining whether the boarding/alighting is successful is improved. The facility control unit 11 may determine whether or not boarding and alighting have succeeded in combination with the presence or absence of a message of receiving an boarding completion notification or an alighting completion notification. When the determination is made by combining a plurality of conditions in this way, the accuracy of determining whether the addition or subtraction has succeeded is higher.

Industrial applicability

The communication system of the present invention can be applied to cooperation of facilities and machines operating within the facilities. The device server and the machine server of the present invention can be applied to the communication system. The data structure of the present invention can be applied to communication in the communication system.

Description of the reference symbols

1: a communication system; 2. 2a, 2b: a building; 3. 3a, 3b: building equipment; 4. 4p, 4q: a target; 5: a network; 6: a base station; 7. 7a, 7b: an equipment server; 8: a firewall; 9. 9p, 9q: a target server; 10: a 1 st communication unit; 11: an apparatus control section; 12: a target management unit; 13: a 2 nd communication unit; 14: a target control section; 15: a hoistway; 16: a landing; 17: a landing door; 18: a car; 19: a door of the car; 20: a control panel; 21: a management room; 22: a management terminal; 23: a notification unit; 24: a landing camera; 25: weighing; 26: a car camera; 27: a traffic detector; 28: an on-off observation unit; 1a: hardware; 1b: a processor; 1c: a memory.

Claims

1. An appliance server, the appliance server having: a 1 st communication unit that transmits and receives a message in a common data format to and from a plurality of device servers that communicate with and control devices in a facility; and a device control unit that controls the devices in the facility in accordance with the message received by the 1 st communication unit, wherein,

the message contains 1 st information that specifies the machine, 2 nd information that indicates a transmission direction of the message, and 3 rd information that indicates processing related to the message.

2. The device server of claim 1,

the machine is a robot or a mobile device.

3. The device server of claim 1 or 2,

the device control unit selects a device to be controlled from the plurality of devices in the facility based on the 3 rd information.

4. The device server according to any one of claims 1 to 3,

the device control unit selects the device to be controlled from a plurality of devices in the facility based on the position information of the device stored in association with the information of the device specified by the 1 st information.

5. The device server according to any one of claims 1 to 4,

when the 3 rd information indicates a request for starting the operation of the device to be controlled, the device control unit starts the operation of the device.

6. The device server according to any one of claims 1 to 5,

when the 3 rd information indicates a request to stop the operation of the device to be controlled, the device control unit stops the operation of the device.

7. The device server of any of claims 1-6,

when the 3 rd information indicates a request for changing the operating state of the device to be controlled, the device control unit changes the operating state of the device.

8. The device server of any of claims 1-7,

the device control unit causes an entry/exit management apparatus as the device to be controlled to authenticate the device based on the 1 st information.

9. The device server of any of claims 1-8,

the machine is a 1 st machine controlled by a 1 st machine server of the plurality of machine servers to move within the facility,

when the 3 rd information indicates a hall call of the 1 st car of the elevator calling the device to be controlled, the device control unit causes the elevator to register the hall call.

10. The device server of claim 9,

the device control unit specifies a floor on which the 1 st machine is located based on the position information of the 1 st machine stored in association with the information of the 1 st machine specified by the 1 st information, and causes the elevator to register the hall call for the specified floor.

11. The device server of claim 9 or 10, wherein,

in the case where the elevator has a plurality of cars, the 1 st communication part transmits information that determines the 1 st car among the plurality of cars that responds to the landing call of the 1 st machine to the 1 st machine server, including the information in the message.

12. The device server according to any one of claims 9 to 11,

the 1 st communication unit transmits the message including the 3 rd information indicating the boarding request for the 1 st car to the 1 st machine server when the 1 st car door is opened at the starting floor of the hall call.

13. The device server of claim 12,

the equipment control unit causes the elevator to close a door of the 1 st car when the 1 st machine server receives the message including the 3 rd information indicating completion of elevator boarding for the 1 st car after transmitting the message including the 3 rd information indicating the elevator boarding request to the 1 st machine server.

14. The device server of claim 12 or 13,

when the message including the 3 rd information indicating the boarding request is not received from the 1 st machine server until a predetermined time elapses after the message including the 3 rd information indicating the boarding request is transmitted to the 1 st machine server, the device control unit determines that the boarding of the 1 st machine to the 1 st car is failed, and transmits the message including the 3 rd information indicating the boarding stop request for the 1 st car to the 1 st machine server.

15. The device server according to any one of claims 9 to 14,

the equipment control part is provided with an elevator riding observation part which observes the riding condition of the machine aiming at the cage of the elevator,

the device control unit determines whether or not the 1 st machine has failed to take the elevator with respect to the 1 st car based on the elevator taking situation of the 1 st machine with respect to the 1 st car observed by the elevator taking observation unit, and transmits the message including the 3 rd information indicating an elevator taking stop request with respect to the 1 st car to the 1 st equipment server when it is determined that the 1 st machine has failed to take the elevator with respect to the 1 st car.

16. The device server of claim 15, wherein,

the boarding observation unit observes a boarding condition of the 1 st machine based on at least one of position information of the 1 st machine stored in association with information of the 1 st machine specified by the 1 st information, presence or absence of detection by a traffic detector provided at an entrance/exit of the 1 st car and detecting a situation of traffic at the entrance/exit of the 1 st car, a measurement value of a scale that measures a load of the 1 st car, and an image of the 1 st machine taken by a camera provided in the elevator.

17. The device server according to any one of claims 14 to 16,

the device control unit causes the 1 st car to perform an exclusive operation for the 1 st machine when the 1 st car is caused to respond to the landing call, and causes the 1 st car to cancel the exclusive operation when it is determined that the 1 st machine has failed to take the 1 st car.

18. The device server according to any one of claims 14 to 17,

the equipment control unit transmits the message including the 3 rd information indicating a movement request of the 1 st equipment to a preset position outside the 1 st car to the 1 st equipment server when it is determined that the 1 st equipment fails to take the 1 st car.

19. The device server according to any one of claims 14 to 16,

the device control unit causes the 1 st car to perform exclusive operation for the 1 st machine when the 1 st car is caused to respond to the landing call, transmits the message including the 3 rd information indicating a movement request of the 1 st machine to a preset position outside the 1 st car to the 1 st machine server when it is determined that the 1 st machine fails to take the elevator with respect to the 1 st car, and then causes the 1 st car to cancel exclusive operation when the message including the 3 rd information indicating completion of movement based on the movement request is received from the 1 st machine server.

20. The device server of any of claims 9-19,

when the door of the 1 st car of the elevator having the 1 st machine mounted thereon is opened at the destination floor of the hall call, the 1 st communication part transmits the message including the 3 rd information indicating the getting-off request from the 1 st car to the 1 st machine server.

21. The device server of claim 20, wherein,

the equipment control unit causes the elevator to close a door of the 1 st car when the 1 st machine server receives the message including the 3 rd information indicating completion of the elevator descending from the 1 st car after transmitting the message including the 3 rd information indicating the elevator descending request to the 1 st machine server.

22. The device server of claim 20 or 21, wherein,

when the message including the 3 rd information indicating the getting-off request from the 1 st car is not received from the 1 st machine server until a predetermined time elapses after the message including the 3 rd information indicating the getting-off request is transmitted to the 1 st machine server, the device control section determines that the 1 st machine has failed the getting-off from the 1 st car, and transmits the message including the 3 rd information indicating the getting-off suspension request from the 1 st car to the 1 st machine server.

23. The device server according to any one of claims 9 to 22,

the equipment control unit has an elevator-descending observation unit that observes a situation in which the machine descends from the car of the elevator,

the equipment control unit determines whether the 1 st machine has failed to get off the 1 st car based on a situation in which the 1 st machine gets off the 1 st car observed by the car-off observation unit, and transmits the message including the 3 rd information indicating a request to stop the 1 st car from getting off to the 1 st machine server when the 1 st machine has been determined to have failed to get off the 1 st car.

24. The device server of claim 23,

the descending observation unit observes a descending situation of the 1 st machine based on at least one of position information of the 1 st machine stored in association with information of the 1 st machine specified by the 1 st information, presence or absence of detection by a traffic detector provided at an entrance/exit of the 1 st car and detecting a traffic situation at the entrance/exit of the 1 st car, a measurement value of a scale for measuring a load of the 1 st car, and an image of the 1 st machine taken by a camera provided in the elevator.

25. The device server of any of claims 22-24,

the device server includes a notification unit configured to notify of a landing failure when the device control unit determines that the 1 st device has failed to land from the 1 st car.

26. The device server of any of claims 1-25,

when detecting the occurrence of a movement request event that is an event requiring the movement of the device, the 1 st communication unit transmits the message including the 3 rd information indicating the movement request of the device corresponding to the type of the movement request event to a device server that controls the device.

27. A machine server, the machine server having: a 2 nd communication unit that transmits and receives a message based on a common data format to and from a device server that controls devices in a facility; and a device control unit that controls the devices in the facility based on the message received by the 2 nd communication unit, wherein,

28. A communication system having an appliance server and a plurality of machine servers,

the device server has: a 1 st communication unit that transmits and receives a message based on a common data format to and from the plurality of machine servers; and a device control unit that controls devices in the facility based on the message received by the 1 st communication unit,

the plurality of machine servers each have: a 2 nd communication unit that transmits and receives a message based on a common data format with the device server; and a device control unit that controls the devices in the facility based on the message received by the 2 nd communication unit,

the message contains 1 st information that specifies the machine, 2 nd information that indicates the transmission direction of the message, and 3 rd information that indicates processing related to the message.

29. A data structure, said data structure being a data structure of a message: the message is transmitted and received in a common data format between a plurality of machine servers that communicate with and control machines within the facility and an equipment server that controls equipment within the facility, wherein,

the data structure includes 1 st information for specifying a machine in a facility, 2 nd information indicating a transmission direction of a message, and 3 rd information indicating a process to be executed by a control target of the message.