JPH02194797A - Terminal identification device for communication system - Google Patents

Abstract

PURPOSE:To preserve security, and simultaneously, to facilitate work to register and rewrite an ID number by registering the ID number of each terminal in an electrically rewritable non-volatile memory at each terminal, and preventing this rewriting unless a prescribed condition is satisfied. CONSTITUTION:An extension terminal 50 is provided with the electrically rewritable non-volatile memory EEPROM 51 for storing the ID number and an erasure.write circuit 53 for performing the erasure and the write of the IO number for EEPROM 51 as the setting means of the ID number, and only when control data purporting that the registration is permitted is given from a main device 100, it writes the new ID number in EEPROM 51, and in addition, transmits it to the main device 100 as the control data. On the other hand, the main device 100 is provided with CPU 55 for regulating and controlling the whole operation of system, and only in the case where the prescribed condition is satisfied at the time of the reception of the data to request the rewriting, it sends permission data. Thus, the work to register and rewrite the ID number can be facilitated, and simultaneously, the security can be preserved.

Description

[Detailed Description of the Invention] [Objective of the Invention] (Industrial Application Field) The present invention is directed to a system in which a plurality of terminals are connected to a switching device or a main device (hereinafter collectively referred to as a center), such as a button telephone device, for example.
The present invention relates to a terminal identification device for identifying a communicating terminal by attaching a terminal identification number to communication data in a communication system connected to a center and communicating control data and voice data with a center.

(Prior Art) A typical example of this type of communication system is a button telephone device. FIG. 9 shows the system configuration of a key telephone device in which a plurality of terminals are connected to one main device.

As shown in the figure, the main device 1 includes at least one outside line 3 and a plurality of extension terminals 5. ~5n are connected. The extension terminals 51 to 5n are multi-connected to the main device 1 via a common audio signal line 7 and a control data line 9. Main device 1
operates by obtaining AC100V power from connector 1,
By placing the extension terminals 5, to 5 under its control, calls between them and the outside line 3 and calls between the extension terminals are controlled.

In a telephone system that employs such a multi-terminal connection method, the control data exchanged between the main device 1 and each extension terminal 5□-51 is based on the identification number (I) of each extension terminal 5□-5.
D number). That is, for example, the first
As shown in Figure 0, the downlink data output from the main device 1 to the terminal 5 has a 1 and a dot code "0" at the beginning to indicate downlink data and an ID number unique to the terminal 5. A code number (hereinafter referred to as a downlink ID number) is added. In addition, the uplink data output from the terminal 5 to the main device 1 includes a code number (hereinafter referred to as uplink ID number) is added.

Then, based on the uplink and downlink ID numbers, the main device 1
And the terminals 51 to 5□ are designed to be able to identify communication partners.

Such an ID number for each terminal needs to be registered in the system when the system is installed or when the contents of the system are changed such as adding more terminals. A conventional configuration for registering this ID number will be explained with reference to a configuration diagram of a conventional extension terminal 5 shown in FIG.

The extension terminal 5 has a CPU for controlling the inner part of this terminal.
13, which includes a ROM 17 that stores a control program via a bus 15, a RAM 19 that stores data necessary for control, and an input/output interface 21 that relays the transmission and reception of control data to and from the internal terminal. It is connected. The CPU 13 uses a setting switch 23 for setting an ID number via the input/output interface 21, and a key matrix 25 having dial keys and function keys.
, a hook switch 31 that turns on/off in conjunction with off-hook/on-hook of the handset 29, and a main device interface circuit 33 that relays communication with the main device 1 and supplies power from the main device 1 to each part. control data. Also, CPU
13 is connected to the main device interface circuit 33 and the main device interface circuit 33 via the human output interface 21.
The control data is transmitted to a call switch 39 that selectively connects the audio signal line 35 from the receiver to either the handset 29 or the speaker 37 for on-hook calls, and the display 41 that displays various displays such as an incoming call display and an in-transit display. can now be sent.

The two handsets have a collocation circuit 4 that performs 2-wire and 4-wire exchange, etc.
The speaker 37 is connected to the call switch 39 via an output amplifier 45. The speaker 37 is connected to the call switch 39 via an output amplifier 45.

The main device interface circuit 33 includes an audio interface section 33a connected to the audio signal line 7 and a control data line 9.
It has a data interface section 33b connected to.

Registration of the ID number is performed using the setting switch 23. The setting switch 23 is, for example, a 4-bit rotary switch, and is manually operated to set an ID number. The state of this setting switch 23 is read by the CPU 13 through the human output interface 21, and the CPU 13 converts the read ID number into control data and sends it to the human output interface 2.
1 to the main device interface circuit 33.

The main device interface circuit 33 transmits the data of the ID number from the data interface section 33b to the control data line 9.
Send to. The data of this newly set ID number is prefixed with the previously set ID number of this terminal 5, is sent to the control data line 9, and is received by the main device 1. The main device 1 identifies which terminal the data comes from based on the ID number at the beginning, and registers the newly set ID number in the ID number registration area of the terminal 5 in the built-in memory.

(Problem to be Solved by the Invention) As described above, in the conventional communication system, an ID number is registered by a manually operated setting switch 23 such as a rotary switch provided in each terminal. However, since such a setting switch 23 can be operated by the user of each terminal without permission, for example, by changing the ID number of one's own terminal to the ID number of another's terminal, it is possible to change the ID number of one's own terminal to that of another's terminal. It is possible to avoid charges by having the main device recognize it as if it were a phone call, or to break the outside call restriction by changing the ID number of a terminal that is restricted from making outside calls to the ID number of a terminal that is capable of making outside calls. It is.

Therefore, instead of the setting switch 23, a ROM in which an ID number is written in advance is used, and the record of this ROM is transferred to the CPU 13.
There is also a system in which registration is performed by reading the data and sending it to the main device 1. In the case of devices that use this ROM, the above actions cannot be easily performed, but on the other hand, if the ID number needs to be changed due to changes in the system contents, etc., it is possible to replace the ROM with another ROM. Requires time-consuming work.

Furthermore, whether the setting switch 23 or the ROM is used, there is a problem in that it is troublesome to check for duplicate ID numbers within the same system.

Therefore, an object of the present invention is to provide a communication system that includes a center and terminals, in which the user of each terminal cannot change the ID number without permission, but a specific person such as the person in charge of managing the system can change the ID number as necessary. The purpose is to make it easy to register and change ID numbers.

[Structure of the invention]

(Means for Solving the Problems) The present invention provides an electrically rewritable terminal-side nonvolatile memory for registering an identification number provided in a terminal, and a device for rewriting the identification number registered in this memory. an electrically rewritable center-side non-volatile memory for registering the identification number of each terminal provided at the center; and a number rewritten by the rewriting means for the identification number registered in this memory. The rewriting means transmits rewriting request data to the determining means prior to rewriting, and the determining means receives the rewriting request data upon receiving the rewriting request data. To provide a terminal identification device for a communication system in which permission data is sent to a rewriting means only when a predetermined condition is satisfied, and the rewriting means executes rewriting only when receiving the permission data.

(Function) A new ID different from the current ID number for a certain terminal.
When attempting to register a number, data requesting rewriting is first sent from the rewriting means to the determining means. The determining means sends permission data to the rewriting means only if a predetermined condition is satisfied upon receiving the request data. The rewriting means rewrites the ID number of the terminal registered in the terminal to a new number only after receiving the permission data, and the registration means rewrites the ID number of the terminal registered at the center side to the new number.

If predetermined conditions are not met when the rewrite request data is sent, a new ID number cannot be registered. Here, the predetermined condition is, for example, that a specific code is input before rewriting, or that a switch installed in the center cabinet is turned on. Therefore, general users who are not informed of the above-mentioned specific code or who are unable to open the center cabinet cannot register or change the ID number on their i-hands.

The ID number of each terminal is registered in an electrically rewritable non-volatile memory in each terminal and in the center. Here, the electrically rewritable nonvolatile memory is, for example, EEPROM, backed-up RAM, or the like. By registering an ID number in such a memory, it can be rewritten by electrical signal processing, making the registration and modification work simple.

In the preferred embodiment of the present invention, a check is also performed for the new ID number, and rewriting is permitted only if there is no duplicate. Therefore, duplicate registration of ID numbers is prevented, and security is more reliably ensured.

(Embodiment) FIG. 1 shows a block configuration of an extension terminal constituting an embodiment of the terminal identification device according to the present invention. This embodiment is applied to a key telephone device, and in FIG. 1, the same elements as those in FIG. 11 already explained are given the same reference numerals and redundant explanation will be omitted.

The extension terminal 50 according to the present invention uses the setting switch 23 in the conventional terminal 5 in FIG.
Instead, it has an electrically rewritable nonvolatile memory, for example, an EEFROM 51, for storing an ID number, and an erase/write circuit 53 for erasing and writing the ID number to the EEPROM 51. This erase/write circuit 53 is placed under the control of the CPU 13 via the input/output interface 21. Also, E.E.
The PROM 51 is under the control of the erase/write circuit 53.
It stores the ID number given from CPolB through the input/output interface 21, reads out the stored IDI number, and sends it to the CP through the input/output interface 21.
It is now sent to U13.

The control program stored in ROMI 7 includes I
A program for registering a D number is included, but this program only registers a new ID number in the EE when control data to permit registration is given from the main device 1, as will be described later.
The content allows writing to the PROM 51 and transmitting it to the main device 1 as control data.

FIG. 2 shows a block configuration of the main device 1 secured in this embodiment.

This main device 100 has a CPU 55 for controlling the overall operation of the system, which is connected via a bus 57 to a ROM 59 that stores a control program, and various data necessary for control (ID number, outside line call restriction, It is connected to a RAM 61 for storing information such as call charges, etc., and an input/output interface 63 for relaying data transmission and reception with various parts in the main device. The CPU 55 is connected to an external line interface circuit 65 that relays communication with the external line 3 via an input/output interface 63, and a terminal 50 that is multi-connected to the main device 100 via an audio signal line 7 and a control data line 9. a terminal interface circuit 67 for relaying communication with the terminal and supplying driving power to the terminal; a sound source circuit 69 for generating various status identification tones (dial tone, ringback tone, beep tone, hold tone, etc.); It transmits control data to a communication path switch 71 that exchanges audio signals between circuits 65, 67, and 69, and also transmits control data to an external line interface circuit 65 and a terminal interface circuit 67.
It is now possible to receive control data from These circuits operate by receiving DC power from a power supply circuit 75 connected to an AC 100V power supply through a connector 73.

The terminal interface circuit 67 includes an audio interface section 67a connected to the audio signal line 7 from the terminal 50, and a data interface section 67 connected to the control data line 9.
It has b. Upstream data from the terminal 50 is received by the data interface section 67b and sent to the CPU 55 through the input/output interface 63. Also, CPU5
The control data for the terminal 50 output from 5 is sent to the data interface section 6 through the input/output interface 63.
7b, and is sent to the control data line 9 as downlink data.

The ROM 59 contains an I/O code sent from the terminal 50 only when a predetermined password is sent from the terminal 50.
A program configured to allow registration of D numbers is stored. The ID number is sent from the terminal 50 to the main device 100 as control data. This ID number is input from the data interface section 67b to the CPU 55 through the input/output interface 63. The CPU 55
If a predetermined PIN number has been entered from the terminal 50 prior to entering the D number, the entered ID number will be sent to the RA.
It is stored in the ID number registration area assigned to that terminal 50 in M61.

The RAM 61 is backed up by a battery 77 during a power outage to protect the registered contents.

Next, the operation when setting an ID number in this embodiment will be explained with reference to the block diagrams shown in FIGS. 1 and 2, and the data communication diagram between the main device 100 and the terminal 50 shown in FIG. 3. do. In addition, Fig. 3A shows the case where registration is performed normally.
FIG. 3B shows the communication operation when duplicate registration occurs. Also, the ID number shall be 3 digits.

There are two types of ID number registration: registration that is performed when a new telephone system is installed, and registration that is performed when the contents of an already-operated telephone system are changed. For registration, which is performed only during installation, normally all terminals 50 will be initially set with the same ID number (for example, "000") at the time of shipment from the factory, so multiple terminals 50 may be connected to the main device 100 at the same time and registered. If an attempt is made to do this, confusion will occur because the main device 100 cannot identify each terminal 50. Therefore, during registration during installation, each terminal 50 is connected to the main device 100 one by one, and after the registration of one terminal 50 is completed, it is disconnected and the next terminal 50 is connected. Register. on the other hand,
When registering when changing the system in operation, each terminal 50 has already been registered.
Since different ID numbers are set for the terminals 50, registration can be performed while all terminals 50 are connected to the main device 100. In either case, the registration operation for each terminal 50 is as follows.

First, a case where registration is performed normally will be explained.

First, referring to FIG. 1, in the key matrix 25 of the terminal 50, a registration mode setting request, for example, "*#*
#*#” is dialed, and then an ID number registration request, for example, “123456” is dialed. This dial is detected by the CPU 13, and the CPU 13 stores this dial data “*#*#*#123456” in the EEFROM.
ID number currently set in 51, for example “123
'' to the main device face circuit 33. Then, the third
As shown in FIG. A, dial data "*#*#*#123456" with an uplink ID number "1123°" based on the current ID number "123" at the beginning is sent to the main device 100.

Referring to FIG. 2, in main device 100, dial data "*#*#*#123456" is input to CPU 55 together with the ID number. The CPU 55 receives the input I
By comparing the D number "123" with the ID number of each terminal 50 currently set in the RAM 61, it is possible to recognize which terminal 50 the data is from. Next, CPU5
5 recognizes the registration mode setting request based on the input data "*@*@*@". Subsequently, the CPU 55 receives input data “1”.
ID preset 23456° in RAM61
Verify with the number registration code “123456”. Furthermore, ID
Any code can be set as the number registration code. Since the input data "123456" and the ID number registration code "123456" match, the CPU 55 recognizes that an ID number registration request has been made and switches to the ID number registration mode. When entering the ID number registration mode, the CPU 55 first sends registration permission data to the RA.
It is sent to the terminal interface circuit 67 along with the current ID number "123"3" of the terminal 50 in M61.

Then, as shown in FIG. 3A, the current ID number "12"
Registration permission data prefixed with the downlink ID number “0123” based on “3” is transmitted to the terminal 50.

Referring to FIG. 1, the terminal 50 compares the ID number "123" attached to the registration permission data received by the CPU 13 with the current ID number "123" in the EEFROM 51, and if they match, Recognizing that the data is downlink data for its own terminal, it sends a display command based on the registration permission data to the display 41 to cause a display (for example, a liquid crystal display or lighting of an LED) to indicate that registration permission has been granted.

Next, in the key matrix 25 of the terminal 50, the new I
A D number, for example "789" is dialed. This dial data "789" is input to the CPU 13. CP
U13 writes this new ID number "789" into a predetermined area of RAM19. At the same time, the CPU 13 sends this new ID number "789" to the main device interface circuit 33 along with the current ID number "123" in the EEPROM 51. As a result, as shown in FIG. 3A, the new ID number "789" is treated as upstream data with the upstream ID number "1123" based on the current ID number "123" at the beginning.
is attached and sent to the main device 100.

Referring to FIG. 2, in main device 100, the received new ID number "789" is input to CPU 55 together with the current ID number "123" added to the beginning.

The CPU 55 stores the first ID number “123°” in the RAM 61.
The uplink data is identified from which terminal 50 by comparing it with the ID number within. Next, the CPU 55 compares the new ID number "78,9" with the ID number in the RAM 61 and reads R.
Check whether the ID number is the same as that of another terminal in AM61. If there is no duplication, the CPU 55 sends the registration command data to the terminal interface circuit 67 together with the current ID number "123" of the terminal 50. Then, Figure 3A
As shown in , the registration command data is sent to the terminal 50 with the downlink ID number "0123" based on the current ID number "123" added to the beginning.

Referring to FIG. 1, in the terminal 50, when the CPU 13 receives the registration instruction data, it drives the erase/write circuit 53 to write the current ID number "123" in the EEFROM 51.
After erasing the new I stored in RAM91
Write the D number "789" to the EEPROM 51. Next, the CPU 13 sends the write completion data to the main device interface circuit 33 along with the new ID number "789".

As a result, as shown in FIG. 3A, the write-completed data is sent to the main device 100 with an uplink ID number "1789" based on the new ID number "789" added to the beginning of the data.

Referring to FIG. 2, in main device 100, after transmitting the above-mentioned registration instruction data, CPU 55 rewrites the current ID number "123""123°" of terminal 50 in RAM 61 to a new ID number "789". .After that, CPU55
receives write completion data from the terminal 50. As a result, the CPU 55 recognizes that the registration of the ID @ number "789" is completed, returns its own operation mode from the registration mode to the normal mode, and sends the registration mode cancellation data to the terminal as shown in FIG. 3A. 50 to send.

In response to the registration mode cancellation data, the CPU 13 of the terminal 50 cancels the registration permission display on the display 41 and returns to the normal incoming call standby mode.

Next, the operation in case of duplicate registration will be explained.

Referring to FIG. 3B, the operation is the same as in FIG. 3A until the new ID number "789" is sent to the main device 100 and the CPU 55 checks for duplication with other ID numbers in the RAM 61. . Referring to FIG. 2, if the CPU 55 discovers that the ID numbers are duplicated, the CPU 55 stores data that does not allow duplicate registration to the current ID number "123" of the terminal 50.
It is also sent to the terminal interface circuit 67. Then, C
The PU 55 sends a command to the sound source circuit 69 to output a registration failure warning sound (for example, a sound such as "pippipipip..."), and also controls the communication path switch 71 to output the registration failure warning sound to the terminal interface circuit 67. send to As a result, as shown in FIG. 3B, the data that does not allow duplicate registration and the alarm sound data that does not allow registration are sent to the terminal 50 with the downlink ID number "0123" added to the beginning of each.

Referring to FIG. 1, in the terminal 50, the CPU 13 causes the display 41 to display a message to that effect (e.g., liquid crystal display, LED blinking, etc.) for 3 seconds based on the data that does not allow duplicate registration, and during that time, the CPU 13 causes the call switch to be displayed. 39 to speaker 37
to output a registration failure warning sound from the speaker 37. After that, when another new ID number, for example "890", is dialed again from the key matrix 25, the C
The PU 13 rewrites the ID number "789" in the RAM 19 to the newly dialed ID number "890", and also changes this new ID number "890" to the current ID number "1".
23" to the main device interface circuit 33. As a result, as shown in FIG. 3B, the new ID number "8
90" is the upstream data and the upstream ID number is "112" at the beginning.
3” and is sent to the main device 100.

After that, if the new ID number "890" does not overlap with any other ID number, the process will proceed in the same way as in the case of normal registration as described above, and the new ID number "890"
0゛ is registered.

As described above, in this embodiment, the ID number registration code "123456" is arbitrarily set in advance.
Only when a code equal to 3456" is dialed from the terminal 50, registration permission data is output from the main device 100 and a new ID number can be registered.
Only a specific person who knows the D number registration code "123456" can register an ID number; general users cannot register an ID number.
By not informing the user of the No. 1 registration code, it is possible to prevent general users from changing their ID number without permission. Also, terminal 5
Since the EEFROM 51, which is easy to rewrite, is used as the memory for registering the ID number in 0, it is easy to change the ID number. Note that a backed-up RAM can also be used instead of the EEPROM 51.

FIG. 4 is a block diagram showing the configuration of a key telephone main unit constituting another embodiment of the present invention, and the same elements as in FIG. 3 are given the same reference numerals.

This main device 101 differs from the main device 100 shown in FIG. 2 in that it has an ID number registration switch 79. This switch 79 can be turned on and off manually, and when turned on, it supplies the output voltage of the power supply circuit 75 to the CPU 55 via the input/output interface 63. The C,P U 55 is programmed not to accept ID number registration requests from terminals unless this switch 79 is in the on state. The ID number registration switch 79 is housed in the cabinet of the main device 101, and cannot be operated by a general user who cannot open the cabinet.

The terminal connected to this main device 101 has the same configuration as the terminal 50 shown in FIG.

In this embodiment, the ID number can be registered by first opening the cabinet of the main device 101 and turning on the ID number registration switch 79, and then performing the same registration operation as in the previous embodiment. When all necessary registrations are completed, turn off the ID number registration switch 79 and close and lock the cabinet of the main device 101, making it impossible for the user to change the ID number without permission. becomes.

In this embodiment, by turning off the ID number registration switch 79 provided in the cabinet of the main device 101, it is possible to prevent the ID number from being changed without permission. In operation, terminal 5
The operation of inputting the ID number registration request dial "123456" from 0 and the matching process in the main device between the dial data and the ID number registration code "123456" may be omitted.

In addition, in this embodiment, the initial ID at the time of system installation
It is also possible to use the ID number registration switch 79 as a dedicated switch for number registration. An example of the initial ID number registration operation in such a case will be described with reference to the block diagrams of FIGS. 1 and 4 and the signal transmission/reception chart between the terminal 50 and the main device 101 shown in FIG.

Here, it is assumed that the terminal 50 has an ID number "000" set to - standard when shipped from the factory, and this ID number
Main device 1 only for terminal 50 with number “000”
01 allows registration of an initial ID number.

First, with reference to FIG. 1, FIG. 4, and FIG. 5A, the operation when an ID number is normally registered will be described. First, after confirming that no terminal is connected to the main device 101, the seven ID number registration switches of the main device 101 are turned on. When the CPU 55 of the main device 101 detects a signal input from the switch 79 via the human output interface 63, it switches to the initial ID number registration mode.

Next, one terminal 50 is connected to the main device 101. The terminal 50 receives power from the terminal interface circuit 67 of the main device 101 and starts operating.

First, the CPU 13 uses the ID number "EEPR,0M51"
000'' and convert it to the upstream ID number “1000”
and transmits it to the main device 101 as shown in FIG. 5A.

In the main device 101, the CPU 55 determines the ID number “000” sent from the terminal 50, and this
If it is confirmed that the D number is "000", the registration permission data with the downlink ID number "o o o o" attached at the beginning is transmitted to the terminal 50 as shown in FIG. 5A.

In the terminal 50, the CPU 13 receives the registration permission data from the main device 101 and causes the display 41 to display that registration is permitted. Next, select the I you want to register from the key matrix 25.
When a D number, for example “001°” is dialed, the CPU
13 is this ID number "001#" and the top ID
It is sent to the main device 101 with the number "1000" added thereto. If the ID number you want to register is the ID number of the last registered device plus "1" (this is usually the case for initial ID number registration), enter the ID number. In order to simplify the operation by 1%, you can, for example, just dial *“. In that case, C
PUI 3 has the dial data “*” and the upstream ID at the beginning.
It is sent to the main device 101 with the number "1000" added thereto. At the same time, the CPU 13 outputs "001" input by dial.
” or “*”, “1” is added to the previous ID number.
'' is added to the RAM as the ID number that you want to initially register.
19.

In the main device 101, the CPU 55 receives the ID number "001" to be initially registered sent from the terminal 50, and checks whether this ID number overlaps with any other already registered ID number. Additionally, if data "*" is sent from the terminal 50, the CPU 55 adds 1" to the previously registered ID number, sets this as the ID number to be initially registered, and checks for duplicates in the same way as above. As a result, if there is no duplication, the CPU 55 prints the downlink ID number "
0000" is sent to the terminal 50, and then the ID number to be initially registered, for example "001", is sent to the ID number registration area for the terminal 50 in the RAM 61.
Register.

In the terminal 50, the CPU 3 responds to the registration instruction data from the main device 101 and stores the ID number in the RAM 19 as an EE.
Register in FROM51. After the registration is completed, the CPU 3 transmits to the main device 101 write completion data with an uplink ID number "1001'" based on the registered ID number, for example "001", at the beginning.

When the main device 101 receives this, the CPU 55 cancels the ID number registration mode and sends the set ID number "001".
Registration mode cancellation data is sent to the terminal 50 with the downlink ID number "0001" based on the . In response to this, the terminal 50 cancels the registration permission display on the display 41.

Thereafter, the terminal 50 that has completed registration is removed from the main device 101, and the next terminal is connected to the main device 101 and the same registration operation as above is performed. In this way, each terminal 50
are connected to the main device 101 one by one and their ID numbers are registered, and after the registration of all the terminals 50 is completed, all the terminals 50 are multi-connected to the main device 101 and the system starts operating.

By the way, in the ID number duplication check in the above-mentioned registration process, ffl with other already registered ID numbers
If a duplicate is found, similar to the operation in the case of duplicate registration already explained with reference to FIG. Another ID number will be dialed again from the terminal 50.

Figure 5B shows an ID number different from the factory ID number '000''.
The terminal 50 with the D number, for example '100', is the main device 1.
This shows the operation when connected to 01.

In this case, the uplink ID number "1100" is transmitted from the connected terminal 50 to the main device 101. C of main device 101
When the PU 55 recognizes that the transmitted ID number "100" is different from the factory default ID number "000", the terminal 5
0, the unregistration data and unregistration warning sound each having a downlink ID number "0100" added to the beginning are transmitted.

In the terminal 50, the CPU 13 causes the display 41 to display that registration is not possible in response to the unregistration data, and causes the speaker 37 to output an unregistration alarm sound. Thereafter, this terminal 50 is removed from the main device 101, another terminal 50 in a factory-shipped state is newly connected to the main device 101, and the above-described registration operation is repeated again.

In the two preferred embodiments of the present invention described above,
There was only one terminal system that was multi-connected to the main device, but
As shown in FIG. 6, the present invention can be applied to any system having two or more multi-connection terminal systems.

In ID number setting in such a system having a plurality of multi-connected terminal systems, all the terminals 50,.

50..., 50, 50. 50nya 2. ...
2' n n1
150 to set a different ID number u1
1 is desirable. By doing so, for example, even if the terminal 50 of one terminal system is replaced with the terminal 50, +1 of the other terminal system, the ID number does not need to be changed (it can be used as is. If a restriction on making outside calls is imposed on the terminal 50, the restriction can still function effectively even if the terminal 50 is moved to another terminal system.

In FIG. 7, a terminal 50□ is connected to the main device 103.

Although a system in which 502, . When terminals are star-connected, originally,
Although it is not necessary to distinguish terminals by ID numbers, if a method of distinguishing terminals by ID numbers is adopted, for example, terminals 501 and 50
Even if you exchanged
This is convenient because there is no need to change the number (which is the same as the D number or has a one-to-one correspondence).

FIG. 8 shows an example of a format for uplink ID numbers and downlink ID numbers that is different from the above-mentioned embodiments.

In this format example, the upstream and downstream ID numbers include the system ID number. This system ID
The number is set for each main device, for example, at the time of factory shipment or installation. By using such a format, even if a terminal from another system is brought into one system and an attempt is made to connect and use it without permission, the terminal cannot be used, so there is an advantage that security can be maintained between systems.

When using such a format, the system ID number may be registered, for example, as follows. First, ROM59 or RAM61 in the main device 100.101
Set the system 10 number in advance. In the terminal ID number registration operation already explained with reference to FIGS. 3 and 5, when the main device 100.101 sends ID number registration instruction data to the terminal 50, the system
Send the D number to the terminal 50 at the same time and read the EEPRO of the terminal 50.
Register it in M51.

〔Effect of the invention〕

As explained above, according to the present invention, the ID number of each terminal is registered in the electrically rewritable nonvolatile memory of each terminal, and the rewriting cannot be performed unless predetermined conditions are met. This ensures security by preventing general users who do not know how to meet the specified conditions from rewriting ID numbers without permission, while also making it easy to register and rewrite ID numbers by electrically controlling the memory. This effect can be obtained.

Furthermore, since it is possible to check for duplicate ID numbers, duplicate registration is prevented and security can be maintained more reliably.

[Brief explanation of the drawing]

FIG. 1 is a block configuration diagram of a terminal constituting an embodiment of a terminal identification device for a communication system according to the present invention, and FIG.
A block configuration diagram of a key telephone main device constituting an embodiment of the present invention together with the terminal shown in the figure, FIG. 3 shows the terminal shown in FIG.
FIG. 4 is a block diagram of the main device constituting another embodiment of the present invention together with the terminal shown in FIG. 1; Figure 5 is a diagram showing the communication status of data exchanged during ID number registration between the terminal in Figure 1 and the main device in Figure 4, and Figure 6 is a diagram of a telephone system having a plurality of multi-connection terminal systems. System configuration diagram. Figure 7 is a system configuration diagram of a telephone system in which terminals are star-connected to the main unit. Figure 8 is a system configuration diagram of a telephone system in which terminals are star-connected to the main unit.
Figure 9 is a system configuration diagram of a general telephone system having multiple terminals connected to the main unit, and Figure 10 is a diagram of the format of communication data between terminals. FIG. 11 is a diagram showing a general format of data to be communicated, and is a block configuration diagram showing a terminal conventionally used in a system such as that shown in FIG. 7... Audio signal line, 9... Control data line, 13...
・CPU, 17...ROM, 19...RAM. 21... Input/output interface, 25... Key matrix, 33... Main device interface circuit, 50
...Terminal, 51...EEPR''OM, 53...Erasing/writing circuit, 55...C 61...RAM, 63 67...Terminal ink-up battery, 79...100.101 .1

Claims (1)

[Claims] 1. In a communication system in which a plurality of terminals are connected to a center and each of them communicates data with the center, an identification number of the terminal registered in advance is attached to the data to be communicated. In terms of identifying the terminal that is communicating,
Each terminal has an electrically rewritable terminal-side nonvolatile memory for registering its own terminal identification number, a rewriting means for rewriting the identification number registered in this memory, and each terminal provided at the center. an electrically rewritable center-side nonvolatile memory for registering each identification number of the terminal; a registration means for rewriting the identification number registered in this memory to a number rewritten by the rewriting means; means for determining whether to permit rewriting, and the rewriting means transmits data requesting rewriting to the determining means prior to rewriting,
The determining means sends data for permitting rewriting to the rewriting means only if a predetermined condition is satisfied upon receiving the data requesting rewriting, and the rewriting means receives the permission data from the determining means. A terminal identification device for a communication system, characterized in that it performs rewriting only when received. 2. The apparatus according to claim 1, further comprising means for inputting a code when performing rewriting, and the rewriting means inputs data indicating the input code together with the request data to the determining means prior to rewriting. and the determining means stores a preset code, and determines that the predetermined condition is satisfied when the stored code and the transmitted code match. terminal identification device for communication systems. 3. The apparatus according to claim 1, further comprising a switch housed in the cabinet of the center, the state of the switch being transmitted to the determining means, and the determining means receiving information from the rewriting means. 1. A terminal identification device for a communication system, characterized in that it is determined that the predetermined condition is satisfied if the state of the switch is a predetermined state when request data is received. 4. In the apparatus according to claim 1, the rewriting means transmits the new identification number to be rewritten to the determining means prior to rewriting, and the determining means determines that the predetermined condition is satisfied and that the number is A terminal identification device for a communication system, characterized in that data for permitting the rewriting is transmitted only when the identification number of another already registered terminal is not duplicated. 5. A terminal identification device for a communication system according to claim 1, wherein the terminals are multi-connected to the center. 6. A terminal identification device for a communication system according to claim 5, wherein the center has a plurality of multi-connection systems for the terminals. 7. The apparatus according to claim 1, further comprising means for transmitting registration instruction data to the rewriting means when the new identification number that the rewriting means is attempting to rewrite does not overlap with any other already registered identification number. Furthermore, it has
A terminal identification device for a communication system, wherein the rewriting means executes rewriting only when receiving both the permission data and the registration instruction data.