JPS6054557A - Management system of subscriber data - Google Patents

Abstract

PURPOSE:To prevent an error resulting from unnatural operation, by automatically rewriting subscriber data in a service device by only inputting rewritten information of a subscriber data management table from an input-output device connected to an exchange. CONSTITUTION:An exchange 10 and service device 20 connected to subscribers 1-3 are connected with each other through trunks 150 and 250 and a signal transmitter 160 and signal receiver 270 are installed to the exchange 10 and service device 20, respectively. When telephone numbers of the subscriber terminals 1-3 and rewriting information (register, change, deletion) corresponding the subscribers are inputted from the input-output device 120 of the exchange 10, a CPU110 rewrites a subscriber data management table A in the exchange. Rewriting data are sent from the transmitter 160 to the receiver 270 and the subscriber data management table B of the service device 20 is automatically rewritten. When a subscriber calls the service device 20, the subscriber number and recognition number are transferred from the table A to the table B and servicing works are started. Therefore, wrong servicing work is prevented.

Description

Detailed Description of the Invention (1) Technical Field of the Invention The present invention relates to an input/output system connected to an exchange in a communication system consisting of an exchange connecting subscriber terminals (including telephones) and service equipment. Following the registration, modification, and deletion of subscriber data (hereinafter referred to as "L&Rewrite information") on the device,
The present invention relates to a subscriber data management method that enables dynamic rewriting of subscriber data in a service device.

(2) Background of the technology In recent years, it has become possible to connect to an exchange, connect to a subscriber terminal via the exchange, and once send voice messages/fax messages to the subscriber terminal. Send a voice message/fax message, etc. to a specified destination.

Provides voice mail service/fax mail service, etc. There are service devices such as voice storage devices/fax storage and forwarding devices.

There are two ways to manage subscriber terminals in this service equipment: one is based on the phone number of the subscriber terminal assigned by the exchange, and the other is a system where the subscriber terminal is managed using an independent number separate from the phone number. However, the present invention relates to the former case. That is, regarding subscriber terminals within the communication system,
It is managed by both the exchange and the service equipment based on the telephone number.

(3) Problems with the Prior Art Hereinafter, a conventional subscriber data management system will be explained with reference to the drawings.

FIG. 1 is a block diagram showing the connection between an exchange and service equipment in the conventional system, FIG. 2 shows a conventional subscriber data management table, and FIG. , is a procedure flow for rewriting the subscriber data management table.

In FIG. 1, 1, 2.3 are subscriber terminals, 10 is a switch, 20 is a service device, 100.200 is a line switching unit (1-IW), and 110, 210 is a central processing unit (CPU).
), 120, 220 are input/output devices (Ilo), 130,
230 is a main memory (MM), 240 is a disk (D
K) and other storage devices.

Figure 2 fa1 and Figure 2 (b) show the structure of the subscriber data management table stored in the main memory of the exchange side and the service equipment side, respectively, and Figure (a) shows the installed/unimplemented subscriber terminal. , which manages terminal numbers, terminal attributes, etc. (b1
The figure shows management of αKl terminal number, terminal attributes, etc.

As shown in the procedure flow of FIG. 3, when rewriting the subscriber data management table ja) in the exchange, the exchange 10
When the telephone number of the subscriber terminal and the rewriting information corresponding to the subscriber are input from the input/output device 120 connected to (
Step 400), the central processing unit 110 of the exchange 10
For example, the content of the rewriting information is determined (step 401), and the subscriber data management table (a) in the exchange is rewritten according to the rewriting information.

(a) If the replacement information is registered, the newly input telephone number is registered in the subscriber data management table (al) in the exchange (step 402).

(b) If the rewriting information is changed, change the telephone number in the subscriber data management table (a) in the exchange that corresponds to the input telephone number before change to the new input telephone number ( Step 403).

(c) If the rewrite information is deleted, the subscriber data management table in the exchange corresponding to the input telephone number (a)
The telephone number within is deleted (step 404).

Also, subscriber data management table (b) in the service device
When performing rewriting, the telephone number of the subscriber terminal and the rewriting information corresponding to the subscriber are input from the input/output device 220 connected to the service device 20, as shown in the procedure flow of FIG. This is done in the same way as the procedure for changing the subscriber data management table in the exchange described above.

As mentioned above, according to the conventional method, a switching machine.

In order to rewrite each subscriber data in the service equipment, it is necessary to input the subscriber data rewriting information separately from each input/output device connected to the exchange and the service equipment and rewrite the data in °C. Therefore, there is a drawback that a discrepancy may occur between the subscriber data in the exchange and the subscriber data in the service device due to human error.

(4) Purpose of the invention The object of the present invention is to solve the problem of subscriber data within an exchange.

The service equipment rewrites the subscriber data in accordance with the subscriber data rewriting information in the input/output device connected to the exchange, without causing any inconsistency with the subscriber data in the service equipment. The object of the present invention is to provide a subscriber data management method that enables dynamic management of subscriber data.

(5) Structure of the Invention The present invention provides each subscriber terminal with an identification number that is different from a telephone number and can be uniquely recognized between an exchange and a service device, and the exchange has an identification number that can be uniquely recognized between an exchange and a service device. By providing a means for notifying the telephone number and identification number of the subscriber terminal, and providing the service device with a function to receive and process the information from the exchange, the subscriber terminal can receive the subscription information using the input/output device connected to the exchange. This enables the service device to dynamically rewrite subscriber data by following the subscriber data rewriting information G.

(6) Examples of the invention Embodiments of the present invention will be described below with reference to the drawings.

FIG. 4 is a block diagram showing the connection between an exchange and a service device representing one embodiment of the present invention.

FIG. 5 is a subscriber data management table representing an embodiment of the present invention, and FIG. 6 is a procedure flow representing an embodiment of the present invention.

The same reference numerals as in FIGS. 1, 2, and 3 indicate the same parts; 150 and 250 in FIG. 4 are trunks, 160 is a signal transmitter (SND), and 270 is a signal receiver (R).
EC), 350 in FIG. 5 Ca1 is a subscriber data management table on the exchange side that represents an embodiment of the present invention, and this table records information such as installation/uninstallation of subscriber terminals, terminal numbers, and identification numbers.

Terminal attributes, etc. are managed, and FIG.
Identification numbers, flags representing usage status of subscriber terminals, terminal attributes, etc. are managed.

The procedure for changing subscriber data in the exchange 10 will be described below.

As shown in the procedure flow of FIG. 6(a), when the telephone number 2 of the subscriber terminal and the rewriting information corresponding to the subscriber are input from the input/output device 120 connected to the exchange 10 (step 500) , the central processing unit 110 of the exchange IO determines the content of the rewrite information (step 501), and rewrites the subscriber data management table 350 in the exchange according to the rewrite information.

(a) If the rewriting information is registration, the newly input telephone number and unused identification number are registered in the table 350 (step 502).

(b) When the rewriting information is changed, the telephone number in the table 350 that corresponds to the manually entered telephone number before the change,
Change to the newly input phone number (step 503)
).

(c) If the rewriting information is deletion, the telephone number in the table 350 that corresponds to the manually entered telephone number.

Then, the identification number corresponding to the telephone number is deleted from the table (step 504).

In this way, the subscriber data management table 350 in the exchange is rewritten according to the input rewriting information.

After that, as shown in the procedure flow of FIG. 6(b), subscriber 1
(Telephone number - 3001) makes a call to access the service device 20 (step 600), the exchange 10 detects the call from the subscriber 1 (step 600).
Step 602): Determine whether the destination number is addressed to the service device 20 (Step 7).
03).

If the destination number is not addressed to the service device 20, the exchange l
O moves to the normal processing procedure.

If the destination number is addressed to the service device 20, the exchange l1A
taio is the subscriber data management table 35 in the exchange.
After searching for the identification number (1111) corresponding to the telephone number (3001) of the subscriber 1 (step 604), the destination service device 20 is notified of the incoming call (step 605). In response to this, the service device 20 accepts the incoming call (step 650). After notifying the incoming call (step 605), the exchange 10 sends the subscriber 1's telephone number (3001) and identification number (1111) to the signal transmitting device (SND) 16 to the cough service device 20.
0 (step 606).

In response, the service device 20 receives the telephone number (300L) and identification number (1111) of the subscriber 1 through the signal receiving device (REC) 27'0 (step 65).
1) Search whether the identification number (1111) exists in the subscriber data management table 360 in the service device (step 652).

(d) If the identification number (11, 11) is not found, the telephone number (300
Step 655: 1) and the identification number (1111) are registered in the subscriber data management table 360 in the service device.
), the flag is set to "1" (step 656).

(e) If the identification number (1111) is found, the telephone number corresponding to the identification number (1111) and the telephone number (3001 notified by the exchange corresponding to the identification number (1111)) are the same. Determine whether the
step 653).

(i) If the telephone numbers match, set the flag to 1'' (step 656).

(ii) If the telephone numbers do not match, change the identification number (1111) to the telephone number (3001) notified by the exchange (step knob 654), and then set the flag to "1". (Ste Nobu 656).

After the above operations, the service device 20 sends an acceptance response to the exchange 10 (Step 57), and the subscriber 10 confirms the response from the service device 20 (Step 607). ) The line between the subscriber 1 and the service device 20 is connected (Steps 608 and 658), and the service device 20 starts the service.

Further, in the service device 20, a subscriber data management program is periodically activated. When the program is started, as shown in the procedure flow of FIG.
0), if the flag is set to ``0'', the identification number and telephone number are deleted (step 702); otherwise, the flag is set to ``0'' (step 701).

In this way, the above operation is repeated for all subscribers (step 703), and after the processing for all subscribers is completed, the execution of the program is terminated.

According to an embodiment of the present invention, by simply inputting the rewriting information of the subscriber data management table from the input/output device connected to the exchange, the subscriber data in the service device is dynamically updated according to this information. Therefore, inconsistencies due to human error will no longer occur between the subscriber data in the exchange and the subscriber data in the service equipment.

In the above example, the subscriber data management table in the service equipment is dynamically changed to Y! by rewriting the subscriber data management table in the exchange. As an example of its application, it is possible to dynamically rewrite the subscriber data management table in the exchange by rewriting the subscriber data management table in the service equipment.

(7) As described in detail, according to the present invention, by simply inputting the rewriting information of the subscriber data management table from the input/output device connected to the exchange, the rewriting information of the subscriber data management table can be followed, and the artificial This is effective because the subscriber data in the service device can be dynamically rewritten without causing inconsistencies due to erroneous operations.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the connection between the exchange and the service equipment in the conventional system. Diagram C81 in FIG. FIG. 3 is a procedure flow showing the subscriber data rewriting procedure in the conventional system,
FIG. 4 is a block diagram showing the connection between an exchange and a service device representing one embodiment of the present invention, and FIG.
The figure shows the switch side. FIG. Registration of data management table. Addition, change, deletion procedure flow, (b) figure shows registration and addition of subscriber data management table in the service device. Flowchart of change procedure; Figure (C) does not show the flow of procedure for deleting the subscriber data management table in the service device. 1.2, 3: subscriber terminal, 10; exchange, 20 = service equipment, 100, 200: line switching unit (HW), 110
, 210: Central processing unit (CPU), 120, 220:
Input/output device (Ilo), 130.230: Main storage device (
MM), 240: Disk (DK), 150,250
: ) Rank, 160: Signal transmitter (SND), 27
0: Signal receiving device (REC), 350: Subscriber data management table on the exchange side, a6o: Subscriber data management table on the service device side.

Claims (1)

[Claims] In a communication system consisting of an exchange that connects subscriber terminals each having a number, and a service device that connects to the exchange and provides services to the subscriber terminals, a telephone number is different from a telephone number, and the exchange and the service device A uniquely recognizable number is assigned to each subscriber terminal, and the exchange and service equipment manage subscriber terminals based on this number. , provide the telephone number of the subscriber terminal and a means for notifying the number;
By providing the service device with a function to receive and process the information from the exchange, it can follow the registration, change, and deletion of subscriber data in the input/output device connected to the exchange,
Dynamically register, change, and update subscriber data on service devices
Subscriber data management method that allows deletion