An embodiment of the present invention will be described below with reference to the accompanying drawings.
Firstly, a configuration of a communication system using a telephone exchange which is an exchange according to the embodiment of the present invention will be described.
The telephones 2a and 2d communicate with the telephone exchange 1 via an analog signal. The telephones 2b and 2e communicate with the telephone exchange 1 via a digital signal. The telephones 2c and 2f communicate with the base station 5 via a wireless digital signal. The base station 5 communicates with the telephone exchange 1 via a digital signal. The telephone exchange 1a is connected to the network 3 and telephones 2a, 2b, and 2c. The telephone exchange 1b is connected to the network 3 and telephones 2d, 2e, and 2f. Only some of the telephones 2a to 2f may be used, and a communication terminal using another communication method may be used.
The functions of the SLC 12, SLC controller 13, switch 14, and outside I/F section 15 have not been changed compared to a conventional telephone exchange. The SLC 12 has BORSCHT (Battery feed, Over voltage protection, Ringing signal sending, Supervisory, Coder-decoder, Hybrid, Testing) function, and the analog system telephone 2 can also be taken in the digital subscriber line.
The monitor section 16 monitors the line usage rate of the telephone exchange 1 (the ratio of the number of lines being used relative to the number of lines available to the telephone exchange 1 or the ratio of the bandwidth being used relative to the bandwidth available to the telephone exchange 1). The trunk circuit 17 includes a ringer 21, a PB (Push Button) section 22, a DT (Dial Tone) controller 23, a conversation securing processing section 31 (channel controller), a data processing section 32 (data conversion section), a database 33 (data transmission section), and an announce section 34. The functions of the ringer 21, PB section 22, and DT controller 23 have not been changed compared to a conventional telephone exchange.
The functions of the other components in the trunk circuit 17 differ depending on whether the telephone exchange 1 is disposed on the call-out side or call-in side. The conversation securing processing section 31 executes a conversation securing mode on the call-out side; while issues an acknowledgement on the call-in side. The data processing section 32 compresses transmission data into compressed data on the call-out side; while restores the transmission data from the compressed data on the call-in side. The database 33 stores or deletes the compressed data on the call-out side. The announce section 34 announces, on the call-in side, date or sender name included in the transmission data to the telephone 2 disposed on the call-in side.
Next, operation of the communication system according to the present embodiment will be described.
When lines are crossed, the call-out side telephone exchange (telephone exchange 1) uses the conversation securing processing section 31 to execute the conversation securing mode and uses the data processing section 32 to perform data compression to reduce traffic load of each channel, thereby securing the number of calls connected or resources (channels) on the IP network to increase the number of channels that can be used at a time. Further, the call-out side telephone exchange stores data in the database 33 and, if transmission data has not reached the call-in side due to call loss, retransmits the data. For example, when lines are crossed, the call-out side telephone exchange uses 1% of the available bandwidth to execute the conversation securing mode to compress transmission data in the conversation securing mode into 1/100 its volume, thereby substantially doubling the number of channels that can be used at a time as compared to that in normal time. A configuration in which an extra frequency band is prepared for the telephone exchange 1 and the telephone exchange 1 uses the prepared frequency band only at the execution time of the conversation securing mode may be employed.
When the call-out terminal goes off-hook to originate a call to the call-out side telephone exchange (S11), the SLC controller 13 of the call-out side telephone exchange determines whether a busy state is occurring or not (S12). The SLC controller 13 determines that a busy state is occurring if the line usage rate detected by the monitor section 16 exceeds a predetermined threshold. If a busy state is not occurring (No in S12), the SLC controller 13 performs connection processing to the network 3 in the same manner as a conventional telephone exchange (S13). If a busy state is occurring (Yes in S12), the conversation securing processing section 31 transmits to the call-out terminal a request for confirmation of conversation securing mode utilization for obtaining confirmation of utilization of the conversation securing mode together with a busy tone (S14). Then, the call-out terminal prompts a user to check whether to utilize the conversation securing mode or not according to the request for confirmation of conversation securing mode utilization transmitted from the call-out side telephone exchange and determines whether the confirmation of utilization of the conversation securing mode has been obtained or not (S15).
If confirmation of utilization of the conversation securing mode has not been obtained from the user (No in S15), the call-out terminal goes on-hook (S16), and this flow is ended. On the other hand, if confirmation of utilization of the conversation securing mode has been obtained from the user (Yes in S15), the call-out terminal transmits conversation securing mode utilization confirmation to the call-out side telephone exchange. Then, the monitor section 16 monitors the network state to acquire the line usage rate (S22), and the conversation securing processing section 31 selects an adequate conversation securing mode based on the acquired line usage rate, data amount and distance from the call-out terminal, and a protocol used (S23). In the conversation securing mode, a data compression method, line (channel on the telephone network 6 or IP network 7), and frequency band to be used, etc., are specified.
At this time, the conversation securing processing section 31 selects, as a line to be used, e.g., a line with a low usage rate (a line which is not congested), a line with a broader frequency band, or a line with a small delay. The conversation securing processing section 31 determines a frequency band in accordance with the data amount to be transmitted. The conversation securing processing section 31 uses, e.g., one of the following first to third data compression methods.
In the first data compression method, if a voice signal from the telephone 2 is an analog signal, the data processing section 32 performs an A/D conversion to convert the analog voice signal into voice data (digital signal) and performs compression coding for the voice data to obtain compressed data. In the second data compression method, the data processing section 32 performs voice recognition for a voice signal or voice data from the telephone 2 to convert the signal or data into text data which is compressed data. In a third data compression method, the data processing section 32 notifies the call-out terminal of prepared fixed phrase candidates to prompt the user of the call-out terminal to select one of the choices and obtains a selected number of the fixed phrase as compressed data. The fixed phrase is a sentence to respond a situation (e.g., confirmation about the safety of interested parties in case of an emergency) where lines are easily crossed and therefore is a minimum sentence that needs to be transmitted. By using the above data compression methods, it is possible to significantly reduce the frequency band for each channel in the conversation securing mode as compared to that in normal time.
Then, the conversation securing processing section 31 issues a start notification of a conversation securing mode selected by the monitor section 16 to the call-out terminal (S24). The conversation securing processing section 31 may arbitrarily start the conversation securing mode without obtaining the confirmation of utilization of the conversation securing mode from the user and, after that, transmit the conversation securing mode start notification to the call-out terminal.
After receiving the conversation securing mode start notification (S25), the call-out terminal receives an input of transmission data (voice or data) from the user and transmits the input data to the call-out side telephone exchange (S26). Then the data processing section 32 adds basic information such as name of a sender or date information to the transmission data from the call-out terminal and performs data compression for the transmission data according to the data compression method in the current conversation securing mode (S31). The database 33 stores the compressed data obtained as a result of the data compression (S32). Then the monitor section 16 starts monitoring whether any compressed data exists in the database 33 (S33) and determines whether the compressed data can be transmitted to the network 3 via a line in the conversation securing mode (S34). If the data transmission is not possible (NG in S34), the monitor section 16 returns to step S33 after a predetermined time has elapsed and makes determination once again. On the other hand, the data transmission is possible (OK in S34), the outside I/F section 15 reads in compressed data stored in the database 33 and transmits the compressed data to the call-in side telephone exchange via the network 3 (S35).
When detecting that any compressed data exists in the database 33 after a predetermined time has passed from step S33, the monitor section 16 determines that the compressed data has not been normally transmitted due to call loss or the like and instructs the outside I/F section 15 to retransmit the compressed data.
Then, after receiving the compressed data via the network 3, the data processing section 32 of the call-in side telephone exchange restores the transmission data from the compressed data (S41). Then, the announce section 34 announces the basic information included in the transmission data to the call-in terminal, and the SLC controller 13 determines whether it can be connected to the call-in terminal (S42). If the connection is not possible (NG in S42), the SLC controller 13 discards the transmission data (S43). On the other hand, if the connection is possible (OK in S42), the SLC controller 13 transmits the transmission data to the call-in terminal. Then, the call-in terminal receives the transmission data (S44) and transmits a reply indicating that the data has been received, to the call-in side telephone exchange (S45). Upon receiving the reply, the conversation securing processing section 31 of the call-in side telephone exchange issues an acknowledgment (S46) and transmits it to the call-out side telephone exchange via the network 3 (S51).
Upon receiving the acknowledgment, the SLC controller 13 of the call-out side telephone exchange determines whether it can be connected to the call-out terminal (S52). If the connection is not possible (NG in S52), the SLC controller 13 discards the acknowledgment (S53). On the other hand, if the connection succeeds (OK in S52), the SLC controller 13 transmits the acknowledgment to the call-out terminal. The call-out terminal receives the acknowledgment and transmits a reply indicating that the acknowledgment has been received to the call-out side telephone terminal (S54). Upon receiving the reply, the conversation securing processing section 31 of the call-out side telephone terminal terminates the conversation securing mode, transmits a conversation securing mode termination notification to the call-out terminal (S55), and deletes the compressed data stored in the database 33 (S56). Upon receiving the conversation securing mode termination notification, the call-out terminal goes on-hook (S57), and this flow is ended.
Note that the data compression may be performed not by the data processing section 32 of the call-out side telephone exchange but by the call-out terminal, and the data restoration may be performed not by the data processing section 32 of the call-in side telephone exchange but by the call-in terminal.
According to the present embodiment, when lines are crossed, transmission data is compressed on the call-out side and restored on the call-in side. As a result, a communication channel can be secured using limited resources, thereby avoiding a conversation disabled state. Further, the configuration in which the call-in terminal notifies the call-out terminal that the transmission data has been received allows reliable communication. Further, by applying the conversation securing mode in case of disaster or the like, important information such as confirmation of the safety of interested parties can reliably be performed.
A monitor step corresponds to steps S22 and S33 in the embodiment. A channel control step corresponds to steps S23 and S24 in the embodiment. A data conversion step corresponds to step S31 in the embodiment. A data transmission step corresponds to steps S32, S33, and S34 in the embodiment. A data restoration step corresponds to step S41 in the embodiment.
Further, it is possible to provide a program that allows a computer constituting the exchange to execute the above steps as an exchange control program. By storing the above program in a computer-readable storage medium, it is possible to allow the computer constituting the exchange to execute the program. The computer-readable storage medium mentioned here includes: an internal storage device mounted in a computer, such as ROM or RAM, a portable storage medium such as a CD-ROM, a flexible disk, a DVD disk, a magneto-optical disk, or an IC card; a database that holds computer program; another computer and database thereof; and a transmission medium on a network line.
Number | Date | Country | Kind |
---|---|---|---|
2006-210548 | Aug 2006 | JP | national |