JP2018042173A - Communication system, communication device, and communication method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable data processing having a small delay even when a resource for the processing is small, in applying different module configurations to emergency transmission and non-emergency transmission performed in an emergency state of an elevator.SOLUTION: A communication method for transmitting data from an elevator to a call center includes performing processing using at least one of a first module and a second module. To a session started in a non-emergency state, non-emergency setting for processing data using both of the first module and the second module is applied. To a session started in an emergency state, emergency setting for processing data using not the first module but the second module is applied. In the session to which the emergency setting is applied, the application of the emergency setting is continued until the session ends even when the emergency state transits to the non-emergency state in the middle of the session.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a technique for switching a data communication method according to a situation. For example, in data transmission between an elevator control unit and a call center, it relates to data transmission relating to an emergency state of the elevator.

  For maintenance of a plurality of elevators at a long distance, related data is periodically collected on the elevator side and transmitted to a management department such as a call center for analysis and maintenance. Examples of the data include detection data of various sensors, data generated spontaneously by the device, and voice and other data input by an elevator user. Data is collected by a small processor or control unit in each elevator and transmitted to a call center through a WAN (wide-area network).

  Wireless technologies such as LTE (Long-Term-Evolution) are often used in networks, and such network links are often bandwidth limited and the available bandwidth varies. Depends on external factors and can change over time.

  In case of an emergency, an emergency call button inside the elevator allows the passenger to make an emergency call to the call center. This call is usually a two-way voice call. In order to assess whether the currently available bandwidth of the communication link is sufficient for a voice call, a bandwidth assessment is performed periodically or just before making an emergency call.

  In order to save operating costs, an emergency call is made using VoIP (Voice-over-IP) over the same communication link used for maintenance data transmission. Further operational cost savings require a reduction in the amount of data transmitted over the network, which is achieved by applying data compression prior to transmission over the WAN.

  In call centers, compressed data must be decompressed before use. Compression and decompression is one example, and there are other ways to help reduce operating costs, such as other ways to reduce data, and such methods are generally referred to as “data conversion”. It is called. Such transformations, such as compression and decompression, require certain calculations performed on the data, thereby causing a certain delay in transmission. However, emergency calls have very high requirements on voice quality, and the delay for transmission needs to be as small as possible.

  One solution to the problem of conflicting normal transmission (non-emergency transmission) and emergency transmission requirements is to use dedicated WAN concatenation for emergency transmission. Another solution is to prohibit unrelated non-emergency transmissions.

  In the latter solution, as described in Patent Document 1, when network connection is shared between different transmissions, the emergency transmission is preferentially processed and the available resources that can be used by the emergency transmission are reduced. It is to improve. This requires a distinction between emergency transmissions and non-emergency transmissions, for example, to distinguish between emergency transmissions and non-emergency transmissions, e.g. TCP / IP destination 3 tuple (TCP / IP destination 3-tuple), i.e. Related session information indicating the protocol, destination IP address and destination port number is considered. In addition, the content of the transmission data is analyzed.

US Patent Publication US2006 / 0194,566A1

  Considering the increase in operating costs, it is not practical to use a dedicated WAN for emergency transmission. So, to improve the available resources that emergency transmission can use on the shared line, during the emergency transmission, prohibit irrelevant non-emergency transmission or process the emergency transmission preferentially. Can be considered.

  Non-emergency transmission prohibition and emergency transmission priority processing require a distinction between non-emergency transmission and emergency transmission. One of the methods for determining this is to examine, for example, TCP / IP destination 3 tuple, ie, session information indicating a protocol, a destination IP address and a destination port number. The problem with this approach is that, for example, if a similar TCP / IP destination 3 tuple is used, it may not be possible to distinguish between emergency and non-emergency transmissions based solely on session information. Therefore, in many cases, in addition to session information evaluation, the contents of the converted data must be analyzed. However, such content analysis is difficult due to the capabilities of the small processors typically used in elevator control units.

  Also, in many cases, a certain amount of data must be processed first before final results are obtained, so the analysis of such content itself introduces a certain time delay during that period. Cannot meet the high demands on the quality of emergency call connections. Also, sudden or unilateral changes in the configuration related to data conversion can cause errors in compression and decompression, for example, if such changes are recognized between the elevator side and the call center side and are not synchronized. May cause loss.

  The present invention enables data processing with low delay even when resources for processing are small when different module configurations are applied to emergency transmission and non-emergency transmission performed for an emergency state of an elevator, for example. The purpose is to do.

  One aspect of the present invention that solves the above problem is a communication system that transmits data from a transmitter to a receiver while distinguishing data into non-emergency data and emergency data. In this system, the transmitter includes an input unit, an output unit, a storage device, a session management unit, a control unit functional block, and a module for processing data. The storage device includes a session parameter for specifying a session for transmitting data, a session management table for storing a generation timing of the session, an emergency flag table for storing a switching timing between an emergency state and a non-emergency state, and non-emergency data and emergency data. A module flag application table that defines a mode of module application. The session management unit writes and reads the session management table. When data is input from the input unit, the control unit functional block obtains information on the session related to the data from the session management unit, and the emergency flag table. Based on the session generation timing and conversion timing, the data is classified into non-emergency data or emergency data, and the module is applied to the data based on the discrimination and the contents of the module flag application table and received from the output unit. Send to the machine.

  Another aspect of the present invention is a communication device that distinguishes and transmits data into non-emergency data and emergency data. This communication apparatus includes an input unit, an output unit, a storage device, a session management unit, a control unit functional block, and a module for processing data. The storage device includes a session parameter that specifies a session for transmitting data, a session management table that stores the generation timing of the session, an emergency flag table that stores a switching timing between an emergency state and a non-emergency state, non-emergency data, and an emergency A module flag application table that defines a mode of application of the module to each of the data. The session management unit writes and reads the session management table. When data is input from the input unit, the control unit functional block obtains information on the session related to the data from the session management unit, and the emergency flag table. Based on the session generation timing and the conversion timing, the data is classified into non-emergency data or emergency data, and the module is applied to the data based on the discrimination and the contents of the module flag application table. Send.

  Still another aspect of the present invention is a communication method for processing data by at least one of a first module and a second module when transmitting data from an elevator to a call center. In this method, two states, an emergency state and a non-emergency state, can be set. In a session that was started when it was in a non-emergency state, a non-emergency setting is applied in which data is processed by both the first module and the second module. In a session that is started in an emergency state, an emergency setting is applied in which data is processed by the second module without using the first module. In the session to which the emergency setting is applied, even when the emergency state transitions to a non-emergency state on the way, the application of the emergency setting is continued until the session is ended.

  The present invention allows for immediate and resource lightweight determination of emergency / non-emergency configurations for transmission and conversion module applications and avoids intermittent or desynchronized configuration changes.

The component block diagram which illustrates the outline | summary of the system configuration | structure of this invention. FIG. 4 is an application diagram of a communication sequence and transmission and conversion module illustrating different sessions and their respective module applications with respect to emergency conditions received by an external emergency device. A time chart illustrating the different events, a comparison of the timestamps of a given event and their different results. FIG. 3 is a component block diagram illustrating the configuration of related devices on the elevator side and the call center side. FIG. 2 is a component block and interaction diagram illustrating a simplified overview of the interaction between different components to achieve the objectives of the present invention. The hardware block diagram which illustrates the hardware component of the structure which can implement this invention. FIG. 3 is a sequence diagram of the acquisition of emergency signal status and associated data structure updates of the present invention. FIG. 5 is a sequence diagram illustrating an important main function of the present invention in case of emergency data transmission. In the case of non-emergency data transmission, a sequence diagram illustrating an important main function of the present invention. The program flow of the main function of the present invention performed on the elevator side. The program flow of the session and emergency time stamp comparison function performed by the main function of the present invention on the elevator side. 6 is a program flow illustrating application of data transmission and conversion module according to emergency / non-emergency related state of the present invention. The program flow of the main function of this invention performed by the call center side. 6 is a program flow illustrating updating related data structures for registered emergency / non-emergency signals of the present invention. Schema that illustrates the module flag application table. Schema illustrating the emergency flag table. Schema illustrating an example session management table. Schema illustrating emergency network flag structure.

  Embodiments will be described in detail with reference to the drawings. However, the present invention is not construed as being limited to the description of the embodiments below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or the spirit of the present invention.

  In the structures of the invention described below, the same portions or portions having similar functions are denoted by the same reference numerals in different drawings, and redundant description may be omitted.

  In the present specification and the like, notations such as “first”, “second”, and “third” are attached to identify the components, and do not necessarily limit the number or order. In addition, a number for identifying a component is used for each context, and a number used in one context does not necessarily indicate the same configuration in another context. Further, it does not preclude that a component identified by a certain number also functions as a component identified by another number.

  The position, size, shape, range, and the like of each component illustrated in the drawings and the like may not represent the actual position, size, shape, range, or the like in order to facilitate understanding of the invention. For this reason, the present invention is not necessarily limited to the position, size, shape, range, and the like disclosed in the drawings and the like.

  One of the embodiments described below will be briefly described. The elevator control unit receives an emergency signal from an emergency device, for example an emergency call button in the elevator car, and then registers the associated emergency status change and their respective timing in the emergency status change table. When transmission data is ready for transmission, for example after some data sources provide the data to the control unit, the associated session creation time and the recently associated valid emergency time stamp from the emergency state conversion table To be compared. Regarding the comparison result, the transmission and conversion module is applied to the transmission data according to a part of the configuration, the network header indicating the previous comparison result is added, and the receiving call center side applies the configured transmission and conversion module in a similar manner. be able to.

  1 to 18 are used to explain the first embodiment in more detail. In order to provide an overview to the first embodiment of the present invention, a brief description of each drawing is as follows.

  FIG. 1 illustrates example components of the system configuration of the first embodiment. In order to provide the essential concept of the present invention, FIGS. 2 and 3 are used as follows.

  FIG. 2 illustrates the communication sequence and transmission and conversion module application for different sessions for each emergency state during each session creation time.

  FIG. 3 illustrates a simplified overview of different module configurations as a result of different session generation and emergency signal reception timing and comparison of their respective timings.

  The two figures show that the relationship between the registered emergency signal timing and the session creation time used for data transmission is either sent using an emergency configuration or sent using a non-emergency configuration A method of determining whether will be described.

  In addition to the different components of the present invention, their interaction will be described as follows with reference to FIGS.

  FIG. 4 illustrates the possible component configurations and associated data and control connections between the main components of the device at the transmitting elevator side and the receiving call center side.

  FIG. 5 shows a simplified overview of the data flow and component interaction between the main components on the transmitting elevator side when the data to be transmitted arrives, and how the respective transmission and conversion module configurations are selected. Is illustrated.

  A possible hardware configuration for implementing the first embodiment of the present invention will be described with reference to FIG.

  FIG. 6 illustrates a hardware configuration diagram of a possible hardware configuration of one embodiment of the present invention.

  An event sequence for explaining the gist of the present invention will be described with reference to FIGS. FIG. 7 applies whenever a new emergency signal condition is acquired, for example when an emergency button is pressed and a related signal is received, or when a previous emergency condition is turned off with a related signal from the call center. FIG. 4 illustrates a sequence diagram for updating related data structures. FIG. FIG. 8 is a sequence diagram illustrating a general operation of the present embodiment when the module configuration applied to the transmitted data is an emergency configuration. FIG. 9 is a similar sequence diagram illustrating the general operation of this embodiment when the module configuration is a non-emergency configuration.

  The program flow on the main elevator side performed for the elevator control unit will be described below with reference to FIGS. 10, 11 and 12, and FIG. 12 is the flow performed on the call center side described later. FIG. 10 is a program flow diagram of the main functions on the elevator side that are performed by the control unit on the transmission side and transmitted to the call center when data arrives from a predetermined data source. FIG. 11 illustrates the transmission side of FIG. 10 after a related session used for transmission is received from the session manager to determine which transmission and conversion module configuration should be applied to the currently pending data. FIG. 10 is a program flow diagram of a session and emergency time stamp comparison function performed as a sub-flow by the main program flow of the control unit of FIG. 12 is a program flow diagram illustrating the application of the transmission and conversion module with respect to the emergency / non-emergency configuration determined by the program flow of FIG. 11, when the data is transmitted, the main program flow of the control unit on the elevator side When data is received, it is performed as a sub-flow according to the main program flow of the center side communication function.

  The program flow on the main call center side performed at the call center will be described with reference to FIG. Further, as described above, the program flow of FIG. 12 is also performed on the call center side. FIG. 13 is a program flow diagram illustrating the main functions on the call center side performed by the communication function on the receiving side when data is received.

  As briefly described in the following paragraphs, when the control unit on the elevator side receives an emergency signal, the program flow of FIG. 14 is performed.

  FIG. 14 is a program flow diagram illustrating an emergency flag table update flow performed by the control unit on the elevator side when an emergency signal is received, for example, after an emergency button is pressed.

  The main data structure necessary for the first embodiment of the present invention will be described as follows with reference to FIGS. The data structure of FIG. 15 is stored and used in both the elevator-side control unit and the call center, while the data structures of FIGS. 16 and 17 are stored and used only in the elevator-side control unit. FIG. 15 is a schema illustrating a module flag application table for explaining a transmission and conversion module configuration for emergency and non-emergency transmission managed by the control unit on the elevator side and the communication function on the call center side. FIG. 16 is a schema illustrating an emergency flag table for explaining the timing of emergency signal conversion managed by the control unit on the elevator side. FIG. 17 illustrates a simplified session management table that includes a session creation time stamp and additional session parameters and is managed by the session manager on the elevator side.

  In order to allow the control unit on the elevator side to notify the remote call center of the emergency state of the current transmission, a network flag is used as described below with reference to FIG. FIG. 18 is a simplified schema illustrating the emergency state network flag structure and the network header flag that allows the sending elevator side to notify the receiving call center side of the emergency state.

  The foregoing brief description has provided a general overview of the invention. Detailed description of each drawing is as follows.

  In the present embodiment, functions such as calculation and control are realized by a program stored in a storage device being executed by a processor (CPU), thereby cooperating with other hardware. When a program executed by a computer, its function, or means for realizing the function is referred to as “function”, “means”, “part”, “unit”, “module”, “block”, “flow”, etc. There is. In addition, for convenience, these may be described as processing subjects.

  A function equivalent to the function configured by software can be realized by hardware such as FPGA (Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit). Such an embodiment is also included in the scope of the present invention.

  FIG. 1 illustrates a system configuration (100) of an embodiment. The elevator (110) houses a control unit (120) that is coupled to the WAN (150), and the call center (130) is similarly coupled to the WAN. The control unit (120) in the elevator (110) can send and receive data to the call center (130) through the WAN (150).

  FIG. 2 illustrates a communication sequence of a plurality of sessions when transmitting data from an elevator to a call center, and an emergency / non-emergency transmission applied in response to an emergency / non-emergency state transition and a conversion module used therefor. To do.

  The emergency state (201) is illustrated on the left side by an emergency state change line (210). “ON” indicates an emergency state, and “OFF” indicates a non-emergency state. That is, this information indicates the transition timing from the emergency state to the non-emergency state and the transition timing from the non-emergency state to the emergency state. As shown on the timeline (220), all four different sessions “Session # 1” through “Session # 4” start from the transmitter (202). In FIG. 2, the transmitter (202) is an elevator-side endpoint for data transmission, and shows a simplified session origin. On the opposite call center side, the receiver (208) is also a simplified endpoint.

  Before the data of each session is transmitted through the WAN (205), on the transmission side, the first transmission conversion module, that is, module # 1 (203), and the second transmission and conversion module, that is, module # 2 Applied or passed to (204). On the receiving side, the session data is applied or passed to module # 2 (206) and module # 1 (207) in reverse order.

  As illustrated by line (221), “Session # 1” is generated while the emergency state is “OFF”, as illustrated by emergency state change line (210), so non-emergency transmission. The module configuration for is applied. That is, first, module # 1 (203) is applied to data at 222 on the transmission side, module # 2 (204) at 223, module # 2 (206) at 224 on the reception side, and module # 1 (207) at 225 is applied to the data. The A response from the receiver (208) is performed in the same manner. That is, first, module # 1 (207) is applied at the receiving side 226, then module # 2 is applied at 227, followed by module # 2 (204) at 228 on the transmitting side, and module # 1 (203 at 229). ) Applies.

  Session # 2 is similarly generated in a non-emergency state. However, after session # 2, an emergency change to "ON" occurs as illustrated at 211 on the emergency change line. During such a modified emergency state, session # 3 is generated and the module configuration for emergency transmission is applied. That is, although module # 1 (203) is passed by 240 on the transmission side, module # 2 (204) is applied at 241 and similarly, module # 2 (206) is applied at 242 on the reception side. 243, module # 1 (207) is passed.

  Before session # 4 is created, an emergency state transition to “OFF” occurs, as illustrated at 212, after which the module configuration for the non-emergency state is applied to the data for session # 4. .

  On the other hand, session # 3 continues after timing 212, and data is exchanged between transmitter 202 and receiver 208. After the timing of 212, the emergency state is "OFF" as illustrated at 213 on the state change line, but since session # 3 was generated during the emergency "ON" state, 260, 261 , 262 and 263, the configuration for emergency transmission is applied.

  In the same manner, after the emergency state is changed to “ON” in 214, the subsequent transmission through the session # 4 described above is generated while the emergency state is “OFF”. As shown by 272 and 273, a module configuration for non-emergency transmission is used.

  The feature of the sequence illustrated in FIG. 2 is that the transmission and conversion module configuration for each session is determined based on the emergency state at the time of session generation, regardless of the current emergency state. This is a delay-inducing module for emergency transmission while ensuring the safety of data transmission to which different schemes are applied by ensuring that the order and application of the modules are kept the same on the sending and receiving sides. Allows for rapid disabling of.

  FIG. 3 illustrates a comparison of emergency change state and session creation time timings in two examples (300 and 350).

In the first example (300), a first emergency signal (eg, pressing an emergency button in an elevator car) is first received at time t _E of 311 as shown on the timeline (305). The After some time, at 312 a new session is created at time t ₁ . Thereafter, the first data transmission occurs at a time _{t 2} 313, the second data transmission at time _{t 3} at 314 is generated.

To determine whether to use an emergency module configuration or a non-emergency module configuration, at both data transmission timings t ₂ and t ₃ , an emergency signal timestamp t _E and a session creation time timestamp t ₁ In the example (300), as illustrated at 340, the emergency module configuration is applied because the session creation time t ₁ is the same as or later than the registration time of the emergency signal t _E.

In the second example (350), a new session is generated by the first 361 at time _{t 1.} Subsequently, the first data transmission at time _{t 2} at 362 is generated. Thereafter, the emergency signal at time _{t E} 363 is received. Then, the second data transmission at time _{t 3} at 364 is generated.

In this example, the comparison at 390 indicates that the session creation time t ₁ is earlier than the emergency signal time t _E , so the non-emergency module configuration is applied for the first and second data transmissions. The timing comparison illustrated in FIG. 3 shows that the emergency transmission and conversion module configuration should be applied to the transmission of pending data until the specified session ends, or the non-emergency transmission and conversion module configuration. Provides an easy and quick way to determine what should be applied. Generally, since the session generation time is managed by the session management unit, a configuration for registering and managing the timing of registered emergency state change and comparing related timings before data transmission may be added.

  FIG. 4 illustrates the components of one embodiment of the present invention and their respective data and control connections.

  On the transmission side shown in the upper part is an elevator (110) that houses a control unit (120), an emergency input device (410), and a predetermined data source (411). In one embodiment, the emergency input device (410) is an emergency call button in an elevator car. The control unit (120) is a processor including a number of functional blocks and data structures. In one embodiment, the control unit (120) is a general purpose processor and the functional blocks illustrated in FIG. 4 are an abstract concept of their actual representation.

  The functional blocks included in the control unit (120) are the session management unit (420), the control unit functional block (430), the first transmission and conversion module, that is, the module # 1 (450), and the second transmission and conversion module. That is, module # 2 (460). In the description of this embodiment, the number of transmission and conversion modules is limited to two for ease of understanding, but in general, the number of modules is limited. Not.

  In one embodiment, module # 1 is a bandwidth evaluation module and module # 2 is a compression / decompression module. The session manager (420) manages the end-to-end communication session between the elevator control unit (120) and the remote call center (130). In one embodiment, the session manager (420) Processing TCP and UDP sessions. Processing includes, for example, session creation and destruction. Information regarding session management is stored in a session management table (1800) connected to the session management unit (420). Connections for control are indicated by dotted lines.

  The control unit functional block (430) handles end-to-end data transmission of maintenance data and emergency call data and application of the transmission and conversion module to the transmission data.

  Data transmitted from a predetermined data source (411) is transmitted, and in one embodiment, the data source periodically transmits elevator usage and related component status information. The transmission data flow is illustrated by the dotted line (441). In order to control the transmission data flow through different transmission and conversion modules, the control unit functional block (430) controls the switches (440 and 442) with the control connection (445), and the first switch (440) Whether the transmission data flows through the module # 1 (450) is controlled, and the second switch (442) controls whether the transmission data flows through the module # 2 (460).

  In order to determine which module should be applied to the transmitted data, the control unit functional block (430) includes, in one embodiment, a transmission and conversion module application configuration for the emergency / non-emergency state of the session. Information in the flag application table (1500a) is used. In order to determine the emergency state of the session, the control unit functional block (430) uses related session information received by the session manager (420) and the emergency flag table (1600). In one embodiment, the emergency signal received by the emergency input device (410) is registered in the emergency flag table (1600). After the necessary modules are applied, the transmission data is transmitted through the WAN (150) to the call center (130) on the receiving side shown on the lower side.

  The call center (130) block, like the control unit (120), has a number of transmission and conversion modules whose application is controlled by two switches (472 and 474) which are sequentially controlled by the call center communication function block (470). That is, a processor including module # 2 (490) and module # 1 (480). The call center communication function block (470) applies the module application configuration using the module flag application table (1500b), similarly to the control unit function block (430) on the elevator side. In order to determine the emergency state, the call center communication function block (470) refers to the network header information included in the received transmission data.

  With the control and data flow between the components as illustrated in FIG. 4, the elevator side determines the application of the transmission and conversion module based on the emergency / non-emergency status according to the information managed in the table. be able to. On the receiving call center side, it is possible to apply the transmission and conversion module based on the emergency / non-emergency state in consideration of the network header information.

  FIG. 5 illustrates an overview of the operation of one embodiment of the present invention, focusing on the main components of the control unit (120). The general data flow is illustrated at the bottom, where data (540) is received by the control unit (120) and can be selected by the position of the switch (550), one of the paths preconfigured by different modules. And sent to WAN (150).

  In this simplified overview, two transmission and conversion modules, namely module # 1 and module # 2, are applied in this order, or only module # 2. For example, the former configuration is for non-emergency transmission and the latter is for emergency transmission.

  Information and judgment related to the setting of the switch (550) will be described using the upper two-third components of FIG. First, a signal from an emergency input device (410), which will be described later with reference to FIG. 14, is received and processed by a functional block (1400) that performs an emergency flag table update flow, and the result is registered in the emergency flag table (1600). .

  When data is transmitted (for example, data (540)), a related session is requested from the session management unit (420) that sequentially uses information stored in the session management table (1800). The session information and related emergency status information stored in the emergency flag table (1600) are processed by the function block (1100) to determine the emergency status of the related session.

  A function block (1100), which will be described later with reference to FIG. 11, performs a time stamp comparison function flow for comparing a session and an emergency time stamp. The emergency state for the related session and the application configuration of the modules included in the module flag application table (1500) are processed by the function block (1200), and the switch ( 550) is set.

  The function block (1200) performs an actual “switch setting” and transmission and conversion module by performing an application function flow (1200) of a module that applies all enable communication modules to data, as will be described later with reference to FIG. Is being applied.

  The effect of the component interaction illustrated in FIG. 5 is that the emergency state change information obtained by the control unit function block based on the registered emergency signal and the timing of the related session information managed by the session management unit are compared. To apply an emergency or non-emergency module configuration to the actual transmission data.

  FIG. 6 illustrates the configuration of possible hardware components to implement this embodiment. The control unit (120) may include similar components that can perform the different functions described in this embodiment. CPU (715), main memory (720) and auxiliary memory (730) as storage devices, NIC (740) and predetermined serial input / output (I / O) (760) are interconnected through a predetermined communication bus (710). Has been.

  The number of components can vary, for example, other NICs are attached to the bus. The CPU (715) may be a general-purpose processor and can access other components connected through the communication bus (710). For example, the CPU (715) accesses a program instruction stored in the main memory (720), Can handle the program. The program is, for example, a predetermined machine code that implements a different program flow of the embodiment of the present invention.

  In one embodiment, the program instructions are stored in a predetermined non-volatile auxiliary memory (730) that is copied into the main memory (720) by the CPU at a start time and then executed. In one embodiment, the data source (411) and the emergency input device (410) are connected through a serial I / O (760), and the WAN is connected through a NIC (740).

  The configuration illustrated in FIG. 6 is a minimum configuration for embodying the present embodiment, and can be changed without restricting the application of the present embodiment. According to an exemplary embodiment, the CPU (715) executes a program stored in the memory (720 or 730) to perform the functions of the embodiment. Without limiting the scope of the present invention, a non-general purpose processor may be used instead of the CPU (715).

  FIG. 7 illustrates an emergency signal acquisition and registration sequence. The emergency input device (410) and control unit function block (430) on the transmitting elevator side as well as the call center (130) on the receiving side are illustrated. Predetermined emergency state information, for example a “button press” message (610), is transmitted by the emergency input device (410) and received by the control unit function block (430). Thereafter, the control unit functional block (430) performs an emergency flag table update flow (1400a). In the processing of the emergency flag table update flow (1400a), for example, the emergency state change is registered in the emergency flag table (1600) (not shown). This completes the basic processing sequence of the event that causes the emergency “ON” state change.

  At the bottom of FIG. 7, the event that causes the emergency state to change to “OFF” is also illustrated, the call center (130) sends an “emergency turn-off” message (620), and then the emergency flag table update flow (1400b). Is transmitted to the control unit functional block (430). In the processing of the emergency flag table update flow (1400b), for example, the related emergency state change is registered in the same manner as described above. In general, the sender of the non-emergency signal (“emergency situation OFF” message (620)) is the call center (130), but other signal sources that do not limit the scope of the invention are possible.

  The sequence described in FIG. 7 occurs every time a predetermined signal message (610 or 620) is received by the control unit function block (430). The sequence illustrated in FIG. 7 allows an emergency state change update based on an emergency signal and related information received from an emergency input device such as an emergency call button in an elevator car, for example.

  FIG. 8 is a sequence diagram of an embodiment of the present invention in the case of emergency data transmission. The illustrated components are a control unit functional block (430) on the transmission elevator side, a session manager (420), a first transmission and conversion module, i.e. module # 1 (450), and a second transmission and conversion module, That is, the module # 2 (460) and the second transmission and conversion module on the reception call center side, that is, the module # 2 (490), the first transmission and conversion module, that is, the module # 1 (480), and the call center communication function Block (470).

  First, a predetermined message (810) that data is ready for transmission is received by the control unit functional block (430). Subsequently, the operation of the main flow (1000) is performed by the control unit function block (430).

  In the main flow (1000), first, in 815, a “session acquisition” message is transmitted to the session management unit (420) to request a session related to the data to be transmitted. The session management unit 420 performs a predetermined session lookup process (817), and returns the related session in 819 to the control unit function block (430). This associated session may be referred to as the “current session”.

  When a response (819) to the session request (815) is sent to the control unit functional block (430), a session lookup (817) sets up a new session by the session manager (420), or Existing sessions are searched.

  Subsequently, in the control unit functional block (430), the time stamp comparison function flow (1100) for comparing the session and the emergency time stamp is performed by the main flow (1000). In this comparison, as shown in the sequence diagram of FIG. 7, the time stamp of emergency state change previously registered in the emergency flag table (1600) and the message (819) returned from the session management unit (420) are displayed. By comparing, the emergency state for the current session associated is determined. Details of the main flow (1000) will be described later with reference to FIG. 10, and details of the time stamp comparison function flow (1100) will be described later with reference to FIG.

  In this example, the emergency state for the current session is “ON”, which means that the emergency configuration is applied to the current session. Therefore, the emergency flag setting process (820) in the network data is subsequently performed by the main flow (1000) of the control unit functional block (430), the TCP option is added to the network data, and it is applied to the receiving call center. Notify emergency status.

  Thereafter, the application function flow (1200a) of the module that applies to the data of all the enable communication modules is performed by the main flow (1000) of the control unit function block, and all the data regarding the emergency state of the current session Apply the necessary transmission and conversion modules. In this example, since it is an emergency transmission, since only module # 2 is applied, transmission data is transmitted to module # 2 (460) by message (830), and the result processed by module # 2 (460) is a message ( 832), the transmitted data is updated.

  Finally, the main flow (1000) of the control unit functional block (430) transmits the transmission data of the message (838) to the call center communication functional block (470).

  The main flow (1300) of the call center function block receives the transmission data, checks the emergency flag acquisition function block (850) in the network data for the relevant TCP option in the network data, and determines the emergency state of the current session. .

  Since in this example it is an urgent transmission, the urgent module configuration must be applied because the relevant TCP options are discovered. Subsequently, the application function flow (1200b) of the module that applies to the data of all enabled communication modules is performed by the main flow (1300) of the call center function block, and all necessary transmissions regarding the emergency state of the current session. And apply functional modules. Here, since the configuration for emergency transmission applies only module # 2 as in the configuration applied on the transmission side, the received transmission data is stored in module # 2 (490) in the message (860). ) And the result is returned in message (862) to update the received transmission data.

  This completes the main function process. In one example, the call center communication function block (470) can then store the received transmission data or use it for a predetermined maintenance related analysis.

  FIG. 9 is a sequence diagram of an embodiment of the present invention in the case of non-emergency data transmission. In general, the functional sequence illustrated in FIG. 9 is similar to that illustrated in FIG. 8, and some are changed in relation to the emergency / non-emergency status of the current session. This description focuses primarily on the differences.

  After the transmission data prepared for transmission is received in the message (910) by the control unit function block (430), the main flow (1000) is performed, and then the current session is received by the session management unit. A time stamp comparison function flow (1100) that compares subsequent sessions and emergency time stamps turns the emergency state for the current session “OFF”, which means that a non-emergency configuration is applied.

  In this case, a module application function flow (1200a) for performing application to data of all enabled communication modules is subsequently performed. First, the transmission data is transmitted to the module # 1 by the message (930), the result processed by the module # 1 is received by the message (932), and the transmission data is updated. The updated transmission data is transmitted to the module # 2 by the message (934), the result processed by the module # 2 is received by the message (936), and the transmission data is updated again. The updated transmission data is transmitted to the call center communication function block (470) by a message (938).

  The call center communication function block (470) receives the transmitted data in its main flow (1300) and determines the associated emergency state of the current session by checking for certain associated TCP options in the network data. In the example of FIG. 9, such an option is not found, so a non-emergency condition is assumed.

  Subsequently, a module application function flow (1200b) for applying the data to all enabled communication modules is performed, and the received transmission data is first transferred to the module # 1 in the message (960). Send, receive the result in message (962), update the send data, send the updated send data again to module # 2 in message (964), and send the result in message (966) And update the transmission data accordingly. Further, the processing of the transmission data received and updated can occur in the same manner as described in FIG.

  FIG. 10 illustrates a program flow of the main flow (1000) performed in the control unit functional block (430) of the transmission side elevator.

  When data is transmitted in step (1015), the program flow is started by the control unit functional block (430) on the transmission side. In this case, the data is, for example, data generated by the data source (411).

  Subsequently, in step (1020), a session applicable to the transmission (referred to as a current session) is requested from the session management unit (420) using the network parameter of the data to be transmitted. For the network parameter, for example, a predetermined protocol, a destination IP address, and a protocol port can be set in the maintenance-related data.

  If the associated session does not yet exist, the session manager (420) handles all the steps necessary to set up and set up a session with the remote call center. Here, in one embodiment, the session is a known UDP or TCP session, and can be established by a known step. In one embodiment, the session information generated as a result of the processing may be one row of the session management table (1800) of FIG.

  Subsequently, the time stamp T1 of the current session is obtained in step (1030). The time stamp T1 can be acquired as a value in the T1 column (1810) of previously received session information by designating a session parameter and referring to the session management table (1800). The generation time of the current session can be known from the time stamp T1.

  Subsequently, a time stamp comparison function flow (1100), which is a sub-flow for comparing sessions and emergency time stamps, is performed. The result of the time stamp comparison function flow (1100) is recorded in an emergency state variable (the current session emergency state, “Yes” or “No”) in a subsequent step (1040).

  In the next step (1050), the value of the emergency state variable is evaluated, and if the value is “Yes”, it means that the emergency configuration should be applied to the transmitted data, and the program flow is step (1052). Following this, an emergency flag is set in the network data. In one embodiment, this flag is as described below in the emergency flag field (1735) of the emergency network flag structure (1700) of FIG.

  In the next step, a module application function flow (1200) for applying data to all enabled communication modules is performed as a subflow, and the communication module can convert the transmission data as necessary. .

  Subsequently, the transmission data subjected to data conversion as necessary is transmitted to the receiver in step (1060). The receiver is, for example, a call center (130). Finally, the flow ends at step (1090).

  If the emergency state variable evaluates to “No” in step (1050), this means that a non-emergency configuration should be applied to the transmitted data, and the program flow skips step (1052), Continuing to the applied function flow (1200) of the module, which is a subflow that is immediately called.

  According to the program flow of FIG. 10, after the data to be transmitted is received by the transmitting control unit functional block, the related subflows are sequentially performed, the related current session information is received, and the related current session is related. Determine the emergency situation. Based on the determined emergency state, apply the transmission and conversion module for transmission data, and prepare and receive header flags in the network data to notify the receiver of the emergency state determined before the current session The emergency state can be determined only by considering the network header on the side.

  FIG. 11 illustrates the details of a time stamp comparison function flow (1100) for comparing session and emergency time stamps.

  As shown in step (1115), this program flow is started by the control unit function block (430) of the transmitting elevator as a sub-flow of the main flow (1000) after the current session is received from the session management unit. The

  First, in step (1120), the time stamp T1 of the current session is determined. This may be a value in the T1 column (1810) of the current session information received in step (1020) of the main flow (1000) in FIG. 10, and indicates the generation time of the current session.

  Subsequently, in step (1130), the final entry of the emergency flag table (1600) of FIG.

  Subsequently, in step (1140), the time stamp TC is determined as the time stamp in the column TE of the entry of the variable C.

  In step (1150), the time stamp T1 of the current session is compared with the time stamp TC of the variable C entry. That is, it is evaluated whether T1 is equal to or greater than TC. If the evaluation is affirmative, that is, if the current session creation time is currently included in the variable C and is equal to or later than the registration time of the received emergency signal, continue with step (1152). Here, the value of the “emergency flag” column of variable C is returned to the control unit function block (430).

  The value of the “emergency flag” column is the registered emergency state currently contained in variable C, and in one embodiment this is the emergency flag in the emergency flag column (1620) in the emergency flag table (1600). Possible and may have a value of “ON” or “OFF”.

  The program flow ends at step (1190). If the evaluation in step (1150) is negative, that is, if the current session generation time specified by the time stamp T1 is earlier than the registration time of the emergency signal currently included in the variable C, the processing continues in step (1154).

  In step (1154), it is evaluated whether or not the entry of the variable C is the first entry of the emergency flag table (1600). If affirmative, the program flow continues to step (1152) because there is no earlier emergency signal registered in the emergency flag table (1600).

  If not, the program flow continues at step (1158) where the previous entry in the emergency flag table (1600) is recorded in variable C. For example, when the variable C includes the third entry of the emergency flag table (1600) in step (1150), the second entry of the emergency flag table (1600) is recorded in C in step (1158).

  Subsequently, the program flow continues to step (1140), where the time stamp TC is determined as the time stamp in the column TE of the previous variable C entry.

  In the time stamp comparison function flow (1100) of FIG. 11, the emergency status of the related entry in the emergency flag table (1600) for the current session is determined. By determining the emergency state, it is then possible to determine which module configuration should be applied to the transmission data without considering the content of the transmission data or the predetermined statistics of the network data.

  In order to detect “related entries” in the emergency flag table (1600), entries are determined in reverse order from the entry having the largest time stamp (ie, the last entry). In order to detect the state of the “related entry” at the time when the current session occurs, the processing loop of FIG. 11 is executed until the time stamp TC of the entry is smaller than or equal to the time stamp T1 of the current session. do it. The “current session time stamp” is substantially a time stamp when the current session is generated.

  FIG. 12 shows a module application function flow (1200) for applying data to all enabled communication modules. This program flow is executed by both the control unit (120) on the transmission side and the call center (130) on the reception side.

  As shown in step (1215), this program flow is performed by the main flow (1000) of the control unit functional block (430) on the transmitting side after the emergency state of the current session is determined and before data is transmitted. Be started. In addition, after the data is received and the presence and state of the emergency flag in the received network data are determined, the process is started by the main flow (1300) of the receiving side call center communication function block (470). The main flow (1300) will be described later with reference to FIG.

  In step (1220), the current emergency state is obtained as an emergency state variable. If the component to be performed is the control unit function block (430), the current emergency state is determined by the result of the time stamp comparison function flow (1100) that has been called as a subflow in the main flow (1000). If the component to be executed is the call center communication function block (470), the current emergency state is determined by the program step (1344 or 1346) of the main flow (1300) of the call center communication function block.

  At step (1230), the value of the emergency state variable is evaluated and if the result is positive (ie, the result indicates an emergency state), program flow continues at step (1232).

  In step (1232), the application column is set to “Emergency configuration” in the module flag application table (1500).

  Subsequently, in step (1240), the current entry is set to the first entry of the module flag application table (1500).

  In step (1250), the value in the column of the application column of the entry of the current entry is considered.

  In step (1260), it is evaluated whether the value considered in step (1250) is “applied”. If the evaluation of step (1260) is positive (ie, the value is “apply”), program flow continues to step (1262).

  In step (1262), the module referenced by the module ID column (1510) of the current entry is applied to the transmission data. For example, if the module is a compression module, the transmission data is compressed by the module. Another example is a bandwidth evaluation module, where network data including network responses is considered and bandwidth evaluation is performed based on the considered data, while transmission data is not changed.

  In the following step (1264), it is evaluated whether or not the current entry is the last entry in the module flag application table (1500). If the evaluation at step (1264) is affirmative, the program flow ends at step (1290).

  If the evaluation at step (1264) is negative, the program flow continues at step (1268), where the current entry is set to the next entry in the module flag application table (1500). For example, if the current entry is the first entry of the module flag application table (1500), the current entry is set to the second entry of the module flag application table (1500) in step (1268). Subsequently, the program flow continues to step (1250).

  If the evaluation at step (1260) is negative, step (1262) is skipped and the program flow continues at step (1264), which means that the module currently referenced by the entry is passed or skipped. .

  If the evaluation in step (1230) is negative, the program flow continues to step (1234), where the application column is set to the non-emergency configuration column (1520) of the module flag application table (1500). The The program flow then continues with step (1240).

  The effect of the program flow illustrated in FIG. 12 is to determine the emergency state of the current session and set the application state of each module according to the module flag application table (1500) accordingly.

  FIG. 13 illustrates a main flow (1300) of the call center communication function block (470). This program flow is initiated by the receiving call center communication function block (470) when data is received.

  Data is received in step (1320). In step (1330), an attempt is made to acquire an emergency flag for the received network data. For example, it detects the presence of an emergency flag TCP option, illustrated in the emergency status network flag structure (1700) of FIG.

  In step (1340), the presence of an emergency flag is determined. If the evaluation is affirmative (ie, if an emergency flag is found), the program flow continues at step (1342), where the found emergency flag is set (“ON”) or set. ("OFF") is evaluated.

  If the evaluation at step (1342) is positive (ie, if the emergency flag in the data is “ON”), the program flow continues to step (1344), where the emergency state variable is set to “Yes”. The

  In the next step (1200), as described with reference to FIG. 12, a module application function flow (1200) for applying data to all enabled communication modules is performed as a subflow. Subsequently, the program ends at step (1390).

  If the evaluation at step (1342) is negative (ie, if the emergency flag in the data is “OFF”), the program flow continues at step (1346), where the emergency state variable is set to “No”. The Thereafter, the program flow continues to step (1200).

  If the evaluation at step (1340) is negative, the program flow continues at step (1346).

  The effect of the program flow of FIG. 13 is to evaluate the associated emergency state for data received based on network data while avoiding the management and evaluation of separate tables or other data structures.

FIG. 14 illustrates a program flow for the function of the emergency flag table update flow (1400). The program flow consists of a control unit function block on the sending side when a predetermined emergency signal is received, for example when an emergency call button in an elevator car is pressed or when an “emergency OFF” signal is received by a call center, for example. 430). In step 1420, the variable E is set to values of nearest emergency flag column (1620) of the entry of the emergency flag table (1600) (i.e., an entry with the largest timestamp _{T E} column (1610) Selected and its urgent flag value is recorded in variable E). In the next step (1430), the received emergency signal is recorded in variable S, and the emergency signal may have a value of “emergency” or “normal” (ie, non-emergency). In the next step (1440), it is evaluated whether or not the value of the variable S is “urgent”. If yes, the program flow continues at step (1442) where the value of variable E is “ON”, ie the emergency status of the most recent entry in the emergency flag table (1600) is “emergency” ( In this case, it is evaluated whether the emergency flag is “ON” or whether the emergency state is “non-emergency” (in this case, the emergency flag is “OFF”). If the evaluation is positive, the program flow ends at step (1490). If the evaluation at step (1442) is negative, the program flow continues at step (1448), where the emergency state variable is set to “Yes”. In the next step (1450), the current time stamp is recorded in the variable T, which is, for example, the current time received by a predetermined physical or logical clock. In the next step (1460), the emergency flag table (1600) a new entry is created for _{(T E} column (1610 in the variable T used for the) value and urgent flag column for a variable emergency condition in the (1620) New entries are attached to the emergency flag table (1600). Subsequently, the program flow continues at step (1490) and the program ends. If the evaluation in step (1440) is negative, the program flow continues in step (1444), where it is evaluated whether or not the value of variable E is “ON”, similar to the evaluation in step (1442). Is done. If the evaluation is positive, step (1446) continues, where the emergency state variable is set to “No”. The program flow continues at step (1450). If the evaluation in step (1444) is negative, the program ends in step (1490). The effect of the program flow of FIG. 14 is that an emergency state change or change (from “emergency” to “non-emergency” in the emergency flag table (1600) for quick comparison in the main flow (1000) of FIG. Conversely) is to register.

  FIG. 15 illustrates the schema of the module flag application table (1500) used by both the sending control unit functional block (430) and the receiving call center communication functional block (470).

  This table includes three columns: module ID column (1510), non-emergency configuration column (1520) and emergency configuration column (1530). The module ID column (1510) includes an identifier for each module present in the system configuration.

  The non-emergency configuration column (1520) and the emergency configuration column (1530) contain values of “apply” or “pass” and are specified by the module ID of the column (1510). Describe whether the module should be applied ("Apply") or not ("Pass").

  The example illustrated in FIG. 15 is a module configuration in which module “1” is first applied in the case of non-emergency transmission, then module “2” is applied, and only module “2” is applied in the case of emergency transmission. explain. The module flag application table (1500) may be prepared by the system engineer or the management unit and then stored in the non-volatile auxiliary memory (730), and in the main memory (720) upon initialization for actual use. Can be copied. Such preparation must be applied at both the control unit (120) and the call center (130).

  Normally, when a module is “applied” in the module flag application table (1500a) of the control unit (120), the module is also “applied” in the module flag application table (1500b) of the call center (130). Become. Further, when a module is “passed” in the module flag application table (1500a) of the control unit (120), the module is also “passed” in the module flag application table (1500b) of the call center (130). Become.

  Also, typically, the order of modules referenced by the module ID column (1510) in the call center (130) is opposite to the order of modules referenced by the module ID column (1510) in the control unit (120), The order of application of modules on the call center side is opposite to that on the elevator side. For example, if the order of modules on the elevator side is “1” and then “2”, the order of modules on the call center side is usually “2” and then “1”.

  The effect of the schema of FIG. 15 is that it makes it possible to define the configuration of which modules should be applied in which order based on the emergency situation.

  FIG. 16 illustrates the schema of the emergency flag table (1600) used by the sending control unit function block (430).

This table includes a _TE column (1610) and an emergency flag column (1620). The _TE column (1610) contains an emergency state change timestamp, and the emergency flag column (1620) contains whether the new emergency state is emergency ("ON") or ("OFF").

In this embodiment, the emergency flag table (1600), entry with the smallest timestamp _{T E} column (1610) is in the initial state. In the example of FIG. 16, the first entry is in the initial state, its time stamp is “0.0”, and the emergency flag value is “OFF”.

Thereafter, the newly registered emergency flag table entry does not have a smaller time stamp, and the value of the time stamp increases as time passes. Therefore, the value of _{T E} column (1610) is ascending.

  For example, the emergency flag column (1620) is set to “OFF” in the initial state as illustrated in the first entry of this example, and thereafter, transitions between the “ON” and “OFF” states are alternated.

Examples of the emergency flag table is shown in Figure 16, the first entry for _{T E} value is "0.0", a urgent flag value is "OFF", the second entry for _{T E} value "1,463,106,191.52357756 "and the urgent flag is set to"", the third entry for _{T E} value" oN "is, urgent flag is" 1463114351.63438774 "is set, the fourth entry for _{T E} value" OFF 1465894427 .26855124 "and the emergency flag is set to" ON ".

  The effect of the schema of FIG. 16 is to manage emergency state transitions (including their respective occurrence times) so that emergency time stamps and session creation time stamps can be quickly compared.

  FIG. 17 illustrates an example schema of a session management table (1800) managed by the session management unit (420) in the transmission-side control unit (120).

  This table includes a T1 column (1810) and a session parameter column (1820). The T1 column (1810) includes a time stamp of the session creation time, and the session parameter column (1820) includes additional information about the session, eg, protocol, source IP address, source protocol port, destination IP address, and destination. Contains 5 tuples describing protocol ports.

  In this embodiment, it is guaranteed that the entry in the session management table (1800) is unique. The table “slot” is not reused, for example, after the session specified by the third entry in the table is discarded, a new different session can later be recorded in the third entry.

  The example of the session management table illustrated in FIG. 17 is generated at the time “146658890955.8273157157” and is described by the 5-tuple “TCP: 10.0.0.1:3114: 10.0.0.2:5000”. The first session, time “1465891381.48874950” and the second session, time “14665894428”, described by the 5-tuple “TCP: 10.0.0.1:4121: 10.0.0.2:5000” .14782374 "and the third session described by the 5-tuple" UDP: 10.0.0.1:41214:10.0.10.1:5060 "and time" 14665895093.34837919 " 5 tuple “UDP: 10.0.0.1:41214:10.0.10.1 A fourth session illustrated by 5060 ".

  According to the schema of FIG. 17, the time stamp T1 of the session creation time so as to enable the comparison of the session creation time of step (1150) and the emergency state change time performed in the time stamp comparison function flow (1100) of FIG. Can be provided.

  FIG. 18 illustrates an emergency state network flag structure (1700) that allows the sending control unit (120) to notify the receiving call center of the emergency state applied to the transmitted data at the sending side. With this configuration, the receiving side can apply the same module configuration as the transmitting side to the same emergency state without considering management of network data content or a predetermined related data structure.

  In this embodiment, the emergency state network flag structure (1700) transmits an emergency flag using the TCP option. The emergency flag field (1735) has a Boolean value as illustrated in the field (1737). For example, “1” indicates an emergency state. The effect of the data structure of FIG. 18 is to allow emergency state synchronization for the application of the associated module at both the sender and receiver.

  The present invention is not limited to the embodiments described above, and includes various modifications. For example, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace the configurations of other embodiments with respect to a part of the configurations of the embodiments.

120: Elevator control unit 150: WAN
410: Emergency input device 420: Session management unit 430: Control unit functional block 450: Transmission and conversion module # 1
460a: Transmission and conversion module # 2 (configuration # 1)
460b: Transmission and conversion module # 2 (configuration # 2)
540: Data 550: Switch (simplified)
1100: Time stamp comparison function flow 1200: Module application function flow 1400: Emergency flag table update flow

Claims (15)

A communication system for transmitting data from a transmitter to a receiver separately from non-emergency data and emergency data,
The transmitter is
An input unit, an output unit, a storage device, a session management unit, a control unit functional block, and a module for processing the data,
The storage device
A session parameter for specifying a session for transmitting the data, a session management table for storing the generation timing of the session,
An emergency flag table for storing the transition timing between the emergency state and the non-emergency state;
A module flag application table that defines a mode of application of the module for each of the non-emergency data and the emergency data,
The session management unit writes and reads the session management table;
When data is input from the input unit, the control unit functional block obtains session information related to the data from the session management unit, reads the emergency flag table, and generates the session generation timing and the conversion Based on the timing, the data is classified into non-emergency data or emergency data, the module is applied to the data based on the discrimination and the contents of the module flag application table, and transmitted from the output unit to the receiver. ,
Communications system. When the control unit functional block distinguishes the data into emergency data, the control unit functional block adds a flag indicating that the data is emergency data to the data, and transmits the data from the output unit to the receiver.
The communication system according to claim 1. The receiver
A receiving side input unit, a receiving side output unit, a receiving side storage device, a call center communication functional block, and a receiving side module for processing the data;
The receiving side storage device
A receiving-side module flag application table that defines a mode of application of the module for each of the non-emergency data and the emergency data;
The call center communication function block detects the flag when data from the transmitter is input to the receiving side input unit, and determines whether the data is non-emergency data based on a result of the detection. And applying the receiving module to the data based on the result of the determination and the contents of the receiving module flag application table,
The communication system according to claim 2. There are a plurality of the modules and the receiving side modules, and one of the modules and one of the receiving side modules make a pair,
The module flag application table and the receiving module flag application table are:
Define whether to perform processing in the module for each of the non-emergency data and the emergency data, and the order of the processing,
The communication system according to claim 3. The emergency flag table is
The conversion timing from the emergency state to the non-emergency state and the conversion timing from the non-emergency state to the emergency state are stored, and the conversion timings are arranged in ascending order in time.
The communication system according to claim 4. The transmitter transmits the non-emergency data and the emergency data to a call center from a control unit attached to an elevator,
The receiver is for receiving the non-emergency data and the emergency data at the call center,
The timing for switching from the non-emergency state to the emergency state is set based on a signal transmitted from an emergency call button attached to the elevator.
The communication system according to claim 5. The timing for switching from the emergency state to the non-emergency state is set based on a signal transmitted from the call center.
The communication system according to claim 6. The module includes a conversion module that compresses or decompresses data,
The module flag application table and the receiving module flag application table are defined so as not to apply the conversion module to the emergency data.
The communication system according to claim 7. The emergency data includes voice data,
The communication system according to claim 8. The flag is a TCP option flag.
The communication system according to claim 2. A communication device that transmits data separately into non-emergency data and emergency data,
An input unit, an output unit, a storage device, a session management unit, a control unit functional block, and a module for processing the data,
The storage device
A session parameter for specifying a session for transmitting the data, a session management table for storing the generation timing of the session,
An emergency flag table for storing the transition timing between the emergency state and the non-emergency state;
A module flag application table that defines a mode of application of the module for each of the non-emergency data and the emergency data,
The session management unit writes and reads the session management table;
When data is input from the input unit, the control unit functional block obtains session information related to the data from the session management unit, reads the emergency flag table, and generates the session generation timing and the conversion Based on the timing, the data is classified into non-emergency data or emergency data, based on the content of the discrimination and the module flag application table, the module is applied to the data, and transmitted from the output unit,
Communication device. When the control unit functional block distinguishes the data into emergency data, the control unit functional block adds a flag indicating that the data is emergency data to the data.
The communication apparatus according to claim 11. A communication method for processing data by at least one of a first module and a second module when transmitting data from an elevator to a call center,
Two states can be set, emergency and non-emergency,
In a session initiated when the non-emergency state was applied, apply a non-emergency setting that processes the data in both the first module and the second module;
In the session started when the emergency state, the emergency setting to process the data in the second module without using the first module,
In the session to which the emergency setting is applied, even when the emergency state transits to the non-emergency state on the way, the communication method continues to apply the emergency setting until the session ends. The first module is a module that compresses the data;
In the session that was started when the emergency state, the voice data is transmitted as the data.
The communication method according to claim 13. The emergency state is started by operating an emergency call button of the elevator,
The non-emergency state is started by releasing the emergency state by a release signal transmitted from the call center.
The communication method according to claim 13.

Images